Failed to load DICOM SEG series using dicom study json
See original GitHub issueBug Report
Describe the Bug
When loading a study via the Study Dicom Json and the study contains a series and its segmentation (DICOM SEG), the viewer fails to load the segmentation series:
error messages:
- ToolbarRow: Cannot read properties of undefined (reading ‘SeriesInstanceUID’)
- Referenced series for SEG dataset not present.
- Source data not present
Interestingly, the exact same series load correctly together when using the viewer /local
route:
Running OHIF Viewer 4.12.18 from the docker hub. Also just tested in 4.12.19 local dev branch.
What steps can we follow to reproduce the bug?
- Have a set of a dicom image and a dicom-seg segmentation made using e.g. dcmqi (DICOM for Quantitative Imaging) library
- Have a dicom json containing two series 1) original dicom image and 2) dicom segmentation
- Load the dicom json using the route
/viewer?url=<json_url>
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Unable to load DICOM segmentation - 3D Slicer Community
I'm trying to load a DICOM segmentation. I looked through other similar posts, but they didn't help me. Unfortunately I cannot share the...
Read more >Writing DICOM-SEG — pydicom-seg 0.2.0-dev documentation
For writing DICOM-SEG files, some information besides the segmentation data is ... The resulting metainfo.json file can be loaded using a compatibility ...
Read more >Frequently Asked Questions (FAQ) - dcmqi-guide - GitBook
I cannot load DICOM SEG into Slicer · Conversion fails with the "Missing Attribute(s)" error - what should I do? · I cannot...
Read more >How does DICOM support big data management ...
This work aims to verify whether the advanced features of the DICOM standard, beyond imaging data storage, are effectively used in research ......
Read more >DICOM re‐encoding of volumetrically annotated Lung ... - NCBI
DICOM SEG objects have a number of desirable features for encoding segmentations. ... the segmentation was populated using a schema‐constrained JSON file.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After fixing the
ReferencedSeriesSequence
, now it’s failing because it misses another SQ metadata,PerFrameFunctionalGroupsSequence
. I find it inconvenient to having to serialize these data into the dicom json, when the OHIF can actually correctly parse them by itself. Is it possible to let OHIF fetch these missing metadata directly from the dicom files?you can activate the OHIFDicomTagBrowserExtension https://github.com/OHIF/Viewers/blob/master/platform/viewer/src/index.js#L57 for your local build, and you can explore the DICOM structure. I hope it helps.