-
Notifications
You must be signed in to change notification settings - Fork 73
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
add a workflow to connect optional workflow inputs to non-optional tool inputs #321
base: main
Are you sure you want to change the base?
add a workflow to connect optional workflow inputs to non-optional tool inputs #321
Conversation
to non-optional tool inputs
We should be able to infer the output data type, that's probably not that hard to do, as we do that with other outputs as well. |
You mean in the pick value tool? Question is how to set this? Can we do this in the ECMAS script? Is there an example / docs (I'm really missing docs on expression tools .. is there any)? |
Yes, format_source should just do it in https://github.com/galaxyproject/tools-iuc/blob/main/tools/pick_value/pick_value.xml#L149 |
Will try. But syntax and functionality-wise I'm not entirely sure how to address a dataset that is nested in two conditionals and a repeat (which might have some null datasets) :) |
Syntax-wise |
Test Results (powered by Planemo)Test Summary
Failed Tests
❌ Treat-optional-workflow-input.ga_1Problems:
Workflow invocation details
|
Using this workflow as sub-workflow should simplify workflows. I think that having this might be cool irrespective of if we do galaxyproject/tools-iuc#5713 + galaxyproject/galaxy#17271 -- which do more or less the same .. but still its two tools (which have nothing to do with the actual WF vs a single subworkflow witha clearly described purpose). But if we implement them the dataset creation tool could be removed here (which reduces the overhead of 1 tool call).
Edit: not happy yet. Problem is that the tool input requires a datatype, but the output of pick_value sets none. Setting the datatype of a subworkflow is not possible .. which apparently renders the approach useless. Would there be an option to set the output datatype of pick_value in a way that is useable by workflows.