TestKnnVectorQuery.testScoreEuclidean fails
See original GitHub issueDescription
Reproducibly fails on main
branch.
Gradle command to reproduce
./gradlew test --tests TestKnnVectorQuery.testScoreEuclidean -Dtests.seed=1DAEE5C9217129EB -Dtests.nightly=true -Dtests.locale=mas -Dtests.timezone=Africa/Libreville -Dtests.asserts=true -Dtests.file.encoding=UTF-8
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
30 Questions to test a data scientist on K-Nearest Neighbors ...
1) [True or False] k-NN algorithm does more computation on test time rather than train time. A) TRUE B) FALSE. Solution: AThe training...
Read more >3. Baseline models & k-Nearest Neighbours
Looking at the test score we see that our model get's a slightly negative value, which means that it is doing a little...
Read more >KNN Numerical Example (hand computation) - Micro-PedSim
1. Determine parameter K = number of nearest neighbors · 2. Calculate the distance between the query-instance and all the training samples ·...
Read more >Understanding K-Nearest Neighbour Algorithm in Detail
Given a dataset with different classes, KNN tries to predict the correct class of test data by calculating the distance between the test...
Read more >K Nearest Neighbor : Step by Step Tutorial - ListenData
For any given problem, a small value of k will lead to a large variance in predictions. Alternatively, setting k to a large...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just backported to 9.x and 9_4 branches
I believe https://github.com/apache/lucene/commit/e69c48b8d941f44bb73f0594b5f72947efe80948 should fix. I guess LuceneTestCase.newIndexWriterConfig can randomly commit, or result in unusual configs anyway. I don’t think we want to forceMerge in this case because some of the test users of that method rely on document order.