User Tools

Site Tools


operations:agenda2020_02_27

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.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
operations:agenda2020_02_27 [2020/02/26 12:44]
Simin Salarpour
operations:agenda2020_02_27 [2020/02/27 02:34] (current)
Simin Salarpour
Line 3: Line 3:
 ** Next week's chair: ** Mas ** Next week's chair: ** Mas
  
-**Attended:​** ​+**Attended:​** ​Mas, Katie, Becca, Prad, Jay, Lim, Jamie, Gabor, Guifre
  
 **Apologies:​** ​ **Apologies:​** ​
  
-**Absent:​** ​+**Absent:​** ​Earl, Eloise, Lucas, Patrick, Tiege
  
 **General Issues** **General Issues**
-    * +    * Hobart 26m 
 +        * Problem with the brakes problem/a hydraulic fault alarm   
 +           * Hydraulic pipes have to be replaced, need one or two more days 
 +    * LBA shifts coming on March, June and July 
 + 
  
                
 **Handover Issues** **Handover Issues**
     * R4934      * R4934 
-        * Yarragadee+        * Yarragadee ​12m
               * Large difference between formatter and maser delays. Check for stability of new offset. error happens occasionally and clears itself (Lim)               * Large difference between formatter and maser delays. Check for stability of new offset. error happens occasionally and clears itself (Lim)
 +                  * Jamie will look at it.
     * AUA061     * AUA061
-        * Yarragadee +        * Yarragadee ​12m 
-              * Very large positive(!?) data difference. +200TB or about 5%. Module is large enough to handle additional data (Lucas). +              * Very large positive data difference. +200TB or about 5%. Module is large enough to handle additional data (Lucas). 
 +                  * Probably one-hour si0056 experiment causes the data difference.
         * Hobart 12m         * Hobart 12m
-              * When I set up the delaylive, noticed a series of clock-jumps on the dbbcho ​starting at 5:00UT, then again at 6:00,6:30 and 7:00. Clock jumps are on the order of -0.015us(Lucas) +              * series of clock-jumps on the dbbcho on the order of -0.015us (Lucas). 
-aHave not reset the dbbcho (yet) as the summary script reports okay delays and samplers. Appears stable at the moment but if it jumps again I will reset (Lucas) +                  * In mix-mode observations can be ignored
-b. Jumped again at 8:00 UT, halted and reconfigured dbbcho. Missed scan 057-0821b, 0825+        * Katherine 12m      ​ 
-c. Called Jamie. clkoff isn't actually indicative for dbbcho problems when hooked up to Hobart12m. So don't worry about delaylive hb.  ​ +              * Drives lost connection, got stuck (Lucas). 
-              * Drives lost connection, got stuck. Required a thorough reboot (reboot drives didn't work), reboot system then a 2min wait+[drives on]+operate+source=disable+antenna=open+antenna=operate worked ​(Lucas). ​Missed scans 057-0839 up to 057-0851. +              * Flexbuffke got into a nasty state and wasn't happy (Lucas)
-                ​ +              * The current fix is to (halt obviously), umount all the drives, remount them, restart jive5ab and re-setupsx (Lucas). 
-              * Flexbuffke got into a nasty state and wasn't happy. ​The first sign was the data rate on Grafana went from the '​normal'​ smooth 3Gbps scans to ugly, spiky and somewhat random data rates. Another sign was the number of dropped packets in “mk5=evlbi?​” – maybe we should add this to katherine midob? +                  * Due to wet season ​and power outagesHave to restart the connection ​and Fluxbuff. 
-                * The current fix is to (halt obviously), umount all the drives, remount them, restart jive5ab and re-setupsx. On flexbuffke there are two scripts in /tmp/. After logging in as su (ssh observer@flexbuffke then su in random terminal), run script /​tmp/​UMountAllFlexbuff.sh; wait make sure they all unmount, then run /​tmp/​MountAllFlexbuff.sh. After this you need to go to the flexbuffke jive5ab window (normally running on the vnc, with lots of “Reply: !”–type stuff) ​and ctl-C OR just pkill jive5ab from observer@flexbuffkeThen restart ​by up-arrowing or typing “/​opt/​jive5ab-2.9.0 -m2 &” or maybe …“-3.0.0” jury is out which one atm. Then setupsx in the field system ​and make sure the datarate is okay and “mk5=evlbi?​” looks happy and is increasing (Lucas) +                  ​
  
  
        
   ​   ​
/home/www/auscope/opswiki/data/attic/operations/agenda2020_02_27.1582721093.txt.gz · Last modified: 2020/02/26 12:44 (external edit)