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.
AUST40
Jesse (UT 223/0700 - 223/1900)
DIM crashed on yg (prior to pointing check) returned “error m5 -23 mk5cn: error openingg, mark 5 probably not running”. Restarted DIM
Turns out the above DIM crash was probably due to a module swap (to 32TB) at yg.
I went full potato and reset the hb pcfs when I saw “no pcfs activity for xx” not realising it was due to a break between scans: probably lost scan 223-0709 because of this 
First scan for Katherine (0312-770 @ 07:00:00) did not occur as the target was below horizon(?) for entire length of scan.
Yg had a mk5 malfunction at 223.10:19 during scan 1037a “error m5 -104 mk5cn: time-out, connection closed”. PCFS restart, DIM restart.
Vasaant (UT 223/1900 - 224/0700)
Sources below elevation limit at Ke and Yg for source 1352-632 @ scan 223-2228 and at Ke again for source 1352-638 @ scan 224-0002b.
Power failure at Yg resulting in no data collection between UT 224/0312 - 0333. Scans missed: 224-0311, 224-0313.
AUST39
The disk positions are recorded on the printout (fairly early in the experiment) as too many scans were missed and there was no connection to Ke and Yg to figure out the start diks pos of the experiment End person (Warren) will have to look through the logs just for the first couple of scans to see which ones were actually recorded.
Hb:
- mk5 returned errors stating the that mk5 can't record while data transfers (for some reason this did not set off the alarm like it did at Ke)
- these errors were returned during the 1st couple of scans so I don't know if they're any good
- log reported that recording stopped mid scan 222-0016a (at UT00:16:42) and then reported that the next scan was 0013 (???)
- this ridiculous notion of re-recording a previous scan I think is what caused the field system to crash, missing all scans after this until 0036: e-remote doesn't work well as a time machine evidently
- schedule resumed at scan 0036 (disk pos: 5382.679)
- All S band tsys values too high for entire experiment
Ke:
- Alarms went off right at the beginning of the experiment saying things like (mk5-900): “can't record while data transfers”, “not while other activity”
- This went on until the field system had a fit and Jamie had to restart - again, I have no idea how usable any of these scans are
- first recorded scan after FS fit was 222-0041 (disk pos: 5843.831)
- Tsys values in bands 09-12 always too high (band 09 approximately 180K)
Yg:
- no connection throughout the start of the experiment but presumably, similar errors arose
- first scan after finally re-connecting was 222-0044 (diskpos: 5996.523)
- Tsys values in band 11 consistently 50K
Schedule errors day 222 22:32:31 and 22:33:27, requests to Mk5 recorder ( for scan_check perhaps?) while recording. Recording continued despite error messages.
AUST38
Experiment started OK 00:00, all modules blank: Hb - HOB+0118/16000, Ke: HOB+1008/16000, Yg: HOB+0118/32000 And yes, that's correct, we have two different modules with identical VSNs: HOB+0118/16000 in Hb and HOB+0118/32000 in Yg. Both are used for AUST38 and AUST39.
Hb: strong spikes in ch 14,15)
Ke: S band, esp. ch11, 12, 15 – strange autocorr bandpass, extremely high Tsys (150-185K). RFI? Bad calibration?
Yg: DIMino program fails sporadically (scans 221-0101 - 0108 are lost); S band Tsys in ch 12, 13, 14 is too high (105-120K)
All: autocorr bandpass in ch.14 looks “steep” in all three antennas.
R4647
All disks started at zero GB.
hb: FGI-0004
ke: USN-0069
yg: USN-0023
Nothing to report except experiment started OK at 18:30.
Notes on tsys:
- S-band reading high on ke all night.
- X-band reading low on yg all night.
- S-band reading high on hb all night. (e.g. ch09 – ch12 127,118,112,129 @ 2014.220.18:04:31.08)
- Temperature values noted intermittently in additional notes of checklist.
AUA075
Hobart 12m
- Field system crashed - noticed at approximately 20:30 Hobart time, 10:30 UTC. Prad restarted experiment but Telescope was stuck in SLEW and wasn't changing elevation/azimuth. Warren called and restarted system again. System function normal by 23:00 hobart/ 13:00 UTC. (Jasper)
All Stations (Yg, Hb, Ke)
- Some of the checklists for stations had error comments made on them (when none was necessary) since operator was not aware of the idiosyncrasies of station systems. Warren overviewed systems and deemed them functional and satisfactory. (Jasper)
R1645
- Experiment started OK @ all stations.
- pcfske to time difference ~2 seconds with “mk5=dot?”. fmset to sync to 0 prior to recording of next scan.
