CALDB Public Release Notes Version 1.0 CALDB Date: 2000-03-26T05:00:00 I. WHAT IS CALDB 1.0? CALDB 1.0 is an indexed version of the old ASCDS_CALIB directory, which is used by SDP to select appropriate calibration files by means of an index. CALDB 1.0 is partially compatible with the HEASARC caldb structure which can be accessed from GSFC's HEASARC CALDB web page. In CALDB 1.0, only the calibration (so-called ARD) files required by SDP are actually in the index. CALDB 1.0 is also being used as a repository for CIAO user-specifyable files, which are not yet indexed, as well as the ARDLIB files, which are not read from CALDB by CIAO 1.x. (Version 2.0 of CAIO and CALDB will be more integrated, with CALDB 2.0 being fully indexed for both SDP and CIAO calibration data files.) II. CALDB structure The CALDB directory structure is specified in the internally- maintained and frequently updated "caldb.txt" file, developed by Arnold Rots of SAO. The CALDB has three main directory trees, "docs", "data", and "software" under the main CALDB directory. At the HEAD LAN, the CALDB lives at /data/CALDB/. "docs" has the CALDB version file and shipping MANIFEST files. "software" has the caldb configuration and setup files, such as caldbinit.unix. "data" has the substructure dictated by the keyword settings of the caldb files. The first directory contains the TELESCOP value options, which only include "chandra" for this caldb. Under data/chandra are the INSTRUME value options for chandra for which there are actual CALDB files: acis, ephin, hrc, pcad, sim, and tel. From there the directories divide to accommodate the FITS CCLS0001 keyword (bcf, or cpf). For TEL, which subsumes "grating" and "hrma" options, the directory breaks into hrma and grating, and grating to letg and hetg. The index files reside in the index/ directories under each instrument. HRMA, GRATING, and TEL files are indexed together under tel/index. The CALDB software uses the linked file under each instrument called caldb.indx, which links to one of the real index files under index/. The versioning of the CALDB is maintained by keeping up the configuration of versioned index files under index/. Every time a new file is added to a particular index, the index is first copied to the next version number caldbN000#.indx, and then the information is added for the new file. This results in a new CALDB version as a whole. CALDB version numbers are maintained, along with their corresponding index file configurations and CALDB dates, in docs/chandra/caldb_version/caldb_version.fits. The first item in the last row of this file has the current version of the CALDB. FILENAMES currently indexed under CALDB 1.0: The following files, in their appropriate directories, are what exist in CALDB 1.0. Updates to this will produce replacement files for some of these, or new files and possibly new directories. ACIS branch: $CALDB/data/chandra/acis/bcf/badpix/acisD1999-07-22badpixN0004.fits $CALDB/data/chandra/acis/bcf/badpix/acisD1999-08-12badpixN0001.fits $CALDB/data/chandra/acis/bcf/evtsplt/acisD1996-11-01evtspltN0001.fits $CALDB/data/chandra/acis/bcf/gain/acisD1999-07-22gainN0002.fits $CALDB/data/chandra/acis/bcf/gain/acisD1999-08-13gainN0002.fits $CALDB/data/chandra/acis/bcf/gain/acisD1999-09-16gainN0003.fits $CALDB/data/chandra/acis/bcf/grade/acisD1996-11-01gradeN0001.fits $CALDB/data/chandra/acis/bcf/gtilim/acisD1999-07-22gtilimN0001.fits $CALDB/data/chandra/acis/bcf/gtilim/acisD1999-07-22gtilimN0002.fits $CALDB/data/chandra/acis/cpf/rmf/acisD1999-08-26irmfN0002.fits EPHIN branch: $CALDB/data/chandra/ephin/bcf/geom/ephinD1999-07-22geomN0001.fits HRC branch: $CALDB/data/chandra/hrc/bcf/badpix/hrciD1999-07-22badpixN0001.fits $CALDB/data/chandra/hrc/bcf/badpix/hrcsD1999-07-22badpixN0001.fits $CALDB/data/chandra/hrc/bcf/degap/hrciD1999-07-22gapN0001.fits $CALDB/data/chandra/hrc/bcf/degap/hrcsD1999-07-22gapN0001.fits $CALDB/data/chandra/hrc/bcf/qe/hrciD1999-07-22qeN0003.fits $CALDB/data/chandra/hrc/bcf/qe/hrciD1999-07-22qeuN0001.fits $CALDB/data/chandra/hrc/bcf/qe/hrciD1999-07-22uvisN0002.fits $CALDB/data/chandra/hrc/bcf/qe/hrcsD1999-07-22qeN0003.fits $CALDB/data/chandra/hrc/bcf/qe/hrcsD1999-07-22qeuN0001.fits $CALDB/data/chandra/hrc/bcf/fptest/hrciD1999-07-22fptestN0001.fits $CALDB/data/chandra/hrc/bcf/fptest/hrcsD1999-07-22fptestN0001.fits $CALDB/data/chandra/hrc/bcf/eftest/hrciD1999-07-22eftestN0001.fits $CALDB/data/chandra/hrc/bcf/eftest/hrcsD1999-07-22eftestN0001.fits $CALDB/data/chandra/hrc/bcf/sattest/hrciD1999-07-22sattestN0001.fits $CALDB/data/chandra/hrc/bcf/sattest/hrcsD1999-07-22sattestN0001.fits $CALDB/data/chandra/hrc/bcf/gtilim/hrciD1999-07-22gtilimN0001.fits $CALDB/data/chandra/hrc/bcf/gtilim/hrciD1999-10-04gtilimN0001.fits $CALDB/data/chandra/hrc/bcf/gtilim/hrcsD1999-07-22gtilimN0001.fits $CALDB/data/chandra/hrc/bcf/gtilim/hrciD1999-07-22gtilimN0002.fits $CALDB/data/chandra/hrc/bcf/gtilim/hrciD1999-10-04gtilimN0002.fits $CALDB/data/chandra/hrc/bcf/gtilim/hrcsD1999-07-22gtilimN0002.fits $CALDB/data/chandra/hrc/bcf/fptest/hrcsD1999-07-22fptestN0002.fits PCAD branch: $CALDB/data/chandra/pcad/bcf/align/pcadD1999-08-12alignN0001.fits $CALDB/data/chandra/pcad/bcf/align/pcadD1999-08-12alignN0002.fits $CALDB/data/chandra/pcad/bcf/align/pcadD1999-08-12alignN0003.fits $CALDB/data/chandra/pcad/bcf/align/pcadD1999-08-12alignN0004.fits $CALDB/data/chandra/pcad/bcf/align/pcadD1999-08-12alignN0005.fits $CALDB/data/chandra/pcad/bcf/align/pcadD1999-08-12alignN0006.fits $CALDB/data/chandra/pcad/bcf/ccd/acapD1998-12-14ccdN0001.fits $CALDB/data/chandra/pcad/bcf/cti/acapD1998-09-30ctiN0001.fits $CALDB/data/chandra/pcad/bcf/fdc/acapD1999-08-12fdcN0001.fits $CALDB/data/chandra/pcad/bcf/fdc/acapD1999-08-12fdcN0002.fits $CALDB/data/chandra/pcad/bcf/image/acapD1998-09-18darkN0001.fits $CALDB/data/chandra/pcad/bcf/image/acapD1998-09-18respN0001.fits $CALDB/data/chandra/pcad/bcf/iru/iruD1999-08-12charN0001.fits $CALDB/data/chandra/pcad/bcf/rws/rwaD1999-08-12bspdN0001.fits $CALDB/data/chandra/pcad/bcf/sfma/gyroD1999-08-12sfmaN0001.fits SIM branch: $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0001.fits $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0002.fits $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0003.fits $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0004.fits $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0005.fits $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0006.fits $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0007.fits $CALDB/data/chandra/sim/bcf/pos/simD1999-07-22posN0008.fits $CALDB/data/chandra/sim/bcf/poscorr/simD1999-07-22poscorrN0001.fits TEL branch: $CALDB/data/chandra/tel/hrma/cpf/wpsf/hrmaD1996-11-01wpsfN0001.fits $CALDB/data/chandra/tel/hrma/cpf/rpsf/psfsize.fits $CALDB/data/chandra/tel/hrma/cpf/rpsf/psfsize_19991012.fits Data effects: Most of these files (excluding the N0002 GTILIM files) have been in effect before the switch to the CALDB directory access in SDP, so the change is mostly neutral. However, CALDB 1.0 will have been active beginning with processing dates after DATE=2000-04-05T05:00:00. All data processed after this DATE value will have used CALDB 1.0 to access the above calibration files. Again, no significant effects on processing are expected due to this change in calibration file selection in SDP. The first processing version or ASCDSVER to use CALDB 1.0 is R4CU5.