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
Periodic flushing of Comet experiment data by CometLogger is sometimes necessary to ensure all metrics and data remain up to date in the Comet UI and aligned with saved model checkpoints. Some users accomplish this by creating custom Callbacks, though this approach can be rather cumbersome.
Pitch
It is proposed to enhance the CometLogger implementation to support flushing collected data to Comet after each checkpoint is saved. This would be configurable via the flush_every parameter of the CometLogger.
This improvement allows users to manage Comet experiment flushing using the standard PyTorch Lightning approach by registering appropriate ModelCheckpoint callbacks with the Trainer.
Description & Motivation
Periodic flushing of Comet experiment data by
CometLogger
is sometimes necessary to ensure all metrics and data remain up to date in the Comet UI and aligned with saved model checkpoints. Some users accomplish this by creating custom Callbacks, though this approach can be rather cumbersome.Pitch
It is proposed to enhance the
CometLogger
implementation to support flushing collected data to Comet after each checkpoint is saved. This would be configurable via theflush_every
parameter of theCometLogger
.This improvement allows users to manage Comet experiment flushing using the standard PyTorch Lightning approach by registering appropriate
ModelCheckpoint
callbacks with theTrainer
.Alternatives
No response
Additional context
No response
cc @lantiga @Borda
The text was updated successfully, but these errors were encountered: