Skip to content
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

fix track cluster remover template definition #6595

Conversation

mtosi
Copy link
Contributor

@mtosi mtosi commented Nov 25, 2014

in the migration from HLTTrackClusterRemover to TrackClusterRemover
I realized that in confDB we do not have the TrackClusterRemover template :(

it turned out to be due to the fact that no cfi is available for this module
moreover, this module is used by explicitly defining it in all tracking cff files !

=> this PR is meant for

  1. add trackClusterRemover_cfi.py file
    w/ default parameters which should be in as general as possible
  2. fix the handling of the input parameters w/in TrackClusterRemover
  3. update all (?) python configuration where there is an explicit definition of the TrackClusterRemover module,
    in order to instead import-and-clone the default template

this PR is needed for then letting the HLT config being migrated to use TrackClusterRemover (which is multithread safe), instead of HLTTrackClusterRemover which should not be maintained anymore ...

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @mtosi (mia tosi) for CMSSW_7_3_X.

fix track cluster remover template definition

It involves the following packages:

RecoLocalTracker/SubCollectionProducers
RecoParticleFlow/PFTracking
RecoTracker/ConversionSeedGenerators
RecoTracker/IterativeTracking

@cmsbuild, @nclopezo, @StoyanStoynev, @slava77 can you please review it and eventually sign? Thanks.
@ghellwig, @appeltel, @mmarionncern, @makortel, @forthommel, @yduhm, @GiacomoSguazzoni, @gbenelli, @rovere, @lgray, @nickmccoll, @jlagram, @gpetruc, @cerati, @VinInn, @threus, @dgulhan, @bachtis, @venturia this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
@nclopezo you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@perrotta
Copy link
Contributor

@mtosi : did you provide a 74X copy of this PR?
Could you please do so, if not?

@slava77
Copy link
Contributor

slava77 commented Nov 26, 2014

Hi Andrea, if HLT proposes #6618 as a combined PR, maybe you could stick to a single one?

@@ -1,18 +1,21 @@
### who is using this python file ?
### I found it obsolete, at least in terms of the TrackClusterRemover setting
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@VinInn @rovere @cerati
Please take note of these comments and possibly clean up in not so distant future. (not this PR)
Thank you.

@slava77
Copy link
Contributor

slava77 commented Nov 28, 2014

+1

for #6595 b17cb4d

tested as a part of #6618 (using 730pre3 as a baseline, in test area sign468
no differences in RECO outputs based on monitored quantities.
(while the #6681 is stuck a bit on unrelated subject, this should keep moving along)

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_3_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar

@davidlange6
Copy link
Contributor

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants