-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metric aggragation is broken for LoggerCollection #1547
Comments
are you using the last master? |
@Borda thanks! It now works for a single logger. But it seems that problem persists when several loggers are used, so I updated the issue. This happens because metrics to aggregate are not propagated to child loggeres |
I'm also having this issue with multiple loggers on master. Seems that the test results are printed at the end, but the loggers don't log the test metrics. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
🐛 Bug
After changes in #1278 it is now not possible to log testing metrics after traning while using several loggers.
To Reproduce
Say we want to run a MINST example and also want to add a change - log testing metrics after training. For that we define a Callback
and pass it to trainer
callbacks
argument.We would also like to use several loggers to track all metrics, say
MLFlowLogger
andTensorBoardLogger
. For this we create instances of these loggers and pass them intoTrainer
in a list.Expected behavior
Testing metrics should be logged - but they don't as there's no final aggregation when our logger is a
LoggerCollection
Additional context
In my opinion, the logic in
agg_and_log_metrics
and_finalize_agg_metrics
is hard to follow, so I'd be happy if user could choose plain oldlog_metrics
which worked nicely.The text was updated successfully, but these errors were encountered: