weiqi001/bankruptcy-mlflow-dashboard
๐ MLflow tracking dashboard
The experiment history for the Corporate Bankruptcy Early-Warning System, served from Hugging Face rather than from someone's laptop.
Every training run of the pipeline records ~15 parameters, ~15 metrics and its artefacts, plus a nested run for each candidate algorithm on each feature set. That is what you are looking at.
Where the data comes from
GitHub Actions Hugging Face
-------------- ------------
model-training
mlflow server on :5555 (in the job)
train.py logs every run
โ
โผ
sync-tracking
uploads mlflow.db + mlruns/ โโโโโโโโโถ dataset repo
restarts this Space โโโโโโโโโถ this Space
โ
โผ
restore.py pulls the
snapshot on boot, then
mlflow server serves itThe dashboard therefore reflects every completed pipeline run, refreshed within about a minute of one finishing, because the pipeline restarts this Space after it syncs.
What "real-time" means here
To switch to live logging, point the training job at this Space:
env:
MLFLOW_TRACKING_URI: https://<owner>-<space>.hf.spaceRead the trade-offs in the project's docs/MLFLOW_DASHBOARD.md before doing that โ chiefly that a Space filesystem is ephemeral, so a restart loses anything not yet synced, and that a public Space is writable by anyone who knows the URL.
Configuration
Set in the Space's Settings โ Variables and secrets:
Without MLFLOW_DATASET_REPO the Space still starts, with an empty store.
Related
- Application โ the Streamlit early-warning app
- Dataset โ the 10,503 firm-years the model was fitted on
- Source โ the GitHub repository and its MLOps pipeline
