I need to split enormous bam files into smaller pieces, to parallelize haplotype calling. It's widely recommended in other posts to split these by chromosome. However, my files are so large (whole genomes at high coverage) that calling haplotypes on a single chromosome can still take more than a week.
I'd therefore like to split these further, e.g. split the chr1 bam file into 8 smaller 'chunks'. However, it's essential that the reads covering a particular region of a chromosome are distributed only in the same 'chunk', otherwise it would be impossible to accurately call the haplotype of that region. Can anyone suggest how I might split a bam file and ensure this?
I've tried using the 'split' function in alntools, which is intended to split bams "such that all the alignment of a same read appear only in a single chunk." However, the project is no longer actively maintained and there are dependency conflicts that mean it no longer works. Any suggestions would be much appreciated.
•
written
by
M9Q6Ixc31Fc8 •
1 answer
I need to split enormous bam files into smaller pieces, to parallelize haplotype calling
Indexed BAM supports random access so there no technical reason why you have to split the bam at all. Many good callers will be able to multi-thread the calling. Other callers will have a parameter to specify a region of interest and will only make calls in that region. In the case of the latter, you can just split your genome into X non-overlapping 'chunks' and start X instances of your caller, each configured with a different region of interest.
It's only if you caller supports neither of those scenarios that you will need to split your bam file, and even then, you could just use samtools to split your bam if you know the intervals. Splitting by chromosome is a very crude approach to multi-threading but there are still a number of callers out there that do take this approach.
Log in to answer this question.
-
Calling variants/SNP for single-cell RNA-seq data
written by QX •
-
Is it possible to run bayescan with a splitted chromosome?
written by mataman_lib •
-
Experience with BaseRecalibratorSpark and ApplyBQSRSpark
written by nhaus •
-
Best way to find intervals for parallelization of joint variant calling
written by William
-
HaplotypeCaller GVCF on one bam files
written by rayzghimire •
-
Best approach for parallelizing bwa mem over multiple CPUs
written by M9Q6Ixc31Fc8 •
-
Variant calling in genomic chunks
written by Damian Kao
-
Split a BAM within a chromosome without losing read pairs
written by Ian Fiddes
-
Implementing And Parsing Blast Search On Long Query
written by sorrywm •
-
Split Bam Files By Region For Parallel Variant Calling
written by William
You mean you want to make sure all chunks' reads are not overlapped (which means one alignment occurs in only on chunk), is there any other criteria?