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.
R4898
Katherine 12m
Disk VSN: | Data volume at beginning: GB
- Experiment started okay. (Earl)
- Mk5 required reboot (Xlr session error…)
- 2019.164.21:28:30 ALARM: error m5 -900 : no disks available
- 23:20 - Rebooted mk5ke (record pointer not incrementing error) [JMc]
- 23:24 - Schedule resumed. (JMc)
- data between 21:28 and 23:24 dubious.
- 2130 - Notes that the caltsys readings are all negative, though apparently correct in magnitude. Possibily a config issue (JMc)
Yarragadee 12m
Disk VSN: | Data volume at beginning: GB
- Experiment started okay (Earl)
- Mk5 required reboot (Xlr session error…)
- 23:30. mk5yg has an (+1) intger second offset in the data, leading to repeated setcl errors. This will need to be accounted for in correlation (JMc)
R1898
Katherine 12m
Disk VSN: HAY-0047 | Data volume at beginning: 0.705 GB
- 1700 experiment started OK (mas)
- Tsys negative values (~-200 to ~-100)? (Lim)
- 0742 UT - “No space left on device”. Warren deleted some old files on pcfske. Experiment resumed at 0818 UT. Missed scans: 163-0742a, 163-0747a, 163-0749, 163-0755, 163-0759 (Lim)
- 09:31 UT - ALARM: error m5 -104 mk5cn: time-out, connection closed. Failed to open terminal from within the pcfs. mk5 records normally, auto-correlation still updates on spectra.php, get_stats OK (Lim).
- 09:31 UT - Can't open display in pcfske: “Client is not authorized to connect to Servergv” and “Client is not authorized to connect to serverxterm Xt” (Lim).
- 1619UT ALARM: error m5 -900 : not while recording or playing. Everything was fine. Didn't know what caused it. Searched on wiki about it and saw that it can be ignored. Any theories, Jamie?? (Jay)
Yarragadee 12m
Disk VSN: USN-0150 | Data volume at beginning: 0.769 GB
- 1700 experiment started OK (mas)
- received consistent error “error being ignored: error sp -4 unrecognized name (not a function or procedure) after each scan. Have informed Warren (mas)
R4897
Katherine 12m
Disk VSN: WSRT-033 | Data volume at beginning: 1.218 GB
- 18.30UT Experiment started okay (Momtaz).
Yarragadee 12m
Disk VSN: TR-00011 | Data volume at beginning: 3.077 GB
- 18.30UT Experiment started okay (Momtaz).
- 21.26UT ALARM: Automatic wind stow activated, due to heavy rain and wind (Momtaz).
- 21.36UT Auto-stow released. Scans effected: 157-2129 and 157-2132a (Momtaz).
- 21.38UT ALARM:Automatic wind stow activated, due to heavy rain and wind (Momtaz).
- 22.01UT Auto-stow released. Scans effected: 157-2139,157-2149a and 157-2151(Momtaz).
- 21.04UT ALARM:Automatic wind stow activated, due to heavy rain and wind (Momtaz).
- 22.11UT Auto-stow released. Scans effected: 157-2107a and 157-2111b (Momtaz).
- 23:38UT False wind stow alarm from log monitor as it first opened log file-“2019.157.23:38:41 ALARM Automatic wind stow activated” this line not found in log file (Warren)
OHG119
Hobart 26m
Disk VSN: abc-123 | Data volume at beginning: 16213.42 GB
- 1830UT experiment started one scan late due to drive issues. First scan 155-1732 (missed scan 155-1730b).
- 2050UT drives crashed. Diagnostic: persistent missed scan alarms and #antcn# alarms (including cannot allocate memory). Fix appears to be “rem_reboot -r rakbus sys26m”, ping sys26m until it comes back up then resume schedule. This also requires that you “sudo /etc/init.d/sqlmonitor restart”. All on newsmerd (Lucas)
- Windstowed from 2253→0422 (JMc)
- Terminated FS @ 0244 to fix GPIB comms issue. Restarted ~0400 (JMc)
- No useful data 2253-0423 (JMc)
- Windstowed 0518→ (JMc)
- 0714UT Schedule was put on halt beacuse of bad wind condition. will put it back on schedule when wind problem solves out. (Jay)
- 1118UT Wind speed is now ok and stable. I have put telescope back on schedule. starting from scan 156-1124. (Jay)
Katherine 12m
Disk VSN: HAY-0062 | Data volume at beginning: 1958.74 GB
- 1830UT Experiment started okay (Lucas).
Yarragadee 12m
Disk VSN: BKG+0137/2000 | Data volume at beginning: 0.00 GB
- 1830UT Experiment started okay (Lucas).
- 0115 - 0121 - Windstow at Yarragdee (JMc)
- 0450 - rfpic not answering. disabled in preob to avoid timeout delays (JMc).
R1897
Katherine 12m
Disk VSN: HAY-0062 | Data volume at beginning: 1.571 GB
Proc file does not seem to have been generated properly, this is causing issues noticeable in the test recording. I am using the r1895ke proc file now instead. Please note this if you need to re-setup the experiment at some point. (Tiege)
→Proc issue due to a typo in skedf.ctl (DNNC rather than DBBC). skedf.ctl may not be applied until after a restart of the FS. (JMc)
- 1700UT - Experiment started OK (Tiege)
Yarragadee 12m
Disk VSN: HOB+0064 | Data volume at beginning: 1.699 GB
This setup happened after Jamie and Guifre were attempting top upgrade DBBC software. I closed the new DBBC software, opened the old, then restarted fs. Everything was fine (including test recording), however, while doing pointing check (after typing fivept) I encountered the error “TPI Overflow”. This froze up the pointing check, not letting it progress any further. It was fixed by again restarting and resyncing the DBBC software. Not sure if just a one off quirk, but noting it down just in-case. This was all prior to schedule start so no data is affected. (Tiege)
Also, drive information on system monitor for Yg seems to be completely broken. The message box is showing many Monica issues. Have tried restarting both Rxmon and Monica as a whole. This has not fixed it. Telescope appears to be working correctly, I may just need to restart a specific part of Monica that I do not know. (Tiege)
→Drive info restored after restarting the antmon program [/etc/init.dMonica.antmon stop && /etc/init.dMonica.antmon start as root] (JMc)
- 1700UT - Experiment started OK (Tiege)
R4896
Katherine 12m
Disk VSN: NRAO-108 | Data volume at beginning 0.449 GB
- 1830 UT Experiment started OK (mas)
- 2052 UT - FS crashed. Missed scans 150-2052 - 150-2126 (mas)
- 2135 UT - Alarm scan check reports Mark5 data format problem (indicated by the letter “E” at the end of the line).Module swap probably required. Occur during scan 150-2135 (mas)
- 0618 - FS terminated itself. Restarted @ 0633, first good data @0640. No useful data 0618-0640 (JMc)
Yarragadee 12m - excluded due to technical problem
