Open mheskett opened 2 years ago
If I am not wrong its default behaviour is to merge bins of no coverage that is why you got bins of different length. To skip the those regions you could use --skipNAs
Hey thanks for the response @LeilyR . skipNAs wont help since i need all files across samples to have the same set of regions. Is there any way to force the binsize to remain the same, no merging, and report all regions with 0 coverage as well? If not I can just use BedTools against a set of genomic windows
Hey, Have you solved the problem? I have met the same problem I would much appreciated it if you could give any suggestions!
Yeah you need to use bedtools intersect with sliding windows instead (see bedtools make windows)
On Sat, Jul 9, 2022 at 8:34 AM Aannaw @.***> wrote:
Hey, Have you solved the problem? I have met the same problem I would much appreciated it if you could give any suggestions!
— Reply to this email directly, view it on GitHub https://github.com/deeptools/deepTools/issues/1144#issuecomment-1179562829, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACUDDNQ34QUWBV5ELJV7SODVTGLYVANCNFSM5ZAJLBFA . You are receiving this because you authored the thread.Message ID: @.***>
I'm calling bamcoverage on several bam files and specifying the binsize to 50,000. I expect every file to have identical coordinates (first three columns in bed file), otherwise I wont be able to compare them against each other. however after just a few lines I get variable bin sizes (between 50 and 300kb), and its different between to files that i paste together here