-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support for DICOM #32
Comments
Hi @sarthakpati Thanks for suggesting 😃 Cheers, |
Yup, it is the same on our side. I'll put this on our list, too. 😄Will coordinate here. |
Hey, Cheers, |
Hi @benmalef and @sarthakpati Thank you for offering to contribute! The basic idea for supporting file formats that can not be read by tifffile, is to provide an Array like interface to the new format, which then lazily loads only the data needed to return a specific slice. You can look at the open draft PR for mirax support, where I use kerchunk to build an index for reading the compressed image data via zarr. You could do something similar for DICOM I suppose. Another option is to look at something like pydicom, and see if it either provides that array interface, or if it can be wrapped to do so. In the end what you should try is to have the pyramidal image stack for the main image as the I'm happy to give feedback on PRs, but can't guarantee prompt answers due to other projects having priority right now. Also let me know if you need more information to get started. Cheers, |
Just pinging for awareness: On the Bayer side @sdvillal @wolny -- is there someone to provide more immediate feedback for this these days? Or does BigPicture have an interest in support for DICOM here @erikogabrielsson ? |
From my side I'd also be happy to provide feedback on PRs. Simple solution would be to add |
Hey,
It would be great to add the ability to support WSI DICOM. There is a very nice library called wsidicom that takes care of it in a nice way.
Cheers,
Sarthak
The text was updated successfully, but these errors were encountered: