User Tools
operations:documentation_ops2_cont14
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 Last revision Both sides next revision | ||
|
operations:documentation_ops2_cont14 [2014/04/30 05:20] Jim Lovell [Module Swaps] |
operations:documentation_ops2_cont14 [2014/05/07 10:30] Vasaant Krishnan [Some Additional Ho 26m Notes] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | |||
| ====== CONT14: Notes for operators ====== | ====== CONT14: Notes for operators ====== | ||
| Line 6: | Line 5: | ||
| * [[#schedule_overview_and_module_usage|Observing schedule and module usage overview]] | * [[#schedule_overview_and_module_usage|Observing schedule and module usage overview]] | ||
| + | * [[#26m_antenna|The Hobart 26m antenna]] | ||
| + | * [[#schedule_and_procedure_files|Schedule and procedure files]] | ||
| + | * [[#monitoring_observations|Monitoring observations]] | ||
| * [[#schedule_changeover|Schedule changeover procedure]] | * [[#schedule_changeover|Schedule changeover procedure]] | ||
| - | * [[#module_swaps|Swapping Mark5 modules]] | ||
| * [[#observatory_checking|Observatory checking procedure]] | * [[#observatory_checking|Observatory checking procedure]] | ||
| - | * [[#fringe_checks|Fringe Checks]] | ||
| ===== Schedule Overview and Module Usage ===== | ===== Schedule Overview and Module Usage ===== | ||
| - | Please read the [[operations:documentation_cont14_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_cont14_overview|Overview Page]] for general information on the CONT14 observations as well as session notes from IVS. The google calendar on the [[operations:schedule|schedules page]] describes experiment and shift times. |
| <note>Mark5 Nomenclature: "**Bank swap**" means changing where the data are recorded from one bank to the other. This does NOT mean modules are powered on/off or physically moved. | <note>Mark5 Nomenclature: "**Bank swap**" means changing where the data are recorded from one bank to the other. This does NOT mean modules are powered on/off or physically moved. | ||
| Line 19: | Line 19: | ||
| </note> | </note> | ||
| - | The CONT14 schedules are named ''C14nn'' where ''(nn = 01, 02, 03, ... , 15)''. They all start at 00:00 UT and finish at 23:57 UT so there is only a 3 minute gap, just enough time to change schedule files and modules (if needed). Every day, an hour is set aside for detailed system checks at each site. They are staggered so that only one antenna is out of the array at a time. System check times for our sites are as follows: | + | The CONT14 schedules are named ''C14nn'' where ''(nn = 01, 02, 03, ... , 15)''. They all start at 00:00 UT and finish at 23:57 UT so there is only a 3 minute gap, just enough time to change schedule files and banks (if needed). Every day, an hour is set aside for detailed system checks at each site. They are staggered so that only one antenna is out of the array at a time. System check times for our sites are as follows: |
| ^ Site ^ Check time (UT) ^ Check time (Hobart) ^ | ^ Site ^ Check time (UT) ^ Check time (Hobart) ^ | ||
| Line 51: | Line 51: | ||
| The other difference is that the S/X receiver on the 26m is cryogenic and can warm up. It's a good idea to keep an eye on the cryo temperatures and warn Brett if they start to increase. More on this and other things to keep an eye on are described in [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]]. | The other difference is that the S/X receiver on the 26m is cryogenic and can warm up. It's a good idea to keep an eye on the cryo temperatures and warn Brett if they start to increase. More on this and other things to keep an eye on are described in [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]]. | ||
| + | |||
| + | Also please note that the VNC session that is running the Field System software can be found by typing <code>vncviewer newsmerd:1</code> | ||
| ===== Schedule and procedure files ===== | ===== Schedule and procedure files ===== | ||
| Line 56: | Line 58: | ||
| All schedule and procedure files for the period from C1401 to C1415 should already be prepared and ready to use before your shift. | All schedule and procedure files for the period from C1401 to C1415 should already be prepared and ready to use before your shift. | ||
| - | Note that for CONT14 the procedure for setting up the Mark5 and DBBC is called ''setup8f'', NOT ''setupsx''. | + | <note important>Note that for CONT14 the procedure for setting up the Mark5 and DBBC is called ''setup8f'', NOT ''setupsx''.</note> |
| Line 64: | Line 66: | ||
| * [[operations:documentation.eRemoteControl_checklist_midob|Description of checklist parameters for AuScope 12m telescopes]] | * [[operations:documentation.eRemoteControl_checklist_midob|Description of checklist parameters for AuScope 12m telescopes]] | ||
| * [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]] | * [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]] | ||
| + | |||
| + | Also please keep the [[operations:handover|Handover notes]] page up to date. | ||
| ===== Schedule Changeover ===== | ===== Schedule Changeover ===== | ||
| + | |||
| + | <note>The Schedule Changeover procedure is the same for all telescopes except Katherine where the daily System Checkout coincides either with the start or end of a schedule.</note> | ||
| + | |||
| + | |||
| + | ==== All Stations Except Katherine ==== | ||
| There is only a 3 minute gap between the CONT14 schedules (23:57 to 00:00 UT). The end of each schedule has been modified to include commands to swap banks if necessary and then start the next schedule, so it should happen automatically. However, please pay careful attention when this happens. Note that it takes about 1 minute to swap banks as the commands include 30 second pauses either side of the bank swap command. The commands being sent are as follows (where "nn" is the schedule number and "xx" is the two-letter station code): | There is only a 3 minute gap between the CONT14 schedules (23:57 to 00:00 UT). The end of each schedule has been modified to include commands to swap banks if necessary and then start the next schedule, so it should happen automatically. However, please pay careful attention when this happens. Note that it takes about 1 minute to swap banks as the commands include 30 second pauses either side of the bank swap command. The commands being sent are as follows (where "nn" is the schedule number and "xx" is the two-letter station code): | ||
| Line 75: | Line 84: | ||
| Please make sure: | Please make sure: | ||
| * The new schedule starts. Look in the "Status Monitor" section of eRemoteCtrl and check that SCHED is set to the correct file | * The new schedule starts. Look in the "Status Monitor" section of eRemoteCtrl and check that SCHED is set to the correct file | ||
| - | * Type the command <code>mk5=bank_set?</code> and check that the correct module is selected. The first one in the list is the active bank and the number between the slashes is the module capacity in GB. For example: <code>17:28:12.83/mk5/!bank_set? 0 : B : HOB+0025/6000/1024 : A : NYAL-019/2000/1024 ;</code> says the module in Bank B is active, has a VSN of HOB+0025 and is 6000 GB (6 TB) in capacity. | + | * Type the command <code>mk5=bank_set?</code> and check that the [[operations:documentation_cont14_timetable|correct module]] is selected. The first one in the list is the active bank and the number between the slashes is the module capacity in GB. For example: <code>17:28:12.83/mk5/!bank_set? 0 : B : HOB+0025/6000/1024 : A : NYAL-019/2000/1024 ;</code> says the module in Bank B is active, has a VSN of HOB+0025 and is 6000 GB (6 TB) in capacity. |
| - | If for some reason the new schedule hasn't started or the wrong bank is selected then you will need to issue these commands by hand. | + | If for some reason the new schedule hasn't started or the wrong bank is selected then you will need to issue the ''bank_set'' and ''schedule'' commands by hand. |
| Once the new schedule has started: | Once the new schedule has started: | ||
| * [[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 CONT14 experiments from Yarragadee and Katherine are shipped to Hobart, and all data are eTransfer-ed to Bonn for correlation. | + | * Send off the log files from the previous experiment 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 CONT14 experiments from Yarragadee and Katherine are shipped to Hobart, and all data are eTransfered to Bonn for correlation. |
| - | ===== Module Swaps ===== | + | |
| - | Module swaps should be coordinated with local staff at the observatories and should //only//occur at the start of a System Check period. Remember that not all System Check periods require a module swap. Before a module is swapped, you and the local person **must** agree, on the phone, that both modules are idle. | + | ==== Schedule Changeover at Katherine ==== |
| - | === Procedure === | + | At Katherine the System Checkout period occurs in the hour before a schedule change on every day except Sunday, when it occurs in the hour after a schedule change. In either case, the procedure is to carry out the System Checkout first (see below), then make sure the [[operations:documentation_cont14_timetable|correct module bank]] is selected, then start the new schedule by hand. |
| - | * Wait for the System checkout period to start (times are given at the top of this page) | + | - Do the [[operations:cont14_observatory_check|System Checkout]] |
| - | * Wait for the current scan to finish, i.e. look in the schedule summary file for the next "Stop Data" time, wait for that time and look for a ''disk_record=off'' in the log to confirm that the command to stop recording has been sent. | + | - Type the command <code>mk5=bank_set?</code> and check that the [[operations:documentation_cont14_timetable|correct module]] is selected. The first one in the list is the active bank and the number between the slashes is the module capacity in GB. For example: <code>17:28:12.83/mk5/!bank_set? 0 : B : HOB+0025/6000/1024 : A : NYAL-019/2000/1024 ;</code> says the module in Bank B is active, has a VSN of HOB+0025 and is 6000 GB (6 TB) in capacity. If for some reason the the wrong bank is selected then you will need to issue these commands by hand: |
| - | * halt the schedule. This makes sure that no recording can possibly happen during the swap and crash the Mark5: <code>halt</code> | + | - <code>mk5=bank_set=inc</code> Wait about 15 sec |
| - | * wait about 10 sec and verify that the recording has stopped with a <code>mk5=dot?</code> command. Look for ''FHG=off'' in the response. If you see ''FHG=on'' then the Mark5 is recording and you should stop it with a <code>disk_record=off</code>. | + | - <code>mk5=bank_set?</code> |
| - | * Confirm with the local person that the four disk activity lights are NOT flashing on either module | + | - Start the schedule. The command to send is as follows (where "nn" is the schedule number and "xx" is the two-letter station code): |
| - | * **Wait for one minute** and again confirm with the local person that the four disk activity lights are NOT flashing. | + | - <code>schedule=c14nnxx,#1</code> |
| - | * Ask the local person to turn the key on the used module and swap it with a blank one of the correct size. | + | - Please make sure the new schedule starts. Look in the "Status Monitor" section of eRemoteCtrl and check that SCHED is set to the correct file and the time next to NEXT is in the (near) future. |
| - | * Wait for three green lights above the new module to indicate it is powered up and ready. | + | |
| - | * If this station is NOT Katherine you probably want to continue with the old, partially filled module. So confirm you have the right one with a <code>mk5=vsn?</code> and if it isn't, change to the correct one with a <code>mk5=bank_set=inc</code>, wait about 10 sec, then do and another <code>mk5=vsn?</code> | + | |
| - | * Make a note in the log that a new module has been inserted into Bank A or B, and say which bank is currently active. Please include VSN codes in the message. | + | |
| - | * Send an email to transfers@postoffice.maths.utas.edu.au so that we know what's happened | + | |
| - | Note that you can view the Mark5 recorder and the status of the modules remotely using the control room Pan-Tilt-Zoom (PTZ) web cameras: | + | Once the new schedule has started: |
| - | * Hobart: http://ptzhb.phys.utas.edu.au | + | |
| - | * Katherine : http://ptzke.phys.utas.edu.au | + | |
| - | * Yarragadee : http://ptzyg.phys.utas.edu.au \\ These cameras have pre-defined way-points (menu in lower right). Select the Mark5 recorder (e.g. for Hobart it's "mk5hb" for the 12m, "mkv" for the 26m). You may have to pan and zoom a bit to read the labels and see the lights. | + | |
| + | * [[operations:startmessage|Send a start message to IVS]]. | ||
| + | * Send off the log files from the previous experiment 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 CONT14 experiments from Katherine are shipped to Hobart, and all data are eTransfer-ed to Bonn for correlation. | ||
| ===== Observatory Checking ===== | ===== Observatory Checking ===== | ||
| Note that the observatory checking procedure requires you to interrupt the schedule and miss some scans. This allows us to skip checks if necessary but also means if the checks take less than the allocated hour we can be observing again as soon as possible. | Note that the observatory checking procedure requires you to interrupt the schedule and miss some scans. This allows us to skip checks if necessary but also means if the checks take less than the allocated hour we can be observing again as soon as possible. | ||
| - | Firstly, check the schedule summary printout and find out which is the first scan to finish after the start of the check period. The idea is to stop the schedule while no data are being recorded. For example, if the check time is 19:00 UT, then in the schedule below, it could be halted after 19:05:45 UT but before 19:07:43 UT: | + | Note that Observatory checks coincide with schedule changeovers at Katherine. See the notes above for the procedure at Katherine, but for all other sites, please read on... |
| - | <code> | + | Please follow this [[operations:cont14_observatory_check|Observatory System Checkout]] Procedure |
| - | Start Start Stop Record | + | |
| - | Scan Line# Source Az El Cable Record Data Data Dur Gbyte | + | |
| - | date = 2013NOV21 DOY = 325 | + | |
| - | . | + | |
| - | . | + | |
| - | . | + | |
| - | 325-1854 140 1610-771 170 6 CCW 18:53:58 18:54:08 18:58:33 4:25 35.0 * | + | |
| - | 325-1859 159 1255-316 119 19 CCW 18:59:02 18:59:12 19:05:45 6:33 43.8 * | + | |
| - | 325-1907a 178 0131-522 218 7 CCW 19:07:43 19:07:53 19:20:57 13:04 56.7 * | + | |
| - | . | + | |
| - | . | + | |
| - | . | + | |
| - | </code> | + | |
| - | Now, wait for the scan gap, and then type: | + | Now you can re-start the schedule. Just use the schedule name without any line number suffix. e.g. <code>schedule=c1408hb |
| - | <code>halt</code> | + | 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 is being stopped for system checks. e.g. <code>"Halting schedule for system checks</code> | + | |
| - | We want to keep all the check data in a separate log, so open a log file called "check.log": | + | 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> |
| - | <code>log=check</code> | + | |
| - | At this point it's probably worth verifying that the recorder has stopped: | + | ===== Some Additional Ho 26m Notes ===== |
| - | <code>mk5=dot?</code> | + | It is useful to be able to graphically view the 20K and 70K receiver temperatures, as well as the pressure vary with time. |
| - | 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 ''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. | + | On Ops2 start by: |
| - | + | <code>>> ssh oper@hobart | |
| - | Now the checks can begin: | + | >> cd /usr2/log/ |
| - | - Send the antenna to (Az, El) = (1, 87) deg <code>test1</code> | + | >> logpl</code> |
| - | - 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: | + | This will open up a GUI called: **LogPlotter 2**. |
| - | - 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 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. | + | |
| - | - Then type: <code>bread</code> You will see what the DBBC has set the BBC freqs to (compare with the .prc file). Output looks like this: <code><time>/<bbc name>/<Frequency (MHz)>/<Conditioning module in use>,<Bandwidth (MHz)>,...</code> the Frequency, Conditioning module label and bandwidth should agree with the listing in ''dbbcsxd''. | + | |
| - | - Check the maser. See the[[operations:maser_check|Hydrogen Maser check]] notes | + | |
| - | - check that the clock offsets are in range <code>clkoff | + | |
| - | 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 | + | |
| - | - 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> | + | |
| - | - [[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. //Wait for eRemoteCtrl to report ''flagr/antenna,acquired'' before continuing to the next//: <code> | + | |
| - | test1 | + | |
| - | test2 | + | |
| - | test3 | + | |
| - | test4 | + | |
| - | 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). 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: | + | |
| - | - Select "Export -> ASCII Data" | + | |
| - | - When asked for a file name, give the current obs code and station name (e.g. a1308hb), the word "check", and end with ".txt". For example: <code>a1308hb_check.txt</code> | + | |
| - | - Select "Export -> PNG image" | + | |
| - | - 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 | + | |
| - | 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 open a log file by clicking **File** --> **Open Log** in the header of the GUI. In the new window that pops up, input the log name (e.g. c1403ho.log) and open the file. | ||
| - | ===== Fringe Checks ===== | + | Go to **Plotting** and select |
| + | <code>rx-9-70k | ||
| + | rx-9-20k | ||
| + | rx-9-pres</code> | ||
| - | On 1921-293 every day. Procedure? | + | The plots do no update automatically, so issue **File** --> **Open Log** when an update is required. |
/home/www/auscope/opswiki/data/pages/operations/documentation_ops2_cont14.txt · Last modified: 2014/05/07 10:31 by Vasaant Krishnan
Page Tools
