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
vavilov parameters kappa fix #29399
vavilov parameters kappa fix #29399
Conversation
…en float and double
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29399/14542
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
this should be addressed before full PR tests can start |
The code-checks are being triggered in jenkins. |
Oops sorry I forgot to run the code format before pushing. Should be ok now |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29399/14545
|
A new Pull Request was created by @OzAmram (Oz Amram) for master. It involves the following packages: CondFormats/SiPixelTransient @ggovi, @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test workflow 13034.0 |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Ok I just pushed a new commit |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29399/14661
|
please test |
The tests are being triggered in jenkins. |
Still not clear to me why you do not apply the boundary limitation at L4067 to the returned This is indoubtly a ultra-minor point: once tests succeed this PR will be considered ready to be merged by reco. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1
|
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
A small PR to fix the issue reported here. The issue was caused by rounding differences between float and doubles. Namely that the value of kappa when on the edge of its allowed range as a float (0.01f) was less than the double value (0.01) used to check for errors. This fix simply adds a small amount to Kappa if it is exactly on the edge.
Tested by following the procedure outlined here and checking that this does indeed fix the error.