Samtools mpileup: AF1 and DP4 not provided
1
0
Entering edit mode
4.0 years ago

Hello!

I'm using this command line:

and the resulting VCF lines look pretty much like this:

which is different from a "typical" VCF line (example taken from the internet):

chr10 3360 . T C 103 . DP=31;AF1=0.5;CI95=0.5,0.5;DP4=6,3,13,9;MQ=20;FQ=27;PV4=1,0.13,1,0.015 GT:PL:GQ 0/1:133,0,54:57

In particular I was interested in the AF1 and DP4 information which is not provided.

Any ideas?

samtools mpileup AF1 INFO • 1.8k views
0
Entering edit mode
4.0 years ago

I run samtools mpileup and then pipe it into bcftools call, which produces AF1 and DP4 each and every time.

Try running it like this (or modify this slightly to suit your needs):

samtools mpileup --redo-BAQ --min-BQ 30 --per-sample-mF \
--output-tags DP,AD -f GENOME.fasta --BCF My.bam | \
bcftools call --multiallelic-caller --variants-only -Ov > My.bcf


Kevin

0
Entering edit mode

Hi!

Thanks a lot, unfortunately it still doesn't provide such information. Is it possible that it is because I generated a VCF with samtools mpileup instead of a BCF like you did? That doesn't actually make sense to me, but it seems to be the only difference in the pipeline.

0
Entering edit mode

For DNA-seq, I do the alignment with bwa and then it's just a series of samtools and Picard commands before I reach the final variant calling step. Which aligner did you use?

0
Entering edit mode

I was using .bam files from Genome In A Bottle project, i belive they are aligned with novalign. I just tried also with TCGA samples that are aligned with BWA (if I am correct) and these are the results:

now I can see the DP4 value, but still AF1 is missing.

0
Entering edit mode

It may be related to program versions, in that case.

I use bwa-0.7.12 (bwa mem), samtools-1.3.1, and bcftools-1.3.1