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

Allow the specification of different search strategies #11

Open
hadronzoo opened this issue Nov 10, 2015 · 3 comments
Open

Allow the specification of different search strategies #11

hadronzoo opened this issue Nov 10, 2015 · 3 comments

Comments

@hadronzoo
Copy link

Rather than always defaulting to minDom_LB, would it be possible to specify other strategies?

@aengelberg
Copy link
Owner

Other strategies are on the radar. Thanks for submitting.

On Monday, November 9, 2015, Joshua Griffith [email protected]
wrote:

Rather than always defaulting to minDom_LB, would it be possible to
specify other strategies?


Reply to this email directly or view it on GitHub
#11.

@tanders
Copy link

tanders commented Apr 1, 2016

Choco also allows users to define their own search strategy (variable and value ordering, http://choco-solver.org/user_guide/4_advanced.html#defining-its-own-search-strategy). For complex CSPs a good custom strategy can greatly speed up the search process, or help to find a better first solution.

Thanks!

Torsten

@aengelberg
Copy link
Owner

Exposing custom strategies through a Clojure interface would be tough, especially while keeping the Choco solve performant. A strategy is basically a function that takes an array of variables and returns a variable. It would be confusing for the Loco user to declare constraints with keyword variables and then have to manipulate Choco variable objects at solve-time. I'll have to give it more thought.

I'm definitely going to add in the existing Choco built-in strategies when I get the chance (and it's low-hanging fruit for anyone who wants to contribute).

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 a pull request may close this issue.

3 participants