Skip to content

[Sad Catapella B6][Scientific QA] Malformed explicit NGFF coordinate transforms are silently treated as unknown calibration #94

Closed

Description

@guijacquemet

Scope and classification

Sad Catapella Batch 6 at d7a538e56d41ac1093ba79adcad397c21b3dfd32. Confirmed diagnostic gap with deliberate fallback behavior (there are tests that explicitly accept this). This issue proposes a stricter scientific QA policy, not a claim that pixel data are misread. Distinct from #73 (missing axes) and closed #39 (unknown-scale placeholder).

Evidence

Counterexample / impact

An OME-Zarr experiment where each image explicitly declares coordinateTransformations as a dictionary instead of a list passes pixel preflight with physical_sizes=PhysicalSizes(). If every image has this malformed field, there is no missing_pixel_size or invalid_calibration warning. Scientifically valuable calibration metadata are silently discarded; the cause is absent from normal outputs, potentially making downstream analyses appear merely uncalibrated.

Proposed policy and acceptance

Differentiate (a) not provided size (validly unknown) from (b) explicitly provided but malformed transform (invalid metadata). Keep pixels readable if desired, but emit a path-specific, actionable invalid_physical_calibration issue in preflight and run, optionally block calibrated downstream outputs. Do not silently substitute 1 µm or require all images to be calibrated. Add mixed and all-malformed datasets, zero/negative scales, invalid arrays, unsupported transform types, valid unknown-scale marker, and checks that warnings survive manifest/report writing. Requires an explicit severity decision, no Numba.

Activity

  1. added a commit that references this issue on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions