-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault #4
Comments
I can report the very same for the yeast genome ... Reads used: SRR5989373 . Have you been able to resolve the issue? If I call it with |
Hi @ydLiu-HIT , which reference were you using? Could you send the link or share it? Thanks |
Hi @jmaricb since I got a very similar problem, maybe you could use my case instead: I used the reads from SRR5989373 together with the ensembl 94 release: ftp://ftp.ensembl.org/pub/release-94/gtf/saccharomyces_cerevisiae/Saccharomyces_cerevisiae.R64-1-1.94.gtf.gz ftp://ftp.ensembl.org/pub/release-94/fasta/saccharomyces_cerevisiae/dna/Saccharomyces_cerevisiae.R64-1-1.dna_sm.toplevel.fa.gz Thanks for looking into this! |
Ensembl genome with version 92 of GRCm38. link: ftp://ftp.ensembl.org/pub/release-92/fasta/mus_musculus/dna/Mus_musculus.GRCm38.dna.primary_assembly.fa.gz |
@mjoppich @ydLiu-HIT I have located this segmentation fault. It was happening in the ksw2 aligner which would crash for very big references or very big queries. I have added this exception and tried it with this dataset that you linked: https://www.ncbi.nlm.nih.gov/sra/?term=SRR6238555 |
Hi jmaricb: I just re-run GraphMap2(v0.6.3) with the same read and reference as before, but it still gets as segmentation fault as follow: [11:54:03 BuildIndexes] Loading reference sequences. [1]+ Segmentation fault (core dumped) ~/software/graphmap2/bin/Linux-x64/graphmap2 align -x rnaseq -r /data/ydliu/Reference/mouse_GRCm38.fa -d /data2/ydliu/ONT_reads/SMRT/mouse/SRR6238555.fasta -o mouse_graphmap2.sam -t 24 |
The reference I was using: https://drive.google.com/file/d/1OwfUcsJ8iqvuKOR0UJpb1PYRYCl1pLbN/view?usp=sharing |
I am looking into this right now, again. As I can see from your comment the tool crashed right after loading reads into the memory, before aligning single read, right? Right not that doesn't happen for me. It aligns reads slowly, but it hasn't crash yet. I will try to see what happens and will let you know. |
Hi!
Recently, I was doing a benchmark for the performance of long spliced reads aligners(minimap2, GMAP, GraphMap2 and deSALT), but when I was running graphmap2 (v.0.6.01) on mouse pacbio SMRT reads and got a segmentation fault when 2.66% reads have been processed using 24 threads, shown in the screenshot:
The source of reads which I used can be found in https://www.ncbi.nlm.nih.gov/sra/?term=SRR6238555
How can I prevent segmentation faults?
thanks
Michael
The text was updated successfully, but these errors were encountered: