-
Notifications
You must be signed in to change notification settings - Fork 99
Fix parameter ordering/naming for reference (omp) batch CG #1701
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
Conversation
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.
LGTM.
one question might to @pratikvn : is there any reason that the device side follows the another algorithm more?
I think we re-arranged it so that the convergence check is first. But I dont see a particular reason for that. I will maybe compare the performance for both and maybe unify the device side to the reference one as well. |
7f77522
to
30c2d86
Compare
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1701 +/- ##
===========================================
+ Coverage 90.24% 92.05% +1.81%
===========================================
Files 764 764
Lines 62927 62678 -249
===========================================
+ Hits 56787 57701 +914
+ Misses 6140 4977 -1163 ☔ View full report in Codecov by Sentry. |
This merge fixes the parameter ordering of the `initialize` function for the reference+omp implementation of the batch CG. Additionally, a parameter name in `update_x_and_r` is changed to better reflect the actually used variable. Related PR: ginkgo-project#1701
This PR fixes the parameter ordering of the
initialize
function for the reference+omp implementation of the batch CG. Additionally, a parameter name inupdate_x_and_r
is changed to better reflect the actually used variable.