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 (closed)

Opened 8 years ago

Closed 8 years ago

BUG: min/max calculation BIG jp2

Reported by: wmoore Owned by: jburel
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: 0.0d
Sprint: 2011-06-16 (14)

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.

Attachments (2)

Picture 50.png (386.3 KB) - added by wmoore 8 years ago.
Initial rendering settings of jp2 image
Picture 58.png (208.4 KB) - added by wmoore 8 years ago.
PC3 Plate 1 INCELL 1000

Download all attachments as: .zip

Change History (14)

Changed 8 years ago by wmoore

Initial rendering settings of jp2 image

comment:1 Changed 8 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.

comment:2 Changed 8 years ago by cblackburn

The min/max values look to be okay. The default rendering setting on two channels are wrong.

A similar file: data_repo/from_skyking/nikon-jp2/kira/DapiFitcTexRed008.jp2 has the correct rendering settings when imported.

comment:3 Changed 8 years ago by jburel

  • Sprint changed from 2011-06-02 (13) to 2011-06-16 (14)

Moved from sprint 2011-06-02 (13)

comment:4 Changed 8 years ago by cblackburn

It looks like for two channels the lower value is calculated okay but the upper value is out by a factor of 10 or so.

Changed 8 years ago by wmoore

PC3 Plate 1 INCELL 1000

comment:5 Changed 8 years ago by wmoore

Just imported this plate onto the windows server - all are 'BIG' images and rendering settings are initially saturated.

comment:6 Changed 8 years ago by cblackburn

  • Cc jburel added

comment:7 Changed 8 years ago by jburel

Forgot to bring that point today.
We may want to turn off the "best guess" and use the min/max.

comment:8 Changed 8 years ago by wmoore

You mean just for Big images? But strange that this is working for most images, and that 'reset' returns it to the saturated settings.

comment:9 Changed 8 years ago by jburel

didn't get that. I will have a look

comment:10 Changed 8 years ago by jburel

  • Owner changed from cblackburn to jburel

comment:11 Changed 8 years ago by jburel

  • Remaining Time set to 0.3
  • Status changed from new to accepted

comment:12 Changed 8 years ago by jburel <j.burel@…>

  • Remaining Time changed from 0.3 to 0
  • Resolution set to fixed
  • Status changed from accepted to closed

(In [1dc9b50d6944bc63a222b57f5af08a8c5a0535bd/ome.git] on branch develop) Fix min/max calculation, values not correctly set when dealing with tiles (close #5555)

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

We're Hiring!