Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with original syntax - image format from aws #36

Open
federicomarollatouch opened this issue Jan 9, 2025 · 0 comments · May be fixed by #37
Open

Error with original syntax - image format from aws #36

federicomarollatouch opened this issue Jan 9, 2025 · 0 comments · May be fixed by #37

Comments

@federicomarollatouch
Copy link

federicomarollatouch commented Jan 9, 2025

Hi,

Version: 3.8.5

I have an issue when trying to load a study with the transfer syntax 1.2.840.10008.1.2.4.91. When the image is downloaded via the API /datastore/<datastore_id>/imageSet/<imageset_id>/getImageFrame, it is returned as image/j2c (as also indicated in the official documentation) unlike other studies (e.g., with syntax 1.2.840.10008.1.2.4.202) that return image/jph.

This seems to cause an exception that prevents the images from loading:

loadImageToCanvas.ts:156  
_setThrew is not defined wadors:undefined/studies/.../series/.../instances/.../frames/1?accept=image/jphc&DatastoreID=...&frameID=...&ImageSetID=....&healthlake=true

I replaced the actual data with ....

The same study, when decompressed with the previously mentioned syntax, opens correctly. Is this issue caused by OHIF, or is it a problem with loading from AWS? Is it mandatory to decompress the DICOMs, or could there be another solution?

EDIT 13.01.24:
There is also another error that clearly says that a jph file is not returned.

ojph error 0x00050044 at ojph_params.cpp:597: Rsiz bit 14 not set (this is not a JPH file)

But why using the local viewer and directly loading these original files the images are loaded correctly?

Thank you,
regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant