fix the boolean flags in the python scripts

[govoni]

boolean flags should be set as follows:

http://wingware.com/psupport/python-manual/2.5/lib/optparse-handling-boolean-options.html

[l-cadamuro]

Ehm why should we do this? The same boolean flags are used for example here and work fine
https://github.com/LLRCMS/LLRHiggsTauTau/blob/master/NtupleProducer/test/submitOnTier3_LLRHTauTau.py#L47

[govoni]

I don't even know why it works elsewhere, but we ended up in a situation, with Olivier, where the thing was not properly working, here:

https://github.com/LLRCMS/KLUBAnalysis/blob/master/scripts/skimNtuple.py#L51

basically the option to run the HHKinFiter is taken as a string, not as a bool.

[l-cadamuro]

Oh yes, indeed I checked and it is true also in the other script we use to submit on the tier3.
But we always used one option as “true” and the other converted to a string so the problem never showed up.
So when we have time it is better to replace with boolean options like --dokinfit and --no-dokinfit etc.

Il giorno 31/ott/2015, alle ore 13:46, Pietro Govoni notifications@github.com ha scritto:

I don't even know why it works elsewhere, but we ended up in a situation, with Olivier, where the thing was not properly working, here:

https://github.com/LLRCMS/KLUBAnalysis/blob/master/scripts/skimNtuple.py#L51 https://github.com/LLRCMS/KLUBAnalysis/blob/master/scripts/skimNtuple.py#L51
basically the option to run the HHKinFiter is taken as a string, not as a bool.

—
Reply to this email directly or view it on GitHub #30 (comment).

[giacomoortona]

Yes, I was planning to do it after this round of skimming, in order not to mess up with people scripts right now