AIPS HELP file for FITTP in 31DEC19
As of Mon Dec 10 16:46:38 2018
FITTP: Task to write maps or uv data on a FITS-tape.
DOALL -1.0 1.0 1 (T) do all, -1 (F) do 1st.
INNAME Image name(name). Standard.
INCLASS Image name(class). Standard.
INSEQ 0.0 9999.0 Image name(seq. #).
INDISK 0.0 9.0 Disk drive #. 0 => any
INTYPE File type. Blank => any
OUTTAPE 0.0 9.0 Tape drive #. 0 => 1
Disk file name
DOEOT -1.0 1.0 1 (T) go to end tape first.
FORMAT 0.0 4.0 tape format: 0 => 3.
1 for 16-bit integer
2 for 32-bit integer
3 for 32-bit IEEE
4 for 8-bit integer maps
BLOCKING 0.0 10.0 tape blocking factor (<= 10)
CATNO Limit range of catalog number
Use: FITTP converts the standard header and map or uv data and writes
it on a output tape in the FITS format. The 1st image or all
images that match the input parameters can be written. The tape
is left following the End-of-file mark which terminates the last
file written. All Clean Components extension files for maps or
ANtenna files for uv data will be written with the image in a
special TABLES format (following the image itself in the file).
Other tables-format extension files will also be written.
When using this task (or FITAB) to transfer data to another
software system such as CASA, users should be aware of
limitations in this process. The images and UV data files
should be transferred flawlessly. However, the other software
systems may not understand the tables accompanying the files.
For images, there are Clean Component (CC) and Clean Gaussian
(CG) tables. CC files are understood on occasion, but CG files
are rarely understood. For UV data files there are a wide
variety of tables. Antenna (AN) and Source (SU) files are
usually understood, but Flag (FG), Calibration (CL and SN),
SysPower (SY), Bandpass (BP), Polarization D-terms (PD), etc.
are unlikely to be understood. Use SPLIT or SPLAT to apply
these tables to the data and then FITTP the result. Note that
few packages understand uv data written in tabular form by
FITAB. OBIT and other Parseltongue-based packages often use
AIPS for some or much of their processing and so are more likely
to understand the multiple tables and they do accept FITAB
DOALL......True (> 0) means do all files matching the input
parameters, false (<= 0) means do the 1st match
INNAME.....The input image name (name). Standard defaults.
INCLASS....The input image name (class). Standard defaults.
INSEQ......The input image name (seq. #). 0 => any if DOALL
is true, 0 => highest if DOALL is false.
INDISK.....The input disk unit #. 0=> search all disks in
order for file meeting the other criteria.
INTYPE.....The input data type (MA or UV or ' ' for either)
OUTTAPE....The output tape unit #. 0=> 1.
DATAOUT....The name of a disk file into which to write.
If blank then write to tape. If output is to a
disk file, only 1 file can be written (DOALL=-1).
The name is limited to 48-characters and must be
in the form
where is the remote computer name,
is the environment variable (logical
name) for the disk area in which the file named
is to be stored. is usually
omitted when the file is local to the current
DOEOT......True (> 0) means to advance the tape to the end
of information (double EOF) before writing, false
means write wherever the tape is now positioned.
Note: set DOEOT true ONLY if you think that there
are already FITS data files on the tape AND if
you wish to preserve them.
FORMAT.....Code to tell what format to be used in writing the
main uv or image data portion of the file as
1 for 16-bit integers - only images
2 for 32-bit integers - only images
3 for 32-bit IEEE floating point - images and
required for uv data
4 for 8-bit integers - only images
Default: 0 => 3.
If you want to import your FITS data into another
system, make sure that it is able to read the
format that you have selected.
BLOCKING...Code to tell what blocking factor to be used in
writing the whole file
Default: 0 => 10.
Considerations: (a) blocking factor <= 10.
(b) AIPS releases prior to 15APR87 can read
only FORMATs 1 and 2. Do not use blocking
if you may go to an earlier release of AIPS.
This same consideration also applies to
most other FITS readers around the world.
(c) Blocking is ignored when writing to disk
rather than tape.
(d) Larger blocks use fewer I/O operations
making tape reads and writes more efficient.
CATNO......Range of catalog numbers over which the operation is to
take place. CATNO(1) <= 0 -> 1; CATNO(2) < CATNO(1) ->
very large. BE CAREFUL with this - it limits the range
allowed independent of the value of DOALL. CATNO=0 is
recommended unless you intend limitations.