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

Variants below min_coverage still being called #262

Closed
mproberts99 opened this issue Jan 19, 2024 · 3 comments
Closed

Variants below min_coverage still being called #262

mproberts99 opened this issue Jan 19, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@mproberts99
Copy link

Hi,

I have set the min_coverage parameter to 10, but am still observing calls with read counts below that number in the final VCF. When I up the parameter to 20, then I see those have disappeared. Is there a range around the min_coverage that Clair3 still allows that would explain the presence of these calls? I have attached the VCF and the log.
run_clair3.log
merge_output.vcf.gz

@zhengzhenxian
Copy link
Collaborator

zhengzhenxian commented Jan 22, 2024

Hi, @mproberts99,

Thanks for the log. Seem all low-coverage variants were reported by the full-alignment model. We will check and get back to you soon.

@aquaskyline
Copy link
Member

Hi, @mproberts99, sorry for the late response, we have checked and confirmed it is a problem in our code. The problem doesn't affect the correctness of each variant but allows some variants below the minimum coverage to be outputted. We will solve the problem in the next update, but before that, a hard filter on DP after calling could also solve the problem.

@aquaskyline aquaskyline added the bug Something isn't working label Feb 21, 2024
@aquaskyline
Copy link
Member

Fixed in v1.0.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants