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

Timestamp isn't imported #15

Open
froody opened this issue Feb 22, 2023 · 2 comments
Open

Timestamp isn't imported #15

froody opened this issue Feb 22, 2023 · 2 comments

Comments

@froody
Copy link

froody commented Feb 22, 2023

I just imported all my runs from mlflow and the timestamps seem to reflect the time to import each run, not the actual times from mlflow

@mihran113
Copy link
Contributor

Hey @FOODy! Thanks a lot for reporting. That is actually the case, cause aim.Run object was created at that time.
The alternative will be to import the times from mlflow as a param for aim.Run object (for ex. mlflow_creation_time as string), would that make sense, or is it necessary for your case that the timestamp from mlflow's run to be reflected in aim.Run's created_at field?

@roman-vygon
Copy link

Adding to this, metric history is also created during sync, so absolute and relative time as x-axis aren't useful. It would be helpful to either replace the timestamp with one from MLFlow or add another column.

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

3 participants