Determine time spent in solver for CPLEX#636
Open
danielelerede-oet wants to merge 3 commits intoPyPSA:masterfrom
Open
Determine time spent in solver for CPLEX#636danielelerede-oet wants to merge 3 commits intoPyPSA:masterfrom
danielelerede-oet wants to merge 3 commits intoPyPSA:masterfrom
Conversation
This file contains hidden or 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
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.
Changes proposed in this Pull Request
When calling CPLEX through linopy, the returned
Resultobject contained only:statussolutionsolver_model = m(the rawcplex.Cplexobject)but it did NOT include the solver runtime.
This creates of course an issue for benchmarking cplex as we cannot reliably access the solve time from linopy, and of course the profiler misses it completely
Other solvers in Linopy already expose structured metrics:
Knitroreturns a KnitroResult with runtime + gaps + errorsHiGHSruntime accessible via solver infoGurobi / Xpresscan access runtime from APISo I'm proposing here to add a lightweight wrapper, similar to Knitro:
CplexResult = namedtuple("CplexResult", ["model", "reported_runtime"])and modify the solve steps accordingly.
Checklist
doc.doc/release_notes.rstof the upcoming release is included.