Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Do you feel supporting "reusable holdout" is in scope of prettytensor? #11

Open
windenntw opened this issue Feb 13, 2016 · 1 comment
Open

Comments

@windenntw
Copy link

Given that prettytensor combined with TF and ipython makes very very easy to do large scale, iterative exploration, I wonder if it would be in scope to incorporate a default implementation of Reusable Holdout [1] into the runner class and provided examples -- specially for less-experienced people to get a head-start in doing analysis in a good way.

[1] http://googleresearch.blogspot.com/2015/08/the-reusable-holdout-preserving.html

@eiderman
Copy link
Contributor

Yes, I think that an implementation would be good to have. The method mentioned in the paper (thresholdout) requires a full pass over both the training and holdout dataset so it would need to be implemented as part of the runner or queuing system. Utilities for splitting the data and tracking the number of uses would also be nice.

Would you be interested in submitting a patch? You would need to follow the instructions at https://github.com/google/prettytensor/blob/master/CONTRIBUTING.md

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

No branches or pull requests

2 participants