User Tools

Site Tools


2015:groups:tools:lhaad:proposal2

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
2015:groups:tools:lhaad:proposal2 [2015/06/19 16:46]
nishita.desai
2015:groups:tools:lhaad:proposal2 [2015/06/22 15:36] (current)
daniel.schmeier
Line 9: Line 9:
  
 The idea is to write a plain text file that can be read easily into The idea is to write a plain text file that can be read easily into
-xml if needed (and hence universally readable). ​ The name of the block become sthe xml tag.  Anything that follows is turned into attributes. e.g. "name ATLAS" inside the block becomes <​experiment name="​ATLAS">​. ​ Anything inside the block starting with "#"​ is added as a comment, i.e. the first block below automatically ​converts to  +xml if needed (and hence universally readable). ​ The name of the block become sthe xml tag.  Anything that follows is turned into attributes. e.g. "name ATLAS" inside the block becomes <​experiment name="​ATLAS">​. ​ Anything inside the block starting with "#"​ is added as a comment, i.e. the block  
 +<code autoconf>​ 
 +info analysis 
 +  # Details about experiment  
 +  id ATLAS-2014-XXX 
 +  publication JHEP11(2014)118 
 +  sqrtS 8.0 
 +  lumi 20.0 
 +</​code>​ 
 +converts to
 <code autoreconf>​ <code autoreconf>​
 <info name="​analysis"​ id="​ATLAS-2014-XXX"​ publication="​JHEP11(2014)118"​ sqrtS="​8.0"​ lumi="​20.0"​ description="​Details about analysis">​ <info name="​analysis"​ id="​ATLAS-2014-XXX"​ publication="​JHEP11(2014)118"​ sqrtS="​8.0"​ lumi="​20.0"​ description="​Details about analysis">​
Line 53: Line 61:
   ptmin 20   ptmin 20
   etamax 2.5   etamax 2.5
-  pileup_sub _link_ 
   # Can provide code and/or link to writeup with details of implementation   # Can provide code and/or link to writeup with details of implementation
   code _code_link   code _code_link
-  doc _link_to_file_with_details +  doc _link_to_file_with_details 
 +  doc _link_to_doc_about_pilup_removal
  
 function isolation ​ function isolation ​
Line 119: Line 127:
  
 function mt function mt
-  # mT requires one lepton and met i.e. mt(lep(1),met)+  # mT requires one lepton and met i.e. mt(lep.1,met)
   arg1 detectorobj   arg1 detectorobj
   arg2 detectorobj   arg2 detectorobj
Line 185: Line 193:
   eff 0.95   eff 0.95
   trigger e_trigger.OR.mu_trigger.OR.met_trigger   trigger e_trigger.OR.mu_trigger.OR.met_trigger
-  select ​pt(lep(1))>25 +  select lep.1.pt>25 
-  reject ​size(lep)>1 +  reject lep.size>1 
-  select ​size(jet)>2+  select jet.size>2
   select met>100   select met>100
  
Line 193: Line 201:
 cut tN_diag cut tN_diag
   contains preselect   contains preselect
-  select size(jet)>4 +  select ​jet.size>4 
-  select ​pt(jet,1)>60 +  select jet.1.pt>60 
-  select ​pt(jet,2)>60 +  select jet.2.pt>60 
-  select ​pt(jet,3)>40 +  select jet.3.pt>40 
-  select ​pt(jet,4)>25 +  select jet.4.pt>25 
-  select mt(lep(1),​met)>​=60+  select mt(lep.1,​met)>​=60
   select m(hadtop)>​=130   select m(hadtop)>​=130
   select m(hadtop)<​=205   select m(hadtop)<​=205
   reject size(tau)>​0   reject size(tau)>​0
-  select deltaR(bjet(1),lep(1))<2.5+  select deltaR(bjet.1,lep.1)<2.5
   select metBYsqrtHT>​5   select metBYsqrtHT>​5
-  select delPhi(jet(1),​met)>​0.8 +  select delPhi(jet.1,​met)>​0.8 
-  select delPhi(jet(2),​met)>​0.8+  select delPhi(jet.2,​met)>​0.8
  
 </​code>​ </​code>​
  
 ====== Part 3: Present results of the analysis. ​ Give numbers, exclusions, digitised histograms, link to plots, etc. ====== ====== Part 3: Present results of the analysis. ​ Give numbers, exclusions, digitised histograms, link to plots, etc. ======
 +
 +We need to think about information that is absolutely necessary for validation and whether to put it in the same kind of info block (which are currently entirely optional).
  
 <code autoconf>​ <code autoconf>​
2015/groups/tools/lhaad/proposal2.1434725214.txt.gz · Last modified: 2015/06/19 16:46 by nishita.desai