CTI correction error in the pipeline product data
Edited by the GOF
The XIS team found that an inappropriate CTI correction was made to some of the AO1 data obtained during August - October, 2006. The inappropriate CTI correction resulted in a systematically lower energy scale, up to 20 eV at 5.9 keV, in the event files. This was caused by the use of an old CALDB files for the CTI correction during the pipeline processing. Hence, if your data are affected by this error, please reprocess the data to get a correct energy scale using the latest CALDB files as explained below.
1. Observations and data affected by this error
Observations which satisfy the following conditions are affected by the CTI correction error:
(1) the observation did not utilize the Spaced-row Charge Injection (SCI)
(2) the observation was made between 2006-08-15 and 2006-10-31.
(3) the processing version, designated as "PROCVER", is earlier than 18.104.22.168.
Sequence numbers of all the observations affected by this error are listed below:
In the pipeline products, the unfiltered/cleaned event files are
affected by the CTI correction error. The unfiltered data are
labelled as aeXXXXXXXXXxi[0-3]_N_mmmmmmmm_uf.evt.gz in the
xis/event_uf subdirectory, and, the cleaned event
files are as aeXXXXXXXXXxi[0-3]_N_mmmmmmmm_cl.evt.gz in the
xis/event_cl subdirectory, where XXXXXXXXX represents the 9-digit
sequence number of
the observation and mmmmmmmm is a file identifier.
Since the spectra in the xis/products are extracted from the cleaned event files, both source (aeXXXXXXXXXxi[0-3]_N_mmmmmmmm_sr.pi) and background (aeXXXXXXXXXxi[0-3]_N_mmmmmmmm_bg.pi) spectra are also affected by this error.
2. Details of the error
Since the CTI increases with time due to the radiation damage in space, the CTI-correction parameters are time dependent. The current CALDB files contain a table which provides the relevant parameters at specific epochs. Because the processing tool to correct the CTI (xispi) refers to the CTI parameters at the epoch closest to the time of the observation, the table has many entries with enough frequency. However, because the calibration of the CTI takes some time, the CTI parameters for the latest observations are not known. This means that the table should contain CTI parameters extrapolated to future. (Note that the CTI parameters in the current CALDB files are not valid to the data obtained with SCI.)
The CALDB files originally used contained the extrapolated CTI values only up to 2006-08-13 00:00:00. Therefore, the parameters at this epoch were always used even for the data obtained after August 13. This caused an insufficient correction of the charge loss, and reduced the total pulse height slightly. This error occurred to data from all four sensors.
The figure below shows a time history (2006 Jun - 2006 December) of the center energy of Mn Kalpha line from the 55Fe calibration source, which illuminate a corner of the XIS1, segment A. Each mark corresponds to a sequence of observation. Deviation of the line center energy from 5.895 keV increases with time and reaches up to 20 eV by the end of October.
The error mentioned above can be corrected by applying the CTI correction tool xispi again with correct CTI parameters. The entire Suzaku archive will be reprocessed with the correct CTI parameters when the processing verion 2.0 becomes available.
Correction to the cleaned event files:
(Note: this requires the new version of xispi, part of Suzaku FTOOLS version 4.)
unix% xispi infile=ae501008010xi0_0_3x3n066a_cl.evt.gz \ outfile=ae501008010xi0_0_3x3n066a_cl_cticorr.evt \ hkfile=ae501008010xi0_0.hk.gz \ makepifile=ae_xi0_makepi_20070124.fits
Correction to the unscreened event files:
1. Recalculate the pulse invariant (PI) and grade values with the latest CALDB file. In the current release, the CALDB files for the CTI correction are ae_xi[0-3]_makepi_20070124.fits. This is done with xispi, the XIS-specific tool in HEASOFT v6.1.2.
unix% xispi infile=ae501008010xi0_1_3x3n066z_uf.evt.gz \ trcor_caldbfile=ae_xi0_makepi_20070124.fits \ cticor_caldbfile=ae_xi0_makepi_20070124.fits \ grade_caldbfile=ae_xi0_makepi_20070124.fits \ pha2pi_hkfile=ae501008010xi0_0.hk.gz \ pha2pi_caldbfile=ae_xi0_makepi_20060823.fits \ outfile=ae501008010xi0_1_3x3n066z_uf_cticorr.evt
The unfiltered event files and house keeping (HK) file are in the xis/event_uf and xis/hk subdirectories, respectively.
2. Screen with xselect (filter column), using GRADE and STATUS information.
xsel:SUZAKU > set datadir . xsel:SUZAKU > read event ae501008010xi0_1_3x3n066z_uf_cticorr.evt xsel:SUZAKU-XIS0-STANDARD > filter column "GRADE=0:0 2:4 6:6 STATUS=0:131072"
Calibration source areas are not removed in the pipeline processing. You are requested to do by yourself if needed. If you are using xselect, substitute "GRADE=0:0 2:4 6:6 STATUS=0:65535" for the above criterion.
3. Screen with xselect (select hk), using common HK, to discard the data during maneuver.
xsel:SUZAKU-XIS0-STANDARD > read hk hkfiles=ae501008010.hk.gz expand=yes > HK file directory >[./] xsel:SUZAKU-XIS0-STANDARD > select hk "AOCU_HK_CNT3_NML_P==1" xsel:SUZAKU-XIS0-STANDARD > extract event xsel:SUZAKU-XIS0-STANDARD > save event ae501008010xi0_1_3x3n066z_uf_cticorr.evt_gsmnvcut > Use filtered events as input data file ? >[no] yesThe common HK file is in auxil subdirectory.
4. Screen with xselect (select hk), using XIS HK, to discard the data during data rate low. The criteria are given by "Sn_DTRATE < 3", where n=0, 1, 2, 3, depending on the sensor ID.
xsel:SUZAKU-XIS0-STANDARD > read hk hkfiles=ae501008010xi0_0.hk.gz expand=yes > HK file directory >[./] xsel:SUZAKU-XIS0-STANDARD > select hk "S0_DTRATE<3" xsel:SUZAKU-XIS0-STANDARD > extract event xsel:SUZAKU-XIS0-STANDARD > save event ae501008010xi0_1_3x3n066z_uf_cticorr.evt_dtratecut > Use filtered events as input data file ? >[no] yes
5. Screen with xselect (select hk), using extended house keeping (EHK) file, to discard the data during SAA.
xsel:SUZAKU-XIS0-STANDARD > read hk hkfiles=ae501008010.ehk.gz expand=yes > HK file directory >[./] xsel:SUZAKU-XIS0-STANDARD > select hk "SAA_HXD==0 && T_SAA_HXD>436 && ANG_DIST<1.5" xsel:SUZAKU-XIS0-STANDARD > extract event xsel:SUZAKU-XIS0-STANDARD > save event ae501008010xi0_1_3x3n066z_uf_cticorr.evt_saacut > Use filtered events as input data file ? >[no] yesThe EHK file is in auxil subdirectory.
6. Then, cleaned events are selected with the following criteria:
xsel:SUZAKU-XIS0-STANDARD > read hk hkfiles=ae501008010.ehk.gz expand=yes > HK file directory >[./] xsel:SUZAKU-XIS0-STANDARD > select hk "ELV>5 && DYE_ELV>20" xsel:SUZAKU-XIS0-STANDARD > extract event xsel:SUZAKU-XIS0-STANDARD > save event ae501008010xi0_1_3x3n066z_cticorr_cl.evt > Use filtered events as input data file ? >[no] no xsel:SUZAKU-XIS0-STANDARD > exit > Save this session? >[no]
7. Finally, cleansis is applied to remove hot/flickering pixels.
unix% cleansis datafile=ae501008010xi0_1_3x3n066z_cticorr_cl.evt \ outfile=ae501008010xi0_1_3x3n066z_cticorr_cl2.evt \ cellsize=5 logprob=-.53E+01 bthresh=3 \ phamin=0 phamax=4095 chipcol=SEGMENT
If you have any questions concerning Suzaku, visit the Feedback form.