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/27 02:19] Jim Lovell |
operations:documentation_ops2_austral15day [2013/11/27 23:57] Jim Lovell [Schedule Changeover] |
||
---|---|---|---|
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 53: | Line 54: | ||
* [[operations:startmessage|Send a start message to IVS]]. | * [[operations:startmessage|Send a start message to IVS]]. | ||
* Send off the log files to IVS. Refer to the page [[operations:documentation.ivs.commentsfile|Prepare the comments file and transfer the logs]] for details. Note that all modules for AUSTRAL experiments from Yarragadee and Katherine are shipped to Hobart, and all AUSTRAL data are eTransfer-ed to Curtin for correlation. | * Send off the log files to IVS. Refer to the page [[operations:documentation.ivs.commentsfile|Prepare the comments file and transfer the logs]] for details. Note that all modules for AUSTRAL experiments from Yarragadee and Katherine are shipped to Hobart, and all AUSTRAL data are eTransfer-ed to Curtin for correlation. | ||
+ | |||
+ | ===== Module Swaps ===== | ||
+ | |||
+ | |||
===== Observatory Checking ===== | ===== Observatory Checking ===== | ||
Line 115: | Line 120: | ||
- 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> |