The BLAST+ binaries support multi-threaded operation, which is handled
via the $GALAXY_SLOTS environment variable. This should be set
automatically by Galaxy via your job runner settings, which allows you to
(for example) allocate four cores to each BLAST job.
In addition, the BLAST+ wrappers
Thanks Dannon for the reference. I checked out the tool and installed from
toolshed on my local Galaxy instance. I also checked out the related paper
which refers that the Blast executables run in parallel by partitioning the
input files into fragments and running batches in parallel. That sounds
Thanks Dannon for the reference. I checked out the tool and installed from
toolshed on my local Galaxy instance. I also checked out the related paper
which refers that the Blast executables run in parallel by partitioning the
input files into fragments and running batches in parallel. That sounds
Hi John, Alex, All,
Elaborating on the motivation behind my question of running tools within
tool. First, running a tool in parallel at large-scale. For example, if I
need to find a pattern from 1000 files via Galaxy Select tool from Text and
Filter tool-group, I am limited by providing one file
Galaxy has an API that is capable of running tools - certainly this is
one path forward on something like this. I am not sure it is the best
path forward though. Probably the best way to enhance Galaxy's
execution capabilities is to extend the Galaxy core framework itself -
this has its own
wishes,
Alex
-Oorspronkelijk bericht-
Van: galaxy-dev-boun...@lists.bx.psu.edu
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] Namens John Chilton
Verzonden: woensdag 5 februari 2014 22:54
Aan: Ketan Maheshwari
CC: galaxy-dev@lists.bx.psu.edu
Onderwerp: Re: [galaxy-dev] running tools within
