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
Hip mitigation #15114
Hip mitigation #15114
Conversation
A new Pull Request was created by @VinInn (Vincenzo Innocente) for CMSSW_8_1_X. It involves the following packages: RecoTracker/MeasurementDet @cmsbuild, @cvuosalo, @slava77, @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. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
-1 Tested at: d5168db You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals
When I ran the RelVals I found an error in the following worklfows: DAS Error140.53 step1 DAS Error |
GSF tracking parameters had never been tuned maybe EGamma POG should have a look and not just set all cuts to ~inf : at some point junk kicks in and efficiency is lost... |
@rafaellopesdesa @fcouderc |
On 7/6/16 11:57 PM, Vincenzo Innocente wrote:
I missed this.
|
In any case "somebody" has to decide
|
Here are some technical numbers, based on 276092 JetHT There is about 1s/event increase (about 5% of total CPU).
The event sizes go up and down per product. The net change is about 1%, mainly coming from generalTracks. Changes in the reco file:
|
+1
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
Thanks Slava for these tests: you are indeed the first to try this new HIP simulation/mitigation chain! |
@VinInn is it possible to make a 80X backport to possibly have a dedicated 80X patch release to do a selected rereco of some runs/PDs ? |
why in 80X? btw we then need also a backport of HIP Simulation... |
it would make easy to compare w/ prompt reco and faster to prepare the campaign given that GT is already there |
On 7/12/16 8:27 AM, arizzi wrote:
If this can be made configurable for 80X (or even 81X), off by default
\ |
a straight backport is trivial (a few line patch) |
On 7/12/16 9:06 AM, Vincenzo Innocente wrote:
It should be possible to do all the tests and comparisons in 81X, The development of things appears to go in the direction of having the
|
So, what shall we do?
btw keep in mind that we still hope to be able to identify affected APVs from data themselves and make the mitigation more local @venturia fyi as well |
On 7/12/16 9:53 AM, Vincenzo Innocente wrote:
No, only when it's configurable.
What is the time scale for this?
|
the new parameter will make the pair with this for instance http://cmslxr.fnal.gov/dxr/CMSSW_8_0_5/search?q=MaxSagitta&case=true what what concern APV identification: no-ETA |
+1 |
On 7/12/16 10:34 AM, Vincenzo Innocente wrote:
I may be misunderstanding the term "neutralize". At this point I was just thinking of a global on/off switch for the Your comments point to further improvements that would run differently
|
HIP Mitigation as extensively presented and discussed.
See for instance:
https://indico.cern.ch/event/539401/contributions/2207119/attachments/1296862/1934523/HipMitigation3.pdf