Question ID = 0162
Question ID = 0162
Assigned Member (担当者)2013-01-11 T.TamuraName and Institute (質問者/機関)Mr. Giulia MantovaniQuestion (質問)I have a couple of questions about the xis data reduction.I reduced the observation of IC 4329A, 702113010, and I compared my spectrum with the one that I already have, reduced by someone else, in order to see if I understood every step of the process. After performing theaepipelineon the unfiltered event of the xis0, I performed the additional screening. I applied the standard filters withxselect in this way: sisclean 2 5 -5.24 3 0 4095 select mkf "AOCU_HK_CNT3_NML_P==1 && ANG_DIST<1.5 && S0_DTRATE<3 && S1_DTRATE<3 && S2_DTRATE<3 && S3_DTRATE<3 && SAA_HXD==0 && T_SAA_HXD>436 && ELV>5 && DYE_ELV>20" filter time file ../hk/ae702113010xi0_0_tel_uf.gti My problem at this point is that the event file is not cleaned. So, I tried in another way, downloading the three script provided by the ABC guide (xisrepro.xco, xis_event.sel, xis_mkf.sel) and typing@xisreproin xselect. The extracted event file is now cleaned, but I do not understand the difference between the two screening processes. After the extraction of the spectrum for the xis0, I compared it (data group 1) with the old one for the xis0 (data group 2), fitting them together inxspecwith the same simple model: Current model list: ===================================================== Model constant<1>*powerlaw<2> Source No.: 1 Active/On Model Model Component Parameter Unit Value par comp Data group: 1 1 1 constant factor 1.00000 frozen 2 2 powerlaw PhoIndex 1.85232 +/- 1.26243E-02 3 2 powerlaw norm 2.10233E-02 +/- 4.38047E-04 Data group: 2 4 1 constant factor 1.52468 +/- 1.27228E-02 5 2 powerlaw PhoIndex 1.85232 = 2 6 2 powerlaw norm 2.10233E-02 = 3 _____________________________________________________ The normalization constant between the spectra should be 1, but it is not. I attached the image of the spectra with their background. What could be the problem? Answer from(回答の文責)Suzaku Help (T.Tamura)Answer (答え)I wonder if you tried to filter the cleaned file which were already filtered in aepipeline by the same sisclean and condition. aepipeline create "cleaned files" by default setting. If you uesd these cleaned file as input for xselect and use the same filtering as in the aepipeline, the above situation can be understood. Please check below for the filtering in aepipeline. See aepipeline.html . Please check carefully log files from aepipeline and xselect, which should tell you what filtering are performed in the process. If you can not solve your problem, please send detailed log files for each processing (aepileline and xselect). Status （詳細なステータス）2013-01-11 Accept2013-01-21 Answered 2013-02-04 Closed 
|