User Tools
handover:a1508
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
handover:a1508 [2015/02/18 23:30] David Horsley |
handover:a1508 [2015/02/19 18:07] (current) liza |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Data volume at beginning: 1.4 GB (test recording + fringe check) | Data volume at beginning: 1.4 GB (test recording + fringe check) | ||
| + | |||
| + | * 00:11 UT : disc pos ~40 GB behind - Rxmon stop command returns "operation not permitted; no process killed" not sure what to do since everyone is in the WHS training... (Ellen) | ||
| + | * 01:41 UT : Rxmon stopped and started. (Ellen) | ||
| + | * 02:10 UT : swapped modules over. Looked like everything was running again fine but then the mark 5 went crazy and tried to record to both modules. We did a full power cycle 3 times to fix this. Scans between 050-0211 and 050-0239 are either bad or were missed. (Ellen) | ||
| + | * Schedule resumed for scan 050-0241. (Ellen) | ||
| + | * 09:46UT: mark 5 lost connection. Halted schedule tried SSReset to no avail, hard rebooted as superuser, seemed to fix the problem. Schedule restarted 09:51, missed scans 050-0944b to 050-0956a (Imogen) | ||
| + | * 10:11UT: noticed that the time offset in the formatter (when issued mk5=dot? command) was more than 10ms. In fact, it was 50ms. However, this value fell with the next check and continued to fall until it was below 10ms. (Imogen) | ||
| + | * 10:54UT: mark 5 keeps losing connection, not sure why (Imogen) | ||
| + | * 11:49UT: scans 050-1146 to 050-1156 were lost due to attempt to heal the "ERROR m5 -104 mk5cn: time-out, connection closed" (restarted DIMino and fs, helped for now) (Liza) | ||
| + | * 12:02-04UT: DIMino stopped, restarted it twice, affected scans 050-1202, 050-1204a (Liza) | ||
| + | * 13:48-13:59UT: Problems with Mark5B, restarted DIMino repeatedly. Scans affected are 050-1348 to 050-1358. Meanwhile, clock jump occured, fmset synch performed 14:01;23 between scans 050-1400 and 050-1402 (Liza) Due to the Mark5 resetting, following scans were recorded to a wrong module UAO-0026/2000: | ||
| + | * 1 a1508_hb_050-1356+ | ||
| + | * 2 a1508_hb_050-1358 | ||
| + | * 3 a1508_hb_050-1400 | ||
| + | * 4 a1508_hb_050-1402 | ||
| + | * 16:45 restarted DIMino, fs, schedule. Scans 050-1645 and 050-1647 were affected (Liza) | ||
| + | * By the end, it recorded 300GB less due to repeated ERROR m5 -104 mk5cn: time-out, connection closed and attempts to recover it (Liza) | ||
| **Katherine 12m:** | **Katherine 12m:** | ||
| Line 12: | Line 29: | ||
| Data volume at beginning: 1.12 (test recording + fringe check) | 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) | + | * 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. | |
| - | 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) | |
| - | 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: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) |
| - | + | * Due to continuous recording, disc pos now ~53 GB ahead of schedule. (Ellen) | |
| - | 23:00 UT Jamie walks in the room and suddenly the it decides to fix itself >.< (Ellen) | + | * Scan 049-2327 completed successfully. (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) | + | |
| Line 39: | Line 52: | ||
| * The DBBC issue causing problems in S band is ongoing | * The DBBC issue causing problems in S band is ongoing | ||
| + | * The wind monitor has not been able to connect from 22:00 UT to 00:30 UT (and counting). (Ellen) | ||
| + | * By the end, it recorded 100GB less (Liza) | ||
| {{tag>}} | {{tag>}} | ||
/home/www/auscope/opswiki/data/attic/handover/a1508.1424302212.txt.gz · Last modified: 2015/02/18 23:30 by David Horsley
Page Tools
