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.
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.
Yarragadee 12m
Observer: Arwin
rfpic=cross,direct
when schedule=gt05yg,#1
was entered. Recording for sband=direct(20v) from 0100 UT onwards. ifa power levels were very high, ifa was approx 39000 whilst ifb was around 29000. See Image 1 belowrfpic=*,cross
. Recording for Sband=cross from 12:42UT onwards. The power levels were under control for this setting, ifa settled around 24800 whilst ifb settled around 29000. See Image 2 below“rpfic=cross,direct
and as such may not have loaded the correct setting and just imported the default rfpic=direct,direct
? rfpic=cross,cross
and started recording for the sband=cross (14V) again. Power levels were stable and near the target power levels (ifa and ifb). See Image 3 belowrfpic=cross,direct
to record again for the s=direct 20v with the correct settings.rfpic=cross,cross
again to observe at lower voltage because the peak was high in the spectrum analyser. Noticed a small drop followed by a big drop (Image:4) around 0218UT (not sure if this was related to the voltage setting or due to the spacecraft going out of view of the dish). The lower power level remained stable until 0220UT before the peak disappeared.rfpic=direct,direct
to return to the normal ivs mode. Cancelled the iread
command output every 10 sec, fs terminated, tracking stopped, antenna stowed, UTC1-UTC time difference brought back to 0. Image:1
Image:2
Image:3
Image:4
Hobart 12m Disk VSN:PKS+0021 Data Volume at beginning: 2841 GB
Katherine 12m Disk VSN:NRCAN-01 Data Volume at beginning: 0 GB
Yarragadee 12m Disk VSN:OSOD-054 Data Volume at beginning: 0 GB
Hobart 26m Disk VSN:HOB+1011
Data Volume at beginning: 2580 GB
Hobart 12m
Disk VSN: PKS+0021
Data Volume at beginning: 0 GB
Hobart 12m
Disk VSN: GSFC+017
Data Volume at beginning: 2.179 GB
Katherine 12m
Disk VSN: GSFC+023
Data Volume at beginning: 54.026 GB
Yarragadee 12m
Disk VSN: HOB+0041
Data Volume at beginning: 1.282 GB
Fringe test done twice, no fringes on any channel in any baseline. Hobart 12m
Disk VSN: HOB+0129
Data Volume at beginning: 1.789 GB
Katherine 12m
Disk VSN: USN-0032
Data Volume at beginning: 0 GB
Yarragadee 12m
Disk VSN: BKG+0142
Data Volume at beginning: 0 GB
GENERAL ISSUES
Watchdog timeout alarm isn't sounding for hb. OR any of the other stations ke yg
No alarm for WARNING: error st -10 rampepochtime not -1 when preparing to load, check antenna is in “operate”.
No alarm for WARNING: error st -8 power on timed-out.
No met data onwards from 2015_10_20? Have to wait until data is up before yg logs can be done.
Hobart 12m
Disk VSN: HOB+0129
Data Volume at beginning: 0.3GB
Katherine 12m
Disk VSN: BKG-0036
Data Volume at beginning: 0.3GB
Yarragadee 12m
Disk VSN: BKG-0064
Data Volume at beginning: 0.3GB