I am with Peter that the best thing to do is probably to specify
true or false. We just had a similar report from Bjoern though -
the thinking being that this was probably allowed in the past (using
the truevalue/falsevalue) but Galaxy lost that functionality -
https://trello.com/c/iGk3f1pE.
Hi all,
I have encountered a problem when trying to run trinityrnaseq (Galaxy Tool
Version 0.0.1) from Galaxy. Leaving the strand-specificity input parameter as
None will prevent the form from being submitted. Instead, the
strand-specificity input box will be highlighted in red and I'm asked
Hello Peter C.
Thanks for the prompt response - yes, using 'true' and 'false' in the tests
seems to work for my simple example (as do 'True' and 'False').
However I suspect that there is something else going on in the real tool that
I'm trying to test, as I still can't get this to work - so
Hello
I'm currently writing tests for a tool and think I've found a situation where
the behaviour of the boolean parameter type does not seem correct within the
test environment.
The tool defines the following boolean parameter:
param name=spmr type=boolean truevalue=--SPMR falsevalue=
On Fri, May 8, 2015 at 3:05 PM, Peter Briggs
peter.bri...@manchester.ac.uk wrote:
Hello
I'm currently writing tests for a tool and think I've found a situation where
the behaviour of the boolean parameter type does not seem correct within the
test environment.
The tool defines the
Hi Christian,
was the trinityrnaseq tool installed from the Tool
Shed? Which repository? Just to check this is not a tool
problem.
Cheers,
Nicola
Il 08.05.2015 10:44 Christian Schudoma (TSL)
ha scritto:
Hi all,
I have encountered a problem when trying to
run trinityrnaseq (Galaxy Tool
The problem is not in the Cheetah code, which does not get executed
because of the validation error.
I think this a Galaxy bug which tries
to validate the parameter values but interprets the value None of the
library_type param as no option selected.
Nicola
Il 08.05.2015 19:18
Christian
