Allow resuming an exploration and running in substeps #118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables two new workflows addressing #107:
This can be useful when running
optimasinteractively. It would allow the user, for example, to tune the hyperparameters of the generator between eachrun.exploration_dir_path.This allows us to seamlessly continue a previous exploration
This features are enabled by the new
'reuse_output_dir'and'final_gen_send'options inlibensemblev1.0.0.Changes
n_evalsargument toExploration.run.resumeoption toExploration.Explorationnow keeps track of the number of evaluations.runfinishes is now calledexploration_history_after_evaluation_{}.npy.n_trialsproperty toGeneratorto easily count how many trials it has generated.Generator. Previously the generator was not informed about them. As a consequence, the last generated trials in theAxgenerators remained as not completed, even though they did run.gen_functionwhere more trials than needed would be generated in the final batch. Thegen_functionis now aware of the maximum number of trials that should be generated.Exploration._reset_libensemblemethod has been removed. It seems that this workaround (introduced in Updating for new libE interface #88) is no longer needed inlibensemblev1.0.0.libensemblev1.0.0.