Please use the Transfers Page for information on data transfer.
See the Modules Page
Please enter any significant events related to the AuScope VLBI project, including observations, configuration changes, hardware upgrades etc.
Following pointing observations by Jamie over the weekend, a new model has been calculated. RMS in xEl is 10 mdeg, in El it's 15 mdeg.
New solutions loaded at 03:30 UT.
Prior to r1478, observed 1921-293 at X-band, (az,el) = (-92.95, 43.40).
Offsets were:
xEl = -0.015 El = -0.01
New pointing solutions have been installed:
P1 = -0.0058 P2 = 0 P3 = 0.0142 P4 = 0.0114 P5 = -0.0081 P7 = 0 P8 = -0.0265 P9 = -0.001
and drive offsets (20.21 in az and el) set to 0.1141 deg and -3.5933 deg respectively.
Running in velocity mode we hit the hard limit before the soft limit
Further observing and debugging showed the encoder offsets were inserted with the wrong sign! Fixing this remedied the elevation limit problem but the Az hard limits were moved out slightly to give +/- 270 deg movement.
Some piggy-backed data collected during r4477.
Before r1476, pointing check on 1921-293 (az,el = -82, 54). Offsets:
xEl = 0 deg
El = -0.01 deg
No need to update model
During the R1474 observations on the 16th March 2011 a problem was encountered. The autocorrelation plot looked like the one in the example that can usually be safely ignored see (here). This was misinterpreted by the observer as an issue with the dbbc. Further investigation showed dimino to not be running. A restart of dimino did nothing to improve the situation. Furthermore there were then errors reported on pmstalmhb to do with being unable to contact the mk5.
The dbbc was re-setup at which time the autocorrelation display appeared normal. However observer error meant the wrong line number was given and the 12m went slewing off through a whole bunch of sources. The schedule was halted and resumed at the correct line number but now Mk5 connection issues re-emerged. A final restart of dimino fixed the issues.
After this systemp12 would no longer run, complaining about an error with the ./readpower.sh script. There were also multiple “formatter is offset from the FS time” and “warning onsource status is slewing” errors during this run.