Creating ACIS RMFs with mkacisrmf

ACIS GRADED Mode Data

There is limited use for mkacisrmf when working with data taken in GRADED mode. The data must have the time-dependent gain adjustment applied; there is no CTI correction for GRADED mode.

unix% dmkeypar acis_evt1.fits DATAMODE echo+
GRADED

It is appropriate to use mkacisrmf for observations taken in GRADED mode with the source on a back-illuminated chip (ACIS-S1 or S3) only. For these chips, run mkacisrmf for the extracted spectrum case or the specific location case, depending on which best suits the data analysis.

Responses for the front-illuminated chips in GRADED mode data should still be created by running mkrmf.

Running specextract

Since calibration is only available for the two chips in GRADED mode, the specextract script will use mkrmf to create the RMF response files. If your source is on ACIS-S1 or S3, follow the instructions in the Using mkacisrmf with the specextract script section to create a new RMF file with mkacisrmf.

ACIS -110 C Data

There is limited use for mkacisrmf when working with data taken at the -110 C focal plane temperature. The data must have the time-dependent gain adjustment applied; the TGAIN calibration for -110 C was first released in CALDB 3.4.3. There is no CTI correction for this temperature.

unix% dmkeypar acis_evt1.fits FP_TEMP echo+
163.952042

It is appropriate to use mkacisrmf for observations taken at -110 C with the source on a back-illuminated chip (ACIS-S1 or S3) only.

For these chips, run mkacisrmf as shown in the extracted spectrum case or the specific location case, depending on which best suits the data analysis. However, in either case, the infile parameter must be set to the version N0005 P2_RESP file:

unix% pset mkacisrmf \
      infile=$CALDB/data/chandra/acis/cpf/p2_resp/acisD2000-01-29p2_respN0005.fits

Responses for the front-illuminated chips at -110 C should still be created by running mkrmf.

Running specextract

Since calibration is only available for the two chips, specextract script will use mkrmf to create the RMF response files. If your source is on ACIS-S1 or S3, follow the instructions in the Using mkacisrmf with the specextract script section to create a new RMF file with mkacisrmf.

A. Creating an RMF to match an extracted spectrum

This method is the recommended way of constructing RMFs with mkacisrmf.

In this scenario, the user has extracted a spectrum from a given region using dmextract and wishes to compute a matching RMF. For example:

unix% dmextract \
      "data_evt2.fits[(x,y)=circle(4232,3289,30)][bin pi=1:1024:1]" \
      test_src.pi  wmap="det=8"

unix% mkacisrmf infile=CALDB \
      outfile=test_wrmf.fits \
      energy=0.3:9.5:0.005 \
      channel=1:1024:1 \
      chantype=PI \
      wmap=test_src.pi \
      asolfile=pcadf084244404N001_asol1.fits \
      gain=CALDB

The wmap option in the call to dmextract creates a weight map (see the documentation for dmextract) which mkacisrmf will use to create a counts-weighted RMF over the extraction region. The WMAP is stored in an extension of the spectrum file.

mkacisrmf creates a weighted RMF appropriate for the spectral extraction region. The asolfile parameter is set to the observation-specific aspect solution, which is used to derive the correct instrument coordinates for the WMAP. The energy range is chosen as 0.3:9.5:0.005 in order to avoid an error from mkwarf later in the analysis.

The infile parameters is set to "CALDB" so that the tool will use the information in the wmap file header to determine the P2_RESP calibration file to use. Similarly, the gain parameter should be set to "CALDB" in order to ensure that the gain file which matches the P2_RESP file is used.

If you prefer, it is acceptable to give a full path to the gain file in the CALDB, e.g.

unix% pset mkacisrmf \
      gain=$CALDB/data/chandra/acis/bcf/gain/acisD2000-01-29gain_ctiN0006.fits

The corresponding mkrmf syntax is:

unix% mkrmf infile=CALDB outfile=sources.wrmf \
      axis1="energy=0:1" axis2="pi=1:1024:1" weights=sources.wgt

B. Creating an RMF at a specific location

For this case, it is assumed the user wishes to create an RMF file for a specific location on one of the ACIS CCDs, independent of a given dataset or extraction region. In this situation, the infile and gain filenames must be supplied, since the tool does not have access to any source data to determine which calibration files should be used.

Determine which gain file was used in the data processing:

unix% dmkeypar evt2.fits gainfile echo+
/soft/ciao/CALDB/data/chandra/acis/bcf/gain/acisD2000-01-29gain_ctiN0006.fits

This event file has been reprocessed with the version 6 gain file.

Choose the mkacisrmf calibration file (called a "P2_RESP" file). The P2_RESP and gain files are released in pairs of matching versions, so simply choose the file which has the same "N000x" version as the gain:

