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

separate model and solver attributes #6

Closed
chriscoey opened this issue Jul 1, 2017 · 2 comments · Fixed by #7
Closed

separate model and solver attributes #6

chriscoey opened this issue Jul 1, 2017 · 2 comments · Fixed by #7

Comments

@chriscoey
Copy link
Contributor

chriscoey commented Jul 1, 2017

only 3 overlap, and they don't really make sense (per discussion with @mlubin). so separate these attributes.

also from discussion with @mlubin: define an interface for asking a solver whether a group of "types" of constraints is supported together. and also a way to ask the solver, given an existing model that has already been solved, what types of constraints can be added to it. EDIT moved to #8

there is confusion on my part on what a model is and what a solver is. I think perhaps the terminology could be revisited to make it clearer.

@chriscoey
Copy link
Contributor Author

chriscoey commented Jul 1, 2017

@mlubin suggested Instance or SolverInstance instead of Model. maybe Solver is fine as-is

@chriscoey
Copy link
Contributor Author

in #7, I renamed model to instance, and also separated instance and solver attributes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant