Segmentation fault (core dumped)
iagooteroc opened this issue · 0 comments
iagooteroc commented
Hi. I'm using wtdbg2 2.5 in a linux cluster but I'm getting a Segmentation fault error before it finishes.
As input, I am using extracted fastq reads from a specific region of a bam file, like this:
samtools view -b -h ${INPUT_BAM} "chr5:15361335-19361335" > ${OUTPUT_BAM}
samtools fastq ${OUTPUT_BAM} > ${OUTPUT_FASTQ}
My wtdbg2 command looks like this:
wtdbg2 -x preset2 -R -L 200 -l 256 -e 1 -S 1 --rescue-low-cov-edges --node-len 256 --ctg-min-length 256 --ctg-min-nodes 1 -t ${THREADS} -i ${OUTPUT_FASTQ} -fo ${OUTDIR}
And the command output looks like this:
[Mon Sep 16 14:26:18 2024] loading reads
16900 reads
[Mon Sep 16 14:26:19 2024] filtering from 16900 reads (>=200 bp), 285548919 bp. Try selecting 200000000 bp
[Mon Sep 16 14:26:19 2024] Done, 6641 reads (>=200 bp), 200001280 bp, 781188 bins
[ ... ]
[Mon Sep 16 14:31:41 2024] output "assembly.ctg.dot.gz". Done.
[Mon Sep 16 14:31:41 2024] building contigs
[Mon Sep 16 14:31:41 2024] searched 939 contigs
[Mon Sep 16 14:31:41 2024] Estimated: TOT 4318976, CNT 925, AVG 4670, MAX 206592, N50 20736, L50 49, N90 1536, L90 375, Min 256
Segmentation fault (core dumped)
I tried with a couple of other regions and one of them worked fine, no idea why. Any clue of what's going on?
Full wtdbg2_output.txt. I could provide the input file but it's ~500MB.
Thank you.