BFC chain:
"pp2009c ITTF VFPPVnoCTB BEmcChkStat beamLine Corr4 OSpaceZ2 OGridLeak3D -dstout -evout"

run in stardev

Run on W triggered events

QA code is at:

/star/u/rjreed/PPV2009/Eval500GeV03

 198003 events

 162913 with at least 1 vertex with rank > 0

1353 with bbc Vz values |bbcVz|<=200

vpd Vz distribution is still strange

See http://drupal.star.bnl.gov/STAR/blog/rjreed/2009/aug/19/ppv-500-gev-test-run-qa for previous QA

Figure 1: # of positively ranked vertices per event

Figure 2: Rank of index 0 (black) and index 1 (red) vertices.

Figure 3: Vz of index 0 vertices with rank >0

Figure 4: # of BEMC matches for index 0 vertices with rank > 0

Figure 5: # of EEMC matches for index 0 vertices with rank > 0

Figure 6: # of TPC CM matches for index 0 vertices with rank > 0

Figure 7: # of tracks used to construct index 0 vertex with rank > 0

Figure 8: Refmult associated with index 0 vertex with rank > 0

Figure 9: bbc Vz as obtained by muEvent->bbcTriggerDetector().zVertex()

Figure 10: vpd Vz as obtained by muEvent->vpdTriggerDetector().TimeDifference()*(-1) which came out of discussion over previous vpd Vz results.  I will need to rerun and see if this is fixed when I try to obtain Vz from correct method.

Figure 11: Zoomed in vpd vz.  I'm concerned over why there appear to be so many more vpd Vz vertices than bbc.