[Beholder plugin] use different summary key to avoid merging with the other summaries #1148
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.
This PR suggests to use a different summary key instead of using a default one for Beholder plugin.
Using Beholder plugin with
tf.estimator.Estimatorresults in the following InvalidArgumentError.This is because
tf.estimator.Estimatorregisters a loss scalar summary with a default collection key and merge it with the other summaries with the default key including Beholder's summary. As a result, we are required to feedframe_placeholderwhen running a training op.Since beholder writes summaries with a different cycle from a training op, it is better to separate them.