This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
handover:c1715_v1715 [2017/12/12 01:13] Patrick Yates |
handover:c1715_v1715 [2017/12/13 00:24] (current) Patrick Yates |
||
---|---|---|---|
Line 3: | Line 3: | ||
**Hobart 26m** | **Hobart 26m** | ||
- | Disk VSN: HOB+0094 | Data volume at beginning: 8993.644 GB | + | Disk VSN: HOB+0094 | Data volume at beginning: 8991.644 GB |
+ | 346-0614b | ||
* 00:00 UT - Experiment started OK (Jonny) | * 00:00 UT - Experiment started OK (Jonny) | ||
+ | * 0616UT Missed scan 346-0614b slewing (Liz) | ||
**Katherine 12m** | **Katherine 12m** | ||
Line 12: | Line 13: | ||
* 00:00 UT - Experiment started OK (Jonny) | * 00:00 UT - Experiment started OK (Jonny) | ||
+ | * 0632UT "-error m5 -104 mk5cn: time-out, connection closed, as recording started", but fs in vnc is okay, eremote also seems okay so just noting. (Liz) | ||
+ | * 2017.346.06:29:14.27?ERROR m5 -104 mk5cn: time-out, connection closed | ||
+ | * 2017.346.14:24:41.27?ERROR m5 -104 mk5cn: time-out, connection closed | ||
+ | * 2017.346.18:55:41.28?ERROR m5 -104 mk5cn: time-out, connection closed | ||
+ | * This error only happened on one scan for each instance. Checking (dot, mode) and pinging the mk5 showed that it was both connected and okay (Lucas). | ||
+ | |||
**Yarragadee 12m** | **Yarragadee 12m** |