-
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 on Yeast Transcriptome #11
Comments
I'm looking into this now. Will let you know when I find the error. |
@mjoppich I have tried running the same command you did: and I didn't get segmentation fault. This is the .sam file it generated: https://www.dropbox.com/s/q6vsdbukzfanrue/SRR5989373_1.unmod.sam.gz Now, it could be something nondeterministic, I will try to see what could be wrong. If you have anything more useful for me let me know. |
Thanks for your help! I built graphmap2 with debug flags
Does that help you? |
Other question: which branch are you on? I am using the master branch (or whatever else is the default branch). |
I am using master branch, the default one. Thank you for the help, I can see that, when generating MD string in the alignment generation, the program tries to access the negative index in the array. Someone already reported similar issue, but on different place and it happened because his gtf file was not correct. Now, I also ran the program in gcd and I don't get segmentation fault, but some undefined behaviour obviously is happening. I will look into this MS string generation and I will make sure that it doesn't break. But, can you show me the stack trace you get in gdb when running without gtf file? and i get the error: ERROR: Duplicate chromosome name: chrchromosome |
The GTF file is downloaded from ensembl. I would guess they know how to make a GTF file ... The stacktrace for running without the gtf file:
Not having a GTF file and still getting the error in this very same location sounds like a more general problem instead of a GTF problem ;) The outfile remains empty btw ;) |
The generation of transcriptome from GTF file is not working. I have to fix that. But if you run the program without --gtf and with --rebuild-index (to overwrite the index generated with gtf file) it should work, ti does for me. |
Hi, as mentioned in my last post:
And indeed, I always run with --rebuild-index. The following call results in the above segfault (the one from 17:55:30):
Actually my feeling is that the problem lies in the |
Hi, yes I do, I run with -x rnaseq. I understand everything you are saying, but I don't know why you are getting segmentation fault when running without gtf and with --rebuild-index. Because, as I said, i don't get the segmentation fault in that case, both in debug and release. I used the reference and the dataset you provided in your first post mode and I the program finishes with the results I posted above. PS: It is true that you don't have to (or even shoudn't) run the program with -x rnaseq if you use gtf file because the generated index will not contain introns and then there is no need to use -x rnaseq. |
Hi, I am running graphmap2 on the following data:
Reads:
ftp://ftp.sra.ebi.ac.uk/vol1/fastq/SRR598/003/SRR5989373/SRR5989373_1.fastq.gz
Reference GTF:
ftp://ftp.ensembl.org/pub/release-94/gtf/saccharomyces_cerevisiae/Saccharomyces_cerevisiae.R64-1-1.94.gtf.gz
Reference:
ftp://ftp.ensembl.org/pub/release-94/fasta/saccharomyces_cerevisiae/dna/Saccharomyces_cerevisiae.R64-1-1.dna_sm.toplevel.fa.gz
Using v0.6.3 (git pull and built today) I still get Segmentation Faults:
I can also call graphmap2 in a different fashion:
/mnt/d/dev/git/graphmap2/bin/Linux-x64/graphmap2 align --rebuild-index -x rnaseq --gtf /home/mjoppich/dev/data/genomes/Saccharomyces_cerevisiae.R64-1-1.94.gtf --threads 8 -r /home/mjoppich/dev/data/genomes/Saccharomyces_cerevisiae.R64-1-1.dna_sm.toplevel.gm2.fa -d fastq/SRR5989373_1.fastq -o graphmap2/SRR5989373_1.unmod.sam
Then the segmentation fault occurs earlier:
I'd be more than happy if you could look into this issue. Given the few introns, the yeast genome might be useful for debugging :)
The text was updated successfully, but these errors were encountered: