FA-55039 / Astronomical coordinate conventions / Member archive

Redshift wavelength grid: Equivalent width is treated as an integrated flux quantity · case 04

The adapter reports an incorrect rest equivalent width while other fields remain valid.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

For this catalog adapter, redshift factor f=1+z is provided as positive integer f. Rest wavelength, rest bin width, observed line wavelength, observed equivalent width, and wavelength density obey their explicitly stated f-scalings. No velocity convention is inferred. Output fields are defined by: rest_wavelength = d['obs']/d['f']; rest_bin_width = d['width']/d['f']; predicted_line = d['rest']*d['f']; rest_equivalent_width = d['ew']/d['f']; rest_density = d['density']*d['f']; bin_integral = d['density']*d['width']

Why this case matters

Catalog, detector, sky-coordinate, and spectroscopy adapters must preserve the association between numeric coordinates and their declared reference conventions.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
astronomical fixture 0	`{"bin_integral": 24, "predicted_line": 80, "rest_bin_width": 4.0, "rest_density": 6, "rest_equivalent_width": 6, "rest_wavelength": 61.5}`	`{"bin_integral": 24, "predicted_line": 80, "rest_bin_width": 4.0, "rest_density": 6, "rest_equivalent_width": 3.0, "rest_wavelength": 61.5}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.