Task #7954 (closed)
Fix Image<->MicrobeamManipulation
| Reported by: | ajpatterson | Owned by: | ajpatterson |
|---|---|---|---|
| Priority: | blocker | Milestone: | OMERO-4.4 |
| Component: | Specification | Version: | n.a. |
| Keywords: | dbmodelcompare, schema | Cc: | jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | 2012-05-08 (14) |
Description (last modified by ajpatterson)
In the Model an Image can have direct links to 0 or more MicrobeamManipulations. I do not see this linkage in the DB. It looks like you have to go through experiment.
Email the list and try and find some real use cases.
Change History (21)
comment:1 Changed 12 years ago by ajpatterson
comment:2 Changed 12 years ago by jburel
- Sprint changed from 2012-02-14 (8) to 2012-02-28 (9)
Moved from sprint 2012-02-14 (8)
comment:3 Changed 12 years ago by ajpatterson
- Description modified (diff)
- Summary changed from Resolve Image MicrobeamManipulation to Email list about Image<->MicrobeamManipulation
comment:4 Changed 12 years ago by jburel
- Sprint changed from 2012-02-28 (9) to 2012-03-13 (10)
Moved from sprint 2012-02-28 (9)
comment:5 Changed 12 years ago by jburel
- Sprint changed from 2012-03-13 (10) to 2012-03-27 (11)
Moved from sprint 2012-03-13 (10)
comment:6 Changed 12 years ago by ajpatterson
- Status changed from new to accepted
comment:7 Changed 12 years ago by rkferguson
- Owner ajpatterson deleted
- Status changed from accepted to new
comment:8 Changed 12 years ago by rkferguson
- Owner set to ajpatterson
- Status changed from new to accepted
comment:9 Changed 12 years ago by rkferguson
- Owner ajpatterson deleted
- Status changed from accepted to new
comment:10 Changed 12 years ago by rkferguson
- Owner set to ajpatterson
- Remaining Time set to 0.2
comment:11 Changed 12 years ago by rkferguson
- Status changed from new to accepted
comment:12 Changed 12 years ago by jburel
- Cc jburel added
- Sprint changed from 2012-03-27 (11) to 2012-04-10 (12)
Andrew is off, moving to next sprint
comment:13 Changed 12 years ago by ajpatterson
Mail sent.
comment:14 Changed 12 years ago by ajpatterson
- Owner ajpatterson deleted
- Status changed from accepted to new
comment:15 Changed 12 years ago by ajpatterson
- Owner set to ajpatterson
- Remaining Time changed from 0.2 to 0.1
comment:16 Changed 12 years ago by jburel
- Sprint changed from 2012-04-10 (12) to 2012-04-24 (13)
Moved from sprint 2012-04-10 (12)
comment:17 Changed 12 years ago by jburel
- Sprint changed from 2012-04-24 (13) to 2012-05-08 (14)
- Summary changed from Email list about Image<->MicrobeamManipulation to Fix Image<->MicrobeamManipulation
Curtis: 02/04/2012
Hi Andrew,
We are in the process of trying to resolve some outstanding differences between the OME Schema and the way this is represented in the OMERO Database.
One of the differences is how MicrobeamManipulations are linked to Images.
We are looking for some real use cases. Can anyone who is working with MicrobeamManipulation, either in code against OMERO or by writing OME-XML or OME-TIFF files please get in touch.
When we first added MicrobeamManipulation to the schema, LOCI had some use cases for it: ablation and photobleaching. At the time we had recently added a second laser to our main optical workstation, which provided an ablation capability. So our main requirement was that we could record all such ablation events in OME-XML, with a timestamp of when the event occurred, as well as the center point of the event. These events would accrue over time during acquisition based on manual user activation, and ultimately get written out to the final OME-XML block at the end of the run.
Unfortunately, my understanding is that due to a technical issue, we had to remove the ablation laser from our system, and it is not currently available, so WiscScan does not yet support recording of MicrobeamManipulation events into the metadata.
That said, we do hope to provide such capabilities again in the future, so continued support of MicrobeamManipulation elements is appreciated.
Regards,
Curtis
comment:18 Changed 12 years ago by jburel
- Priority changed from minor to blocker
comment:19 Changed 12 years ago by ajpatterson
Decision: Add the missing link table between Image and MicrobeamManipulation to the Database. Without this you cannot tell which manipulations happen to each Image if you have multiple Images and multiple MicrobeamManipulation associated with the same Experiment.
comment:20 Changed 12 years ago by jburel
- Remaining Time changed from 0.1 to 0
- Resolution set to fixed
- Status changed from new to closed
comment:21 Changed 12 years ago by jburel
Added to #8084.
this needs resolved but we have no real data as far as we know to provide use cases - asks lists for data - but probably not 4.4