What allele frequency threshold do you recommend?
0
1
Entering edit mode
7.5 years ago
agata88 ▴ 870

Hi all!

I have a result from Varscan mpileup2snp and mpilepu2indel with default parameters including variant allele frequency =0.01 (1%). (--min-var-freq)

I am wondering, what is the recommendation for allele frequency threshold? This 1% looks very low and creates results with unwanted records.

Thanks in advance!

Best,

Agata

varscan • 4.2k views
ADD COMMENT
0
Entering edit mode

Is this for somatic or germline variants in a diploid organism?

ADD REPLY
0
Entering edit mode

Its germline, human.

ADD REPLY
1
Entering edit mode

So theoretically the variant frequency for a heterozygous variant would be ~50%, right? Then indeed 1% is very unlikely. Obviously it will rarely be exactly 50%, but with sufficient coverage it should be quite close to that. It's a trade-off between sensitivity and specificity, but I don't think it's unreasonable to expect at least 25%.

ADD REPLY
0
Entering edit mode

Thanks, I agree, especially when we have probe, WES and WGS sequencing where the de-duplication should be performed. I thought that maybe even higher in this situation, 35%?. In primer targeted sequencing (multipleks) I think it should stay 1%, do you agree?

ADD REPLY
0
Entering edit mode

I thought that maybe even higher in this situation, 35%?

You can indeed be more stringent and as such reduce false positives but you'll miss variants which are by chance only represented in 34% of the reads. It's a trade-off.

In primer targeted sequencing (multipleks) I think it should stay 1%, do you agree?

Multiplex PCR-based target enrichment prior to NGS? I think you'll commonly get high coverage there and can be more stringent. Unless you have SNPs in your primer I don't think you should expect a divergent frequency of variant alleles.

ADD REPLY

Login before adding your answer.

Traffic: 1255 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6