Changes between Version 52 and Version 53 of PublicAnalysisDatabase


Ignore:
Timestamp:
Mar 10, 2015, 6:34:51 PM (10 years ago)
Author:
Benjamin Fuks
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PublicAnalysisDatabase

    v52 v53  
    1111You then need to create a working directory by starting !MadAnalysis 5 as
    1212{{{
    13  ./bin/ma5 -E -R
     13 ./bin/ma5 -R
    1414}}}
    15 and follow the instructions displayed to the screen. So far, there is no automatic installation in the form of an analysis library. Instead, analyses have to be added by hand.  This is done by running the script newAnalyzer.py (located in !Build/SampleAnalyzer), passing as an argument the name of the analysis of interest. For instance,
     15and type
     16{{{
     17install PAD
     18}}}
     19
     20New analyses can be added in a second step by running the script newAnalyzer.py (located in !Build/SampleAnalyzer), passing as an argument the name of the analysis of interest. For instance,
    1621{{{
    1722 python newAnalyzer.py cms_sus_13_011
    1823}}}
    19 will create and modify all necessary files for adding the analysis named cms_sus_13_011. In particular, a pair of header and source C++ files cms_sus_13_011.cpp and cms_sus_13_011.h are now available in the subdirectory !Build/SampleAnalyzer/User/Analyzer. These files must be replaced by those available for download in the database (see list below). A more convenient library mode to install several analyses at once is in preparation.
     24will create and modify all necessary files for adding the analysis named cms_sus_13_011. In particular, a pair of header and source C++ files cms_sus_13_011.cpp and cms_sus_13_011.h are now available in the subdirectory !Build/SampleAnalyzer/User/Analyzer. These files must be replaced by those available for download in the database (see list below).
    2025
    2126After execution of an analysis, exclusion under the CLs prescription can be computed with the Python code [http://madanalysis.irmp.ucl.ac.be/attachment/wiki/PhysicsAnalysisDatabase/exclusion_CLs.py exclusion_CLs.py] It requires [http://www.scipy.org/ SciPy] to be installed.
     
    2429 install RecastingTools
    2530}}}
    26 within !MadAnalysis 5. This will create a local copy of [http://madanalysis.irmp.ucl.ac.be/attachment/wiki/PhysicsAnalysisDatabase/exclusion_CLs.py exclusion_CLs.py] in every new working directory.
     31within !MadAnalysis 5. This will create a local copy of [http://madanalysis.irmp.ucl.ac.be/attachment/wiki/PhysicsAnalysisDatabase/exclusion_CLs.py exclusion_CLs.py] (as well as [http://madanalysis.irmp.ucl.ac.be/attachment/wiki/PhysicsAnalysisDatabase/getmaps.py getmaps.py], see below) in every new working directory.
    2732In both cases, the code should be called as
    2833{{{
    2934 ./exclusion_CLs.py analysis_name mypoint.txt [run_number] [cross section in pb]
    3035}}}
    31 The exclusion results will be printed on the screen and in an output file located in the directory mypoint.txt/ of the output of the analysis.
     36The exclusion results will be printed on the screen and in an output file located in the directory mypoint.txt/ of the output of the analysis. In order to get the efficiency map associated with a given benchmark point, the following script can be run
     37{{{
     38 ./getmaps.py mypoint.txt
     39}}}
     40This creates one file for each analysis that have been executed, this file containing the efficiency associated with each of the signal regions of the relevant analysis.
     41
    3242
    3343''We strongly encourage users to publish their re-implemented LHC analyses via Inspire.'' This way they not only become part of the public database, rendering them as useful as possible to the community, but they also become individually searchable and citable.