Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert incoming data to appropriate resolution for all GT #48

Open
5 tasks done
Tracked by #47
rhoadesScholar opened this issue Nov 26, 2024 · 1 comment
Open
5 tasks done
Tracked by #47
Assignees
Labels

Comments

@rhoadesScholar
Copy link
Member

rhoadesScholar commented Nov 26, 2024

This should coincide with a significant refactor of how TEST_CROPS are declared:

  • The repo should include a test_manifest.csv that has the following columns:
  1. crop_name
  2. dataset
  3. class label
  4. voxel_size
  5. translation (on nm)
  6. shape (in voxels)
@rhoadesScholar
Copy link
Member Author

rhoadesScholar commented Nov 27, 2024

Function to appropriately rescale/crop predictions to match the test crops' resolutions, both before and after participant submissions. Should be called by package_submission() thus allowing participants to preview the results of the conversion, before submitting the data. Should work for both OME-NGFF metadata and classic metadata options.

From Saalfeld:
incoming test volumes may declare their resolution, if present and different from reference resolution, scale before evaluation, spec for scaling:

  • coordinates indicate the front top left voxel corner
  • binary labels are scaled using bilinear interpolation (upscaling or downscaling by factors <=2)) or volume averaging (downscaling by factors > 2) followed by thresholding
  • enumerated labels are scaled using nearest neighbor interpolation (upscaling) or volume max (downscaling), special implementations for integer downscaling factors appreciated, non-integer downscaling may be approximated by downscaling to nearest integer followed by nearest neighbor downscaling for the rest

Then:

  • Add above to README

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant