Skip to content

Conversation

@ShrimpCryptid
Copy link
Contributor

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.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • This change requires updated or new tests

Change summary:

  • Tidy, well formulated commit message
  • Another great commit message
  • Something else I/we did

Steps to Verify:

  1. A setup step / beginning state
  2. What to do next
  3. Any other instructions
  4. Expected behavior
  5. Suggestions for testing

Screenshots (optional):

Show-n-tell images/animations here

Keyfiles (delete if not relevant):

  1. main file/entry point
  2. other important file

Thanks for contributing!

@ShrimpCryptid ShrimpCryptid self-assigned this Nov 19, 2025
@ShrimpCryptid ShrimpCryptid added the new feature New feature or request label Nov 19, 2025
@ShrimpCryptid ShrimpCryptid changed the title fix: Validate 3D source paths feat: Validate 3D source paths (3D paths pt. 2) Nov 19, 2025
@ShrimpCryptid ShrimpCryptid changed the base branch from main to fix/writer-warn-3d-paths November 19, 2025 22:51
@ShrimpCryptid ShrimpCryptid force-pushed the fix/warn-invalid-3d-paths branch from 827876f to 69b7502 Compare November 19, 2025 22:56
Base automatically changed from fix/writer-warn-3d-paths to main November 21, 2025 23:00
from colorizer_data.utils import (
INITIAL_INDEX_COLUMN,
_get_frame_count_from_3d_source,
get_frame_count_from_3d_source,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed this function

Comment on lines +453 to +455
("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.
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants