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 12:17]
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 //+//​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 12: Line 12:
  
  
-=== MA5 PAD vs SModelS correspondence (13 TeV): ===+=== MA5 package to be used for correlation studies === 
 + 
 +- Any version of the code from v1.8.20 onwards, to be downloaded e.g. from {{ 2019:​groups:​tools:​ma5_v1.8.20.tgz | here }}. 
 + 
 +- This version contains two new dedicated functions (to be added in tools/PAD/​Build/​Main/​main.cpp):​ 
 +   * 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/ 
 + 
 + 
 +**Generic overview of [[RecastCodeComparison|what is implemented in which recast framework]]** 
 + 
 + 
 + 
 +=== MA5 PAD - SModelS correspondence (13 TeV): ===
  
 //nb mono-X analyses generally cannot be treated in SModelS // //nb mono-X analyses generally cannot be treated in SModelS //
  
 ^ Analysis ID        ^ Short description ​        ^ SMS in SModelS ^ Result Type ^ Comment ^ ^ Analysis ID        ^ Short description ​        ^ SMS in SModelS ^ Result Type ^ Comment ^
-| ATLAS-SUSY-2015-06 | multijet + MET, 3.2 fb-1  | T1, T2         | EM |  +| ATLAS-SUSY-2015-06 | multijet + MET, 3.2 fb-1  | T1, T2         | EM | superseded by 36 fb-1 analysis ​
-| ATLAS-SUSY-2016-07 | multijet + MET, 36 fb-1   ​| ​--             -- should include this in SModelS |+| ATLAS-SUSY-2016-07 | multijet + MET, 36 fb-1   ​| ​T1, T2, T5ZZ, T5WW(off) ​EM | in SModelS ​develop ​|
 | CMS-SUS-16-033 ​    | multijet + MET, 36 fb-1   | T1, T1bbbb, T1tttt(off),​ T2, T2bb, T2tt(off) | UL |  | CMS-SUS-16-033 ​    | multijet + MET, 36 fb-1   | T1, T1bbbb, T1tttt(off),​ T2, T2bb, T2tt(off) | UL | 
 | CMS-SUS-16-039 ​    | multilepton EWK  | TChiWZ(off),​ TChiWH, TChipmSlep... | UL |  | CMS-SUS-16-039 ​    | multilepton EWK  | TChiWZ(off),​ TChiWH, TChipmSlep... | UL | 
-| CMS-SUS-16-052 ​    | 1L stop, soft    | T2bbWWoff, T6bbWWoff ​(only PAS version!)| UL, aggregated ​EM | +| CMS-PAS-SUS-16-052 ​    | 1L stop, soft    | T2bbWWoff, T6bbWWoff | UL, agg-EM |  ​|
 | CMS-SUS-17-001 ​    | 2L stop          | T2tt(off), T6bbWW | UL  |  | CMS-SUS-17-001 ​    | 2L stop          | T2tt(off), T6bbWW | UL  | 
  
 +See also http://​madanalysis.irmp.ucl.ac.be/​wiki/​PublicAnalysisDatabase
  
-=== ColliderBit ​vs SModelS correspondence (13 TeV): ===+ 
 +=== ColliderBit ​SModelS correspondence (13 TeV): ===
  
 ^ Analysis ID        ^ Short description ​        ^ SMS in SModelS ^ Result Type ^ Comment ^ ^ Analysis ID        ^ Short description ​        ^ SMS in SModelS ^ Result Type ^ Comment ^
-| ATLAS-SUSY-2016-07 | multijet + MET    -- -- should include this in SModelS |+| ATLAS-SUSY-2016-07 | multijet + MET   ​T1, T2, T5ZZ, T5WW(off) ​EM | in SModelS ​develop ​|
 | ATLAS-SUSY-2016-15 | 0L stop   | --             | -- | should include this in SModelS |  ​ | ATLAS-SUSY-2016-15 | 0L stop   | --             | -- | should include this in SModelS |  ​
 | ATLAS-SUSY-2016-16 | 1L stop   | --             | -- | should include this in SModelS | | ATLAS-SUSY-2016-16 | 1L stop   | --             | -- | should include this in SModelS |
 | ATLAS-SUSY-2016-17 | 2L stop   | T2tt(off), T2bbWWoff | UL | should include this in SModelS | | ATLAS-SUSY-2016-17 | 2L stop   | T2tt(off), T2bbWWoff | UL | should include this in SModelS |
 | ATLAS-SUSY-2016-28 | b-jets + MET   | --             | -- | should include this in SModelS | | ATLAS-SUSY-2016-28 | b-jets + MET   | --             | -- | should include this in SModelS |
-| ATLAS-SUSY-2016-24 | multilepton EWK   ​| ​--             | -- | should include this in SModelS |+| ATLAS-SUSY-2016-24 | multilepton EWK   ​| ​(UL: TChiWZ, TSlepSlep, ...) (EM: TChiWZ) ​            | -- | should include this in SModelS ​(currently in Philipp'​s branch) ​|
  
 | CMS-SUS-16-033 ​    | multijet + MET    | T1, T1bbbb, T1tttt(off),​ T2, T2bb, T2tt(off) | UL |  | CMS-SUS-16-033 ​    | multijet + MET    | T1, T1bbbb, T1tttt(off),​ T2, T2bb, T2tt(off) | UL | 
Line 41: Line 56:
 | CMS-SUS-16-034 ​    | SFOS lept. + jets  | T5ZZ, TChiWZ | UL | only on-Z SRs in ColliderBit | | CMS-SUS-16-034 ​    | SFOS lept. + jets  | T5ZZ, TChiWZ | UL | only on-Z SRs in ColliderBit |
 | 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 ====
 +
 +Members: Sezen, Wolfgang (, Harrison)
 +
 +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)
 +
 +  * 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.
 +
  
2019/groups/tools/correlations.txt · Last modified: 2019/06/27 17:10 by sezen.sekmen