Changes between Version 3 and Version 4 of GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Finish

06/21/13 23:40:13 (9 years ago)



  • GEC17Agenda/GettingStartedWithGENI_III_GIMI/Procedure/Finish

    v3 v4  
     1= Finish =
     2== E. Push to iRODS ==
     5<div style="text-align:left; width:323px; margin-left:auto; margin-right:auto;">
     6<img id="Image-Maps_2201210012154478" src="" usemap="#Image-Maps_2201210012154478" border="0" width="323" height="531" alt="" />
     7<map id="_Image-Maps_2201210012154478" name="Image-Maps_2201210012154478">
     8<area shape="rect" coords="14,16,52,54" href="" alt="" title=""    />
     9<area shape="rect" coords="53,10,152,60" href="" alt="" title=""    />
     10<area shape="rect" coords="53,86,152,136" href="" alt="" title=""    />
     11<area shape="rect" coords="53,162,152,212" href="" alt="" title=""    />
     12<area shape="rect" coords="53,237,152,287" href="" alt="" title=""    />
     13<area shape="rect" coords="52,312,151,362" href="" alt="" title=""    />
     14<area shape="rect" coords="53,387,152,437" href="" alt="" title=""    />
     15<area shape="rect" coords="169,388,268,438" href="" alt="" title=""    />
     16<area shape="rect" coords="53,462,152,512" href="" alt="" title=""    />
     17<area shape="rect" coords="12,91,55,128" href="" alt="" title=""    />
     18<area shape="rect" coords="11,167,54,204" href="" alt="" title=""    />
     19<area shape="rect" coords="11,242,54,279" href="" alt="" title=""    />
     20<area shape="rect" coords="9,317,52,354" href="" alt="" title=""    />
     21<area shape="rect" coords="269,393,312,430" href="" alt="" title=""    />
     22<area shape="rect" coords="10,391,53,428" href="" alt="" title=""    />
     23<area shape="rect" coords="11,467,54,504" href="" alt="" title=""    />
     24<area shape="rect" coords="321,529,323,531" href="" alt="Image Map" title="Image Map" />
     26<!-- Image map text links - End - -->
    2 == D.1 !LabWiki ==
    4 Labwiki is a tool which provides a user-friendly interface to visualize your experiment. To know more about !LabWiki please visit [ LabWiki] [[BR]]
    5 Labwiki can be used to Plan, Prepare and Run your Experiment.[[BR]]
     31=== E.1 Overview ===
    7 === D.1.1 Plan ===
    8 Labwiki accounts have already been created for you for this tutorial. To use Labwiki, go to [ GIMI portal] and login with the username and password you have been given.[[BR]]
     33In GIMI, [ iRODS] is used as the repository for measurement data. At the moment our iRODS data system consist of three servers (RENCI, NICTA, and UMass) and a metadata catalog (located at RENCI).
    10 [[Image(Labwiki_1.png)]]
    12 Figure (1)
     37=== E.2 Storing data on iRODS ===
    14 After you have successfully been signed in you will be able to see a screen like the one below. [[BR]]
     39* After successful completion of an experiment the measurement data from the experiment have been stored in iRODS. We will now look into two options on how this data can be handled.
     41=== E.2.1 iRODS command line tools in the user work space ===
     42  * The GENI [ User Workspace] comes already with the iRODS command line tools installed.
     43  * If you have not done so far use [ iinit] to create a file that contains your iRODS password in a scrambled form. This will then be used automatically by the [ icommands] for authentication with the server.
     45$ iinit
     47    You will be prompted for a password. Please enter the one given on the paper handout.
     49  * The iRODS client uses a configuration file (~/.irods/.irodsEnv) that sets certain parameter for the icommands. Here is and example:
     51# iRODS personal configuration file.
     53# This file was automatically created during iRODS installation.
     54#   Created Thu Feb 16 14:06:27 2012
     56# iRODS server host name:
     57irodsHost ''
     58# iRODS server port number:
     59irodsPort 1247
     61# Default storage resource name:
     62irodsDefResource 'iRODSUmass2'
     63# Home directory in iRODS:
     64irodsHome '/geniRenci/home/gimiXX'
     65# Current directory in iRODS:
     66irodsCwd '/geniRenci/home/gimiXX'
     67# Account name:
     68irodsUserName 'gimiXX'
     69# Zone:
     70irodsZone 'geniRenci'
     72  * Retrieve file from your iRODS home directory into user workspace.
     74$ iget <file_name>
     77    Assuming you wanted to retrieve a file called gimitesting.sq3 the command would look as follows:
     79$ iget gimitesting.sq3
     82  * Store data from user workspace into your iRODS home directory.
     84$ iput <file_name>
     87  * Add metadata information to stored file.
     89$ imeta add -d <file_name> <name> <value> <unit>
     91    For example if you wanted to add the slice name of the experiment as metadata for file gimi01-ping_all.sq3, the command would look as follows:
     93$ imeta add -d gimi01-ping_all.sq3 SliceName gimi01
     95    (<unit> is not required.)
     97=== E.2.2 iRODS web interface ===
     98iRODS also provides a nice and easy to use [ web interface], which we will explore in the following.
     99  * Point the browser in your user workspace to the following link:
     100  * Input the following information to sign in:
     103Port: 1247
     104Username: as given on printout
     105Password: as given on printout
     107  * The following screenshot shows an example for the web interface: [[Image(irods_screen.png)]]
     111=== E.3 IRODS and OML ===
     112In GIMI we have enabled an option in OML2.8 that allows the execution of script. We use this functionality to automatically save measurement results in IRODS after a measurement has successfully completed.
     116=== E.4 DISCLAIMER ===
     117The iRODS service we are offering within the scope of GIMI does NOT guarantee 100% reliable data storage (i.e., we do NOT back up the data). If you are performing your own experiments and want to use iRODS you are absolutely welcome but be aware that we do NOT guarantee recovery from data loss.
    17 [[Image(Labwiki_2a.png)]]
    19 Figure (2)
    22 The left column could contain the steps to run the experiment or general information about the experiment.[[BR]]
    26 [[Image(Labwiki_2.png)]]
    28 Figure (3)
    30 === D.1.2 Prepare ===
    31 In the Prepare column, you can select the experiment that you want to execute. In this column you will also be able to edit your experiment script.[[BR]]
    33 [[Image(Labwiki_3.png)]]
    35 Figure (4)
    37 After editing, click on the save icon at the top of the column to save your script. [[BR]]
    38 Next, click and drag the icon at the top left corner over to the right column Execute.[[BR]]
    40 === D.1.3 Execute ===
    42 Here, you can start your experiment and Visualise it. In the name tab, type in the name you wish to give the experiment. There are no particular rules for this.[[BR]]
    44 Under slice name, type in the name of your slice as you have entered in the Flukes tool while setting up your slice. [[BR]]
    45 Then. scroll towards the bottom of this column and under the tab named Graph, type 'true'.This enables the graph view on your execute column.[[BR]]
    46 Once the experiment starts running you will be able to scroll down and view the graph.[[BR]]
    48 [[Image(Labwiki_4.png)]]
    50 Figure(5)
    52 Click on 'Start Experiment' at the bottom of the screen.
    54 [[Image(Labwiki_5.png)]]
    56 Figure(6)
    58 After a couple of seconds, you can see the graph at the bottom of the screen.[[BR]]
    60 [[Image(Labwiki_6.png)]]
    62 Figure (7)
    65 You can click and drag it to the Plan screen just above Figure 12. This will display the graph along with the experiment description. This graph is also dynamic.[[BR]]
    67 [[Image(Labwiki_7.png)]]
    69 Figure (8)
    71 You can click and drag the experiment description to the Prepare column. This allows you to add any comments or details about the experiment results.[[BR]]
    72 Similarly, Experiments 2 and 3 can be run using the same procedure. Experiment 2 does not have a graph.[[BR]]
    74 [[Image(Labwiki_8.png)]]
    76 Figure(9)
    78 Once you have your slice up and running you can visualize any experiment using !LabWiki.