Difference: Run2Hbb (2 vs. 3)

Revision 32014-11-26 - PaulMullen

Line: 1 to 1
 

Run 2 H->bb twiki

Line: 32 to 32
  https://twiki.cern.ch/twiki/bin/view/AtlasProtected/CxAODFramework
Added:
>
>
To check out the package create a directory to keep the framework in. I will refer to this as $MyAnalysisDir. Go to $MyAnalysisDir and do the following

svn co svn+ssh://svn.cern.ch/reps/atlasphys/Physics/Higgs/HSG5/software/VHAnalysis/LHCRun2/CxAODFramework/CxAODMaker/trunk CxAODMaker
svn co svn+ssh://svn.cern.ch/reps/atlasphys/Physics/Higgs/HSG5/software/VHAnalysis/LHCRun2/CxAODFramework/CxAODReader/trunk CxAODReader
svn co svn+ssh://svn.cern.ch/reps/atlasphys/Physics/Higgs/HSG5/software/VHAnalysis/LHCRun2/CxAODFramework/CxAODTools/trunk CxAODTools
svn co svn+ssh://svn.cern.ch/reps/atlasphys/Physics/Higgs/HSG5/software/VHAnalysis/LHCRun2/CxAODFramework/FrameworkExe/trunk FrameworkExe
svn co svn+ssh://svn.cern.ch/reps/atlasphys/Physics/Higgs/HSG5/software/VHAnalysis/LHCRun2/CxAODFramework/FrameworkSub/trunk FrameworkSub
svn co svn+ssh://svn.cern.ch/reps/atlasphys/Physics/Higgs/HSG5/software/VHAnalysis/LHCRun2/CxAODFramework/TupleMaker/trunk TupleMaker
svn co svn+ssh://svn.cern.ch/reps/atlasphys/Physics/Higgs/HSG5/software/VHAnalysis/LHCRun2/CxAODFramework/TupleReader/trunk TupleReader
 

Local Test Run

Changed:
<
<
To run the framework you need to check out all the packages then do
>
>
To run the framework you need to check out all the packages

then do

 
setupATLAS
Line: 45 to 61
 
Changed:
<
<
This will automatically make a directory called myDir and inside it you will find a directory called data-outputLabel/ which contains a file with all the trees saved by the analysis framework. There is also another folder called output-outputLabel/ which contains a file with some metadata information stored inside.
>
>
This will automatically make a directory called myDir and inside it you will find a directory called data-outputLabel/ which contains a file(a "CxAOD" that has an xAOD structure) with all the trees saved by the analysis framework. There is also another folder called output-outputLabel/ which contains a file with some metadata information stored inside. There is also a command hsg5frameworkTuple that will produce both a CxAOD and a ntuple. The folder structure should be the same but with extra data-tuple/ and output-tuple/ directories.

Next time you log in you only have to go to your analysis directory and run

 
Added:
>
>
setupATLAS
rcSetup

and you should be able to now run the framework.

 

Running On The Grid

Added:
>
>
Running on the grid uses the EventLoop grid plugin for submitting jobs. Details of this can also be found on the EventLoop twiki linked above. To submit to a grid the command is

python FrameworkExe/scripts/run_grid.py MyDatasetList.txt

The file MyDatasetList.txt should be a list of datasets with a linebreak after each one. e.g.

 
Added:
>
>
mc14_8TeV.117050.PowhegPythia_P2011C_ttbar.merge.DAOD_HIGG5D2.e1727_s1933_s1911_r5591_r5625_p1784
data12_8TeV.00204240.physics_Muons.merge.DAOD_HIGG5D2.r5724_p1751_p1784

The file itself must be located in $MyAnalysisDir/FrameworkSub/In/. Yo will also want to edit $MyAnalysisDir/FrameworkExe/data/framework-run.cfg. It contains the vtag variable that can be used to configure the output names.

The python script runs the hsg5frameworkTuple command for each of the datasets in the .txt document. It creates an output name that is currently ignored by the C++ which builds the output name itself using the vtag variable.

 

Making Plots From Your Shiny New Grid Files

Line: 74 to 113
  .....
Added:
>
>
You then need to add the names muon_data, top and Zbb to the sample_names vector in FrameworkExe/util/hsg5frameworkReadCxAOD.cxx and recompile by doing rc compile from $MyAnalysisDir. You can now run the hsg5frameworkReadCxAOD MyOutDir executable.
 This will make output files hist-Zbb.root, hist-muon_data.root, hist-top.root.
Changed:
<
<
To make stacked plots from these files we then do root -b -q 'FrameworkExe/macros/runCxAODPlots.cxx("submitDir")' where submitDir is the directory that contains the hist-*.root files.
>
>
To make stacked plots from these files we then do root -b -q 'FrameworkExe/macros/runCxAODPlots.cxx("MyOutDir")' where MyOutDir is the directory that contains the hist-*.root files.
 

-- Paul Mullen - 2014-10-02

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback