This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
operations:starting_monitoring [2012/06/06 09:52] Stas Shabala [If econtrol gets closed during an observation] |
operations:starting_monitoring [2012/06/21 19:16] Warren Hankey [Starting and Monitoring IVS sessions] |
||
---|---|---|---|
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]]. | + | 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. |
+ | |||
+ | 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: |