This is on a local install of Galaxy? The problem with the tool
sounds to be similar to the one you are having with trinity. The core
issue could be that the binary has not been installed. But first, you
set up the installation as a production server? And again, just to
sure, you are running the most current distribution?
Initial set up:
Then to set up as a "production server" (meaning, customize):
Some tool wrappers come with the Galaxy distribution, others you
from the Tool Shed. Of these, some tools (including many from a Tool
Shed repository) will manage the installation of dependencies like
binaries, but others require that you download and install the
underlying binary yourself (true for any in the distribution and some
the Tool Shed).
This is what the dependencies are and where to find them (when a tool
in the distribution, or was, check the Tool Shed repository if that is
where the tool is sourced from):
And this is how to incorporate it into your instance:
How to install tools from the Tool Shed:
This was a question that is a good fit for the email@example.com
mailing list as well, so if you need help with installation, please
a new question there. The more specific you are about what the problem
is, the easier it is for others to offer help (where in the
process you are having issues, etc.). Both velvet and trinity can be
resource intensive, so if you have trouble with them on a local
(run, but not enough resource - compute or memory), then moving to a
cloud may be a solution.
All Admin wiki docs are here:
And prior Q&A plus admin docs can be searched here:
(Both are linked from the wiki side bar under "Deploy Galaxy")
Hope this helps!