Bugfix: better display and settings control#17
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
📋 Summary
Important
README, typos, ...)📝 Changes
Details
torchmeter/display.py: Fixed the validation check mechanism for custom settings, and the setting application was extracted as an independent logic to better meet the requirements of various initialization parameters. In addition,repeat_footerwas set as a class property and the acceptable types were extended, making the setting truly convenient and efficient. In the table rendering,keep_custom_nameandkeep_new_colare added to control whether the custom column names and new columns persist during the program's execution.torchmeter/engine.py: fix module scanning bug, causenamed_children()will squash repeat modules into one.