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

Collect feedback on MLflow logging #938

Open
wd60622 opened this issue Aug 16, 2024 · 2 comments
Open

Collect feedback on MLflow logging #938

wd60622 opened this issue Aug 16, 2024 · 2 comments
Labels

Comments

@wd60622
Copy link
Contributor

wd60622 commented Aug 16, 2024

Handful of items are logged now. Would like to know what else would be useful? Thinks like:
General PyMC

  • total samples?

MMM

  • saturation curves
  • posterior plots

Doesnt need to be in the autologging per say

@wd60622
Copy link
Contributor Author

wd60622 commented Aug 19, 2024

Many of the params should be logged before the pm.sample in the autologging. This way, the UI gets information about the run before a long function call happens

@wd60622
Copy link
Contributor Author

wd60622 commented Aug 24, 2024

Parameters will act like strings. So storing number of sample would not allow for comparisons like: params.posterior_samples >= 2000

Thus, it might make sense to store as a metric for better experience in the MLflow UI. Though it might be handled differently in tools like DataBricks

Reference: https://mlflow.org/docs/latest/search-runs.html#searching-by-params

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

No branches or pull requests

1 participant