Line: 1 to 1  

Vertices with low p_{T} tracks
 
Line: 9 to 9  
Added:  
> >  Event galleryEventGalleryDijet  
Minimum biasMinimum bias Pythia p+p events at 14 TeV. Generated, simulated and reconstructed with CMSSW_1_2_0_pre1 with special code for low p_{T} reconstruction.  
Added:  
> >  Event galleryEventGallery  
Vertex resolutionDistribution of vertex residuals with the standard setting (PtMin=1GeV/c) and the low p_{T} setting (PtMin=0). 
Line: 1 to 1  

Changed:  
< <  Vertices with low p_{T} tracks  
> >  Vertices with low p_{T} tracks  
Changed:  
< <  Vertices with low pT tracks Minimum bias Pythia p+p events at 14 TeV . Generated, simulated and reconstructed with CMSSW_1_2_0_pre1.  
> >  Minimum bias Pythia p+p events at 14 TeV. Generated, simulated and reconstructed with CMSSW_1_2_0_pre1 with special code for low p_{T} reconstruction.  
Changed:  
< <  Vertex resolution Distribution of vertex residuals with the standard setting (PtMin =1GeV/c) and the low pT setting (PtMin =0).  
> >  
Changed:  
< <  The resolution has strong multiplicity dependence, shown here as function reconstructed track multiplicity NRecTracks .  
> >  Vertex resolutionDistribution of vertex residuals with the standard setting (PtMin=1GeV/c) and the low p_{T} setting (PtMin=0).  
Changed:  
< <  Multiple vertices Distribution of the number of reconstructed (charged pixel) tracks for several NVertices values is shown, that is for different number of found vertices. The following four plots are done with different vertex reconstruction parameters in RecoPixelVertexing /PixelVertexFinding/data/PixelVertexes.cff (ZSeparation, NTrkMin , PtMin ).  
> >  
Changed:  
< <  * Standard parameters: Only high multiplicity events give vertex.  
> >  The resolution has strong multiplicity dependence, shown here as function reconstructed track multiplicity NRecTracks.  
Changed:  
< <  * Lowering PtMin to 0: Now all tracks take part in vertex finding. Even low multiplicity events give a vertex, if, say, NRecTracks > 8.  
> >  
Changed:  
< <  * Even looser: Lowering NTrkMin to 2. This choice gives vertex to very low multiplicity events, but at the same time many events will have multiple vertices.  
> >  Multiple vertices  
Changed:  
< <  * Even looser: Increasing ZSeparation to 0.5 cm. A possible cure of the previous problem.  
> >  Distribution of the number of reconstructed (charged pixel) tracks for several NVertices values is shown, that is for different number of found vertices. The following four plots are done with different vertex reconstruction parameters in RecoPixelVertexing/PixelVertexFinding/data/PixelVertexes.cff (ZSeparation, NTrkMin, PtMin).
Standard parametersOnly high multiplicity events give vertex.
Lowering PtMin to 0Now all tracks take part in vertex finding. Even low multiplicity events give a vertex, if, say, NRecTracks > 8.
Even looserLowering NTrkMin to 2. This choice gives vertex to very low multiplicity events, but at the same time many events will have multiple vertices.
Even looserIncreasing ZSeparation to 0.5 cm. A possible cure of the previous problem.  
 FerencSikler  12 Nov 2006  
Changed:  
< < 
 
> > 

Line: 1 to 1  

Added:  
> >  Vertices with low p_{T} tracksVertices with low pT tracks Minimum bias Pythia p+p events at 14 TeV . Generated, simulated and reconstructed with CMSSW_1_2_0_pre1. Vertex resolution Distribution of vertex residuals with the standard setting (PtMin =1GeV/c) and the low pT setting (PtMin =0). The resolution has strong multiplicity dependence, shown here as function reconstructed track multiplicity NRecTracks . Multiple vertices Distribution of the number of reconstructed (charged pixel) tracks for several NVertices values is shown, that is for different number of found vertices. The following four plots are done with different vertex reconstruction parameters in RecoPixelVertexing /PixelVertexFinding/data/PixelVertexes.cff (ZSeparation, NTrkMin , PtMin ). * Standard parameters: Only high multiplicity events give vertex. * Lowering PtMin to 0: Now all tracks take part in vertex finding. Even low multiplicity events give a vertex, if, say, NRecTracks > 8. * Even looser: Lowering NTrkMin to 2. This choice gives vertex to very low multiplicity events, but at the same time many events will have multiple vertices. * Even looser: Increasing ZSeparation to 0.5 cm. A possible cure of the previous problem.  FerencSikler  12 Nov 2006
