General Comments

• I messed up, and didn't start the telescopes at 1700UT. By the time I realised it was 2300UT. All telescopes running by 2320UT

Hobart 12m:

Disk VSN:HOB+0120

Data volume at beginning: 5730 GB

• 1400UT Experiment started OK (JS)
• 0020UT Tracking outside tolreance messages in eremote control. Accordign to the wiki this happens on windy days, keeping an eye on this. (AK)
• 0022UT Wind stow activated (00:22:18)
• 0027UT Wind stow released (00:27:31). Scans affected 250-0023 through to 250-0027. (AK)
• 0157UT Auto-stow sequencing from 01:57:24 to 02:03:05. Scans affected 250-0157 to 250-0202
• 0210UT Auto-stow sequencing 02:10:59 to 02:16:09. Scans affected 250-0210 to 250-0215
• 0310UT Auto-stow sequencing 03:10:23 to 03:34:54. Scans affected 250-0311 to 250-0334
• 0335UT Auto-stow sequencing 03:35:54 to 03:55:13. Scans affected 250-0335 to 250-0354
• 0356UT Auto-stow sequencing 03:56:20 to 04:01:57. Scans affected 250-0356 to 250-0401
• 0404UT Auto-stow sequencing 04:04:28 to 04:23:00. Scans affected 250-0403 to 250-0422.
• 0650 UT disk_pos lagging by at approx 20 Gb at last check. (AK)
• Final disc pos 56 GB behind schedule (Ellen)

Katherine 12m:

Disk VSN:HOB+0051

Data volume at beginning: 0 GB

• 1400UT Experiment started OK (JS)
• 0650 UT disk_pos lagging by approx 55 Gb at last check. (AK)
• Final disc pos 62 GB behind schedule (Ellen)

Yarragadee 12m:

Disk VSN: USN+0225

Data volume at beginning: 0 GB

• 1400UT Experiment started OK (JS)
• 2059UT WARNING: error ib -4 gpib device time-out on response c1. Both clkoff and maserdelay are responsive, nothing seems wrong. (AK)
• 0040UT disk_pos is lagging by approx 60 gb. (AK)
• 0650 UT disk_pos lagging by approx 100 Gb at last check. (AK)
• Final disc pos 143 GB behind schedule (Ellen)