Hi, I have two problems and I hope you can help me.
The first one is, I can't download a package within the tool-dependency
description, because our company uses a proxy.
How can I define using a proxy in the "tool_dependencies.xml" file?
The second one is, I try to run functional tests in our t
Hi Everyone
I was recently trying to update tools that I installed from the central tool
shed. However, it seems that a temporary redirect on the central tool shed
server is causing my galaxy installation to throw a stack trace. Anyone else
encountered this? Thanks in advance.
URL:
http://
Il giorno gio, 02/10/2014 alle 16.50 -0700, Dooley, Damion ha scritto:
> I see Galaxy API has a feature to import a history dataset into the
> library (in copy_hda_to_ldda() fn from GCC2013 training day course).
> Is this available as well via Bioblend? Latest docs don't seem to
> include this feat
Hi Khalid,
I'd suggest you to open a Trello card for this:
http://galaxyproject.org/trello/
Best,
Nicola
Il giorno ven, 03/10/2014 alle 17.30 +, Alam, Khalid K. (MU-Student)
ha scritto:
> Hi;
>
> I’m getting ready to submit several (5) tools for processing data
> related to combinatorial s
It would be great to have someone from the Galaxy community involved in
this reproducible science hack-a-thon, as Galaxy is such a positive
contribution to workflows in reproducible science.
==
Reproducible Science Hackathon:
Curriculum & Workflow D
Hi all,
I'm developing some tools on my Galaxy instance and I need to get some
information about the job that a tool creates.
The question is, how can I have a job_wrapper object in my tool wrapper? I
tried to use the reserved variable $__app__, but I got errors.
I couldn't import and use the gal
Hello,
I installed clustalomega from the galaxy main toolshed using the admin
interface of our local galaxy install. When I run the tool, I get this
message:
Dataset generation errors
Dataset 55: co_alignment.fasta
Tool execution generated the follow
Tell us what you are trying to do and maybe someone might know the way to solve
it. It could be easier, the same, or more difficult than you imagined.
Iyad Kandalaft
Bioinformatics Programmer
Microbial Biodiversity Bioinformatics
Science & Technology Branch
Agriculture & Agri-Food Canada
iyad.ka
Yes - I am with Iyad - having more context would probably help :). You
can inject job_wrapper related stuff into tool execution in a very
round about way perhaps by creating a dynamic job destination that
consumes the job_wrapper and then creates a job destination with
enviornment variables set to
