User Tools
operations:starting_monitoring
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.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
operations:starting_monitoring [2011/07/27 01:45] Jim Lovell [Recovering from power failures] |
operations:starting_monitoring [2012/07/25 23:34] (current) Jamie McCallum |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| Applications -> AuScope [Hobart|Katherine|Yarragadee] -> econtrol | Applications -> AuScope [Hobart|Katherine|Yarragadee] -> econtrol | ||
| - | Click on the boxes next to “StatusMonitor" and "Logging and Operator Input”. This should trigger the program to connect to pcfshb and you’ll see a status window and log window. If you don't see any information updating in the status window, type [ctrl]-[shift]-e to start the server process on the field system. You can send PCFS commands and comments from the bottom of the log window. Note you won’t see the log window update until the next scheduled command is sent. | + | Click on the boxes next to “StatusMonitor" and "Logging and Operator Input”. This should trigger the program to connect to pcfs[hb|ke|yg] and you’ll see a status window and log window. If you don't see any information updating in the status window, type [ctrl]-[shift]-e to start the server process on the field system. You can send PCFS commands and comments from the bottom of the log window. Note you won’t see the log window update until the next scheduled command is sent. |
| Set up the log monitor to provide warnings and alarms: | Set up the log monitor to provide warnings and alarms: | ||
| Line 13: | Line 13: | ||
| (As a backup, pmSTALM can be used but it checks for fewer error conditions. This is described [[operations:documentation.pmstalm| here]].) | (As a backup, pmSTALM can be used but it checks for fewer error conditions. This is described [[operations:documentation.pmstalm| here]].) | ||
| - | At least 5 min prior to to the scheduled start, start the schedule with e.g. <code>schedule=r4447hb</code> as usual. Note: do NOT specify a start line number. [[operations:startmessage|Then send a start message to IVS]]. | + | For Hobart and Katherine, start the schedule with e.g. <code>schedule=r4447hb</code> if there is longer than 5 minutes until the nominal start of the schedule. For Yarragadee, ALWAYS start the schedule with <code>schedule=r4447yg,#1</code>. This is necessary because the snp file has been edited to deal with the transmission stows which confuses the fs. |
| + | |||
| + | Unless: you try to start late within five minutes of the scheduled start and get errors like; //m5 -900 no scans//;// m5 -900 not while recording or playing//;// m5 -900 can't get device info//. The mk5 is looking for the previous scheduled scan to check, which doesn't exist, and can't start the next scheduled scan recording. In this case start schedule with start line number <code>schedule=r4447hb,#1</code> Otherwise: do NOT specify a start line number. | ||
| + | |||
| + | [[operations:startmessage|Then send a start message to IVS]]. | ||
| During the experiment, the following checks can be made. Please log them using the new Checklist GUI: | During the experiment, the following checks can be made. Please log them using the new Checklist GUI: | ||
| Line 20: | Line 24: | ||
| Please go through the checklist as often as you like but **at least once every 2 hours**. A description of the checklist parameters and what to look out for is available here: | Please go through the checklist as often as you like but **at least once every 2 hours**. A description of the checklist parameters and what to look out for is available here: | ||
| * [[operations:checklist_parameters|Description of checklist parameters]] | * [[operations:checklist_parameters|Description of checklist parameters]] | ||
| + | The **system monitor** provides a useful summary of the drives & other Monica parameters. You can run it on ops4 or ops5 with the command ''monitor_system.pl'' or from the drop-down menu on the desktop "Applications -> AuScope -> Monitor System". Run it once for each site. | ||
| + | |||
| + | You can launch clock displays too from the "Applications -> AuScope" menu. | ||
| + | |||
| + | It's best to only have the Katherine and Yarragadee VNC sessions running when running through the checklist and to rely on econtrol, the system monitor and the log monitor the rest of the time. You should use the VNC sessions to check that the autocorrelation spectra are OK though. | ||
| + | |||
| + | [[http://auscope.phys.utas.edu.au/webcams_etc.html|This web page]] provides a one-page summary of the webcams and weather radar. | ||
| - | It's best to only have the Katherine and Yarragadee VNC sessions running when running through the checklist and to rely on econtrol and the log monitor the rest of the time. You should use the VNC sessions to check that the autocorrelation spectra are ok though. | + | The PC in the "lounge" (ops6) runs the same PCFS log monitor that ops4 does. To start it, double-click on the "Log monitor" icon on the desktop and then open the same log file that econtrol is writing to. Run it once for each station. |
| ===== Other things to watch out for ===== | ===== Other things to watch out for ===== | ||
| Line 113: | Line 124: | ||
| Lastly, please make a note in the log that Tsys measurements have been disabled. | Lastly, please make a note in the log that Tsys measurements have been disabled. | ||
| - | It is possible to remotely reset the power sensor at both Yarragadee and Hobart. You should first follow the procedure outlined above, then kill any remaining ''systemp12rcp.sh'' or ''ReadPower.sh'' processes running on pcfs[hb|ke|yg] (use ''ps -ef | grep ReadPower'' to identify the process IDs). Become root with ''su'' and issue the command | + | It is possible to remotely reset the power sensor at all three telescopes. You should first follow the procedure outlined above, then kill any remaining ''systemp12rcp.sh'' or ''ReadPower.sh'' processes running on pcfs[hb|ke|yg] (use ''ps -ef | grep ReadPower'' to identify the process IDs). Become root with ''su'' and issue the command |
| <code> | <code> | ||
| /etc/init.d/AgilentU2000 restart | /etc/init.d/AgilentU2000 restart | ||
| Line 124: | Line 135: | ||
| When you restart econtrol from the menu it may be unable to load the telescope information (the drop-down menu boxes), and the terminal from which econtrol runs produces "Can't open interface" type errors. If this happens, in the econtrol window (the green one, not the terminal) press ''Control+shift+e'', and then try to open one of the drop down boxes again - this time the icon in the bottom right corner should go from red through 'connecting' to green, the information will now load, and observing can continue as normal. | When you restart econtrol from the menu it may be unable to load the telescope information (the drop-down menu boxes), and the terminal from which econtrol runs produces "Can't open interface" type errors. If this happens, in the econtrol window (the green one, not the terminal) press ''Control+shift+e'', and then try to open one of the drop down boxes again - this time the icon in the bottom right corner should go from red through 'connecting' to green, the information will now load, and observing can continue as normal. | ||
| + | |||
| + | When econtrol is back, check that there is a green bar above the red dot, second icon to the right of the text entry field. This indicates that a log file is being recorded. If there is not a green bar on this button, press the button and specify an appropriate filename in ''/vlbobs/ivs/logs''. Then in the Log Monitor, choose File > Open Log File and select the new file. Make a note that there are two log files. | ||
| + | ==== If econtrol can't connect ==== | ||
| + | |||
| + | Recording continues as econtrol is a front-end viewer for the field system, so don't panic :) | ||
| + | |||
| + | If the econtrol program can't connect even after repeated ''Ctrl+Shift+e'' commands, you should check to make sure that the econtrol daemon is running on the pcfs machine. Log in to pcfshb and run ''ps -ef | grep econtrold''. There should be two entries in the list. If it's not running then start it with ''/usr2/econtrol/bin/econtrold''. If it is running at first but you still can't connect, try killing the econtrold processes and restarting it. | ||
/home/www/auscope/opswiki/data/attic/operations/starting_monitoring.1311731137.txt.gz · Last modified: 2011/10/26 06:37 (external edit)
Page Tools
