------------------------------------------------------------------------------- README ------------------------------------------------------------------------------- ***** OUR SCRIPTS ARE GIVEN "AS THEY ARE" (for openSUSE 11.4): YOU NEED TO BE FAMILIAR WITH OSA IN ORDER TO KNOW/UNDERSTAND WHAT YOU ARE DOING WITH THEM, AND TO BE ABLE TO UPDATE THEM TO YOUR CONFIGURATION ***** =============================== DATA DOWNLOAD =============================== All the INTEGRAL public data can be freely downloaded via the ISDC dedicated web page http://www.isdc.unige.ch/integral/archive#DataRelease ========================================== PROCESS & POST-PROCESS OF IBIS/ISGRI DATA ========================================== IMPORTANT ============ We have used the tools in the GOLIA_scripts.tar file to build GOLIA (see Paizis et al., 2013, for a detailed description). They use freely available interpreters and need no compilation. We recall that GOLIA is an automatic extraction and as such IT IS NOT OPTIMIZED for all cases. It should be considered as the starting point for more detailed investigations, especially for what concerns the LCR results that are the result of a source selection (e.g. DETSIG > 3 and sources of interest). To learn to analyze INTEGRAL/IBIS data, please refer to the official Documentation: OSA IBIS/ISGRI COOKBOOK http://www.isdc.unige.ch/integral/analysis#Documentation KNOWN ISSUES OF S/W http://www.isdc.unige.ch/integral/osa/9.0/issues_osa All the scripts we provide are optimized for our local configuration (e.g. directory paths) and SHOULD BE UPDATED according to your setup. TAR FILE =========== The tar file contains [1] The SHELL scripts to analyse IBIS/ISGRI used to build GOLIA: For the IMA part: launch_IMA.sh analysis_IMA.csh Usage (with updated paths in both routines): > source launch_IMA.sh For the LCR part (to be run AFTER the IMA part): launch_LCR.sh analysis_LCR.csh Usage (with updated paths in both routines): > source launch_LCR.sh analysis_IMA.csh and analysis_LCR.csh can be merged to perform IMA and LCR analysis in one step. In the current configuration, we made all IMA analysis first, in order to have a quantitative view of the archive, and then we run LCR on it. [2] The PERL script to save in a given directory (e.g. RESULTS) all the ASCII files extracted from IMA FITS files (to be run after the IMA part, regardless of the LCR one). ima_pick.pl-1.05 Usage (with updated path, line 136 " @skyResFileList = `find.... " command) > perl ima_pick.pl-1.05 --dbase_res_dir ./RESULTS A SHORT DESCRIPTION ======================== [1'] The analysis performed with [1] runs on files that should look like this: > tail -4 riv108X.txt 108901010010 108901020010 108901030010 108901040010 It will result in: ***IMAGES (IMA) in 4 bands En band 1: 17-30 keV En band 2: 30-50 keV En band 3: 17-50 keV En band 4: 50-100 keV (with list of sources detected and their properties) ***LIGHTCURVES (LCR) in 1 band (100 sec binning) 17-30 keV [2'] DESCRIPTION of ima_pick.pl This script will extract the results from the ISGRI IMA analysis and save them in an $dbase_res_dir/isgri.source.dat ASCII file. The location of the data is hardcoded in the script as @skyResFileList = `find /THE_RIGHT_PATH/ -name "isgri_sky_res.fits.gz"`; and will need to be personalized for your needs. Each ASCII file is for one source and it contain the results of the science window by science window imaging step. In detail: COLUMN | TYPE | DESCRIPTION ------------------------------------------------------------------- 1 SCWID Science Window identifier 2 TSTART Start time of the Science Window (in IJD = MJD-51544.0) 3 EXPOSURE Effective exposure time (sec) 4 RA POINTING RA of the centre of the FoV 5 DEC POINTING DEC of the centre of the FoV 6 FLUX 1 Detected rate in en. band 1 7 ERROR_FLUX 1 Detected rate error in en. band 1 8 DETSIG 1 Detection significance en. band 1 9 RA_FIN 1 Source RA (KNOWN: fixed position from input catalogue - NEW: detected RA) 10 DEC_FIN 1 Source DEC (KNOWN: fixed position from input catalogue - NEW: detected DEC) 11 FLUX 2 Detected rate in en. band 2 12 ERROR_FLUX 2 (as above) 13 DETSIG 2 (") 14 RA_FIN 2 (") 15 DEC_FIN 2 (") 16 FLUX 3 Detected rate in en. band 3 17 ERROR_FLUX 3 (as above) 18 DETSIG 3 (") 19 RA_FIN 3 (") 20 DEC_FIN 3 (") 21 FLUX 4 Detected rate in en. band 4 22 ERROR_FLUX 4 (as above) 23 DETSIG 4 (") 24 RA_FIN 4 (") 25 DEC_FIN 4 (") An ERROR_FLUX of "-1.0" means that the fit did not converge and no error was computed (it happens for weak sources). Values of "0.0" mean that the source was not detected in the given energy band. NEW SOURCES: the isgri_NEW_1.dat file (if any) contains all the new sources that were found as NEW_1. It is NOT the same source in all the rows of the file. Check RA_FIN and DEC_FIN that for NEW sources is the detected position in the given energy band. This version assumes 4 energy bands have been analysed (extentions 2, 3, 4, 5 of isgri_sky_res.fits.gz). This can be modified changing the part in the code that looks like: # enList (energy band list) is the data structure number of each energy band. push(@enList, "2"); push(@enList, "3"); ... by adding or removing extentions. Multiple runs with same directory name will append the results to the already existing ASCII files. This is useful for large data bases for whch shell commands like ls -l might fail. More with perl ima_pick.pl-1.05 --help [3'] Once the archive is available, together with all the ASCII files created by ima_pick, browsing and visualization of the IMA results can be easily performed with any software that reads ASCII files. To make mosaics of the images or collection of the 100s lightcurves, see the ISDC documentation.