Increase reproducibility and control stochasticity #106
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merging Pedro's fix on the mutation/crossover variations applied to the pop.
… passed to models
|
tested on macos/windows/linux. Also on 3.9/3.10/3.11. Looks good! |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[please review the Contribution Guidelines prior to submitting your pull request. go ahead and delete this line if you've already reviewed said guidelines.]
What does this PR do?
We increase the reproducibility of tpot2 by locking in a random number generator that is passed between classes. Additionally, we pass the random_state value to all other functions that use it within tpot2.
Where should the reviewer start?
Reviewers can start by looking at the estimator -> evolvers -> all classes that evolver uses to evolve population.
How should this PR be tested?
Making sure that multiple seed runs yield similar results across different runs/computational environments.
Any background context you want to provide?
What are the relevant issues?
[you can link directly to issues by entering # then the number of the issue]
Screenshots (if appropriate)
Questions: