FA-54847 / Astronomical coordinate conventions / Member archive

Detector cutout reference: Vertical reference pixel reads the horizontal cutout metadata · case 02

The adapter reports an incorrect crpix y while other fields remain valid.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

A one-based FITS-like detector cutout has zero-based start sx,sy, explicit halo hx,hy, and unchanged plate scale. CRPIX belongs to the padded cutout; valid bounds exclude halo. Data section uses inclusive pixel endpoints. Output fields are defined by: crpix_x = d['rx']-d['sx']+d['hx']; crpix_y = d['ry']-d['sy']+d['hy']; science_first_x = d['hx']+1; science_last_x = d['hx']+d['w']; parent_first_y = d['sy']+1; parent_last_y = d['sy']+d['h']

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	`{"crpix_x": 11, "crpix_y": 18, "parent_first_y": 8, "parent_last_y": 37, "science_first_x": 3, "science_last_x": 22}`	`{"crpix_x": 11, "crpix_y": 15, "parent_first_y": 8, "parent_last_y": 37, "science_first_x": 3, "science_last_x": 22}`	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.