Made combined modules the default for both prompt and extended tracking.
(Also moved references to fitpattern.txt file out of Hybrid algo, where they are not needed. These references remain available to the pure Tracklet algo via "#ifndef USEHYBRID" statements in the C++ and via function trackletConfig() in Customize_cff.py).
(Also fixed compilation errors in the pure tracklet L1 track algo. But @aryd / @skinnari should note that this algo crashes when doing the track fit, because of a variable outside the allowed digi range. This problem has existed for some time. I'm unable to fix it).
Performance of PROMPT tracking on ttbar+200PU (for Pt > 2)
Non-combined modules:
efficiency = 95.04 +- 0.14%
tracks/event = 167.99
Combined modules:
efficiency = 94.27 +- 0.15%
tracks/event = 166.61
Performance of EXTENDED tracking on ttbar+200PU (for Pt > 2)
Non-combined modules:
efficiency = 96.55 +- 0.12%
tracks/event = 269.95
Combined modules:
efficiency = 96.55 +- 0.12%
tracks/event = 276.97
So there is a 0.8% efficiency loss (due to MP truncation) for PROMPT tracking, which is not present for EXTENDED tracking (probably because the latter is not a full emulation).
PR description:
Made combined modules the default for both prompt and extended tracking.
(Also moved references to fitpattern.txt file out of Hybrid algo, where they are not needed. These references remain available to the pure Tracklet algo via "#ifndef USEHYBRID" statements in the C++ and via function trackletConfig() in Customize_cff.py).
(Also fixed compilation errors in the pure tracklet L1 track algo. But @aryd / @skinnari should note that this algo crashes when doing the track fit, because of a variable outside the allowed digi range. This problem has existed for some time. I'm unable to fix it).
Performance of PROMPT tracking on ttbar+200PU (for Pt > 2)
Non-combined modules:
efficiency = 95.04 +- 0.14% tracks/event = 167.99
Combined modules:
efficiency = 94.27 +- 0.15% tracks/event = 166.61
Performance of EXTENDED tracking on ttbar+200PU (for Pt > 2)
Non-combined modules:
efficiency = 96.55 +- 0.12% tracks/event = 269.95
Combined modules:
efficiency = 96.55 +- 0.12% tracks/event = 276.97
So there is a 0.8% efficiency loss (due to MP truncation) for PROMPT tracking, which is not present for EXTENDED tracking (probably because the latter is not a full emulation).