Skip to content
This repository has been archived by the owner on Dec 7, 2022. It is now read-only.

Decouple local search operators #38

Closed
N-Wouda opened this issue Aug 2, 2022 · 1 comment · Fixed by #43
Closed

Decouple local search operators #38

N-Wouda opened this issue Aug 2, 2022 · 1 comment · Fixed by #43
Assignees
Labels
enhancement New feature or request

Comments

@N-Wouda
Copy link
Owner

N-Wouda commented Aug 2, 2022

Similar to #32 for the crossover operators: we should decouple the operators from the LocalSearch (LS) class to allow testing their added value. This is difficult, because the LS class is a bit of a beast. I attempted to clean this up before in #24, but that eventually did not work out. Another attempt might be more successful, however.

First, we need to determine a good signature for the local search operators. What must they minimally know about the current neighbourhood? What do they use currently? Can we pass that data in as arguments, and somehow get a (possibly improved) solution out?

@N-Wouda N-Wouda added the enhancement New feature or request label Aug 2, 2022
@N-Wouda
Copy link
Owner Author

N-Wouda commented Aug 2, 2022

@LiekevdHeide @LuukPentinga if you're looking for a useful thing to do (other than reviewing PR's!): this is quite important and decidedly non-trivial :-).

@N-Wouda N-Wouda self-assigned this Aug 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant