2008 evaluation

Status: Evaluation of current BFC, no changes to PPV code yet

2008 PPV evaluation plan

Run #9069005 will be used

http://online.star.bnl.gov/RunLog/Summary.php?run=9069005
 

 

Trigger Name Trigger ID # Events daq source file needed daq files expected # triggers
zerobias 9300 525 st_zerobias all 525
toftpx 220710 354459 st_toftpx 5 90000
fms-slow 220981 29914 st_fmsslow 20 20000
bbc 220000 2646 st_physics all 2646
bh1-mb 220510 8612 st_physics all 8612
etot-mb-l2 7 2853 st_physics all 2853
jp1-mb-l2 8 5676 st_physics all 5676
bh2-mb-slow 220520 14236 st_physics all 14236

 daq files are located at

/star/data03/daq/2008/069/

9069005f 9069005t  9069005z  9069005p
 

bfc.C will be run in stardev with options:

root4star -b -q  bfc.C'(1,1e6,"DbV20080820 pp2008 ITTF OSpaceZ2 OGridLeak3D beamLine VFPPVnoCTB debug logger","/star/data03/daq/2008/069/*")'

 

The verision of PPV includes the August 2008 change that Post Crossing Tracks are dropped which was enacted in response to the change of the TPC cluster finder

 

MuDst files will be placed at:

