Two level logs
See original GitHub issueI’d like to log the values at two levels, I mean,
iiter = 0
for epoch in range(1, 10):
for batch in data_loader:
iiter += 1
loss = model(batch)
...
wandb.log({"loss": loss}, step=iiter)
...
wandb.log({"loss_mean": loss_mean}, step=epoch)
However, it shows “wandb: WARNING Step must only increase in log calls”. Is there a way to control two level values?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Logging Levels: What They Are & How to Choose Them
Learn about the most common log levels and how they work. ... There are two main things that you can think of, especially...
Read more >Understanding logging levels - IBM
Each log message has an associated log level that gives a rough guide to the importance and urgency of the message. Each level...
Read more >When to use the different log levels - Stack Overflow
I generally subscribe to the following convention: Trace - Only when I would be "tracing" the code and trying to find one part...
Read more >Log4j – Custom Log Levels - Apache Logging Services
Log4J 2 supports custom log levels. Custom log levels can be defined in code or in configuration. To define a custom log level...
Read more >Logging Levels: What They Are and How They Help You
Oh-and generally, something called a logging level. ... When it comes to logging, you have two essential and opposing forces, if you will....
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 FreeTop 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
Top GitHub Comments
For example,
Now different categories values are shown in the same level in the UI.
We are closing this issue due to inactivity, please comment to reopen.