Pileup loosing consensus sequence?

MatthewVC · 05-25-2011, 02:58 PM

Hello,

I am doing a project involving re-sequencing mitochondrial genomes and am having some trouble with the SAM Tools pileup function in Galaxy.

Using Galaxy, I am mapping my Illumina reads onto a FASTA copy of the mitochondrial genome using BWA. This is to avoid my reads inappropriately being mapped onto the numerous places in the nuclear genome where fragments of the mitochondrial genome have integrated. This improves my coverage considerably (from roughly 50X when mapping reads to entire genome to 4000+ when mapping only to the mtDNA).

However, when I generate a pileup from the .bam file, the third column, which should have the consensus sequence, consists entirely of “N”s. This is preventing me from continuing with the bioinformatic analysis.

I wanted to see if anyone could offer any suggestions as to why my consensus sequence is lost.

Thanks,
Matt

MatthewVC · 05-25-2011, 03:08 PM

I figured it out a few minutes after posting this. I had used the "build in" reference genome when generating the pileup file instead of using the reference from my history that had also been used to map the reads. I guess I was too quick to post.

Matt

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Samtools pileup Consensus with 0.1.12a version	srividya	Bioinformatics	1	05-23-2011 08:16 AM
Why are there all these As in my consensus sequence: An issue with samtools pileup	dagarfield	Bioinformatics	3	02-03-2011 11:14 AM
Max Mapping / SNP / Consensus Quality in pileup files	agc	Bioinformatics	1	11-22-2010 07:42 AM
Getting pileup consensus from BAM files using Bio::DB::Sam	ragowthaman	Bioinformatics	2	08-03-2010 09:21 AM
gaps in consensus built from samtools pileup	culmen	Bioinformatics	2	07-21-2010 10:02 PM

05-25-2011, 02:58 PM	#1
MatthewVC Member Location: Alabama Join Date: Jun 2010 Posts: 11	Pileup loosing consensus sequence? Hello, I am doing a project involving re-sequencing mitochondrial genomes and am having some trouble with the SAM Tools pileup function in Galaxy. Using Galaxy, I am mapping my Illumina reads onto a FASTA copy of the mitochondrial genome using BWA. This is to avoid my reads inappropriately being mapped onto the numerous places in the nuclear genome where fragments of the mitochondrial genome have integrated. This improves my coverage considerably (from roughly 50X when mapping reads to entire genome to 4000+ when mapping only to the mtDNA). However, when I generate a pileup from the .bam file, the third column, which should have the consensus sequence, consists entirely of “N”s. This is preventing me from continuing with the bioinformatic analysis. I wanted to see if anyone could offer any suggestions as to why my consensus sequence is lost. Thanks, Matt

05-25-2011, 03:08 PM	#2
MatthewVC Member Location: Alabama Join Date: Jun 2010 Posts: 11	I figured it out a few minutes after posting this. I had used the "build in" reference genome when generating the pileup file instead of using the reference from my history that had also been used to map the reads. I guess I was too quick to post. Matt