Skip to content
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

Add step parameter to TensorBoardLogger.log_hyperparams #20176

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

ringohoffman
Copy link
Contributor

@ringohoffman ringohoffman commented Aug 7, 2024

What does this PR do?

Adds a step parameter to TensorBoardLogger.log_hyperparams. This also mirrors the global_step param of torch.utils.tensorboard.SummaryWriter.add_hparams.

Currently, the metrics that get logged using this method are always logged to step 0:

so no meaningful graph is made for the metrics passed to TensorBoardLogger.log_hyperparams. torch.utils.tensorboard.SummaryWriter.add_hparams had the same problem until global_step was added:

I added these changes to my local run and this is what I see now when I call self.logger.log_hyperparams(hparams, metrics=metrics, step=step):

Screenshot 2024-08-07 at 02 29 50

Compared to before (2 epochs in, but you wouldn't know):

Screenshot 2024-08-07 at 02 48 16
Before submitting
  • Was this discussed/agreed via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you list all the breaking changes introduced by this pull request?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

Reviewer checklist
  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

📚 Documentation preview 📚: https://pytorch-lightning--20176.org.readthedocs.build/en/20176/

The metrics that get logged using this method are always logged to step 0, so no meaningful graph is made
@github-actions github-actions bot added fabric lightning.fabric.Fabric pl Generic label for PyTorch Lightning package labels Aug 7, 2024
Copy link

codecov bot commented Aug 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89%. Comparing base (5be58f6) to head (a0c12cf).

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #20176   +/-   ##
=======================================
  Coverage      89%      89%           
=======================================
  Files         267      267           
  Lines       23084    23084           
=======================================
  Hits        20585    20585           
  Misses       2499     2499           

@ringohoffman
Copy link
Contributor Author

Is this good to merge?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fabric lightning.fabric.Fabric pl Generic label for PyTorch Lightning package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants