Speaker
Description
In the initial HMC application, CWL workflows had a special role in heliport. This contribution explains why this seemed necessary at the time and illustrates what has changed since then.
The role of UNICORE as a central component that provides access to our computing resources and also supports workflows has emerged over the course of the project.
It is challenging to support everything that modern workflow languages can support. Instead, we focus in the future on the work with provenance information (visualisation, ...). The execution of CWL will slowly be phased out and moved to stand-alone third-party tools (e.g. Rabix, Toil, UNICORE, ...) which are able to generate provenance metadata according to established standards (wf4ever wfdesc, W3C PROV, ...). This would also allow us to import workflows from other custom software stacks (e.g. spekNG, Eupraxia Notebooks, ...) and move the implementation into the tools themselves instead of creating more HELIPORT plugins.
