Hi Neil,
I've only used this with my own tools, but basically it looks like:
command whatever_your_tool_has_now /dev/null /command
where /dev/null discards the output.
Best,
Wolfgang
On 31.05.2014 01:11, neil.burd...@csiro.au wrote:
Yes that would work. Can you supply an example if
Hi Neil,
I had some problems with this before too, so I created an tool config option a
long time ago in my own galaxy fork. Never really bothered with submitting it,
but it lives in these commits:
https://bitbucket.org/glormph/adapt/commits/4ba256a9b8782642429ecb5472a456584bed86d5
Hi Isabelle,
Not sure about specifying the absolute path for the tool dependency dir, but I
always use it. Also, my env.sh neither has a #!/bin/bash shebang line, nor
quote marks around the tool path.
If you are in the hhsuite/default/ dir and source env.sh, can you then run
hhblits yourself
