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

Rework heuristic / exploration level logic #508

Closed
jcoupey opened this issue May 13, 2021 · 1 comment
Closed

Rework heuristic / exploration level logic #508

jcoupey opened this issue May 13, 2021 · 1 comment
Labels

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented May 13, 2021

The -x flag sets a trade-off between "exploration level" (hence computing time) and solution quality one can hope to reach. It actually acts on two different factors:

  1. Spawning more or less parallel searches (those run totally independently for now, and are based on various predefined heuristic tunings).
  2. Pushing each of the searches further by adding steps where we incrementally rework bigger parts of the solution in order to get out of a local search minima.

At the end of the day, only the search yielding the best solution is "used", so running 32 searches in parallel (-x 5) is somehow a waste of resources. We've been doing it this way so far because of course we don't know beforehand which of the heuristic tunings will lead to the best solution, and it works ™.

It would be interesting to explore how we could narrow down the number of searches during optimization, only keeping the most promising ones depending on the context.

My hopes here is to be able to reduce "unproductive" computing times, which could bring faster convergence, or an intensification of the search on more promising leads without increasing the overall computing effort.

@jcoupey
Copy link
Collaborator Author

jcoupey commented Sep 13, 2024

Closing as this is somehow stale. In particular deciding what searches to run based on heuristic solutions does not really seem to make sense: those contain arbitrary biases so the first local search descent does a random re-shuffling of which are the "best".

Also we have other more immediate leads for improvements, e.g. #874.

@jcoupey jcoupey closed this as completed Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant