Changes between Version 139 and Version 140 of PublicAnalysisDatabase
- Timestamp:
- Jul 18, 2016, 3:52:09 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PublicAnalysisDatabase
v139 v140 5 5 ---- 6 6 7 '''IMPORTANT NOTE:''' most of the currently available recast codes have been developed for our MA5tune version of Delphes within [http://madanalysis.irmp.ucl.ac.be/raw-attachment/wiki/PublicAnalysisDatabase/ma5_v1.1.12beta.tgz MadAnalysis5 v1.1]. The latest version is v1.3, with v1.4 to be made available very soon. If you want to use the recast codes validated in the MA5tune with the latest 8 !MadAnalysis 5 v1.2 or v1.3, you still have to install DelphesMA5tune as detailed below. For updating the analysis codes to use them with the standard Delphes3 linked to !MadAnalysis 5 v1.2 or v1.3, see [https://madanalysis.irmp.ucl.ac.be/attachment/wiki/PublicAnalysisDatabase/MA5-1.2.pdf these slides]. In this case it is however advisable to re-do the validation of the analysis code(s). 9 Note also that the standard Delphes and delphesMA5tune still cannot be used simultaneously in v1.2. The update of the full PAD to Delphes3/MA5v1.2 and Delphes3/MA5v1.3 is in progress. 7 The current version of !MadAnalysis 5 is version 1.4 (to be released on July 20). This version (and the former v1.3 version) contains a lot of improvements to make the recasting procedure easier. Although we have two options for taking care of the detector simulation (delphes and delphesMA5tune), we recommend, when developing a new recasting code, to use the latest MA5v1.4 version linked to the standard Delphes3 (see [https://madanalysis.irmp.ucl.ac.be/attachment/wiki/PublicAnalysisDatabase/MA5-1.2.pdf these slides] for more information). 10 8 11 ''When developing a new recast code, preferably use the latest MA5v1.3 linked to the standard Delphes3.''12 9 ---- 13 10 14 In order to use the current version of the PAD, after installation of !MadAnalysis 5, you also need our modified version of Delphes. To install it, type11 In order to use all analyses implement in the PAD, you need to install both the delphes and delphesMA5tune detector simulators and the library of analyses shown below. To this aim, once !MadAnalysis 5 has been installed and started, it is sufficient to type: 15 12 {{{ 16 13 install delphesMA5tune 14 install PADForMA5tune 15 install delphesMA5tune 16 install PAD 17 17 }}} 18 within !MadAnalysis 5. Beware that the standard Delphes and delphesMA5tune cannot be used simultaneously, you must install only the one or the other!! 19 If you want to use our scripts for limit setting and efficiency maps (see [https://madanalysis.irmp.ucl.ac.be/wiki/UsingMa5Pad here]), next type 18 and restart !MadAnalysis 5. 19 20 ---- 21 22 In order to test a new physics signal (corresponding to a Monte Carlo sample mysample.hep.gz or mysample.hepmc.gz), it is sufficient to start !MadAnalysis 5 in the reco mode (./bin/ma5 -R) and type 20 23 {{{ 21 install RecastingTools 24 set main.recast = on 25 set main.store_root = False 26 import <path-to-the-event-sample> 27 submit 22 28 }}} 23 For creating a working directory that contains all the analyses that are publicly available, then type 29 The interpreter then asks to edit the recasting card where one can tick/untick the analyses that need to be recasted. One can also use the command 24 30 {{{ 25 install PAD 31 set main.card_path = <path-to-a-recasting-card> 26 32 }}} 33 to provide the recasting card directly. The output directory contains the events of the store_root option has been set to True, as well as the CLs an efficiency information for each signal region of each of the selected analyses. The cross section excluded at the 95% CL by each region is also provided as additional information. 27 34 28 New analyses (within the PAD or separately) can be added by running the script newAnalyzer.py (located in !Build/SampleAnalyzer), passing as an argument the name of the analysis of interest. For instance, 35 ---- 36 37 New analyses (within the PAD or separately) can be added by running the script newAnalyzer.py (located in !PAD/Build/SampleAnalyzer), passing as an argument the name of the analysis of interest. For instance, 29 38 {{{ 30 39 python newAnalyzer.py cms_sus_14_001 31 40 }}} 32 will create and modify the necessary files for adding the analysis named cms_sus_14_001. In particular, a pair of header and source C++ files cms_sus_14_001.cpp and cms_sus_14_001.h are now available in the subdirectory !Build/SampleAnalyzer/User/Analyzer. You can now either implement the analysis yourself or replace the newly created files with those shared by somebody else (or downloaded from the list below in case you do not use the automatic PAD installation from above). 33 34 Here is a detailed [https://madanalysis.irmp.ucl.ac.be/wiki/Ma5PadStepByStep step-by-step introduction] to installing and using the MA5 PAD 41 will create and modify the necessary files for adding the analysis named cms_sus_14_001. In particular, a pair of header and source C++ files cms_sus_14_001.cpp and cms_sus_14_001.h are now available in the subdirectory !PAD/Build/SampleAnalyzer/User/Analyzer. You can now either implement the analysis yourself or replace the newly created files with those shared by somebody else (or downloaded from the list below in case you do not use the automatic PAD installation from above). 35 42 36 43 ''We strongly encourage users to publish their re-implemented LHC analyses via [https://inspirehep.net/help/data-submission?ln=en Inspire].'' This way they become individually citable. (Send us an email with the Inspire link to integrate your analysis in the PAD.) Recommendations regarding the proper validation are given in [http://arxiv.org/abs/1407.3278 arXiv:1407.3278]. Note that for every analysis that is part of the PAD, a detailed validation note is required. … … 84 91 [http://madanalysis.irmp.ucl.ac.be/raw-attachment/wiki/PublicAnalysisDatabase/delphes_card_cms_b2g_14_004.tcl Delphes card] for the CMS-B2G-14-004 MA5tune (v1.2) analysis 85 92 86 [1] This analysis requires MINUIT libraries. Therefore, the line 87 {{{ 88 LIBFLAGS += -lMinuit 89 }}} 90 should be added to the Makefile of the Build/ directory before compilation. 93 [1] This analysis requires MINUIT libraries.