/star/data05/scratch/rjreed/PPV2008Eval/*

 

Observables to Monitor:

# primary vertices

Z location primary vertices

delta Z between primary vertex z position and bbc or vpd z position

# tracks associated with each primary vertex

 

Cuts to Monitor:

mMinTrkPt (Currently 0.20)

mMinFitPfrack (Currently at 0.70)

Include all EEMC rings

mMaxZradius

Weights for TPC, EEMC, BEMC

 

 

2008 PPV performance Revision 1.29

PPV performance Revision 1.29

Updated 9/7/2008

Table 1 : # of Events processed as of Sept 7.
Trigger Name Trigger ID # # Events Expected # Events Run
zerobias 9300 525 525
toftpx 220710 90000 28720
fms-slow 220981 20000 14299
bbc 220000 2646 938
bh1-mb 220510 8612 7507
etot-mb-l2 7 2853 2506
jpt-mb-l2 8 5676 4983
bh2-mb-slow 220520 14236 12507

 

Table 2: Summary of Vertex finding efficiency and vertex matching with events processed by Sept 2.  For the vpd, matched is defined as the 0 ranked PPV vertex is within 8 cm of the vpd vertex.  For the bbc, matched is defined as the 0 ranked PPV vertex is within 32 cm of the bbc vertex.

Table 3: Summary of Vertex finding efficiency and vertex matching with events processed by Sept 7.  For the vpd, matched is defined as the 0 ranked PPV vertex is within 20 cm of the vpd vertex.  For the bbc, matched is defined as the 0 ranked PPV vertex is within 60 cm of the bbc vertex.

 

 

zero bias

525 Events
# vertices,#events
0,461
1,62
2,2

5 Events with vpd + PPV vertex
15 Events with bbc + PPV vertex

Figure 2: Z postition of rank 0 vertex for zero bias trigger.  Rank 1 and above excluded due to low statistics.

 

Figure 3: Rank 0 PPV vertex Vz - vpd Vz for zero bias trigger.

toftpx

28720 Events
# Vertices, # Events
0,28110
1,565
2,39
3,6

559 Events with PPV rank 0 + vpd
393 Events match (within 8 cm)
41 Events with PPV rank 1 + vpd
7 Events match (within 8 cm)
558 Events with PPV rank 0 + bbc
428 Events match (within 32 cm)
44 Events with PPV rank 1 + bbc
20 Events match (within 32 cm)
509 Events with PPV rank 0 + bbc + vpd
296 Events match both vpd and bbc

 

Figure 5: Z position of rank 0 and rank 1 vertices for tof trigger.

Figure 6: Rank 0 PPV Vz - vpd Vz for tof trigger

Figure 7: Rank 0 PPV Vz - bbc Vz for the tof trigger

Figure 8: Delta Vz(PPV - vpdVz) vs delta Vz(PPV-bbc) for the tof trigger.

fms-slow

#Vertices,#Events

0,5504
1,7503
2,1173
3,110
4,8
5,1
2162 Events with PPV rank 0 + vpd
1435 Events match (within 8 cm)
389 Events with PPV rank 1 + vpd
98 Events match (within 8 cm)
6679 Events with PPV rank 0 + bbc
4617 Events match (within 32 cm)
1026 Events with PPV rank 1 + bbc
453 Events match (within 32 cm)
1954 Events with PPV rank 0 + bbc + vpd
992 Events match both vpd and bbc
 

Figures to be added later.

bbc

2646 Events

# Vertices, # Events
0,1157
1,1293
2,183
3,12
500 Events with PPV rank 0 + vpd
392 Events match (within 20 cm)
71 Events with PPV rank 1 + vpd
27 Events match (within 20 cm)
1409 Events with PPV rank 0 + bbc
1232 Events match (within 60 cm)
185 Events with PPV rank 1 + bbc
114 Events match (within 60 cm)
484 Events with PPV rank 0 + bbc + vpd
360 Events match both vpd and bbc


 

Figure 10: Vz position of PPV rank 0 and rank 1 vertices for the bbc trigger.

 

Figure 11: PPV Vz - vpd Vz for both rank 0 and rank 1 vertices for the bbc trigger.

 

Figure 12: PPV Vz - bbc Vz for both rank 0 and rank 1 vertices for bbc trigger

 

 

Figure 13: Delta Vz(PPV - vpdVz) vs delta Vz(PPV-bbc) for the bbc trigger.

bh1-mb

7507 Events

# Vertices, # Events

0,856
1,5494
2,1032
3,122
4,3
1761 Events with PPV rank 0 + vpd
1452 Events match (within 20 cm)
356 Events with PPV rank 1 + vpd
120 Events match (within 20 cm)
6275 Events with PPV rank 0 + bbc
5729 Events match (within 60 cm)
1082 Events with PPV rank 1 + bbc
676 Events match (within 60 cm)
1699 Events with PPV rank 0 + bbc + vpd
1309 Events match both vpd and bbc


 

Figure 15: Vz position of PPV rank 0 and rank 1 vertices for bh1 trigger

 

Figure 16: PPV Vz - vpd Vz for Rank 0 and Rank 1 vertices for bh1 trigger.

 

Figure 17: PPV Vz - bbc Vz for rank 0 and rank 1 vertices for bh1 trigger

 

 

Figure 18: Delta Vz(PPV - vpdVz) vs delta Vz(PPV-bbc) for the bh1 trigger.

 

etot-mb-l2

2506 Events

# Vertices, # Events
0,95
1,1768
2,539
3,96
4,7
549 Events with PPV rank 0 + vpd
380 Events match (within 20 cm)
204 Events with PPV rank 1 + vpd
61 Events match (within 20 cm)
2252 Events with PPV rank 0 + bbc
2013 Events match (within 60 cm)
599 Events with PPV rank 1 + bbc
367 Events match (within 60 cm)
530 Events with PPV rank 0 + bbc + vpd
339 Events match both vpd and bbc

 

 

Figure 20: Vz position of rank 0 and rank 1 vertices for etot trigger

 

 

Figure 21: PPV Vz - vpd Vz for rank 0 and rank 1 vertices for etot trigger

 

Figure 22: PPV Vz - bbc Vz for rank 0 and rank 1 vertices for etot trigger

 

Figure 23: Delta Vz(PPV - vpdVz) vs delta Vz(PPV-bbc) for the etot trigger.

 

jpt-mb-l2

4983 Events

# Vertices, # Events
0,240
1,3751
2,860
3,120
4,12
1114 Events with PPV rank 0 + vpd
869 Events match (within 20 cm)
292 Events with PPV rank 1 + vpd
84 Events match (within 20 cm)
4419 Events with PPV rank 0 + bbc
4040 Events match (within 60 cm)
927 Events with PPV rank 1 + bbc
553 Events match (within 60 cm)
1072 Events with PPV rank 0 + bbc + vpd
777 Events match both vpd and bbc

 

 

 

 

Figure 25: Vz position of rank 0 and rank 1 vertices for jp1 trigger.

 

 

 

 

Figure 26: PPV Vz - vpd Vz for jp1 trigger

 

Figure 27: PPV Vz - bbc Vz for jp1 trigger

 

Figure 28: Delta Vz(PPV - vpdVz) vs delta Vz(PPV-bbc) for the jp1 trigger.

 

bh2-mb-slow

12507 Events

# Vertices, # Events
0,1292
1,9168
2,1830
3,209
4,7
2970 Events with PPV rank 0 + vpd
2402 Events match (within 20 cm)
649 Events with PPV rank 1 + vpd
216 Events match (within 20 cm)
10555 Events with PPV rank 0 + bbc
9625 Events match (within 60 cm)
1929 Events with PPV rank 1 + bbc
1200 Events match (within 60 cm)
2861 Events with PPV rank 0 + bbc + vpd
2164 Events match both vpd and bbc

Figure 20: Vz position of rank 0 and rank 1 vertices for etot trigger

 

 

 Figure 26: PPV Vz - bbc Vz for jp1 trigger

 

 

Figure 23: Delta Vz(PPV - vpdVz) vs delta Vz(PPV-bbc) for the etot trigger.

 

Figure 27: PPV Vz - vpd Vz for jp1 trigger

 

Comparison between PPV revision 1.29 and track pT change

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

 

PPV Revision 1.29 high luminosity trigger details

 

The following data was taken with triggers: bh1-mb (ID 220510),  etot-mb-l2 (ID 7). jpt-mb-l2 (ID 8), and  bh2-mb-slow (ID 220520).  The total number of events in this set was 16351.
 

 

Figure1 : Delta Vz between PPV Vertex closest to the VPD vertex and the vpd.  PPV ranking was ignored.

Figure 2.  Delta Vz between second closest PPV vertex and vpd vertex.

 

 Figure 3:  This is figure 1 fitted with an unrestrained gaussian.

Figure 4:  This is Figure 1 and 2 (red) plotted on top of each other with a bin width of 6.3 cm (2 times the sigma fitted in Figure 3.)

Detailed event comparison PPV & VPD vertex, (Rosi)

 BFC

"DbV20080712 pp2008 ITTF OSpaceZ2 OGridLeak3D beamLine >VFPPVnoCTB  debug logger"
star/data05/scratch/balewski/2008-daq/st_fmsslow_9060086_raw_1090001.MuDst.root 

Detailed event count

1271 Events ,
256 Events with no PPV vertex,
271 Events with vpd vertex,
144 with at least one PPV vertex matching the vpd,
136 events with the 0 ranked vertex matching the vpd,
10 Events with the 1 ranked vertex matching the vpd ,
49 Events with no PPV vertex  and a vpd Vertex,
5 Events with multiple vertices matching the vpd ,
1 Event with 2 ranked Vertex matching the vpd (multiple match),
1 Event with 3 ranked vertex matching  the vpd (multiple match)

44 Events out of 222 with both PPV and vpd vertex have all vertices
outside of 50 cm of vpd. 11 of these have more than 1 PPV vertex

 Conclusion: out of 271 events with VPD vertex:

  • 49 (18%) has no PPV vertex
  • 151 (56%) has one of PPV vertex closer than 8 cm from VPD vertex
  • 71 (26%)  none of PPV vertices is closer than 8 cm to VPD vertex

 

VertexAnalysis8cm.txt file lists (for the events with a vpd vertex) the event #, # of vertices, rank of each vertex that matches vpd.

 

 

Details of Events with mismatched PPV VPD vertices with vertex location forced

I've run through 5 events where the vpd and the PPV vertices don't match.   daq file location is:

star/data05/scratch/balewski/2008-daq/st_fmsslow_9060086_raw_1090001.daq

 

Here are the PPV Vz values prior to "forcing" the values.  For the histograms, the solid red lines indicate the location of the vpd vertex and the circles indicate the location(s) of the PPV vertices.

EventID = 749 vpdVz = 98.2939 PPV vertices at Vz = -48.75 140.85

EventID = 2115 vpdVz = -34.348 PPV vertices at Vz = -106.55

EventID = 3346 vpdVz = -33.7838 PPV vertices at Vz = 129.35

EventID = 3952 vpdVz = 0.664319 PPV vertices at Vz =

EventID = 4447 vpdVz = 25.5813 PPV vertices at Vz = -99.95

 

For comparison, here is an event where the VPD vertex and PPV vertex were within 8 cm of each other:

 

All the important files (including the likelihood histograms and track multiplicities) can be found at:

/star/u/rjreed/Vertex3/Eventdaq*

 

Here are the results:

daq #7 EventID = 749 vpdVz = 98.2939 # PPV vertices = 10 at Vz = 90 92 94 96 98 100 102 104 106 108

Primaries that passed the cut (flag>0,  pt>0.2GeV, nFitP/nPoss>0.51):

id = 277 flag = 801 Nhits = 7 Npos = 11 pt = 0.370926 frac = 0.636364

id = 278 flag = 801 Nhits = 6 Npos = 11 pt = 0.250512 frac = 0.545455

id = 279 flag = 801 Nhits = 6 Npos = 11 pt = 0.271426 frac = 0.545455

id = 281 flag = 801 Nhits = 8 Npos = 11 pt = 1.57357 frac = 0.727273

id = 283 flag = 801 Nhits = 6 Npos = 11 pt = 0.638242 frac = 0.545455

id = 292 flag = 801 Nhits = 5 Npos = 9 pt = 0.292521 frac = 0.555556

id = 295 flag = 801 Nhits = 7 Npos = 11 pt = 0.213841 frac = 0.636364

 

daq #22  EventID = 2115 vpdVz = -34.348 N PPV vertices = 10 at Vz = -42 -40 -38 -36 -34 -32 -30 -28 -26 -24

Primaries that passed the cut:

id = 48 flag = 301 Nhits = 40 Npos = 45 pt = 0.362589 frac = 0.888889

id = 63 flag = 301 Nhits = 26 Npos = 34 pt = 0.602728 frac = 0.764706

id = 64 flag = 301 Nhits = 35 Npos = 45 pt = 0.392374 frac = 0.777778

id = 66 flag = 301 Nhits = 32 Npos = 45 pt = 0.772336 frac = 0.711111

id = 288 flag = 801 Nhits = 6 Npos = 11 pt = 2.56192 frac = 0.545455

id = 290 flag = 801 Nhits = 9 Npos = 11 pt = 0.206602 frac = 0.818182

id = 291 flag = 801 Nhits = 10 Npos = 11 pt = 0.556056 frac = 0.909091

id = 292 flag = 801 Nhits = 8 Npos = 11 pt = 0.722384 frac = 0.727273

id = 296 flag = 801 Nhits = 6 Npos = 11 pt = 0.236179 frac = 0.545455

id = 297 flag = 801 Nhits = 6 Npos = 11 pt = 0.267664 frac = 0.545455

id = 298 flag = 801 Nhits = 6 Npos = 11 pt = 0.9994 frac = 0.545455

id = 299 flag = 801 Nhits = 5 Npos = 8 pt = 0.332944 frac = 0.625

id = 300 flag = 801 Nhits = 9 Npos = 11 pt = 0.389091 frac = 0.818182

id = 310 flag = 801 Nhits = 5 Npos = 9 pt = 0.236941 frac = 0.555556

 

daq #44 EventID = 3346 vpdVz = -33.7838 N PPV vertices = 10 at Vz = -42 -40 -38 -36 -34 -32 -30 -28 -26 -24

Primaries that passed the cut:

id = 129 flag = 301 Nhits = 38 Npos = 42 pt = 0.352418 frac = 0.904762

id = 433 flag = 801 Nhits = 6 Npos = 9 pt = 0.73871 frac = 0.666667

id = 436 flag = 801 Nhits = 6 Npos = 11 pt = 4.33162 frac = 0.545455

id = 441 flag = 801 Nhits = 7 Npos = 11 pt = 1.19905 frac = 0.636364

id = 446 flag = 801 Nhits = 6 Npos = 11 pt = 2.52832 frac = 0.545455

 

daq #63 EventID = 3952 vpdVz = 0.664319 N PPV vertices = 10 at Vz = -8 -6 -4 -2 0 2 4 6 8 10

Primaries that passed the cut:

id = 177 flag = 301 Nhits = 35 Npos = 40 pt = 0.751434 frac = 0.875

id = 433 flag = 801 Nhits = 7 Npos = 11 pt = 1.16509 frac = 0.636364

id = 437 flag = 801 Nhits = 6 Npos = 10 pt = 0.277501 frac = 0.6

id = 440 flag = 801 Nhits = 6 Npos = 11 pt = 6.03469 frac = 0.545455

 

daq #70 EventID = 4447 vpdVz = 25.5813 N PPV vertices = 10 at Vz = 18 20 22 24 26 28 30 32 34 36

Primaries that passed the cut:

id = 324 flag = 311 Nhits = 9 Npos = 10 pt = 0.50257 frac = 0.9

id = 391 flag = 801 Nhits = 6 Npos = 11 pt = 0.332764 frac = 0.545455

Jan's notes

 -------- Loose notes, needs cleanup, Jan

Lidia's most recent test prodcution of 3 runs (89 files) also had
CTB matching off

 Low Lumi (run9060086), Mid Lumi (run9069059), High Lumi (run 9068124)
 /star/data10/reco/ppProduction2008/ReversedFullField/P08ic_test/2008/*/*
 log files on /star/rcf/prodlog/P08ic_test/log/daq

--------------

Akio's event classification  txt file from 3 files (with differnt luminosity) at the bottom of

http://www.star.bnl.gov/protected/spin/akio/200806/index_5th.html

from Lidia's test production. I checked that I get identical results
with Jan's production and Lidia's for the low lumi run.

-------------

Just remind you that there is "accidental match" between VPD and
TPC vertex up to ~25% (@ high lumi) under the peak.

--------------

* could you show Rosi how to print VPD & BBC vertex position in BFC?

Once Mudst is created, you can get VPD vertex (from TOF electronics) by
   StMuEvent->vpdVz()

For BBC I have not yet implemented the calibrated vertex. Once done,
one should be able to get it from
   StEvent->triggerDetectorCollection()->bbc()->zVertex()

--------- Rosi ---------

While I was doing this, I spun a macro over the MuDst in the folder
above and duplicated some of Akio's results, just to make sure I
understand.

 


So here are the z positions of the ranks 1 and 2 vertices and the vpd:

Fig 1.

 

Locations of Akio's pages in protected/spin

August 13, 3 runs produced with PPV w/o using CTB

----- 

 

PPV vs. VPD , by Xin

Fig 1. VPD-Minuit, d-Au 2008 events, minB events: ZDC East+VPD

 

Fig 2. VPD-PPV, p-p 2008 events, st_physics , no trig selection, mostly E & BEMC triggers

 

