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.
gds01a
Ho
Module VSN (Bank B): HOB+0125. Data volume at start : 0 TB
03:16:07(145) UT. Drives turned off automatically just before recording started. Had to wake up drives and slew to source. Not on source until 03:18:00 (Warren)
06:46 (145) UT. Just realized time reported in e-control status monitor window has become incorrect, 1970.044.18.59, at 2016.145.06:46, fs time in log correct, mk5 time correct, drive pc (live page) time correct, all scheduled events occurring at correct times (Warren)
r4740
Hobart 12m
Disk VSN: HOB+0098
Data volume at beginning: 4384.176 GB
- 13:40UT - eremote control cannot be started, using pcfs vnc (Ross)
- 18:30UT - Experiment started OK (Ross)
rd1604
Hobart 26m**
Disk VSN: HOB+1008/16000/1024
Data volume at beginning: 13284.47gb
- 17:55 UT Experiment started late due to issues with startup and inexperience with setting up the 26m (first setup). First valid scan was 139-1803b , missed 5.1 gb of data (Arwin).
- 17:55 UT ERROR ch -302 v1 frequency does not check with requested value. This error only appeared once. (Arwin)
- 17:55 UT ERROR ch -308 ve total power integrator overflow. Consistently getting this error. (Arwin)
- 19:08 UT Data recorded is on par with the summary file. (Arwin)
- 00:58:47 UT (DOY 140) Wind stowed, schedule halted (Warren)
- 03:01:57 UT recording started, schedule resumed after wind stow (Warren)
- 07:54 UT in checklist disk_pos off by approx 29gb probably due to late start and earlier wind stow (Liz)
- 09:51 UT “ERROR ch -309 v6 alarm” is on occurred 8 times between 09:45:14 and 09:47:45. Could only find one other occurrence of this in the wiki from RD1411 in 2014. At that time it was stopped by “valarm” but it seems to have gone away on its own at this point. Doesn't seem like something anyone was particularly concerned about however, just in case, only scan affected would be 140-0946.(Liz)
- 11:00 UT “ERROR ch -309 v6 alarm is on” error x4 from 11:00:44 to 11:01:47 UT. Scans affected part of 140-1101b.(Liz)
- 12:07 UT “ERROR ch -309 v6 alarm is on” again x12 between 12:01:43 to 12:05:42. It seems to occur in periods. (Liz)
R1740
Hobart 12m:
17:00 UT: Experiment Started OK. Disk position 1799.86 GB at start. (Lucas)
17:00:10 UT 2016.138.17:00:10 WARNING: No PCFS activity for 0.1 minutes.
2016.138.17:00:10 Check VNC session to see if Field System software is running
2016.138.17:00:10 Check network connection.
Restarted field system from IP, also monica, reconfigure dbbc amd log monitor/e-control.
This lead to a new error: (e.g)
2016.138.21:52:35.28?ERROR qk -211 Tsys value for device eu overflowed or was less than zero.
2016.138.21:52:39.19?ERROR ib -10 ibcon initialization failed, gpib devices inaccessible.
Tried to restart GRIB from IP however this did not work.
Jim managed to restart/reconfigure everything; include re adjusting the attenuators which did not restore after fs reboot (is that correct Jim)?
First 'good' scan: 138-1943 755 2052-474 216 84 CW 19:43:06 19:43:49 0:43 300.0 *
All scans before missed. (Lucas)
- 23:50 UT: Manually power cycled GPIB to try and fix error ib -10 - Talk light was constantly on (possible communication jam). After power cycle - talk light is no longer constantly on. Error persists. (Bryn)
- 02:06 UT: Restarted fs to try fix error ib -10. Missed scans 139-0212 and 139-0217. Unsuccessful - Will reboot pcfs during next gap in schedule. (Bryn)
- 02:37 UT: Rebooted pcfs. (Bryn)
- 02:50 UT: error ib -10 fixed, errors with dbbc communication - cycling power. (Bryn)
- 03:04 UT: Reconfigured DBBC and synced time with fmset. (Bryn)
- 03:10 UT: LO was not locked, restarted Rxmon. System temperatures are way off (values between -180000 and 90000) (Bryn)
- 03:25 UT: Halted schedule again - trying to sort out system temperatures. (Bryn)
- 04:15 UT: Schedule resumed - IF attenuation levels were not being automatically set due to a communication error (causing the errant tsys values) - First scan will be 139-0417a. Missed/bad scans are 139-0247 through 139-0415 (Bryn)
crds83
Hobart 26m:
Disk VSN: HOB+1008
Data volume at beginning: 11540.382 GB
- 14:00 UT: Experiment started (Bryn)
- 14:00 UT: Getting errors “WARNING: error 4f -501 formatter was failing the synch test.” and “WARNING: error ib -4 gpib device time-out on response ca” - trying to fix currently. (Bryn)
- 14:20 UT: error ib has resolved of its own accord - only getting 4f now - on call person being consulted (Bryn)
- 15:20 UT: Reran fmset w/ sync - cleared error 4f. Mark IV FM and Field system times lag computer time by 1 second. (Bryn)
- 15:35:30 UT: increased formatter time by 1 second (“sy=run setcl” in operator input and “+” in fmset) - all times now match in fmset (Bryn)
Hobart 12m:
Disk VSN: HOB+0098
Data volume at beginning: 0 GB
- 14:00 UT: Experiment started OK (Bryn)
R4739
Hobart 12m:
Disk VSN: HOB+0047/6000/1024
Data volume at beginning: 2838.454 GB
- 18:30 UT: Experiment started OK (Liz)
- 18:30 UT: Realised disk offset entered was wrong. Instead of starting value of 0GB for total data recorded, starting value was -323.517 GB. Unsure whether able to/worth changing after commencement.(Liz)
- 18:40 UT: onsource only slewing. Missing 133-1841a.(Liz)
- 18:46 UT: onsource only slewing again. Missing 133-1846 (Liz)
- 21:18 UT: onsource only slewing again. Missing 133-2118a (Liz)
- 09:29 UT: onsource status slewing between scans 134-0929a and 134-0931 (sources 0727-115 and 1124-186)
- 09:38 UT: onsource status slewing between scans 134-0936 and 134-0938 (sources 0537-286 and 1759-396)
- 09:52 UT: onsource status slewing between scans 134-0948 and 134-0952b (sources 1144+402 and 0537-441)
- 10:25 UT: onsource status slewing between scans 134-1023 and 134-1025 (sources 0537-286 and 1954-388)
- 11:44 UT: onsource status slewing between scans 134-1141a and 134-1144b (sources 1144+402 and 2052-474)
