Differences

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

--- 2015:groups:tools:lhaad:proposalgrenoble [2016/02/26 10:16]
daniel.schmeier created
+++ 2015:groups:tools:lhaad:proposalgrenoble [2016/02/26 14:26] (current)
daniel.schmeier
@@ Line 1: / Line 1: @@
 This is the proposal from the LHADA Meeting in Grenoble at the end of February 2016.
 It is based on the "latest" combined proposal.
+Here are some things which were discussed during the meeting and which should be considered when updating the proposal
+  -  Binning does not need to be a separate block but can be done at the end of a "cut" block
+  -  "Select" and "Reject" from MadAnalysis5 syntax, as they have a working parser framework
+  -  "weight" keyword necessary, which reweights an event which has to pass that certain histograms at the end of a cutblock, either in form NBins:Min:Max or Bin1;Bin2;Bin3;...;Bin
+  - function calls as in Python-kwargs: isolation(source=tracks,ptmin=10,dR=0.5) to make it easier to read
+  - analysis and results clearly separated, i.e. not put result numbers in cut blocks
+  - rename "detectorobj"
+  - detectobj needs a "change" keyword which can smear objects, not jet select/reject them.
+  - some functions need booleans to be deactivatable, because depending on being phenomenologist or experimentalist, or depending on if one uses Delphes, Rivet, FullSim,... functions might be necessary or not (e.g. smearing functions)
 ====== General Structure ======
@@ Line 22: / Line 34: @@
   - **function** (defines functions that act on these)
   - **cut** (blocks of cuts)
-  - **binning** (following Daniel's idea, for complex descriptions of orthogonal signal regions)
   - **info** (for meta information chosen by the implementer, e.g. information about publication, conf-notes, theory papers used for interpretation, benchmarks, etc.)
@@ Line 55: / Line 66: @@
 ==== function =====
 <code autoconf>
+ALTERNATIVE 1
 function function_name
-  arg1 type-of-arg1
+  arg1 type-of-arg1:name-of-arg1
-  arg2 type-of-arg2
+  arg2 type-of-arg2:name-of-arg2
   return type-of-returnvalue
+  code link-to-actual-code
+  doc link-to-documentation
+</code>
+ALTERNATIVE 2
+<code autoconf>
+function function_name
+  arg1 name-of-arg1
+  arg2 name-of-arg2
   code link-to-actual-code
   doc link-to-documentation
 </code>
 Rules:
-  * allowed keywords: argX, return, code, doc
+  * allowed keywords: argX,  code, doc
-  * argX must count from 1 upwards
+  * argX must count from arg1 upward
+  * all values of the argX- commands must differ
   * it is recommended to follow with a comment about its meaning after each argument
-  * allowed types: int, float, string, bool, detectorobj, tlorentzvector, X-list (X is any of the allowed types)
+  * If typed,allowed types: int, float, string, bool, detectorobj, tlorentzvector, X-list (X is any of the allowed types)
   * for type 'detectorobj' it should be clear from the documentation which information the detectorobj needs to have
 Example:
 <code autoconf>
+ALTERNATIVE 1
 function isolation
   ### Sums up activity in the vicinity of a given candidate
-  arg1 detectorobj # a single electron, muon or photon
+  arg1       detectorobj:candidate # a single electron, muon or photon
-  arg2 string      # "calo", "tracks", "eflow"
+  arg2       string:isosource      # "calo", "tracks", "eflow"
-  arg3 float       # dR cone to be probed
+  arg3       float:dR              # dR cone to be probed
+  arg4       float:ptmin           # minpt of objects to be counted
+  arg5       bool:relIso           # divide by candidate's pt?
+  returnType float # sum of pT of the respective surrounding objects
+  code http://google.de
+  doc http://google.de
+ALTERNATIVE 2
+function isolation
+  ### Sums up activity in the vicinity of a given candidate
+  arg1 cand # a single electron, muon or photon
+  arg2 src      # "calo", "tracks", "eflow"
+  arg3 dR       # dR cone to be probed
   arg4 ptmin       # minpt of objects to be counted
-  arg5 bool        # divide by candidate's pt?
+  arg5 relIso        # divide by candidate's pt?
-  return float # sum of pT of the respective surrounding objects
   code http://google.de
   doc http://google.de
@@ Line 110: / Line 144: @@
   ### Loose muons
   take external
-  select isolation(muon_l.?, 'tracks', 0.4, 0.5)<0.1
+  select isolation(cand=muon_l.?, src='tracks', dR=0.4, ptmin=0.5)<0.1
   code http://muons.mu
   doc http://checkmate.muons.mu
@@ Line 117: / Line 151: @@
   ### loose electrons
   take external
-  select isolation(elec_l.?, 'tracks', 0.4, 0.5)<0.1
+  select isolation(cand=elec_l.?, src='tracks', dR=0.4, ptmin=0.5)<0.1
-  reject overlap(elec_l.?, muon_l, 0.4)
+  reject overlap(cand=elec_l.?, neigb=muon_l, dR=0.4)
   code http://elecs.el
   doc http://checkmate.elecs.el
@@ Line 125: / Line 159: @@
   ### medium electrons
   take elec_l
-  select hasMediumTag(elec_l.?)
+  select hasMediumTag(cand=elec_m.?)
   code http://elecs.el/medium
   doc http://checkmate.elecs.el/medium
@@ Line 468: / Line 502: @@
   select etmiss.pt/HT(jets.1,jets.2,jets.3,jets.4)>5
   select dPhi12
+  bin etmiss=100;125;150;inf
+  bin mT=60;90;120;140;inf
+results tN_diag_results:
+  columns name                 obs    bkg    dbkg
+  entry   tN_diag_g100_g60   3452   3452   59
+  entry   tN_diag_g100_g90   1712   1720   161
+  entry   tN_diag_g100_g120  313    295    50
+  entry   tN_diag_g100_g140  201    235    34
+  entry   tN_diag_g125_g60   2018   2018   45
+  entry   tN_diag_g125_g90   768    767    80
+  entry   tN_diag_g125_g120  117    136    22
+  entry   tN_diag_g125_g140  163    152    30
+  entry   tN_diag_g150_g60   2543   2543   50
+  entry   tN_diag_g150_g90   647    684    79
+  entry   tN_diag_g150_g120  98     13     101
+  entry   tN_diag_g150_g140  217    236    29
 CUT tN_med
@@ Line 495: / Line 549: @@
   select dRbl<3.0
   select HtMissSig>12.5
+results tN_med_high_results:
+  columns  name    obs  bkg   bkgerr
+  entry    tN_med  12   13.0  2.2
+  entry    tN_high 5    5.0   1.0
 </code>

Les Houches

User Tools

Site Tools

Differences

Page Tools