Hi Jan, Akio,

Xiaoping helped me to check the test 2008 pp production data Jan suggested. Please take a look at the attached plot. Basically what is plotted here is vz difference between vpd vertex and tpc vertex for different vpd hit configuration, similar to that in Akio's web page, but using the TOF electronics for vpd hit configuration selection.

So firstly we didn't see the ~30cm width gaussian component. The two narrow gaussian components are attributed to the VPD resolution. In the VPD timing resolution, we see a double gaussian structure, and with about a factor of 2-3 difference in widths. This is consistent with what we see here.  The largest ~50-60 cm gaussian component should be due to the fail of TPC VF and it is related to the beam vz distribution.

And secondly, the resolution in the (E,W)>(1,1) configuration is expected better than the configuration of (E,W)=(1,1). The "dilution" in vpd resolution with more hits seems not true to us.

Generally, we don't see an obvious issue on the VPD side. I am not sure if how the result will change when you use the DSM for selection. Or maybe your statistics is not good enough? Or the data are from some bad TOF runs?

Thanks and Best Regards

/xin

Jan Balewski wrote:
Hi Xin,
Those 2 analysis do not need to be contradicting.
There is much less pileup in dAu than in pp. There may be beam background in pp.

Can you investigate this effect in 2008 pp data from production requested by Matt  ~2 weeks ago, it is done, files are on data09,10.
http://www.star.bnl.gov/HyperNews-star/get/starprod/249/4/1/1/1/1/2.html
It is 3K daq files, 1M events w/ TPC , 1/4 of events have VPD vertex, ~90 % have TPC vertex produced by  fixed PPV.

