90 likes | 164 Views
SLHC Calorimeter Trigger software plans. M.Bachtis , S.Dasu, K.Flood, I.Ross University of Wisconsin. SLHC Calorimeter Trigger code. Code in two packages SLHCUpgradeSimulations/L1Trigger SimDataFormats/SLHC The golden file is here: SLHCUpgradeSimulations/L1Trigger/data/setup.xml
E N D
SLHC Calorimeter Trigger software plans • M.Bachtis, S.Dasu, K.Flood, I.Ross • University of Wisconsin
SLHC Calorimeter Trigger code Code in two packages SLHCUpgradeSimulations/L1Trigger SimDataFormats/SLHC The golden file is here: SLHCUpgradeSimulations/L1Trigger/data/setup.xml Contains all the configuration We have only one one By next week we will have a setup.xml for low/high PU The user just picks the xml he/she wants to use in SLHCUpgradeSimulations/L1Trigger/python/L1CaloTriggerSetup_cfi.py
Rate Calculation and Fast Simulation To calculate the trigger rate with the maximum possible accuracy one has to weigh each event in terms of the Pt hat of the events that are mixed with the original event Branson,Trepagnier CMS IN 2000/038 Fast Simulation does not allow this since it uses a custo event format for the events to be mixed We provided a tweak to get this info in the final event
Fast Simulation with PU Generator Precreated MinBias Simulation
Extension of the Fast Sim code We changed the format of the tree that has the MinBias to include the Pt hat of each event We recreated MinBias (5M – GEN only) with this info GEN only is extremely fast We changed the PileUpProducer to save a vector of the PtHat for each event PtHat recovered in the analyzer to create event weight
SLHCCaloTrigger studies methodology As the PU increases the event size is becoming to large The jobs are starting to become also I/O constrained What we usually do is not save the data Run Fast Simulation with specific PU / Algorithm configuration and plug the analysis at the end Get an ntuple which is small and fast Takes 3-4h to run 10 samples for 100K events each in UW However For studies that the optimal configuration is searched for specific PU it is better to store the data
Calorimeter Trigger output The CaloTrigger returned LV is different from the LV at vertex Not really in high Pt tracks The position resolutions we show are with ref to the vertex LV The tracking people should have in mind that they get the Calo Lorentz Vector Same output at GCT If the point on Calo surface is needed we can try to get it Depends on what the Trigger Tower Geometry has available
Matching For matching clusters to particles we use the BaseParticlePropagator (P.Janot) For a LorentzVector a charge and a vertex it returns the generated particle position on the ECAL surface Then using the energy of the particle we create the LV that the calo trigger would return. Then we match this LV with the Calo TP LV
Plans We will provide the needed configurations for different PU values Plots with efficiency and rate for each configuration will be uploaded on the twiki