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.
r1852
Katherine 12m
Disk VSN: HOB+0114/16000 | Data volume at the beginning: 4109.257 GB
- 17:00 UT - Experiment started OK (Ross).
- 07:00 UT - Warning: formatter to fs time difference 0.5 seconds or greater. Also, when running fmset, mk5 off by a sec. Jamie said not to sync.
Yarragadee 12m
Disk VSN: USN-0150/4000 | Data volume at the beginning: 0.0 GB
- 17:00 UT - Experiment started OK (Ross).
- 21:10 UT - Received the message “ERROR ib -4 GPIB Device time-out on response c1” after a clkoff, but worked second time as expected (Ross).
- 04:35 UT - mk5cn error - DIMino no longer responding. mk5-2yg still ok, logged in and rebooted. (JMc)
- 04:45 UT - mk5-2yg - persistentr 0.4 second offset, ntpdate unable to correct. Rebooting again. (JMc)
- 04:50 UT - ntpdate now works, offsets < 10 ms. (JMc)
- Scans missed between ~0435 and 0451. Good data again from scan 205-0453 (JMc)
R4851
Katherine 12m
Disk VSN: MPI-0153/2000| Data volume at the beginning: 0.0 GB
- 18:30 UT - Experiment started ok.
- 06:45 UT - FS has apparently “hung” after complaining about a disk2file command. No response to commands including “flush” “ti” “list” etc. Rebooting. (JMc)
- Scans missed 201-0639b, 201-0646 (JMc)
Yarragadee 12m
Disk VSN: NRAO-175/2400| Data volume at the beginning: 0.0 GB
- 18:30 UT - Experiment started ok.
R1851
- No sound on ops8 again :(
Katherine 12m
Disk VSN: IAA-0034 | Data volume at beginning: 2.821 GB
- 09:00UT - Autocorrelation spectra on test recording not looking good. Restarted DBBC program, DBBC computer, but no luck. Tried to restart mk5ke, but it wouldn't start up again after shutting down. Called Jamie, who said that it was likely the PCI7200 card in the DBBC had died, and needed replacing. Messaged Mick to see if he would go out and replace card, and take a look at mk5ke.
- 13:00UT - Mick went out to Ke. He diagnosed that mk5ke was not powering on at all, and tried another power cord, but no luck. Meanwhile, he swapped the module over to mk5-2ke, and I edited /usr2/control/mk5ad.ctl on pcfske to point the field system to mk5-2ke. Mick then replaced the card in the DBBC.
- 14:00UT - With replacement card in DBBC, and using mk5-2ke, I ran the test recording and autocorrelation spectra again. It looked better, but there were still some artifacts. I rebooted the DBBC to fix this, and Mick got mk5ke working again, so he swapped the module back and I fixed up the field system. Ran the test recording again, and now the autocorrelation spectra look normal.
- 17:00UT - Experiment started OK. (Patrick)
- 20:20UT - Mk5 time 1 second ahead of field system, halted schedule to fix with fmset, then resumed.
- Missed scans 198-0626 through 198-0637, 198-0644b OK
Yarragadee 12m
Disk VSN: BKG-0048 | Data volume at beginning: 0.288 GB
- 17:00UT- Experiment started OK. (Patrick)
R4850
Katherine 12m
Disk VSN: IAA-0064/2000| Data volume at beginning: 0.192 GB
- 18:30UT - Experiment started OK. (Tiege)
Yarragadee 12m
Disk VSN: PKS-0007/2000 | Data volume at beginning: 0.160 GB
- 18:30UT- Experiment started OK. (Tiege)
RD1805
Hobart 26m
Disk VSN: HOB+0119/32000/ | Data volume at beginning: 32159.422 GB
- 2018.192.18:00:00 Experiment started fine (Lucas).
- 2018.192.20:00:22.63 Module changed over to HOB+0117/32000/ (start position 30676.4 GB)
- First scan on module 192-2000 (Lucas)
- Drove out to Mt P and pumped steel I mean helium. I initially thought pressure/temp were stable and/or falling but they took a turn upwards above 100K and so needed refilling. While pump was on waited for temp < 100K and once it was I turned pump off and drove back. During drove temperature has fallen to 80K (Lucas).
- Also took out full module and inserted new 6000 GB module
APSG43
Hobart
Disk VSN: HOB+0117/32000/1024| Data volume at beginning: 25624 GB
18:00 UT Experiment started OK (Katie)
22:00 UT Field system crashed, but restarted fine.(Katie)
Katherine
Disk VSN: HOB+0041/6000 | Data volume at beginning: 0 GB
18:00 UT Experiment started OK (Katie)
Yarragadee
Disk VSN: HOB+1006/16000/1024 | Data volume at beginning: 0 GB
18:00 UT Experiment started OK (Katie)
