lincc-frameworks / lincc-frameworks/hyrax

Properly log model artifact in MLFlow

Open
#189 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
41
Forks
7
Avg merge
5d 1h
Merged PRs (30d)
8

Description

The model weights file is logged automatically in the primary results directory, MLFlow offers a similar method to store models, but expects those logged models to include either a `signature` or `input_example`. Neither of which seems to be working as expected within the context of Fibad. Providing nothing results in a `WARN` log, and attempting to provide example input produces other error messages.

```
with mlflow.start_run(log_system_metrics=True):
_log_params(config)

# Run the training process
trainer.run(train_data_loader, max_epochs=config["train"]["epochs"])

mlflow.pytorch.log_model(model, "models") # This should include either signature = ... or input_example = ...
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the MLflow run block shown in the issue, especially the trainer.run call and mlflow.pytorch.log_model invocation. Reproduce the WARN and input_example errors with the existing training configuration, then trace how the trained model and example inputs are represented in Fibad. Done means model artifacts are logged without the warning or reported errors and include the required metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.