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/12/05 05:39] Jim Lovell [Starting and Monitoring IVS sessions] |
operations:starting_monitoring [2012/07/25 23:34] (current) Jamie McCallum |
||
|---|---|---|---|
| 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 131: | 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.1323063593.txt.gz · Last modified: 2011/12/05 05:39 by Jim Lovell
Page Tools
