Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #4107 (new)

Opened 14 years ago

Last modified 8 years ago

More robust support for 1, 2 and 4 bit images

Reported by: mlinkert Owned by:
Priority: major Milestone: Unscheduled
Component: Bio-Formats Version: OMERO-5.2.0
Keywords: model, TiffReader, export Cc: FCORNELI@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by mlinkert)

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

Change History (2)

comment:1 Changed 13 years ago by jmoore

imported from bio-formats:#344

comment:2 Changed 8 years ago by mlinkert

  • Description modified (diff)
  • Keywords model TiffReader export added
  • Owner mlinkert deleted
  • Version set to OMERO-5.2.0

Note that current versions of the OME-XML schema allow for a BIT type (i.e. uint1), so point 2 is partially resolved and point 4 can be done as part of #12599. Whether uint2/uint4 are still relevant for inclusion is probably up for debate.

The second point above is related to the discussion in #12599; if it's useful to have a way to get the packed representation, that might be best done through a ReaderWrapper? implementation.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.62606 sec.)

We're Hiring!