Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MLflow Trainer Callback #7698

Closed
noise-field opened this issue Oct 10, 2020 · 3 comments · Fixed by #8016
Closed

MLflow Trainer Callback #7698

noise-field opened this issue Oct 10, 2020 · 3 comments · Fixed by #8016

Comments

@noise-field
Copy link
Contributor

noise-field commented Oct 10, 2020

🚀 Feature request

A callback to log hyperparameters, metrics and cofings/weights to MLFlow, like the existing wandb and Tensorboard callbacks.

Motivation

I use MLFlow as my primary experiment tracking tool. It is convenient to run on a remote server and log the results from any of your training machines, andit also facilitates collaboration.

Trainer is an amazing tool, it makes it very simple to train models, however, the only way to modify the training loop to include custom logging seems to add a callback.

Your contribution

I can contribute a PR.

@julien-c
Copy link
Member

Happy to get a PR on this!

@noise-field noise-field changed the title MLFLow Trainer Callback MLflow Trainer Callback Oct 11, 2020
@RahulKulhari
Copy link

@noise-field is remote tracking with remote server uri with authentication also enabled as part of this feature request ?

@noise-field
Copy link
Contributor Author

@RahulKulhari well, this is not part of the feature request, but you can certainly do remote tracking with mlflow callback. However, you will need to use environment variables (MLFLOW_TRACKING_URI , MLFLOW_TRACKING_USERNAME, MLFLOW_TRACKING_PASSWORD) in advance to configure your connection to the remote server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants