This shows you the differences between two versions of the page.
operations:documentation.logmonitor [2011/05/11 05:09] Jim Lovell |
operations:documentation.logmonitor [2011/10/26 06:37] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | - First make sure that econtrol is running for the antenna you wish to monitor. | + | |
- | - In econtrol, in the "Logging and Operator Input" section, click on the red dot icon ("record the logfile"). This will open a dialog window where you need to give a name for the log file to be saved. Select the "Browse for other folders" option, then double-click on "File System" about half way down on the left, then under the "Name" column to the right, double-click on ''vlbobs'', then on ''ivs'' log, then on ''logs''. Finally, give the log file a name at the top of the dialog. Suggested syntax is <code><experiment_name>_<station_code>_econtrol.log</code>e.g.: <code>r4456_yg_econtrol.log</code> | + | |
- | - The red dot icon in econtrol should now show a green bar in the top left to indicate that the log is being recorded. | + | |
- | - Open a terminal window on ops4 | + | |
- | - type the following: <code>/usr2/st/bin/pcfs_log_monitor.pl <log_file_name></code>. e.g. if you used the recommended syntax: <code>/usr2/st/bin/pcfs_log_monitor.pl r4456_yg_econtrol.log</code>. | + | |
- | - You will be asked which station is being monitored (type 1, 2 or 3) and then the GUI will start. | + | |
- | - At the moment, this program will | + | |
- | - monitor the difference in delays between maser and GPS and formatter and GPS, and sound an alarm if they differ by more than 1 us | + | |
- | - watch for all other error messages and either beep or sound an alarm depending on severity | + | |
- | - watch for Mark5 sync errors that require fmset to be run. | + |