Describe Your Question
- A clear and concise description of what problem you are having.
Hello, I have a single file, large, multi frame CT image. If I load it using the the static-wado-webserver after preparing it with static-wado-creator it loads fine and I am able to do MPR and 3D reconstructions. It also works fine if I use the local load option.
If instead I use the provided dicom-json-generator.js script and serve both the generated metadata json and the dicom file statically, the image loads, I am able to navigate through the series but the 3D reconstruction is all messed up and different.
It works fine for single frame multiple file studies produced by the same modality.
There are no visible messages or errors on the javascript console.
Why is the behavior not consistent? What metadata information is missing from the json file produced by the dicom-json-generator script that could be preventing the correct rendering of the 3D image?
Will this be even possible via dicom-json? If I understand things correctly DICOMWeb works slightly differently with multi framed studies since each frame is “sliced” and served separately from the server.
Please see the attachment for a comparison
- Which OHIF version you are using?
v3.11.0-beta.11