Skip to content
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

Refine storage of subsolver states #403

Closed
kellertuer opened this issue Jul 30, 2024 · 2 comments · Fixed by #399
Closed

Refine storage of subsolver states #403

kellertuer opened this issue Jul 30, 2024 · 2 comments · Fixed by #399

Comments

@kellertuer
Copy link
Member

See #399 (comment),
we could store the evaluation mode of a closed form solution also in a small state to make the type of sub_state more unified.
The keyword should still accept just the evaluation type.

This sounds like an easy refactor task.

@mateuszbaran
Copy link
Member

By the way, do you have an example of where a closed-form subsolver is used?

@kellertuer
Copy link
Member Author

Frank-Wolfe often, Difference-of-Convex, maybe ALM sometimes?

In general it might also be nice to pass a “closed form solution” function to use some other packages solver as a subsolver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants