====== System checks ======

Firstly, check the schedule summary out and find out which is the first scan to finish after the start of the check period (check times for each antenna are given in the table [[operations:documentation_austral15day_overview#system_checks|on this page]]). 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:

<code>
                                         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>

  * Wait for the scan gap and look for a ''disk_record=off'' in the log to confirm that the command to stop recording has been sent, and then type: <code>halt</code>
  * 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>. Repeat this step if necessary.
  * 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>
  * If this System Check period is [[operations:documentation_austral15day_overview#system_checks|one allocated for a Module Swap]], do it next in coordination with the local person on-site:
    * Follow the [[operations:documentation_cont14_module_swap|CONT14 Module Swapping procedure]]
  * 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.

Note: need to start MONICA from the command line
<code>
ssh ops-serv2
./omc.sh
</code>

Now the checks can begin. Note that the procedure is different for the 12m antennas and Hobart 26m:

==== 12m antenna Checkout Procedure ====
  - 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). 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 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 ''ifd8f'' 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 ''dbbc8f8''.
  - 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. a1402hb), the word "check", and end with ".txt". For example: <code>a1402hb_check.txt</code>
    - Select "Export -> PNG image"
    - As above but a ".png" extension. e.g. <code>a1402hb_check.png</code>