Fork me on GitHub

Changes between Version 5 and Version 6 of WorkBook/PileUp


Ignore:
Timestamp:
Mar 6, 2013, 11:34:38 AM (12 years ago)
Author:
Michele Selvaggi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkBook/PileUp

    v5 v6  
    88=== Mixing pile-up ===
    99
    10 The mixing procedure is done via the "PileUpMerger" module. The user can specify 4 parameters: PileUpFile, MeanPileUp, ZVertexWidth, ZVertexResolution.
     10The mixing procedure is done via the {{{PileUpMerger}}} module. The user can specify 4 parameters: {{{PileUpFile}}}, {{{MeanPileUp}}}, {{{ZVertexWidth}}}, {{{ZVertexResolution}}}.
    1111
    12 * PileUpFile:
     12* {{{PileUpFile}}}:
    1313
    1414the event sample containing pile-up events in binary format. This format allows for faster random event access compared to root trees. Basic information about the event is contained (particle 4-momenta, vertex position, and Particle ID)
     
    1616This sample has to be generated in advance with an event generator (typically Pythia6/8 or HERWIG) and then converted into binary format.
    1717
    18 * MeanPileUp:
     18* {{{MeanPileUp}}}:
    1919
    2020the average amount of pile-up events per bunch-crossing. For each hard scattering, N pile-up events will be randomly chosen from the PileUp file, where N is a random number following Poisson statistics with a mean MeanPileUp.
    2121
    22 * ZVertexWidth:
     22* {{{ZVertexWidth}}}:
    2323
    2424Pile-up events randomly populate the z-axis. The position of each pile-up event is generated from a gaussian distribution with a standard deviation ZveterxWidth.
    2525
    26 * ZVertexResolution
     26* {{{ZVertexResolution}}}
    2727
    2828For |z|< ZVertexResolution the hard interaction vertex cannot be distinguished from pile-up vertices. For such pile-up events both charged and neutrals are then merged in the event (no charged particle subtraction).