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
From Dmitriy:
it seems like right now we have a broken/incorrect metric search logic. It seems like then cause of the problem is here -> https://github.com/G-Research/fasttrackml/blob/main/pkg/api/aim/runs.go#L837, mainly related to metric.ContextID != contextID this moment. Because of that align search stopped working and we can see a problem(asked Fabio to double check and align search doesn’t work for him as well). So you can try to reproduce it on your end:
checkout main.
fully reset database.
run service
run python minimal_fasttrackml.py to fill example metrics.
open AIM UI -> metrics -> axes properties from the right panel.
select any metric from the list.
you will see an error -> Not all lines are aligned .
The text was updated successfully, but these errors were encountered:
From Dmitriy:
it seems like right now we have a broken/incorrect metric search logic. It seems like then cause of the problem is here -> https://github.com/G-Research/fasttrackml/blob/main/pkg/api/aim/runs.go#L837, mainly related to metric.ContextID != contextID this moment. Because of that align search stopped working and we can see a problem(asked Fabio to double check and align search doesn’t work for him as well). So you can try to reproduce it on your end:
checkout main.
fully reset database.
run service
run python minimal_fasttrackml.py to fill example metrics.
open AIM UI -> metrics -> axes properties from the right panel.
select any metric from the list.
you will see an error -> Not all lines are aligned .
The text was updated successfully, but these errors were encountered: