This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
operations:agenda2018_10_04 [2018/10/04 02:46] Lucas Hyland |
operations:agenda2018_10_04 [2018/10/04 02:56] Lucia McCallum |
||
---|---|---|---|
Line 9: | Line 9: | ||
* Katherine maser/dbbc/heating appears to have been successful. No more clock jumps recorded in past week? | * Katherine maser/dbbc/heating appears to have been successful. No more clock jumps recorded in past week? | ||
* Antenna monitor shows YG stowed even though tracking and onsource (r4861, r1862) | * Antenna monitor shows YG stowed even though tracking and onsource (r4861, r1862) | ||
+ | * 00 UT session start postponed | ||
**Handover Issues** | **Handover Issues** | ||
- | * R4860 - lots of issues with mk5 and module but they appear resolved and/or specific to that module. Laggy HDD in drive caused mk5cn errors (alarms) despite DIMino running and responding. The timeout lag caused the fs to think mk5cn was not responding (in 5ms period over which it checks?) | + | * **R4860** - lots of issues with mk5 and module but they appear resolved and/or specific to that module. Laggy HDD in drive caused mk5cn errors (alarms) despite DIMino running and responding. The timeout lag caused the fs to think mk5cn was not responding (in 5ms period over which it checks?) |
- | * AUM010 - 'Network to the antenna failed. Fixed by power cycling media adaptor, then rebooting antenna controller'. How does one repeat this fix? | + | * **AUM010** - 'Network to the antenna failed. Fixed by power cycling media adaptor, then rebooting antenna controller'. How does one repeat this fix? |
- | * R1861 - 'Experiment started late due to bad module (USN-0191/2000). First scan 268-1801b. (Atifur)' - What was the diagnostic for this? How do we see this early and prevent it? (did you do a test recording?) | + | * **R1861** - 'Experiment started late due to bad module (USN-0191/2000). First scan 268-1801b. (Atifur)' - What was the diagnostic for this? How do we see this early and prevent it? (did you do a test recording?) |
- | * CRDS98 - needed to manually download and drudg .vex file as the slogit scripts only recognise .skd files? | + | * **CRDS98** - needed to manually download and drudg .vex file as the slogit scripts only recognise .skd files? |