Postprocess after finishing LS about euro-neurips-2022 HOT 3 CLOSED

@LuukPentinga as an idea: at the end of LocalSearch::search you could insert a call to say a method LocalSearch::postProcess();. That thing can then iterate over the routes (and nodes in them) to fix these subpaths. I think that would be a nice way to structure this.

from euro-neurips-2022.

I'm re-opening this while I test following ideas:

• Do this postprocessing only when we have a new best solution;
• Do this only after finishing the algorithm, just the before returning the best solution.

I want to try these variations because postprocessing as we do it now is fairly slow if we scale it up to larger subpath lengths. Those larger lengths are where the value is at, however, so we need to find a balance here, by e.g. doing postprocessing only in a few specific cases.

from euro-neurips-2022.

Do this postprocessing only when we have a new best solution;

This slightly edges out what we're currently doing, particularly with larger k = 6 (instead of 4).

from euro-neurips-2022.