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 #5555 (new)

Opened 13 years ago

Last modified 13 years ago

BUG: min/max calculation BIG jp2 — at Version 1

Reported by: wmoore Owned by: cblackburn
Priority: major Milestone: OMERO-Beta4.3
Component: Import Version: n.a.
Keywords: n.a. Cc: cxallan, jamoore, mlinkert, jburel
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: 2011-06-02 (13)

Description (last modified by cblackburn)

The imported "BIG" image

data_repo/test_images_good/nikon-jp2/DapiFitcTexRed001.jp2

has initial rendering settings (thumbnail etc) very saturated, probably due to incorrect min/max calculations (see screen-shot).

These same rendering settings are also picked when you "Reset" the rendering settings in Insight.

Change History (2)

Changed 13 years ago by wmoore

Initial rendering settings of jp2 image

comment:1 Changed 13 years ago by cblackburn

  • Cc mlinkert-x added
  • Description modified (diff)

Is this image an "fs-lite" format? If not the problem may not be with the BfPixelBuffer? min/max calculation.

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

© 2000-2014 University of Dundee & Open Microscopy Environment. Creative Commons Attribution 3.0 Unported License
OME source code is available under the GNU General public license or through commercial license from Glencoe Software

We're Hiring!