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

Performance Suggestion: "automatic" persistent solvers #1154

Closed
michaelbynum opened this issue Nov 5, 2019 · 2 comments
Closed

Performance Suggestion: "automatic" persistent solvers #1154

michaelbynum opened this issue Nov 5, 2019 · 2 comments

Comments

@michaelbynum
Copy link
Contributor

When re-solving the same model with minor changes, we may be able to "automatically" detect what changed and only update what needs updated.

@whart222
Copy link
Member

whart222 commented Nov 7, 2019

I've implemented ideas like these in COEK, so we have evidence that this is feasible. A key question is whether the time needed to do these checks in Pyomo will be fast enough to call this an optimization. We can check this with the use cases I've used with POEK and COEK.

@jsiirola
Copy link
Member

jsiirola commented May 8, 2020

Archived on the master Performance Proposals Issue (#1430). Closing this performance proposal until active development has begun.

@jsiirola jsiirola closed this as completed May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants