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.
r1786
Hobart
Module: OSOD-351, start position 0.000 GBs
- Experiment started okay (Lucas).
- 10:17 UT module swapped over to HOB+1009 no problems. 2980.762 GB recorded. (Ellen)
Kath
Module: HOB+0034 (“StreamStor1” - label is different to VSN reading) 0.000 GBs
- Experiment started okay (Lucas).
- 18:40 UT, just noticed the maserdelay-clkoff (which was high during setup) has drifted over the last few hours (about 3.7 us!). I'm going to power cycle the dbbc (Lucas).
- 18:47 UT Clock difference back to within nominal range. Only had to restart DBBC software without full powercycle. Will monitor drift over next hour. Hopefully stable. Missed scans are 093-1839 to 093-1849 (Lucas).
- 06:50 UT Disc pos behind 32 GB presumably due to missed scans as described above (Ellen)
Yarragadee
Module: HOB+0021 start position 0.000 GBs
- 07:04 UT Disc position 22 GB behind where is it supposed to be. No indication why. (Ellen)
- 09:00 UT Disc position now 26 GB behind so Yg seems to be losing data at about 2 GB per hour. (Ellen)
R4785
Hobart 12m
Setting up: check on camera that module in Bank A is still not busy reading out, should be done by about 10UT (089) (Warren).
Disk VSN: JIVE-057/2000 (Bank B)
Data volume at beginning: 0 GB
- 18:30UT Experiment started okay (Liz).
Katherine 12m
Disk VSN:OSOD-114
Data volume at beginning: 0.418 GB
- 18:30UT Experiment started okay (Liz).
- 06:13UT - weather monitoring all seems to be completely broken (temp, pressure, humidity, wind) - checking local wind online. (Ellen)
- 09:36UT - Network quite slow, getting “WARNING: error st -27 computer acu time difference exceeded 0.25 seconds” on and off for a few minutes. Everything else is fine. Safe to ignore. (Ellen)
- 16:32UT - tsys values all quite high 120-150, no bad weather to cause this - monitoring
Yarragadee 12m
Disk VSN: USN-0080
Data volume at beginning: 0.418 GB
- 18:30UT Experiment started okay (Liz).
rd1704
Hobart 26m
Disk VSN: MED-0038
Data Volume at Beginning: 0 GB
- Wrong equip.ctl file was loaded to start, needed to fix.
- time-outs to vc rack when running setup8f, required manual power cycle at Mt. P + reset of tty distributor (middle left of VC rack). (Bryn)
- Fixed red lights on first VC of third row with vc15=200,2 (LO Lock light) and vc15=alarm (alarm light).
- 18:48UT Experiment started late due to issues with formatter time, field system time and Mark IV rack. First scan 088-1855 (Bryn)
- Disk offset (due to late start) is 124 GB
r1785
HB
Disk FGI-0004/
Start position 0.000 GBs
- Antenna was wind stowed at beginning of experiment. However it continued recording whilst wind stowed. Antenna was halted and disk_record=off. Wind speed was reported as 98km/s which seems unlikely, BOM reports that is should be >20. Looks like the system has bugged out. I restarted monica. The anemonitor in timehb doesn't seem to have connected and the HMI window has 'high wind alarm signal recieved'. Maybe BOM is wrong and there really is 98 km/h wind? I'll monitor and see if the level drops (Lucas)
- 21:39 UT wind sensor locked up, high reading; restarted wind sensor, all OK now, first scan 086-2145a (Warren)
- 03:00 UT multiple wind stows. Jamie fixed the anemometer. (Lucia)
KE
Disk UVLBI-06/
Start position 0.000 GBs
- Experiment started okay (Lucas).
YG
Disk HAY-0062/
Start position 86.7786 GBs
- Experiment started okay (Lucas).
aov014
Hobart 12m:
Disk VSN: HOB+115
Data volume at beginning: 1690 GB
- 17:30UT Experiment started OK. (Arwin)
Katherine 12m:
Disk VSN: BKG-0015
Data volume at beginning: 0 GB
- 17:30UT Experiment started OK. (Arwin)
Yarragadee 12m:
Disk VSN: GSFC+015
Data volume at beginning: 6400 GB
- 17:30UT Experiment started OK. (Arwin)
R1784
Hobart
Disk VSN: CURT+102
Data Volume at Beginning: 1856.245 GB
- 1700 UT Experiment started OK (Tiege)
Katherine
Disk VSN: USN-0014
Data Volume at Beginning: 630.062 GB
- 1700 UT Experiment started into rfpcn time-out error, Rxmon restarted. first good scan will be 079-1706a on source 0919-260 (Tiege)
- 0150 - 0535 No useful data recorded due to power outage at Katherine. Control and schedule resumed with first useful data at 0535 (JMc).
- The original power outage flattened the CMOS battery, requiring the hwclock procedure to correct it (JMc).
- After rebooting, the machine apparently stayed off the network for about an hour. It was firstthought that this was due to the fsck check of the drives, but was actually a network problem. The symptoms were a lack of access via ping, ssh or VNC when attempting to connect from either the campus machines (ops8) or Mt. Pleasant. pings and ssh connections from mk5ke were fine though. Problem finally resolved with a reboot of pcfske, after logging in through mk5ke (JMc)
Yarragadee
Disk VSN: USN-0097
Data Volume at Beginning: 0.000 GB
- 1700UT Experiment started OK (Tiege)
- 0700UT Alarm cannot connect to pcfs, check vnc. Fs still running but with error along the lines of “wrong length written, file probably too large can't write to disk.” Fixed as per wiki by 07:08UT
