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

ENH: use SegmentDescription to populate SegmentLabel #488

Merged
merged 2 commits into from
Jan 12, 2024

Conversation

fedorov
Copy link
Member

@fedorov fedorov commented Jan 12, 2024

This will be done when SegmentLabel is not passed in configuration. SegmentDescription is better than using CodeMeaning from SegmentationType, as it allows more precise control by the user.

This will be done when SegmentLabel is not passed in configuration.
SegmentDescription is better than using CodeMeaning from SegmentationType,
as it allows more precise control by the user.
fedorov added a commit to fedorov/CloudSegmentator that referenced this pull request Jan 12, 2024
Without SegmentLabel in JSON, dcmqi currently uses the heuristic to populate
it from SegmentedPropertyTypeCodeSequence>CodeMeaning, which is suboptimal, since
it does not take into account laterality. At the same time, SegmentLabel is used
both by OHIF and Slicer (see https://github.com/QIICR/QuantitativeReporting/blob/master/DICOMPlugins/DICOMSegmentationPlugin.py#L202)
to initialize segment names shown to the user. Related to this PR that will
revisit the heuristic used by dcmqi, and use SegmentDescription if SegmentLabel
is not available before defaulting to segmented property type code meaning:
QIICR/dcmqi#488
@fedorov fedorov merged commit d865fca into QIICR:master Jan 12, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant