-
Notifications
You must be signed in to change notification settings - Fork 31
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
Wrong weight names after deserializing model from config #36
Comments
@shkarupa-alex, Thank you! |
Issue persist with TF 2.15.0 |
@shkarupa-alex, ['kernel', 'bias', 'gamma', 'beta', 'moving_mean', 'moving_variance']
['kernel', 'bias', 'gamma', 'beta', 'moving_mean', 'moving_variance']
['kernel', 'bias', 'gamma', 'beta', 'moving_mean', 'moving_variance']
['kernel', 'bias', 'gamma', 'beta', 'moving_mean', 'moving_variance'] Thank you! |
This issue is stale because it has been open for 14 days with no activity. It will be closed if no further activity occurs. Thank you. |
Issue is still here |
System information.
Describe the problem.
Models with custom layers miss their weight names after restoring from config
Describe the current behavior.
See example below. When replacing BatchNormalization with it's successor (the only thing changes - core vs custom class) after restoring from config we got wrong weight names.
Describe the expected behavior.
Weight names of custom layers should be preserved just like built-in ones.
Standalone code to reproduce the issue.
Source code / logs.
Code posted above will print:
The text was updated successfully, but these errors were encountered: