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

feat: LEAP-1340: Add label_order_matters option to naive comparison for timelinelabels #152

Merged
merged 3 commits into from
Aug 21, 2024

Conversation

jombooth
Copy link
Contributor

Adds a (slightly inefficient) option to naive classification that lets the results in annotations be in different orders. This will be used for TimelineLabels (see Video Frame Classification 2 in Notion)

@jombooth
Copy link
Contributor Author

jombooth commented Aug 21, 2024

note that merging #151 will fix CI on this PR. I'd just like us to comment a bit more in that PR about how the code is duplicated from LS SDK

Copy link

codecov bot commented Aug 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.95%. Comparing base (3792573) to head (df91b20).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #152      +/-   ##
==========================================
+ Coverage   69.64%   69.95%   +0.30%     
==========================================
  Files          26       26              
  Lines        2682     2709      +27     
==========================================
+ Hits         1868     1895      +27     
  Misses        814      814              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jombooth jombooth merged commit 73bf332 into master Aug 21, 2024
6 checks passed
@jombooth jombooth deleted the fb-LEAP-1340/naive-for-timelinelabels branch August 21, 2024 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants