How would this be different then the third option you listed? You want it to work with all tools and you as the developer want to be able to construct these files without needing a dummy tool to produce the values? How would imagine these setting files would be disseminated to users and then selected by users? -John On Thu, Oct 9, 2014 at 9:34 AM, Lukasse, Pieter <pieter.lukasse@wur.nl> wrote:
Hi,
Do we have a way (or plans) for sharing tool parameter settings in Galaxy?
I know the following workarounds :
· Share a history with all users: so users can import your step and do “rerun” to run on their own file with your settings
· Wrap the step in a workflow with all parameters set and publish this workflow: users can run this “workflow”
· Have a dummy tool to produce a settings file and allow the users to choose this file when running the real tool
· Use a conditional and many macros that are basically a copy of each other, only differing in the parameter values
But what I would like to have is a way to define bindings between a settings file and the parameters in the tool form. Any plans, ideas?
Thanks,
Pieter Lukasse
Wageningen UR, Plant Research International
Department of Bioinformatics (Bioscience)
Wageningen Campus, Building 107, Droevendaalsesteeg 1, 6708 PB, Wageningen, the Netherlands
T: +31-317481122; M: +31-628189540; skype: pieter.lukasse.wur
___________________________________________________________ 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, please use the interface at: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/