The response to that was SVTyper could not find any paired-end, inward facing reads in the bam and that it was an alignment issue. If I do samtools stats on the file in question though:
then in amongst everything else I get:
SN raw total sequences: 127748452
SN reads paired: 127748452 # paired-end technology bit set
SN inward oriented pairs: 55933739
i.e this bam file contains only paired reads and ~80% of them are inward orientated. The initial command above runs fine if I omit this particular file, so it's something in the file that's causing it. I don't know what specifically to look at in the file to be able to identify the problem though.
The header of the sam file was requested in the other issue mentioned, so I've attached that in case it helps:
Trying to run svtyper on a vcf produced by lumpy, using the docker container found via: docker pull halllab/svtyper:v0.7.1-3c5218a
This looks the same as an error produced whilst attempting to diagnose another fault, detailed here: https://github.com/hall-lab/speedseq/issues/91
The response to that was SVTyper could not find any paired-end, inward facing reads in the bam and that it was an alignment issue. If I do samtools stats on the file in question though:
then in amongst everything else I get: SN raw total sequences: 127748452
SN reads paired: 127748452 # paired-end technology bit set SN inward oriented pairs: 55933739
i.e this bam file contains only paired reads and ~80% of them are inward orientated. The initial command above runs fine if I omit this particular file, so it's something in the file that's causing it. I don't know what specifically to look at in the file to be able to identify the problem though.
The header of the sam file was requested in the other issue mentioned, so I've attached that in case it helps:
trio3F15.bam.header.txt
Thanks Ben.