Hobart 12m:

Disk VSN: HAY-0055

Data volume at beginning: 1.4 GB (test recording + fringe check)

Katherine 12m:

Disk VSN: HOB+0124

Data volume at beginning: 1.12 (test recording + fringe check)

22:35 UT clkoff returned a value ot ~E-001, while maserdelay was fine. “counter” didn't help, neither did “fmset” (Ellen)

Scans 049-2235 to 049-2245 are bad.

22:47 UT restarted the DBBC session and reconfigured, clkoff is still giving value of ~E-002. I open fmset again and the values all matched up, but I synced it any way in the hope of fixing the clkoff issue. But this actually un-synced the 3 numbers… “counter” didn't fix it this time either. (Ellen)

23:00 UT Jamie walks in the room and suddenly the it decides to fix itself >.< (Ellen)

23:02 UT Schedule wouldn't start properly, then the field system wouldn't respond to any commands. Tried to kill it but it wouldn't die properly so I couldn't restart it. Dave came to the rescue and killed it properly so I could restart the schedule at 23:21 UT. For most of this time the mark 5 was recording non-stop. Missed scans 049-2247a to 049-2326. (Ellen)

Scan 049-2327 completed successfully. (Ellen)

Yarragadee 12m:

Disk VSN: HOB+0121

Data volume at beginning: 8369 GB

• We had some initial trouble with the module or mk5 when it refused to do a test record. The pointers were noticed to be at ~4TB rather than the expected ~8TB. The module eventually came good after:
  • moving the module to the other bank
  • rebooting mk5yg
  • running SSReset
  • restarting DIMino several times,
  • running “mk5=recover=2”
• The DBBC issue causing problems in S band is ongoing