new option in cfg file: ltcube and minos

[dcfidalgo]

I know that there is a very similar request, but i think it is worth reconsidering.

• New option 'ltcube' introduced in the cfg file. Now you can specify a live time cube that will be used for the analysis.
• For the analysis in the different energy bins, enrico now uses the ltcube from the global fit instead of producing the same file x times. This was very easy to implement with the new ltcube option.
• New option 'minos' introduced in the cfg file. Now you can choose if you want to calculate MINOS errors or not. I found that depending on your analysis it can take a very long time, so i thought it would be nice to have the possibility to skip it.
  Cheers,
  David

[davidsanchez]

Hi thanks for the contribution.
If you give the option for the user to use an ltcube, you should give him the possibility to either compute it or download it

In the config file generation, this has to be also transparent for the user.
cheers
david

[dcfidalgo]

Hi David,
I guess the idea was that if someone already computed the ltcube by themselves or wants to use the same ltcube for several analyses, they can do so and save a significant amount of time (especially when using a full, now almost 8 year data set).
But since both options (ltcube and minos) are both not vital for the analysis in the sense that they only speed it up, i would not include them in the std config file and just mention them in the docs. In this way the config file stays manageable, but users who bump into the same "issues" that i had can search the docs.
Cheers,
david

[davidsanchez]

Hi

in the std config file you can have them with default value as you defined in the default config file.

It would be nice to have some tool to compute the ltcube before the analysis (as enrico_download is use to download weekly data), maybe put it at some place where enrico can get it easly when creating a config file

cheers
david