The GO table is the principal way of specifying a list of sources and coordinates to be observed. Examples of tables can be found in the directory: /home/astro-util/users For example, it may be instructive to look at the tables: example.obs pulsar.obs calibrators.obsSee the GBT Observing Tables document for an introduction to GO tables.
Glish setup scripts:
Create a script following the examples below.
To run a script, type:
$ source /home/gbt/gbt.bash
$ glish -l scriptname.g
Examples of scripts:
HI_setup.g [21cm spectral line: position switching]
HIfs_setup.g [21cm spectral line: frequency switching]
point_setup.g [Pointing/continuum at 3.6 cm]
H2O_setup.g [H20 line double beam switched]
OHsetup.g [Four OH transitions, freq. switching]
CLEO save/restore:
(refer to Starting CLEO, if necessary)
TO SAVE the system configuration:
From the CLEO launcher, select "Utilities/Tools-->SaveAllConfiguration"
You will be asked to select the devices whose parameters you want to save.
Select only the receivers and devices that you need.
In general, do not include the antenna itself.
Then give the file a name with a .tcf extension, and save it in
the directory ~gbtops/Cleo_tcf
TO RESTORE a saved system configuration:
From the CLEO launcher, select "Utilities/Tools-->LoadAllConfiguration"
Find the save file, usually in the ~gbtops/Cleo_tcf directory,
open it. You then are asked to select the desired managers and
click "Load".
Make sure all managers are "ON" before running scripts or restoring
the CLEO state.
Many managers are put into the "standby" or "off" states when not
in use. Make sure all the managers that are needed for the experiment
are in the "on" state before starting to set them up.
Note that the BCPM manager is a special case and must be turned on
after the BCPM user interface is initialized.
GO may be run on Linux or Solaris. The computers marsha or victor are recommended. 1. Versions. Typically the stable version of AIPS++ is used although the correct version is specified in the /home/gbt/gbt.bash file. For the gbtops account this file is automatically sourced when you login. 2. Start GO. Type in any terminal or xterm window: % GO Or if you need to deselect a device: % GO T 3. Debugging GO. ===> If GO "hangs-up" on the Antenna: This is a glish race condition. Try % GO T n where n is an integer number. Sometimes several tries with different numbers will be necessary. Typically the number should be increased on successive attempts. A good first try is: % GO T 10 ===> If "GO T" crashes on start-up: This is almost always due to the fact that GO "remembers" the previous "Observing Type" that you used and tries to startup in that mode again. When the device for that "Observing Type" hasn't been selected then GO goes down in flames. There are two work-arounds for this problem (until GO can be debugged for this problem which is currently at a low priority): (i) Delete the "go_state" file and then restart GO. This will bring GO up in the default observing type of "Continuum". This will work as long as the DCR is selected. This also causes GO to forget the observers name and the log file name. (ii) Start GO in its simulation mode using the following commands (bash shell example) % source /home/gbt/gbt.bash % export GBT_SIMULATOR=T % GO Change the "Observing Type" to something that will be valid given the devices that you will be de-selecting. Then exit GO. Now start GO in the real mode. % unset GBT_SIMULATOR % GO T
Select "scan coordinator" from the "other panels" button on the GO screen. Make sure the desired receiver and back end are included in the scan coordinator. In general, the following devices should also be included: Antenna, LO1, IFManager, IFRack, ConverterRack, SwitchingSignalSelector, AnalogFilterRack, Measurements. Set the first scan number. This will be automatically incremented as each scan is observed.Back to the top
In the main GO screen, select the Observing type, receiver,
switch mode, and observing procedure.
Set the observing frequency.
Set the velocity definition and rest frame, if doing Doppler
tracking.
Bring up the screen from the "other panels" button for the
specific back end, to set up additional options not available
from the main GO screen.
Back to the top
To verify that things are set up right, use various of the CLEO screens for the different devices: - IF Manager: This shows all the connections and filters in the path from the receiver to the back end. Check that they are as expected. In some cases it is necessary to select a different cabling file -- beware! - LO1: Check that the sky frequency (F0) is right. The IF1 should be: 1080 MHz for prime focus receivers. 3000 MHz for receivers 1_2GHz, 4_6GHz, 8_10GHz, 12_18GHz 6000 MHz for receivers 2_3GHz, 18_26GHz. If doing Dopper tracking, check that the reference system and velocity definitions are right. If doing frequency switching, check the frequency offsets and switching mode is right. Check that the switches are set to connect the receiver to the LO. - Receiver CLEO screen: Check RF filters. Check Polarization mode. Check that the LO power is about 4.5 to 5.5 volts. If not, adjust this in the LO1 screen. - IF Rack: Check that the desired receiver is selected. Check that the IF filters are set correctly. - Converter Rack: Check the desired back end is connected. Check the LO2 frequency. - Analog Filter Rack: Only needed if using the Spectrometer (i.e., the high-speed correlator) Check the correct filter is selected: 50-100MHz (if using 50 MHz bandwidth); 100 MHz converters 25-37.5MHz (if using 12.5 MHz bandwidth); 100 MHz converters 0.8-1.6GHz (if using 800 MHz bandwidth); 1.6 GHz samplers. 0.8-1.0GHz (if using 200 MHz bandwidth); 1.6 GHz samplers.Back to the top
IARDS should be run on a Linux machine. The computer 'naiad' is
recommended.
1. Start IARDS.
% iards (or IARDS)
{remember to set the RTD (real-time display) button in the
GO screen to "yes", if you want to use IARDS !}
2. Debugging IARDS.
see IARDS
Back to the top
Currently it is not recomended to use the load configuration options for any device on gbtaio1 and gbtaio2. These include the LO1, all receivers, and the IF rack. 1. Start CLEO. % cleo Or to launch a specific device (e.g., IF rack) % cleo ifrackBack to the top
(Currently version 3.4.1). To check the version of M&C type: % gbtversion
A script can be sourced to convert from real to simulator mode. % source controlRealGBT.bash (For real mode) % source controlSimulator.bash (For simulator mode)
YGOR managers for the desired receiver(s) and back ends need to be checked. In all cases, LO1, IFRack, IFManager, and ConverterRack will be used. In most cases, the AnalogFilterRack and Switching signal selector will also be used.
Again, the telescope operators will usually take care of this.
Each device or manager is accessed through a CLEO screen.
(Start the CLEO screen by typing:
cleo
[then select the desired device from the launch menu])
Bring up the CLEO MESSAGES screen.
Each manager should be turned "on", if it is not already on.
Check the state and status. These are normally displayed at
the bottom of the cleo screen.
The state should be "ready", and the status should be "clear"
If not, call for help. The message window should indicate the
error condition.
Check the three boxes labelled "M", "A", and "T"
(for manager, accessor, and transporter).
These boxes should all be green. If any of these boxes is red,
something probably needs to be re-booted.
Back to the top
It doesn't hurt for the observer to double check: a. The desired receiver is in position. b. The correct pointing model is installed. Dana Balser summarized the present best values for GBT pointing models. c. Focus tracking, pointing model, refraction are all enabled.Back to the top
The GBT is a facility of the National Science Foundation