-
Notifications
You must be signed in to change notification settings - Fork 25
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
Error: kallisto index file not found kallisto_index #13
Comments
For me it worked with this Conda-environment:
However, I also performed the computations on a cluster, and the process was there always killed with cryptic messages. Finally I figured out, that a significant amount of RAM is needed for this process (I suspect Kallisto to be the origin of that problem). Thus, for me dedicating enough memory to the function call was the key! (2 GBs were not enough, but 8 GBs worked out fine.) |
Hello @wbvguo . I'm currently facing the exact same issue. Were you able to solve it? |
Hi @adinanadeem, I did not try to solve it. |
I had a similar issue, still due to pandas but it did not seem to be the in the kallisto index: Traceback (most recent call last): |
Hello, I tried to get this tool running but encounter an issue. The following are the code and error messages that I got:
Code:
check_strandedness --gtf ref/Mus_musculus.GRCm38.93.gtf --transcripts ref/Mus_musculus.GRCm38.cdna.all.fa --reads_1 reads/test_R1.fastq.gz --reads_2 reads/test_R2.fastq.gz
Output error:
can you provide some suggestions for solving this issue?
The software version on my side is:
how-are-we-stranded-here 1.0.1
rseqc 4.0.0
kallisto 0.48.0
python 3.10.5
also tested for kallisto 0.44.0 and python 3.7.7, with the same issue
The text was updated successfully, but these errors were encountered: