next up previous contents
Next: Creating a second mosaic Up: Useful recipes for JEM-X Previous: Usage of the predefined   Contents


Rerunning the Analysis

Read this if you would like to redo part of your analysis, e.g. if your run has crashed, or if you want to change some parameters.

In case you want to re-run the analysis with different parameters, run og_create but this time with a different "ogid" parameter. This will create a new tree under obs/ogid where all the new results will be stored. If the pipeline has crashed[*], in general it is safer to restart your analysis from scratch removing the obs/ogid directory and restarting from the og_create step.

In any case, we give below a set of recipes that can be useful.

Because of the group concept you cannot just delete the result you do not like and restart the pipeline. All results that were produced in the course of the analysis are linked to the group, and should be detached before you relaunch the script. To do this you can use the og_clean program, that will clean an Observation Group up to the level specified with parameter endLevel. All data structures with a level equal or prior to endLevel will be kept, while the data structure with a later level will be erased. For example, to run the image extraction (IMA level) you should clean from the group whatever comes after the BIN_I level, as this is the level immediately preceding the IMA one.

 og_clean ogDOL="og_jmx2.fits" endLevel="BIN_I"
If og_clean fails it could be due to the fact that the group was corrupted. You should try to fix it with dal_clean program
 dal_clean inDOL="og_jmx2.fits" checkExt="1" backPtrs="1" checkSum="1"
and launch og_clean only afterwards.



Subsections
next up previous contents
Next: Creating a second mosaic Up: Useful recipes for JEM-X Previous: Usage of the predefined   Contents
inthelp@sciops.esa.int