Re: [galaxy-dev] value_label tool input param attribute doesn't work as documented
Hi again, Sorry had to check what exactly was not working, the value_label attribute appears to not work when trying to reference a label from a dynamic_options driven input parameter. regards, Leandro On Wed, Aug 24, 2011 at 7:23 PM, Kanwei Li kan...@gmail.com wrote: Hi Leandro, I tested this on my instance and the example you gave did give me the correct string: Human (hg18). Do you still have this problem? If so, can you provide an example where it still behaves incorrectly? Thanks, K On Thu, Jul 14, 2011 at 4:16 AM, Leandro Hermida soft...@leandrohermida.com wrote: Hi, Looking at the example on the Tool Config Syntax wiki page: Example Assume that the tool includes an input parameter named database which is a select list ( e.g., assume the following inputs ): Toggle line numbers 1 inputs 2 param format=tabular name=input type=data label=Input stuff/ 3 param type=select name=database label=Database 4 option value=alignseq.locHuman (hg18)/option 5 option value=faseq.locFly (dm3)/option 6 /param 7 /inputs Assume that the user selects the first option in the $database select list. Then the following will ensure that the tool produces a tabular data set whose associated history item has the label Blat on Human (hg18). Toggle line numbers 1 outputs 2 data format=input name=output label=Blat on ${database.value_label} / 3 /outputs It shows that .value_label attribute should produce the string in between the option tags, not the actual value. Why does this not work? When I use it it produces the value, or am I doing something wrong? regards, Leandro ___ 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/ ___ 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/
Re: [galaxy-dev] value_label tool input param attribute doesn't work as documented
Hi Leandro, I tested this on my instance and the example you gave did give me the correct string: Human (hg18). Do you still have this problem? If so, can you provide an example where it still behaves incorrectly? Thanks, K On Thu, Jul 14, 2011 at 4:16 AM, Leandro Hermida soft...@leandrohermida.com wrote: Hi, Looking at the example on the Tool Config Syntax wiki page: Example Assume that the tool includes an input parameter named database which is a select list ( e.g., assume the following inputs ): Toggle line numbershttp://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax# 1 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-4197fe3d76b4282c0f9aa2576fbdec6550c3174f_1 inputs 2 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-4197fe3d76b4282c0f9aa2576fbdec6550c3174f_2 param format=tabular name=input type=data label=Input stuff/ 3 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-4197fe3d76b4282c0f9aa2576fbdec6550c3174f_3 param type=select name=database label=Database 4 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-4197fe3d76b4282c0f9aa2576fbdec6550c3174f_4 option value=alignseq.loc*Human (hg18)*/option 5 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-4197fe3d76b4282c0f9aa2576fbdec6550c3174f_5 option value=faseq.locFly (dm3)/option 6 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-4197fe3d76b4282c0f9aa2576fbdec6550c3174f_6 /param 7 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-4197fe3d76b4282c0f9aa2576fbdec6550c3174f_7 /inputs Assume that the user selects the first option in the $database select list. Then the following will ensure that the tool produces a tabular data set whose associated history item has the label Blat on *Human (hg18)*. Toggle line numbershttp://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax# 1 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-c1ccb05e35e84df1d17f7b92455ff66b9d18618b_1 outputs 2 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-c1ccb05e35e84df1d17f7b92455ff66b9d18618b_2 data format=input name=output label=Blat on ${database.value_label} / 3 http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#CA-c1ccb05e35e84df1d17f7b92455ff66b9d18618b_3 /outputs It shows that .value_label attribute should produce the string in between the option tags, not the actual value. Why does this not work? When I use it it produces the value, or am I doing something wrong? regards, Leandro ___ 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/ ___ 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/