Hobart 26m.

Disk VSN: HOB+0033

Data volume at beginning: 3199.326 GB

• 1814 UT Experiment started - delays due to problems with Ke (Bryn)
• 07:02:38UT Antenna Stowed due to high winds (JR)
• 7:45:00UT Schedule halted due to constant wind stows. Av speed: 59.26km/h (JR)
• 10:42UT Schedule resumed (JR). Scans effected: 056-0702 to 056-1050. (JR)
• 12:30 UT Antenna Stowed due to high winds, (AK)
• 13:08 UT Wind was consistently bad (>40km/hr) halted the schedule. (AK)
• 13:18 UT Stopped recording. Realised I should have probably should have entered “disk_record =off” after it stowed the first time. Log monitor still says recording (bug?) though disk_pos has not changed. (AK)
• 14:21 UT restarted the schedule once the wind had died down and the live page said “wind_ok”. Scans affected 056-1231 through to 056-1415. (AK)
• 15:38 UT Antenna stowed due to high winds. (AK)
• 16:15 UT Schedule halted, winds were still >42 km/hr
• 17:58 UT Antenna remained stowed due to winds. The wind temporarily dipped below 30 km/hr tried running “schedule=crf93” but no luck. Missed all scans 056-1538 onwards. (AK)

Hobart 12m:

Disk VSN: HOB+0042

Data volume at beginning: 0 GB

• 1814 UT Experiment started - delays due to problems with Ke (Bryn)
• 07:30UT ALARM Automatic wind stow activated (JR)
• 07:35UT Auto-stow released. Scans effected: 056-0726 and 056-0733 (JR)
• 07:40UT ALARM Automatic wind stow activated (JR)
• 07:51UT Auto-stow released. scans effected: 056-0740 and 056-0748 (JR)
• 08:16UT ALARM Automatic wind stow activated (JR)
• 08:21UT Auto-stow released. Scans effected 056-0813 and 056-0822 (JR)
• 08:27UT ALARM Automatic wind stow activated (JR)
• 08:46UT Auto-stow released, activated again 2 minutes later. (JR)
• 08:56UT Auto-stow released. Scans effected: 056-0822, 056-0830, 056-0838, 056-0846, 056-0853. (JR)
• 09:43UT ALARM Automatic wind stow activated (JR)
• 09:48UT Auto-stow released. Scans effected: 056-0940 and 056-0947 (JR)
• 09:54UT ALARM Automatic wind stow activated (JR)
• 09:59UT Auto-stow released. Scan effected: 056-0955 (JR)
• 12:28UT Automatic wind stow activated. (AK)
• 12:34UT Auto-stow released. Scan affected 056-1224 and 056-1231. (AK)
• 12:37UT mk5=mode? returns 0x55555555 : 2 : 2 ; which is not consistent for a crf experiment. Did a search for previous outputs of mk5=mode? and they were all displaying 0x55555555 : 2 : 2. According to wiki crf experiments should be 0x55555555 : 4 : 2. Not sure if this is of concern? (AK)
• 13:25UT Automatic wind stow. (AK)
• 13:30UT Antenna failed to recover from stow, winds were still high. (AK)
• 13:57UT winds slowed, antenna manually recovered as per wiki's guidelines. Scans affected 056-1327 through to 056-1351 (AK)
• 15:37UT Auto wind stop activated(?) acc to e remote control but no warning in logmonitor
• 15:53UT Auto-stow released. Scans affected 056-1538 and 056-1546. (AK)
• 15:58UT ALARM Automatic wind stow activated (AK)
• 16:04UT Auto-stow released. Scans affected 056-1553 and 056-1600 (AK)
• 16:31UT ALARM Automatic wind stow activated (AK)
• 16:37UT Auto-stow released. Scans affected 056-1631 (AK)
• 16:58UT ALARM Automatic wind stow activated (AK)
• 17:05UT Auto-stow released

Katherine 12m:

Disk VSN: HOB+0119

Data volume at beginning:

• Problems with the Hardware clock on PCFS. PCFS needs restarting again (Bryn)
• PCFS running after reboot. Data good from scan 056-0126 onward — Jim Lovell 2016/02/25 03:34
• 12:37UT mk5=mode? returns 0x55555555 : 2 : 2 ; which is not consistent for a crf experiment. Did a search for previous outputs of mk5=mode? and they were all displaying 0x55555555 : 2 : 2. According to wiki crf experiments should be 0x55555555 : 4 : 2. Not sure if this is of concern? (AK)

Yarragadee 12m:

Disk VSN: MAT+0100

Data volume at beginning: 0 GB

• 1814 UT Experiment started - delays due to problems with Ke (Bryn)
• 12:37UT mk5=mode? returns 0x55555555 : 2 : 2 ; which is not consistent for a crf experiment. Did a search for previous outputs of mk5=mode? and they were all displaying 0x55555555 : 2 : 2. According to wiki crf experiments should be 0x55555555 : 4 : 2. Not sure if this is of concern? (AK)