-
cwl-utils requirements uses less than
-
Some things that would be nice to have available:
- Assertions (#3954)
- Branching (and rejoining) based upon
- the result of a previous input step: final job state, dataset content, etc (cou…
-
@tetron would this be okay for Arvados?
https://github.com/common-workflow-language/cwl-v1.2/commit/a6cb03b3cb67dee2ea644e94b1a57deef4d03c00#diff-bc8aedc9592506dd171277abda2c1207a86260b82508a3a3289…
-
Labelling this as low priority because this is dependent on a larger workflow conversation (and is not a common use case for the site at the moment).
Expected Behavior: TBD on a larger conversation…
-
A variation on the `cwltool` specific experimental extension for "secret" parameters https://github.com/common-workflow-language/cwltool/pull/683
-
Hello, are there any plans to import and/or export workflows written in the Common Workflow Language standards?
https://www.commonwl.org
https://cacm.acm.org/magazines/2022/6/261172-methods-incl…
-
Replace cwltool by cwl-utils for parsing of CWL documents as soon as common-workflow-language/cwl-utils#10 is resolved.
-
Or just to the (unwritten) implementation guidance doc?
https://twitter.com/biocrusoe/status/864700272722944001
-
I think some updates would be helpful in keeping this repo relevant and a good source of information.
- Adding a section on cwl.
The debate about which workflow language to use may actually prev…
-
## Expected Behavior
I tried to run CWL-file with bash-script inclusion, which makes new files.
## Actual Behavior
It failed with error:
```
Workflow error, try again with --debug for more info…