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
L2muon changes: L2MuonSeedGenerator, L2MuonProducer #1864
Conversation
A new Pull Request was created by @trocino (Daniele Trocino) for CMSSW_7_0_X. L2muon changes: L2MuonSeedGenerator, L2MuonProducer It involves the following packages: RecoMuon/L2MuonProducer @nclopezo, @cmsbuild, @anton-a, @thspeer, @slava77 can you please review it and eventually sign? Thanks. |
@perrotta @Martin-Grunewald Also, it's my understanding so far that there should be a set of parameters that keeps the performance roughly unchanged. This set will be used in the frozen menus. Slava |
Hi Slava, Daniele. |
Hi all, In hltL2MuonSeeds/L2MuonSeedGenerator: In hltL2Muons/L2MuonProducer: With these values (which are not default, they need be set this way), the performance is totally unaffected, the triggers will behave exactly as before. It is useful mostly to have the new parameters in release and in the HLT configuration, so that they can be tested by all the PAGs with different values. So probably it's not extremely important if it doesn't make it to pre11. Let me know if you need some more information. |
Hi, I see two new parameters, one is untracked with a default of "TRUE" - does that reproduce the old behaviour? Best regards Martin |
One other thing: it looks like the value of the new untracked boolean affects the physics outcome, hence it should NOT be untracked but tracked. And then please use the same strategy as for the second, tracked parameter described above. |
Hi Martin, |
Great, thanks a lot! |
Does not merge. Moving to pre12 / 71X. |
@trocino Nominally, this PR will go to 71X |
@perrotta @Martin-Grunewald |
+1 tested c6605eb CMSSW_7_0_X_2014-01-14-0200 (local test area sign295) Jenkins is still in "Comparison with the baseline Still running..." |
This pull request is fully signed and it will be integrated in one of the next IBs unless changes (tests are also fine). @ktf can you please take care of it? |
Hi Slava, I had changed something in the jenkins job and it was not triggering the comparison. Thanks for making me notice. I started it again by hand and you can now see the comparison. |
Hi David. Thank you. We should get back to include the reco fwlite script in the tests run by jenkins. validateJR.sh relDirNew relDirRef newVSref matrix_70X.txt
#newVSref specifies the name added to the output to mark where it's from
# matrix_70X.txt is manually made map file between short wflow names, input files and process names the script and map file are in https://github.com/slava77/cms-reco-tools |
This pull request is fully signed and it will be integrated in one of the next IBs unless changes (tests are also fine). @ktf can you please take care of it? |
@ktf |
Hi, For sure we want it in 70X. The list of PRs is added to yesterday's wiki: https://twiki.cern.ch/twiki/bin/view/CMS/OfflineComputingPlanningMeeting20140114 Best regards Martin On Wed, 15 Jan 2014, slava77 wrote:
Martin Martin W. Gruenewald e-mail: Martin.Grunewald@cern.ch |
HLT updates -- L2muon changes: L2MuonSeedGenerator, L2MuonProducer
Any chance that this PR is affecting relvals? https://hypernews.cern.ch/HyperNews/CMS/get/relval/2833/30.html |
Hi David. |
is there a thread you know of confirming that? This one just says it could be a problem…. On Feb 3, 2014, at 2:15 PM, perrotta notifications@github.com
|
I agree it is an issue and it has to be followed up. What I said is simply that it starts at L1 see also https://hypernews.cern.ch/HyperNews/CMS/get/trigger-performance/705/6.html and the plots linked therein, for instance Thus the culprit cannot be L2 muon code, and in particular cannot be davidlange6 notifications@github.com ha scritto:
This message was sent using IMP, the Internet Messaging Program. |
Thanks for the pointer… didn't see that thread (though I notice that L1 had signed off on pre12…) On Feb 3, 2014, at 2:33 PM, perrotta notifications@github.com wrote:
|
The new code in packages L2MuonSeedGenerator, L2MuonProducer introduces the following options in L2 muon reconstruction for muon triggers:
By default, the new code won't affect muon triggers: the new options can only be enabled with a proper configuration in ConfDB, if requested by the TSG.
The standard tests (runTheMatrix) were run successfully in CMSSW_7_0_X_2013-12-16-1400 and CMSSW_7_0_0_pre10. The report can be found here:
http://trocino.web.cern.ch/trocino/Temp/2013-12-17_runTheMatrix/runall-report-step123-.log
In order to run the tests, the new parameters must be added to the following HLT configurations
HLTrigger/Configuration/python/HLT_8E33v2_cff.py
HLTrigger/Configuration/python/HLT_8E33v2_Famos_cff.py
as shown here:
http://trocino.web.cern.ch/trocino/Temp/2013-12-17_runTheMatrix/HLT_8E33v2_cff.py
http://trocino.web.cern.ch/trocino/Temp/2013-12-17_runTheMatrix/HLT_8E33v2_Famos_cff.py