Changes between Version 3 and Version 4 of FeddMultiSwapExample


Ignore:
Timestamp:
Sep 21, 2011 2:18:53 PM (8 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddMultiSwapExample

    v3 v4  
    7575The next three lines configure the SEER experiment control system.  The '''local_seer''' service will add a node named '''control''' to each experiment that is effictively invisible outside the party's area.  Computers will treat that as a SEER controller, and experimenters can connect to it directly to see and manipulate their areas.  The '''seer_master''' service adds a node named seer-master to the experiment that each area's controller will also connect to.  Connecting to the seer-master controller allows thw whole experiment to be viewed and manipulated.
    7676
     77== Creating the Experiment ==
     78
     79To create the experiment:
     80
     81{{{
     82fedd_create.py --file multi-swap-example.tcl --experiment_name=faber-multi
     83}}}
     84
     85You can provide any identifier you like for the experiment name.
     86
     87This will return pretty shortly (though not instantly) with output like this:
     88
     89
     90{{{
     91localname: faber-multi
     92fedid: b4339d8a339097e87ed5624a36b584fe95b0ea0d
     93status: starting
     94}}}
     95
     96The [FeddAbout#GlobalIdentifiers:Fedids fedid] is the unique name for the experiment, and the localname is a human-readable nickname.  It is derived from the suggested experiment name passes to fedd_create.py.  Generally the name passed is the one used, but if there is a name collision, fedd disambiguates.  Finally the status is given.  "Starting" means that fedd is constructing the experiment.  This is generally a process that takes 10 minutes or so, though troubles with individual nodes can make it take longer.Fedd simultaneously swaps a separate experiment in for each sub experiment.
     97
     98You can check on the progress of the experiment using [FeddCommands#fedd_multistatus.py fedd_multistatus.py] which prints a brief status for each federated experiment:
     99
     100{{{
     101$ fedd_multistatus.py
     102faber-multi:b4339d8a339097e87ed5624a36b584fe95b0ea0d:starting
     103}}}
     104
     105When the experiment is active:
     106
     107{{{
     108localname: faber-multi
     109fedid: b4339d8a339097e87ed5624a36b584fe95b0ea0d
     110status: active
     111}}}
     112
     113Experiments can also be "failed" which means it will not come up, and a couple other states.
     114
     115Because creation takes a while, users want to see what's going on, even if it is somewhat cryptic.  There are several ways to do this.  The [FeddCommands#fedd_spewlog.py fedd_spewlog.py] command prints the fedd swapin log to stdout and terminates when the experiment fails or activates.  For example:
     116
     117{{{
     118$ fedd_spewlog.py --experiment_name faber-multi
     11921 Sep 11 13:57:10 fedd.experiment_control.faber-multi Calling StartSegment at https://users.isi.deterlab.net:23233
     12021 Sep 11 13:57:10 fedd.experiment_control.faber-multi Calling StartSegment at https://users.isi.deterlab.net:23231
     12121 Sep 11 13:57:10 fedd.experiment_control.faber-multi Calling StartSegment at https://users.isi.deterlab.net:23231
     12221 Sep 11 13:57:10 fedd.experiment_control.faber-multi Calling StartSegment at https://users.isi.deterlab.net:23233
     123Allocated vlan: 3808Allocated vlan: 380921 Sep 11 13:58:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 1 mins)
     12421 Sep 11 13:59:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 2 mins)
     12521 Sep 11 14:00:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 3 mins)
     12621 Sep 11 14:01:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 4 mins)
     12721 Sep 11 14:02:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 5 mins)
     12821 Sep 11 13:57:17 fedd.access.faber-multi-a State is swapped
     12921 Sep 11 13:57:17 fedd.access.faber-multi-a [cmd_with_timeout]: /bin/rm -rf /proj/TIED/exp/faber-multi-a/tmp
     13021 Sep 11 13:57:17 fedd.access.faber-multi-a [cmd_with_timeout]: /bin/rm -rf /proj/TIED/software/faber-multi-a/*
     13121 Sep 11 13:57:17 fedd.access.faber-multi-a [cmd_with_timeout]: mkdir -p /proj/TIED/exp/faber-multi-a/tmp
     13221 Sep 11 13:57:17 fedd.access.faber-multi-a [cmd_with_timeout]: mkdir -p /proj/TIED/software/faber-multi-a
     13321 Sep 11 13:57:18 fedd.access.faber-multi-a [modify_exp]: Modifying faber-multi-a
     13421 Sep 11 13:57:34 fedd.access.faber-multi-a [modify_exp]: Modify succeeded
     13521 Sep 11 13:57:34 fedd.access.faber-multi-a [swap_exp]: Swapping faber-multi-a in
     13621 Sep 11 14:02:43 fedd.access.faber-multi-a [swap_exp]: Swap succeeded
     13721 Sep 11 14:02:43 fedd.access.faber-multi-a [get_mapping] Generating mapping
     13821 Sep 11 14:02:43 fedd.access.faber-multi-a Mapping complete21 Sep 11 14:03:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 6 mins)
     13921 Sep 11 14:04:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 7 mins)
     14021 Sep 11 14:05:10 fedd.experiment_control.faber-multi Waiting for sub threads (it has been 8 mins)
     141}}}