Scientific workflow engine designed for simplicity & scalability. Trivially transition between one off use cases to massive scale production environments
The CWL parser currently hardcode the same name for all workflows.
Find out if CWL has a way to specify a workflow name. If not use a hash ? A new endpoint parameter ?
@katevoss this could use PO input if it turns out CWL has no way to specify a workflow name
@Horneth commented on Mon Sep 11 2017
The CWL parser currently hardcode the same name for all workflows. Find out if CWL has a way to specify a workflow name. If not use a hash ? A new endpoint parameter ? @katevoss this could use PO input if it turns out CWL has no way to specify a workflow name
@danbills commented on Tue Oct 03 2017
So it turns out that CWL v1.0.2 has an
id
field for Workflow, and cwltool gives us one for free:http://www.commonwl.org/v1.0/Workflow.html#Workflow.
so we should update the model to have a required
id: String
and this problem goes away.@danbills commented on Tue Oct 03 2017
This also applies to
CommandLineTool
, cwltool pre-processing gives us one.