Differences

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

Link to this comparison view

Both sides previous revision Previous revision
operations:agenda2021_10_28 [2021/10/28 13:18]
Earl Lester
operations:agenda2021_10_28 [2021/10/28 13:18] (current)
Earl Lester
Line 21: Line 21:
  
 yg pointing check not working...? yg pointing check not working...?
- 
-**From Handover Notes** 
- 
- 
-====== aua081 ====== 
- 
- 
- 
-**Hobart 12m** 
- 
-Disk VSN: flexbuf-2hb  
- 
-   * Samplers continually bad (prad) 
-   * 2200 UT power cylced dbbc3hb and reconfigured (warren) 
-   * 2307 UT schedule resumed (w) 
-   * 0116 UT restart and reconfigure dbbc3hb (warren) 
-   * 0201 UT first recording with all four samplers good (w) 
-    
-**Katherine 12m** 
- 
-Disk VSN: flexbuffke 
- 
-   * Samplers continually bad 
-   * 1922UT recording started 
-   * 2145 UT looks like dbbc3 crashed (warren) 
-   * 2250 UT power cycled dbbc3, reconfigure (w) 
-   * 2300 UT no recordings found  on flexbuffke (w) 
-   * 2333 UT schedule resumed, first recording 2333  (w) 
-   * 1206UT dbbc3 samplers all bad, halt and reconfigure (Lim) 
-   * 1228UT good samplers, but data contain integer offsets, run setupaum a few times. schedule continued on scan 300-1245 (Lim) 
-   * 1324UT connection to dbbc3ke dropped, couldn't bring it back from pdu2ke even though status was "On". [errors ignored by the log monitor?] (Lim) 
-   * 1620UT still no connection to the dbbc3, likely going to miss all scans after 1324UT. From vbs_ls I see we only started record since 0900UT and recorded only 4.5 hours of data? (Lim) 
-    
- 
-**Yarragadee 12m** 
- 
-Disk VSN: BKG-0049/2000/1024 and HOB+0055/8000 | Data volume at beginning:  909.48 GB and 0.00 GB 
- 
-   * 1730UT Experiment started okay (Prad) 
-   * 1843 UT no more disk space. Modules swapped by yg operator then mk5 crashed  (warren) 
-   * 2143 UT restarted mk5 first good recording 2143 (w) 
- 
- 
- 
-====== AUM040 ====== 
- 
-**Hobart 12m** 
- 
-Disk VSN: flexbuf-2hb  
- 
-   * 1800UT Experiment start ok (Jay) 
-   * 2014UT one of dbbc pps_delay went bad. Power cycling dbbc3. Schedule resumed at 2042UT. power cycling didn't change anything on pps_delay (Jay). 
-   * 1045UT Dbbc3 delay corr went  bad. Power cycled dbbc3 at 1152UT. Schedule resumed at 1224UT  (Jay) 
- 
- 
-**Katherine 12m** 
- 
-Disk VSN: flexbuffke 
- 
-   * 1800UT Experiment start ok (Jay) 
-   * 1829UT all delay corr went bad. halted schedule & Power cycled dbbc3. Schedule resumed at 1910UT  (Jay) 
-   * 0320UT same thing happened again. all delay corr went bad. halted schedule & Power cycled dbbc3. Schedule resumed at 0400UT  (Jay) 
-   *1520UT happened again. all delay corr went bad. halted schedule & Power cycled dbbc3. Schedule resumed at 1555UT  (Jay) 
  
 Jay to Jamie: In regards to aum, power cycling dbbc, delay bad, unstable a recurrent issue.  Jay to Jamie: In regards to aum, power cycling dbbc, delay bad, unstable a recurrent issue.