This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
operations:agenda2016_04_21 [2016/04/20 12:26] Ellen Manning |
operations:agenda2016_04_21 [2016/04/20 21:58] Ellen Manning |
||
---|---|---|---|
Line 8: | Line 8: | ||
Current Issues | Current Issues | ||
+ | |||
+ | * Drives broken on 26m, cancelled today's experiment (RD1603). | ||
* New PCFS at Hobart (thanks Jamie) | * New PCFS at Hobart (thanks Jamie) | ||
- | - | + | |
- | * Maser maintanence at both Katherine and Yarragadee currently, hence Brett is not at the Observatory. Warren is at Mt Pleasant Tuesdays to Thursdays and occasionally Mondays. | + | * Maser maintenance at both Katherine and Yarragadee currently, hence Brett is not at the Observatory. Warren is at Mt Pleasant Tuesdays to Thursdays and occasionally Mondays. |
- | - | + | |
- | * R4734 - Yarragadee: consistent offset between mark 5 and other computers of 0.1 - 0.4 visible in fmset, could not be fixed. Caused by power failure affecting GPS receiver (new UPS installed) - had to change to Hobart's. Fixed itself 4+ hours later. | + | * CRDS82 - "still getting ve error: ERROR ch -308 ve total power integrator overflow" - what was this and was it fixed Bryn? |
- | - | + | |
+ | * R4734 - Yarragadee: consistent offset between mark 5 and other computers of 0.1 - 0.4 visible in fmset with no sync error, could not be fixed. Caused by power failure affecting GPS receiver (new UPS installed) - had to change to Hobart's. Fixed itself 4+ hours later. Is there any way to fix this other than hope? | ||
* R1735 - A couple of instances where recorder started ~ 7-10 seconds before onsource at both Katherine and Yarragadee. | * R1735 - A couple of instances where recorder started ~ 7-10 seconds before onsource at both Katherine and Yarragadee. | ||
- | - | + | |
- | * R1735 - Hobart e-remote froze, required hard reset of PCFS | + | * High system temperatures - run systemp12 again to make sure it wasn't just one dodgy reading. Monitor make note of how many scans were affected by high tsys values. |
- | - | + | |
+ | * Anything else to note? |