This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
2013:groups:tools:substructure [2013/06/06 11:26] loch.peter [Software version 1] |
2013:groups:tools:substructure [2013/06/06 11:31] loch.peter [Software version 1] |
||
---|---|---|---|
Line 52: | Line 52: | ||
<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> | ||
- | anal02.exe --help --mu=<mu> --nevts=<number of (signal) events | + | anal02.exe --help --mu=<mu> --nevts=<number of (signal) events> |
--sigflist=<text file with list of signal files> | --sigflist=<text file with list of signal files> | ||
--puflist=<text file with list of pile-up files> | --puflist=<text file with list of pile-up files> | ||
</code> | </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 | ||