Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
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 #13077 (new)

Opened 8 years ago

Last modified 7 years ago

Images not linked directly to Instruments

Reported by: mtbcarroll Owned by: jburel
Priority: minor Milestone: Unscheduled
Component: Model Version: OMERO-5.1.3
Keywords: n.a. Cc: jamoore, rleigh, mlinkert, sbesson, dgault
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


Some images do not have an instrument set directly, but nonetheless are associated with an instrument. The Chgrp2 logic copes with this by, if an image is being moved, then also move any instrument linked implicitly to the image via objective settings or via logical channel then detector or light source settings.

I wonder if we could,

  • find out where these model graphs are coming from and decide if they're okay
  • if they're not okay, fix the culprit, and have a SQL upgrade script set instruments for the legacy images in the DB.

Change History (3)

comment:1 Changed 8 years ago by jamoore

Reading this, my assumption is going to be that such an upgrade would be post-5.3.0 and therefore we could put this in a bucket of stuff to follow the growing ROI work. (in which case, we should likely create that bucket). If *not*, then someone should save this from unscheduled-dom.

comment:2 Changed 8 years ago by mtbcarroll

Happy for this to go in 5.x or some new milestone, or to help out in a periodic review of Unscheduled.

comment:3 Changed 7 years ago by mtbcarroll

Related to #12939.

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

We're Hiring!