User 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.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
operations:agenda2020_02_27 [2020/02/26 12:43] Simin Salarpour |
operations:agenda2020_02_27 [2020/02/26 13:03] Simin Salarpour |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| **General Issues** | **General Issues** | ||
| - | * | + | * Hobart 26m |
| + | * Problem with the brakes problem/a hydraulic fault alarm | ||
| **Handover Issues** | **Handover Issues** | ||
| * R4934 | * R4934 | ||
| - | * Yarragadee | + | * Yarragadee 12m |
| - | * Large difference between formatter and maser delays. Check for stability of new offset. | + | * Large difference between formatter and maser delays. Check for stability of new offset. error happens occasionally and clears itself (Lim) |
| - | Above error happens occasionally and clears itself (Lim) | + | |
| - | + | ||
| - | * AUA061 | + | |
| - | * Yarragadee | + | |
| - | * Very large positive(!?) data difference. +200TB or about 5%. Module is large enough to handle additional data (Lucas). | + | |
| + | * AUA061 | ||
| + | * Yarragadee 12m | ||
| + | * Very large positive data difference. +200TB or about 5%. Module is large enough to handle additional data (Lucas). | ||
| * 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) | + | * A series of clock-jumps on the dbbcho on the order of -0.015us. clkoff isn't actually indicative for dbbcho problems when hooked up to Hobart12m (Lucas). |
| - | a. Have 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) | + | * Katherine 12m |
| - | b. Jumped again at 8:00 UT, halted and reconfigured dbbcho. Missed scan 057-0821b, 0825. | + | * 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). |
| - | 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. 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. 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? | * 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? | ||
| - | * 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@flexbuffke. Then 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). | + | * 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@flexbuffke. Then 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/pages/operations/agenda2020_02_27.txt · Last modified: 2020/02/27 02:34 by Simin Salarpour
Page Tools
