Add logging step_loss to a tracker #6053
Closed
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
|
I think it's okay for us to keep the loss reporting as is. @patil-suraj WDYT? |
|
@sayakpaul what do you mean? How am I supposed to see when it starts giving me a zero-step loss? sit 24/7 at my laptop? |
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
I don't understand this change, the train_loss is enough for monitoring |
|
@patrickvonplaten well, why in wandb the main train_loss is not at zero, but in tqdm logs it says step_loss: 0.00? Initially train loss and step loss are the same, but over time step_loss becomes 0.00 and train_loss stays above... |
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.
What does this PR do?
Adds logging step_loss to a tracker
Who can review?