-
Notifications
You must be signed in to change notification settings - Fork 3
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
Compression error/ how to define the "compression_type" argument? #22
Comments
@Phlpp-S
However
This is caused by the line @jwindhager what do you think? |
Hi @Milad4849 Without looking into this in too much detail, I would suspect that the Searching for
As you can see in xtiff's setup.cfg, the last tested version for xtiff was 2022.4.22. I therefore see two options:
Option 1 is probably the easiest, but xtiff seems to be used quite regularly, still (it's also a dependency of steinbock!). In general, I suspect that tifffile has become much more powerful wrt. OME-TIFF since the last version of xtiff was released, so I'm not sure how justified xtiff's existence still is nowadays? @Phlpp-S as a quick fix, could you try installing |
Hi @Milad4849 and @jwindhager , thank you very much for taking a look into this issue.
With the substitution and imagecodecs, now the .tiff export works with a specified compression. However now it seems that the array is not exported correct. I tried it with
where |
Hi @Phlpp-S |
Hi @Milad484 |
This is the code I use check the metadata of the tiff file:
and the output:
The value of the ImageDescription tag in the first page of the TiffFile object is the above OME XML. Reading the image with tifffile: |
Hi @Milad484 |
Hello,
I like this package as it's easy to install and use, however I have a question regarding the compression setting, specifically the compression type.
What to pass here instead of the None to activate a compression?
I saw in the code that it counterchecks with the
tifffile.TIFF.COMPRESSION()
, but was not able to figure out what to pass here.Help would be appreciated
The text was updated successfully, but these errors were encountered: