Tweet
No, I didn't make any modifications.
-
-
Getting the same error
Hi ,
I am getting the exact error of
[bwa_aln_core] calculate SA coordinate... Segmentation faultComment
-
I am getting the same error, any new ideas???
bwa aln Mito.fa TpNoDotStd.fastq > alnTpNoDotStd.sai
[bwa_aln] 17bp reads: max_diff = 2
[bwa_aln] 38bp reads: max_diff = 3
[bwa_aln] 64bp reads: max_diff = 4
[bwa_aln] 93bp reads: max_diff = 5
[bwa_aln] 124bp reads: max_diff = 6
[bwa_aln] 157bp reads: max_diff = 7
[bwa_aln] 190bp reads: max_diff = 8
[bwa_aln] 225bp reads: max_diff = 9
[bwa_aln_core] calculate SA coordinate... 3.00 sec
[bwa_aln_core] write to the disk... 0.01 sec
[bwa_aln_core] 262144 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 3.00 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 524288 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 3.01 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 786432 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 2.96 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 1048576 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 2.97 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 1310720 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 2.99 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 1572864 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 2.98 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 1835008 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 2.99 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 2097152 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... 2.98 sec
[bwa_aln_core] write to the disk... 0.02 sec
[bwa_aln_core] 2359296 sequences have been processed.
[bwa_aln_core] calculate SA coordinate... zsh: segmentation fault bwa aln MitoNC_012920.fa TeopNoDotStd.fastq > alnTeopNoDotStd.saiComment
-
Hi,
i get seg fault like this one in my bwa-0.6.1-r104:
------------------
[bwa_aln_core] refine gapped alignments... sh: line 1: 12337 Segmentation fault
-------------------
It happens when i modify the '-l' switch. When i set it to something below 19 is produces the error. I got it when aligning SOLID reads.
Should i rebuild bwa as per dp05yk suggestion(modify line 82 of bwtaln.c
? Any ideas are appreciated.
thank you.Comment
-
Hi again,
just rebuild bwa as suggested but got the same error.
Now im out of ideas and i have to stick to -l 19 or larger.Comment
-
Yesterday found that BWA-0.6.1 cant be used for SOLID as color space is switched off. Not nice. Now using 0.5.9 and waiting for the new version where all will be all right for SOLID again.Comment
-
We had a problem with seg faults after switching to bwa (0.6.1).
It appears that the problem can be fixed by re-indexing the genomes with new bwa.
Has anyone else seen this?Comment
-
Yes, the index structure is new. Unfortunately, the indexes do not have a header with a versioning scheme, so seg faults would be expected.Originally posted by GenoMax View PostComment
-
I asked my sys admin to update without looking at release notes.
This is going to trip some folks like me who do not always read release notes (for minor version revisions at least).
Originally posted by nilshomer View PostComment
-
Got this error when my machine didn't have enough free memory.
Hope this helps someoneComment
-
Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.Today, 11:43 AM
-
I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.
Here are nine questions we think about, in roughly the order they matter, before... -
Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.
The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
...06-02-2026, 10:05 AM
Comment