-
Notifications
You must be signed in to change notification settings - Fork 19
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
Use z3 to get feasible points #33
Merged
Merged
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
Looking good. One thing throughout -- no print() statements should be left anywhere. Use the global info, err, debug, warn instead. In debug, it's always nice to give the object as an argument (e.g., debug("msg",obj=self)). For info/warn/err, follow the style of other such messages. |
ok, I will fix this |
There should not be any |
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.
Most of the work is done in z3_search.py, which is imported in search.py. The class (Z3search) is instanciated in order to use the solver from search.py.
The two search classes (simplex and randomsimple) show how to use it. In particular, when a point has been visited, it can be removed from the available parameter space (see in randomsimple.py). Another interesting feature is that we can still request particular points (centroid, reflection...) but then, we obtain the nearest feasible point.
Sorry about the conflict. You will see that it is trivial to solve.