asn_table (interactive mode)


The program "asn_table" is run either as an internally polling pipeline process or an interactive program that requires a pipeline resource file. The program generates any type of association file that can be generated in the OPUS pipeline. The type of association file is determined by the choice of resource file assigned with the "-r" option. For all association files, the format of the FITS table is the same. There are three formats of FITS headers: FGS, STIS, and a common format for other instruments. The FGS format does not require any keyword values from other FITS files and the asn_table program can be run from a empty default directory if the FGS resource file "bldasn" is used. For FGS format the information about the presence of both exposure amd product members comes exclusively from the OPUS database table "asn_members".

For STIS, the resource file is "asnsti" and the presence of members is determine by the existence of a member file in the default (SIS) directory with the extension ".pkx". The ".dgx" file is also required for the first present member of the association to set keywords for the association FITS header.

For non-STIS assocations, the resource file is "asnnic" or "asnacs" and the presence of members is determined by the existence of a FITS member file in the default (CAL) directory with the extension " _raw.fits". The first raw file found is read to set keywords for the association FITS header.

For ACS there are two states for the association. The pre-calibration version has all the present flags for the planned products set to "F". The post-calibration version has the present flags set by using the database table "asn_members".

For FGS tables, all the members dataset names in the FITS table have the FGS datatype "J" for the last character of the dataset name.

For non-FGS tables, the member dataset name in the FITS table has the datatype found in the default directory. If the file is not found in the default directory, then  the member name ends in "*" and the present flag is set to "F".

For testing the cataloging of associations with  missing members and products, leading to the insertion of "assoc_orphan" table entries in the ARCH database, the contents of the header of the association table does not matter. There are two formats to run "asn_table" with the "bldasn" resource file. The second format is for testing.

   > asn_table -r bldasn  <asn_id>                : for normal FGS asn tables

   >asn_table -r bldasn <asn_id>.<did>       : for FGS header with science member names

The <asn-id> is the nine-character association ID that ends in "0" and <did> is the OSF data ID used in the science pipeline for association processing

The ACS has two kinds of asn tables: pre-calibration and post-calibration. To create an ACS asn table with the correct header that has the desired  product presence flags, there are two formats to run "asn_table" with the "asnacs" resource file.

   >asn_table -r asnacs <asn_id>                 : for pre-calibation product present flags

   >asn_table -r asnacs <asn_id>.aca           : for post-calibation product present flags

Using either format with other science resource files should make no difference since the pre-calibration product present flags are not changed by calibration processing.