You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data-flow audit 2026-10-29 (H1), MINOR. At v0.3.1.
Unknown pixel size written as scale 1. In the OME-Zarr copies, physical_sizes.py:133-136 and zarr_export.py:414-425 write scale 1 with no unit. Leave the transform out, or record that the size is unknown.
Manifest flags read with bool().manifest.py:351,376,547 turn "false" into True. Accept JSON booleans only.
No per-file axis roles in the manifest. Consumers rebuild them from the experiment's mapping, which is wrong for OME-Zarr files whose declared order differs. Record each file's roles.
CSV columns ignored. The normalization v0.3.1 CSV reader ignores the plane_id, image_file and bit_depth columns and recomputes plane_id, so an inconsistent row is accepted. Check them.
Labels above 2^63. uint64 masks with labels above 2^63 are accepted but cannot become an int64 label_id downstream. Refuse them.
Version type in the contract. Contract §9 shows manifest_version/schema_version as numbers, but they are written as strings ("1", "4"). Say so in the contract.
Activity
Make the manifest writer strict about flags too
Refuse non-boolean run flags before reading any image
guijacquemet commentedon Oct 30, 2026
Every item is now on main:
channel_names_trimmed: Read and write channel_names_trimmed as a strict manifest flag #45;plane_id,image_file,bit_depth): in normalization#19, pinned through normalization v0.3.2 in Pin the normalization brick to its release v0.3.2 #47, with a regression test here.This issue was already closed when #44 merged. With the pin in, nothing remains, so it stays closed.
Generated by Claude Code