-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Add --samples_per_plugin to specify explicit sampling counts #1138
Conversation
…ification of samples to keep per summary type. Previously, TensorBoard always downsampled summaries for OOM reasons but some users wanted the ability to keep all their summaries of some types. With this flag, --samples_per_plugin='histogram=2,images=0' keeps TensorBoard defaults for other summaries, restricts the number of histograms to 2, and keeps all image summaries.
samples_per_plugin
that allows for custom spec…
If using tensorboard-pytorch, how can one upgrade the tensorboard to 1.9.0 in order to use this feature? |
@linzhiqiu We have no affiliation with tensorboard-pytorch, but as far as I can tell it looks like tensorboard-pytorch primarily offers a PyTorch-compatible way to write summary data to event files, which you'd then view with regular TensorBoard. So however you're getting TensorBoard now, you would just update it. If you're getting TensorBoard as part of a TensorFlow installation via |
Thank you so much for this feature. I was about to manually export all the images, this is 100x better. 😍 |
Aw, thank you for telling me that! :)
…On Wed, Jul 25, 2018 at 4:41 PM Jon Perl ***@***.***> wrote:
Thank you so much for this feature. I was about to manually export all the
images, this is 100x better. 😍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1138 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ab4bt0beKouQ9ys7GzMdwjtY0vFNWLKGks5uKQJFgaJpZM4TXmlH>
.
|
Summary: Before `--samples_per_plugin` existed, the only way to change the sampling thresholds was to patch `application.py` manually. But the flag has been the right way to do this since #1138, and manual patching has been insufficient since the flag value was exposed to plugins in #3271. There’s no need to discuss this implementation detail any more. wchargin-branch: readme-remove-application-reference wchargin-source: b79027ec8b279537bdf38f7b5d7f36cf5dd38498
Summary: Before `--samples_per_plugin` existed, the only way to change the sampling thresholds was to patch `application.py` manually. But the flag has been the right way to do this since #1138, and manual patching has been insufficient since the flag value was exposed to plugins in #3271. There’s no need to discuss this implementation detail any more. wchargin-branch: readme-remove-application-reference
Add TensorBoard flag
samples_per_plugin
that allows for custom specification of samples to keep per summary type.Previously, TensorBoard always downsampled summaries for OOM reasons but some users wanted the ability to keep all their summaries of some types.
With this flag, --samples_per_plugin='histogram=2,images=0'
keeps TensorBoard defaults for other summaries, restricts the number of histograms to 2, and keeps all image summaries.