User Tools
operations:documentation_ops2_austral15day
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:documentation_ops2_austral15day [2013/11/29 03:50] Jim Lovell [Module Swaps] |
operations:documentation_ops2_austral15day [2014/11/25 03:36] (current) Jim Lovell [Module Swaps] |
||
|---|---|---|---|
| Line 79: | Line 79: | ||
| * Wait for the scan to finish and observe that the four disk activity lights stop flashing | * Wait for the scan to finish and observe that the four disk activity lights stop flashing | ||
| - | * Ask the local person to turn the key on the used module and swap it with a blank one | + | * halt the schedule. This makes sure that no recording can possibly happen during the swap and crash the Mark5: <code>halt</code> |
| + | * Ask the local person to turn the key on the used module and swap it with a blank one. | ||
| + | * Wait for three green lights above the new module to indicate it is powered up and ready. | ||
| + | * Resume the schedule with the cont command <code>cont</code> | ||
| * Make a note in the log that the modules have been swapped. Include VSN codes in the message. | * Make a note in the log that the modules have been swapped. Include VSN codes in the message. | ||
| - | * Send an email to transfers@postoffice.maths.utas.edu.au so that we know what's happened | + | * Send an email to auscope-operations@list.utas.edu.au so that we know what's happened |
| ===== Observatory Checking ===== | ===== Observatory Checking ===== | ||
| Line 144: | 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> | ||
/home/www/auscope/opswiki/data/attic/operations/documentation_ops2_austral15day.1385697048.txt.gz · Last modified: 2013/11/29 03:50 by Jim Lovell
Page Tools
