Hi all,
I am working on a way to add/install tools to galaxy in a more automated way.
I need that for the galaxy-taverna interoperability work we are doing
(https://trac.nbic.nl/elabfactory/wiki/eGalaxy). The generator
produces a galaxy tool (.zip or an .xml + .rb) that I want to install
as
Hi Glen,
Good to know. I assume that currently that is not happening though,
right? If yes, is it in your immediate plans?
It should happen now - each step in the workflow would get submitted as a
separate job to the cluster. At that point it is up to the job scheduler and
not Galaxy to
Hi Glen,
All is clear now. Thanks for the info! :)
K.
the job should copy its output files into the Galaxy database/files directory
before it terminates. So assuming you are not using data staging and the
database directory is shared via NFS, then the next tool will read the files
from
