Open lu-kas opened 4 years ago
This is now implemented with max_loop_inc
in the OptimiserProperties
.
However, it seems that the burn-in for the SPOTPY SCE is excluded from the counting, thus the first time an optimisation run is started an extra generation is performed - the burn-in.
If max_loop_inc
is set to one, then only the burn-in should be executed, if needed. but if it is set to a higher value and the burn-in needs to be run, this will in fact lead to an 'extra generation'. Do you have a short running test example for that?
have spotpy compute only one generation