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:documentation_ops2_austral15day [2013/12/05 03:33] Jim Lovell [Module Swaps] |
operations:documentation_ops2_austral15day [2014/05/11 02:07] David Horsley |
||
---|---|---|---|
Line 146: | Line 146: | ||
- As above but a ".png" extension. e.g. <code>a1308hb_check.png</code> | - As above but a ".png" extension. e.g. <code>a1308hb_check.png</code> | ||
- | Now you can re-start the schedule. Just use the schedule name without any line number suffix. e.g. <code>schedule=a1308hb | + | Now you can re-start the schedule. Just use the schedule name without any line number suffix. e.g. <code>schedule=c1406hb |
- | setupsx</code> This will start the next scan that occurs at least 5 min in the future. Check that the antenna goes to the next source in the schedule that satisfies this criterion. | + | setup8f</code> This will start the next scan that occurs at least 5 min in the future. Check that the antenna goes to the next source in the schedule that satisfies this criterion. |
Now make a note in the log that the schedule has been restarted following system checks. e.g. <code>"Schedule resumed following system checks</code> Also, if there were any problems during the checks or anything else of note, now is a good time to do it. For example, if the weather was too cloudy to verify the pointing: <code>"Pointing check not successful, probably due to bad weather</code> | Now make a note in the log that the schedule has been restarted following system checks. e.g. <code>"Schedule resumed following system checks</code> Also, if there were any problems during the checks or anything else of note, now is a good time to do it. For example, if the weather was too cloudy to verify the pointing: <code>"Pointing check not successful, probably due to bad weather</code> |