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.

Changes between Initial Version and Version 1 of Ticket #11834, comment 4


Ignore:
Timestamp:
01/06/14 14:58:39 (10 years ago)
Author:
mtbcarroll
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11834, comment 4

    initial v1  
    1 https://github.com/openmicroscopy/openmicroscopy/pull/1933 fixes this for selecting wells. However, what is the expected behavior when one chooses plates or runs? For instance, if I select a plate, do I save only the samples from wells in that plate but not in the runs underneath it (a plate may have both kinds of well), or do I include the well samples from every run under the plate? (I will have to check to what extent these "underneath" things are even already "loaded" into the client if we haven't yet expanded the node.) I also wonder how well the naming of image files in the zip archives copes with having multiple samples in the same well, whether from the same run or different runs in the plate. Basically, I'm concerned that might be too large a can of worms for 4.4.10. 
     1https://github.com/openmicroscopy/openmicroscopy/pull/1933 fixes this for selecting wells. However, what is the expected behavior when one chooses plates or runs? For instance, if I select a plate, do I save only the samples from "orphaned" wells in that plate but not in the runs underneath it (a plate may have both kinds of well), or do I include the well samples from every run under the plate? (I will have to check to what extent these "underneath" things are even already "loaded" into the client if we haven't yet expanded the node.) I also wonder how well the naming of image files in the zip archives copes with having multiple samples in the same well, whether from the same run or different runs in the plate. Basically, I'm concerned that might be too large a can of worms for 4.4.10. 
    22 
    33A separate issue is that the client oddly asks for a local save location, but then just attaches the zip server-side instead; perhaps there is already a ticket to either actually do a download or eliminate the file dialog. 

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.27609 sec.)

We're Hiring!