Below is an explanation of the current list of items to check during an observation:
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). The monitoring software will calculate the difference for you and should ring an alarm if the difference is not acceptable. See this entry in the common Problems section for a remedy.
mk5=mode?. The result should be
/mk5/!mode? 0 : ext : 0x55555555 : 2 : 2 ;for R1, R4 and CRF experiments,
/mk5/!mode? 0 : ext : 0x55555555 : 4 : 2 ;for OHIG, APSG and observations.
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.
disk_posin econtrol 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. It is normal for Yarragadee
disk_posto lag its expected value due to regular stows for USN uplinks.
wthcommand, which will look like this:\\/#wx#/16.1,1007.9,58.6\\Also make a note in the log of present weather conditions (if you're at the observatory). Start the comment with the word “weather”, e.g. “weather 50% cloud, light winds”. Note that weather is not currently logged at Yarragadee.
/usr/bin/xterm -name monit2 -e /usr2/fs/bin/monit2