Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SEG source series should also be parsed from SourceImageSequence
See original GitHub issueRequest
SourceImageSequence should be parsed to determine the image series that is associated with segmentation.
Why should we prioritize this feature?
As observed from debugging https://github.com/ImagingDataCommons/IDC-WebApp/issues/238, segmentations from TCIA ISPY collection are using SourceImageSequence, not ReferencedImageSequence to refer to the image series segmented.
In the retrospect, I wonder if the approach used in I-SPY is the correct one. We use ReferencedImageSequence in dcmqi, and @dclunie never called out for using SourceImageSequence, so maybe what we do in dcmqi is still the right way to do it. Need to check with David.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@JamesAPetts yes, when I read it, I had the same thought, but it is the case that what we have in dcmqi was checked and double checked by David Clunie via our joint work on many datasets we shared created by dcmqi, so I am puzzled … I will ask David when I get a chance.
Going to close this for now, I’ve made the required upgrades to read all the data I can see on IDC. I tested 20-30 studies looking for edge cases but all seem good now. If you find an edge case/if there is any fundemental issue you encounter please open another ticket.
Thanks.