Skip to the navigation links
Last modified: 28 December 2009

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

Bugs: mkwarf


Caveats

  1. ERROR: Max egridspec energy=10 above max FEF energy=9.886

  2. ARF over bad columns and node boundaries (12 Dec 2007)

Bugs

  1. Issue with the WMAP when the source is at a chip edge

  2. # mkwarf (CIAO 4.2): ERROR: Could not map response region to FEF region (04 Jun 2008)


Caveats

  1. ERROR: Max egridspec energy=10 above max FEF energy=9.886

    mkwarf is required to compute and write a "weightfile" output file which contains FEF regions for use by mkrmf. If the energy range in the input RMF is greater than that in the FEF files, you get an error like:

    ERROR: Max egridspec energy=10 above max FEF energy=9.886
    

    Although the comparison to the FEF files is unnecessary in this case, there is currently no way to turn it off (e.g. set the weightfile to "NONE").

    Workaround:

    In order to avoid the error, it is necessary to define an energy range for mkacisrmf that falls within the boundaries of the FEF files, i.e. approximately 0.28 - 9.8 keV. See the Creating an RMF to match an extracted spectrum section of the mkacisrmf analysis thread for an example command.

  2. ARF over bad columns and node boundaries (12 Dec 2007)

    The combination of the TDET and single pixel changes in CIAO 4.0 causes mkwarf to skip bad pixels. This is a problem if the observation is over a bad column or node boundary, in which case the ARF is significantly over-estimated.


Bugs

  1. Issue with the WMAP when the source is at a chip edge

    If the observation has large dy & dz offsets in the aspect solution file and they are quite variable during the observation, the tool will fail with a CALDB error. The large (and varying) offsets cause the mapping from DET to CHIP coordinates to fail and the tool cannot determine which response calibration file to use in creating the RMF.

  2. # mkwarf (CIAO 4.2): ERROR: Could not map response region to FEF region (04 Jun 2008)

    This issue is often related to a mkwarf change in CIAO 3.4: using single pixel resolution when evaluating the wmap. The edge of the wmap (in detector coordinates) ends up getting mapped to chip coordinates at 1024.5 which is rounded to 1025. It then tries to find the FEF region that converts chipy=1025 (for which there are none) and thus fails.

    Workaround:

    Supply the aspect solution in the asolfile parameter when running mkwarf. The aspect shifts the coordinate transform back to where the pixels all map to good chip coordinates.


Last modified: 28 December 2009