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

Hot-start not implemented ? #49

Open
flomnes opened this issue Jul 18, 2022 · 1 comment
Open

Hot-start not implemented ? #49

flomnes opened this issue Jul 18, 2022 · 1 comment
Assignees
Labels

Comments

@flomnes
Copy link
Collaborator

flomnes commented Jul 18, 2022

Benchmarks indicate that hot-start is not properly implemented in the XPRESS interface.

@flomnes flomnes added the xpress label Jul 18, 2022
@flomnes flomnes self-assigned this Jul 18, 2022
@flomnes
Copy link
Collaborator Author

flomnes commented Jul 19, 2022

For the Sirius interface, this piece of code was commented out in method SiriusInterface::SetVariableBounds

//if (!supportIncrementalExtraction && !(slowUpdates & SlowSetVariableBounds)) {
//	InvalidateModelSynchronization();
//}
//else

Note that !supportIncrementalExtraction && !(slowUpdates & SlowSetVariableBounds) is always true.

Before that change, the hot-start was broken, after it worked fine. Internally, the default value for "keep basis" in Sirius is true.

The default value for XPRS_KEEPBASIS is 1, meaning "The previously loaded basis (last in memory) should be used."

I don't know if we want to delay extraction for variable bounds in XPRESS like we did in Sirius. It seems to me that XpressInterface::SetVariableBounds pretends to do that, but actually does nothing (bounds are lost forever), to be confirmed.

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

No branches or pull requests

1 participant