[BUG] RBC 3D shows 2-3 discrepancies only when whole gtest suite is executed
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 251
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
When the whole test_raft gtest suite is executed, there seem to be 2-3 discrepancies (out of 8000 samples) that pop up in the RBC 3D test when k is in the range [2, 5]. When running the RBC tests alone, compute-sanitizer isn't showing any errors.
It could be possible that this is exposing a larger issue (potentially numerical or correctness) in the landmark or data point filtering.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the discrepancy in the full test_raft gtest suite, then compare it with the standalone RBC tests for k in [2, 5]. Use compute-sanitizer while investigating the RBC 3D test and the suspected landmark or data point filtering paths. Done means the discrepancies are explained and the relevant tests run consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- machine-learning, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100