The optimisation module has two purposes: to run an optimisation study where gs2
dynamically reconfigured and the timing for each configuration is returned, and to dynamically optimise gs2
before the start of the simulation.
As of Sep 2015 the mechanism for doing this is essentially complete. What is missing is a clever algorithm to take a path to the optimal configuration. Essentially at the moment the only optimisation algorithm choice is to run through and measure almost every possible configuration (which takes a very long time).
As of the creation of the 7.0 release candidate, I still haven't created a decent optimisation search algorithm. Therefore I am bumping a milestone of this feature to 7.1