-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Improvements in track quality criteria in PF for muon seeded iterations (76X) #11434
Conversation
<< std::endl; | ||
if (_debug) std::cout << " cut is DPt/Pt < " << _DPtovPtCut[Algo] * sigmaHad << std::endl; | ||
if (_debug) std::cout << " cut is NHit >= " << _NHitCut[Algo] << std::endl; | ||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please cleanup commented out parts ... if needed keep behind LogTrace or LogDebug (preferred)
A new Pull Request was created by @bachtis (Michalis Bachtis) for CMSSW_7_6_X. Improvements in track quality criteria in PF for muon seeded iterations (76X) It involves the following packages: RecoParticleFlow/PFProducer @cmsbuild, @cvuosalo, @slava77 can you please review it and eventually sign? Thanks. |
#include "DataFormats/MuonReco/interface/Muon.h" | ||
#include "RecoParticleFlow/PFProducer/interface/PFMuonAlgo.h" | ||
|
||
class ImprovedTracksImporter : public BlockElementImporterBase { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Improved" is generally not a good name
What will happen to the next developments? "ImprovedImproved"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clearly, "BetterImproved", followed by "UpgradedBetterImproved"...
@bachtis Not possible to extend the existing general tracks importer? (to avoid these codes from diverging over time?) |
@bachtis I read your description, that says it is inconvenient rather than impossible, which is why I made the comment. It is not good to have two sets of code that do mostly the same thing. Since it is going to 75X there is likely time to reparse the HLT configs. However, if time is pressing. This can be taken care of in another PR. @slava77 @Martin-Grunewald comments? |
Also, what about GeneralTracksImporterV2? Much less wordy and has the benefit of not needing a countably infinite list of adjectives. |
Well if @Martin-Grunewald agrees with reparsing we can replace the old one. The matrix tests will crash at HLT if this is not done though . |
@bachtis Make a customization function named customizeFor_(PRNumber) and stick it in HLTrigger/Configuration. There are a few examples in there. This will allow matrix tests to run. |
OK then lets see if it is OK to change the hltParticleFlowBlock module.and then decide how to proceed |
the hlt is supporting changes to 75x via customize functions. Should be easy
|
so can somebody tell me what exactly I have to do- which files to change? In that case I would prefer to modify the old importer instead of adding new one |
If you'd use a fillDescriptions method, you can add all the parameters you want, |
@davidlange6 |
An even better solution. On Sep 23, 2015, at 5:26 PM, Martin Grunewald <[email protected]mailto:[email protected]> wrote: @davidlange6https://github.com/davidlange6 — |
The python change for this happens in some PSet inside of a VPSet. Is there a way to do fillDescriptions for an individual plugin in a list? |
HI . I am running the matrix. In fact since HLT iterations are different it might work out of the box . |
In fact no intervention is needed in HLT config . Implemented code review comments. PR should be updated now |
Yes one can have a fillDescription state the properties of PSets within a VPSet. |
@@ -33,6 +38,9 @@ class GeneralTracksImporter : public BlockElementImporterBase { | |||
const std::vector<double> _DPtovPtCut; | |||
const std::vector<unsigned> _NHitCut; | |||
const bool _useIterTracking,_cleanBadConvBrems,_debug; | |||
|
|||
PFMuonAlgo *pfmu_; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unique_ptr indeed, please.
@cmsbuild please test |
@slava77 already asked for test.. |
I'm running higher stat tests to see the effects. |
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_6_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
+1 |
Improvements in track quality criteria in PF for muon seeded iterations (76X)
@bachtis Does the migration observed in wf1313 have any sizeable impact on the resolution of high pT jets? |
@bachtis Just asking since there are no plots on the PR... |
Should not have any impact . If you have a ~TeV track that will be killed the calorimeter should measure it better . Only one event changed in the Flat QCD sample I rerecoed so I dont expect any effect |
I could rerun on more events. There wasn't much to see with 22 events
|
@lgray I don't think 1K events will be enough (4K maybe). First is to show that tracks go away on the high end of chFrac (this is a more clear "thing are in the right direction" plot) And the reco/gen plot for high et jets: it's not very convincingly mildly better |
See #11433