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

Use z3 to get feasible points #33

Merged
merged 15 commits into from
Dec 27, 2020
Merged

Use z3 to get feasible points #33

merged 15 commits into from
Dec 27, 2020

Conversation

coti
Copy link
Collaborator

@coti coti commented Dec 24, 2020

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.

@brnorris03
Copy link
Owner

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.

@coti
Copy link
Collaborator Author

coti commented Dec 24, 2020

ok, I will fix this

@coti
Copy link
Collaborator Author

coti commented Dec 24, 2020

There should not be any print left...

@brnorris03 brnorris03 merged commit 52f7448 into brnorris03:master Dec 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants