CALDB PUBLIC RELEASE NOTES VERSION 2.21 CALDB EFFECTIVE DATE: 2003-02-14T16:00:00 Public Release Noon, Feb. 14, 2003 I. Summary of Changes A. Repaired ACIS -120C CTI-corrected FEF (v2) Location: $CALDB/data/chandra/acis/cpf/fefs/ Filename: acisD2000-01-29fef_pha_ctiN0002.fits The syntax error reported on the caveats page for version N0001 of this file has been repaired and the new file completely tested. It is now ready for use, and the workaround in the thread is no longer necessary. B. ACIS CTI-corrected background files The availability of CTI-correction for events in Chips 0, 1, 2, 3, and 6 means that background blank-field files should be provided for these chips which are also corrected. The CTI-corrector will NOT work on the existing background sets, so the sets must be made ready before going in the CALDB. For the remaining five chips, the same background sets will work for both CTI and non-CTI corrected events files. So, we have configured the CALDB so that you get whatever you need by following the thread, and running the new version of acis_background_lookup. Location: $CALDB/data/chandra/acis/bcf/bkgrnd/ Files: CTI-corr: acis1sD2000-01-29bkgrnd_ctiN0001.fits acis1sD2000-12-01bkgrnd_ctiN0001.fits acis236sD2000-01-29bkgrnd_ctiN0001.fits acis236sD2000-12-01bkgrnd_ctiN0001.fits acisiD2000-01-29bkgrnd_ctiN0001.fits acisiD2000-12-01bkgrnd_ctiN0001.fits New, but non-CTI-corr: acis57sD2000-01-29bkgrndN0003.fits acis7iD2000-01-29bkgrndN0003.fits acis7sD2000-01-29bkgrndN0003.fits acis8sD2000-01-29bkgrndN0003.fits acis57sD2000-12-01bkgrndN0002.fits acis7iD2000-12-01bkgrndN0002.fits acis7sD2000-12-01bkgrndN0002.fits acis8iD2000-12-01bkgrndN0002.fits acis8sD2000-12-01bkgrndN0002.fits C. HETG -1 order LSFPARM files Location: $CALDB/data/chandra/tel/grating/hetg/cpf/lsf/ FILES: acismeg-1D1999-07-22lsfparmN0003.fits acisheg-1D1999-07-22lsfparmN0003.fits Now it is possible to calculate -1 order observation- specific grating RMFs using mkgrmf. D. GTI Limits: Relaxed Roll Tolerances (SDP only) (These new files have no affect on CIAO users at all.) For ACIS LOCATION: $CALDB/data/chandra/acis/bcf/gtilim/ Files:acisD1999-07-22gtilimN0005.fits acisD2002-11-15gtilimN0002.fits For HRC Location: $CALDB/data/chandra/hrc/bcf/gtilim/ Files: hrciD1999-07-22gtilimN0005.fits hrciD1999-10-04gtilimN0005.fits hrciD2002-11-15gtilimN0002.fits hrcsD1999-07-22gtilimN0005.fits hrcsD2002-11-15gtilimN0002.fits II. Technical Details: A. ACIS CTI-corr responses (FEF) v2: The version 1 of this file had a syntax error in the VFUNC keywords in the principal HDU: 0056 VFUNC1 GAUSS1D ( PHA ; G1A) + GAUSS1D ( PHA ; G1B) String Component 1 0057 VFUNC2 GAUSS1D ( PHA ; G2A) + GAUSS1D ( PHA ; G2B) String Component 2 0058 VFUNC3 GAUSS1D ( PHA ; G3A) + GAUSS1D ( PHA ; G3B) String Component 3 0059 VFUNC4 GAUSS1D ( PHA ; G4A) + GAUSS1D ( PHA ; G4B) String Component 4 0060 VFUNC5 GAUSS1D ( PHA ; G5A) + GAUSS1D ( PHA ; G5B) String Component 5 0061 VFUNC6 GAUSS1D ( PHA ; G7) String Component 6 0062 VFUNC7 POWLAW1D ( PHA ; P0) String Component 7 0063 VFUNC8 ERF ( PHA ; E1) String Component 8 0064 VFUNC9 ERFC ( PHA ; E2) String Component 9 For VFUNC1-5, everything behind the "+" sign was being ignored by the software. This meant that the low-level wings in the CTI-corr responses were suppressed. This didn't turn out to be a very strong effect, so it went unnoticed. The effect was expected to be stronger for the NON-CTI responses calculated for chips 4,5,7,8,9, however the effect was only marginal even for these cases. In the new version 2 of this file, the VFUNC keywords now read: 0060 VFUNC1 GAUSS1D ( PHA ; G1A) String Component 1 0061 VFUNC2 GAUSS1D ( PHA ; G2A) String Component 2 0062 VFUNC3 GAUSS1D ( PHA ; G3A) String Component 3 0063 VFUNC4 GAUSS1D ( PHA ; G4A) String Component 4 0064 VFUNC5 GAUSS1D ( PHA ; G5A) String Component 5 0065 VFUNC6 GAUSS1D ( PHA ; G1B) String Component 6 0066 VFUNC7 GAUSS1D ( PHA ; G2B) String Component 7 0067 VFUNC8 GAUSS1D ( PHA ; G3B) String Component 8 0068 VFUNC9 GAUSS1D ( PHA ; G4B) String Component 9 0069 VFUNC10 GAUSS1D ( PHA ; G5B) String Component 10 0070 VFUNC11 GAUSS1D ( PHA ; G7) String Component 11 0071 VFUNC12 POWLAW1D ( PHA ; P0) String Component 12 0072 VFUNC13 ERF ( PHA ; E1) String Component 13 0073 VFUNC14 ERFC ( PHA ; E2) String Component 14 and we now confirm the entire function is implemented by mkgrmf. C. -1 Order HEG/MEG LSFPARM files The HETG SDS team has developed new line-spread function (LSF) parameter files applicable to the -1 order of HEG and MEG. See http://space.mit.edu/CXC/LSF/LSF_0002/index.html for general information concerning development of LSF parameters. From Bish Ishibashi (HETG team): "The HETG SDS team (Bish Ishibashi) has developed calibrations for the line-spread-function (LSF) parameters relevant to the -1 order of HEG and MEG with ACIS-S. Paired with the existing +1 order files already in CALDB, these data allow a reasonably thorough representation of the grating RMF for the entire first-order distribution pattern. Certain asymmetries may now be accounted for more precisely in the first-order response, making more detailed line-profiling possible. Certain caveats which are applicable to these data are tabulated in the following document: http://space.mit.edu/CXC/LSF/LSF_0002/LSF_cavea.html "These data are derived from detailed fits of monoe-energetic beam observations simulated with MARX version 4.0 [HETG calibration benchmark], using two pair of a "Gaussian + Lorentzian" model for the line peaks and wings." D. GTI_LIM v5/2: IMG_ROLL_RMS tolerances broadened from 20 to 40 arc seconds: Revised GTI limits files are provided for on-the-sky observations (OBS_MODEs other than 'SECONDARY'). The PCAD image roll limit (img_roll_rms) is revised from 20 arcsec to 40 arcsec per the recommendation of the SOT Aspect team. The increased value will allow observation time intervals with a single FID light to be considered good time. The value was determined empirically from a sample of existing single FID light data, which have image roll values in the range 20-40 arcsec. The following PCAD related GTI limit is changed: From: (img_roll_rms:1<=20.0) To: (img_roll_rms:1)<=40.0) Relevance: May be installed at any time in SDP.