-
Notifications
You must be signed in to change notification settings - Fork 168
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
finding pseudoalignments for the reads ...Segmentation fault (core dumped) #105
Comments
What is the error reported? We fixed an issue in v0.42.5 which could be the cause of this. Can you run this on the latest versio 0.42.5 |
Kallisto version is 0.42.4 and this is the error message:
I will download v0.42.5 and try again. |
I tried with kallisto ver. 0.42.5 with the following command and the error still persists. Command:
Program halted with the following error:
|
In your case you seem to have only a single sequence in your index, can you confirm that this is what you expected? Can you run kallisto quant without the pseudobam, I'm just trying to isolate whether there is a problem with the pseudobam or other parts. can you also report what is written to stderr when you run your command as |
The index file has more than one sequence. I just reported the end of the stdout. This is the output of both stdout and stderr:
Also, "core.xxxx" file is written inside the working directory. |
The sequences you are aligning have the ending I'll have to check for this a bit more carefully when doing pseudoalignment. kallisto never uses the quality values so you can supply a dummy value, essentially converting the FASTA file to a FASTQ files. You can try this by just converting the first few sequences of the input file to FASTQ |
Yes.I confirmed that I will test with |
I also ran into a segfault when generating the pseudobam, but due to a slightly different problem . I was running kallisto using process substitution to deal with an interleaved paired end file kallisto quant -t 8 -i kallisto.idx -o my_sample --pseudobam <(seqtk seq -1 interleaved.fq) <(seqtk seq -2 interleaved.fq) Kallisto runs perfectly fine without the --pseudobam flag, but it crashes if I request the pseudobam. I figured the pseudobam needs re-reading the fastq files, so I tried doing the split beforehand and then the seg fault does not happen (runs fine). Would be nice to add this to the docs at least :). A nice would have also would be support for interleaved paired end files :) |
Hello, I face this problem: " [ bam] writing pseudoalignments to BAM format .. Segmentation fault" I run this pipeline: this is the outcome message: [quant] finding pseudoalignments for the reads ... done If anyone could help me out, it would be great! |
Any idea if this issue has been resolved yet. I am also getting something very similar:
|
So, personally, I went with STAR since I was not in a hurry, but someone in another post suggested going back to the older version that works. But frankly, I didn't try it. Also if I remember when I removed the "--pseudobam --genomebam --gtf genes.gtf" and run for example "kallisto quant -i index -o output --single -l 200 -s 20 file1.fastq.gz file2.fastq.gz file3.fastq.gz" it worked. Very good luck! |
keeps happening to me too in kallisto 0.46.2:
works when removing the |
When trying to get pesudobam file, it gives me the core-dump error.
Machine is Ubuntu server with x86-64 architecture.
The text was updated successfully, but these errors were encountered: