Difference: HiggsAnalysisAtATLASUsingRooStats (43 vs. 44)

Revision 442013-08-27 - WilliamBreadenMadden

  META TOPICPARENT 
 name="WebHome"
- META TOPICPARENT
+ name="WebHome"
-<
<
+-- WilliamBreadenMadden - 2013-08-05
->
>
+-- WilliamBreadenMadden - 2013-08-27
  example file: $ROOTSYS/tutorials/histfactory/example_channel.xml
-<
<
+<!DOCTYPE Channel  SYSTEM 'HistFactorySchema.dtd'>
->
>
+%CODE{"html"}%
   InputFile="./data/example.root" HistoName="" >
    HistoName="data" HistoPath="" />
       <-- HistoPathHigh="" HistoPathLow="histForSyst4"/>-->
-<
<
->
>
+%ENDCODE%
  caveats
 A slash must be added to the end of the HistoPath string attribute of the Channel, Data and Sample tags when referencing directories other than the root directory in ROOT files, in such a manner as follows:
-<
<
->
>
+%CODE{"html"}%
 HistoName="myDataHistogram" HistoPath="myDirectory/" />
-<
<
->
>
+%ENDCODE%
  colon characters in Name attributes
  example file: ttH_m110_channel.xml
-<
<
+<!DOCTYPE Channel SYSTEM 'HistFactorySchema.dtd'>
->
>
+%CODE{"html"}%
 <-- channel name and input file -->
InputFile="data/ttH_histograms.root" HistoName="">
-<
<
->
>
+%ENDCODE%
  example file: ttH_m110_top-level.xml
-<
<
+<!DOCTYPE Combination SYSTEM 'HistFactorySchema.dtd'>
->
>
+%CODE{"html"}%
 <-- workspace output file prefix -->
OutputFilePrefix="workspaces/ttH_m110_workspace" Mode="comb" >
-<
<
->
>
+%ENDCODE%
  create XML configuration files automatically
 %CODE{"c++"}%
void AddPreprocessFunction(std::string name, std::string expression, std::string dependencies);
-<
<
->
>
+%ENDCODE%
  create a class representing a preprocess function and add it to a measurement directly using the constructor PreprocessFunction and a method of a measurement object
-<
<
->
>
+%CODE{"c++"}%
 PreprocessFunction::PreprocessFunction(std::string Name, std::string Expression, std::string Dependents);
void AddPreprocessFunction(const std::string& function);
%ENDCODE%
 Make the main directory.
-<
<
->
>
+%CODE{"bash"}%
 cd ~
mkdir test
cd test
-<
<
->
>
+%ENDCODE%
 Make the directory for the XML configuration files.
-<
<
->
>
+%CODE{"bash"}%
 mkdir config
-<
<
->
>
+%ENDCODE%
 Make the directory for the input histogram ROOT files.
-<
<
->
>
+%CODE{"bash"}%
 mkdir data
-<
<
->
>
+%ENDCODE%
 Make the directory for the workspace.
-<
<
->
>
+%CODE{"bash"}%
 mkdir workspaces
-<
<
->
>
+%ENDCODE%
  Generate input histograms. 

Change to the directory for the input histograms.
-<
<
->
>
+%CODE{"bash"}%
 cd data
-<
<
->
>
+%ENDCODE%
 Run some code such as the following. For fun, we will create a simulated data signal at about 126 GeV at about three times the number of events of that which was expected.

 example file: make_test_histograms.c
-<
<
->
>
+%CODE{"c++"}%
 {
	// Create the expected signal histogram.
		// Create the function used to describe the signal shape (a simple Gaussian shape).
 		myData->Write();
		myFile.Close();
}
-<
<
->
>
+%ENDCODE%
  Create the workspace.
 Change to the directory for the configuration XML files.
-<
<
->
>
+%CODE{"bash"}%
 cd ~/test/config
-<
<
->
>
+%ENDCODE%
 Copy the HistFactory XML schema to the configuration directory.
-<
<
->
>
+%CODE{"bash"}%
 cp $ROOTSYS/etc/HistFactorySchema.dtd .
-<
<
->
>
+%ENDCODE%
 Create XML configuration files in the configuration directory.

 example file: test_top-level.xml
-<
<
->
>
+%CODE{"html"}%
 <-- workspace output file prefix -->
-<
<
->
>
+%ENDCODE%
  example file: test_channel.xml
-<
<
->
>
+%CODE{"html"}%
 <-- channel name and input file -->
-<
<
->
>
+%ENDCODE%
 As you can see, the model is very simple. There is the expected signal, the expected background and the actual data (in this case, the data is simulated). The point of interest relates to the signal and the expected data will be compared to the actual data.

 Run hist2workspace.
-<
<
->
>
+%CODE{"bash"}%
 hist2workspace config/test_top-level.xml
-<
<
->
>
+%ENDCODE%
 There should now be created 4 files in the workspaces directory:
-<
<
->
>
+%CODE{"bash"}%
 test_workspace_combined_datastat_model.root
test_workspace_datastat.root
test_workspace_results.table
test_workspace_test_datastat_model.root
-<
<
->
>
+%ENDCODE%
 The test_workspace_combined_datastat_model.root file is the ROOT file that contains the combined workspace object (is has constraints, weightings etc. properly incorporated). This is the file you are almost certainly interested in. The test_workspace_test_datastat_model.root file contains a workspace object without proper constraints, weightings etc. I don't know what the other two files are.
  example file: ProfileLikeliHoodCalculator_confidence_level.cpp
-<
<
->
>
+%CODE{"c++"}%
 #include 
#include 
#include
 				myConfidenceInterval->UpperLimit(*myPOI) <<"]\n"<<endl;
	return 0;
  }
-<
<
->
>
+%ENDCODE%
 Compile this code using a Makefile such as the following:

 example file: Makefile
-<
<
->
>
+%CODE{"bash"}%
 ProfileLikeliHoodCalculator_confidence_level.cpp : ProfileLikeliHoodCalculator_confidence_level.cpp
	g++ -g -O2 -fPIC -Wno-deprecated  -o ProfileLikeliHoodCalculator_confidence_level.cpp ProfileLikeliHoodCalculator_confidence_level.cpp `root-config --cflags --libs --ldflags` -lHistFactory -lXMLParser -lRooStats -lRooFit -lRooFitCore -lThread -lMinuit -lFoam -lHtml -lMathMore -I$ROOTSYS/include -L$ROOTSYS/lib
-<
<
->
>
+%ENDCODE%
 Compile the code.
-<
<
->
>
+%CODE{"bash"}%
 make
-<
<
->
>
+%ENDCODE%
  results 

The end result as displayed in the terminal output is the following:
-<
<
->
>
+%CODE{"bash"}%
 % confidence interval on the point of interest SigXsecOverSM: [2.99653, 3.00347]
-<
<
->
>
+%ENDCODE%
  further information

View topic | History: r51 < r50 < r49 < r48 | More topic actions...