s4n is able to call cwltool for local execution via
s4n execute local -r cwltool <FILE> <ARGS> (-r is also --runner)
For scenarios where cwltool is not available (e.g. Windows) there is also
s4n execute local <FILE> <ARGS> which is a basic local runner only accepting CommandLineTools which handles most of the simple stuff CWL can do (48/195 tool conformance tests pass)
I think this is ready for merge:
The current status:
Can execute local CWL Files using CWLTool -> s4n execute local --runner cwltool
Can execute local CWL CommandLineTools using a custom runner -> s4n execute local --runner custom or s4n execute local
Workflows currently not in supported by custom runner as we have no internal representation yet due to not having the workflow commands ready
Custom Runner passes most "usual" cases of CWL Conformance Tests, but a lot does not work yet (like inline javascript, nullables, arrays, Any-Type) which currently fails because CWL with these features can not be parsed yet
s4n is able to call
cwltool
for local execution vias4n execute local -r cwltool <FILE> <ARGS>
(-r
is also--runner
)For scenarios where
cwltool
is not available (e.g. Windows) there is alsos4n execute local <FILE> <ARGS>
which is a basic local runner only accepting CommandLineTools which handles most of the simple stuff CWL can do (48/195 tool conformance tests pass)