-
Notifications
You must be signed in to change notification settings - Fork 4
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
Remove label keys from lite
classification
#776
Conversation
@@ -173,35 +171,24 @@ def classifications_image_example() -> list[Classification]: | |||
Classification( | |||
uid="uid5", | |||
groundtruths=[ | |||
("k4", "v4"), | |||
("k5", "v5"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cut the "k5" and "k3" entries out of this data, rather than replicating our tests 3x everywhere this data is used, because these keys didn't seem worth repeating as separate, unique tests: they both just test for a false negative / false positive combo, which is already tested in "uid5" by gt=['v4'] and pd=['v1', 'v8']
{ | ||
"type": "Accuracy", | ||
"value": [0.0], | ||
"value": [0.5], # TODO add comment about the bug here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch! The 1/3 accuracy is b/c we are dividing by n_datums
in the computation. This resulted in a flawed output since that label key didnt exist for one datum.
Improvements
lite
tests and functions to no longer use label keys