FA-55985 / Astronomical coordinate conventions / Member archive

Barycentric arrival corrections: Barycentric geometric delay omits source-direction projection · case 05

The adapter reports an incorrect roemer delay while other fields remain valid.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

A supplied timing adapter has observer position r projected onto source direction n, speed c>0, Einstein delay E, Shapiro delay S, and geocenter projection g. Barycentric arrival is t+r*n/c+E+S. This model composes explicit corrections only and does not calculate ephemerides or relativistic delays. Output fields are defined by: roemer_delay = d['r']*d['n']/d['c']; arrival = d['t']+d['r']*d['n']/d['c']+d['E']+d['S']; topocentric_residual = (d['r']-d['g'])*d['n']/d['c']; geocentric_arrival = d['t']+d['g']*d['n']/d['c']+d['E']+d['S']; observer_arrival = d['t']-d['r']*d['n']/d['c']-d['E']-d['S']; geometric_rate = d['n']/d['c']

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	`{"arrival": 112.0, "geocentric_arrival": 109.0, "geometric_rate": 0.5, "observer_arrival": 96.0, "roemer_delay": 2.0, "topocentric_residual": 3.0}`	`{"arrival": 112.0, "geocentric_arrival": 109.0, "geometric_rate": 0.5, "observer_arrival": 96.0, "roemer_delay": 4.0, "topocentric_residual": 3.0}`	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.