Skip to the navigation links
Last modified: 28 December 2009

URL: http://cxc-newtest.cfa.harvard.edu/ciao4.2/bugs/specextract.html

Bugs: specextract


Bugs

  1. Calibration necessary for the script to choose mkacisrmf instead of mkrmf

  2. # mkacisrmf (CIAO 4.2): WARNING: No files found matching CALDB search:
    ...
    query=CTI_CORR.eq.NO.and.CTI_APP.eq.PPPPPSPSPP (03 Mar 2008)


Bugs

  1. Calibration necessary for the script to choose mkacisrmf instead of mkrmf

    When determining whether to use mkrmf or mkacisrmf, the script does a CALDB lookup to compare the calibration applied to the event file and the most recent file available in the CALDB. This means that the data needs to have been processed with very newest calibration, not just a "good enough" version; that is, even if the new calibration will have a minimal effect on your data, specextract requires that it be applied for the "use mkacisrmf" switch to be triggered.

    Users who don't wish to reprocess can still use specextract, but run mkacisrmf afterwards to create new RMF files.

  2. # mkacisrmf (CIAO 4.2): WARNING: No files found matching CALDB search:
    ...
    query=CTI_CORR.eq.NO.and.CTI_APP.eq.PPPPPSPSPP (03 Mar 2008)

    Some CTI-corrected data have CTI_CORR=yes in the header, but no CTI_APP keyword. In this case, mkacisrmf (which is called by specextract) incorrectly uses "CTI_CORR.eq.NO" in the CALDB query, as shown in the warning message, when it should be "CTI_CORR.eq.YES". The ACIS CTI Correction why topic explains the difference between the CTI_CORR and CTI_APP keywords.

    Workaround:

    Run acis_process_events, e.g. by following the Reprocessing Data to Create a New Level=2 Event File thread, so that the CTI_APP keyword is added to the header.

    specextract will run correctly on the reprocessed data.


Last modified: 28 December 2009