... Compton[*]
For the time being, Compton analysis is not available
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... PIF[*]
The Pixel Illumination Factor (PIF) is a number between 0 and 1, which expresses the theoretical degree of illumination of each detector pixel for a given source in the sky.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... analyze[*]
It is no more needed to add the extension `[1]' but the name of the FITS file (`swg.fits') is needed unless you use the very basic format without the directory path `scw/0039/' and without the final `/' as shown below [1].
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... shells[*]
If the setenv command fails with a message like:`setenv: command not found' or `setenv: not found', then you are probably using the sh family. In that case, please replace the command `setenv my_variable my_value' by the following command sequence: `my_variable=my_value ; export my_variable'. In the same manner, replace the command `source a_given_script.csh' by the following command `. a_given_script.sh' (notice the leading `.' !).
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... chattier[*]
For instance, the exit status of the program will now appear.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... COR[*]
Remember that -in order to fully exploit the latest improvements- the analysis needs ALWAYS to be performed starting from COR level, as new calibration files have been introduced.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... IMA2[*]
IMA2 level is for PICsIT analysis only, and there is no difference for ISGRI analysis whether endLevel is set to IMA, or IMA2.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... SIGNIFICANCE[*]
Note that systematic errors are not included in the calculation of the detection significance (DETSIG).
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... RESIDUAL[*]
The intensity image from which all photons attributed to the detected sources were removed.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... EXPOSURE[*]
The actual exposure map of the field of view in seconds.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... parameter[*]
To read a given extension in XSPEC (version 12) you have to specify it in curly or squared brackets (depending on the spectral type): If you want to examine in XSPEC the spectra produced at scw level, you can load them as e.g., data scw/*/isgri_spectrum.fits [3] or as data XXX_single_pha2.fits{3}.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... (PIF[*]
PIF is a number between 0 and 1, which expresses the theoretical degree of illumination of each detector pixel for a given source in the sky.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...specat.fits[*]
specat.fits has to be of the ISGR-SRCL-RES type, meaning that it has to be created by the imaging step (with OBS1_DoPart2=1, since this file is created at mosaic stage). See section 7.2 to learn how to go from the imaging result file isgri_srcl_res.fits to your specat.fits, to avoid software crash.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... images[*]
Note that the run time is proportional to the number of sources detected.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... crashed[*]
If any executable crashes then it terminates with non zero status. The meaning of the status value can be found at http://www.isdc.unige.ch/integral/analysis#Errors
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... steps[*]
Please note that the images that you intend to merge MUST have the same energy boundaries i.e. all the ScW maps must have been analysed in the same way. You cannot merge a 20-40keV map with a 30-50keV one.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... needs[*]
e.g., through the rbnrmf FTOOL
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... 41)[*]
The IBIS data mode can be checked in the archive by selecting IBIS mode column on the page with additional parameters
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.