the datasets and processes from the main config are refactored into their own modules
resonant hh samples are added
the hbw.InferencePlots task is added, which plots variables based on an inference model
a law.shared.cfg is added, which can be used to access outputs from the first reference analysis (status of the repository after this PR, to be produced)
To use the law.shared.cfg, it is a good idea to write your own law config, which inherits from the law.shared.cfg. For a sl analysis, it could look like this:
[core]
# inherit from the analysis configuration file, allowing to use datasets
# stored at DESY without a Grid certificate
inherit: $HBW_BASE/law.shared.cfg
[analysis]
# set your default analysis inst to "hbw_sl"
default_analysis: hbw.analysis.hbw_sl.hbw_sl
default_config: c17
default_dataset: ggHH_kl_1_kt_1_sl_hbbhww_powheg
[outputs]
# decide, for which tasks you want to produce your own outputs, e.g. rerun the MLTraining and everything that follows
cf.BundleRepo: local
cf.BundleSoftware: local
cf.BundleBashSandbox: local
cf.BundleCMSSWSandbox: local
cf.BundleExternalFiles: local
cf.ProduceColumns: local
cf.MLTraining: local
cf.MLEvaluation: local
cf.CreateHistograms: local
cf.MergeHistograms: local
cf.MergeShiftedHistograms: local
cf.PlotCutflow: local
cf.PlotCutflowVariables: local
cf.PlotVariables: local
cf.PlotShiftedVariables: local
cf.CreateDatacards: local
hbw.InferencePlots
task is added, which plots variables based on an inference modellaw.shared.cfg
is added, which can be used to access outputs from the first reference analysis (status of the repository after this PR, to be produced)To use the
law.shared.cfg
, it is a good idea to write your own law config, which inherits from thelaw.shared.cfg
. For a sl analysis, it could look like this: