[metrics] reuse metrics in a progress bar
See original GitHub issue🚀 Feature
reduce duplicated metrics in general output dict and progress bar
Motivation
it can be confusing for a user to passing the same metric multiple times in single output
Pitch
in such case just specify key/name of metric shown in progress bar… but still it would make it less flexible to show what you want just having {‘loss’: None, “my-var”: 123} and none mean that it takes from the general/upper-level dict?
Additional context
https://pytorch-lightning.slack.com/archives/CQXV8BRH9/p1585479078063900
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Reuse Metrics - YouTube
By now it's well known you can obtain useful DITA production metrics.But measuring reuse in particular is tricky, since there are many ways ......
Read more >Metrics for Reuse Size and Reuse Measuring Size How hard ...
Software Reuse: Metrics and Models. ACM Computing ... A metric is a quantitative indicator of an ... ô Accurate reuse measurement to track...
Read more >Reuse metrics - Wikipedia
Amount of reuse metrics are used to assess and monitor a reuse improvement effort by tracking percentages of reuse for life cycle objects....
Read more >(PDF) Software Reuse: Metrics and Models. - ResearchGate
In this article we survey metrics and models of software reuse and reusability, and provide a classification structure that will help users ...
Read more >4 CSS Progress Bars You Can Use on Your Website
These ready-to-use elements help you create dynamic web applications quickly and efficiently. You can use progress bars to display metrics, show ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I agree that we need to keep dictionaries for backward compatibility, I just think that if we offer a solution to users that takes care of the problem (
Resultobjects) and it is not that hard to convert from dictionaries, then it is not really a problem :]@Borda I think we can close this, since users just need to use the
Resultobjects to remove such duplications