Data Delivery Procedures
- We perform testing on data formats and structures as well as checking certain
science value ranges, using certify. For history tracking purposes
and clarity of use, comment lines and history records have been inserted into the
header files of all of the data. We check for the existence of this information and
look for concise reasons for data updates. All of these steps have been designed
around certain data quality criteria and functionality.
- All of the data files are given unique new names following a date/time convention, using uniqname.
- If the files delivered are in GEIS format, loopfits and
fitsverify are run to convert from GEIS
to FITS and check the validity of the FITS files.
- check_load is run to check various keywords within the load files
against the same keywords in the data files.
- cdbs_sql_gen is run to generate the sql statements for installation
into CDBS, and installs a lock on the particular delivery number generated.
- run_delivery_sql installs the data and/or pointers into the database.
- check_cdbs is then run to make internal consistency checks on the
database.
- opus_sql_gen generates a sql file for opus, representing the
installation instruction software.
- update_ga_date is a last step in "locking-in" the delivery
to CDBS, updates the general_availability_date within the database, and releases
the lock on the delivery number.
- opus_catalog generates a catalog file for OPUS.
- The catalog file and the sql file, both for OPUS, and the reference data (FITS files)
are transfered to a special directory in which an automatic process moves everthing over
to OPUS.
- The reference data are then archived to DADS using a tool
called cdbs_make_request.
- Finally, the reference data is moved to its final resting place, the CDBS
online archives.
Once OPUS has installed the data, the ground system has the latest reference calibration
data to be used for any observations coming through the system. A feedback mechanism
brings information back to CDBS from OPUS on the verification of installation and on the
exact installation time.
Additional steps of operations involves entering paper forms which track the whole process
into the CDBS library, and notifying Instrument Scientist of the installation into OPUS.
For a pdf copy of the delivery procedures (which have been described above), click
on Delivery Procedures for all instrument data.
To get a pdf copy of the delivery form, click on
Data Delivery Form.
