[Feature] Support individual scalar reporting without plots
See original GitHub issueWhen using logger.report_scalar
a plot is automatically generated to accommodate for a time-series axis.
There is no current way for the user to report a single scalar with a name (that is not a time-series) and have it both aesthetically pleasing and visible enough in the WebUI. Using iteration=0
just wastes space by creating a scatter plot with a single datum.
It would be great to have e.g. logger.report_scalar(name="MAE", value=mae)
, and have it visible as a table (or similar) with e.g.:
Scalar name | value |
---|---|
MAE | 0.123 |
NRMSE | 0.4 |
My favorite scalar | and it’s actually a string |
Even better, once these are in place, they can automatically be aligned between multiple experiments for comparison.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:23 (17 by maintainers)
Top Results From Across the Web
Scalars Reporting - ClearML
To reports scalars, call the Logger.report_scalar method. To report more than one series on the same plot, use the same title argument. For...
Read more >TensorBoard Scalars: Logging training metrics in Keras
This tutorial presents very basic examples to help you learn how to use these APIs with TensorBoard when developing your Keras model. You...
Read more >Apply insights in Power BI to explain fluctuations in visuals
Easily gain insights to increases or decreases in Power BI Desktop or the Power BI service.
Read more >MATLAB fsurf - Plot 3-D surface - MathWorks
This MATLAB function creates a surface plot of the function z = f(x,y) over the default ... Use fs to query and modify...
Read more >4.2 Simple base R plots | An Introduction to R
You can also use the formula notation when using the plot() function. However, in contrast to the previous method the formula method requires...
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
Hey, thanks for replying so quickly!
Adding it to the leaderboard is a good start (though requires some adjusting for column names). It’s also the single experiment look that just looks… bad. This is unhelpful and hard to read:
It would make sense to have these as a table instead, as some kind of “experiment final metric” or some metric that is not associated with a specific timepoint.
Hi @cpatrickalves @idantene @mmiller-max , while there isn’t a solution yet, it is in the making!
The plan is to have a logger interface in which you can do something like logger.report_single_metric(name=“my metric”,value=123). In the scalars tab, you’ll have a table with these reported metrics. This means there will be a single table per experiment with those values. The table will also appear in the comparison view, so you can compare values across experiments. As for coloring according to number, we’ll take a look but not sure it’ll be released in the first go (Let me know if this is critical and I can try and re-prioritize).
Anything I missed? I’ll update here once there’s something available