CONCEPT T6 / SCIENTIFIC WORKFLOWS AND REPRODUCIBLE DEPLOYMENT

Agentic workflows you can run again.

A scientific workflow chains simulation, analysis, AI, and visualization steps across machines. It is only useful as evidence if another person can run it again and get an explainable result.

01

Deployment as a record

Jarvis describes a software stack and its resources as a pipeline that can be deployed, monitored, and torn down. CLIO Core ships pipelines for Aurora, Delta, local machines, and other targets, so a run records its own configuration.

02

Integrations

The workflow integration catalog covers simulations such as LAMMPS and Gray-Scott, storage services, and I/O benchmarks such as IOR and FIO.

03

Agent-operated steps

When an agent performs a step, the tool calls and their results become part of the workflow record. The IOR deployment evaluation in the eScience 2025 poster measured agents configuring the benchmark across several agent and model combinations and prompt variations.

How IOWarp approaches it

Where to go deeper.

Applications that use it

  • A1

    Agents in the materials workflow

    Design on HPC, additive manufacturing, X-ray tomography, and fatigue testing: the Utah team’s reference workflow, and the agent tools built for it.

    Active collaboration
  • A4

    Agentic workflows across HPC and cloud

    A DOE Genesis Mission project at PNNL on performance-aware agentic workflows for the Genesis Mission Platform. The IOWarp team works on workflow motifs and performance models.

    Project began August 2026
  • A5

    CLIO on national research systems

    Where CLIO Core has been built and run: ALCF Aurora, DeltaAI, and the Ares cluster.

    Built and run on national systems
Common questions

Common questions.

What is Jarvis?

A deployment framework from the Gnosis Research Center that describes software stacks as pipelines over a resource graph. CLIO Core uses it for per-machine deployment.