This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
operations:documentation_ops2_austral15day [2013/11/26 22:22] Jim Lovell [Monitoring observations] |
operations:documentation_ops2_austral15day [2013/11/27 23:56] Jim Lovell [AUSTRAL 15-day Observations : Nov 28 to Dec 16 2013] |
||
---|---|---|---|
Line 3: | Line 3: | ||
* [[#schedule_overview_and_module_usage|Observing schedule and module usage overview]] | * [[#schedule_overview_and_module_usage|Observing schedule and module usage overview]] | ||
* [[#schedule_changeover|Schedule changeover procedure]] | * [[#schedule_changeover|Schedule changeover procedure]] | ||
+ | * [[#module_swaps|Swapping Mark5 modules]] | ||
* [[#observatory_checking|Observatory checking procedure]] (every 3 days) | * [[#observatory_checking|Observatory checking procedure]] (every 3 days) | ||
* [[#fringe_checks|Fringe Checks]] | * [[#fringe_checks|Fringe Checks]] | ||
Line 31: | Line 32: | ||
It is also possible to monitor the 15m telescope at Hartebeeshoek and you may be asked to respond to problems when local staff are unavailable. | It is also possible to monitor the 15m telescope at Hartebeeshoek and you may be asked to respond to problems when local staff are unavailable. | ||
* [[operations:documentation.monitor_hart15|Monitoring the Hart 15m telescope]] | * [[operations:documentation.monitor_hart15|Monitoring the Hart 15m telescope]] | ||
+ | |||
+ | It may also be possible to monitor the Warkworth 12m antenna. Details to follow if this becomes possible. | ||
===== Schedule Changeover ===== | ===== Schedule Changeover ===== | ||
Line 45: | Line 48: | ||
mk5=vsn?</code> If it doesn't, then the VSN will need setting: | mk5=vsn?</code> If it doesn't, then the VSN will need setting: | ||
- [[operations:van_setting|Setting a module VSN code]] | - [[operations:van_setting|Setting a module VSN code]] | ||
- | - Now start the new schedule. Include the '',#1'' section so that you start the schedule on the first line, e.g. <code>schedule=a1303hb,#1</code> | + | - Now start the new schedule. Include the '',#1'' suffix so that you start the schedule on the first line, e.g. <code>schedule=a1303hb,#1</code> |
Once the new schedule has started: | Once the new schedule has started: | ||
Line 100: | Line 103: | ||
- Measure the Tsys while at a high elevation <code>systemp12</code> | - Measure the Tsys while at a high elevation <code>systemp12</code> | ||
- [[operations:documentation.test_antenna#antenna_pointing_check|Check the pointing]] | - [[operations:documentation.test_antenna#antenna_pointing_check|Check the pointing]] | ||
- | - There are a series of Az/El slews to move the antenna over it's full range. Type each of these commands into eRemoteCtrl in the order they appear. <note important>Wait for eRemoteCtrl to report ''flagr/antenna,acquired'' before continuing to the next</note>: <code> | + | - There are a series of Az/El slews to move the antenna over it's full range. Type each of these commands into eRemoteCtrl in the order they appear. //Wait for eRemoteCtrl to report ''flagr/antenna,acquired'' before continuing to the next//: <code> |
test1 | test1 | ||
test2 | test2 | ||
Line 113: | Line 116: | ||
- 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</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 you can re-start the schedule. Just use the schedule name without any line number suffix. e.g. <code>schedule=a1308hb |
+ | 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. | ||
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> | ||
- | ===== Starting ===== | ||
- | The usual startup procedure can now be done: [[operations:starting_monitoring_9.10.5|Starting and Monitoring]] | ||
===== Fringe Checks ===== | ===== Fringe Checks ===== | ||
On 1921-293 every day. Procedure? | On 1921-293 every day. Procedure? |