Implement OptimizerRunner

[mkommend]

The OptimizerRunner should be an additional view to execute optimizers without showing them explicitly. It only needs start, pause, stop and prepare button to handle the execution. Additionally it would be very nice to be able to specify how many optimizers should run parallel (e.g. number of cores) and an estimation of the remaining execution time.

[swagner]

Instead of implementing an OptimizerRunner as a specialized view for executing optimizers (i.e. for executing an Experiment) I recommend to enable hiding the details part in collection views. This would enable us to hide the details of all optimizer in the ExperimentView and an additional OptimizerRunner therefore would not be necessary.

I created ticket #1095 for this enhancement.

[swagner]

Showing and hiding details in collection views has been implemented (cf. ticket #1095).

[swagner]

Providing an estimation for the remaining execution time of an experiment is very hard as there are some algorithms (e.g. OSGA) for which the number of iterations is not known a priori. Therefore I do not think that this enhancement is worth the effort.

[swagner]

Providing a possibility for the user to choose how many optimizers of an experiment should be started in parallel is a good idea. I created ticket #1102 for this enhancement.

[swagner]

Milestone Iteration 4 deleted

[swagner]

Milestone Current deleted