Repository navigation
Match segmentation filenames by default - #1002
Merged
Merged
Conversation
✅ Deploy Preview for volview-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
PaulHax
force-pushed
the
segmentation-filename-matching
branch
from
October 29, 2026 00:53
89ea736 to
492e025
Compare
PaulHax
marked this pull request as ready for review
October 29, 2026 00:54
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.
Loading an image with a matching
.segfile now imports its labels as segments without an IO configuration file. SettingsegmentationExtensionto an empty string disables automatic matching.Filename matching requires a dot, dash, or underscore after the base-name prefix, so
patient001-tumor.seg.nrrdmatchespatient001.nrrdwhilepatient0012.seg.nrrddoes not. See the filename matching implementation.