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 phi windows computation #12882
Fix phi windows computation #12882
Conversation
A new Pull Request was created by @VinInn (Vincenzo Innocente) for CMSSW_8_0_X. It involves the following packages: DataFormats/Math @cmsbuild, @cvuosalo, @davidlange6, @slava77 can you please review it and eventually sign? Thanks. Following commands in first line of a comment are recognized
|
@cmsbuild, please test |
The tests are being triggered in jenkins. |
@VinInn does this solves the issue with infinite loop due to NaNs in 10039.0 TTbar_14TeV on GCC 5.3.0? |
@davidlt , should, how many events were needed to trigger the infinite loop? (or is enough 10039.0 out of the box?) |
out-of-the-box is enough and it hangs on 7th event (quite fast after launching the workflow) |
|
@@ -43,6 +43,9 @@ namespace tkDetUtil { | |||
auto sp = (x0*x1+y0*y1)/std::sqrt((x0*x0+y0*y0)*(x1*x1+y1*y1)); | |||
sp = std::min(std::max(sp,-1.f),1.f); | |||
dphi = std::acos(sp); | |||
|
|||
// if (dphi>0.5*M_PI) std::cout << "large dphi " << dphi << ' ' << ts.localDirection() << ' ' << ts.globalMomentum().perp() << ' ' << maxDistance << 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.
is this important to have here?
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.
nope. was planning to add a max-dphi limit: we need conversion to be under control first though.
Will remove
Hardwired default moved to max-float. took the opportunity to fix a logic error unveiled by gcc530 in DQM |
@@ -408,7 +408,7 @@ void HitEff::analyze(const edm::Event& e, const edm::EventSetup& es){ | |||
const TrajectoryStateOnSurface tsosTEC9 = itm->updatedState(); | |||
|
|||
// check if track on positive or negative z | |||
if (!iidd == StripSubdetector::TEC) cout << "there is a problem with TEC 9 extrapolation" << endl; | |||
if (!(iidd == StripSubdetector::TEC)) cout << "there is a problem with TEC 9 extrapolation" << 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.
this appears to be the only "bare" cout (not protected by DEBUG).
The bug disabled it.
If it should stay exposed for default processing, it has to be converted to LogWarning/LogInfo.
Otherwise, please add "& DEBUG"
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.
is not under my direct responsibility...
I will protect with DEBUG...
@cmsbuild, please test |
The tests are being triggered in jenkins. |
+1
|
Fix phi windows computation
This PR is a continuation of my two last ones.
took the opportunity for some minor cleanup
A Major cleanup and refactoring of the three major seeding routines is badly needed.
(may occur in time for 8_0_0 if resources available)
Minor regression, timing improvement observed
MTV for the usual 1000 ttbar events PU35 at
http://innocent.home.cern.ch/innocent/RelVal/pu35_80_Xwin21/
(compared to current IB)