The examples below assume Katherine running v252ai.
If you are stopping the previous schedule early (e.g. finishing a Fringe Check schedule ahead of time), use
halt to stop the schedule and then make sure the disk has stopped recording:
Now make sure you have the correct Mark5 module selected. Type
and check the serial number against what you think it should be. For the March LBA session, a list of modules agains experiments is given in the Observing Roster page. If you need to change modules use the
mk5=bank_set command. e.g. to change to Bank B:
, then run
If time permits, make a recording test before starting and check the bit stats and autocorrelations (note this won't work from a fringe-checking schedule):
From the Field System:
proc=v252aike setup01 disk_record=on (wait ~10 sec) disk_record=off scan_check postob
Now start the schedule
See these sections for notes on known problems, things to watch out for etc:
During the run, make sure that:
onsourceand check the antenna is tracking, which it should be provided a new source command hasn't recently been issued.
maserdelay. These values should be within 0.5 microsecond of each other and stable (i.e. similar results if you issue the commands again). If not, see this entry in the common Problems section for a remedy.
mk5=mode?. The result should agree with the procedure file setting in setup01
mk5=dot?. Make sure it reports a small offset (~<10ms) as the final value, that
FHG_offdepending on whether it is currently recording or not. If not,
fmsetmay need to be run.
To do this, open a terminal on pcfs[hb|ke|yg], and type
Only run fmset when the mk5 is not recording; therefore, halt the schedule with halt and stop recording with disk_record=off; check with mk5=dot?
When the interface appears, type
then confirm with a
Following this, the clocks should all be synchronised and agree with UT. Press the [Esc] key to exit
fmset. Then check the times again:
you can continue the schedule with cont
disk_posin the field system should report three values - the current number of btyes recorded, bytes at start of previous scan and bytes at start of current scan. If not currently recording, the first and third values should agree.
wthcommand, which will look like this:\\/#wx#/16.1,1007.9,58.6
One difference from IVS observing is that the postob procedure will also pop up a window listing the bit statistics of the recorded data. The observer should check this regularly to make sure it stays at near to the nominal 18/32/32/18 distribution (±2%).
If monitoring from Mt. Pleasant, use pmSTALMke.sh to monitor the alarms. If you want the station alarms to go off when there’s an error (rather than playing a sound through the speakers), use pmSTALMke.newsmerd.sh. I’d recommend changing the title of the terminal window to make it clear which alarms are from which station