Open Masterxilo opened 2 years ago
Usually, Segmentation fault
error require carefully running the data in a debugger (such as gdb
, valgrind
): would it be possible for you to send use the alignment file so that a C/C++ dev could try it?
Also:
Warning: 45.4% of the read pairs were discarded because the sequence is too short. The flag "--min_length" can be used to configure the minimum length. This seems a bit heigh, though I'm not that experienced with predicthaplo (@kpj : do you have any feedback?)
What is your current experimental setup? How were your reads generated? (is it assymetric read pairs ? e.g. a MiSeq that has 300bp on Read1 and 200bp on Read2)
Hi Ivan/@DrYak, nice to hear from you.
As the data originates from a virus mix and not a patient, that should be no problem. I sent you a download link along with a Dockerfile that reproduces exactly the way I invoke it.
As for how the reads where generated I don't know specifics. I have included links to the raw fastq files as well. I guess our read lengths are symmetric, the technique used is 2x250bp, so I guess they are all the same length. Lisa: Can you comment on that?
It is worth noting that on the same samples we got #27 when we produced the .bam file using https://github.com/medvir/SmaltAlign
This .bam file was produced with a pipeline by Sandra that apparently uses bwa.
Hi there
since apparently our other .bam file seems to contain only unpaired reads (#27), we now started with a .bam file produced by a different processing pipeline from our NGS data.
Now we get a bit farther, but still predicthaplo errors out in the end
Does this tell you anything?
I am running this on a fairly powerful computer with 64 GB RAM, so I don't think it crashes for out of memory reasons.