This is an old revision of the document!
Below is an explanation of the current list of items to check during an observation:
onsource
and check the antenna is tracking, which it should be provided a new source command hasn't recently been issued.clkoff
and 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 and R4 experiments, (0 : ext : 0x55555555 : 2 : 1 ;, for Katherine????????)
/mk5/!mode? 0 : ext : 0x55555555 : 4 : 2 ; for OHIG, APSG and CRF observations.
* Mark5: mk5=dot? response nominal
This is a check of the Mark5 decoder time. Check the time offset in the formatter with this command in econtrol:
mk5=dot?. Make sure it reports a small offset (~<10ms) as the final value, that
syncerr_eq_0 and that
FHG_on or
FHG_off depending on whether it is currently recording or not.
* Mark5: disk_pos OK
The command
disk_pos in eRemoteControl 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_pos to lag its expected value due to regular stows for USN uplinks. The Log Monitor also reports disk usage
* Meteorology: Weather (wth) being logged
Look through recent messages in the field system log for output from the
wth'' command, which will look like this:\\/#wx#/16.1,1007.9,58.6