[python] PF batch normaliation var initialization with 1 (break behavior backward compatibility)
#294
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TakuyaNarihira
added
enhancement
release-note-break-compat
TakuyaNarihira
changed the title
var initialization with 1 (break behavior backward compatibility)var initialization with 1 (break behavior backward compatibility)
TakuyaNarihira
changed the title
var initialization with 1 (break behavior backward compatibility)var initialization with 1 (break behavior backward compatibility)
Note this breaks the behavior backward compatibility
TakuyaNarihira
force-pushed
the
feature/20181107-pf-batch-norm-var-init-1
branch
from
a6d422f
to
b477199
Compare
TakuyaNarihira
changed the title
var initialization with 1 (break behavior backward compatibility)var initialization with 1 (break behavior backward compatibility)
TE-StephenTiedemann
pushed a commit
that referenced
this pull request
Feb 18, 2022
F.cumsum and F.cumprod
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 must be merged after merging #293)
This changes the default initialization of
bn/varparameter from zero to one. Initialization with 0 biased the running variance towards 0. Also, the 0 initialization led to unstable inference at the early stage of training due to near-0 division in bn.Note that this breaks the behavior backward compatibility in parametric_functions.batch_normalization. Any experiment previously performed can be reproduced by passing
param_init={'var': I.ConstantInitializer(0)}option.