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

Debug info on local search operators #658

Closed
jcoupey opened this issue Jan 25, 2022 · 1 comment · Fixed by #659
Closed

Debug info on local search operators #658

jcoupey opened this issue Jan 25, 2022 · 1 comment · Fixed by #659

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Jan 25, 2022

For development/debugging, it would be useful to compute some stats on local search operators. Typically how many moves of each type are tested and how many are applied (maybe with associated gain). I don't think we have a sound way to decide how many of the tried moves are actually valid because most of them are usually discarded without even checking validity, based on the potential gain (or a lower bound of the gain).

@jcoupey
Copy link
Collaborator Author

jcoupey commented Jan 25, 2022

At first I though about simply using static members for all operator classes for counts, but that won't work because of concurrency (else we'd have to wrap the updates around locks which is a no-go).

Probably the best way is to have each LocalSearch instance keep track of what is going on during its own run. The upside is that we can then have per-search stats.

@jcoupey jcoupey added this to the v1.12.0 milestone Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant