2013:groups:tools:substructure
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
2013:groups:tools:substructure [2013/06/06 11:17] loch.peter [Configurations & Software] |
2013:groups:tools:substructure [2013/06/06 11:34] loch.peter [Software version 1] |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| The actual number of pile-up interactions added to the signal event is taken from a Poisson distribution around $\langle\mu\rangle$. | The actual number of pile-up interactions added to the signal event is taken from a Poisson distribution around $\langle\mu\rangle$. | ||
| - | ==== 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 containing lists of PseudoJets (from Fastjet) representing | + | 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 |
| * the total particle (hadron) level event (signal + pile-up) | * the total particle (hadron) level event (signal + pile-up) | ||
| Line 45: | Line 45: | ||
| * 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, on most systems I expect a | + | The code is not very convenient to use in this version. After unpacking with |
| - | <code>make all</code> should work to compile the library and the example in anal02.C. | + | <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> | ||
| + | anal02.exe --help --mu=<mu> --nevts=<number of (signal) events> | ||
| + | --sigflist=<text file with list of signal files> | ||
| + | --puflist=<text file with list of pile-up files> | ||
| + | </code> | ||
| + | Some hints: | ||
| + | * ''--help'' prints a brief usage instruction (which I think is not up-to-date, so please ignore!) | ||
| + | * ''--mu=<mu>'' expects the number of interactions per event. if ''<mu> < 0'', exactly ''|<mu>|'' interactions are collected into one event. ''<mu> > 0'' means a Poisson-distributed number of pile-up interactions will be collected from the pile-up (minimum bias) event samples. | ||
| + | * if you specify both signal and pile-up input, ''<mu>'' should be the number of pile-up events to be added to one signal event | ||
| + | * ''--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!). | ||
| + | |||
| ===== Methods ===== | ===== Methods ===== | ||
2013/groups/tools/substructure.txt · Last modified: 2013/06/07 15:46 by andy.buckley
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
