-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Validate 3D source paths (3D paths pt. 2) #99
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
base: main
Are you sure you want to change the base?
Conversation
827876f to
69b7502
Compare
| from colorizer_data.utils import ( | ||
| INITIAL_INDEX_COLUMN, | ||
| _get_frame_count_from_3d_source, | ||
| get_frame_count_from_3d_source, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renamed this function
| ("source") and channel ("segmentation_channel") to use for the 3D image source. The source | ||
| must be either a URL or a path inside the output dataset directory. If `None`, 3D frames | ||
| will not be included in the dataset. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have an idea for supporting files outside the output dataset directory via symlinks, which I'll open as pt. 3 of this chain. For now, enforcing that paths must be inside the output dataset directory (or be a URL) will prevent loading errors, but it potentially requires users to move their (huge) Zarr data around.
Problem
What is the problem this work solves, including
Link to story or ticket
Solution
What I/we did to solve this problem
with @pairperson1
Type of change
Please delete options that are not relevant.
Change summary:
Steps to Verify:
Screenshots (optional):
Show-n-tell images/animations here
Keyfiles (delete if not relevant):
Thanks for contributing!