User Tools

Site Tools


operations:documentation.logmonitor_eremotectrl

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
operations:documentation.logmonitor_eremotectrl [2016/05/19 03:56]
Tiege McCarthy [Starting the log monitor]
operations:documentation.logmonitor_eremotectrl [2016/12/20 04:05]
Jim Lovell
Line 8: Line 8:
   - The red dot icon in econtrol should now show a green bar in the top left to indicate that the log is being recorded:\\ {{:​operations:​econtrol_log_recording.png|}}   - The red dot icon in econtrol should now show a green bar in the top left to indicate that the log is being recorded:\\ {{:​operations:​econtrol_log_recording.png|}}
   - Type a command into the Operator Input section (next to the blue triangle) so that the new log file is created. e.g. <​code>​clkoff</​code>​   - Type a command into the Operator Input section (next to the blue triangle) so that the new log file is created. e.g. <​code>​clkoff</​code>​
-  - Now start the log monitor from the Applications menu on ops2:\\ ''​Applications -> AuScope -> Log monitor''​+  - Now start the log monitor from the Applications menu on ops8:\\ ''​Applications -> AuScope -> Log monitor''​ 
 +    - Or try the [[operations:​documentation.logmonitor_v3|new experimental version]].
   - You will be asked which station is being monitored (type 1, 2 or 3) and then the GUI will start. ​   - You will be asked which station is being monitored (type 1, 2 or 3) and then the GUI will start. ​
   - Select\\ ''​File -> Open Log File''​ \\ and type in the name of the log file you just created (e.g. ''/​vlbobs/​ivs/​logs/​r4456_yg_econtrol.log''​) or click on Browse and find the file.   - Select\\ ''​File -> Open Log File''​ \\ and type in the name of the log file you just created (e.g. ''/​vlbobs/​ivs/​logs/​r4456_yg_econtrol.log''​) or click on Browse and find the file.
Line 25: Line 26:
     - 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.
  
-Too 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. ​+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: For example:
 <​code>​ <​code>​
/home/www/auscope/opswiki/data/pages/operations/documentation.logmonitor_eremotectrl.txt · Last modified: 2016/12/20 04:05 by Jim Lovell