User Tools

Site Tools


operations:agenda2019_05_30

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:agenda2019_05_30 [2019/06/13 01:46]
Md. Momtazur Rahman
operations:agenda2019_05_30 [2019/06/13 04:44] (current)
Md. Momtazur Rahman
Line 1: Line 1:
 **Chair:** Momtaz **Chair:** Momtaz
  
-**Attended:​**  ​+**Attended:​**  ​Earl, Mas, Lucas, Lim, Prad, Patrick,​Tiege,​ Simin, Gabor, Katie, Ross 
  
-**Apologies:​** ​+**Apologies:​** ​Jay
  
 **Absent:​**  ​ **Absent:​**  ​
Line 10: Line 10:
 **General Issues** **General Issues**
  
-    * Please remember to send log information+    * Please remember to send end and start message and log file
-    * FS crashed for a couple of experiments.+    * FS crashed for a couple of experiments- David Hosley was looking into the problem and would be updated the Field System as well! 
 +  ​
    
- 
 **Handover Issues** **Handover Issues**
  
Line 20: Line 20:
  
  ​**Katherine 12m**  ​**Katherine 12m**
-   * **Alarm scan check reports Mark5 data format problem** (indicated by the letter "​E"​ at the end of the line)(mas) +   * **Alarm scan check reports Mark5 data format problem** (indicated by the letter "​E"​ at the end of the line)(mas)-It appears only once, so keep on eye if it pops up again. ​
- +
-**Yarragadee 12m**  +
-   * Excluded due to technical problem+
  
  
 R1897: R1897:
  
- ​**Katherine 12m** 
- 
-  * **Proc file does not seem to have been generated properly**, this is causing issues noticeable in the test recording (Tiege). 
-  * Proc issue due to a typo in skedf.ctl (DNNC rather than DBBC). skedf.ctl may not be applied until after a restart of the FS. (JMc) 
  
 **Yarragadee 12m** **Yarragadee 12m**
  
-  * I encountered the error **TPI Overflow**. This froze up the pointing check, not letting it progress any further. It was fixed by again restarting and resyncing the DBBC software. ​Not sure if just a one off quirk, but noting it down just in-case. This was all prior to schedule start so no data is affected (Tiege). +  * I encountered the error TPI Overflow.This froze up the pointing check, not letting it progress any further ​- Tiege managed to solve the problem ​by restarting and resyncing the DBBC software.
-    +
-  * Also, **drive information on system monitor for Yg seems to be completely broken**. The message box is showing many Monica issues. Have tried restarting both Rxmon and Monica as a whole. This has not fixed it. Telescope appears to be working correctly, I may just need to restart a specific part of Monica that I do not know (Tiege). +
-  * Drive info restored after restarting the antmon program [''/​etc/​init.dMonica.antmon stop && /​etc/​init.dMonica.antmon start''​ as root] (JMc).  +
- +
  
 OHG119: ​ OHG119: ​
Line 46: Line 34:
 **Hobart 26m** **Hobart 26m**
  
-   * **Experiment started one scan late due to drive issues**(Lucas). +   * Schedule was put on halt because of bad wind condition. Will put it back on schedule when wind problem solves out?(Jay)-Lucas refer to the Newsmerd: winlog and winstow.
-   * **Drives crashed**. Diagnostic: persistent missed scan alarms and #antcn# alarms (including cannot allocate memory). Fix appears to be "​rem_reboot -r rakbus sys26m",​ ping sys26m until it comes back up then resume schedule. This also requires that you "sudo /​etc/​init.d/​sqlmonitor restart"​. All on newsmerd (Lucas) +
-   * **Terminated FS @ 0244 to fix GPIB comms issue**. Restarted ~0400 (JMc) +
-   * **Schedule was put on halt because of bad wind condition**. Will put it back on schedule when wind problem solves out?(Jay) +
-  +
- +
-**Yarragadee 12m** +
-   * **Windstow** at Yarragdee (JMc) +
-   * **rfpic not answering**. disabled in preob to avoid timeout delays (JMc).+
  
  
Line 61: Line 41:
 **Yarragadee 12m** **Yarragadee 12m**
  
-  *ALARM: Automatic wind stow activated, due to heavy rain and wind (Momtaz). +  * **False wind stow alarm from log monitor**(Warren)-Need to ask Warren ​as it appears only once.
-  *23:​38UT ​**False wind stow alarm from log monitor** as it first opened log file-"​2019.157.23:​38:​41. ALARM Automatic wind stow activated"​ this line not found in log file(Warren)+
  
  
Line 68: Line 47:
  
 **Katherine 12m** **Katherine 12m**
-  ​* **Tsys negative values** (~-200 to ~-100)? (Lim). +  * Tsys negative values(~-200 to ~-100)? (Lim)- Need to ask Jamie for further instructions
-  ​* **ALARM: error m5 -104 mk5cn: time-out, connection closed**. Failed to open terminal from within the pcfs(Lim). +  * ALARM: error m5 -104 mk5cn: time-out, connection closed. Failed to open terminal from within the pcfs(Lim)-Need to ask Jamie for further instructions
-  ​* **Can't open display in pcfske**: “Client is not authorized to connect to Servergv” and “Client is not authorized to connect to serverxterm Xt” (Lim). +  * Can't open display in pcfske: “Client is not authorized to connect to Servergv”(Lim)- Check mk5 
-  ​* **ALARM: error m5 -900 : not while recording or playing**(Jay).+  * ALARM: error m5 -900 : not while recording or playing(Jay)- Jamie will look into this problem.
  
 **Yarragadee 12m** **Yarragadee 12m**
-  * Received consistent error '​**error being ignored: error sp -4 unrecognized name (not a function or procedure) after each scan**'​(mas)+  * Received consistent error '​**error being ignored: error sp -4 unrecognized name (not a function or procedure) after each scan**'​(mas)- Mas has already informed to Warren to look into this problem.
/home/www/auscope/opswiki/data/attic/operations/agenda2019_05_30.1560390395.txt.gz · Last modified: 2019/06/13 01:46 by Md. Momtazur Rahman