FA-55403 / Astronomical coordinate conventions / Member archive

Orbital phase labels: Eclipse-centered phase omits the catalog phase-zero shift · case 03

The adapter reports an incorrect eclipse phase while other fields remain valid.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

A folded-orbit coordinate has period P>0, elapsed time t from periastron, and phase offset q in cycles. Phase is fractional cycle, cycle index is floor quotient, mean anomaly is phase times a full turn, and eclipse phase offsets are explicit. No orbital dynamics is solved. Output fields are defined by: phase = (d['t']/d['P']+d['q'])%1; cycle_index = int((d['t']/d['P']+d['q'])//1); mean_anomaly = 360*((d['t']/d['P']+d['q'])%1); phase_zero_epoch = d['epoch']-d['q']*d['P']; eclipse_phase = ((d['t']/d['P']+d['q'])-d['eclipse'])%1; phase_rate = 1/d['P']

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 5	`{"cycle_index": 1, "eclipse_phase": 0.8999999999999999, "mean_anomaly": 233.99999999999997, "phase": 0.6499999999999999, "phase_rate": 0.1, "phase_zero_epoch": 102.5}`	`{"cycle_index": 1, "eclipse_phase": 0.3999999999999999, "mean_anomaly": 233.99999999999997, "phase": 0.6499999999999999, "phase_rate": 0.1, "phase_zero_epoch": 102.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.