Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store the training set internally so the user doesn't have to repeatedly pass it #9

Closed
rhiever opened this issue Nov 12, 2015 · 3 comments
Assignees

Comments

@rhiever
Copy link
Contributor

rhiever commented Nov 12, 2015

Since the training set is required to properly run the pipeline each time, this information should be stored internally so the user doesn't have to repeatedly pass it to TPOT (e.g., with the score() function).

@rhiever rhiever self-assigned this Nov 12, 2015
@rhiever
Copy link
Contributor Author

rhiever commented Nov 12, 2015

Actually, this is a bad idea. It can be disastrous to have multiple copies of a very large data set.

@rhiever rhiever closed this as completed Nov 12, 2015
@rasbt
Copy link
Contributor

rasbt commented Nov 12, 2015

Agreed! Plus, the training set may already be copied a bunch of times already (unless you disable the mutliprocessing in certain pipeline objects)

@rhiever
Copy link
Contributor Author

rhiever commented Nov 12, 2015

I actually need to work through the pipeline operator code and probably remove all the copy() operations. I think they're unnecessary, but I'm actually not sure if the DataFrames are being passed by copy or reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants