-
Notifications
You must be signed in to change notification settings - Fork 3
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
Possibility to subsample when loading the binary ? #13
Comments
Hi, I would like to know more details about your use case. What event types are you loading? and how large is the event file? Does your use case require iterating through all events, or does it only need to process certain filtered events?
If you simply want to iterate through the events, maybe you can try out the raw method by TensorBoard/TensorFlow as documented here. |
From: https://github.com/tensorflow/tensorboard/blob/master/README.md
And according to the
For instance, the asker from the StackOverflow thread trains over 20M steps. I train over 1e6 steps but run 100 experiments. If I log accurately the training score I end up with an extremely large DataFrame. It would be nice to have an option to downsample randomly (with a seed interface then) or evenly. Ideally for n training curves, same time steps are kept. Thank you for your consideration, |
Thanks for providing the detailed information. I think reservoir sampling is a useful feature and won't be too hard to implement. However, I'm not sure if we can manually set the RNG seed... This feature may be implemented by modifying the code here. I'll see if I can add this feature in my free time. Meanwhile, I suggest loading each experiments individually and downsample them by yourself. You can retrieve a deterministic results by stacking the downsampled experiments. |
Hello,
Is it possible to subsample the event file while loading ? What do you recommend if we don't have enough RAM like in a Jupyter notebook to read the event file ?
I know that tensorboard use a subsampling strategy.
Thanks for you consideration.
The text was updated successfully, but these errors were encountered: