User Tools

Site Tools


operations:agenda2018_10_04

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
operations:agenda2018_10_04 [2018/10/04 02:56]
Lucia Plank
operations:agenda2018_10_04 [2018/10/04 03:16] (current)
Lucas Hyland
Line 1: Line 1:
 **Chair:** Lucas **Chair:** Lucas
  
-**Attended:​** ​+**Attended:​** ​Tiege, Mas, Atifur, Katie, Lucia, Simin, Jay 
  
 **Absent:** Patrick, Ross, Jesse **Absent:** Patrick, Ross, Jesse
Line 8: Line 8:
  
     * 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 ​says YG stowed even though tracking and onsource (r4861, r1862), az el still move just little box says stow 
-    * 00 UT session ​start postponed+    * 00UT session postponed ​- probably not until 2020? 
 +    * Fix wiki 
 +    * New observers
  
  
Line 16: Line 18:
     * **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** -  ​HB ​'​Network to the antenna failed. Fixed by power cycling media adaptor, then rebooting antenna controller'​. How does one repeat this fix? Ask Jamie another time
  
  
-    * **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** - KE '​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?​) ​- Tried normal things, dimino check, restart mk5.
  
  
-    * **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? ​ 
/home/www/auscope/opswiki/data/pages/operations/agenda2018_10_04.txt · Last modified: 2018/10/04 03:16 by Lucas Hyland