Fixed #92 #94
Merged
Fixed #92 #94
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
Previously, the TPOT predict and score methods needed the training data to be passed to them again to provide the predictions and scores. Now, TPOT stores an internal pointer to the training data such that this is no longer required.
optimized_pipeline, training_features, and training_classes don’t need to be directly accessed by the user. I have made them private variables in the TPOT class.
The user should not need to access the TPOT classifier methods directly. I have made them private.
The user should not have to access pset and toolbox directly. I have made them private variables.
Updated the docs to reflect the changes to tpot.predict() and tpot.score().
Since the model functions were changed to private functions, the unit tests need to be updated to refer to the private functions properly.
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.
See #92 for details.