FA-56298 / Astronomical coordinate conventions / Member archive

Spectral reference frame chain: LSR spectral shift is skipped after an independent barycentric correction · case 03

The adapter reports an incorrect apply lsr while other fields remain valid.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

A finite spectral frame adapter supplies topocentric frequency f and additive shifts a=topocentric-to-barycentric, b=barycentric-to-LSR, and g=geocentric-to-barycentric. These are stipulated precomputed coordinate shifts in common units, not physical velocity or Doppler formulas. Provenance booleans mark shifts already applied. Output fields are defined by: lsr_frequency = d['f']+d['a']+d['b']; geocentric_frequency = d['f']+d['a']-d['g']; apply_barycentric = d['f'] if d['bary_done'] else d['f']+d['a']; apply_lsr = d['f'] if d['lsr_done'] else d['f']+d['b']; recover_topocentric = d['f']-d['a']-d['b']; lsr_from_geocenter = d['f']+d['g']+d['b']

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 2	`{"apply_barycentric": 106, "apply_lsr": 109, "geocentric_frequency": 104, "lsr_frequency": 113, "lsr_from_geocenter": 111, "recover_topocentric": 91}`	`{"apply_barycentric": 106, "apply_lsr": 102, "geocentric_frequency": 104, "lsr_frequency": 113, "lsr_from_geocenter": 111, "recover_topocentric": 91}`	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.