Batchruns are not executed correctly

[sforsten]

Batchruns which contain optimizers that produce multiple runs are not executed correctly, because the batchrun stops when the runs counter is larger than the repetitions counter. The described behavior can be reproduced by executing the attached file.

E.g., A batchrun should be repeated 5 times and contains an experiment with 3 standard algorithms. The batchrun stops after 2 repetitions, as the embedded experiment produces 3 runs with every execution.

Additionally the execution time is not correct after removing all runs from the run collection (should be 00:00:00).

[mkommend]

test file that demonstrates the described behavior

[mkommend]

Upon further investigation it is obvious that this behavior has nothing to to with the number of runs present in the BatchRun.

[mkommend]

r7576: Removed questionable source lines in execution state handling in the BatchRun and the Experiment.

[mkommend]

Please review and test carefully r7576. It would be best if the execution state handling works correctly right now, but I am not quite convinced.

In addition I am not sure of the purpose of the lines, which were removed with r7576.

[abeham]

I just found a bug that I think is related to this: When you create a new batch run, add an optimizer and click on the run button of that optimizer instead of that on the batch run, the optimizer will run once and then terminates. This is correct and expected, but the batch run also stops which is incorrect - it should be in paused state.

Maybe we should disable showing the run controls for the algorithm altogether when it's embedded into a batch run. I mean it does look complicated when you have two play, pause, stop, and prepare buttons.

[abeham]

This batch run can be used to view the behavior described in comment 6.

[ascheibe]

I have talked to Andreas today and we found another bug. When an inner optimizer is executed once and then the batch run is prepared and afterwards the inner optimizer is executed again, it is executed repetitions-times. I have fixed this bug and the one mentioned in comment 6 and 7 in r8189. Maybe you can have a look at it again if everything still works as expected. I have also tested your fix for the original problem and it still works.

[mkommend]

r8190: Corrected tool tips in optimizer views and last errors in batchrun execution state handling.

[abeham]

r8194:

• Replaced in BatchRun the four boolean action flags with an enum
• Caught InvalidOperationException when changing the state of the nested optimizer, which usually occurs in a race-condition

[swagner]

Thank you for working on this issue. I reviewed the changes and I do not have any additional comments. However, to be honest I am not really happy with this code, as it is still quite complex, error-prone and hard to understand. We all know that execution state handling in optimizers, batchruns and experiments is complicated and cumbersome. Therefore we should think about a fundamental redesign at the next opportunity. I also agree with abeham that we probably should remove the steering buttons of embedded optimizers.