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

IVF-PQ: tighten the test criteria #1135

Merged
merged 9 commits into from
Jan 14, 2023

Conversation

achirkin
Copy link
Contributor

Make the recall reporting a bit more verbose and try to tighten the min_recall for various test cases. This should help spot any regressions in future and improve our understanding of ivf-pq performance for various inputs.

@achirkin achirkin self-assigned this Jan 11, 2023
@github-actions github-actions bot added the cpp label Jan 11, 2023
@achirkin achirkin added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change 2 - In Progress Currenty a work in progress labels Jan 11, 2023
@achirkin achirkin marked this pull request as ready for review January 12, 2023 15:02
@achirkin achirkin requested a review from a team as a code owner January 12, 2023 15:02
Copy link
Member

@cjnolet cjnolet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@cjnolet cjnolet added 5 - Ready to Merge and removed 2 - In Progress Currenty a work in progress labels Jan 13, 2023
@achirkin
Copy link
Contributor Author

Not yet, sorry! I'm doing a bit more investigation on couple edge cases

@achirkin achirkin added 5 - DO NOT MERGE Hold off on merging; see PR for details 2 - In Progress Currenty a work in progress and removed 5 - Ready to Merge labels Jan 13, 2023
@cjnolet
Copy link
Member

cjnolet commented Jan 13, 2023

@achirkin got it! No rush for sure

@achirkin achirkin added 5 - Ready to Merge and removed 5 - DO NOT MERGE Hold off on merging; see PR for details 2 - In Progress Currenty a work in progress labels Jan 13, 2023
@achirkin
Copy link
Contributor Author

Test failures to be expected until #1141 is merged

@codecov-commenter
Copy link

codecov-commenter commented Jan 13, 2023

Codecov Report

Base: 87.99% // Head: 87.99% // No change to project coverage 👍

Coverage data is based on head (72d852c) compared to base (36b315d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@              Coverage Diff              @@
##           branch-23.02    #1135   +/-   ##
=============================================
  Coverage         87.99%   87.99%           
=============================================
  Files                21       21           
  Lines               483      483           
=============================================
  Hits                425      425           
  Misses               58       58           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@cjnolet
Copy link
Member

cjnolet commented Jan 14, 2023

/merge

@rapids-bot rapids-bot bot merged commit 2af2749 into rapidsai:branch-23.02 Jan 14, 2023
rapids-bot bot pushed a commit that referenced this pull request Jan 23, 2023
In #1135, we adjusted the min_recall values to report if any regressions happen in ivf-pq. However, `eval_neighbours` function, which is used in several ANN test suites, doesn't fail unless the regression is really large (it prints a warning if the calculated recall is "slightly" smaller than the expected recall).
In this PR, I make `eval_neighbours` always fail if the calculated recall is smaller than the expected recall. Slightly adjust the tests and do a small refactoring along the way.

Authors:
  - Artem M. Chirkin (https://github.com/achirkin)
  - Corey J. Nolet (https://github.com/cjnolet)

Approvers:
  - Tamas Bela Feher (https://github.com/tfeher)

URL: #1156
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 - Ready to Merge cpp improvement Improvement / enhancement to an existing function non-breaking Non-breaking change
Projects
Development

Successfully merging this pull request may close these issues.

3 participants