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

Use MLflow experiment name instead of id for Aim experiment name #9

Open
stedn opened this issue Feb 3, 2023 · 5 comments
Open

Use MLflow experiment name instead of id for Aim experiment name #9

stedn opened this issue Feb 3, 2023 · 5 comments

Comments

@stedn
Copy link

stedn commented Feb 3, 2023

This would be just a "nice-to-have" if it's possible. Currently, the Aim experiment name is set to the experiment ID from mlflow. This makes it a little bit confusing because it's not always top-of-mind which experiment ID is associated with a given run.

Looking at the aim repo I couldn't see a way to set the experiment name separate from the experiment ID so this might not be possible, but thought I would check.

@stedn
Copy link
Author

stedn commented Feb 3, 2023

Also just wanted to add that I think this project is some great work and will be very helpful to my team using MLflow and wanting to incorporate some of the visually attractive cross-run comparison tools like you'd find in W&B etc. Thanks!

@alberttorosyan
Copy link
Member

Hey @stedn!
I think it should be possible to set the experiment name during the conversion.
mlflow Python SDK has a method for getting the Experiment object by it's ID.

@mihran113
Copy link
Contributor

Hey @stedn! Thanks for the suggestion, makes sense. This should be relatively easy to add, will include in the next release.

@ositaunus
Copy link

maybe stating the obvious: instead of 'instead', it would be more helpful to have both available - the name as the first thing you see, because it is more intuitive, and then with little inspection the ID to confirm it is the right experiment (sometimes names can be similar)

@sirykd
Copy link
Contributor

sirykd commented Feb 20, 2023

with little inspection the ID to confirm it is the right experiment (sometimes names can be similar)

Should be covered by #14, which makes the experiment id accessible again via 'mlflow_experiment_id'

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

No branches or pull requests

5 participants