SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Large scale MC production

josie avatar
josie
11 diapositives · 269 Views · Oct 06, 2014

This document outlines a comprehensive proposal for large-scale Monte Carlo (MC) production, focusing on MC DSTs. It discusses key production challenges, such as the necessary background insertion and resource allocation for efficient computation. The initial proposal includes producing 500 pb-1 of KS, yielding approximately 500 million events, achievable in 2-3 months with optimal conditions. The outlines of background integration, upgrades in data reconstruction, and trial runs are also detailed. The proposal emphasizes the importance of consistency with previous datasets and seeks feedback on ambitious expansion.

#large scale mc production #large scale mc production ppt #powerpoint #presentation
Large scale MC production - slide 1
01 / 11Large scale MC production
1 / 17

Télécharger la présentation

Large scale MC production
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Large scale MC production M. Moulson Offline Discussion, 21 October 2002 • Outline • What to produce? • How to produce? • Proposal for MC DST’s • Timescale and tasking

  2. What to produce? • My original proposal: • 500 pb-1 of KS all, KL all  500M events • 2—3 months if done efficiently on AIX farm • Useful for background studies for all neutral kaon analyses • Universally approved (?) • Only counter-proposal to require KL decay before EmC • Should we consider being more ambitious? •  all: 500 pb-1  1.5 M events, 6—9 months • See how it goes, maybe try K+K- next, if there is demand

  3. Main issues for production • To what extent do these issues need to be resolved before we start generating? • Upgrades to geanfi/datarec • Production of MC DST’s • Insertion of machine background • Allocation of computing resources

  4. Upgrades to MC • Are there upgrades planned that must be finished before production starts? • Initial state radiation • Wire sag in DC • Different on first ~10 layers. Easy to implement. • Probably best not to include in reconstruction for consistency with 2001-2002 data • Thickness of DC wall • Missing 100 um of Al, 50 um too much CF (to be checked) • Should be easy to correct • Other issues?

  5. DST’s for MC events: a proposal • Produced from mcr output • Reconstruction bankset exactly identical to data DST’s • MC-truth bankset highly compressed • All variables needed to fill PROD2NTU structures precalculated and stored • Banks eliminated: • MC hit banks (DHIT, CHIT) • MC raw-bank equivalents (MCEL, MDTC) • MC link banks (CEKA, DTHA)

  6. Bank list and data structures

  7. Background insertion: status • Desirable to introduce background for large scale production • Probably will not be complete on timescale for starting generation but could become ready shortly afterwards • Begin generation/first reconstruction anyway? • Status: Code is under development • Background selection criteria: Miscetti • Insertion module: Moulson, Patera • Haven’t seriously begun to address logistics yet.

  8. Background insertion: plans • Global sampling proposal: • Harvest background from all 2001-2002 data: • Recognized gg events have s  120 nb-1 • ~50M gg events in 450 pb-1, ~100 GB volume • Insert each background event in ~10 MC events • If gg selection efficiency not significantly dependent on background, obtain background profile that matches data • MC sample then refers to entire data set, not easy to subdivide • Can also subdivide into run groups. How big should they be? • Larger means better averaging, simpler organization • 2001, 2002 defined by separate MC run ranges (in any case) • Groups should be of order ~10 pb-1 to avoid problems matching size of MC (35 nb-1) and data (100—200 nb-1) files

  9. Possible scheme for production .dst × BEFORE background available geanfi datarec .mcr .mcr geanfi background +datarec AFTER background available .dst

  10. Allocation of computing resources • Current CPU allocation: • AIX (92 CPU’s): • Users: 16 (fibm11—fibm14) • DST’s: 8 (fibm30, fibm32) • Reconstruction: 68 (all others except fibm16) • SunOS (40 CPU’s, ~16 AIX equivalent) • Users: 8 (fsun01, fsun02) • MC production: 32 • Big tasks during coming months: MC production, kpm DST’s • Need ~54 IBM CPU’s to complete MC production in 60 days • Assumes 1M evt/day/(40 Sun CPU’s), 1 IBM CPU = 2.5 Sun CPU’s • Very desirable to produce kpm DST’s on IBM nodes: • Also desirable to produce MC events on IBM nodes?

  11. Task list • MC upgrades: • ISR ____________________ • DC geometry ____________________ • MC DST’s • Bank-reduction code Moulson ____________ • Database modifications ____________________ • Background insertion • Event selection Miscetti • Coding Moulson, Patera, Miscetti • Testing Others • Resource allocation ____________________ Other issues? Volunteers?