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

Decision for this explicit Pattern Search implementation #122

Open
Leschoep opened this issue Sep 26, 2018 · 1 comment
Open

Decision for this explicit Pattern Search implementation #122

Leschoep opened this issue Sep 26, 2018 · 1 comment

Comments

@Leschoep
Copy link

Hello all,

I am working on an implementation of Pattern Search for an auto-tuning-framework based on the pattern search algorithm of Hooke and Jeeves. By looking at the results I get with my implementation and comparing them with the ones from OpenTuner Pattern Search, I recognized that the results from OpenTuner are not as good as the ones one I got with the added pattern step, especially in big search spaces. I guess that's because the algorithm is trapped in local minima, not able to get out again to continue exploring, but I don't really know.

So I was wondering, why did you decide to go for this specific version of Pattern Search? Is there a specific reason?

Greets!

@jansel
Copy link
Owner

jansel commented Oct 20, 2018

The included pattern search is primarily a baseline and in most of our testing is worse than the other available techniques. Pull requests to improve it are welcome.

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

No branches or pull requests

2 participants