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
This brings up a good point. I think that the evaluation tables should have the matrix uuid just like the predictions table has.
As far as how to achieve this now, I think you could do a JSON join from specific fields in the matrix_metadata column in the matrices table and columns from the evaluation table.
- Add matrix uuid column to both train and test evaluations table
schemas,
updating the factory as well and adding migration to create it
- commit session in test util MockMatrixStore so the matrix actually
shows up in the database
- In ModelEvaluator, include matrix_uuid in evaluation data sent to
database
Running
triage
without storing the predictions (in CLI:--no-save-predictions
flag) apparently "breaks" the connection between model and test matrix.What do I mean by "breaks" is that (again, apparently) there is no way to see, in the DB in which matrix the model was tested.
Originally, one possible query to do that was:
Any ideas?
The text was updated successfully, but these errors were encountered: