User Tools

Site Tools


2013:groups:tools:substructure

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
2013:groups:tools:substructure [2013/06/06 11:51]
gregory.soyez [Methods]
2013:groups:tools:substructure [2013/06/07 15:46] (current)
andy.buckley [Software version 1] Link to Bitbucket, etc.
Line 39: Line 39:
 ==== Software version 1 ==== ==== Software version 1 ====
  
-Pile-up can be added dynamically using this **{{:​2013:​groups:​tools:​anal02.tar.gz| ​software}}**. The main concept here is that the ROOT based raw data is converted into an ''​Event'' ​obejct ​containing lists of ''​PseudoJet''​s (from ''​Fastjet''​) representing+Pile-up can be added dynamically using Peter'​s eventmanager software. All the software for the LH pile-up/​substructure studies is being developed through a [[https://​bitbucket.org/​andybuckley/​lh2013pileup/​overview|Bitbucket repository]]:​ you can check out without an account. Send a request for access if you want to commit (push) to the main code repository. 
 + 
 +(Previous version of software as a {{:​2013:​groups:​tools:​anal02.tar.gz| ​tarball}}.
 + 
 +The main concept here is that the ROOT based raw data is converted into an ''​Event'' ​object ​containing lists of ''​PseudoJet''​s (from ''​Fastjet''​) representing
  
   * the total particle (hadron) level event (signal + pile-up)   * the total particle (hadron) level event (signal + pile-up)
Line 45: Line 49:
   * the particle (hadron) level pile-up event    * the particle (hadron) level pile-up event 
  
-The code is not very convenient to use in this version. ​After unpacking with +The code is not very convenient to use in this version. ​On most systems I expect a
-<​code>​ +
-tar zxvf <​archive>​.tar.gz +
-</​code>​ +
-on most systems I expect a+
 <​code>​make all</​code>​ should work to compile the library and the example in ''​anal02.C''​. ​ For implementing your own analysis, please check the ''​anal02.C''​ and ''​Zprime_Py8::​analyze(Event&​ rEvt)''​ (your playground) in ''​Zprime_Py8.C''​ as examples. The program supports a few command line arguments <​code>​make all</​code>​ should work to compile the library and the example in ''​anal02.C''​. ​ For implementing your own analysis, please check the ''​anal02.C''​ and ''​Zprime_Py8::​analyze(Event&​ rEvt)''​ (your playground) in ''​Zprime_Py8.C''​ as examples. The program supports a few command line arguments
 <​code>​ <​code>​
Line 62: Line 62:
   * ''​--sigflist=<​file>''​ specifies a text file (no ""​ around file name!) with a list of signal files to be processed. If this list is not given, ''​Zprime_Py8::​analyze(...)''​ will not be invoked.   * ''​--sigflist=<​file>''​ specifies a text file (no ""​ around file name!) with a list of signal files to be processed. If this list is not given, ''​Zprime_Py8::​analyze(...)''​ will not be invoked.
   * ''​--puflist=<​file>''​ specifies a text file (no ""​ around file name!) with a list of pile-up files to be processed. If this list is not given, only signal events are analyzed (you should set ''​--mu=1''​ in this case!). ​   * ''​--puflist=<​file>''​ specifies a text file (no ""​ around file name!) with a list of pile-up files to be processed. If this list is not given, only signal events are analyzed (you should set ''​--mu=1''​ in this case!). ​
- 
  
 ===== Methods ===== ===== Methods =====
2013/groups/tools/substructure.1370512272.txt.gz · Last modified: 2013/06/06 11:51 by gregory.soyez