You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 26, 2021. It is now read-only.
Description
Provide means to specify logging Frequency during training. For Visdom, all logging results are kept in memory (risking OOM), and with tensorboardlogger, disk I/O may bottleneck training otherwise.
Proposal
There are different ways to tackle this. One could be to utilize CombinedLogger from trixi. However, I'm unsure whether CombinedLogger allows for logging frequencies assigned per logged object (e.g. Scalars every iteration and images every Nth iteration), which is a feature I would like to have.
Additional context
Solve before implement logging frequencies as part of #47
The text was updated successfully, but these errors were encountered:
Description
Provide means to specify logging Frequency during training. For Visdom, all logging results are kept in memory (risking OOM), and with tensorboardlogger, disk I/O may bottleneck training otherwise.
Proposal
There are different ways to tackle this. One could be to utilize
CombinedLogger
fromtrixi
. However, I'm unsure whetherCombinedLogger
allows for logging frequencies assigned per logged object (e.g. Scalars every iteration and images every Nth iteration), which is a feature I would like to have.Additional context
Solve before implement logging frequencies as part of #47
The text was updated successfully, but these errors were encountered: