-
Notifications
You must be signed in to change notification settings - Fork 3
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
Refactor dual cone projections #237
Merged
Merged
+164
−94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
|
PierreQuinton
force-pushed
the
factorize_dual_cone_projections
branch
from
January 21, 2025 17:15
d9f60e3
to
5c15741
Compare
I really like the idea! I'll make a proper review and probably merge later this week. |
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Jan 30, 2025
ValerianRey
reviewed
Feb 1, 2025
PierreQuinton
commented
Feb 2, 2025
PierreQuinton
commented
Feb 3, 2025
… Proposition 1 instead of the dual of projection onto the dual cone.
I think a5f562a is worth a changelog entry, with a vague explanation of what was done and how it may affect results. For instance Changed
|
…annot infer any grad from our solve using qp_solvers.
ValerianRey
reviewed
Feb 4, 2025
- Change parameter order - Change variable names - Simplify operations - Rename functions - Improve documentation
- Always use G for the gramian - Always use u and U for a vector / tensor of weights prior to projection - Always use w and W for a vector / tensor of projection weights - Add underscore to disambiguate with numpy version when necessary
- I think it's better to not name self.weighting(matrix) as u, because it doesn't have the same role as a single u afterwards. Therefore, I removed this variable name.
|
ValerianRey
changed the title
Factorize dual cone projections
Refactor dual cone projections
Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Both
DualProj
andUPGrad
rely on projections onto the dual cone, this PR factorizes the computation of such projections into one utility in the aggregation package.