User Tools
Sidebar
operations:handover
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.
It is ESSENTIAL to put your name after EVERY entry.
Copy and paste the template into the new handover notes
====== 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.
R4729
Hobart 12m:
Disk VSN: HOB+1006
Data volume at beginning: 0 Gb
- 1830 UT Experiment started OK (Tiege)
Katherine 12m:
Disk VSN:USN-0173
Data volume at beginning: 0 Gb
- 1830 UT Experiment started OK (Tiege)
- 2016.064.11:33:34 ALARM: error m5 -104 mk5cn: time-out, connection closed (Lucas)
- 2016.064.11:33:52 Alarm acknowledged
- Missed scans 064-1134a through to 064-1158a (because I halted it pending resolution [not realising error was to be ignored {usually}]).
Yarragadee 12m:
Disk VSN:BKG-0034
Data volume at beginning:0 Gb
- 1830 UT Experiment started OK (Tiege)
R1729
Hobart 12m:
Disk VSN: HOB+0121
Data volume at beginning: 13749.302 GB
Katherine 12m:
Disk VSN: NAIC-004
Data volume at beginning: 0.000 GB
- 10:03 UT - Wind speeds are over 50km/h. Antenna stuck at about -69Az and 24El during scans 061-1003 to 061-1042. (Ellen)
- 10:44 UT - Schedule halted to reboot antenna drives. Drives restarted ok, antenna was able to stow. FS crashed. Total scans missed: 061-1044b - 061-1101b. (Ellen)
Yarragadee 12m:
Disk VSN: USN-0178
Data volume at beginning: 0.000 GB
- Dead screen on ops2 obscures pcfsyg and dbbcyg when they opens in their default location. Need to randomly click in that part of screen until vnc window can be found.
r4728
r4728
Hobart 12m:
Disk VSN: HOB+0042
Data volume at beginning:2054.578 Gb
- 1908 UT Experiment started late due to slow setup during change of experiment. First scan was 056-1911. Hb and yg e-Remotecontrols had become unresponsive and needed to be restarted. (AK)
- 00:07 UT - wind stow. Affected scans 057-0005 through 057-0059; may have a couple of scans in between while wind slowed down. (Lucia)
Katherine 12m:
Disk VSN:USN-0067
Data volume at beginning: 1491.951 Gb
- 1908 UT Experiment started late due to slow setup during change of experiment. First scan was 056-1911. Hb and yg e-Remotecontrols had become unresponsive and needed to be restarted. (AK)
Yarragadee 12m:
Disk VSN:NTO-0010
Data volume at beginning:0 Gb
- 1908 UT Experiment started late due to slow setup during change of experiment. First scan was 056-1911. Hb and yg e-Remotecontrols had become unresponsive and needed to be restarted. (AK)
- 0800 UT Antenna got stuck, had to reset the drives, missed scans between 057-0800a and 057-0815a inclusive (Tiege)
- 0908 UT AUtomatic wind stow activated, will update with scans missed when it unstows. winds at >55 kph (Tiege)
- 0917 UT auto stow released, missed 057-0910 and 057-0913, winds back to <20kph (Tiege)
- 0947 UT DBBC crash, mk5 crash, sntp server dropped connection, everything going haywire. Fixed the DBBC and mk5 but couldnt get a connection again to the controller clock. Called Jim (on-call) and he is attempting to rectify the situation. (Tiege)
- 1053 UT Jim has sorted the issue with the dropped connection to the SNTP server, there was a power glitch at Yaragadee at 0753 UT and it seems like some things did not come up after the UPS came online. This means scans from 0753 UT to 0947 UT have a high chance of being dodgy and between 0947 UT and 1053 UT all scans were missed. The scans dodgy/missed between 0753 and 1053 are 057-0753b through to 057-1047 inclusive. (Tiege)
crf93
Hobart 26m.
Disk VSN: HOB+0033
Data volume at beginning: 3199.326 GB
- 1814 UT Experiment started - delays due to problems with Ke (Bryn)
- 07:02:38UT Antenna Stowed due to high winds (JR)
- 7:45:00UT Schedule halted due to constant wind stows. Av speed: 59.26km/h (JR)
- 10:42UT Schedule resumed (JR). Scans effected: 056-0702 to 056-1050. (JR)
- 12:30 UT Antenna Stowed due to high winds, (AK)
- 13:08 UT Wind was consistently bad (>40km/hr) halted the schedule. (AK)
- 13:18 UT Stopped recording. Realised I should have probably should have entered “disk_record =off” after it stowed the first time. Log monitor still says recording (bug?) though disk_pos has not changed. (AK)
- 14:21 UT restarted the schedule once the wind had died down and the live page said “wind_ok”. Scans affected 056-1231 through to 056-1415. (AK)
- 15:38 UT Antenna stowed due to high winds. (AK)
- 16:15 UT Schedule halted, winds were still >42 km/hr
- 17:58 UT Antenna remained stowed due to winds. The wind temporarily dipped below 30 km/hr tried running “schedule=crf93” but no luck. Missed all scans 056-1538 onwards. (AK)
Hobart 12m:
Disk VSN: HOB+0042
Data volume at beginning: 0 GB
- 1814 UT Experiment started - delays due to problems with Ke (Bryn)
- 07:30UT ALARM Automatic wind stow activated (JR)
- 07:35UT Auto-stow released. Scans effected: 056-0726 and 056-0733 (JR)
- 07:40UT ALARM Automatic wind stow activated (JR)
- 07:51UT Auto-stow released. scans effected: 056-0740 and 056-0748 (JR)
- 08:16UT ALARM Automatic wind stow activated (JR)
- 08:21UT Auto-stow released. Scans effected 056-0813 and 056-0822 (JR)
- 08:27UT ALARM Automatic wind stow activated (JR)
- 08:46UT Auto-stow released, activated again 2 minutes later. (JR)
- 08:56UT Auto-stow released. Scans effected: 056-0822, 056-0830, 056-0838, 056-0846, 056-0853. (JR)
- 09:43UT ALARM Automatic wind stow activated (JR)
- 09:48UT Auto-stow released. Scans effected: 056-0940 and 056-0947 (JR)
- 09:54UT ALARM Automatic wind stow activated (JR)
- 09:59UT Auto-stow released. Scan effected: 056-0955 (JR)
- 12:28UT Automatic wind stow activated. (AK)
- 12:34UT Auto-stow released. Scan affected 056-1224 and 056-1231. (AK)
- 12:37UT mk5=mode? returns 0x55555555 : 2 : 2 ; which is not consistent for a crf experiment. Did a search for previous outputs of mk5=mode? and they were all displaying 0x55555555 : 2 : 2. According to wiki crf experiments should be 0x55555555 : 4 : 2. Not sure if this is of concern? (AK)
- 13:25UT Automatic wind stow. (AK)
- 13:30UT Antenna failed to recover from stow, winds were still high. (AK)
- 13:57UT winds slowed, antenna manually recovered as per wiki's guidelines. Scans affected 056-1327 through to 056-1351 (AK)
- 15:37UT Auto wind stop activated(?) acc to e remote control but no warning in logmonitor
- 15:53UT Auto-stow released. Scans affected 056-1538 and 056-1546. (AK)
- 15:58UT ALARM Automatic wind stow activated (AK)
- 16:04UT Auto-stow released. Scans affected 056-1553 and 056-1600 (AK)
- 16:31UT ALARM Automatic wind stow activated (AK)
- 16:37UT Auto-stow released. Scans affected 056-1631 (AK)
- 16:58UT ALARM Automatic wind stow activated (AK)
- 17:05UT Auto-stow released
Katherine 12m:
Disk VSN: HOB+0119
Data volume at beginning:
- Problems with the Hardware clock on PCFS. PCFS needs restarting again (Bryn)
- PCFS running after reboot. Data good from scan 056-0126 onward — Jim Lovell 2016/02/25 03:34
- 12:37UT mk5=mode? returns 0x55555555 : 2 : 2 ; which is not consistent for a crf experiment. Did a search for previous outputs of mk5=mode? and they were all displaying 0x55555555 : 2 : 2. According to wiki crf experiments should be 0x55555555 : 4 : 2. Not sure if this is of concern? (AK)
Yarragadee 12m:
Disk VSN: MAT+0100
Data volume at beginning: 0 GB
- 1814 UT Experiment started - delays due to problems with Ke (Bryn)
- 12:37UT mk5=mode? returns 0x55555555 : 2 : 2 ; which is not consistent for a crf experiment. Did a search for previous outputs of mk5=mode? and they were all displaying 0x55555555 : 2 : 2. According to wiki crf experiments should be 0x55555555 : 4 : 2. Not sure if this is of concern? (AK)
AUA009
Hobart (12m)
Module: HOB+0042, start pos: 4784.542 GB
- 1753 UT - Experiment started late, but seems to be running ok. (Nick)
- 'mk5=mode?' gives '0 : ext : 0xffffffff : 1 : 2 ; ' which is not in the wiki. (Nick)
- get quite a few 'Tsys value for device id overflowed or was less than zero.' errors. (Nick)
- caltsys disabled at 0130 as this was causing significantly shortened scans (missing approximately 10s of each scan). Disk pos lagging by 400 GB due to late start and this problem. (JMc)
Hobart (26m)
Module: HOB+0033, start pos: 0 GB
- 1753 UT - Experiment started late, but seems to be running ok. (Nick)
- 'mk5=mode?' gives '0 : ext : 0xffffffff : 1 : 2 ; ' which is not in the wiki. (Nick)
- Get a lot of errors as follows:
- 'ERROR ch -302 v1 frequency does not check with requested value'
- 'ERROR ch -308 ve total power integrator overflow'
- 'ERROR ch -317 Total power integrator overflow on IF2'
- 'ERROR ch -350 The Receiver 20K stage is hotter than 40K'
- caltsys disabled at 0145 as this was causing significantly shortened scans (missing approximately 6s of each scan). Disk pos lagging by 60 GB due to late start and this problem. (JMc)
Katherine
Module: HOB+0119, start pos: 3605.989 GB
- 1753 UT - Experiment started late, but seems to be running ok. (Nick)
- 'mk5=mode?' gives '0 : ext : 0xffffffff : 1 : 2 ; ' which is not in the wiki. (Nick)
- 1414 UT PCFS died. Calling Warren (on call) to assist (Bryn)
- 1552 UT PCFS still won't boot. (Bryn)
- 1700 UT stowed telescope, still having issues with pcfs. Redoing setup to prepare for next experiment (Bryn)
Yarragadee
Module: HOB+0130, start pos: 3429.876 GB
- 1753 UT - Experiment started late, but seems to be running ok. (Nick)
- 'mk5=mode?' gives '0 : ext : 0xffffffff : 1 : 2 ; ' which is not in the wiki. (Nick)
- caltsys disabled at 0130 as this was causing significantly shortened scans (missing approximately 10s of each scan). Disk pos lagging by 450 GB due to late start and this problem. (JMc)
R1728
Hobart
Module: HOB+0121, start pos: 1328.564 GB
- 1700 UT - Experiment started ok. (Ellen)
- 0947UT Wind-stow (JS)
- 0953UT Wind-stow released (JS)
- 1017UT wind-stow (JS)
- 1030UT Wind-stow released (JS)
- 1048UT wind-stow (JS)
- 1053UT Wind-stow released (JS)
- Scans affected by wind stows: 054-0945a – 054-0951a, 054-1013 – 054-1028, 054-1049a – 054-1053a
Katherine
Module: HOB+0119, start pos: 309.139 GB
- 1700 UT - Experiment started ok. (Ellen)
Yarragadee
Module: HOB+0130, start pos: 302.948 GB
- 1700 UT - Experiment started ok. (Ellen)
- 1708 UT - Delay through DBBC (pps_delay1) has changed from 61949 to 61950. Keeps swapping between these 2 values (ie not drifting) and the delay differences are stable too. Unfortunately, the alarm sounds every 15 mins or so and can't be turned off - Configure in the log monitor only affects delay differences and there's no alarm code to change the action file of the log monitor. (Ellen)
/home/www/auscope/opswiki/data/pages/operations/handover.txt · Last modified: 2018/10/29 16:27 by Jesse Swan
