1 / 6

pp-pileup in MDC4

This document presents a detailed overview of the MDC4 performance in modeling pp collision events, highlighting goals, statistical analysis, and vertex finder efficiency. Key issues encountered, such as system crashes and corrupted data, are addressed alongside fixes applied. A total of 100,000 pp events were processed with considerations for leading particle reconstruction efficiency, signal-to-noise ratios, and track generation using PYTHIA 6.1. The resulting performance metrics indicate successful processing and analysis within the STAR framework.

osias
Télécharger la présentation

pp-pileup in MDC4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. pp-pileup in MDC4 • Goals • MDC4 statistics • vertex finder performance (ppLMV) • leading particle recon efficiency Jan Balewski, IUCF Star Analysis Meeting May 13, 2001 , BNL

  2. MDC4 overview • Small problems of MDC4: • crash after ~400 eve  fixed • SVT crash on empty eve  fixed • root crash after 15,000 eve  fixed • root version RCF vs. PDSF  recompiled • NFS problem corrupted DST  rerun • 100,000 pp events processed • PYTHI 6.1, minbias, nondiffractive • GSTAR with y2001 (actual) geometry • 8 pileup events added • root4star --> ppDST • ‘spin sorted’ -distributions for rLP • ResourcesMDC4=1 hour of STAR • CPU : 50 sec/event •  total 1400 hours CPU •  1000 jobs with 100 events •  2 days on 100 CPU (real time) Thanks to Yuri, Lidia, Helen and all other for help

  3. MDC4: pp event topology in 2001 L=4•1030cm-2s-1,NON DIF =28 mb Collision rate = 120 KHz 60 bunches/ring  213 nsec 1 coll/50 bunches = 1 coll/10 sec 40 sec TPC drift  8 coll/ TPC frame pileup  few 100 tracks in TPC diamond total width of ± 15 cm PYTHIA minbias trigger event, generated at s=200 GeV Leading Particle Track color encodes its transverse momentum (GeV/c) Y 104 Total 105 events ( 1 hour of STAR) X minbias trigger 12 primary tracks, ~30 TPC tracks Leading Particle pT (GeV/c)

  4. MDC4: Vertex finder (ppLMV) -2 -2 0 0 2 2 Only TPC tracks used with 8 pileup’s /event (without pileup in green) RMS=6.7 cm generated =7.5 cm Z (cm) RMS=4.7 mm (3.2 mm) ‘efficiency’=96% (90%) signal/noise =5/2 (68/1) RMS=4.3 mm (3.2 mm) Vertex Z (cm) Vertex X (cm)

  5. MDC4: Efficiency of ppLMV vs. LP pT 0 0 1.5 1.5 -1.5 -1.5 Only TPC tracks used with 8 pileup’s /event Leading Particle pT <1 GeV/c RMS=5.1 mm signal/noise =5/2 pT =[2,3] GeV/c RMS=3.3 mm signal/noise =9/1 pT =[1,2] GeV/c RMS=3.9 mm signal/noise =6/1 Vertex Z (cm) Vertex Z (cm)

  6. MDC4: Reconstructed LP vs.  With 8 pileup’s per event (no SVT) No pileup (no SVT) GeV/c GeV/c problem GeV/c GeV/c  of recon LP (deg)  of recon LP (deg)

More Related