Sorry for bumping this, but it seems like such a standard boilerplate step of
installing a tool that someone muts know how.
-Joel
I installed the?bedtools tool from the public toolshed to my galaxy cluster.
The jobs were failing because I hadn't installed the required binaries:
? ?An
Date: Mon, 5 Nov 2012 17:44:49 +
Subject: Re: [galaxy-dev] Where should I put a tool's required binaries?
From: p.j.a.c...@googlemail.com
To: thisisj...@hotmail.com
CC: galaxy-dev@lists.bx.psu.edu
On Mon, Nov 5, 2012 at 5:34 PM, Joel Rosenberg thisisj...@hotmail.com wrote:
Sorry
Thanks, James. That page is exactly what I was looking for.
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists,
I installed the bedtools tool from the public toolshed to my galaxy cluster.
The jobs were failing because I hadn't installed the required binaries:
An error occurred running this job:
/opt/sge/default/spool/execd/ip-10-194-50-118/job_scripts/2: line 13:
genomeCoverageBed: command not
The galaxy webserver can solve this by allowing cross-domain resources from
whatever toolsheds have been configured.
http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
-Joel
___
Please keep all
(Apologies if this is in duplicate, Peter Cock may have forwarded it on after I
posted it to the user list)
So I'm trying to install the recently migrated ncbi_blast_plus tool from the
Tool Shed to my local galaxy instance running in EC2 and am getting errors at
the installation step.
After
Hello,
I've been learning about the tool shed, as precipitated by the decision to move
the blast tool out of the standard distribution.
(I'm having a problem doing so as documented here:
