-
Notifications
You must be signed in to change notification settings - Fork 11
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
Data always saved as int16 #10
Comments
Hi, @rharkes |
I ran into the problem when binning multiple pixels together. The value of the sum went over 65535 so I thought to store them as uint32. But I agree this is probably an exception. However, after some analysis has been applied, data is often in float32 format. For example after convolution filters. Also we very often have multi channel data from confocal microscopes with 8 bit pixels per channel. There it is a bit of a waste to store and open them as uint16 I would say. |
I agree that float32 makes sense to add. I am unfortunately quite busy at the moment to add and test this properly. As for |
It would be nice if npy2bdv would also offer the option to store data in a different datatype than int16. Maybe the writer could give a warning if data might have been altered? This is the case for any data not in
[np.uint8 np.int8 np.int16]
.The text was updated successfully, but these errors were encountered: