fix to allow mutations to actually occur to an individual #108
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?
When experimenting with TPOT2 and only allowing mutations to occur, no variation would be applied to the parents. This is because the
var_op
was 'mutate', not 'mutation'. Additionally, we needed to send an individual to thecopy_and_mutate
function, not a numpy array. This fix does all that.Where should the reviewer start?
tpot2/population.py
->create_offspring2()
How should this PR be tested?
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: