-
Notifications
You must be signed in to change notification settings - Fork 0
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
Which image file formats to choose? #5
Comments
I think all tools we normally use for teaching run Bio-Formats and can open those readable "standard" formats. Therefore, I think if it is not the strangest format ever, I would keep the original format (also for the sake of not messing up with the metadata. |
I agree with @biovoxxel . |
OK, I wanted to disagree and say we should support community standards, but experiments that I did today appear to have such a FRUSTRATING outcome that I indeed start to wonder whether, e.g., CZI is preferable over OME.TIFF. I am probably overreacting right now, but I spent the last couple of days dealing with various image file format issues and I am sort of loosing the patience a little bit ;-) |
I recently wrote this chapter out of similar frustration. In Python it's much worse compared to Java/ImageJ btw. And I agree with the above comments. Let's keep files in the format they come if possible. |
Yeah, I thought that at least ImageJ and Bio-Formats would play well along together. To learn that they don't is a bit of a shocker I must say.... |
I have a CZI file that I would like to contribute.
Should I convert it? To what?
My personal opinion:
It is useful to also have commercial file formats, but only for teaching how to deal with those file formats.
Data that is of general use should be in a wide spread and easy to deal with community standard file format.
I think currently there the only option is OME.TIFF?!
What do you think? ping @haesleinhuepf @RoccoDAnt @ArneS70 @biovoxxel
The text was updated successfully, but these errors were encountered: