[galaxy-dev] Suppress stdout in history item
Hi, Currently if there is anything written to stdout it is also shown in the expanded history item of the job (in the right hand history panel). Is there a way to suppress that? I searched for a possible solution but could not find anything. Thank you, Best regards, Hans van Leeuwen ___ 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/
Re: [galaxy-dev] Suppress stdout in history item
Hello Bjorn, Thank you for your response. Indeed, I do want to have the stdout, but I don't want it to show up in the history item. I will try the suggestion to print 10 empty lines at the beginning of stdout. Greetings, Hans On Mon, Mar 24, 2014 at 11:18 AM, Björn Grüning bjoern.gruen...@gmail.comwrote: Hi Hans, you can remove the entire stdout if you want, but that is probably not what you want. An other hack I can imagine is to insert 10 empty lines at the beginning of stdout. Ciao, Bjoern Am 24.03.2014 10:40, schrieb Hans van Leeuwen: Hi, Currently if there is anything written to stdout it is also shown in the expanded history item of the job (in the right hand history panel). Is there a way to suppress that? I searched for a possible solution but could not find anything. Thank you, Best regards, Hans van Leeuwen ___ 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/ ___ 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/
[galaxy-dev] dynamic_options selected value as input for second dynamic_options function call
Hello, I would like to have a tool form with a two parameters: 1. Select State 2. Select Town The options for 'Select State' are dynamically generated with dynamic_options which calls a python function, which connects to a database and returns the list of States. This works fine in my form xml code: param name = State_id type=select dynamic_options=getStates() label=Select State display=radio multiple=false Now I want to dynamically create the options for '2. Select Town'. To make this work I need to take the selected option from '1. Select State', pass it as an argument to a dynamic_options function call that would then connect to a database and retrieve the Towns for the provided State. These Towns would then be the options for '2. Select Town'. So, the second parameter '2. Select Town' should do something like this: param name = Town_id type=select dynamic_options=getTowns([user selected value in 1. Select State]) label=Select Town display=radio multiple=false The part in square brackets is pseudo code; this is the part that I cannot get to work . That part should also be automatically refreshed if the user changes the selection in '1. Select State'. I looked into the use of conditional but I don't see how I can use that if I don't know beforehand what values I can have (determined in real time based on content of database), so I cannot code the when tags. Any help is greatly appreciated. Thank you in advance, Hans ___ 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/
Re: [galaxy-dev] dynamic_options selected value as input for second dynamic_options function call
Hi, I found a working workaround using the deprecated page tags: inputs page param name = State_id type=select dynamic_options=getStates() label=Select State display=radio multiple=false/ /page page param name = Town_id type=select dynamic_options=getTowns(State_id) label=Select Town display=radio multiple=false/ /page /inputs This works; both select lists (on separate GUI pages) are dynamically generated when the called function connects to a database to retrieve the options. However, as it is recommended not to use page tags any longer, can anyone suggest how to write above example using condition and when tags instead? I have searched a lot but can't find out how to do it. Thank you, Hans ___ 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/
