Stv: performance of iterations


Jason pointed out to me that for each event, Stv currently prints out the number of seeds and subsequently tracks found at each iteration. I put these into an ntuple and made some plots. My conclusions follow the plots. All plots show the iterations in colors 1,2,3,4, and have what I call the iterations' "performance" on the vertical axis (ordinate), which is defined as the fraction of seeds in that iteration which become tracks. The goal here is to understand whether performance is a better tool to decide when to stop iterating rather than simply stopping after iteration 2.

How it was done:

To explain the definitions, for each event is printed out lines like this:
StvMaker:INFO - StvKalmanTrackFinder::FindTracks: : SeedFinder(Default) Seeds=s1 Tracks=t1 ratio=xx%
StvMaker:INFO - StvKalmanTrackFinder::FindTracks: : SeedFinder(Default) Seeds=s2 Tracks=t2 ratio=yy%

I have kept s1..6 and t1..6 for each event. The performance of an iteration i is then simply (ti/si), and the ordinate of the plots is always log10(ti/si). Scripts used to generate the plots (StvIterations_*) are attached to this drupal page.


Run 9 pp500 st_W Run 9 pp500 W embedding Run 10 AuAu Ideal MC Definition of abscissa
t1 + ...
log10([ti+1 + ...]/[t1 + ...])

where i is the iteration examined,
such that for iteration 2
the quantity plotted is:

log10([t3 + ...]/[t1 + ...])
si+1 + ...
log10([si+1 + ...]\[s1 + ...])
log10([ti+1 + ...]/[si+1 + ...])

  1. The more tracks there are to find, the less performant iteration 1 will be.
  2. For AuAu200 events in which iteration 2 is performant (converts >10% of seeds into tracks), there are very few total tracks.
  3. Less than 1% of tracks (in nearly all events) are found after iteration 2.
  4. There is no notable correlation between fraction of unfound tracks and the performance of iteration 2.
  5. Using seeds as a proxy for time spent (correlated, but perhaps a poor proxy anyhow), then stopping after a poorly performing iteration saves more time (or a larger fraction of the event's time) at each iteration.
  6. Each iteration's performance has only a mild correlation with performance or remaining iterations.