User Tools

Site Tools


operations:agenda2020_04_09

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

Next revision
Previous revision
operations:agenda2020_04_09 [2020/04/09 02:54]
Patrick Yates created
operations:agenda2020_04_09 [2020/04/09 03:34] (current)
Patrick Yates
Line 1: Line 1:
 **Chair:** Patrick **Chair:** Patrick
  
-** next week's chair: ** ?+** next week's chair: ** Katie
  
-**Attended:​** ​Patrick+**Attended:​** ​Mas, Earl, Tiege, Jamie, Katie, Prad, Eloise
  
 **Apologies:​** ​ **Apologies:​** ​
Line 10: Line 10:
  
 **General Issues** **General Issues**
-    * When do observations start in the New Year+    * Remote observing: anyone tried it? comments, questions, tips
-      * **First session 2nd January (R4)** +      * Seems to work well. 
-      * Additional sessions (not regular IVS) will be added in +      ​Still access card only after Easter, but UTAS is strongly discouraging people to be on campus. Might change. 
-    * Warkworth will join a series ​of new AUSTRAL experiments next year (30-40) +      ​Some problems with network access. Waiting on IT department for support for this. 
-    * First 2020 meeting: **16th January** +      ​There are notes for using SSH gateway as an alternative to VPN. Linked off remote observing page, walks through setting up an SSH tunnel. 
-      * If there are problems in last 2 weeks of 2019contact Jamie/Warren+    ​checkmk5 procedure missing from proc files? 
 +      * Jamie will look into slogit & see if it's a simple fix. 
 +    * Mixed mode updates? 
 +      * Observing procedure same as before. Still configuring & monitoring outside field system. 
 +      * Future version ​of FS will be able to do everything itself. 
 +    * Fibre works on Mon/Tues 
 +      * Took out wiki, since been repaired. Shouldn'​t recur 
 +    * ops-serv2 was left off after power works 2 weeks ago. 
 +    * **Ho drives:** 
 +      ​One of the drives can struggle to start. Motor encoder, affecting Y2 drive. 
 +      ​Might need to start drives (using vdesk), then let it sit for a bit before moving it. 
 +      * Can see this looking at camera. Y2 drive current meter doesn'​t move. 
 +      * If it still doesn'​t workthis is a job for Brett or Warren 
 +      * Eric will probably need to replace motor encoder.
  
 **Handover Issues** **Handover Issues**
-   ​* ​AUA058 +   ​* ​AUA063 
-      Experiment started late due to disagreement between IVS schedule & observer roster +     ​* **Yg:** Started ​on flexbuffygswitched to mk5yg later 
-        ​AUA scheduled at a weird hour +       * fs machine was unbootable day before, couldn'​t ​fix it
-        ​Double check IVS schedule and AuScope schedule (**might happen more often**) +       ​ran using a script outside ​the field systembit of a kludge 
- +       * had mk5 or module issue, possibly an issue with the mk5 iteslfAlternative recording system is using dbbc + flexbuff. Might need to switch to this
-   * AOV042 +   ​R1941 
-      * **Ho:** Started ​latedrives weren'​t ​turning on. Fixed on its own after ~10 minutes+     * **Yg:** pcfs froze, needed restarting 
-        Brett has worked on drives. One of the drives was not responding quick enoughshould be fixedNeed to keep trying till it works+       ​* pcfs machine is getting oldreplacement machine is being configured onsite, will switch over at some point
-      * **Ho:** PCFS crashed. Restarted and received ''​Allocating memory for antenna monitoring''​ error. Fixed with a reboot of drive pc and pcfs +   ​* ​APSG46 
-        Fixed by killing all vdesk connections,​ then rebooting drive pc and pcfs if problem persists +     ​* **Ho:**  
-      * **Ho:** PCFS locked upRestarted vdesk. +       ​wrong receiver on axis. 
-        * Same problem as above +       ​Mk5 module write protect error 
-   ​* ​AUA059 +         Module was used in Tidbinbilla (modified mk5C). Causes issues if it's not erased before recording. Can't add to the module. 
-      * **Ho:​** ​RXP network connection down +         Possibly not an issue with jive5ab, vsdimino 
-        Something to do with drive pc and RAKBUS +       ​Focus platform linear bearings came loose, needed fixing 
-      * **Ho:** PCFS crashed+         ​Have intercom to listen to cryogenics in focus cabin 
-   ​T2136 +         Heard clunking, paused observation to go up and fix it. 
-      * **Ho:** PCFS crashedRestarted and received ''​Allocating memory for antenna monitoring''​ errorFixed after rebooting ​drive pc (twice) with ''​rem_reboot -r rakbus ​sys26m''​ +         Daily check from Mt Pleasant is good. 
-      **Ho:** After drive reboot, receiver switched to Warm S-Band (on its own?)Experiment halted ​to investigate,​ Warren went up to receiver cabin and manually changed to S/X. Rebooted rx26m, still something wrong with rx comms+       * Received continuous errors "Allocating memory for antenna monitoring"Fix was rebooting sys26m. 
-        Related to power outage? +         ​Usually because ​drive pc has run out of monitoring pointsPossibly due to network issues
-   ​CRF115 +         ​Can often fix by terminating field system & restarting 
-      * **Ho:** S/X receiver in position, but in manual mode, display will be wrong. +         ​Check for any unnecessary ​spare vdesk sessions & close them 
-        In manual mode, live page & rxp should show correct readings most of the time, but OTTER won'​t. +         ​Guaranteed way to fix is rebooting sys26m, but this takes a while (~4 minutes)
-        * X,Y,Z should be correct ​(read off camera& reliable +
-        * On RXP display, number only matters if you're using the multifeed+
  
/home/www/auscope/opswiki/data/attic/operations/agenda2020_04_09.1586400892.txt.gz · Last modified: 2020/04/09 02:54 by Patrick Yates