This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
handover:aua003 [2015/05/07 03:49] cjordan |
handover:aua003 [2015/05/07 12:58] cjordan |
||
---|---|---|---|
Line 16: | Line 16: | ||
Data volume at beginning: 5040.692 GB <- This value was stop position from aua002. aua003hb.log says that disk_pos is actually 5357.358 GB (vk) | Data volume at beginning: 5040.692 GB <- This value was stop position from aua002. aua003hb.log says that disk_pos is actually 5357.358 GB (vk) | ||
* 18:00 UT - Experiment started OK (vk) | * 18:00 UT - Experiment started OK (vk) | ||
+ | * 11:30 UT - Disc position keeps falling behind. Is now ~130 GB behind schedule (lost 30 in 2.5 hours). (Ellen) | ||
Line 26: | Line 27: | ||
* 18:00 UT - Experiment started OK (vk) | * 18:00 UT - Experiment started OK (vk) | ||
+ | * 06:15 UT - brief network latency spike caused the computer acu time difference to raise to ~1s. Resolved after 2 min. | ||
+ | * 12:36 UT - difference between maserdelay and clkoff reached -0.5 us. Counter didn't help. Ran fmset at the end of the scan, didn't help. So I halted the schedule at 12:52 UT shutdown the DBBC and reconfigured it and that fixed it. (Ellen) | ||
+ | * 12:57 UT - schedule resumed. Missed scan 127-1251. (Ellen) | ||
**Yarragadee 12m:** | **Yarragadee 12m:** | ||
Line 40: | Line 44: | ||
* atsnap schedule not running for first ~6 hours. First good source at 23:54. (Dave) | * atsnap schedule not running for first ~6 hours. First good source at 23:54. (Dave) | ||
+ | * 06:05 UT - Finished to make way for next experiment. (Dave) | ||
| |