It was the one on the wiki page.
Ka Ming
From: Peter Cock [p.j.a.c...@googlemail.com]
Sent: July 29, 2011 2:42 AM
To: Ka Ming Nip
Cc: Edward Kirton; galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] Job output not returned from cluster
On Fri, Jul 29
Hi Shantanu,
I am also using a SGE cluster and the DRMAA runner for my Galaxy install. I am
also having the same issue for jobs that were killed.
How did you define the run-time or memory/runtime configurations in your DRMAA
URLs?
I had to add -w n in the DRMAA URLs in order for my jobs to be
From: ambarish biswas [ambarishbis...@gmail.com]
Sent: July 27, 2011 4:18 PM
To: Ka Ming Nip
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] DRMAA options for SGE
Hi Ming,
just an idea, -w n might be hiding the error reporting. Is your jobs
getting
My jobs have this problem when the command for the tool is wrapped by the
stderr wrapper script.
Ka Ming
From: galaxy-dev-boun...@lists.bx.psu.edu [galaxy-dev-boun...@lists.bx.psu.edu]
On Behalf Of Edward Kirton [eskir...@lbl.gov]
Sent: July 28, 2011
From: galaxy-dev-boun...@lists.bx.psu.edu [galaxy-dev-boun...@lists.bx.psu.edu]
On Behalf Of Ka Ming Nip [km...@bcgsc.ca]
Sent: July 26, 2011 10:39 AM
To: galaxy-dev@lists.bx.psu.edu
Subject: [galaxy-dev] DRMAA options for SGE
Hi,
I am trying to configure the proper memory resource
Hi,
I am trying to configure the proper memory resource requests for my Galaxy tool.
This is what I have under the tool_runners section of universe_wsgi.ini
[galaxy:tool_runners]
...
mytoolname = drmaa://-l mem_free=1G -l mem_token=1G -l h_vmem=1G/
...
When I execute my tool on Galaxy, I get
