Entering edit mode
16 months ago
MaxMin
▴
10
Hello everyone,
After installing InterProScan and placing Phobius, SignalP, and TMHMM in the folders required by InterPro, the following analyses still appear to be disabled:
Deactivated analyses:
SignalP_GRAM_NEGATIVE (4.1) : Analysis SignalP_GRAM_NEGATIVE is deactivated, because the resources expected at the following paths do not exist: bin/signalp/4.1/signalp
TMHMM (2.0c) : Analysis TMHMM is deactivated, because the resources expected at the following paths do not exist: bin/tmhmm/2.0c/decodeanhmm, data/tmhmm/2.0c/TMHMM2.0c.model
SignalP_EUK (4.1) : Analysis SignalP_EUK is deactivated, because the resources expected at the following paths do not exist: bin/signalp/4.1/signalp
Phobius (1.01) : Analysis Phobius is deactivated, because the resources expected at the following paths do not exist: bin/phobius/1.01/phobius.pl
SignalP_GRAM_POSITIVE (4.1) : Analysis SignalP_GRAM_POSITIVE is deactivated, because the resources expected at the following paths do not exist: bin/signalp/4.1/signalp
How can I solve this?
Can you show us the paths where you've placed these files please? (E.g., with
ls.)Sure,
Thank you.
signalp:mv interproscan-5.68-100.0/bin/signalp/4.1/signalp/* interproscan-5.68-100.0/bin/signalp/4.1/Should fix this one.
phobius:I am not sure why this one is malfunctional. Here is what my directory from an older (still functional) version of
interproscanlooks like forphobius:I think it's worth checking
phobius_install.txtand theREADMEto see if anything additional has to be done to activatephobius. If you haven't tried executingphobius.pldirectly, I'd try this also to see if and also. Executing it with--helpspecified should produce something like this:I cannot advise you regarding
tmhmmunfortunately as I do not have it available at hand. But I do remember it was a bit difficult to get running (some paths had to be changed within the main scripts if I recall). But the warnings produced byinterproscansimply indicate missing files. You could try copyingdecodeanhmm.Linux_x86_64asdecodeanhmmandTMHMM2.0.modelasTMHMM2.0c.modelwithin the2.0csubdirectory to see if this fixes the issue already.