Timestamp and reformat epoch log message #211
Merged
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've found it practical to know how long a given epoch has taken to train. Also, format the losses nicer: * Print the weighed loss, not the unweighed. This is more intuitive, and has the property that the stated loss is indeed the sum of its components. * Print the loss in scientific notation, since they now can scale differently * Use uniform distance between the fields when printing
jakobnissen
force-pushed
the
timestamp
branch
from
d582b1f to
ac8b252
Compare
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.
I've found it practical to know how long a given epoch has taken to train. Also, format the losses nicer: