Many are delivered with CASA. You need to find your data repository, whose location can vary with installation and operating system.
If you look there you will see ALMA, CARMA, EVLA, etc, and can set the antennalist input to one of them
os.system("ls " + repodir) # alma.out01.cfg # alma.out08.cfg # ... antennalist=repodir+"alma.out20.cfg"
You can also simply set antennalist="alma;0.5arcsec" and simobserve will choose the closest configuration based on the frequency of your sky model.
Others, including your own, possibly fictitious Observatory
To simulate an observation using the same list of antennas in an existing ALMA or VLA measurement set, you can use the analysisUtils script called buildConfigurationFile to construct a configuration file from the antenna location information in the ms.
The configuration files are merely ASCII files with four or five columns: X,Y,Z,diameter, and optional station name. For example for ALMA, the columns are
- UTM-X (Easting; meters).
- UTM-Y (Northing; meters).
- Z (Altitude in meters)
- Diameter (meters). =simdata= uses a primary beam calculated using Airy patterns for the diameters you specify and a 1m diameter circular blockage in the center of each antenna or station. CASA has more accurate primary beams for some observatories, and will used those if available.
The file must begin with header information defining the columns. such header lines begin with "#", and must include at least the observatory name and coordinate system:
# observatory = VLA # coordsys = XYZ
Some coordinate systems require further definitions to uniquely specify them.
|coordsys||definition||X,Y,Z=||other fields required|
|XYZ||ITRF earth-centered||X,Y,Z [m]|
|UTM||easting, northing, altitude [m]||zone, datum, hemisphere|
|LOC||Local tangent plane offsets from COA||offset east, offset north, altitude [m]||observatory must be in CASA (see below)|
|GEO||WGS84 geodetic not yet implemented||latitude, longitude, altitude [m]||datum=WGS84|
The next wrinkle is if you are introducing a new array e.g. SKA, some routines in CASA will look for that observatory in the data repository. clean in particular will complain mightily about not finding the observatory. In principle, both simulation and subsequent inversion/clean should work even if the observatory is not present, but WMMV.
If you have write access to your CASA installation, you can add observatories in either earth-centered ITRF or geodetic WGS84 coordinates. As above, you are looking in the data repository, at
obstable = os.getenv("CASAPATH").split(' ')+"/data/geodetic/Observatories"
You need to open that directory in the CASA table browser browsetable, click to make it editable, add a row, and fill in the fields in the row. If you think other users might want your observatory, please contact the CASA helpdesk to request that it be added universally.
NOTE DEC 2013: If you don't have permission to edit the Observatories table in your CASA installation, you can make your own copy (be sure the use cp -r since the table is a directory with subdirectories), and specify the directory containing your new Observatories table, in a file ~/.casarc with the syntax: