Perform all ops in apply_gradient in a given tf.name_scope. #17550
+21
−19
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.
Hi,
today when looking in Tensorboard, I found out that the new optimizers do not create operations in a
tf.name_scope
of thename
given to theOptimizer
constructor.That was the case previously -- see
keras/keras/optimizers/legacy/optimizer_v2.py
Lines 701 to 754 in bdbca4f
while the new
Optimizer
runs onlybuild
in the name scope, not the update operations, seekeras/keras/optimizers/optimizer.py
Lines 633 to 656 in bdbca4f
Therefore, in this pull request, I moved the update operations in
apply_gradient
also inside thetf.name_scope
.The tests seem to run fine, code is correctly reformatted, and I verified in Tensorboard that after the change the update operations are indeed in a name scope.