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"

User Story #8531 (closed)

Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

Support for nonstandard bit depths

Reported by: rleigh Owned by: ajpatterson
Priority: major Milestone: 5.0.0-beta1
Component: Specification Keywords: bit depth, schema, xsd-2013-1
Cc: mlinkert, ajpatterson, jamoore, cxallan, jburel Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description

The OME model currently supports bits depths of multiples of 8.
However many systems (both CCD and confocal at the least) support other bit depths such as 12. Ideally, we should be able to support 12 bit images natively, or else we increase the file size by one third on import, which can consume rather significant amounts of disc space. Support for other/arbitrary depths would perhaps also be useful for other formats.

Change History (10)

comment:1 Changed 12 years ago by mlinkert

  • Cc mlinkert-x ajpatterson jmoore cxallan added

See also #4107.

comment:2 Changed 11 years ago by ajpatterson

  • Keywords schema added

comment:3 Changed 11 years ago by ajpatterson

  • Component changed from Model to Specification
  • Owner set to ajpatterson

comment:4 Changed 11 years ago by ajpatterson

This would require a change to the PixelType? enumeration, or its removal and replacing with a variable for the number of bits. Another option is to keep the PixelType? to indicate the size of the value each pixel is stored in but add a "number of significant bits" value. This would not help with the inflated storage issue but could be useful for processing and analysis.

comment:5 Changed 11 years ago by mlinkert

"12 bit" data is almost always stored as 16 bits per pixel with the 4 most significant bits set to 0; true 12 bit data is quite rare in practice. Personally, I think that it would be sufficient to keep PixelType? as-is, and just add a significant bits field (Bio-Formats already has this internally).

comment:6 Changed 11 years ago by jmoore

  • Cc jburel added
  • Milestone changed from Unscheduled to OMERO-5
  • Priority changed from minor to major

If this is something we're basically already doing, then it makes sense to eat our own dogfood and reduce the pain for others. Bumping.

comment:7 Changed 11 years ago by ajpatterson

  • Keywords xsd-2013-1 added

comment:8 Changed 11 years ago by ajpatterson

  • Status changed from new to accepted

comment:9 Changed 11 years ago by ajpatterson

  • Resolution set to fixed
  • Status changed from accepted to closed

comment:10 Changed 11 years ago by Andrew J Patterson <workonly@…>

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.73968 sec.)

We're Hiring!