The examples below assume Katherine running v252ai.

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

schedule=v252aike

During the run, make sure that

• The telescope is onsource
• There are no mark5 recording errors
• clkoff and maserdelay are within 0.3 microseconds of eachother
• That the autocorrs/bit stats look sensible
• Systemp readings are nominal (Tsys readings are kludged in. If the experiment is recording a single polarisation both tsysS and tsysX will report whatever that is. For dual pol, tsysS is RCP and tsysX is LCP)

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

See the Current Issues section for known problems and how to fix them.

See also these notes on