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

Backtracking during Restart #13

Open
ImkoMarijnissen opened this issue Jul 24, 2024 · 1 comment
Open

Backtracking during Restart #13

ImkoMarijnissen opened this issue Jul 24, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@ImkoMarijnissen
Copy link
Contributor

In the case of a restart, it could be beneficial to completely recalculate from scratch rather than to notify of the (potentially) numerous events.

This would require:

  • Determining when a restart loses "too much" information; we could use a heuristic based on how close the current state of the solver is to a solution
  • Having an interface for propagating from scratch for every propagator
  • Ensuring that the stored events are cleared properly
@ImkoMarijnissen ImkoMarijnissen added the enhancement New feature or request label Jul 24, 2024
@maartenflippo
Copy link
Contributor

Why do we not currently support this? We could say that when we are restarting, we don't notify on backtrack events. Then the synchronize will be called which should be implemented such that the propagator's state is correct wrt the current state.

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

No branches or pull requests

2 participants