You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The picture I have in my mind is to separate the workbook into larger topics each with various notebooks on the various contained topics.
Likelihoods: profiles, intervals and systematics.
Using standard RooStats tools to extract useful information from the likelihood of a model or series of models.
Models: channels, shapes and normalisations.
Construction of Histfactory objects and exporting workspaces. Definition of Histfactory nomenclature (Channel, Region, etc). Explanation of interpolation/morphing scheme.
Hypothesis testing: deconstructing and explaining the standard runSig.C and AsymptoticsCLs.C macros. Presenting results.
I understand that there will be some overlap between these. But if a small amount of repetition can be coupled with a style that facilitates people skimming over each chapter in order to understand the particular issue that they're dealing with.
The text was updated successfully, but these errors were encountered:
As agreed with StatsForum Conveeners, structure should be rich text documentation in chapters with links to images produced by notebooks that can be checked out in swan or loaded in binder. These should fall into 4 sections.
The picture I have in my mind is to separate the workbook into larger topics each with various notebooks on the various contained topics.
Using standard RooStats tools to extract useful information from the likelihood of a model or series of models.
Construction of Histfactory objects and exporting workspaces. Definition of Histfactory nomenclature (Channel, Region, etc). Explanation of interpolation/morphing scheme.
I understand that there will be some overlap between these. But if a small amount of repetition can be coupled with a style that facilitates people skimming over each chapter in order to understand the particular issue that they're dealing with.
The text was updated successfully, but these errors were encountered: