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.
CRF98
Hobart
Disk VSN: HART-032
Volume at Beginning: 0GB
- 17:30UT Experiment started OK (Ross)
Katherine
Disk VSN: IPA-0028
Volume at Beginning: 0GB
- 17:30UT Experiment started OK (Ross)
Yarragadee
Disk VSN: BKG-0037
Volume at Beginning: 0GB
- 17:30UT Experiment started OK (Ross)
- 16:00UT Lost connection to yarragadee, network problem. Yg VPN needed a reset. (Arwin)
Hobart 26
disk HOB+0025
- 03:00 UT Just found out that Ho should also be observing. Apparently Warren did start it, though this was missed by AuScope observer. The schedule started late (6 hours late) due to changeover from astronomy schedule confusion. First full scan is 019-0017 at 00:17 UT. Additional problems due to wrong recorder specified in the schedule. Experiments seems to run fine, will send off start message now. (Lucia)
- 03:50UT Vacuum pressure is at 3.9 (should be <3.5). Told Brett and he will take care of it. (Lucia)
- 05:42UT Vacuum pressure was low (3.5) now is 3.9 again. Spoke to Brett. As long as the temperature (70k) is not rising, we are good. 70k stage has been stable at about 54K over the last two hours. (Lucia)
- 15:00UT Have been getting the following errors: “ ERROR ib -4 GPIB Device time-out on response ca” and “ERROR qy -1 Error in response from counter”. Consulted with Warren, he said not to worry about these. (Arwin)
R1775
Hobart
Disk VSN: UVLBI-06
Volume at Beginning: 0GB
- 1700UT Experiment started OK (JS)
- 2211UT Windstow activated (JS)
- 22:16UT ALARM Automatic wind stow activated
- 22:16UT Auto-stow released, 9 secs later.
Yarragadee
Disk VSN:WSRT-049
Volume at Beginning: 0GB
- 1700UT Experiment started OK (JS)
aov013
Hobart
Disk VSN: HAY-0041
Volume at Beginning: 0GB
- 16:30UT Experiment started OK (Bryn)
Katherine
Disk VSN: NOT-0001
Volume at Beginning: 0GB
- 16:30UT Experiment started OK (Bryn)
- 18:34UT ALARM: error m5 -900 can't xlrstop() (Bryn)
- 18:43UT ALARM: error m5 -900 can't get device info when trying to restart mk5 (Bryn)
- 18:46UT ERROR m5 -112 mk5cn: EOF pre-draining input, mark 5 may have crashed, connection close (Bryn)
- 18:46UT ERROR m5 -114 mk5cn: re-open after pre-drain error was okay, proceeding to transaction. (Bryn)
- 18:50UT rebooted mk5 machine (Bryn)
- 18:54UT ERROR m5 -105 mk5cn: error on read, see above for error, connection closed (Bryn)
- 18:55UT Can perform tasks on other disk in rack (i.e. mk5=dot?, disk_record=on, disk_record=off) (Bryn)
- 19:00UT continuing experiment, recording to HOB+0130. 67.291GB Recorded to NOT-0001. Data at beginning of recording to HOB+0130: 21616.9 GB First scan will be 016-1908b. Last scan on NOT-0001 is 016-1829 (Bryn)
Yarragadee
Disk VSN: HAY-0021
Volume at Beginning: 0GB
- Getting WARNING: error wx -8 met: can not get localhost information. (Bryn)
- 16:30UT Experiment started OK (Bryn)
mv005
Hobart
Recording to module HOB+012, start position 10751.511 GBs.
Katherine
Recording to module HOB+0130, start position 10941.927 GBs
Yarragadee
Recording to module HOB+0059, start position 0.00 GBs
- Station started late due to wrong module. First scan no0017, 2327-376
mv004
Hobart
Module HOB+0120, 0.00GBs.
- Many wind-stows:
- -00:27:29
- 00:34:01-00:39:26.15
Katherine
Module HOB+0130, recorded 1043.582 GBs previously.
- Power outage, antenna got stuck after the system recovered:
- halt
- disk_record=off
- antenna=off
- terminate
- in timeke, HMI, 'reset drives', wait until both comms stati are green
- fs
- proc=mv004ke
- setup01
- antenna=open
- antenna=operate
- source=stow
And it moved. Then I restarted the schedule. Generator status was 'in auto-off' so I assumed the power came on without any problems.
Yarragadee
Module HOB+0100, 0.00GBs
R4774
Hobart
Module USN-0014/Start 0.00 GB
- 18:32UT Experiment started late, first scan 012-1832 (Nick)
- 18:32UT Quite a few of the values on the system monitor are red, with drive status and drive control unknown (Nick)
- 18:45UT clkoff-maserdelay delay was excessively large (533072.774 us), reconfiguring the DBBC worked as explained at http://auscope.phys.utas.edu.au/opswiki/doku.php?id=operations:monitoring_hb#clkoff_reading_is_drifting_or_far_from_the_maser-gps_offset (Nick)
- Some wind stows. Check logs to note off source times. (Jim)
- 2017.013.06:14:55 ALARM: Large difference between formatter and maser delays. Check for stability of new offset. Reconfigured dbbc. This seemed to work. Hobart was wind-stowed anyway (Lucas)
- 10:30 UT Hobart recovered from 'wind stow'.
- Antenna probably hadn't been wind stowed actually for a while. I noticed the wind speed had dropped to 7.5km/h bu the antenna hadn't recovered.
- Anyway after a few resets of antenna, drives, reboots, system and no change I thought the monica data was wrong since the wind speed didn't change from 7.5km/h. This has worked for me in the past to I tried it first.
- Antenna started setting off alarms due to missed scans and started trying to record data whilst stowed. Never a good sign. Solution was to:
- halt
- disk-record=off
- antenna=off
- terminate fs
- restart
- antenna=open
- antenna=operate
- proc=r4774hb
- schedule=r4774
And it was away!
- First good scan after recovery 013-1039.
- IMPORTANT NOTE I skimmed the logs to see where it went wrong and I think the moment it buggered up was a note that said 'auto-stow recovery failed'. From then on it got stuck in a loop of trying to stow but never getting there. Maybe this should be an alarm??
- 14:30 Automatic wind stow. Released on it's own. 013-1451 first scan after release.
- 15:20 I think monica weather server isn't working, wind data hasn't updated for a while. I needed to go up to the telescope (to put in a mv004 module) and the wind was very clearly >7.7km/h (it nearly blew me over) that the monitor system showed (Lucas)
- 15:30 Auto-stow released, source 1144-379, but probably not for long (Lucas)
Katherine
Module NRAO-005 (960 GB)/Start at scan 013-0349 (711.5 GB offset) 711.50 GB
- 18:32UT Not running until maser has been fixed.
- 03:49UT Maser repaired, looks good. Data should be OK from scan 013-0349 onward (Jim)
Yarragadee
Module MPI-0413/Start 0.00 GB
- 18:32UT Experiment started late, first scan 012-1832 (Nick)
- 21:50UT Data is invalid prior to scan 012-2151c (was unable to communicate with the DBBC) (Nick)
