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

Progress can be slow in repetitive regions #14

Closed
dancooke opened this issue Nov 12, 2017 · 1 comment
Closed

Progress can be slow in repetitive regions #14

dancooke opened this issue Nov 12, 2017 · 1 comment
Assignees

Comments

@dancooke
Copy link
Member

Progress can be very slow in repetitive regions with mipmapped reads as many candidates are proposed. Often these regions are eventually skipped as there are too many possible haplotypes. The problem is especially bad for somatic and de novo calling where hours can be spent in a small region (< 1Kb). There is currently some logic in place to help avoid spending too much time in these regions, namely candidate generation masking, and disabling haplotype lagging in regions with too many candidates, but clearly these measures are not sufficient. We need a new approach to help detect these regions with high specificity.

@dancooke
Copy link
Member Author

This is no longer such an issue in general, especially since 453c4ab. Somatic calling can still be slow in these types of regions (and quite slow in general), however this is more of a result of the tumour model in particular.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant