User Tools
Sidebar
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Handover notes
Please use this page to write up any notes on anything that needs to be passed on to the next observer or should go into the end of experiment message.
Notes should be placed below the horizontal line as a new blog entry.
Continuing problems should be copied to the Current Issues page.
**Template for Handover notes:**
Be sure to add any specific notes about the experiment if required, for example “Special back end configuration for x reason”. Put as much detail as you can - the more the better.
====== Experiment Name ====== **Hobart 12m** Disk VSN: abc-123 | Data volume at beginning: 2.34 GB * 1300UT a comment from me (user) **Katherine 12m** Disk VSN: | Data volume at beginning: GB * **Yarragadee 12m** Disk VSN: | Data volume at beginning: GB * 1300UT Experiment started okay (JMc).
Format for entering a comment It is important to stick to this formula - there is a good reason we need this information, so please include it!
Time stamp in UT * Comment * (Your Name)
For Example:
20:00UT: Wind stows, Missed scans 012-3456 to 012-3457 (Jim)
20:50UT: Mark5 lost connection, had to restart Mark5 and reconfigure DBBC, called Jamie on call to fix, missed scans 012-3456 to 012-4567 (Jim)
Again - as much detail as you can. It is important to remember that these notes will be sent to the correlator, so please make sure they make sense to others.
R1767
Hobart
Module: TR-00012, start pos 0.481 GB
- 1700UT - Experiment started OK. (Tiege)
Katherine
Module: GSFC+025, start pos 0.288 GB
- 1737UT - Experiment not started yet, originally delay as pcfske had to be power cycled and took a long time to come up. New issue is Antenna convinced it is stuck, despite everything on the system monitor and on timeke saying it is OK. Have tried all the usual field system commands as well as all the rests on timeke. (Tiege)
- 1759UT - Have tried restarting the FS now also, no dice, the telescope will slew to the new source, everything is displaying as green, however, the field system is displaying the 'Antenna stuck' message and hence the telescope wont record. (Tiege)
Yarragadee
Module: HAY-0049, start pos 0.288 GB
- 1700UT - Experiment started OK. (Tiege)
HOB008
Hobart 26m Disk VSN:HOB+0126
Data Volume at beginning: 7235 GB
- 2000UT Data not being recorded initially, reloaded schedule and procedure files (Ross)
- 0055 - Restarted DBBC Control program as clkoff/dbbc=pps_delay readings indicated a loss of synch. (JMc).
- Missed scans 324-0420, 324-0417 and 324-0422 due to 'previous source in the schedule not reached before new source was commanded …'. Alarm did not go off for this (Lucas)
- 0830UT - Disc pos ~200 GB behind, holding steady. (Ellen)
- 0845UT - Hg pressure still at about 4.0 (Lucas reported it had been a little high). Appears stable, probably just due to hot weather. Continuing to monitor. (Ellen)
- 0900UT - Hg pressure fallen down to 3.1 microns. (Ellen)
- 1040UT - Module filled up and automatically switched to recording onto HOB+0120, which already had 9901 GB on there. First scan on module was 324-1041. 2092 GB recorded to HOB+0029. (Ellen)
Hobart 12m
Disk VSN: HOB+0029
Data Volume at beginning: 3577 GB
- 1900UT Experiment started OK (Ross)
- 22:30 to 23:06UT, getting mk5cn time-out connection closed errors, restarted dimino and dbbc (and re-synced) but continued getting errors. Called on-call person, they recommended editing checkmk5 file in pfmed to exclude /sys/… command which produced autocorrelations by commenting out with “, but this didn't work either. Re-started schedule as the error was deemed to be benign. Alarm was commented out of alarm_control (Lucas/Ross)
- 0215 UT The diskpack that was being recorded to was marked as 'Faulty', and there was a lag between accepting a 'disk_record=off' command, which was longer than the 500ms window the fs allowed, thereby giving the mk5cn time-out error. Jamie was able to correct this and the alarm was un-commented. (Lucas/Jamie)
- 0830UT - Disc pos ~130 GB behind, holding steady. (Ellen)
- 1040UT - Module filled up and automatically switched to recording onto HOB+0120, which already had 9901 GB on there. First scan on module was 324-1041. 2092 GB recorded to HOB+0029. (Ellen)
r4766
Hobart 12m:
Disk VSN:HOB+0029
Data volume at beginning:1858.7
- 18:30UT Experiment started OK (Arwin)
- 09:22UT Alarm sounded WARNING: No PCFS activity for 307.0 minutes. Checked pcfs, all was running fine. Seems to be a noted current issue, when I acknowledged the alarm and reset watchdog, was fine. (Liz)
Katherine 12m:
Disk VSN:BKG-0026
Data volume at beginning:1032.6
- 18:30UT Experiment started OK (Arwin)
- 0030 Bank changed to avoid running out of space. (JMc)
- 0341 UT: Out of space on both modules at Katherine. Martin unable to access the site due to excavation work. Schedule halted. (JMc)
Yarragadee 12m:
Disk VSN:NYAL-025
Data volume at beginning:0.0
- 18:30UT Experiment started OK (Arwin)
- 10:05UT ALARM: error m5 -104 mk5cn: time-out, connection closed. Current scan on log monitor -ve GB? Watching it (Liz)
- 10:10UT next scan was normal again and total data recorded seemed fine so seemed benign (Liz)
OHG105
Hobart
Module: HOB+0120, start pos 8860.714 GB
- 1800UT - Experiment started ok.
- 1215UT - Windstow 12:15:25 to 12:20:39. Scans affected 322-1214 to 322-1218 (inclusive) (arwin)
Katherine
Module: OSOD-038, start pos 0 GB
- 1800UT - Experiment started ok.
Yarragadee
Control room camera was so bad I couldn't see the mk5 rack at all, let alone double check the modules. It was complete garbage below the top quarter of the feed. (Ellen)
Module: HOB+0043, start pos 963.443 GB
- 1800UT - Experiment started ok.
T2114
Hobart 12m
Disk vsn: HOB+0120 Start position: 7782 GBs
- Not using the allocated module USN-0097, as it is not loaded (JS)
- 1730UT Experiment started OK (JS)
- Total data recorded: 1078 GB
Katherine
Disk vsn: BKG-0026/1400 Start position: 0 GBs
- 1730UT Experiment started OK (JS)
- Total data recorded: 1032 GB
Yarragadee
Disk vsn: HOB+0043 Start position: 0 GBs
- 1730UT Experiment started OK (JS)
- 1:50 (321) UT data pointer lags expected by 1.5 GB (Warren)
- Total data recorded: 963 GB
R1766
Notes
eremote still doesn't appear to work on ops8 OR ops4, the backup control doesn't appear to connect either (I could be wrong, I'm not very familiar with it). So the current way to view/monitor the experiment is to have the VNC to the pcfs open and have the logs going. Then you ssh into the pcfs from ops8 and find the 'stream_log' script.
It is currently located in /home/observer/deh/opsutils/ so cd to that dir and type (e.g for hb):
./stream_log hb
This will begin streaming the log from pcfs to /tmp/hb.log. Then from the log monitor, start monitoring that file (/tmp/hb.log). Seems to be best to do a clkoff first.
Because e-remote control is not working, checklists are unavailable. Will be regularly running through the checklist points and noting anything out of the ordinary below.
Hobart 12m
Disk vsn: BKG+0142/4000 Start position: 3.269 GBs
- Autocorrelation spectrum at Hobart is a mess. Reconfigured dbbc and still no change. I'll see what happens after the experiment begins and if it fixes itself (Lucas). Update: after first scan it was fine. Must have been the bug in the plotting program.
- Experiment started ok (Lucas).
- 0042 - Ran fmset to correct jumps in reported pps_delay through the DBBC. (JMc)
Katherine
Disk vsn: HOB+0094/160000 Start position: 9051.643 GBs
- Getting error 'computer to acu time difference exceeded 0.25 seconds, see value above' every second. All the delays are fine and the beep is extremely annoying. Wiki says error is meaningless (probably network issues?) but I cannot turn the beep off (Lucas).
- Experiment started ok (Lucas).
- 2200 - Rebooted drives in HMI to clear the ACU time difference problem. (JMc)
Yarragadee
Disk vsn: HOB0104/16000 Start position: 7877.132 GBs
- Experiment started ok (Lucas).
- 05:34 Wind stow, missed scan 320-0535b (Bryn)
