You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just like we have a CommandlineTool and Workflow editor, we should have an ExpressionTool editor. This editor would be largely like the CommandlineTool except that it would have no dockerImage field, no resource hints fields etc. and would create an ExpressionTool object. The workflow editor also needs to detect and understand ExpressionTool so it can be dropped into a canvas.
Please see the specification for fields supported by ExpressionTool. As a template, this is a bit like CommandlineTool with most fields stripped out and an expression field substituted for baseCommand
A simple example ExpressionTool is:
class: ExpressionTool
cwlVersion: v1.0
expression: '$({"out": inputs.word1 + inputs.word2 })'
id: expr_tool
inputs:
- id: word1
label: Word 1
type: string
- id: word2
label: Word 2
type: string
outputs:
- id: out
label: Word out
type: string
Just like we have a
CommandlineTool
andWorkflow
editor, we should have anExpressionTool
editor. This editor would be largely like theCommandlineTool
except that it would have nodockerImage
field, no resource hints fields etc. and would create anExpressionTool
object. The workflow editor also needs to detect and understandExpressionTool
so it can be dropped into a canvas.Please see the specification for fields supported by
ExpressionTool
. As a template, this is a bit likeCommandlineTool
with most fields stripped out and anexpression
field substituted forbaseCommand
A simple example
ExpressionTool
is:A more detailed example
ExpressionTool
, shamelessly lifted from https://www.biostars.org/p/226272/#226360 is:Needed to help out #407
The text was updated successfully, but these errors were encountered: