mass ranges in config.py as in "trig" mode
@cramonal noticed that mass ranges for Z are set in config.py
[1] to the wide range used in "trig" mode, see [2].
Is there a reason why we redefine the ranges in config.py
?
The ranges defined there are only used in cut&count mode and have a very small effect on the resulting efficiencies. The difference can get more relevant in cases with low stat/high background though.
A small test is provided after changing the mass ranges in config.py
. Nothing changes in "fit" mode, and very small differences can be seen in "cut&count" mode.
Proposed solution: either fix the ranges in config.py
or modify prepare.py
such that
from run_single_fit.py import setMassRange
and use it instead of config.massRanges
[1] https://gitlab.cern.ch/cms-muonPOG/spark_tnp/-/blob/Spark3/config.py#L70
[2] https://gitlab.cern.ch/cms-muonPOG/spark_tnp/-/blob/Spark3/run_single_fit.py#L24