Fix behaviour of unfrozen BatchNormalization layer (resolves #46) #47
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.
Previously, if
BatchNormalization
was initialized withBatchNormalization(freeze=False)
, its behaviour was not equivalent to the standardBatchNormalization
layer, as one would expect. Instead, it was always forced to be in training mode, providing wrong validation results.This PR does not change the behaviour for
freeze=True
, but makes the layer equivalent to the standardBatchNormalization
layer from Keras forfreeze=False
.