Thanks
Jan



On Oct 1, 2008, at 11:40 PM, Xin Dong wrote:

Hi Akio,

Thanks for this message. Actually we always see the resolution will be improved if we require more VPD hits. I don't quite understand the ~25cm gaussian distribution at this step. Xiaoping helped me check the dAu data (we don't have TPC vertex in pptoftpx triggered data), you can find the distribution from the attached plot. It shows that with more VPD hit requirement, the vertex resolution is better. No 25cm-width gaussian contribution appears.

So  let me answer your questions directly, see them inline.
Akio Ogawa wrote:
Hello

I posted this yesterday to vertex mailing list. I'd like to make
sure you know this since you may be more intersted than us.

In zVPD-zTPC distribution at pp, we see 3 structures. See Fig 2 (2 gaussian fit) and Fig6 (3 gaussian fit) of
http://drupal.star.bnl.gov/STAR/blog-entry/rjreed/2008/sep/11/ppv-revision-1-29-high-luminosity-fmsslow-trigger-evaluation 

First is sigma ~3cm peak where TPC and VPD vertex matches. Quite
reasonable with resolutions of those two vertex finding.

2nd is sigma ~80cm, which is understandable if TPC and VPD picked
up 2 different vertex. Vertex distribution is ~gaussian with sigma
~60cm. If we pick 2 randomly and take difference, then sigma should be sqrt(2)*60cm ~ 85cm.

