Todo List

Member GammaComboEngine::scaleDownErrors ()

implement a more generic version of this function.

Member MethodAbsScan::calcCLintervalsSimple (int CLsType=0)

: Do it properly from the very start by introducing a bkg model and propagate it to the entire framework.

Member MethodAbsScan::removeDuplicateSolutions ()

upgrade the quickhack to a proper option

Member MethodDatasetsPluginScan::readScan1dTrees (int runMin, int runMax, TString fileNameBaseIn="default")

: Like for the normal gammacombo stuff, use a seperate class for the PROB scan! This is MethodDatasetsPLUGINScan.cpp, after all

replace this such that there's always one bin per scan point, but still the range is the scan range.

Also, if we use the min/max from the tree, we have the problem that they are not exactly the scan range, so that the axis won't show the lowest and highest number.

If the scan range was changed after the toys were generate, we absolutely have to derive the range from the root files - else we'll have bining effects.

Member MethodDatasetsProbScan::sethCLFromProbScanTree ()

replace this such that there's always one bin per scan point, but still the range is the scan range.

Also, if we use the min/max from the tree, we have the problem that they are not exactly the scan range, so that the axis won't show the lowest and highest number.

If the scan range was changed after the toys were generate, we absolutely have to derive the range from the root files - else we'll have bining effects.

Member MethodPluginScan::analyseToys (ToyTree *t, int id=-1)

replace this such that there's always one bin per scan point, but still the range is the scan range.

Also, if we use the min/max from the tree, we have the problem that they are not exactly the scan range, so that the axis won't show the lowest and highest number.

If the scan range was changed after the toys were generate, we absolutely have to derive the range from the root files - else we'll have bining effects.

Member MethodPluginScan::setParevolPLH (MethodProbScan *s)

This setting is currently being ignored by the DatasetsPluginScan