FA-53328 / Raster memory layout / Member archive

Four Tap Sensor Storage: Tap packet start uses logical tap order or drops relocation · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at packet_origin.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

A stipulated even-sized sensor splits the image into four quadrants. Each readout tap scans toward the center: right taps reverse x, bottom taps reverse y. Tap packets have three-byte headers and are stored in order [2,0,3,1]. Return the named intermediate layout descriptor and final address fields; all quantities are integer byte offsets unless explicitly stated.

Why this case matters

Offline raster resource, upload, readback, and storage-layout regression model.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
layout fixture 1	`{"address": 24, "allocation_end": 417, "half_height": 4, "half_width": 6, "local_x": 0, "local_y": 0, "packet_origin": 21, "packet_pitch": 99, "storage_slot": 1, "tap": 0}`	`{"address": 123, "allocation_end": 417, "half_height": 4, "half_width": 6, "local_x": 0, "local_y": 0, "packet_origin": 120, "packet_pitch": 99, "storage_slot": 1, "tap": 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.