WandB batch metrics logging error
See original GitHub issue🐛 Bug Report
In wandb all batch metrics are logged as single value per epoch.
Expected behavior
Batch metrics must be logged once per step.
Catalyst version: 21.7
Additional context
The problem is here:
https://github.com/catalyst-team/catalyst/blob/master/catalyst/loggers/wandb.py#L115
Step must be equal to global_sample_step, not global_epoch_step.
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (18 by maintainers)
Top Results From Across the Web
Log Data with wandb.log - Documentation - Weights & Biases
Call wandb.log(dict) to log a dictionary of metrics, media, or custom objects to a step. Each time you log, we increment the step...
Read more >Attempting to log metrics per epoch returns a "step must ...
log to the step in my enumerate statement. However, doing so gave me a warning: wandb: WARNING Step must only increase in log...
Read more >Brief Introduction to Logging with Weights & Biases
Logging metrics and various kinds of data using wandb.log; Analyzing model with wandb.watch; Checking statistics of system usages collected by ...
Read more >Logging — PyTorch Lightning 1.8.5.post0 documentation
Track your parameters, metrics, source code and more using Comet. ... is possible if the batch is a custom structure/collection, then an error...
Read more >Logging results and uploading models to Weights & Biases
In this example, we train a simple XGBoost model and log the training results to ... X = batch["data"] y = batch["target"] #...
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
Just running tests. PR coming soon
Okay, thanks for the clarification. I’ll update the logger with the intended artifacts use case.