mmmmc...@gmail.com
unread,Dec 6, 2017, 10:39:28 AM12/6/17Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to deepTools
Hi all-
I have paired-end sequencing data, and I would like to generate bigwig files showing coverage (i.e. exact number of reads) at a given genomic location. I first generated these files using default settings:
bamCoverage -b file.bam -o out_file -of bigwig -bs 1
However, when I then looked at the resulting bigwig and compared them to the BAM files they were generated from in IGV, I noticed that the coverage was ONLY considering reads, and DID NOT consider the insert between mate pairs. I would like to include the insert between mate pairs as part of my coverage.
So, I made new bigwig coverage files using the extendRead option:
bamCoverage -b file.bam -o out_file -of bigwig -bs 1 -e
Now, when I look at the BAM file and the new bigwig file in IGV, the coverage numbers are different than the previous bigwigs produced using default settings. However, these numbers now appear to be inflated somehow. In some cases, they are double what the actual value should be.
My assumption was that the coverage file would now simply count inserts as an additional read. As an example, if I had a single base pair which was covered by two different paired ends and one insert, I would have expected a coverage value of 2 in the bigwig generated using default settings, and a coverage value of 3 in the new -extendRead bigwig. Am I misinterpreting the option? I can easily send screenshots, as well as the reports which were generated during the making of the files.