- General information
- Data readiness
- Grid and Cloud
- Infrastructure
- Machine Learning
- Offline Software
- Embedding
- Reconstruction
- Field Issues
- Reconstruction Code QA
- STAR Reconstruction Software
- Vertex finders
- KFParticle Vertex Finder
- PPV vertex
- STAR Vertex Finder Performance Comparison
- Simulation
- Production
- S&C internal group meetings
- Test tree
Comparison between PPV revision 1.29 and track pT change
Updated on Tue, 2008-09-09 14:12. Originally created by rjreed on 2008-09-08 01:49.
Under:
This compares the effiiciency of the current PPV vertex finder (revision 1.29 which includes PCT fix) to the suggested change of including tracks with 0.1 GeV < pT < 0.2 GeV to the algorithim. Currently PPV only uses tracks with pT > 0.2 GeV. Since tracks with 0.1 GeV will not reach the BEMC and would be rejected with the PPV algorithim, we've included only tracks with 0.1 < pT <0.2 which cross the central membrane and we did not require them to point to a tower.
The bfc code is at:
/star/data05/scratch/rjreed/PPV2008Eval/Vertex5/
The daq files processed as of 9/7/2008 are at:
/star/data05/scratch/rjreed/PPV2008Eval/MuDstPt100/
Table 1: Efficiency comparison between PPV revision 1.29 and altered PPV which accepts lower pT tracks. Matching with the vpd is defined as the rank 0 PPV vertex is with 20 cm of the vpd vertex, and matching with the bbc is defined as the rank 0 PPV vertex is within 60 cm of the bbc vertex.
Table 2: Break down of the number of events used to calculate the efficiencies of the altered PPV vertex algorithim.
Table 3: PPV revision 1.29 statistics posted here for ease of comparison
»
- Printer-friendly version
- Login or register to post comments