User Tools

Site Tools


2019:groups:tools:correlations

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
2019:groups:tools:correlations [2019/06/25 17:19]
sabine.kraml
2019:groups:tools:correlations [2019/06/27 16:30]
wolfgang.waltenberger [Quantifying overlaps between analysis search regions using ADLs]
Line 1: Line 1:
  ​====== Study: correlations between signal regions ======  ​====== Study: correlations between signal regions ======
  
-//Members: Sophie, Wolfgang, Humberto, Benj, Andy, Sabine, Sezen //+//​Members: ​**Sophie**, Wolfgang, Humberto, Benj, Andy, Sabine, Sezen //
  
 Problem statement: to identify pairs of signal regions of the analyses in the PAD database that can safely be treated as approximately uncorrelated. Problem statement: to identify pairs of signal regions of the analyses in the PAD database that can safely be treated as approximately uncorrelated.
Line 19: Line 19:
    * void manager.DumpSR(std::​ostream&​):​ writes a series of 0 and 1. One entry for each considered signal region. One line per event. To be included in the event loop.    * void manager.DumpSR(std::​ostream&​):​ writes a series of 0 and 1. One entry for each considered signal region. One line per event. To be included in the event loop.
    * void manager.HeadSR(std::​ostream&​):​ writes the header of the file: one comment line (starting with a hash) with the list of analysis-SR. To be included before entering the event loop/    * void manager.HeadSR(std::​ostream&​):​ writes the header of the file: one comment line (starting with a hash) with the list of analysis-SR. To be included before entering the event loop/
 +
 +
 +**Generic overview of [[RecastCodeComparison|what is implemented in which recast framework]]**
 +
  
  
Line 33: Line 37:
 | CMS-SUS-17-001 ​    | 2L stop          | T2tt(off), T6bbWW | UL  |  | CMS-SUS-17-001 ​    | 2L stop          | T2tt(off), T6bbWW | UL  | 
  
-From http://​madanalysis.irmp.ucl.ac.be/​wiki/​PublicAnalysisDatabase+See also http://​madanalysis.irmp.ucl.ac.be/​wiki/​PublicAnalysisDatabase
  
  
Line 53: Line 57:
 | CMS-SUS-16-039 ​    | multilepton EWK  | TChiWZ(off),​ TChiWH, TChipmSlep... | UL |  | CMS-SUS-16-039 ​    | multilepton EWK  | TChiWZ(off),​ TChiWH, TChipmSlep... | UL | 
  
 +==== Quantifying overlaps between analysis search regions using ADLs ====
  
-=== CheckMate - SModelS correspondence (13 TeV)=== +MembersSezenWolfgang (Harrison)
- +
-//... to be done ...// +
- +
-From https://​github.com/​CheckMATE2/​checkmate2/​tree/​master/​data/​analysis_info/​ +
- +
-atlas_1712_08119 ​    ​39 ​  ​electroweakinos search with soft leptons ​                                                    +
-   +
-atlas_1712_02332 ​    ​24 ​  ​squarks and gluinos0 lepton2-6 jets                                                         +
- +
-atlas_1709_04183 ​    ​14 ​  stop pair production, 0 leptons ​                                                              +
- +
-atlas_1802_03158 ​    ​7 ​   search for GMSB with photons ​                                                                +
- +
-atlas_1708_07875 ​    ​2 ​   electroweakino search with taus and MET                                                     +
- +
-atlas_1706_03731 ​   19 same-sign or 3 leptons RPC and RPV SUSY +
  
-cms_sus_16_039 ​     158  electrowekinos ​in multilepton final state    +Find and visualize overlaps ​in a model-independent way, without generating events. ​ Directly sample the event selection. ​ Useful for analysis design phase, or quick comparisons within experiments (e.g. Run2 CMS SUSY pMSSM combination)
  
-cms_sus_16_048 ​     20    ​two soft opposite sign leptons +  * Start from the analysis description,​ which lists objects and event selections. ​  
 +  * Construct a feature space from all mathematically orthogonal "​basic"​ variables (e.g. MET, jet1.pt, jet2.pt, electron1.eta,​ ...).   
 +  * Randomly sample the feature space for each analysis based on cuts on the feature space components (jet1.pt > 100, MET > 299, etc.). 
 +  * Use the sampled points to compute values for "​composite"​ variables such as HT(jets), dphi(jets), MT(lepton, MET), etc. 
 +  * Compare feature spaces between analyses, find and visualize overlaps and exclusions. 
 +  * As a very simple first step, we simply check if two analyses are disjoint in any of the basic variables.
  
-Here's also a table with a [[RecastCodeComparison]] 
  
2019/groups/tools/correlations.txt · Last modified: 2019/06/27 17:10 by sezen.sekmen