This wiki is not maintained! Do not use this when setting up AuScope experiments!

Sep 01, 2300UT

Any additions, changes?

Agenda:

First items:

1. New issues from Warkworth

2. New issues from AuScope

3. Phase-cal measurements At AuScope (Brian)

4. Clock jumps

Any Maser comparison data showing jumps?

Most recent experiment analyzed was r1700 (Aug 11), which is not recent enough for cross check

Analysts back down a bit on how much data is being lost, but still adds significant extra work

5. Auto-stow tests

“Synopsis” of tests, redo at least Jim's test 1

New (not discussed before):

6. Katherine has completed aov004

DBBC unstabled — several clock drifts

7. Did Hobart observe AOV004?

8. Yarragadee has completed r4702

1905 UT: Windstow activated. Appears to be a misread on windy the anemom (wind speed 9999 km/h). Reset the windyg box to bring the average windspeed back down. Misreads continued. Did cold reset on windyg. Still the occasional misread. Could be on the anemometer end (An insect on the ultrasound transducers?)

9. Kath12 R4701

ACU time difference outside limits requiring use of fmset Missed Scans 233-1048b to 233-1051c. FS reported clock error at 1050Z. Session started at 1830z. -ACU Clock jump or drift was 16 hours after session started.

Ed: FMSET won't help this problem, formatter and FS and computer agreed, NTP configuration issue? First error 10:48:58, last at 10:51:27, about 2:30 seconds, SNTP updates are at 30 second intervals. Problem cleared on its own, 10 seconds after 5B time reset

10. Wark12m : Registers Master Status

That's the way I read it also. When its windy we see the HMI interface the “POS ERROR” fields go red as the error is > 1/10000 of a degree. So the current position goes red also as technically its not “on source”, but the error might be of the order 6/10000 of a degree ( ~2' ) so still well within the FWHM of the beam even at X-Band. The current “antcn” code is if the current posn is > 1/1000 degree from the commanded position or the AzMasterStatus or ElMasterStatus are not 0, then flag not tracking. I can “relax” these limits for being on-source. Just take “current posn” to “commanded posn” and ignore the Status registers (well still log them if not 0, but don't set the flag to be not tracking).

11. R4697 Ww

The overwhelming majority of scans have produced no fringes on WW baselines – the WW-KK baseline, for example is seeing ~1 scan with fringes per hour. On top of that, the SBD is varying wildly – a rare pair of two successful scans within 10minutes of each other on the WW-KK baseline jumped nearly 1us.

12. R1697, R4697, R1698 Ww

all have 1 second clock offset

13. no fringes for Wark12 AUA006 even when antenna was tracking.

14. R4701 cold weather trips motor. Session stopped, antenna moved up and down to warm oil, then session continued. (question - The antenna moving for three hours did not warm oil?)

Old

15. Warkworth GPIB controller progress?

16. AuScope NTP update

17. Hobart VC LO progress

Ed nudged Mike to look into it, has two to send, need to figure out shipping arrangements, probably between Brett and Don Sousa, Don is unavailable right now

18. Yg replaced ifpci server?