unix% ls -1 $CALDB/data/chandra/acis/cpf/p2_resp/
acisD2000-01-29p2_respN0002.fits
acisD2000-01-29p2_respN0003.fits
acisD2000-01-29p2_respN0004.fits
acisD2000-01-29p2_respN0005.fits
acisD2000-01-29p2_respN0006.fits

For this gain, acisD2000-01-29gain_ctiN0006.fits, use the acisD2000-01-29p2_respN0006.fits file as the infile parameter.

When running mkacisrmf, be sure that the path to the input response and gain files is correct for the local CALDB installation.

unix% mkacisrmf \
      infile=$CALDB/data/chandra/acis/cpf/p2_resp/acisD2000-01-29p2_respN0006.fits \
      outfile=location_rmf.fits \
      wmap=none \
      energy=0.3:10.0:0.005 \
      channel=1:1024:1 \
      chantype=PI \
      ccd_id=7 \
      chipx=645 \
      chipy=10 \
      gain=$CALDB/data/chandra/acis/bcf/gain/acisD2000-01-29gain_ctiN0006.fits 

This command creates an RMF at a position of (645, 10) in CHIP coordinates on CCD 7.

The corresponding mkrmf syntax is:

unix% mkrmf \
      infile="$CALDB/data/chandra/acis/cpf/fefs/acisD1999-09-16fef_phaN0002.fits[FUNCTION][ccd_id=7,chipx=641:672,chipy=1:32]" \
      outfile=3c273.rmf axis1="energy=0.1:11.0:0.01" axis2="pi=1:1024:1"

C. Using mkacisrmf with the specextract script

specextract, a script for creating ACIS spectra, has the ability to determine when mkacisrmf should be used in place of mkrmf.

specextract reads the source and background file header keywords to determine when the observation was taken and what calibration has been applied. The script then 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 the 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 and run mkacisrmf afterwards to create a new RMF file. This approach is also appropriate for users who have run specextract on GRADED mode or -110 C data and want to create an RMF for a source on ACIS-S1 or S3.

unix% dmkeypar acis_evt2.fits GAINFILE echo+
acisD2000-01-29gain_ctiN0005.fits

Since this file has an older CTI-corrected gain file applied, specextract used mkrmf to create the RMFs. The version N0005 calibration is sufficient for mkacisrmf, though, so it is possible to run the tool independently of the script to create a new response file.

Choose the mkacisrmf calibration file (called a "P2_RESP" file). The P2_RESP and gain files are released in pairs of matching versions, so simply choose the file which has the same "N000x" version as the gain:

unix% ls -1 $CALDB/data/chandra/acis/cpf/p2_resp/
acisD2000-01-29p2_respN0002.fits
acisD2000-01-29p2_respN0003.fits
acisD2000-01-29p2_respN0004.fits
acisD2000-01-29p2_respN0005.fits
acisD2000-01-29p2_respN0006.fits

For this gain, acisD2000-01-29gain_ctiN0005.fits, use the acisD2000-01-29p2_respN0005.fits file as the infile parameter.

If you intend to use XSpec instead of Sherpa to model and fit the data, read the "Matching the ARF and RMF energy grids" caveat before continuing.

Now run the tool:

unix% mkacisrmf \
      infile="$CALDB/data/chandra/acis/cpf/p2_resp/acisD2000-01-29p2_respN0005.fits" \
      outfile=acis_new_rmf.fits \
      energy=0.3:10.0:0.005 \
      channel=1:1024:1 \
      chantype=PI \
      wmap=acis_src1.pi \
      asolfile=pcadf084271087N001_asol1.fits \
      gain=$CALDB/data/chandra/acis/bcf/gain/acisD2000-01-29gain_ctiN0005.fits 

The wmap parameter is set to the source spectrum file created by specextract. The script always creates a x WMAP block, so this approach will work with any specextract output. The new RMF file is named acis_new_rmf.fits.

Be sure to update the spectrum file header to contain the name of the new RMF file.

D. Using mkacisrmf with the psextract script

The psextract script uses the mkrmf tool to create the RMF. Users who have the correct calibration applied to the data may run mkacisrmf independently to create a new RMF.

unix% dmkeypar acis_point_evt2.fits GAINFILE echo+
acisD2000-01-29gain_ctiN0005.fits

The file has an appropriate CTI-corrected gain applied to it, so we can use mkacisrmf. For the point source case, mkacisrmf is run in "Creating an RMF at a specific location" mode.

Choose the mkacisrmf calibration file (called a "P2_RESP" file). The P2_RESP and gain files are released in pairs of matching versions, so simply choose the file which has the same "N000x" version as the gain:

unix% ls -1 $CALDB/data/chandra/acis/cpf/p2_resp/
acisD2000-01-29p2_respN0002.fits
acisD2000-01-29p2_respN0003.fits
acisD2000-01-29p2_respN0004.fits
acisD2000-01-29p2_respN0005.fits
acisD2000-01-29p2_respN0006.fits

