Closed lindenb closed 9 years ago
You are pretty close, just a few changes:
inputBinding: {}
on the #echo-in
parameter to indicate you want it added to the command line.#step0
should be named #step0.echo-out
(this is formed from the id of the step and name of the output parameter).source: #step0.echo-out
Here's the fixed up version:
#!/usr/bin/env cwl-runner
- id: "#echocmd"
class: CommandLineTool
inputs:
- id: "#echo-in"
type: string
label: "Message"
description: "The message to print"
default: "Hello World"
inputBinding: {}
outputs:
- id: "#echo-out"
type: File
label: "Printed Message"
description: "The file containing the message"
outputBinding:
glob: messageout.txt
baseCommand: echo
stdout: messageout.txt
- id: "#main"
class: Workflow
label: "Hello World"
description: "Puts a message into a file using echo"
inputs: []
outputs:
- id: "#main.output"
type: File
source: "#echocmd.echo-out"
steps :
- id: "#step0"
run: {import: "#echocmd"}
inputs: []
outputs:
- { id: "#echocmd.echo-out" }
:+1: thanks; I'll update the code on monday
OK, I've updated my cwl, It's working now , thanks ! :-)
10H23: added a second example hello-param.cwl with parameters.
I like this. @lindenb do you mind if I merge it in?
@mr-c yes, you can merge :-)
I've got some other questions/test-cases. I'll ask for help in another pull-request.
Thanks
My pleasure!
Hi Peter, thank your for your help.
My current interest is to translate my Makefile-based workflows to other engines. So my first idea is to just implement a minimal workflow, something like:
my attempt so far:
(well I tried a few variations of this, without success...) The specification is quite large, and honestly, I didn't read/understand the whole document.
How can I make it run please ? :-)
Of course, don't accept this pull request for now. :-)
While I'm here:
Thank you for your help,
Pierre