[BUG FIX] - Segmentation fails for DCM spec files - OspreyCoreg Ospre… #508
Conversation
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
…ySeg - Stella Hadfield Elliot This bug was related to the fact that DCM files have no filename during the fileparts generation of the file input. Therefore, they were always flagged as SameName files. However, without a filename the OspreySeg output resulted in similar file names for all datasets. This has now been fixed for OspreyCoreg and OspreySeg.
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.
…ySeg - Stella Hadfield Elliot
This bug was related to the fact that DCM files have no filename during the fileparts generation of the file input. Therefore, they were always flagged as SameName files. However, without a filename the OspreySeg output resulted in similar file names for all datasets.
This has now been fixed for OspreyCoreg and OspreySeg.