Previous results were for preco03.02 with overlap fix.
Release preco03.02 should be equivalent. Here we start with that release but use a newer version of gtr_find (v00-19-52) which fixes the problem with the overlap efficiency. I have requested this fix be included in the next build of preco03.
Here are results for single muons and Pythia Z -> mu mu with zero, one and two minbias background events. As usual these are for pT above 0.5 GeV/c.
run bg chk CPU mem swp tm pe pTt # mc eff misr fake fcsq mcsq nclu ---- -- ---- ---- --- --- -- -- --- ---- ---- ---- ---- ---- ---- ---- m50 0 401 1 0 1 0.5 1629 .937 .002 .009 18.4 5.5 17.0 m03 0 401 m01 0 401 pzmm 0 401 19 72 96 0 1 0.5 683 .770 .198 .038 20.4 15.0 13.1 pzmm 1 401 170 119 144 0 9 0.5 1892 .837 .394 .110 21.5 20.2 11.3 Note: There are some new columns: pe = # tracks dropped after finding due to propagation errors mem = max memory as reported by the framework swp = max swap as reported by the frameworkFor the Pythia events, here are results for tracks with pT above 10 GeV/c.
pzmm 0 401 10.0 154 .968 .027 .027 19.4 5.9 17.0 pzmm 1 401 10.0 160 .950 .092 .072 19.5 6.8 16.1Here are plots showing the found (top) and lost (bottom) tracks in the z0-tan(lambda) plane.
The figures include curves showing the subdetector boundaries. The central horizontal band is the CFT acceptance. The thin bands above and below are the overlap region. The regions above the top V and below the bottom V are the SMT forward acceptance. There are also regions in the upper left and lower right between the CFT overlap and the SMT forward which are not covered. These are the "gaps".
m50 pzmm + 0 bg low pT high pT pzmm + 1 bg low pT high pT
Here is the CPU time (sec/event) broken down by track-finding step as reported by the framework:
run bg cc co c cs f csf --- -- --- --- --- --- --- --- pzmm 0 1 4 1 1 11 0 pzmm 1 5 67 3 11 79 3 pzmmThere is a problem here that the times for the last entry do not add up to the total observed time. I suspect a problem in the framework.