Comparison of the new L3 tracking with the one used in the Tk muon reco ON-GOING

Timeline → end of the year (TSG) 21 Dec 2016

Optimize the new L3 reconstruction: ON-GOING

IO algorithm – ROI DONE

OI algorithm PENDING

More complete set of studies on performance comparisons using MuXX OR TkMuXX as a FOM, different signal samples should be tested in order to have all possible phase spaces covered: DY, ttbar, close-by-muon , displaced muons, low pT muon (from JPsi) PENDING

Revise/design a smarter the combination of the out-in and in-out sequence. PENDING

Ideas/prelim studies on the combination between new L3 and Tk muon reconstruction PENDING

Have already in place in CMSSW the new L3 sequence using current geometry. PENDING

Including the new module which runs the TkMu path if the New L3 does not reconstruct the muon successfully. PENDING

List of unused classes that could be removed from CMSSW when switching to the new L3. PENDING

Final deadline for having integrated in CMSSW, March 2017. 01 Mar 2017

Switch to new geometry and test everything still works. PENDING

Clean-up CMSSW by removing unused classes. PENDING

Task list for the next milestone: 01 Nov 2016

performance studies comparing new/old L3 using few signal samples:

efficiencies

timing

track quality measurements

ROI optimization

Look at events failing the HLT L3 reconstruction.

Design:

1) Seeding: One inside-out seeding algorithm using

For now we will use 1 seed collection. When we need to know if the seed was IO or OI we can just ask for its direction. We need to think about how the ROI will be created for the seed finding.

The OI algorithm will be a combination of state based and hit based. For OI state based the errors are rescaled, including alignment. For OI hit based we need to consider how many layers should be used, especially in the overlap region.

For the IO hit based algorithm we will reuse all the current tracking code. We need to consider how the window size will be created and whether we use the error matrix when calculating the size.

2) Regional (track) reconstruction

3) Matching

4) Final fit and parameter assignment

5) Filter

In New Design 1 for the production part there are 2 modules (EDProducers). The first produces a collection of L3 Tracks given a L2 muon track collection. The second produces L3 Muon track links collection are matching a L3 track with the L2 track. The following diagram describes the process:

Compared to the current design, described below there are fewer calls to read/write from the event bus (described by the blue bar in these diagrams). One of the motivations to have this in 2 modules instead of one is to perform the check on whether a seed generation algorithm needs to be activated or not by checking the currently available L3 tracks.

Running the New Code

IO design and testing

Taking all the parameters from the tracker community. Already in the current HLT menu, as it is used for the HLT_TkMu50 path: