-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Fix invalid value for weights_summary #5296
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5296 +/- ##
======================================
Coverage 93% 93%
======================================
Files 134 134
Lines 9950 9954 +4
======================================
+ Hits 9261 9266 +5
+ Misses 689 688 -1 |
@rohitgr7 as you are changing API we need to move it to 1.2 |
I thought I created this branch on top of release branch only. Will update it. |
8088068
to
d6bc41b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. One thing:
Why not keep mode
to avoid the API change?
+1 for keeping mode please :) |
I did that to have the exception at one place for both the cases.
Will update this then. |
e22b0b0
to
3f4f4bd
Compare
@rohitgr7 is it as a bugfix for master or a feature for 1.2? there is some confusion as it is a 1.2 milestone but the target is |
bugfix now. forgot to update the milestone. Updated! |
Didn't realize the API was inconsistent. I like what you propose. We can do it in another PR |
* Fix weights_summary * use mode * fix * optional * what was I thinking (cherry picked from commit 062800a)
What does this PR do?
The main fix here is if you do
model.summarize(None)
it still prints the total params, trainable params, ... and if you domodel.summarize('invalid_string or value')
it won't raise an error and will act likeNone
.Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