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.
aug004
Hobart 12m:
Disk VSN: HOB+0126, Data volume at beginning: 85 GB
- Pointing solution: 2015.023.23:10:04.24#fivpt#xoffset 223.1793 79.2251 0.00554 -0.01362 0.00242 0.00285 1 1 1618m49
Katherine 12m:
Disk VSN: GSFC+022, Data volume at beginning: 85 GB
- Pointing solution: 2015.023.23:09:44.20#fivpt#xoffset 175.8087 54.1101 -0.00089 0.00246 0.00199 0.00424 1 1 1618m49
- UT 14:44 Single alarm sounded at 14:40
ALARM: scan_check reports Mark5 data format problemlooks to be no consequences or repetition. (JS)
Yarragadee 12m:
Disk VSN: USN-0002, Data volume at beginning: 24 GB
- Note that iread values are bad (S-band):
- /ifa/1,agc,1,25000,34,25468
- /ifb/4,agc,4,29000,18,28689
- /ifc/2,agc,2,35000,63,38131
- /ifd/2,agc,2,35000,63,44721
- The following point checks were done:
- 2015.023.23:14:09.20#fivpt#xoffset 150.4285 64.2660 0.05054 0.00538 0.00707 0.06890 0 1 1618m49
- 2015.023.23:41:07.22#fivpt#xoffset 105.3795 39.5677 0.00000 0.00538 0.01255 0.06890 0 0 1921-293
- 2015.023.23:52:16.17#fivpt#xoffset 163.0582 67.6059 0.00000 0.00538 0.00620 0.06890 0 0 1618m49
- The first scan (3C279 at 024-0000) was missed. It appears that bank A of the mk5 does work properly. The troubleshooting was as follows:
- USN-0002 could not be recorded to in bank A, so it was swapped with HOB+0031 in bank B.
- USN-0002 could be recorded to in bank B - the module is fine. Swapped to bank A for the schedule.
- Schedule started, and mk5 issued errors on recording; I thought I checked recording in bank A after the swap, but it appears I did not. Recorded to bank B in time for the second scan.
- UT 12:43 iread values are still bad but haven't drifted (JS)
- /ifa/1,agc,1,25000,34,24567
- /ifb/4,agc,4,29000,18,28779
- /ifc/2,agc,2,35000,63,37537
- /ifd/2,agc,2,35000,63,44248
- The long and short of the disk swap business above is: The module that needs to be recorded to next (AUG005 @11am local time) is in bank A, but Chris was unable to verify if bank A can be recorded to. This module may need to be physically moved to bank B for recording. (JS)
r1671
Hobart 12m:
Disk VSN: UAO-0026 Data volume at beginning: 0 GB
- Pointing corrections: -0.00298 -0.02682 Source: Pictora
Katherine 12m:
Disk VSN: USN-0087 Data volume at beginning: 0 GB
- Chris screwed up - his alarm didn't go off, and Ke did not start with the schedule. However, Ke had an issue with driving to sources - any source issued causes Ke to drive to the elevation limit of 5 degrees, then complains it is stuck. After contacting Warren 1.5 hours into the schedule, pcfske was restarted - however, it was then not communicable remotely. Martin was called to get pcfske into a workable state. At some stage along the way, the fs time was wrong, despite ntp and so forth on pcfske being correct. This is due to the fs grabbing time from the hardware clock, which may depend on a bad battery in the computer. Jamie corrected this, but the hardware clock may reset on a reboot. (Chris)
- First recorded scan of the schedule is at 20:21:16. Nothing was recorded before this - 236 GB not recorded. (Chris)
- Autocorrelation spectra steep in bands 12 and 13 (Ross).
Yarragadee 12m:
Disk VSN: USN-0111 Data volume at beginning: 0 GB
- Yg is suffering from a faulty DBBC - X-band channels are OK, but S-band may not be.
- Pointing corrections: 0.13474 0.00000 Source: Pictora The pointing is probably awful because of the bad S-band Tsys.
- Tsys readings unreliable in bands 09 and 10, and autocorrelation spectra steep in bands 11 through 14 (Ross).
AUG003
Hobart 12m:
Disk VSN: HOB+0120 Data volume at beginning: ~3828GB
Katherine 12m:
Disk VSN: HOB+1002 Data volume at beginning: ~5424GB
- 01:04 UT - More antenna stuck messages, but Ke corrects itself. (Chris)
Yarragadee 12m:
Disk VSN: HOB+0118 Data volume at beginning: ~5511GB
- 06:30UT - Tsys reading problematic. Channels 5-8 sometimes overflowed. This problem is persistent since friday. (Lucia)
- 15:30UT - Addition to Lucia's comment. Judging from autocorrelation spectra and Tsys values, there are coming and going problems in X-band channels 5,6,7,8 chs S-band 1, 4, 5, 6: ridiculous Tsys values, slopes and peaks in spectra, phase disturbance. Started after New Year (4G network launch in Australia?) (was first observed during MEX tracking 05.01.15) (Liza)
- 23:51UT The usual problem persists in certain directions (for example, UT 2015.018.23:51:15.82 it was source 1908-201 and no problem in direction of 1424-418. So looking some 30deg up and left from the camera problem is more prominent than 30deg up and right) (Liza)
AUG002
Hobart 12m:
Disk VSN: HOB+0120 Data volume at beginning: 0GB
23:50UT - Not starting schedule due to very high winds consistently above 55kph. Rather than break anything, I will leave the schedule until the wind dies down. (Imogen)
01:37UT - schedule started after wind dropped below 40kph for long enough (Imogen)
02:47UT - wind stow activated, gust of 88kph (!) (Imogen)
03:05UT - wind stow activated, came out of wind stow for about 10 minutes, then went back into stow again (Imogen)
03:22UT - came out of wind stow (Imogen)
03:57UT - wind stow activated (Imogen)
04:09UT - came out of wind stow (Imogen)
04:17UT - wind stow activated (Imogen)
04:35UT - came out of wind stow (Imogen)
04:37UT - back into wind stow again. Gusts are getting much higher again up to 75 kph, halted schedule and stowed antenna or something is going to get broken (Imogen)
08:12 UT - back on source for scan 017-0815, average wind has decreased for the moment, still some strong gusts. (Warren)
08:17 UT -stowed immediately after 017-0815, stowed for scan 017-0817 (W)
08:27 UT - back again for scan 017-0833, just under stow threshold, antenna being buffeted (W)
08:38 UT - stowed during scan 017-0837a, wind increasing (W)
08:43 UT - recording halted, recorded scans 017-0840a, 017-0842, 017-0843 no good (W)
09:18 UT -sched resumed, first scan 017-0924 then 10:07; wind stowed during scan 017-1006, recorded scans 017-1009, 017-1010 no good (W)
10:16 UT -sched resumed, first scan 017-1021 (W)
20:23 UT - A gust of wind triggered the autostow. This affects the tail end of source 017-2021, and nothing is recorded until 017-2032a (Chris).
21:07 UT - Another gust triggered autostow at 21:02. Released at 21:07.
Katherine 12m: Disk VSN: HOB+1002 Data volume at beginning: 0GB
23:15UT: DBBC attenuation levels were incorrect, restarted dbbc software, fixed the problem (Imogen)
23:30UT: Mark 5 would not get bank status, restarted mark 5, resynced with fmset, all good (Imogen)
23:45UT: lost connection with pcfske, could not get back into VNC session, but was able to ssh into pcfske and run field system from a remote terminal, everything working ok (connected to eremotectrl ok), except for the lack of VNC session (Imogen)
23:53UT: didn't get time to do five point check due to mark 5/dbbc/pcfs problems (Imogen)
21:10 UT: Antenna was apparently stuck for a few scans:
2015.017.21:08:35.11#trakl#Antenna stuck
2015.017.21:08:52.14#trakl#Antenna stuck
2015.017.21:09:07.11#trakl#Antenna stuck
… but came out of this state when a new scan arrived, before I had time to fix it (Chris)
Yarragadee 12m: Disk VSN: HOB+0118 Data volume at beginning: 20GB
00:22 UT: Connection with eremotectrl lost - monitoring from pcfs only (Imogen)
22:27 UT: DBBC channels 05 - 09 (X-band) have high Tsys values. Probably RFI. This has also been noted in a checklist. (Chris)
R4670
03:18UT UPS for ops-2 died (go figure). Jamie fixed it though. No scans were missed at Katherine (Hobart was still in wind stow and we power cycled the DBBC at Yarragadee). (Ellen)
Hobart
Module: USN-0202, start pos ~270 GB
- 00:27UT Windstow (Ellen)
- 01:20UT Halted schedule due to windstow (because I forgot to do it earlier…) Bad scans 016-0027a to 016-0114, inclusive. (Ellen)
- 02:19UT Schedule resumed at scan 016-0228, only needed to type in “schedule=…” as opposed to restarting the FS (yay). Missing 016-0120b to 016-0222a. (Ellen)
- 02:32UT Windstowed again. Scans 016-0228 and 0230b good, scan 016-0233a bad. Schedule halted again at 02:38UT. (Ellen)
- 03:50UT Schedule resumed. Missing 016-0238a to 0345. (Ellen)
- Disc pos ~100 GB ahead
- 07:46UT antenna wind stowed 07:53 auto stow released succeeded (yeah!). missed scans: 016-0744 (parts) to 016-0751a inclusive (Lucia).
- 07:58UT stowed again. 08:04 auto-release successful. missed scans: 016-0759 to 016-0804 (Lucia).
- 18:03UT Module ran out of space; instead of swapping I decided to miss the last 4 scans (016-1803 to 1824a). (Ellen)
Katherine
Module: HOB+0034, start pos ~2270 GB
Yarragadee
Module: UAO-0018 (first 49 GB), USN-0093
- UT 19:01 Quickly swapped to module B USN-0093 as per instructions from site staff (JS)
- 23:55UT Autocorrelation really dodgey in band 5 and quite fuzzy in bands 6 - 13. Tsys continuously overflowed in band 5, often very high/overflowing in band 6. (Ellen)
- 01:10UT Tsys bands 05 - 08 all negative, but Autocorrelation has come good. (Ellen)
- 01:42UT Tsys band 05 overflowed, 06 - 08 too high (~490-660) consistently. (Ellen)
- 03:22UT Halted schedule to give dbbc a full power cycle to try and fix tsys values. It didn't work, bands 05 - 08 are still bad. Missed scans 016-0322 to 0345. (Ellen)
- Disc pos ~100 GB behind
- 05:43UT Tsys bands are all reasonable. (Ellen)
- 06:20UT antenna waiting at limit for scan 016-0624 (Az: +269.98, El: 43.36). Slewed to next source without troubles. (Lucia)
- 07:01UT weird Tsys values again - details in checklist (Lucia)
CRF86
Hobart 12m:
Disk USN-0202
Data volume at beginning: 1.723TB
Katherine 12m:
Disk VSN: HOB+0034
Data volume at beginning: 3.707TB
Yarragadee 12m:
Disk VSN: UAO-0018
Data volume at beginning: 67 GB
- UT 18:44 CH 05-08 have v.high tsys values (>640K) power levels OK (JS)
- UT 18:55 CH 05-08 OK now (JS)
- UT 19:01 Quickly swapped to module B USN-0093 as per instructions from site staff (JS)
