This chapter provides a brief outline of the standard analysis steps. Details are explained in subsequent chapters. Analysis topics covered in this chapter are:
We assume that the user has downloaded and decrypted the Suzaku data, and has access to the latest versions of the Suzaku FTOOLS and CALDB.
Users should check
http://www.astro.isas.jaxa.jp/suzaku/log/operation/,
http://www.astro.isas.jaxa.jp/suzaku/log/hxd/, and
http://www.astro.isas.jaxa.jp/suzaku/log/xis/
for any important event (operational or instrumental issues)
that may affect your specific observation.
Users should also check the processing version of the data,
as recorded in the PROCVER keyword in any of the
FITS files. Users should then consult
http://suzaku.gsfc.nasa.gov/docs/suzaku/aehp_proc.html
to see if there are any issues for data processed using that version
of the pipeline.
Users should check for any software or calibration updates that may affect the data in question. The Suzaku GOF disseminates information in several ways.
These updates may simply note a newly discovered calibration problem, instruct users on how to obtain a software patch or updated calibration file, or provide workarounds such as an ad-hoc procedure that should be run on specific datasets.
The pre-extracted spectra and light curves in the product subdirectories, both for the XIS and the HXD, are provided for quick-look purposes only. We recommend against using these files for actual data analysis.
Event FITS files are provided to the users in two flavors (Chapter 3), unfiltered (event_uf) and screened (event_cl). Although the pre-determined screening criteria can never be perfect for each individual observation, they produce convenient and generally reliable event lists that are convenient to use. Whenever possible, it is more convenient for beginning users to start with the screened event files.
However, there are many circumstances which forces the users to start with unfiltered event files. We will endeavor to provide specific recipes when it is necessary to do so.
The following chapters (6 and 7) do contain descriptions of how to re-create screened event files with a different set of screening criteria.
The following are the steps in the spectral analysis of XIS data.
Chapter 6 contains pointers on the size and shape of the source extraction region, and on the typical background extraction region for a point source. The particle background is a strong function of the location of the Suzaku spacecraft within the geomagnetic field, and therefore is variable in time. The X-ray background is a function of the pointing direction. Therefore, ideally, the background spectrum should be extracted from the neighboring source-free region(s) of the same CCD chip from the same observation. However, for the analysis of extended sources, it is sometimes necessary to consult other observations, including the non X-ray background (NXB) database compiled by the XIS team.
We also explain the RMF and ARF generators. The latter is based on ray-tracing and can be extremely time-consuming. We therefore describe several options for speeding up ARF generation, as well as subsequent spectral fits.
Three of the XIS units (each with a frontside illuminated, or FI, chip) are sufficiently similar that we recommend the spectra from these units be summed for spectral fitting under most circumstances. However, we never recommend combining the event files (this will lead to the loss of information critical to downstream software). Also, XIS1 (with a backside illuminated, or BI, chip) has a distinctly different response and so XIS1 data should not be combined with those from other units.
The following are the steps, explained in detail in Chapter 7, in the spectral analysis of HXD data.
Since the HXD is a non-imaging instrument, users need not/cannot consider ``extraction regions.'' Instead, it is necessary to subtract the particle and X-ray background from the observation data. This is done using the background files generated by the HXD team, who model the particle background based on the orbital location and other information. In normal situations, the PIN background files are prepared within a few weeks of the distribution of the processed data to the PI; GSO background files are made about a month after distribution.
There is a noticeable dead time even for faint sources because the particle background alone results in a high count rate. This must be corrected for in the data. The background files, on the other hand, do not need a dead-time correction. However, in the case of the PIN, background files have an artificially inflated count rate to ensure sufficient statistical accuracy, and this has to be taken into account.
The HXD team provides the response files for the PIN and GSO, rather than response generators. The PIN settings have been adjusted since the initial operation several times, including changes in the bias voltage used on-board, and in the low energy thresholds used in ground processing. Therefore it is necessary to select a response file appropriate for the epoch of the observation.
The following are the steps in the timing analysis of XIS data.
Users who have become familiar with XIS spectral analysis should find little difficulties in performing XIS timing analysis. In this case, it is generally safe to add light curves from all XIS units.
The following are the steps in the timing analysis of HXD data.
Again, this process parallels that of the spectral analysis, but requires the correction of time-variable dead-time, as explained in Chapter 7.
The following are the steps in the imaging analysis of XIS data.
Chapter 6 contains a detailed description on how to generate exposure maps.
example% xispi infile=ae101005070xi0_0_3x3n066z_uf.evt.gz \
outfile=ae101005070xi0_0_3x3n066z_uf_new.evt \
hkfile=../hk/ae101005070xi0_0.hk.gz
then using the xselect command file, xisrepro.xco
(and associated screening criteria files) that we provide:
xsel > @xisrepro(see Chapter6 for further details)
xsel:SUZAKU-XIS-1-STANDARD > read event > Enter the Event file dir >[] . > Enter Event file list >[] ae101005040xi1_0_5x5n000a_cl.evt.gz xsel:SUZAKU-XIS-1-STANDARD > extract all xsel:SUZAKU-XIS-1-STANDARD > plot image xsel:SUZAKU-XIS-1-STANDARD > plot curve xsel:SUZAKU-XIS-1-STANDARD > plot spectrum xsel:SUZAKU-XIS-1-STANDARD > save spectrum
example% addascaspec fi.add fi.pha fi.rsp fi_b.pha(see Chapter6).
unix% mgtime "ae101005040hxd_0_pinno_cl2.evt+2,ae101005040hxd_0_pinbgd.evt+2" \ ae101005040hxd_wel_pin.gti AND
xsel > read event xsel > ./ xsel > ae101005040hxd_0_pinno_cl2.evt.gz xsel > filter time file ae101005040hxd_wel_pin.gti xsel > extract spec xsel > save spec ae101005040hxd_0_pinno_cl2.pha xsel > clear all xsel > yes xsel > read event xsel > ./ xsel > ae101005040hxd_0_pinbgd.evt.gz xsel > filter time file ae101005040hxd_wel_pin.gti xsel > extract spec xsel > save spec ae101005040hxd_wel_pin_bgd.pha xsel > exitThis creates the source spectrum (ae101005040hxd_0_pinno_cl2.pha) and background spectrum (ae101005040hxd_wel_pin_bgd.pha).
unix% hxddtcor event_fname="ae101005040hxd_0_pse_cl.evt" \
pi_fname="ae101005040hxd_0_pinno_cl2.pha"
unix% cp ae101005040hxd_wel_pin_bgd.pha \
ae101005040hxd_wel_pin_bgd_expcor.pha
unix% fkeyprint infile=ae101005040hxd_wel_pin_bgd_expcor.pha keynam=EXPOSURE
----- output ---
# FILE: ae101005040hxd_wel_pin_bgd_expcor.pha
# KEYNAME: EXPOSURE
# EXTENSION: 0
EXPOSURE= 1.755875832736492E+03 / Exposure time
# EXTENSION: 1
EXPOSURE= 1.755875832736492E+03 / Exposure time
# EXTENSION: 2
EXPOSURE= 1.755875832736492E+03 / Exposure time
-----------------
unix% fparkey value=1.755875832736492E+04 \
fitsfile="ae101005040hxd_wel_pin_bgd_expcor.pha+0" keyword=EXPOSURE
unix% fparkey value=1.755875832736492E+04 \
fitsfile="ae101005040hxd_wel_pin_bgd_expcor.pha+1" keyword=EXPOSURE
unix% fparkey value=1.755875832736492E+04 \
fitsfile="ae101005040hxd_wel_pin_bgd_expcor.pha+2" keyword=EXPOSURE