Task #4107 (new)
Opened 15 years ago
Last modified 8 years ago
More robust support for 1, 2 and 4 bit images — at Initial Version
| Reported by: | mlinkert | Owned by: | mlinkert |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Bio-Formats | Version: | n.a. |
| Keywords: | n.a. | Cc: | FCORNELI@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
1, 2 and 4 bit images are currently supported, but not in the most flexible way. Instead of storing these images in their original bit depth, we automatically convert them to 8 bit data and throw away the original bit depth. We should do the following:
- use the type BufferedImage?.TYPE_BYTE_BINARY when constructing BufferedImages?
- add a new flag to the API to toggle how openBytes handles < 8 bit data - developers can choose whether to get original data (e.g. 1 byte represents 8 pixels), or expanded data (i.e. 1 byte represents 1 pixel)
- potentially add new pixel types to the OME data model (uint1, uint2, uint4, etc.)
- update the TIFF writer to export 1, 2 and 4 bit data
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
