Bedtools - Errors in coveragedBed
Hi all.
I was running coverageBed with my exome bam file but it takes too long time and it hasn't returned output value.
Is it right that coverageBed takes much time to finish?
my bed file was very tiny so I thought that something might go in a wrong way.
below is my command and my bed file.
coverageBed -abam /DATA1/dmcb/TAR22_WES/TAR22S_sequence_readgroup_sort_dup_remove_realigned_recal.bam -b fgfr.bed -d > TAR22.cov.del.b36 10 123239372 123239472
1 answer
You might try this:
samtools view -u -L fgfr.bed myaln.bam \ | coverageBed -abam - -b fgfr.bed -d > out.bed
Which means: First get the reads overlapping your bed file, then do the counting.
With 20GB of bam file I'm not surprised coverageBed takes more then 10 min.
(By the way, the title of your post is misleading as there is no error reported in your question)
Log in to answer this question.
More posts like this
-
Use Bedtools to extract stranded read depth from BAM files
written by gtho123
-
ADTEx coverage issue
written by 2nelly
-
Question about number of reads within intervals
written by iraun
-
Calculating Exome Coverage
written by Coryza •
-
Get The Idea Of Splicing From Reads Mapped In Rna-Seq
written by antgomo •
-
Getting Number Of Reads In Intervals With Bedtools
written by user
-
Intersectbed/Coveragebed -Split Purify Exon?
written by Puriney
-
Intersectbed Tool Generating Empty File
written by bioinfo
-
Comparing And Plotting Coverage Between Two Bam Files
written by Rubal7
-
Reporting The Bam Reads Overlapping A Set Of Intervals With Bedtools
written by User 9996
How big is your bam file??
my bam file size is approximately 20G.
I thought that file B size was small that I expected it will take just less than 10 minutes.. but it is my mistake
therefore, how big is your fgfr.bed file? may it be restricting your output to that single region?
sharing a
samtools view input.bam | headplus ahead fgfr.bedoutputs would help.Related question: is there a tool that will do the same thing more quickly, possibly using an index for the bam file? After all, IGV can plot the coverage for a small region very quickly even for a large BAM file.
coverageBeddoes not only report coverage, but bins of coverage. if per base coverage is needed,samtools depth input.bamcan be used, and it's fairly fast (uplimited to 8000x though).