Fastqc 0.67 errors while Fastqc 0.64 does not
When I run FastQC version 0.64 on a fastqsanger dataset I get results. However when I run FastQC version0.67 on the same dataset I get the following error:
Fatal error: Exit code 1 () /bin/sh: 1: fastqc: not found Traceback (most recent call last): File "/mnt/galaxy/shed_tools/toolshed.g2.bx.psu.edu/repos/devteam/fastqc/3a458e268066/fastqc/rgFastQC.py", line 166, in <module> fastqc_runner.run_fastqc().
Why?
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Galaxy StringTie error
written by trkfs •
-
Installing Galaxy
written by GA •
-
local galaxy error
written by arraychip •
-
StringTie error: list index out of range
written by nazaninhoseinkhan
-
LefSE input error
written by dazhudou1122
-
Tool: NCBI SRA Tools: "Extract reads in SAM or BAM format from NCBI SRA" is broken
written by Open Genomes •
-
mpileup (2.0) not working on local galaxy server
written by sharmavikas3529 •
-
Galaxy commits subprocess errors
written by kaji331 •
-
galaxy main tool shed "join" installation error
written by yu.1.wang •
-
Detecting Clusters Of Anomalously Mapped Pairs With Svdetect On Galaxy
written by antomarto84 •
FastQC is currently in v.0.11.5? Where in the future did you get 0.67 from?
I assume this is some other software (in v. 0.67) calling FastQC internally? It seems that FastQC is not in
$PATH. This appears to be a galaxy related error.version 0.67 is the version number that Galaxy supplies. I assume this is up to date in that Galaxay was just installed on my computer 3 weeks ago.
Please use
ADD REPLY/ADD COMMENTwhen responding to existing posts.Do you have FastQC installed on your computer? You could try adding that directory to $PATH and re-starting galaxy.
You may also want to post this question to Galaxy biostars in case this is not enough.
Just wondering whether you've managed to fix this issue, because I have the exact same problem and I'm stuck. Thanks!
I was no ever to fix the problem and so I just use the earlier version 0.67