Why Use JAWS

✨ New Features

  • With a simple command, jaws submit, you can submit a workflow. Running pipelines is made easier by conveniently masking the details of how and where the jobs run.

  • You can monitor your jobs with simple commands, like jaws log.

  • You have access to multiple compute clusters operated by different national labs. For example, to submit to the compute site at Pacific Northwest National Lab (PNNL), the command would be jaws submit <wdl> <inputs.json> tahoma, where “tahoma” is the name of the cluster.

  • Your workflows are easily scalable. For example, if you have tasks that can be run in parallel, you can select multiple nodes.

../_images/why_jaws.svg

Here are some additional benefits to using JAWS.

Leverages Community Supported Tools

JAWS is built upon a foundation of robust, community-supported tools, ensuring reliability and widespread compatibility.

../_images/technologies_used.png

Technologies used:

  • Authentication: Globus OAuth.

  • Cromwell: processes workflows described in either WDL Workflow Description Language.

  • Docker, Shifter, Singularity: defines run environment.

  • HTCondor: jobs are relayed to multiple compute clusters; for example, “dori” & “jgi”.

  • Globus: File transfer to/from multiple end-points using GridFTP.

  • REST APIs: multiple JAWS components communicate by REST.

  • RabbitMQ: Message broker used to communicate workflow tasks between Cromwell and the workers running on the compute cluster.