You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: