-
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
Prefix log_metrics keys with class name in callbacks #12228
Conversation
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you need further help see our docs: https://pytorch-lightning.readthedocs.io/en/latest/generated/CONTRIBUTING.html#pull-request or ask the assistance of a core contributor here or on Slack. Thank you for your contributions. |
088725e
to
1f3e9c2
Compare
for more information, see https://pre-commit.ci
Are the broken code-runners blocking review? |
Yes, we have some blocking issues in our CI currently. Can you also update the CHANGELOG? |
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
The tests probably need to be adjusted given the new name. And a changelog entry would be nice :)
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.
should we do this for LearningRateMonitor?
What does this PR do?
It groups metrics logged by the built in callbacks by the callback class name.
Screenshot from tensorboard:
As i write a plethora of callbacks myself, i found this to be a nice thing to have, and why not upstream it while at it.
Fixes #12231
Does your PR introduce any breaking changes? If yes, please list them.
This may change the label/key some metrics are logged under.
Before submitting
PR review
Anyone in the community is welcome to review the PR.
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 🙃