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.
R4727
Hobart
Module: USN+0220, start pos: 3773.4 GB
- 1830 UT Experiment started OK (Tiege)
- Ran out of disk space ~04:30. Both banks had full modules. Replaced and experiment restarted at ~04:57 (Stas).
- 2016.050.18:10:46 ALARM: Delay through DBBC has changed. Monitor for stability and reset DBBC if it drifts. (Jonathan)
Katherine
Module: OSOD-118 start pos: 0 GB
- 1830 UT Experiment started OK (Tiege)
- 1830 UT Module VSN not appearing in eRemoteCtrl window, however, storage remaining is still showing fine. this means an error is getting thrown occasionally stating that the VSN does not contain a + or a - in first seven characters.
Yarragadee
Module: MED-0015, start pos: 0 GB
- 1830 UT Experiment started OK (Tiege)
OHG102
Hobart
Module:USN+0220, start pos: 2625.458 GB
1800 UT - Experiment started ok. (Ellen)
- 0917 eremotecontrol retunred onsource as slewing twice before retuning tracking. This was followed with the following two errors (AK)
- error an -103 pointing computer tracking errors are too large.
- error qo -301 warning: onsource status is slewing!
- 0930 UT (approx) one of the Hobart s band sys temp spiked to about 3300 while another to about 1300, the relevant channel numbers were recorded in the checklist
Katherine
Module: USN-0137, start pos: 1666.807 GB
1800 UT - Experiment started ok. (Ellen)
- 0759 UT Katherine had the following error “error ib -4 gpib device time-out on response c2”. Wiki had instructions on “ERROR sp -4 GPIB Device time-out on response c2”. As per the wiki's suggestion, ran the “counter” command followed by the input of “maserdelay” and “clkoff” a few times. Everything seems okay (AK)
Yarragadee
Module: USN-0150, start pos: 2296.388 GB
1800 UT - Experiment started ok. (Ellen)
- Call station at the end of the experiment to change modules. (AK)
T2109
Hobart
Module: USN+0220, start pos: 1651.8 GB
- 1730 UT Experiment started OK (JS)
- 2120 UT S-band temps exceptionally high 363–400K for CH 09 – 12
- 2125 UT S-band temps stabilised (~130K)
- 0542 UT Hobart had the following two errors (AK)
- 05:42:28 WARNING: error an -103 pointing computer tracking errors are too large.
- 05:42:28 WARNING: error qo -301 warning: onsource status is slewing!
Katherine
Module: OSOD-118, start pos: 1634.1 GB (total 132.9 GB recorded here)
Module: USN-0137 start pos: 876.7 GB
- 1730 UT Experiment started OK (JS)
- 2042UT moved to module USN-0137 since there isn't enough room on the other module (JS)
- 0023 mark5 crashed, rebooted with Dave Horsley's help. Missed two scans (AK)
- 048-0023a 823 1954-388 154 62 CCW 00:23:02 00:29:51 6:49 283.0
- 048-0035 840 1424-418 230 24 CCW 00:35:10 00:37:05 1:55 289.5
- 0102 formatter to fs time difference was 2 secs, fixed using fmset when telescope was not recording, as per wiki guidelines (AK).
- 0331 UT Katherine threw two errors, consulted with Ellen Manning, errors are listed below (AK)
- 03:31:20 WARNING: error an -103 pointing computer tracking errors are too large.
- 03:31:20 WARNING: error qo -301 warning: onsource status is slewing!
- 0524 UT katherine threw the same two errors listed in the comment above (AK)
- mk5=dot? time was slightly high, approx 13 ms. Consulted with Jamie who suggested running “sy=run setcl offset & ” when no data is being recorded. Time was constant around 13 ms even after running the command (AK)
Yarragadee
Module: HAY-0028, start pos: 0 GB
- 1730 UT Experiment started OK (JS)
- 11:30UT: Yarragadee want to be called when experiment is finished (18:00) to change over modules (NH)
r1727
Hobart
Module: USN+0220, start pos: 0 GB
- 1700 UT Experiment started OK (Bryn)
Katherine
Module: OSOD-118, start pos: 0 GB
- 1700 UT Experiment started OK (Bryn)
- 0544 UT Katherine threw two errors, unable to find help on wiki, no more errors after this (Arwin)
- 0544 error an -103 pointing computer tracking errors are too large
- 0544 error qo -301 warning: onsource status is slewing
- 08:35 UT 2016.047.08:34:02 ALARM: Delay through DBBC has changed. Monitor for stability and reset DBBC if it drifts.
Yarragadee
Module: NRAO-143, start pos: 0 GB
- 1700 UT Experiment started OK (Bryn)
r4726
Hobart 12m
Module: HOB+0119, start pos: 4893 GB
- 18:33 UT - Experiment started 6 min late due to slow setup (Missed scans 042-1830b to 042-1836). (Bryn)
- 00:37 UT - the wind sensor in Ke is broken. Brett disconnected it last week, now it is sending a 'stow-command' in the System Monitor. This should be ignored and does not actually cause the antenna to stow. (Lucia)
- 14:10 UT Accidently cycled Hb DBBC instead of Ke.. scans affected: 043-1408, 043-1411, 043-1414, 043-1422, 043-1426a, 043-1433, 043-1434b, 043-1440b
- 14:30 UT DBBC timeout. Rebooted DBBC and ran fmset
- 14:55 UT restarted PCFS due to log monitor not displaying 'recording'
- 15:23 UT ALARM: Delay through DBBC has changed. Monitor for stability and reset DBBC if it drifts. Rebooted DBBC and reran fmset again
- 15:44 UT ALARM: Delay through DBBC has changed. & WARNING: Mark5 reports sync error. Recording seems to be OK, possibly due to break in schedule?
- 15:52 UT ALARM: Large difference between formatter and maser delays. & Still Mark5 sync error. Ran fmset to resync, syncerror_gt_3 is now syncerr_eq_0
- Restarted on scan 043-1608. Appears to be OK now. (missed 043-1448b, 043-1451, 043-1453a, 043-1456a, 043-1501, 043-1505, 043-1507, 043-1511b, 043-1517, 043-1523, 043-1531, 043-1534, 043-1538b, 043-1540, 043-1544b, 043-1551, 043-1555, 043-1604 due to halting the schedule to restart the dbbc, and due to mark5 sync errors)
Katherine 12m
Module: BKG+0135, start pos: 0 GB
- 18:33 UT - Experiment started 6 min late due to slow setup (Missed scans 042-1830b to 042-1836). (Bryn)
- 14:08:46 ALARM: Delay through DBBC has changed. Scan affected is 043-1408 (Jonathan)
- Again at 14:15. Rebooting DBBC
- 14:20 reconfigured DBBC: scans affected: 043-1408, 043-1411, 043-1414, 043-1422, 043-1426a, 043-1433, 043-1434b, 043-1440b
OHG101
Hobart 12m
Module: HOB+0119, start pos: 3813.9 GB
(From previous handover notes: No other module to record onto, R1726 first experiment on here.)
- 18:00 UT - Experiment started ok. (Tiege)
- Log monitor reporting negative disk usage for current scan at 042.01:13 UT. — Jim Lovell 2016/02/11 01:21
Katherine 12m
Module: USN-0137, start pos: 0 GB
- 18:00 UT - Experiment started ok. (Tiege)
Yarragadee 12m
Module: USN-0150, start pos: 1136 GB
- 18:00 UT - Experiment started ok. (Ellen)
