-
Notifications
You must be signed in to change notification settings - Fork 999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding "select" as parameter type of input parameters #8159
Comments
No, it's not possible at the moment, and as you mentioned it's not that straightforward, but we'll think about how to do this. |
@mvdbeek Thank you. Do you think (in a first move) that we can use |
Just brainstorming here a little: So the idea is that the you'd have a text field that is configured not at runtime but when the workflow is defined ? The downside here is that this would not be very flexible, and to turn this into a select field you'd have to list the valid options manually (and you somehow need to know what those valid values are). I was thinking that maybe we could have a real workflow select style parameter that you can connect to select parameters. This would be less of a concern for #7496 since the dbkey is a stronger convention. |
For the record I asked @jmchilton what he's thinking about this, and his response was
So perhaps a gxformat2 workflow could look like this:
I think that'd work nicely for selecting dbkeys and simple select parameters. For more conditional logic one could use an expression tool to produce a derivative of the parameter, for instance setting genome size dependent on the genome parameter, or selecting a dbkey for common sequence contaminants for a given species. |
@mvdbeek I was talking of text field only if is was simpler to implement as a first move. And I would like to be able to configure it at runtime of course. And this could work for reference genome as well. In a workflow with Blast, Bedtools etc... Blast and Bedtools can use the same reference genome. Blast for the alignment, Bedtools to grab the sequence. It's nice to be able to set this parameter only once.
I not sure that I understand. I was not talking about that, using same input parameter for different tools!
Perfect! |
Got these since 20.01: #9086 |
How are you able to specify name-value select boxes? Currently it appears the only option is value-value |
tested on usegalaxy.eu (19_05) and SnpEff build
We can use
Simple inputs used for workflow logic
as input parameter forRemove sequence version label
as it's a Boolean.We can't use
Simple inputs used for workflow logic
as input parameter forParse Genbank into Fasta
as it's a select (Yes / No)Is it possible to do that in another way? Or do we have to wait for a new commit?
I understand that it can be tricky because the displayed values (ie: GenBank) are not necessary the values used in command line (ie: gb).
The main goal I use
Simple inputs used for workflow logic
is to find these parameters at the top of the page when a workflow is launched, and when the same tool is used several times in a workflow. It avoids users to set same parameters several times.#7496 is a similar issue.
The text was updated successfully, but these errors were encountered: