From a644986bbb9c5cb6bd149e314bcfa8bef8660d97 Mon Sep 17 00:00:00 2001 From: Kyle Cormier Date: Tue, 10 Oct 2023 15:40:06 +0200 Subject: [PATCH 1/2] Minor documentation for update for regexps when floating params --- docs/part3/runningthetool.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/part3/runningthetool.md b/docs/part3/runningthetool.md index a1208a92a61..2e84caba87d 100644 --- a/docs/part3/runningthetool.md +++ b/docs/part3/runningthetool.md @@ -55,7 +55,7 @@ There are a number of useful command line options which can be used to alter the - `--freezeParameters name1[,name2,...]` Will freeze the parameters with the given names to their set values. This option supports the use of regexps via by replacing `name` with `rgx{some regular expression}` for matching to *constrained nuisance parameters* or `var{some regular expression}` for matching to *any* parameter. For example `--freezeParameters rgx{CMS_scale_j.*}` will freeze all constrained nuisance parameters with the prefix `CMS_scale_j`, while `--freezeParameters var{.*rate_scale}` will freeze any parameter (constrained nuisance or otherwise) with the suffix `rate_scale`. - use the option `--freezeParameters allConstrainedNuisances` to freeze all nuisance parameters that have a constraint term (i.e not `flatParams` or `rateParams` or other freely floating parameters). - - similarly the option `--floatParameters` sets the parameter floating. + - similarly the option `--floatParameters` sets the parameter floating and also accepts regular expressions. - groups of nuisances (constrained or otherwise), as defined in the datacard, can be frozen using `--freezeNuisanceGroups`. You can also specify to freeze nuisances which are *not* contained in a particular group using a **^** before the group name (`--freezeNuisanceGroups=^group_name` will freeze everything except nuisance parameters in the group "group_name".) - all *constrained* nuisance parameters (not `flatParam` or `rateParam`) can be set floating using `--floatAllNuisances`. From 6171a362ef200671af1b45a34c2eb2e7e7cb5a8f Mon Sep 17 00:00:00 2001 From: Kyle Cormier Date: Tue, 10 Oct 2023 15:34:08 +0200 Subject: [PATCH 2/2] Add some additional documentation for ChannelCompatibilityCheck groups --- docs/part3/commonstatsmethods.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/part3/commonstatsmethods.md b/docs/part3/commonstatsmethods.md index 3ceca849546..f09255dfeb1 100644 --- a/docs/part3/commonstatsmethods.md +++ b/docs/part3/commonstatsmethods.md @@ -771,6 +771,8 @@ By default, the signal strength is kept floating in the fit with the nominal mod In the default models build from the datacards the signal strengths in all channels are constrained to be non-negative. One can allow negative signal strengths in the fits by changing the bound on the variable (option `--rMin=`), which should make the quantity more chisquare-like under the hypothesis of zero signal; this however can create issues in channels with small backgrounds, since total expected yields and pdfs in each channel must be positive. +Optionally, channels can be grouped together by using the option `-g ` where `` is a string which is common to all channels to be grouped together. The `-g` option can also be used to set the range for the each POI separately via `-g =,`. + When run with the a verbosity of 1, as the default, the program also prints out the best fit signal strengths in all channels; as the fit to all channels is done simultaneously, the correlation between the other systematical uncertainties is taken into account, and so these results can differ from the ones obtained fitting each channel separately.