New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow TrackClusterRemover to work on either pixel or strip clusters alone (92X backport) #19544
Allow TrackClusterRemover to work on either pixel or strip clusters alone (92X backport) #19544
Conversation
Conflicts: DQM/CTPPS/python/ctppsDQM_cff.py DQM/CTPPS/test/diamond_dqm_test_cfg.py
…ng92X Exo trigger prompt monitoring92 x
…nge-0-93X IOV range returned ordered by since
…on90X ECAL PFCluster Correction 9X
A new Pull Request was created by @JanFSchulte (Jan-Frederik Schulte) for CMSSW_9_2_X. It involves the following packages: Alignment/OfflineValidation @ghellwig, @perrozzi, @ianna, @kpedro88, @fabozzi, @Martin-Grunewald, @mommsen, @vanbesien, @govoni, @perrotta, @civanch, @monttj, @silviodonato, @cmsbuild, @fwyzard, @GurpreetSinghChahal, @davidlange6, @smuzaffar, @Dr15Jones, @kkousour, @mdhildreth, @cerminar, @slava77, @ggovi, @mulhearn, @efeyazgan, @vazzolini, @rekovic, @kmaeshima, @arunhep, @emeschi, @thuer, @dmitrijus, @alja, @franzoni, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Right now, the TrackClusterRemover uses both pixel and strip clusters at all times. This PR introduces the possibility to have it run on either of them alone. Backport of PR #19543