Allow exiting the anneal early via .min_energy #49
Conversation
This file contains 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.
Hey!
Thank you for this very nice library. While simulated annealing is not really that difficult to write from scratch, this library has a very nice abstraction, nice visualization, and the auto() searching for parameters is extremely handy.
I have now used this library a couple of times to generate pretty complex timetables, and it has worked great. What I do find a bit frustrating is that sometimes I know that my problem has an optimal solution and I know what it is, but I have no automatic way of letting the algorithm know that, so it keeps searching even after already finding that solution.
This PR adds a
.min_energymember allowing the user to specify an energy that is acceptable, letting theanneal()exit early.