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 Next revision Both sides next revision | ||
|
operations:documentation_ops2_austral15day [2013/11/26 02:56] Jim Lovell [Observatory Checking] |
operations:documentation_ops2_austral15day [2013/11/28 02:41] Jim Lovell [Module Swaps] |
||
|---|---|---|---|
| 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 10: | Line 11: | ||
| Please read the [[operations:documentation_austral15day_overview|Overview Page]] for information on the observations, start and stop times etc. The google calendar on the [[operations:schedule|schedules page]] describes experiment and shift times. | Please read the [[operations:documentation_austral15day_overview|Overview Page]] for information on the observations, start and stop times etc. The google calendar on the [[operations:schedule|schedules page]] describes experiment and shift times. | ||
| - | The AUSTRAL schedules are named ''A13nn'' where ''(nn = 01, 02, 03, ... , 15)''. Interleaved with the AUSTRAL sessions are R1614, CRF79 and R4615. There is only a 5 minute gap between AUSTRAL observations, just enough time to change schedule files and modules (if needed). Every three days, an hour is set aside for detailed checks at each site. They are staggered so that only one antenna is out of the array at a time. Check times for AuScope sites are as follows: | + | The AUSTRAL schedules are named ''A13nn'' where ''(nn = 01, 02, 03, ... , 15)''. Interleaved with these are regular IVS sessions R1614, CRF79 and R4615. There is only a 5 minute gap between AUSTRAL observations, just enough time to change schedule files and modules (if needed). Every three days, an hour is set aside for detailed checks at each site. They are staggered so that only one antenna is out of the array at a time. Check times for AuScope sites are as follows: |
| ^ Site ^ Check time (UT) ^ Check time (Hobart) ^ | ^ Site ^ Check time (UT) ^ Check time (Hobart) ^ | ||
| Line 17: | Line 18: | ||
| | Yg | 04.00 - 05.00 | 15.00 - 16.00 | | | Yg | 04.00 - 05.00 | 15.00 - 16.00 | | ||
| - | We are using 16 TB modules at each station. They will hold two days of data each, so module changes will occur at every second schedule change. The schedule files are written such that the same source is observed at the same sidereal time every day, so the actual schedule changes are NOT at the same UT every time. Note also that R1614, CRF79 and R4615 will go on different modules to the AUSTRALs. Please refer to the [[operations:start#auscope_ivs_module_allocation|Module Usage Spreadsheet]] for a list of which modules to use for which experiments. | + | We are using 16 TB modules at each AuScope station. They will hold two days of data each, so module changes will occur at every second schedule change. The schedule files are written such that the same source is observed at the same sidereal time every day, so the actual schedule changes are NOT at the same UT every time. Note also that R1614, CRF79 and R4615 will go on different modules to the AUSTRALs. Please refer to the [[operations:start#auscope_ivs_module_allocation|Module Usage Spreadsheet]] for a list of which modules to use for which experiments. |
| - | + | ||
| - | The sections below describe how operations differ from normal. | + | |
| + | The sections below describe how operations differ from normal. Note that it will be possible to monitor the Hart 15m antenna and possibly Warkworth as well. | ||
| ===== Schedule files ===== | ===== Schedule files ===== | ||
| Line 28: | Line 28: | ||
| Please carry out the regular two-hourly checks as normal during the observations. | Please carry out the regular two-hourly checks as normal during the observations. | ||
| - | * [[operations:documentation.eRemoteControl_checklist_midob|Description of checklist parameters]] | + | * [[operations:documentation.eRemoteControl_checklist_midob|Description of checklist parameters]] for AuScope telescopes |
| + | 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]] | ||
| + | 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 51: | 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 ===== | ||
| + | |||
| + | 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:aust15nov2013_module_change_times|Module swapping schedule]] | ||
| + | |||
| + | 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''): | ||
| + | |||
| + | <code> | ||
| + | Start Stop Record | ||
| + | Scan Line# Source Az El Cable Data Data Dur Gbyte | ||
| + | date = 2013NOV28 DOY = 332 | ||
| + | 332-2101 7 0648-165 254 6 CCW 21:01:11 21:02:05 0:54 .0 XXX | ||
| + | 332-2102b 24 1606+106 50 27 NEUTR 21:02:57 21:04:13 1:16 6.9 * | ||
| + | 332-2104 41 1622-253 89 48 NEUTR 21:04:52 21:06:18 1:26 16.6 * | ||
| + | 332-2110 58 0454-810 188 31 CW 21:10:01 21:11:30 1:29 27.6 * | ||
| + | 332-2111 75 0230-790 184 26 CW 21:11:54 21:18:16 6:22 39.0 * | ||
| + | 332-2118b 92 2052-474 140 13 CW 21:18:58 21:22:29 3:31 87.9 * | ||
| + | 332-2122 109 2300-683 166 18 CW 21:22:54 21:24:35 1:41 114.9 * | ||
| + | 332-2125 126 0727-115 260 6 CW 21:25:51 21:26:21 0:30 127.9 * | ||
| + | </code> | ||
| + | |||
| + | === 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. | ||
| + | * The new module can be inserted, **but don't turn the key yet!** | ||
| + | * 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 new module | ||
| + | * Make a note in the log that the modules have been swapped. Include VSN codes in the message. | ||
| ===== Observatory Checking ===== | ===== Observatory Checking ===== | ||
| Line 84: | Line 116: | ||
| If the response includes the text ''FHG_off'' then the recorder is off. However, if you see ''FHG_on'' then you're still recording, so stop the recorder with <code>disk_record=off</code> | If the response includes the text ''FHG_off'' then the recorder is off. However, if you see ''FHG_on'' then you're still recording, so stop the recorder with <code>disk_record=off</code> | ||
| - | If not running already, [[operations:documentation:start_monica|Start MONICA]] and choose the pre-set ''aunt_check'' profile from the GUI for the antenna. e.g. for hobart <code>Navigator -> hb -> aunt_check</code> This will plot antenna coordinates, tracking errors and motor currents against time. | + | If not running already, [[operations:documentation:start_monica|Start MONICA]] and choose the pre-set ''aust_check'' profile from the GUI for the antenna. e.g. for hobart <code>Navigator -> hb -> aust_check</code> This will plot antenna coordinates, tracking errors and motor currents against time. |
| Now the checks can begin: | Now the checks can begin: | ||
| - Send the antenna to (Az, El) = (1, 87) deg <code>test1</code> | - Send the antenna to (Az, El) = (1, 87) deg <code>test1</code> | ||
| - | - Wait for it to get there (look for ''flagr/antenna,acquired'' or watch the system monitor display) | + | - Wait for it to get there (look for ''flagr/antenna,acquired'' or watch the system monitor display). While you're waiting, Check the generator status: |
| + | - At Hobart and Katherine you can check the status of the backup generator via the System Monitor interface. The default mode is "In Auto, off" which means it's ready to turn on if there's a power failure but it's currently switched off. If it's in any other state, query it with the On Call person. | ||
| - Check that the RF and IF signal paths are correct and the attenuators are at their nominal levels. Refer to the notes on [[operations:rf_if_check_9.10.5|configuring the RF and IF signal paths]] | - Check that the RF and IF signal paths are correct and the attenuators are at their nominal levels. Refer to the notes on [[operations:rf_if_check_9.10.5|configuring the RF and IF signal paths]] | ||
| - Check the DBBC is properly configured: <code>iread</code> You will see what the current Conditioning module settings are. Output format is: <code><time>/<Module label>/<IF input number>,<Auto or Manual gain control>,<Nyquist filter number>,<Target power level>,<attenuation>,<actual power level></code> Check there’s agreement with what appears in the ''ifdsx'' definition in the procedure file. The actual power level should agree pretty well with the target level. The attenuation number can be anywhere between 0 (none) and 63 (maximum). If you see it at 0 or 63, it means the Conditioning module is having trouble getting the power to the right level. You may want to adjust the attenuators (see [[operations:rf_if_check_9.10.5|configuring the RF and IF signal paths]]) to get them back in range. | - Check the DBBC is properly configured: <code>iread</code> You will see what the current Conditioning module settings are. Output format is: <code><time>/<Module label>/<IF input number>,<Auto or Manual gain control>,<Nyquist filter number>,<Target power level>,<attenuation>,<actual power level></code> Check there’s agreement with what appears in the ''ifdsx'' definition in the procedure file. The actual power level should agree pretty well with the target level. The attenuation number can be anywhere between 0 (none) and 63 (maximum). If you see it at 0 or 63, it means the Conditioning module is having trouble getting the power to the right level. You may want to adjust the attenuators (see [[operations:rf_if_check_9.10.5|configuring the RF and IF signal paths]]) to get them back in range. | ||
| Line 96: | Line 129: | ||
| maserdelay</code> and check the difference reported in the log monitor | maserdelay</code> and check the difference reported in the log monitor | ||
| - Make sure Skype is running to allow a chat session with all participating sites plus the on-call person | - Make sure Skype is running to allow a chat session with all participating sites plus the on-call person | ||
| + | - Use the "Audio test" button on the log monitor to check the alarms are audible. | ||
| - Measure the Tsys while at a high elevation <code>systemp12</code> | - Measure the Tsys while at a high elevation <code>systemp12</code> | ||
| - | - 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 104: | Line 138: | ||
| test4 | test4 | ||
| test5 | test5 | ||
| - | test1</code> These commands send the antenna to the following set of (Az, El) coordinates in turn : (1, 87), (1, 6), (1, 45), (-269, 45), (269, 45), (1,87). | + | test1</code> These commands send the antenna to the following set of (Az, El) coordinates in turn : (1, 87), (1, 6), (1, 45), (-269, 45), (269, 45), (1,87). The idea here is to exercise the antenna and log the results se we can look for any changes over the days that may indicate mechanical problems. |
| - Lastly, export the data collected by MONICA from the MONICA GUI as follows: | - Lastly, export the data collected by MONICA from the MONICA GUI as follows: | ||
| - Select "Export -> ASCII Data" | - Select "Export -> ASCII Data" | ||
| Line 111: | Line 145: | ||
| - 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? | ||
/home/www/auscope/opswiki/data/pages/operations/documentation_ops2_austral15day.txt · Last modified: 2014/11/25 03:36 by Jim Lovell
Page Tools
