Changes between Version 11 and Version 12 of GeniTmixCalibTutorial


Ignore:
Timestamp:
06/19/14 14:47:46 (5 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixCalibTutorial

    v11 v12  
    1515
    1616== B Login to nodes ==
    17 Open two new terminal windows, one for each node. 
    18 To log into the nodes reserved in the previous step issue the following command for each node in one of the new windows
     17Open two new SSH terminals, one to each node. 
     18On linux you will may use the following command log into each node reserved in the previous step
    1919{{{
    2020ssh -i ~/.ssh/id_geni_ssh_rsa <username>@<hostname> -p <port>
     
    5757Note that the filenames are swapped on the "right" node.  All you should need to change is what is after "data/" and before ".cinit" or ".crecv".  You are now ready to run the tmix experiment. 
    5858
    59 2.  Tmix relies upon a pre-determined start time to synchronize tmix on the two nodes.  On both nodes run the following command to determine the time 2.and date:
     592.  Tmix relies upon a pre-determined start time to synchronize tmix on the two nodes.  On both nodes run the following command to determine the time and date:
    6060{{{
    6161date
    6262}}}
    6363Note that the time may be in a different time zone. 
    64 Decide on a start time about 2-3 minutes in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes with 30 seconds to spare before that start time.
     64Decide on a start time about a minute or two in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes and allow tmix to initialize.
    6565
    66 Finally, execute the following command on both nodes:
     663.  Finally, execute the following command on both nodes:
    6767{{{
    68 tmix -s HH:MM:SS tmix.conf &
     68tmix -s HH:MM:SS tmix.conf
    6969}}}
    7070where HH:MM:SS is the chosen start time in hours minutes and seconds. 
    7171
    72 Tmix on both hosts will load the data files and then wait until the designated start time. 
    73 You will see "Running for ???? seconds" once tmix is ready to go. 
     724.  Tmix on both hosts will load the data files and then wait until the designated start time. 
     73You will see "Running for ???? seconds" once tmix is ready to go.  When the start time hits, Tmix will start running for 12 minutes (a 10 minute experiment plus 2 minutes of buffer).  Once The experiment has completed you will see output indicating the the log files have been output.  While tmix runs it is customary to experience a few errors, where connections fail to open or close.  It is also customary to see several errors at the end of the experiment indicating that some connections failed to close.  If, however, you see a steady stream of errors, something is wrong.  Type "Ctrl-c", and verify your tmix.conf file, and ensure you followed the directions above. 
    7474
    75 To verify when tmix has started run
     755.  One way to verify that tmix is running is to open another SSH terminal to either node and type:
    7676{{{
    7777top
    7878}}}
    79 You should see tmix at the top of the list once it starts.  To exit top type 'q'.
     79This shows a listing of the most active processes.  You should see tmix at the top of the list once it starts.  Top can also give you an indication of what percentage of the CPU tmix is using.  If you see numbers near 80 or 90% you are near the cap.    To exit top type 'q'.
    8080
    8181After about 12 minutes, the experiment will complete, and a list of statistics will be output to the console.  Also a set of log files with extentions .ert, .trt, .unc, .rt, and .ts will be created in the directory.