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/28 02:30] Jim Lovell [Module Swaps] |
operations:documentation_ops2_austral15day [2014/11/25 03:36] (current) Jim Lovell [Module Swaps] |
||
|---|---|---|---|
| Line 57: | Line 57: | ||
| ===== Module Swaps ===== | ===== Module Swaps ===== | ||
| - | Module swaps should be coordinated with local staff at the observatories. Someone at the site will phone when they want to change a module. | + | Module swaps should be coordinated with local staff at the observatories. Someone at the site will phone when they want to change a module. Estimated module change times are available here: |
| + | * [[operations:documentation_austral15day_module_swaps|Module swapping timetable]] | ||
| - | It's important that the new module is powered up during a scan gap as this draws significant power and the Mark5 can't record to the other module at the same time (and will probably crash). So, when someone from the observatory calls, consult the observation summary file and find an upcoming period of time of at least one minute between a ''Stop Data'' and a ''Start Data'' to carry out the swap. For example, in the schedule below, the period between Scans ''332-2104'' and ''332-2110'' would be a good choice as there's a gap of almost 4 minutes (from ''21:06:18'' to ''21:10:01''). However, a module change between Scans ''332-2118b'' and ''332-2122'' would not be a good idea as the gap is only 25 seconds (from ''21:22:29'' to ''21:22:54''): | + | It's important that the new module is powered down and up during a scan gap as this draws significant power and the Mark5 can't record to the other module at the same time (and will probably crash). So, when someone from the observatory calls, consult the observation summary file and find an upcoming period of time of at least one minute between a ''Stop Data'' and a ''Start Data'' to carry out the swap. For example, in the schedule below, the period between Scans ''332-2104'' and ''332-2110'' would be a good choice as there's a gap of almost 4 minutes (from ''21:06:18'' to ''21:10:01''). However, a module change between Scans ''332-2118b'' and ''332-2122'' would not be a good idea as the gap is only 25 seconds (from ''21:22:29'' to ''21:22:54''): |
| <code> | <code> | ||
| Line 77: | Line 78: | ||
| === Procedure === | === Procedure === | ||
| - | * Any time before the scan gap, ask the local person to power down the module to be removed (by tuning its key) and take it out for storage. It's safe to do this as powering down a module shouldn't draw significant power and therefore interrupt a recording. | + | * Wait for the scan to finish and observe that the four disk activity lights stop flashing |
| - | * The new module can be inserted, **but don't turn the key yet!** | + | * halt the schedule. This makes sure that no recording can possibly happen during the swap and crash the Mark5: <code>halt</code> |
| - | * Wait for the time of the end of the identified scan, and confirm that recording has stopped by making sure that the 4 disk activity lights on the 'live' module go out. | + | * Ask the local person to turn the key on the used module and swap it with a blank one. |
| - | * Ask the local person to turn the key on the new module | + | * 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. | ||
| + | * Send an email to auscope-operations@list.utas.edu.au so that we know what's happened | ||
| ===== Observatory Checking ===== | ===== Observatory Checking ===== | ||
| Line 143: | 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.1385605838.txt.gz · Last modified: 2013/11/28 02:30 by Jim Lovell
Page Tools
