• new recording mode (512Mbps istead of 256), use setup8f instead of setupsx.

HO:

• schedule files was downloaded and drudged, sum file was created.
• Experiment started ok. (JMc)

KE:

• Module HOB+0034 start at 0 GB
• Tsys in bands 9-12 a bit high; change attenuation level?
• DBBC error at 1712. Reconfiguration did not correct problem, so power cycled DBBC. No data between 1713 and 1730. (JMc)
• 11:42 UT - Tsys measures all consistently quite high - probably due to current the storm. (Ellen)

YG:

• Module HOB+0104 (16 TB) start at 2.179 GB
• Experiment started OK. (JMc)

Hobart 26m

Module: HAY-005, start pos 1895.329 GB.

• 18:15 UT - wth command not working, gives error “Problem connecting to metserver socket. Illegal error class code: 0xffffffff.” I had a look at the station file in pfmed but nothing I tried worked. Not urgent so I'll report it at a more reasonable hour. (Ellen)
• 18:31 UT - Experiment started ok. (Ellen)
• 19:49 UT - Again, I am getting alarms fairly regularly, saying “ERROR m5 -104 mk5cn: time-out, connection closed”. This doesn't appear to mean anything as everything still seems fine to me. It has also happened at 19:51, 20:19, 20:22, 21:10, 21:13 UT. (Ellen)
• 22:15 UT - Had to halt schedle for a quick maintinence check. Also, had to restart the field system to reset some settings. The timeout on the Mark 5A was set to 1/10 of a second, which was occasionally setting off a time out alarm. This problem has now been fixed. Schedule restarted and recording to a new module. Disk pos cannot be checked due to change of module. (Imogen)
• The weather monitor machine has failed and is being fixed today. Weather is being reported manually via the BOM website. (Imogen)
• 04:02UT Schedule halted due to reciever maintence (Imogen)
• 04:34UT schedule resumed after reciever maintence (Imogen)

• 0817 UT Telescope started recording to HOB+0095 at some time during Imogen's shift; this wasn't noted. Currently at 399 GB on this module (JS)
• 0822 UT 400.8 GB recorded to HOB+0095 of 650 GB total for experiment to this point. I'm guessing HAY-005 was a ~2TB module and a deficit accounts for the rest (JS)
• 0824 UT There is ~ 150 GB of missing data (I think, i don't know when Imogen changed modules) but the scans that were missed were not noted (sorry Ross) (JS)

Katherine

Module: TR-00014, start pos 0 GB

• 18:30 UT - Experiment started ok. (Ellen)
• 15:54 UT - Antenna stuck, scans 303-1553 and 303-1558 unreliable (Ross).

Yarragadee

Module: NYAL-019, start pos 0 GB

• 18:30 UT - Experiment started ok. (Ellen)

Ho

VSN: HAY-0050 (+1025 GB)

• Exp started OK (JS).
• Perpetual alarm from error m5 -104 mk5cn: time-out, connection closed. The field system and markV still responds to commands thouygh (JS)
• weather monitor not working, going to get Brett to reboot it tomorrow (Imogen)
• 11:20 UT - 70K stage is at 100K with 20K stage at 65K (Ross).

Ke

VSN: OSOD-038 (+0 GB)

• Exp started OK (JS).
• 06:16 UT - Large clock drift detected during check, watching for stability (Ross).
• 06:26 UT - Clock clearly unstable, performed fmset in between scans for now (Ross).
• 06:32 UT - dbbc reset performed in between scans. First safe scan is 300-0634a (Ross).
• 10:06 UT - Clock starting to drift, few dbbc restarts and fmsets to get stable, missing scans from 300-1007b onwards. (Ross).
• 10:53 UT - Field system has become unresponsive and recording cannot be resumed. Field system restarted and recording resumed with scan 300-1116 (Ross). – Missing 60 GB

Yg

VSN: NRCAN-09 (+0 GB)

• Exp started OK (JS).

Hobart 26m

Module: HAY-0050, start pos 0 GB

• 18:30 UT - Experiment started OK. (Ross)
• 00:30UT - Drives on telescope failed, needed to be reset. Missed scans from 295-2348 to (Imogen)
• 06:00 UT - Several times since I started, get the error “m5 -104 mk5cn: time-out, connection closed”. There appears to be nothing wrong with anything and the experiment keeps running without problems. (Ellen)
• 16:20 UT - Receiver pressure is seems to be holding at about 5. Keeping an eye on it. (Ellen)
• 17:01 UT - Receiver pressure has now climbed to 6. Called Brett, he is going to leave it till later since there is not another experiment following. (Ellen)

Katherine

Module: SHAO-017, start pos 0 GB

• 18:30 UT - Experiment started OK. (Ross)296-0638
• 06:38 UT - Delay difference drifting significantly. Halting schedule and restarting DBBC. Missed scan 296-0638. (Ellen)

Yarragadee

Module: BKG-0006, start pos 0 GB

• 18:30 UT - Experiment started OK. (Ross)

Ho

VSN: HOB+0096 (+11385 GB)

• Exp started OK (Dave).

Ke

VSN: USN-0097 (+0 GB)

• Exp started OK (Dave).
• Large amount of interference in Channels 13 & 14 (0 based) (Dave)

Yg

VSN: USN-0032 (+0 GB)

• Exp started OK (Dave).

Hobart 26m

Module: HOB+0096, start pos 10316.985 GB

• 18:16 UT - Receiver pressure at 4.2, 70K stage at 105.9, 20K stage is 67.1. I called Brett and he thinks we should leave it until he can go out at 9am in 3.5 hours. (Ellen)
• 18:30 UT - Experiment started ok. (Ellen)
• 02:38UT schedule halted due to wind stows (Imogen)
• 03:32 UT schedule resumed after wind died down. Missed scans 289-0239a-289-0343 (Imogen)
• 12:31 UT He pressure too low and 70K temperature too high (Ross).

Katherine

Module: MED-0020, start pos 0 GB

• 18:30 UT - Experiment started ok, except the command “clkoff-2” was still in the proc file, so it recorded a huge delay difference. Halted the schedule after the first scan. I couldn't find the right file, called Imogen to fix. (Ellen)
• 18:50 UT - Imogen was unable to fix due “clkoff-2” to internet problems. I have changed the settings in the log monitor so it won't ring alarms every scan. Field system crashed when I tried to restart the schedule. Had to reboot pcfske. The mk5 then crashed and needed power cycling. Did test recording and the Autocorrelation looks fine. (Ellen)
• 19:52 UT - Schedule resumed. Scans missed 288-1836 to 288-1949, inclusive (~ 90GB). (Ellen)

Yarragadee

Module: USN+0224, start pos 5505.2 GB

• 18:30 UT - Experiment started ok. (Ellen)
• 22:03 UT - All tsys values in S-band way too high. (Ellen)