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.
The PCFS Log monitor now checks the Field System log to see when the last entry was. If it's more than 15 mins ago it will ring a beep every 2 seconds as this is a possible sign that the Field System software has dies or that the network has dropped out.
Also removed the check to see if time had gone backwards. This check was buggy and doesn't seem to actually trap a real problem.
MK5-2ke shows a stuck bit in channel 15. First noticed 22 May and may have been persistent throughout CONT14. Autocorrelations show this in 1-bit data but not 2-bit.
Removing connector at mk5 end, cleaning and re-seating didn't fix the problem. Continuing to investigate..
The Hobart26 has a problem with the Y-bearing which makes observing in windy conditions hazardous. In addition, its wind sensor seems to be underestimating the current windspeed. To work around these problems, two scripts are running on hobart (WindLog.sh & WindStow.sh) to log the windspeed readings from the Hobart12 wind sensor, and to stow the dish when a windspeed > 35 km/h is detected.
WindStow.sh will halt the schedule and any current recording, stow the dish and put a comment in the log when a windstow condition is detected. It will stay stowed until the windspeed is <30 km/h for 30 consecutive minutes. Once it's out of windstow, it will restart the schedule (with “schedule=…”) and put a comment in the log.
Please make sure both of the Windlog.sh and WindStow.sh processes are running on hobart when taking over from the previous observer!
Note to observers Can anyone doing an expt changeover PLEASE record the disk pos at expt start on the paper schedule, so that we can properly and easily check disk usage? -Claire
Ke:
Mark 5 Crash at Katherine
At ~17:40UT (03:40am local), the Mark 5 at Katherine crashed.
Could not restart remotely as the power failed, all lights were off. Martin went to the telescope and had to reboot the Mark5 several times (as in pull the plug) before it would completely restart and begin working again. Had to fmset as everything was then out of sync.
Mark5 began recording again at 18:58UT (04:58am local).
Missed scans from 130-1737 through to 130-1854a (possibly one or two either side), have noted this in the Checklist. - Imogen
Ho: