-
Notifications
You must be signed in to change notification settings - Fork 395
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
Added MLflow callback #770
Conversation
Thank you for working on this. I have a few change suggestions how to possibly change this. Please tell me what you think. As you probably saw, this implementation is a bit different than those for tensorboard, neptune, sacred, etc. They all use an object that encompasses something like an "experiment" or "session", which is passed to the logger and is used to run all the methods on. Here, instead we have instead the local import of Without any knowledge of mlflow, I took a dive through the code and it seems like under the hood, And before doing any in depth review and testing out mlflow, could you please rename the callback to |
@cacharle Any updates, do you need support? |
Hi, found a way to use a |
Please tell me once the PR is ready for review. |
… test with real client and run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for addressing my initial comments. I tested the MLFlow logger out and it worked well. So this is a very welcome addition.
There are a few things that I would like you to address before merging, please take a look at the comments. On top of that, could you please add an entry to the CHANGES.md? Thanks.
Should I squash all the commit I made before merging the PR to avoid cluttering the logs? |
- doc string describing the logger usage and his parameters - Tidying up the unit tests - suffixing the attributes out of __init__
Please don't, it makes reviewing harder. I will squash before merging :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing the comments. The MLFlow logger is almost good to go, there are only a few minor comments left and a minor merge conflict to solve.
- Added missing commas - Added run and client parameters documentation for default behaviors - Updated mlflow reference to use intersphinx instead of URLs.
Thanks for implementing these changes and going through the extra effort of linking to the MLFlow docs. Now there is only the merge conflict left to solve :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, great work!
Here is a small draft for #769, I feel like the different loggers have a lot in common and could be refactored in a common class.