On Apr 9, 2013, at 1:38 AM, Joshua Orvis wrote:
It has been a while, but checking in again for any possible solution or
advice where to look here?
On Tue, Feb 26, 2013 at 10:06 AM, Joshua Orvis jor...@gmail.com wrote:
Thanks for your response. That seemed to work, to a point. I redid
It has been a while, but checking in again for any possible solution or
advice where to look here?
On Tue, Feb 26, 2013 at 10:06 AM, Joshua Orvis jor...@gmail.com wrote:
Thanks for your response. That seemed to work, to a point. I redid the
same FASTQ-FASTA conversion test and could see
Thanks for your response. That seemed to work, to a point. I redid the
same FASTQ-FASTA conversion test and could see using command-line
utilities that the job started on the grid (SGE is behind it.)
About 10 minutes have gone by though since the job stopped running on the
grid and the
I have a working local Galaxy instance and wanted to enable DRMAA support
to utilize our SGE (or LSF) grid. Following the guide
herehttp://wiki.galaxyproject.org/Admin/Config/Performance/Cluster I
set what I appeared to need to make this work. From the DRMAA_LIBRARY_PATH
env variable to all the
See if adding the default queue name to the job runner path - eg:
default_cluster_job_runner = drmaa:///default
works any better?
Galaxy will default to the local runner if it can't find the nominated
drmaa path AFAIK and I don't think 'default' is the default
:)
On Tue, Feb 26, 2013 at 4:51