3rd one is the mistery. Sigma is around 25-30cm. So its much
narrower than random. Its hard for TPC to "miss" vertex by
10-20cm, since all track's DCA_z is <3cm.

Rosi changed selection of TPC vertex (more matched tracks) to
make TPC vertex better, she saw no difference in the structure.

Now if look at the plot at bottom of http://www.star.bnl.gov/protected/spin/akio/200806/index_8th.html

which is essentially same plot but divided by # of VPD hits.
This 3rd structure with sigma~25cm is most evident when both VPD-E
and VPD-W has 2 or more hits.

This suggests (at least to me) that when you have more than one hit
in VPD and taking time average, sometimes you are diluting VPD vertex resolution. This can be "real" (another collisions in the same crossing
or some beam halo hitting VPD) or detector effects (hot pmt, too
loose timing cut, etc).

Have you seen this?
==>Xin
No.
Is there way to get some more info from mudst?
==>Xin
The number of hits and Tdiff information should be available from MuDst. Tdiff cut may help some in resolution, but shouldn't create a 20cm gaussian peak.
(For example distance or rms of hits included in average?)
==>Xin
I don't quite understand, distance or rms of hits to what?
Is there some cut you tuned when you accepting hit to form average?
==> Xin
Yes. We have already removed the hits with non-physical timing information (out of trigger timing window, but for sure with 25ns resolution). And we always take the earliest hit.
(for exapmple maximum time difference?)
Is average weighted by ToT?
==> Xin
No. Supposedly the ToT dependence is calibrated. We just do simple average.
Have you tried taking earliest hit only?
==> Xin
Yes.

We will trying to see what the pp data look like. Thanks

/xin

 

Plots Jan

 plots