Open PaulHax opened 1 week ago
Built without sensitive environment variables
Name | Link |
---|---|
Latest commit | 445fa47fa06182905c8089cf68a907c5201e86db |
Latest deploy log | https://app.netlify.com/sites/volview-dev/deploys/66ff21e7fc3c1c0008ce0ca2 |
Deploy Preview | https://deploy-preview-653--volview-dev.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Short putt: turn mergeSegments option to true and expect one component image as output.
Just to make sure there is no misunderstanding here. mergeSegments
option will merge non-overlapping segments into minimal number of files. So if SEG does not have any overlapping segments, unless there is a bug, you should get only one file when mergeSegments
is on. But if some segments overlap, they will be saved into separate files with mergeSegments
on. TotalSegmentator should not produce overlapping segments. But you can look at the NSCLC-Radiomics or QIN-Prostate-Repeatability collections that contains overlapping segments:
NSCLC-Radiomics example: https://viewer.imaging.datacommons.cancer.gov/viewer/1.3.6.1.4.1.32722.99.99.203715003805996641695765332389135385095
QIN-Prostate-Repeatability example: https://viewer.imaging.datacommons.cancer.gov/viewer/1.3.6.1.4.1.14519.5.2.1.3671.4754.121472087445374646718121301133
@jadh4v - one of the above would be a good sample to include in testing in https://github.com/InsightSoftwareConsortium/ITK-Wasm/issues/1208.
As always, to download the images in the above example, you can use StudyInstanceUID
available in the URL and idc-index
package:
$ pip install idc-index --upgrade
$ idc download 1.3.6.1.4.1.14519.5.2.1.3671.4754.121472087445374646718121301133
Note that to see overlapping segments in the above I used OHIF v2. The current OHIF v3 cannot display overlapping segments as of yet, see https://github.com/OHIF/Viewers/issues/3496.
I did misunderstood. Thanks for the clarification and files.
Changed to do the wrong thing better. That is: just using the first output file and popping a warning.
mergeSegments
option to true, pull first output file/component for use as segment group, and pop a warning.closes #639
Suggest we just put these in an issue and not do in this PR: