User Story #6250 (new)
Opened 13 years ago
Last modified 10 years ago
Tiling support — at Version 1
Reported by: | wmoore | Owned by: | wmoore |
---|---|---|---|
Priority: | major | Milestone: | OMERO-Beta4.3.2 |
Component: | Specification | Keywords: | n.a. |
Cc: | cxallan, ajpatterson, mlinkert, ngdias@… | Story Points: | n.a. |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | 2.0d | Estimated Remaining Time: | n.a. |
Description (last modified by wmoore)
Both the data model and OMERO functionality could do a better job of supporting Tiling.
E.g.
http://www.openmicroscopy.org/community/viewtopic.php?f=15&t=722
http://www.openmicroscopy.org.uk/community/viewtopic.php?f=4&t=749&p=2723
Workflows to support:
- Import a bunch of single plane tiffs or colored jpegs etc each with an X and Y position, either defined in pixels or stage units or microns.
- Need to be able to stitch them together into a Big image, handling overlap and gaps.
Some questions to resolve:
- Can we use <Image><StageLabel X=100.2 Y=256.5> or <Plane PositionX=100.2 PositionY=256.5> for tiling if we don't know the units? These are unitless ("microscope reference frame")
- How do we distinguish from X and Y stored as pixels or stage units or microns or row & column?
- Do we use StageLabel? or Plane for a bunch of single plane images BEFORE stitching them together? Does it matter? I guess we usually have more than one plane at each Stage position (E.g. rgba from slide scanner).
- Stitching algorithm should probably check Plane for PositionX etc and if not found, then use StageLabel?
- Does the "Big Images API" support setting an arbitrary region?
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.