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
I am using the MLFlowLogger to keep track of my experiments. To my knowledge, there is no possibility to enable the logging of system metrics: https://mlflow.org/docs/latest/system-metrics/index.html
To me, it seems that both mlflow.enable_system_metrics_logging() and the environment variable MLFLOW_ENABLE_SYSTEM_METRICS_LOGGING are ignored by MLFlowLogger.
Would it be possible to add the option? I think the most sensible would be to add an argument to MLFlowLogger mirroring the behavior of mlflow.start_run(log_system_metrics=True).
As I am already asking, would it also be possible to rename/customize the checkpoints of log_model? The names contain the epoch as number without leading zeros, such that they are incorrectly sorted in the MLflow interface. I would prefer to have some leading zeros such that lexicographical ordering corresponds to the ordering of the epochs.
Description & Motivation
I am using the
MLFlowLogger
to keep track of my experiments. To my knowledge, there is no possibility to enable the logging of system metrics: https://mlflow.org/docs/latest/system-metrics/index.htmlTo me, it seems that both
mlflow.enable_system_metrics_logging()
and the environment variableMLFLOW_ENABLE_SYSTEM_METRICS_LOGGING
are ignored byMLFlowLogger
.Would it be possible to add the option? I think the most sensible would be to add an argument to
MLFlowLogger
mirroring the behavior ofmlflow.start_run(log_system_metrics=True)
.As I am already asking, would it also be possible to rename/customize the checkpoints of
log_model
? The names contain the epoch as number without leading zeros, such that they are incorrectly sorted in the MLflow interface. I would prefer to have some leading zeros such that lexicographical ordering corresponds to the ordering of the epochs.Pitch
No response
Alternatives
No response
Additional context
No response
cc @lantiga @Borda
The text was updated successfully, but these errors were encountered: