Context Navigation

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 Version 4 and Version 5 of Ticket #4903, comment 1

Timestamp:: 04/21/11 05:56:53 (13 years ago)
Author:: dzmacdonald
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #4903, comment 1

-                      v4
+                      v5
    * Writing of Unstaging script to transform the csv file data from the script to OMERO and attaching to the correct OMERO data objects(image, dataset).
   * The rewriting of the script to use local file copies, reverting the script to its original format.
- == Meeting on RAPID in OMERO 20/4 ==
-Present: Jos Koetsier, Donald !MacDonald
- == Managing OMERO Agnostic Scripts ==
-The level of agnosticism an be:
- * Cluster and script are both OMERO agnostic.
- * The Cluster is OMERO aware, the script is OMERO agnostic.
- * The Cluster and script are OMERO aware.
-Depending on the level that is available, affects what possible solutions we can present for staging and unstaging data.
- === Cluster and script are both OMERO agnostic ===
-This means that the prestaging and post staging elements of job submission must convert the data in OMERO to a format required by the script. This presents several difficulties: There needs to be methods available for scripts to use to convert the data in OMERO to the correct format, these transformations have to occur in the OMERO server.
- === Cluster is OMERO Aware and script is OMERO agnostic ===
-This means that the prestaging and post staging elements of job submission could install some scripts on the cluster to download and convert the data to a format required by the script. This could also be performed by an OMERO.fs install on the cluster.
- === Cluster and script are OMERO aware ===
-This is the simplest of methods and the script deployed to the cluster is able to access the data on the OMERO server.