CALDB RELEASE NOTES Version: 2.16 CALDB date: 2002-08-15T13:45:00 NOTE: This is not an public release, because the files do not affect CIAO software or user reprocessing. These files will be appear in a later public release of the CALDB. Summary of Changes: A. GTI Limits updates for ACIS and HRC. In $CALDB/data/chandra/acis/bcf/gtilim/ acisD1999-07-22gtilimN0004.fits acisD1999-07-22gtilim_secN0004.fits Replaced file: acisD1999-07-22gtilimN0003.fits in $CALDB/data/chandra/hrc/bcf/gtilim/ hrciD1999-07-22gtilimN0004.fits hrciD1999-07-22gtilim_secN0004.fits hrciD1999-10-04gtilimN0004.fits hrciD1999-10-04gtilim_secN0004.fits hrcsD1999-07-22gtilimN0004.fits hrcsD1999-07-22gtilim_secN0004.fits Replaced files: hrciD1999-07-22gtilimN0003.fits hrciD1999-10-04gtilimN0003.fits hrcsD1999-07-22gtilimN0003.fits B. OBI Tolerances updates: In $CALDB/data/chandra/tel/bcf/otol/ telD1999-07-23otolsN0002.fits telD1999-07-23otols_secN0002.fits Replaced files: telD1999-07-23otolsN0001.fits telD1999-07-23otols_secN0001.fits II. Technical Details A. GTI Limits v4: Changes to GTI limits file (gtilim): The GTI limits files are split into two files for each configuration. The _sec files contain the GTI limits for OBS_MODE = 'SECONDARY' (observations that are not on the sky, such as internal calibrations), while the other files contain the GTI limits for all other OBS_MODEs (all on-the-sky observations). The CALDB boundary value qualifier CBD10001= 'OBS_MODE("SECONDARY")' is added to the primary HDU header for all of the _sec files, whereas for the other files, the boundary value qualifier CBD10001= 'OBS_MODE("POINTING","RASTER","SCAN","SLEW")' is added. Otherwise, the non _sec files are unchanged. The _sec files have all Aspect related, pointing related, HRMA/OBA temperature related, grating related, and SIM motion related GTI limits removed. The limits removed for the _sec files are (explicitly): Aspect related GTI limits: (img_diam_rms:1<=0.5) (img_roll_rms:1<=20.0) (rw_speed_bad:1<=256.0) (AOFF_GAP:1==0) ((0<=asp_sol_status:1)&&(asp_sol_status:1<256)) (ASPTYPE:1!="OBC") Pointing related GTI limits: (fabs(Point_SunLimbAng:1)>=45.0) (fabs(Point_MoonLimbAng:1)>=6.0) (fabs(Point_EarthLimbAng:1)>=20.0) (fabs(Point_RamVectorAng:1)>=0.0) HRMA/OBA temperature related GTI limits: ((-1.4<=HRMA_CAPGRAD0:1)&&(HRMA_CAPGRAD0:1<1.4)) ((-1.4<=HRMA_CAPGRAD1:1)&&(HRMA_CAPGRAD1:1<1.4)) ((289.5<=HRMA_CAPTEMP:1)&&(HRMA_CAPTEMP:1<299.0)) ((289.5<=HRMA_FRWDTEMP:1)&&(HRMA_FRWDTEMP:1<299.0)) ((289.5<=HRMA_AFTTEMP:1)&&(HRMA_AFTTEMP:1<299.0)) ((289.5<=HRMA_TEMP:1)&&(HRMA_TEMP:1<299)) ((-1.4<=OBA_PERIGRAD0:1)&&(OBA_PERIGRAD0:1<1.4)) ((-1.4<=OBA_PERIGRAD1:1)&&(OBA_PERIGRAD1:1<1.4)) Grating related GTI limits: ((GRATING:1!="FAULT")&&(GRATING:1!="MOVING")&&(GRATING:1!="UNKNOWN")) SIM motion related GTI limits: (MOVING:1==F) These GTI limits are relevant only for on-the-sky observations, and not for OBS_MODE = 'SECONDARY'. This change will eliminate erroneous flagging of bad time intervals for secondary mode data. Note that the actual values of all of the quantities will continue to be available in the mission timeline file; only the limit checks are removed. SDP/Pipline/Tool: get_gti_limits B. OBI Tolerances v2: Changes to OBI TOLERANCES: (1) In each file the following line is corrected in the tolerances definition ELEMENT VALUE DATATYPE MATCHTYPE MATCHVALUE GOODNESS VETO ------- ----- -------- --------- ---------- -------- ---- Old value: DETNAM HRC-SI dmTEXT partial HRC-SI 0 0 New value: DETNAM HRC-SI dmTEXT partial HRC 0 0 The added line ensures that an ObI element that corresponds to actual detnam 'HRC-SI' will match an predicted obspar value of 'HRC' with a partial match. This line is ordered after any exact matches, and allows any actual HRC configuration to partially match a predicted detnam of 'HRC-SI' in the obspar. The previous value of HRC-SI for MATCHVALUE was incorrect. (2) Each file has an added line to the tolerances definition ELEMENT VALUE DATATYPE MATCHTYPE MATCHVALUE GOODNESS VETO ------- ----- -------- --------- ---------- -------- ---- DETNAM HRC-SI dmTEXT exact HRC-S 1 0 inserted after the line ELEMENT VALUE DATATYPE MATCHTYPE MATCHVALUE GOODNESS VETO ------- ----- -------- --------- ---------- -------- ---- DETNAM HRC-SI dmTEXT exact HRC-SI 1 0 and before the line ELEMENT VALUE DATATYPE MATCHTYPE MATCHVALUE GOODNESS VETO ------- ----- -------- --------- ---------- -------- ---- DETNAM HRC-SI dmTEXT partial HRC 0 0 (these lines were previously consecutive). The added line ensures that an ObI element that corresponds to actual detnam 'HRC-S' will match an predicted obspar value of 'HRC-SI' exactly and increment the goodness of the match. Previously, such a situation would fall through to the partial match and not increment the goodness. The purpose of this change is to complete the pipeline implementation supporting the hrcparam table in the ocat in DS 6.9. The new ocat hrcparam table records the planned configuration for each HRC observation. The configuration previously represented by detnam 'HRC-SI' (HRC-S detector in imaging mode) will now be represented by detnam 'HRC-S' and the imaging mode information is recorded in the obspar SPECT_MODE parameter and is used to create a window mask corresponding to the detector active area. The detnam value "HRC-SI' is retired in data system release 6.9. This change allows reprocessing of HRC data with an old obspar file to complete successfully. SDP/Pipeline/Tool OBI_DET