User Tools

Site Tools


operations:documentation.logmonitor_eremotectrl

This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
operations:documentation.logmonitor_eremotectrl [2014/06/17 03:46]
Jim Lovell [Starting the log monitor]
operations:documentation.logmonitor_eremotectrl [2016/05/19 03:57]
Tiege McCarthy [Starting the log monitor]
Line 24: Line 24:
     - The log monitor won't start checking the time difference until the first //new// log entry is received     - The log monitor won't start checking the time difference until the first //new// log entry is received
     - Once a setup is complete there may be several hours before the next log entry at the experiment start. In this case, a series of incessant beeps after 15 minutes could get annoying. Pressing the "Reset watchdog"​ button will reset the log line counter to zero, meaning that the time difference will not be checked again until there'​s a new entry.     - Once a setup is complete there may be several hours before the next log entry at the experiment start. In this case, a series of incessant beeps after 15 minutes could get annoying. Pressing the "Reset watchdog"​ button will reset the log line counter to zero, meaning that the time difference will not be checked again until there'​s a new entry.
 +
 +To set the optimal timeout values in the log monitor open a terminal on ops2 and type ./​watchdog_check.sh <​experiment name>, this will return a value to input into the log monitor for each telescope involved in the experiment. ​
 +For example:
 +<​code>​
 +./​watchdog_check.sh r4734
 +</​code>​
 +Will return:
 +<​code>​
 +hb12: Set watchdog timeout to 12 minutes
 +ke12: Set watchdog timeout to 16 minutes
 +yg12: Set watchdog timeout to 19 minutes
 +</​code>​
  
 Note the log monitor script can also be started on ops6 (the PC in the "​Lounge"​). Just open a terminal window and repeat steps 5 and 6 above. Both ops2 and ops6 share the /vlbobs directory, so log recording needs to be started only from one place. Note the log monitor script can also be started on ops6 (the PC in the "​Lounge"​). Just open a terminal window and repeat steps 5 and 6 above. Both ops2 and ops6 share the /vlbobs directory, so log recording needs to be started only from one place.
/home/www/auscope/opswiki/data/pages/operations/documentation.logmonitor_eremotectrl.txt · Last modified: 2016/12/20 04:05 by Jim Lovell