This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
handover:r1757 [2016/09/12 19:32] Jesse Swan |
handover:r1757 [2016/09/13 10:43] (current) Jesse Swan |
||
---|---|---|---|
Line 7: | Line 7: | ||
* 17:00 UT - Experiment started OK. (Tiege) | * 17:00 UT - Experiment started OK. (Tiege) | ||
* 18:47 UT - Alarm due to delay through DBBC changing, will monitor to see if the delay stabilises. (Tiege) | * 18:47 UT - Alarm due to delay through DBBC changing, will monitor to see if the delay stabilises. (Tiege) | ||
- | * 18:50 UT - Delay immediated stabilised at ~0.4 us, with variation from 0.398 us through to 0.403 us. Going to leave it be as long as it does not start drifting again. (Tiege) | + | * 18:50 UT - Delay immediately stabilised at ~0.4 us, with variation from 0.398 us through to 0.403 us. Going to leave it be as long as it does not start drifting again. (Tiege) |
* 19:26 UT - delay difference drifted again to 0.435 us, going to try and see if restarting DBBC software helps, seems to be staying at the nominal ~0.257 us post-reset. Halted schedule during 256-1925a, first scan after reset will be 256-1944. (Tiege) | * 19:26 UT - delay difference drifted again to 0.435 us, going to try and see if restarting DBBC software helps, seems to be staying at the nominal ~0.257 us post-reset. Halted schedule during 256-1925a, first scan after reset will be 256-1944. (Tiege) | ||
+ | * 22:59 UT - Have noticed that in the time between the previous two checklists ( time where I was asleep) the delay difference has very slowly drifted from ~0.26 us to 0.285 us, gradual enough that is hasn't yet set off the alarm. Jim will be taking over soon so I will mention it to him. (Tiege) | ||
+ | * 23:25 UT: DBBC was still causing a drift so rebooted the machine. Jim | ||
+ | * 23:37 UT: Restarted with scan 256-2347. OK now. Jim | ||
** Katherine ** | ** Katherine ** | ||
Line 20: | Line 23: | ||
* 18:25 UT - Total missed/dodgy scans list: 256-1700b to 256-1733b inclusive were recorded onto USN-0069 using mk5ke (potentially dodgy), scans 256-1742 through to 256-1802 were missed while switching to mk5-2ke, 256-1808 and 256-1809 WERE RECORDED on the new disk (USN-0017), then 256-1814 through to 256-1827b were missed attempting to correct clkoff issue. (Tiege) | * 18:25 UT - Total missed/dodgy scans list: 256-1700b to 256-1733b inclusive were recorded onto USN-0069 using mk5ke (potentially dodgy), scans 256-1742 through to 256-1802 were missed while switching to mk5-2ke, 256-1808 and 256-1809 WERE RECORDED on the new disk (USN-0017), then 256-1814 through to 256-1827b were missed attempting to correct clkoff issue. (Tiege) | ||
* 18:30 UT - Experiment should be running as normal from scan 256-1833b onwards. Just note that 256-1808 and 256-1809 were both recorded to this module also. (Tiege) | * 18:30 UT - Experiment should be running as normal from scan 256-1833b onwards. Just note that 256-1808 and 256-1809 were both recorded to this module also. (Tiege) | ||
+ | * 00:58 UT - Observations stopped from 00:55:48 to 00:58:10 to put in another module in bank A. Jim | ||
+ | |||
+ | * **0720UT to 1030UT** (JS) | ||
+ | * MK5-2KE crashed as well, this was a UPS issure but in the meantime MK5 was fixed | ||
+ | * GPIB fixed, clkoff/maserdelay now working | ||
+ | * Module USN-0017 transferred from mk5-2ke to mk5 bank A, recording will continue on this | ||
+ | * mk5 and dbbc reset, and synced with fmset | ||
+ | * First new scan 257-1039. Missed scans 257-0720b through 257-1035c (215GB deficit) | ||