You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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
The text was updated successfully, but these errors were encountered: