Typical % of unmapped reads to genome contigs assembled from the same library?
0
0
Entering edit mode
6.5 years ago
johnnytam100 ▴ 110

I have an Illumina 150bp whole-genome library of a plant species (genome size ~7.5Gb), using the library I :

1) assembled genome contigs (using SPades, SOAP and platanus)

and

2) map the same library to the contigs from 1) using bwa mem

I discover, using splitsam.sh from BBMap to give me the total no. of reads, no. of mapped reads and no. of unmapped reads, the % of unmapped reads in the total no. of reads ranged from 50-90%.

While I am surprised with the high percentage of unmapped reads, I am wondering what is typical % of unmapped reads to genome contigs, particularly for plant genome if possible.

Thank you very much!

bwa mapping Assembly • 1.7k views
ADD COMMENT
0
Entering edit mode

What was the percentage of reads that were aligned with bwa mem? That should have told you how many reads did not align. If you are not getting good alignments of original reads to the assembly them it is possible that the assembly may be incorrect.

You could use bbmap.sh to map the reads and the stats file should give you a clear idea of how many reads are mapping.

ADD REPLY
0
Entering edit mode

I used samtools flagstat .bam for mapping results of the contigs from SPades and gave me the following output :

10083388 + 0 in total (QC-passed reads + QC-failed reads)
0 + 0 secondary
0 + 0 supplementary
0 + 0 duplicates
1665199 + 0 mapped (16.51% : N/A)
0 + 0 paired in sequencing
0 + 0 read1
0 + 0 read2
0 + 0 properly paired (N/A : N/A)
0 + 0 with itself and mate mapped
0 + 0 singletons (N/A : N/A)
0 + 0 with mate mapped to a different chr
0 + 0 with mate mapped to a different chr (mapQ>=5)

Only 16.51% (which is agreed using splitsam.sh) of total reads were mapped... I believe it is a too little?

ADD REPLY

Login before adding your answer.

Traffic: 3095 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