Why Use JAWSο
JAWS (JGI Analysis Workflow Service) simplifies and scales scientific workflows across multiple HPC facilities, all through a single command-line interface.
π Simplified Workflow Submissionο
With a single command, jaws submit <workflow.wdl> <inputs.json> <site>
, you can launch your pipeline, no matter where it will run. JAWS takes care of moving your files, configuring the environment, and submitting your job securely and efficiently.
π Real-Time Monitoringο
Monitor the status of your workflows using intuitive commands like jaws log
. Check the status, view outputs, and debug failed tasks from a centralized interface.
π Access to Multiple Compute Sitesο
JAWS connects you to compute resources across DOE facilities. Examples include:

JAWS is deployed across multiple DOE HPC systems, with multiple sites per system. Green indicates JGI-accessible sites, purple marks NMDC project sites, and orange shows KBase project sites. * Deployment to the IRI Testbed is in progress.ο
All compute sites are managed centrally by JAWS, allowing users to focus on scienceβnot infrastructure.
π¦ Portable and Reproducible Workflowsο
JAWS runs containerized tasks using Shifter or Apptainer-compatible runtimes. This ensures portability and consistency across systems. All workflows are written in WDL (Workflow Description Language) and executed via Cromwell.
π Performance and Provenanceο
JAWS captures and visualizes detailed performance metrics through the JAWS Dashboard. This includes:
CPU and memory usage
Task-level runtime tracking
Debug return codes
π€ Hands-On Support and Communityο
The JAWS Team actively supports users through:
Weekly office hours and pair programming sessions
Comprehensive documentation and training materials
Monthly JAWS User Meetings for updates, demos, and feedback
Whether youβre porting a legacy pipeline or designing a new one, help is always available.
JAWS helps you run reproducible, scalable, and secure workflows across DOE facilities.ο