Handle undefined correction factors
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the fp_correction function and reproduce the h=2, fpr=0.1 case, where the correction collapses around 355 TB and yields inf. Handle this undefined result by using a high f_h value so splitting is discouraged, then verify the problematic parameter combinations no longer cause incorrect behavior.
Written by the indexing model from the issue text.
Description
For certain combinations of parameters, the fp_correction will yield inf.
E.g. for h=2, fpr=0.1, the function collapses at around 355 TB: WolframAlpha Plot
Idea:
- Set
f_hto a high number to discourage splitting (infis actually a high number :))
- Dominant language
- C++
- Stars
- 10
- Forks
- 11
- Avg merge
- 6h 46m
- Merged PRs (30d)
- 7
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.
More from seqan/chopper
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·