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

Restart for ALMOST_SOLVED integer solutions #132

Open
Wikunia opened this issue May 29, 2019 · 3 comments
Open

Restart for ALMOST_SOLVED integer solutions #132

Wikunia opened this issue May 29, 2019 · 3 comments
Labels

Comments

@Wikunia
Copy link
Member

Wikunia commented May 29, 2019

Currently if almost locally solved integer solutions aren't allowed but almost locally solved is one restart is done to maybe obtain a good solved integer solution.
This restart should probably be an option.

  • removing restarts
  • maybe try restart but if not better accept it nevertheless?
@ccoffrin
Copy link
Member

ccoffrin commented Mar 6, 2022

@Wikunia I was having a look at the current implementation of state_is_optimal and given that allow_almost is in there it made we wonder if this issue has been addressed or if there is something outstanding to investigate?

@Wikunia
Copy link
Member Author

Wikunia commented Mar 6, 2022

I think the question is whether we always allow "almost solved" or whether it makes sense to only allow "locally solved". If the latter one might want to run the problem with a different seed to obtain an actual "locally solved"

@ccoffrin
Copy link
Member

ccoffrin commented Mar 6, 2022

Got it. I will leave this as an open question as some investigation is needed to understand the possible impact.

My hunch is that almost solved models have numerical issues and the almost property will be stable across multiple solutions, but this should be verified.

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

2 participants