For this gain, acisD2000-01-29gain_ctiN0005.fits, we should use the acisD2000-01-29p2_respN0005.fits file as the infile parameter.

To get the necessary coordinate information (ccd_id, chipx, chipy), convert the source region information to chip coordinates with dmcoords:

unix% punlearn dmcoords 
unix% pset dmcoords asolfile="pcadf084244404N002_asol1.fits"
unix% dmcoords acis_evt2.fits 
dmcoords>: sky 4072.125 4245.625            
(RA,Dec):     18:33:33.590    -10:34:08.00
(RA,Dec):      278.38996      -10.56889 deg
THETA,PHI          1.239'          6.09 deg
(Logical):        4072.12       4245.62
SKY(X,Y):         4072.12       4245.62
DETX,DETY         4246.75       4112.53
CHIP ACIS-S3       367.19        383.66
TDET              4284.19       2085.66

dmcoords>: quit

Now we have all the information to run the tool:

unix% mkacisrmf \
      infile="$CALDB/data/chandra/acis/cpf/p2_resp/acisD2000-01-29p2_respN0005.fits" \
      outfile=acis_point_rmf.fits \
      energy=0.3:10.0:0.005 \
      channel=1:1024:1 \
      chantype=PI \
      wmap=none \
      ccd_id=7 chipx=367.19 chipy=383.66 \
      gain=$CALDB/data/chandra/acis/bcf/gain/acisD2000-01-29gain_ctiN0005.fits

The new RMF file is named acis_point_rmf.fits.

Making a new ARF:

If you intend to use XSpec instead of Sherpa to model and fit the data, read the "Matching the ARF and RMF energy grids" caveat before continuing.

psextract users who intend to finish the data analysis in XSpec should now remake the ARF file to ensure that the grid matches the RMF. To do so, get the mkarf command from the history in the ARF file. Change the engrid parameter to use the new RMF file, and rerun mkarf.

unix% dmhistory 3c273.arf tool=mkarf
mkarf asphistfile="3c273.asphist" outfile="3c273.arf" sourcepixelx="4145.9587485" sourcepixely="4045.8953985" 
engrid="grid(3c273.rmf[MATRIX][cols ENERG_LO,ENERG_HI])" obsfile="acis_dstrk_evt2.fits" 
pbkfile="acisf063875928N002_pbk0.fits" dafile="CALDB" mirror="HRMA" detsubsys="ACIS-S3" 
grating="HETG" maskfile="NONE" ardlibparfile="ardlib.par" geompar="geom" verbose="0" 
clobber="no"  

unix% dmhistory 3c273.arf tool=mkarf action=pset

unix% pset mkarf outfile="3c273_new.arf"
unix% pset mkarf engrid="grid(acis_point_rmf.fits[MATRIX][cols ENERG_LO,ENERG_HI])"

unix% mkarf 

Be sure to update the spectrum file header to contain the name of the new RMF (RESPFILE keyword) and ARF (ANCRFILE keyword).

Match an existing ARF

If the specextract or acisspec scripts were used, you already have an ARF file for the data. Rather than remake both the RMF and ARF, get the grid information from the history in the ARF file:

unix% dmhistory acis_src1.warf tool=all
# dmhistory (CIAO 4.0): WARNING: Found "pixlib" library parameters

# dmhistory (CIAO 4.0): WARNING: Found "ardlib" library parameters

mkwarf infile="acis_src1.[WMAP]" outfile="acis_src1.warf" weightfile="acis_src1.wfef" spectrumfile=""
egridspec="0.3:9.5:0.01" threshold="0" feffile="CALDB" mskfile="" mirror="HRMA" 
detsubsysmod="" ardlibpar="ardlib" geompar="geom" clobber="no" verbose="2"  

Use the egridspec value as input for the energy parameter in mkacisrmf:

unix% pset mkacisrmf energy="0.3:9.5:0.01"

This method cannot be used with the ARFs created by psextract. That script creates the RMF first and uses it to define the ARF gridding, so the engrid parameter value looks like "grid(3c273.rmf[MATRIX][cols ENERG_LO,ENERG_HI])". The Using mkacisrmf with the psextract script section has special instructions for those users.

Create the RMF first

Since mkacisrmf can change the requested grid to match the calibration data, create the RMF first and then use it to define the energy grid when creating the ARF. This will work for both mkarf and mkwarf:

unix% pset mkarf \
      engrid="grid(sources_ciao.wrmf[cols ENERG_LO,ENERG_HI])"

or

unix% pset mkwarf \
      egridspec="grid(sources_ciao.wrmf[cols ENERG_LO,ENERG_HI])"