User Story #3286 (closed)
Opened 13 years ago
Closed 11 years ago
Big: Measurement tool needs
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | cxallan | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Server-side changes needed to support the updated measurement tool for dealing with big images.
Change History (7)
comment:1 Changed 13 years ago by jburel
- Milestone changed from OMERO-Beta4.3 to Unscheduled
comment:2 Changed 13 years ago by jmoore
- Cc cxallan added
Jean-Marie, will this mean that the MT won't work or that it will just try to do everything in a planar fashion? Do we have any tests / scenarios for this? If #4853 is added, then we will probably end up with a good number of user reported exceptions unless there are specific client controls.
comment:3 Changed 13 years ago by jburel
I have turned off the MT for big images already, and I am not planning to turn in on for release.
This story will be considered in the second phase.
comment:4 Changed 13 years ago by jmoore
Sounds good. Which commit/ticket turned it off? Are you using PyramidService.hasPixelsPyramid() to do the detection?
comment:5 Changed 13 years ago by jburel
ticket #5034, commit 90e5745.
To detect if the image is big images, I use the resolution levels in the viewer. I will review some of the code
for the preview when I am done.
comment:6 Changed 13 years ago by jmoore
Moved to #5927 (big images phase 2) under unscheduled.
comment:7 Changed 11 years ago by jburel
- Resolution set to invalid
- Status changed from new to closed
Measurement tool will probably be off for the first round.