Task #2552 (new)
Opened 14 years ago
Last modified 8 years ago
ImageContainer-MultiImage or ???
| Reported by: | jburel | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | GatherReqs |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | wmoore, cxallan, jamoore, dzmacdonald, jrswedlow, ajpatterson |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by wmoore)
Following discussing on N-Dim, it is URGENT to introduce
the concept of ImageContainer. Not sure we need to model it (for now)
Why is it that important?
- Multi-images file e.g. lei. Problems are:
- users does not recognize the file. Known fact, we have lost some potential users b/c of that. We can argue that others use the system even if we don't have that in place.
- Most importantly. When I import an .lei file (3 images). I select one file (.lei), import it (with archived on) and end up with 3 OMERO images. Problem is when I want to download the file back, it is impossible to select only one image. I need to select 3 images (which means I have to remember all components 3 ok but Martin has >20 images), download and then... figure out where the .lei file is (file annotation). Conclusion: The workflow is broken.
- Sparse data. They are in a sense similar to the multi-images file problem for storing, the way we will handle them is different.
- Stitched Images. If I stitch a bunch of images together, the result is a single image, but I may not want to duplicate the pixel data. In that case, the image container simply stores the transformations required to stitch it's images into a single image.
- Other possibilites...
ImageContainer will have a type field indicating if it is a multi-image, sparse etc.
A dataset will then be linked to ImageContainer or Image. One way to possibly make the linkage to dataset cleaner is to have multi-image subclass from image. This would seem to fit with the concept established in Paris of an "ImageTransform. (See "Day 2 Discussions"). Many images are the input to an ImageTrannsform and a single image is the output.
Change History (8)
comment:1 Changed 14 years ago by jmoore
- Description modified (diff)
comment:2 Changed 14 years ago by wmoore
- Description modified (diff)
comment:3 Changed 12 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.4
comment:4 Changed 12 years ago by jburel
as discussed today (J-M, Josh, Chris, Colin FS mini-group), the multi-images issue will be addressed when using the new import approach.
comment:5 Changed 12 years ago by jburel
- Milestone changed from OMERO-Beta4.4 to Future
related to Fs work
comment:6 Changed 8 years ago by jamoore
Referencing ticket #9165 has changed sprint.
comment:7 Changed 8 years ago by jamoore
Referencing ticket #9165 has changed sprint.
comment:8 Changed 8 years ago by jamoore
- Milestone changed from Future to GatherReqs
Adding to #4891, since we at least need to make a decision on this during our breaking changes.