Notes on V2.0/2.1 processed XIS Data
1. Changes from V1.x to V2.0/2.1
Major changes incorporated in v2.0/2.1 processing are described in the processing description page.
2. Data screening criteria used in ver2.0/2.1
The standard screening criteria used in the processing pipeline are listed here. Users can produce their own cleaned event files by applying a slightly modified set of criteria.
Frequently seen examples of frequently modified screening criteria are:
Limitations of Calibrations
Now we know several limitations of calibration for the SCI-on normal mode data,
- When we fit Mn Kalpha line taken around 2006 September using the current response (either using the files provided for AO-2 proposers, or generaing new ones using xisrmfgen), an additional line width of 30eV is foudn for both FI and BI data.
- We have calibrated the energy scale of both FI and BI chips so that the center energy of the Mn Kalpha line is 5.895keV in 2006 September
- For the FI chips, we have not tuned the energy dependence of the CTI, nor have we calibrated the gain at low energies. Thus, (a) the systematic uncertainty of the gain is 15eV at most for the Fe XXV Kalpha line, and (b) there may be a positional dependence of the gain in the low energy band*.
- The CTI calibration for the BI chip has not been carried out. Therefore, we cannot gurantee the accuracy of the gain except at the Mn Kalpha line
- We have not yet implemented the time variability of the CTI for the FI or the BI chips. Hence, the gain of the Mn Kalpha line after 2006 September decreases with time. The rates of the energy shift are about 30eV/year for the FI chips and 50eV/year for the BI chip.
It is believed that the calibration files used in
processing pipeline v220.127.116.11 eliminates the above problems. Users can
new calibration to their data.
*Note: We started the SCI to improve the CTI on 2006 September.
Thus, the positional dependence of the gain due to the CTI was rather small at
It is believed that the calibration files used in processing pipeline v18.104.22.168 eliminates the above problems. Users can apply the new calibration to their data.
If you have any questions concerning Suzaku, visit the Feedback form.