Difference: HiggsAnalysisAtATLASUsingRooStats (34 vs. 35)

The ModelConfig RooStats class encapsulates the configuration of a model to define a particular hypothesis. It is now used extensively by the calculator tools. ModelConfig always contains a reference to an external workspace that manages all of the objects that are a part of the model (PDFs and parameter sets). So, in order to use ModelConfig, the user must specify a workspace pointer before creating the various objects of the model.

Line: 667 to 685

Changed:

<
<

Analysis!

>
>

Guidance in writing the XML configuration files

Changed:

<
<

ATLAS recommends the use of the profile likelihood as a test statistic.

>
>

Histograms

Changed:

<
<

Further information

>
>

Units

Changed:

<
<

ROOT links:

>
>

The units of the input histogram and the luminosity specified in the top-level XML configuration file should be compatible; for example, input histograms might be in pb while the luminosity might be in pb^{-1} or input histograms might be in fb while the luminosity might be in fb^{-1}.

Changed:

<
<

ROOT User's Guide

>
>

Naming convention

Changed:

<
<

RooFit links

>
>

The input histogram names are of no special significance, however, it is often preferable to have a good naming convention devised. One might consider the order in which one has information in the XML and aim to have histogram names appear in a similar order when listed alphabetically.

Changed:

<
<

User's Manual

>
>

Generic example:

Changed:

<
<

Tutorials

>
>

Type of histogram	Histogram naming convention
Phenomenon histogram	<phenomenon name>_m<mass point>
Phenomenon upward systematic histogram	<phenomenon name>_m<mass point>_sys_<systematic name>_up
Phenomenon downward systematic histogram	<phenomenon name>_m<mass point>_sys_<systematic name>_do

Changed:

<
<

RooStats links

>
>

The reason for having an "m" character preceding the mass point is that it allows for easy search and replace of the mass point value when automatically producing multiple XML configuration files corresponding to multiple mass points.

Changed:

<
<

Wiki

>
>

Specific example:

Changed:

<
<

RooStats User's Guide

>
>

Type of histogram	Histogram name
ttH histogram	ttH_m110
ttH upward luminosity systematic histogram	ttH_m110_sys_Lumi_up
ttH downward luminosity systematic histogram	ttH_m110_sys_Lumi_do
ttH upward JES systematic histogram	ttH_m110_sys_JES_up
ttH downward JES systematic histogram	ttH_m110_sys_JES_do
WW Herwig 105987 upward luminosity systematic histogram	WW_Herwig_105987_m110_sys_Lumi_up
WW Herwig 105987 downward luminosity systematic histogram	WW_Herwig_105987_m110_sys_Lumi_do
WW Herwig 105987 upward JES systematic histogram	WW_Herwig_105987_m110_sys_JES_up
WW Herwig 105987 downward JES systematic histogram	WW_Herwig_105987_m110_sys_JES_do

Changed:

<
<

Tutorials

>
>

Samples

Changed:

<
<

HistFactory manual

>
>

The sample names are of no special significance, however, it is often preferable to have very short names (e.g., signal1) for the purposes of clarity when, for example, printing the contents of the workspace.

Changed:

<
<

E-group for support with ATLAS-sensitive information: atlas-phys-stat-root@cern.ch

>
>

The NormalizedByTheory attribute should be "True" (as opposed to "TRUE" or "true") for all non-data-driven backgrounds. If the Data tag is removed, expected data shall be used in calculations.

Changed:

<
<

E-mail support for software issues, bugs etc.: roostats-development@cern.ch

>
>

The signal(s) are specified as such through the use of the POI tag.

Example file: ttH_m110_channel.xml

<!DOCTYPE Channel SYSTEM 'HistFactorySchema.dtd'>

<!-- channel name and input file -->
<Channel Name="ttH_m110" InputFile="data/ttH_histograms.root" HistoName="">

Changed:

<
<

Other links

>
>

<-- data -->

HistoName="data" />

<-- signal -->

<-- systematics: -->

<-- backgrounds -->

<-- WW_Herwig_105987 -->

NormalizeByTheory="True" HistoName="WW_Herwig_105987_m110">

<-- Wplusjets -->

NormalizeByTheory="False" HistoName="Wplusjets_m110">

<-- systematics -->

Example file: ttH_m110_top-level.xml

<!DOCTYPE Combination SYSTEM 'HistFactorySchema.dtd'>

<!-- workspace output file prefix -->
<Combination OutputFilePrefix="workspaces/ttH_m110_workspace" Mode="comb" >

   <!-- channel XML file(s) -->
   <Input>config/ttH_m110_channel.xml</Input>

   <!-- measurement and bin range -->
   <Measurement Name="datastat" Lumi="1" LumiRelErr="0.037" BinLow="0" BinHigh="21" Mode="comb" ExportOnly="True">
      <POI>SigXsecOverSM</POI>
   </Measurement>

</Combination>