Use the official Parkes vnc sessions on joffrey:1. Do not use joffrey:2.
The recording machine is different to the DAS control machine! See below
Start the following (in different virtual desktops).
ssh -X vlbi@pkvlbidasthen
ssh -X vlbi@pkvlbidasthen
ssh -X vlbi@pkvsi1then
For DAS and cdisko usage and control see here
The telescope should be parked before you change receiver otherwise the translator can get stuck. Run
atsnap park in an xterm on joffrey
Select the required receiver in “operfcc” and click “place selected receiver on axis”.
Your selected receiver will be on axis once all five status buttons are green and read 'ok'. Alternatively, you can turn on Focus cabin camera using Parkes Monitor & Control GUI to monitor the receiver change. Remember to turn the cameras off when the change is complete, as it is a source of RFI.
Click on the receiver name below for receiver specific setup notes.
|UWB-Low||704 MHz-4.032 GHz|
You MUST select the receiver before starting
atsnap below, otherwise pointing will be wrong.
As of February 2019, observers no longer have to directly call lorun to set up the LO chain.
Both the LO and cal control unit are set via an executable shell script named with the project code and sequential letter epoch (e.g. v558c.sh). This script will call lorun and ccurun and set loGUI and the Cal Control Unit for the appropriate project epoch. LBA support staff will have set up the utility scripts before your observations.
Make sure that the executable exits without throwing any errors. If the LO setup does not exit cleanly, contact LBA support staff as there may be issues with the Parkes Conversion System.
The Switch Matrix is only needed when Mark5 recorder is used (see the Mark5 setup notes ). The DAS are not connected through the switch matrix
The antenna schedule should be copied automatically. If it is missing, download the .psn file from the atnf ftp area (see experiment wiki). As pksobs
on joffrey run
atsnap, with the name of the .psn file. E.g.
The .psn files will be in ~pksobs/lba
Make sure that levels on the VLBI DAS are within range (ie the IF Level is mid range).
If not, adjust attenuation on the loGUI.
Use the C12 attenuators 1&2 for coarse setup (acts on both IFs), use the C40 1,2,3,4 attenuators for fine setup. Usually only the C40 attenuators should be adjusted.
Before adjusting attenuation, click the “refresh” button on loGUI near the bottom left
If you need to change the attenuation, you may want to update the lorun .cmd file.
Tsys is measured by sending a 200 Hz signal to the receiver and a detector connected to the analog output of the VLBI DAS. The lorun script (should) setup the “Stanford Research Systems” signal generator to 200 Hz and amplitude is 5V.
The project executable that was run to set up the LO chain via lorun will also have also called ccurun and set up the Cal Control Unit appropriately for your project.
To view the calibration set up, you can start the “Cal Control Unit” from PKMC gui to ensure all relevant receivers are connected to SRSFG as well as the “DAS BE” and “MARS BE” if Mars is being used.
If the polarisation is swapped, a quick remedy is to swap the DAS inputs at the bottom of rack 2 in the equipment room upstairs. Swap the A1/B1 and A2/B2 short patch cables between the DAS OUT and DAS IN. However when observing remotely this may not be possible. For dual polarization experiments just make a note in the wiki. For single pol experiments just make a different channel selection in cdisko to select the other polarisation.
THE FOLLOWING IS OF HISTORICAL INTEREST ONLY AND IS NO LONGER NEEDED
If you need to check that you are observing at the right frequency, you can use the vertex radiator to generate a test tone using the following procedure:
Get the on source flagging file for the whole session. Log onto a Solaris machine (e.g. pavo) as observer and run “antfg”:
pavo-101% antfg <year> <dayno start> <dayno end>
This creates an AIPS style flagfile as
pavo-101% antfg 2006 316 323
This creates a flagfile covering range of days 2006/316-323 inclusive. This file should be copied to Epping and put in the vlbi ftp area
/pub/people/vlbi/cal/parkes/logs with the name MonthYear, using a 3 letter abbreviation for the month. E.g.:
> scp antflag vlbi@athena:/nfs/ftp/people/vlbi/cal/parkes/logs/Nov2006.antflag
Note that the flag data for an entire session should be contained in a single file. A CGI script extracts the needed entries for individual experiments.
Tsys values are recorded in
These should be mirrored to Sydney, using the following command logged in to a Marsfield Unix machine as vlbi.
A program SYSTEMP runs on the Vax YOWIE, reading the Synch Demod attached to the AT samplers, near the DAS inputs (upstairs control room).
The inputs to the synch Demod are set up by the user - in recent years I have been using the analogue outputs of the DAS Fine Tuner (FT) for this purpose. This isn't ideal but is the best we have. (See notes below).
The program writes 15-second averages to the file;
where each use of the program creates a higher version of this file.
These can be FTP'd by logging-in to YOWIE (as VLBI, usual pw), Appropriate local Parkes (Solaris) machines to use as an intermediate storage location include sagitta, pavo, pisces, perseus or orion.
$vlbi> sd obs$data:[systemp] $vlbi> ftp <target_machine> .... ftp> put SYSTEMP_G.LOG;356 systemp.355
Once the files are on the Parkes Solaris system you can produce something more usuable with the utility pks_tsys;
sagitta% ~rey052/bin/pks_tsys SYSTEMP input file [SYSTEMP.LOG] : systemp.355 TSYS output file [TSYS] : v215a.tsys Integration interval [ 5.000min] : Diode scale factors [ 1.0000 1.0000] :
which averages the raw numbers with a specified interval (default 5 minutes) and scales the values with user-specified calibration factors. These factors need to be determined from calibration observations e.g. “SPOT”.
The file created looks like;
! PRKS Tsys data from file: systemp.355 ! Tcal A/B = 1.0000 1.0000 * 1.0000 318 09:12:35.2 30.4401 29.6506 ! 0.17 0.20 19 318 09:17:29.6 30.3742 29.7018 ! 0.29 0.31 18 318 09:22:24.0 30.4703 29.6044 ! 0.15 0.13 19 ...
which should be close to the format needed for AIPS. The numbers after the “!” are the RMS values for each channel and the number of values in the average.