Version 3 (modified by, 7 years ago) (diff)


GIMI Init Script in Exper Mgmt Envir (EME)

1) Goals

The GIMI init script in EME aims to interactively initialize the experiment environment for each user-running experiment.

2) Tasks for Init Script

  • Get experiment name from user, and derive experiment-id
  • Retrieve project_id from omni or CH
  • Get list of slice_ids from omni or CH, select slice_id for this experiment
  • Get sliver_manifests_rspecs from AMs
  • Parse sliver_manifest_rspec to get slice_node_names (fully qualified)
  • Select default GIMI Portal, or override
  • Setup GSAS (iRODS) structure
    • derive defaults for user_irods_home_directory and
    • target(exper)-directory, or override
    • derive and load proj_exper_step_descriptors
    • load template OMF scripts
    • get user_irods_target(exper)_iticket, assigned to selcted GIMI Portal agent
  • Push sliver_manifest_rspecs and exp_descriptors to iRODS
  • Holding user_credentials, config GIMI Portal exper info:
    • user_identity
    • experiment_id,
    • project_id, and slice_id
    • slice_node_names
    • sliver_manifest_rspecs
    • user_irods_home_directory
    • user_irods_target(exper)_directory
    • user_irods_target(exper)_iticket

3) GIMI Init installation

This session describes the installation procedure The script can be obtained from github:

4) How to run

This session describes the running and consequences of gimi_init

5) Experiment descriptor and iRODS

To be added by Keleigh.

No image "iRODSMainDirectory.png" attached to EME

No image "iRODSExperimentDirectory.png" attached to EME

No image "iRODSManifestDirectory.png" attached to EME

Attachments (4)

Download all attachments as: .zip