Lightning-AI/pytorch-lightning

MLflow logger to log config.yaml as artifact

Open

#18,396 opened on Aug 25, 2023

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Python (3,233 forks)batch import
featurehelp wantedlogger: mlflow

Repository metrics

Stars
 (26,687 stars)
PR merge metrics
 (Avg merge 9d 15h) (3 merged PRs in 30d)

Description

Description & Motivation

The MLflow logger does not currently log the config.yaml file when using LightningCLI, meaning MLflow does not contain a complete record of an experiment

Pitch

The config.yaml file to be logged as an artifact

Alternatives

None, currently use a confluence page to link the MLflow run and config.yaml which is tedious

Additional context

No response

cc @borda

Contributor guide

Research direction
Inspect the MLflow logger class in the codebase, identify where config.yaml is generated by LightningCLI, and add logic to log it as an artifact using mlflow.log artifact.
Tech stack
python
Domain
machine learningai
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75