Untitled

SCO3: gns almaop:~ 3089 > cd /alma/ACS-10.1/ACSSW/config/
SCO3: gns almaop:/alma/ACS-10.1/ACSSW/config 3090 > cat antennaCAIMap-SCO3.dat.ACA
# This file contains the information needed to map antenna names to
# CAIs (correlator antenna inputs).  This file will be used until the
# TMCDB supports this mapping.
# Rules on editing this file are as follows:
#   1.- All comments are preceeded by the pound sign on the first column.
#   2.- All lines must be less that 80 chars!
#   3.- Each line/entry consists of a CAI number and its associated
#   antenna name separated by a comma.
#   4.- There must be one entry per CAI in use up to the maximum number
#   supported by the correlator in use: 2 for the 2-antenna, 16 for a single quadrant,
#   32 for two quadrant, and 64 for the full correlator.
#   5.- CAI numbers must be unique and have the following ranges:
#   0..1 for 2-antenna, 0..15 for single quadrant, 0..31 for two
#   quadrant, and 0..63 for the full correlator.
#   6.- Antenna names must be unique and conform to
#       ANTD-36.00.00.00-004-A-GEN
#
# Breaking any of these rules will cause the CCC to throw a lifecycle
# exception during startup!
# This file is read only once during a session by the CCC (more often
# by the CDP Master) so changes to it will not affect the system until
# a re-initialization of the CORR subsystem has taken place.
# The sample entries below are useful for a single quadrant where all
# CAIs are used or for a dual quadrant or full correlator where only
# the first 16 CAI inputs are in use.  Were these entries to be used
# in a 2-antenna correlator, the CCC would throw a lifecyle exception
# on startup.
0, PM01
1, PM03