Re: [galaxy-dev] Running a workflow programatically

2011-03-02 Thread Darren Brown
Hello Dannon, That is surprising and excellent! Can't wait to hear more. Take care, Darren On Wed, Mar 2, 2011 at 11:38 AM, Dannon Baker wrote: > Darren, > > While this is not currently possible, I'm currently finishing up a first pass > on a workflow API that will allow this sort of interac

Re: [galaxy-dev] Running a workflow programatically

2011-03-02 Thread Dannon Baker
Darren, While this is not currently possible, I'm currently finishing up a first pass on a workflow API that will allow this sort of interaction and hope to have an early version available by the end of this week. I can update you when that has been committed. -Dannon On Feb 24, 2011, at 9:2

Re: [galaxy-dev] RPM repository for NGS tools in Galaxy

2011-03-02 Thread James Taylor
Hi Leon, Thanks for sharing this with the community! As far as similar activities, we are actively working on a solution for packaging and deploying tools. Enis can share more about that, it is what we use already to automatically build our cloud images with all tools and data installed. Impo

[galaxy-dev] RPM repository for NGS tools in Galaxy

2011-03-02 Thread Leon Mei
Dear colleagues, In order to ease administration on our servers running at VIB and NBIC, we will set up an RPM Repository for bioinformatics tools, the primary focus being NGS tools. The purpose is to come to a stable repository of easily installable packages for the common bioinformatics tools th

Re: [galaxy-dev] Shared a value for multiple set-at-runtime workflow parameters

2011-03-02 Thread Dannon Baker
On Mar 2, 2011, at 11:05 AM, Peter Cock wrote: > On Wed, Mar 2, 2011 at 3:42 PM, Peter Cock wrote: >> >> P.S. I do like the color highlighting and live substitution of >> the workflow parameters into each tool step that uses them. >> Very slick! >> > > That was the good news. Now the bad news

Re: [galaxy-dev] Shared a value for multiple set-at-runtime workflow parameters

2011-03-02 Thread Peter Cock
On Wed, Mar 2, 2011 at 3:42 PM, Peter Cock wrote: > > P.S. I do like the color highlighting and live substitution of > the workflow parameters into each tool step that uses them. > Very slick! > That was the good news. Now the bad news - two bug reports. Firstly if you clear the workflow paramet

Re: [galaxy-dev] Shared a value for multiple set-at-runtime workflow parameters

2011-03-02 Thread Peter Cock
On Wed, Mar 2, 2011 at 3:21 PM, Peter Cock wrote: > On Wed, Mar 2, 2011 at 2:51 PM, Dannon Baker wrote: >> Peter- >> >> Just a quick response to your first question-  you might want to give >> the workflow parameters feature a shot to see if it does what you're >> looking to do.  Within the workf

Re: [galaxy-dev] Shared a value for multiple set-at-runtime workflow parameters

2011-03-02 Thread Peter Cock
On Wed, Mar 2, 2011 at 2:51 PM, Dannon Baker wrote: > Peter- > > Just a quick response to your first question-  you might want to give > the workflow parameters feature a shot to see if it does what you're > looking to do.  Within the workflow editor, instead of setting a value to > 'specify at ru

Re: [galaxy-dev] Shared a value for multiple set-at-runtime workflow parameters

2011-03-02 Thread Dannon Baker
Peter- Just a quick response to your first question- you might want to give the workflow parameters feature a shot to see if it does what you're looking to do. Within the workflow editor, instead of setting a value to 'specify at runtime', use a variable tag in the format ${yourvariablename}.

[galaxy-dev] Shared a value for multiple set-at-runtime workflow parameters

2011-03-02 Thread Peter Cock
Hi all, I have a multi-step workflow where I've marked some parameters to be set at run time (in this case, a minimum read length, used in two different workflow steps). I want to use the same parameter value in multiple tools, rather than give the user one prompt for each tool. Is this possible?

Re: [galaxy-dev] Hiding a tool via tool_conf.xml

2011-03-02 Thread Peter Cock
On Thu, Feb 10, 2011 at 5:58 PM, Peter Cock wrote: > Hi all, > > I'm aware that in an individual tool's XML wrapper you can add > hidden="true" to the element to hide the tool from the > listing shown in Galaxy's left hand panel (but the tool is still > loaded and can be called by old workflows e