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.
R4663
Hobart 12m:
Disk VSN: USN-0035
Data volume at beginning: 0 GB
Katherine 12m:
Disk VSN: HOB+0131
Data volume at beginning:start at 16375 GB
Yarragadee 12m:
Disk VSN: BKG-0052
Data volume at beginning: 0 GB
- UT 01:30 wind stow (JS)
- UT 01:58 resumed from line 1204. Scan 330-0200 successful (JS)
- UT 06:17 ALARM: error st -998 reading systemclock1, ALARM: error st -999 tcp/ip connection error. Antenna communication software (antcn) problem. Fixed with commands “antenna=operate” and “antenna=open” (Ellen)
- UT 06:23 wind stow. Missed scan 330-0721 recovering from wind stow, bad scans from 330-0613 to 0717b. (Ellen)
- UT 10:05 antenna went crazy again making scan 330-0959b probably bad. ALARM: error st -998 reading elevationstatus. ALARM: error st -998 reading systemclock1. ALARM: error st -999 illegal state error. Antenna communication software (antcn) problem. Then antenna stuck. Again, typing “antenna=open” and “antenna=operate” a few times fixed the problem. (Ellen)
AUST62
Hb Module HOB+0118 start pos 4831 GB
- 00:06 UT experiment finished about 750 GB behind the schedule for no reason (Ellen)
Ke Module HOB+0131 start pos 5310 GB
- 00:01 UT e-remote would not connect (according to Jesse it had been doing this for ages). Restarting e-remote fixed it for me, but it also caused Yg e-remote to close!! (Ellen)
- 00:39 UT “checkmk5” was not defined in the proc file and so no autocorrelation spectra were being generated which Jamie then fixed. First proper checkmk5 at 00:41 UT (Ellen)
- 02:07 UT e-remote would not open a checklist until 7th attempt, then as soon as I completed it e-remote just shut down (interesting new features…) (Ellen)
- 02:50 UT e-remote stopped responding and now won't close. (Ellen)
- Gave up and started using original e-remote (JS)
- 19:09:09 UT clock jump at Katherine, schedule halted at 19:14 for DBBC reconf. Bad scans: 327-1908 to 1912b, missed scans 1914 to 1936. As soon as the clock jump was fixed, the field system crashed, but not before mk5 could start recording. Recording continuously between 19:37 UT and 19:47 UT. More missed scans before schedule resumed (1937 to 1954a). (Ellen)
Yg Module HOB+0119 start pos 5132 GB
- 00:27 UT Tsys bands 13, 14 consistently too high (between ~130 and 200) (Ellen)
- 02:05 UT Tsys band 12 now above 100 as well (Ellen)
- 22:10 UT e-remote just closed for no reason at all. FS was still running so no scans missed. DID NOT reconnect to the log monitor. I had to create another log file. (Ellen)
AUST61
Hb Module HOB+0118 32GB blank start (JS)
- 4:20 UT Ch14 tsys odd (-20K) (JS) seems fine now (UT 4:30) no it's wacko -1300 @ UT4:36
- 7:50 UT: system monitor false reading (LO status red field)> Monica restarted (Lucia)
- 9:14 UT: accidentally run fmset (wrong station) at 08:27. This brings the recorder to fs delay up to 0.99 sec. Halted schedule at 08:47 and run fmset. Schedule resumed at 08:49 UT. Missed scans 326-0846 & 326-0848. I guess some bad scans before that. (Lucia)
Ke Module HOB+0131 32GB blank start (JS)
- Late start due to numerous issues with clock offsets, DBBC, and MK5. Start at 2014.326.00:53:59.61 (first scan ~5min there after). (JS)
- First successful scan after start Source: 1519-273, Scan_Name: 326-0100 – Data -231GB
(JS) - 9:02 UT: recorder to fs delay too big. Schedule halted at 08:21 UT, run fmset. FS crashed and restarted. Offset is good now. But troubles with eRC which does not find the Server. Jamie updates the version and restarts the fs again. Back to normal operation at 09:09 UT at scan 326-0929. Bad/missed scans # 326-0820 (or before) to 326-0928. (Lucia)
Yg Module HOB+0119 32GB blank start (JS)
- 4:20 UT Ch14 tsys temporarily high (480K) (JS) - seems fine now (UT 4:30)
- 21:55 UT Tsys values in both 13, 14 between 150 and 200 (Ellen)
R4662
Hb NOT RUNNING - no schedule file
Ke
- Module HOB+0041 start pos: 3014 GB (Ellen)
- 04:41 UT - Halted schedule due to mark5 errors. It appears that the connection had closed (vk)
- 04:51 UT - Restarted schedule. Missed scan: 325-0440 (vk)
- 05:20 UT - Received phonecall from Martin saying that this R4 was being recorded onto the same disk as ohig93 (vk)
- 06:10 UT - New eRemote Control is sluggish and keeps closing, had to open old version (Ross).
- 07:35 UT - Switched back to new eRemote Control, seems to be working again (Ross).
- 09:53 UT - New eRemote Control crashed again when I completed checklist (Ross).
- 11:40 UT - New eRemote Control crashed again when I completed checklist. Would use old eRemote Control but links to Tsys seem to have been removed (Ross).
Yg
- Module BKG+0141 start pos: 0 GB (Ellen)
- 18:39 UT module swapped but no scans missed (Ellen)
OHIG93
Hb
- Recording to bank B (HAY-0047) Didn't get starting disk pos (JS)
- (@~18:20 UT) Accidentally power cycled the Hb DBBC when trying to fix the Ke issues. Schedule restarted at 18:46 UT so first scan 5 min after. I'll note the missing scans in the summary (JS)
- Scans missed 323-1809 to 1851
Ke
- (19:30 UT) No recording as of yet in Ke, System temperatures and power levels require attention (JS)
- (20:22 UT) Issues fixed, DBBC reset, power levels OK, clock offset OK Schedule started (JS)
- (02:25 UT) Tsys values are all far too high (113 - 191) except for bands 1-4 which are high 80s to low 90s (Ellen)
- Scans missed 323-1800b to 2016
Yg
- (19:30 UT) Everything fine in Yg land. recording to the same module as OHIG92 (BKG-0037) currently at 10GB (?) (JS)
- missed scan 324-0159 due to module swap (Ellen)
OHIG92
Hb
- no O'Higgins module in the mk5. Recording to HOB+1008 with AUSTALs. 11113.5 GB (Lucia)
- (17:15UTLooks like econt crashed at some point here. Getting “No PCFS activity for 155 minutes” +) but field system is running and responding, and scans seem to be fine nested amongst a host of “Remote access: user with alias 'oper(1)' logged out” (JS)
Ke
- recording to module with O'Higgins experiments. HOB-0041. Disk pos 1021.1 GB (Lucia)
- (17:30UT) system temperatures are nuts range from -6000K to 21000K across all channels! (JS)
- (19:25 UT) Looks like the above system temperature issues are related to power level issues. This may have affected several scans towards the end of the experiment.(JS)
Yg
- recording to empty 2TB module. BKG-0037. 0.0 GB. (Lucia)
/home/www/auscope/opswiki/data/pages/operations/handover.txt · Last modified: 2018/10/29 16:27 by Jesse Swan
