Hi Slava,

HLTMuonL1Filter is an HLTFilter while this L1MuonSelector module is an
EDProducer.

The L1 muon candidates are used to create tracking regions.  There's a
module CandidateSeededTrackingRegionsProducer which can take in a
collection of candidates to produce the tracking regions.  But to select a
subset of the L1 muon candidates to use for tracking regions, I needed to
either (1) produce a filtered collection of L1 muon candidates or (2)
modify the CandidateSeededTrackingRegionsProducer code to be aware of the
HLTFilter decisions.  I chose (1) because it seemed simpler.

As for the code location, this package was suggested by the muon HLT
conveners.  But I'm fine moving it wherever you think is appropriate.

Thanks,
Dominick


On Wed, Jun 4, 2014 at 12:01 AM, Slava Krutelyov <notifications@github.com>
wrote:

> In RecoMuon/TrackerSeedGenerator/plugins/L1MuonSelector.h:
>
> > @@ -0,0 +1,62 @@
> > +#ifndef RecoMuon_L1MuonSelector_L1MuonSelector_H
>
> Why is this in RecoMuon package?
> It reads a L1 trigger object and it writes an L1 trigger object collection.
>
> The functionality seems to be the same as in
> HLTrigger/Muon/src/HLTMuonL1Filter.cc
> Why not use that instead?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/cms-sw/cmssw/pull/4098/files#r13361802>.
>