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.
T2127
NOTE: Schedule appears to have very long slews and dwells, so make timeout very long (25-30mins) to avoid spurious alarms about no FS activity.
Katherine 12m
Disk position at start 0.0 GBs VSN: HAY-0028/960
- Experiment started okay (Lucas).
- 23:25 UT and we have a lovely early one. DBBC began drifting. Halted schedule and reconfigured. Partially missed scan 247-2326 (Lucas).
- 05:30 Schedule halted to reconfigure DBBC after delay jump. (JMc)
- 06:00 Schedule halted to reconfigure DBBC after delay jump. (Lucas)
- 09:25:01 Schedule halted to reconfigure DBBC after delay jump. Possibly could have corrupted the 248-0924 scan and may have missed the 248-0951a (Prad).
Yarragadee 12m
Disk position at start 0.0 GBs VSN: BKG-0026/1480
- Experiment started okay (Lucas).
- 16:42 UT Problem with internet connection (unable to connect to VNC server). Had called Yarragadee on call person to stow the dish and reset the internet connection (mas)
R1858
Katherine 12m
Disk VSN: USN-0150/4000 | Data volume at beginning: 0.449 GB
VSN did not show up so I manually added it.
- 1700 UT - Experiment started OK (Tiege)
- 04:50 UT - Clock jump to 0.326 us (warren)
- 05:00 UT delay growing, dbbc reconfigure, scans affected 247-0449 to 247-0514 (w)
- 05:19 UT - 247-0519b next good scan (w)
- 05:45 UT - clock jump out to 0.32 us (w)
- 06:40 UT - delay out to 0.45 us (w)
- 06:45 UT - rebbot and reconfigure dbbc (w)
- 06:55 UT - back on schedule with scan 247-0655a (w)
- 08:07 UT - Drifting continues - so reconfigured dbbc (katie)
- 08:11 UT - Resume, scans missed 247 0847 - 247 0811b (katie)
- 09:10 UT - Drifting again - reconfiguring (katie)
- 09:13 UT - Resumed schedule (katie)
- 09:27 UT - Drifting again so rebooted this time. (katie)
- 09:43 UT - Resumed schedule (katie)
- 09:44 UT - FS crashed/then had to reconfigure dbbc again (katie)
- 10:24 UT - Schedule resumed. Scans missed 247 0909 - 247 1023 (katie)
- 10:55 UT - Need to reconfigure dbbc (Katie)
- 10:58 UT - Schedule resumed. Scans missed 247 1054 - 247 1057
- 11:28 UT - Need to reconfigure again (katie)
- 11:31 UT - Schedule resumed. Scans Missed 247 1127 - 247 247 1131
Yarragadee 12m
Disk VSN: USN-0049/4000 | Data volume at beginning: 0.449 GB
VSN did not show up, have confirmed above drive via webcam. Was not sure if it is OK to manually add VSN post test-recording?
- 1700 UT - Experiment started OK (Tiege)
aum007
Hobart 12m
Disk VSN: FLEXBUFF | Data volume at beginning: ? GB
- 1900UT Exp started OK. (Arwin)
- 1941UT dbbc25/ 2204.990000,c,32,1,agc,52,58,12938,17246,0,0 . The target value is not quite attained for this frequency (Arwin).
- 1941UT dbbcifa/1,0,agc,2,32595,48000,1. (Arwin)
- 1941UT PPS count is 47228, different from the wiki values (Arwin).
Katherine 12m
Disk VSN: HOB+1007| Data volume at beginning: 0 GB
- SAR Track at 243.2048 UT. Shortened Scans: 243-2044 and 243-2052, scans removed 243-2048. (Arwin)
- 1900UT Exp started OK. (Arwin)
- 09:06UT - Alarm has sounded for a delay drift (appears to have gone from a stable 0.32 us to 0.38. going to reset DBBC software now. (Tiege)
- 09:11 UT - Back up and running now 0.285 us delay, first good scan will be 244-0913 (Tiege)
- 09:35 UT - Has drifted again, did this the other day, Delay becomes unstable while transitioning from day to evening at Katherine. Going to restart the DBBC software again. (Tiege)
- 09:39 UT - Back on schedule, only missed 0937 and 0939, 0940 first scan back (Tiege)
- 1020 UT - Same issue again, restarted software again… mised 1020,1024 and 1027 missed (Tiege)
- 1110 UT - Has happened again, double checked I cant power cycle the mk5. It is still not working, just going to reset software again.. (Tiege)
- 1121 UT - Back up, missed scans 1114, 1117, 1118 and 1120 (Tiege)
- 1137 UT - fs has crashed, likely due to dbbc resync (happened a few experiments ago). Have restarted the field system, looks like no scans have happened since the last delay drift, so scans 1114-1138 were missed inclusive (Tiege)
- 14:33 UT ALARM: Delay through DBBC has changed. Monitor for stability and reset DBBC if it drifts. It seems it is stable now so no need to reset. (Simin)
- 15:23 UT drifts happened again. Have to reconfigure the dbbc. Affected scans: 244-1523 - 244-1542. (Simin)
- 16:02 UT Field system not running! try to restart pcfs. missed scan: 244-1602 - 244-1647. (Simin)
- 17:02 UT drifts happened again. Have to reconfigure the dbbc. Affected scans: 244-1701 - 244-1704. (Simin)
Yarragadee 12m
Disk VSN: GSSC+024 (VSN not showing)| Data volume at beginning: 0 GB
- SAR Track at 243.2142 UT. Scans removed 243-2139, 243-2140,243-2143. (Arwin)
- 1900UT Exp started OK. (Arwin)
R4857
Katherine 12m
Disk VSN: UVLBI-29/2000 | Data volume at beginning: 0.000 GB
- 1830UT Experiment started OK (mas).
- At 18:47 UT, need to reconfigure DBBC due to consistent “Alarm: Large difference between formatter and maser delays” (mas)
- Missed scans from 242-1847 till 242-1849b (mas)
- 08:53 UT DBBC drifting and not stabilising so had to reconfigure. (Katie)
- After 2 reconfigures and 1 reboot, dbbc is stable again (for now). (Katie)
- Missed/affected Scans: 243-0852 until 243-0906a. (katie)
Yarragadee 12m
Disk VSN: SHAO-023/2000| Data volume at beginning: 0.000 GB
- 1830UT Experiment started OK (mas).
R1857
Katherine 12m
Disk VSN: USN-0197/2000 | Data volume at beginning: 0.000 GB
- 1736UT - Experiment was delayed by around 36 minutes. The first scan was the 239-1736a. Issue was with the module. Preferably needs to be checked in prior to avoid such an issue in future (Prad).
- 2112UT - error m5 -104 mk5cn: time-out, connection closed. Recording started right after (Prad).
- 22:41:54 UT - WARNING: error ib -4 gpib device time-out on response c2 (Prad).
- 06:11 UT - pps_delay through DBBC dropping, DBBC shut down for a power cycle. ipske not toggling the power though. Contacted Mick to see about manually resetting (JMc)
- 06:33 UT - Rebooted, re-synched. Back on schedule by 0633. All scans between 0611 and 0633 not recorded (JMc).
- 07:32 UT - delay has been drifting since ~07:00, delay difference has increased from 0.290 to 0.310. Alarm set off after it broke the 0.31 threshold. Reset DBBC softwar, delay backlmat 0.29 us, will continue to monitor for drifting. (Tiege)
- 08:23 UT - Delay is still stable at ~0.29 us (Tiege)
- 10:26 UT - Delay keeps drifting, then stabilising for a short time before drifting again. Only thing I can do at the moment is restart the DBBC software and resync as the IP switch is down currently. Jamie seems to think it might stabilise as the evening gets cooler.
- 10:35 UT - FS crashed after dbbc reboot, restarted fs first scan back is 1038.
- 11:01 UT - delay has drifted again.. restarting and resyncing. Has gone back to 0.29 us. Missed scans are 1101 and 1108. (Tiege)
- 14:04 UT - Abnormal ammount of mk5 time-outs coming in waves, a couple of scans in a row trigger them and then it goes quiet for 30 mins or more, old fixes like antenna=open/operate aren't working, unsure whether it is worth rebooting the mk5 to try and fix this issue or not given how late into the experiment we are and the issues with the mk5 mean it could take a long time to come back online. All autocorrelations appear fine despite the errors. (Tiege)
Scans missed: 0611-0633 inclusive. 0747 and 0750. 1023 to 1035a inclusive. 1101 and 1108.
Note: data between 0630 and 0750 likely affected by clock drifting which occurred shortly after first DBBC reboot. Data from 0900-0925 and 1015-1023 also affected by delay drifting. Delays stable at other times.
Yarragadee 12m
Disk VSN: B UVLBI/2000 | Data volume at beginning: 0.000 GB
- 1700UT - Experiment started okay (Prad).
R4856
Katherine 12m
Disk VSN: USN-0173/2000 | Data volume at beginning: 0.000 GB
- 1830UT - Experiment started okay.
- WARNING: error ib -4 gpib device time-out on response c2 at 14:50:52, 17:29:48, 17:39:50, 18:10:22 and 18:17:57 UT (Prad).
Yarragadee 12m
Disk VSN: PKS-0007/2000 | Data volume at beginning: 0.000 GB
- 1830UT - Experiment started okay.
