j0126 tutorial: clarify native resolution and add data download script - #218
Merged
Conversation
… docs The volume is 9 x 9 x 20 nm (native FFN mip 0), not 10 nm isotropic. Verified: im_align_10nm.zarr/0 is byte-identical to rawdata_realigned mip 0 at the same coordinates on scattered blocks, and its voxel grid [5700, 10913, 10664] matches mip 0 exactly -- a 20 -> 10 nm z-resample would have doubled z. So: * resolution [10,10,10] -> [20,9,9] in both step-1 configs (inert for training, where it only feeds nnU-Net source_spacing, but it is what the configs document about the data); * the zero-shot config no longer instructs a resample that never happened and that the reference runs never used; * params.data.raw_10nm -> raw_em, with the misnomer documented. The data.test `name` stays im_align_10nm: it is baked into the artifact filenames step 2 reads. 2_abiss.yaml's resolution_xyz [10,10,10] is left alone: it is fail-closed checked against already-built precomputed layers, and error correction already uses the correct [20,9,9] (skeletonize.py NATIVE_RESOLUTION_ZYX_NM), so only the neuroglancer display scale is affected. 1_affinity_supervised.yaml now trains on a real 25/8 held-out split (sorted cube names, every 4th from index 2 to val), instead of validating on 3 cubes that were also in train. The released checkpoint and every number in the results table predate this split and are noted as such. The recipe itself is unchanged from base_banis+_zebrafinch_heavy: lr 1e-3, 200k steps, batch 8, patch [48,96,96], aug_em_neuron, from scratch. Docs: resource budget -> RESOURCE.md, staged storage cleanup -> CLEANUP.md, and a new Step 0 that downloads the labelled cubes from HuggingFace and the EM volume with the new scripts/download_precompute.py (source location as argument, mip 0, resumable, shardable). Smoke-tested: a downloaded crop is bit-identical to the local reference zarr. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR clarifies the j0126 tutorial's data resolution and adds tooling to download the EM volume from the public mirror. The key insight is that the native FFN grid is 9 × 9 × 20 nm (x, y, z), not 10 nm isotropic as previously implied. All published results use this anisotropic native resolution.
Key Changes
Documentation & Configuration:
im_align_10nm.zarrstore is byte-for-byte equal to mip 0 (9 × 9 × 20 nm), not a 10 nm isotropic resample[10, 10, 10]to[20, 9, 9](ZYX native grid)Data Access:
--bboxfor testing--shard-id/--num-shardsfor whole-volume runsREADME Reorganization:
Notable Details
https://claude.ai/code/session_014WVoz5xNr9MAkRpdGRytt7