QuantitativeReporting
QuantitativeReporting copied to clipboard
Segmentation-based measurements with DICOM import and export of the results.
Before, only single length types were supported (SRT G-D7FE). This commit adds support for measurements with a long axis (SRT G-A185) and a short axis (SRG G-A186) by creating one...
I cannot find the QuantitativeReporting extension in the ExtensionManager in the Slicer preview release(s). I tried it with a few preview releases, the latest one were I could not find...
Since the DICOM file name is initialized using the current date and time, exporting in the same directory overwrites the previous file. https://github.com/QIICR/QuantitativeReporting/blob/87852c8460ed54de70e8c838f16ddf62da539546/DICOMPlugins/DICOMSegmentationPlugin.py#L351 https://github.com/QIICR/QuantitativeReporting/blob/87852c8460ed54de70e8c838f16ddf62da539546/DICOMPlugins/DICOMSegmentationPlugin.py#L437-L440
This parses specific TID 1500 AI results that contain a rectangle and a score for each detection. It is fairly special-purpose but make this code a more general than the...
follow up on https://discourse.slicer.org/t/loading-dicom-segmentation/14139/12
See: https://github.com/QIICR/QuantitativeReporting/pull/235/#discussion_r428336109
See: https://github.com/QIICR/QuantitativeReporting/pull/235/#discussion_r231232692
See discussion here: https://github.com/QIICR/QuantitativeReporting/pull/235/#discussion_r231214396
At the very least, it should give an error message and not abort as it is right now. Ideally, it probably would make sense to automatically export reference volume as...
I am trying to open dicom segmentation storage on slicer using quantitative reporting and for some of the dicom I get an error (which is strange because all are generated...