-
Notifications
You must be signed in to change notification settings - Fork 14
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
Public algorithm interface renaming using snake_case #942
Conversation
cscs-ci run |
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.
I'm happy with the renaming. I just want to highlight that if we're renaming them there may be room for other changes:
- I see
backTransformation
was shortened tobt
. I'm fine with this. However, doesback_transformation
orbacktransformation
hurt? gen_to_std
vsgeneralized_to_standard
tridiag_solver
vstridiagonal_solver
vstridiagonal
(the triangular solver is calleddlaf::solver::triangular
, the tridiagonal solverdlaf::eigensolver::tridiag_solver
; why does the latter havesolver
twice in the name? same fordlaf::eigensolver::eigensolver
vsdlaf::eigensolver::<something that doesn't repeat eigensolver>
)- if we go for abbreviations why not
red_to_band
?
As said above, I don't want to cause further work on this if you're happy with the current names. I just want to make sure that the options were considered and:
- alternatives were dismissed as worse, or
- the current possible inconsistencies accepted (for a possible future further renaming)
The naming was chosen to match the filename. It is not perfect as you said, but it is a good starting point.
I'm not much happy with the namespace/algorithm names as well, but I didn't find any good solution yet.
Any idea is welcomed to be discussed. |
33a6880
to
5652388
Compare
cscs-ci run |
Notes:
|
@@ -70,13 +70,13 @@ void eigensolver(blas::Uplo uplo, Matrix<T, D>& mat, Matrix<BaseType<T>, D>& eig | |||
/// @param uplo specifies if upper or lower triangular part of @p mat will be referenced | |||
/// @param mat contains the Hermitian matrix A | |||
template <Backend B, Device D, class T> | |||
EigensolverResult<T, D> eigensolver(blas::Uplo uplo, Matrix<T, D>& mat) { | |||
EigensolverResult<T, D> hermitian_eigensolver(blas::Uplo uplo, Matrix<T, D>& mat) { |
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.
Just want to check, is the name EigensolverResult
still accurate?
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.
Leaving this out for now, but @rasolca we probably need your input on what you'd like to do here leter.
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.
No comments in addition to those made by @RMeli.
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.
No extra comment from my side.
Since #886 has been merged first, the internals of the C/ScaLAPACK API will need to be updated here. @albestro, I can open a PR against your branch if you prefer, but it should be a matter of changing two calls: DLA-Future/src/c_api/eigensolver/eigensolver.h Lines 62 to 63 in bcc77db
DLA-Future/src/c_api/factorization/cholesky.h Lines 49 to 50 in bcc77db
|
moved to internal without renaming because it has to be changed before making it public
c8e9b41
to
e929470
Compare
cscs-ci run |
I'm not sure this PR fully address the original intentions of #940. We can go for merging this and later re-open it or create more specific issues (e.g. renaming of internals too) |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## master #942 +/- ##
==========================================
+ Coverage 93.37% 93.44% +0.06%
==========================================
Files 143 143
Lines 8654 8650 -4
Branches 1104 1103 -1
==========================================
+ Hits 8081 8083 +2
+ Misses 388 383 -5
+ Partials 185 184 -1
|
Close #940
As per discussion in https://confluence.cscs.ch/display/SCISWDEV/2023-07-20+algorithm+renaming+discussion
Decisions:
dlaf::
namespacedlaf::eigensolver::internal::Eigensolver
)TODO: