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.
R4655
Hb HOB+0039
- UT 18:30 - Experiment started OK (Vasaant)
Ke BKG+0135
- UT 18:30 - Experiment started OK (Vasaant)
- Noticed during system checks that a couple of bands on the dbbc have been consistently steep since the start of observations (11, 12)
Yg WSRT-049
- UT 18:30 - Experiment started OK (Vasaant)
- Noticed during system checks that a couple of bands on the dbbc have been consistently steep since the start of observations (7,15)
R1655
Hb recording to HOB+0015. Start disk_pos is 1892 GB
- UT 17:00 - Wind stowed at start.
- UT 17:25 - First source after windstow. 7 missed scans: 272-1700 through to 272-1720 corresponding to 30 GB of data
- UT 21:02 - Wind stow. Missed scans from 272-2104 through to 272-2204 corresponding to 50 GB of data.
- UT 22:07 - Observing resumed.
- UT 22:36 - Wind stow.
- UT 23:00 Halted schedule because of wind (Imogen)
- UT ~01:00 schedule resumed (Imogen)
- UT ~2:30 drives at Hb got themselves into a state after a windstow - had to reset them several times meaning more scans lost (Imogen)
- UT ~3:00 no more windstows for Hobart until the end of my shift - Imogen
- Counters timing out occasionally.
- UT 11:23 - rebooted pcfshb in large gap to try to fix problem. No missed scans.
Ke recording to JIVE-064. Start disk_pos is 0 GB (Vasaant)
Yg recording to TR-00012. Start disk_pos is 0 GB (Vasaant)
:
R4654
Hb
- (setup, Lucia) module HOB+0015, 0 GB
Ke
- (setup, Lucia) module OSOD-116, 0 GB
- Last scan went onto module HAY-0030.
Yg
- (setup, Lucia) module BKG+0114, 0 GB
- (setup, Lucia) system monitor stuck
AUST47
Hb:
- Module USN start disk pos: 0 GB
- UT 23:26 - Changed over to rfpic enabled log monitor
Ke:
- Module HOB+1000 start disk pos: 0 GB
- System Monitor not updating at all (needs to be restarted every time you want to check something)
- Jim's rfpic command is throwing up errors for Ke. However, it appears that LO is locked - so antenna operation is not compromised.
- UT 23:26 - Changed over to rfpic enabled log monitor
- UT 05:11 - Schedule halted for disk check
- UT 05:19 - Schedule restarted. Scans missed: 268-0514b, 268-0516, 268-0517b
Yg:
- Module HOB+0047 start disk pos: 0 GB
- System monitor not updating either
- Connection lost to every thing Yg (pcfsyg, timeyg, and even rack cameras) shortly after experiment started (07:01 UT) and Brett worked his magic to fix everything by about 08:45 UT, no scans missed as experiment had recorded first scan before connection was lost
- UT 23:26 - Changed over to rfpic enabled log monitor
- UT 05:14 - Schedule halted to check disk in other module
- UT 05:22 - Schedule restarted. Scans missed: 268-0516, 268-0517a, 268-0519
r1654
Hb:
- Recording to FGI-0004. + 0 GB.
- SpaceX
- Missed scans 266-0211 through 266-0257
- Missed scans 266-0357 through 266-0423a
- Missed scans 266-0526b through 266-0606
- Data before 266-0704 may have incorrect pointing corrections. Refractive corrections are used for SpaceX tracking, and these may have been erroneously enabled.
- Missed scans 266-0704 through 266-0736
- Missed scans 266-0839 through 266-0920b
Ke:
- Recording to USN-0202. + 0 GB.
- Missed scans 266-0211 and 266-0216 due to over-eagerness with SpaceX support.
- Missed scans 266-0400b through 266-0631 due to pcfs crash whilst producing autocorrelations.
Yg:
- Recording to USN-0086. + 0 GB.
- Network connection has been off and on since start of experiment, fixed by 266-0000. (<Chris> This seems benign.)
- Missed scans 266-0211 and 266-0216 due to over-eagerness with SpaceX support.
- mk5=dot? reveals -1s formatter - Was throughout observations.
a1415
Hb:
- LO unlocked @ ~19:00 UT. Jumped back to locked by itself. No other problems identified.
- Scedule started OK first source OJ287 scan 264-0253b
- recording to HOB+0130
- stopped for SpaceX at 04:30 missed scans 264-0432a to 264-0450a (Warren)
- stopped for SpaceX at 06:24:05UT, resumed 07:14, missed scans 264-0625 - 264-0720a (Imogen)
- stopped for SpaceX at 08:07UT, resumed 08:40 , missed scans 264-0806a - 264-0837a (Imogen)
- stopped for SpaceX at 09:38UT, resumed 10:12UT, missed scans 264-0938 - 264-1012b
- antenna stuck from 02:15:12.12 - end of experiment due to work to fix LO unlocked
Ke:
- Scedule started OK first source OJ287 scan 264-0253b
- recording to HOB+0126
- lost power to agilent clock counters for maser 2 gps, and formatter 2 gps
- Restart field system 03:36:05 missed scan 264-0336
- powered agilent counters up at 264 / 05:00
- missed scans 264-0454 to 264–0504b while re-syncing system
Yg:
- Field system restart required at start to get out of wind stow
- rain storm after high winds eased
- First scan 264-0302b
- Recording to HOB+0098
