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
Make Hip mitigation configurable #15194
Conversation
A new Pull Request was created by @VinInn (Vincenzo Innocente) for CMSSW_8_1_X. It involves the following packages: RecoTracker/CkfPattern @cvuosalo, @dmitrijus, @cmsbuild, @slava77, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
@cmsbuild , please test |
The tests are being triggered in jenkins. |
jenkins tests are being done in IB after #15114 is merged. So, the expectation is to have no changes. |
speaking of configurability: what is the python level spell to make MinPtForHitRecoveryInGluedDet become a very large number to disable the mitigation? |
@@ -14,7 +14,7 @@ | |||
Chi2MeasurementEstimatorForP5.nSigma = 4. | |||
Chi2MeasurementEstimatorForP5.MaxDisplacement = 100 | |||
Chi2MeasurementEstimatorForP5.MaxSagitta=-1 | |||
|
|||
Chi2MeasurementEstimatorForP5.MinPtForHitRecoveryInGluedDet=100000 |
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.
an example of python spell
http://cmslxr.fnal.gov/dxr/CMSSW_8_0_5/search?q=MaxSagitta&case=true
gives you an idea of all the places where such an explicit spell can be cast
test failed due to
|
@VinInn |
On 7/14/16 5:32 AM, Vincenzo Innocente wrote:
Maybe this can inspire the method would pick all chi2Estimators of a process and change their
|
and where you suggest such a customize to reside? |
-1 Tested at: 311d80d You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test testRecoMETMETProducers had ERRORS |
Looking at jenkins results, the comparisons look as expected now (conversions didn't change, only cosmics changes). |
return (module for module in process._Process__esproducers.values() if module._TypedParameterizable__type in types) | ||
def customizeMinPtForHitRecoveryInGluedDet(process,value): | ||
for esp in esproducers_by_type(process, "Chi2MeasurementEstimatorESProducer", "Chi2ChargeMeasurementEstimatorESProducer"): | ||
esp.MinPtForHitRecoveryInGluedDet = value |
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 change this to
esp.MinPtForHitRecoveryInGluedDet = cms.double(value)
so that this customization applies as is to HLT and possibly other PSets that were not derived from a clone.
If done, also add
import FWCore.ParameterSet.Config as cms
at the top
With these modifications the function can be tested with --customise RecoTracker/Configuration/customizeMinPtForHitRecoveryInGluedDet.customizeHitRecoveryInGluedDetOff
passed to the cmsDriver.py or runTheMatrix.py
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.
This is intentional.
we want to catch those who do not clone.
They HAVE to clone.
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.
For what concern HLT, my understanding is that as soon this PR will be integrated a new config will be created with the new parameter made explicit.
@mtosi, @Martin-Grunewald, @fwyzard to confirm
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.
I think the HLT policy for new PRs is to support the old/current menu.
So, missing required parameters should be inserted with a customization.
This is a bit special case, because we are discussing the customization function which is not a standard workflow.
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.
relval submission that calls this customization will be rather complicated, each workflow type will need to be handled manually (not all have HLT); although the majority has RECO in step3. So, should likely be OK.
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.
This customise if not modified will not work for fastsim: ~OK, probably.
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.
ok let's modified.
FastSim does not perform patternreco so any value is ok
Fix it so that it is added also in non-clones
Pull request #15194 was updated. @cvuosalo, @dmitrijus, @cmsbuild, @slava77, @vanbesien, @davidlange6 can you please check and sign again. |
@cmsbuild , please test |
The tests are being triggered in jenkins. |
-1 Tested at: 93dbb05 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test testRecoMETMETProducers had ERRORS |
+1 for #15194 93dbb05
|
+1 |
do we have the analogous for 80x ? |
The title say all.
in principle bitwise compatible with previous version...
but for cosmics