Skip to main content
SimplePipeline is deprecated and will be removed no earlier than November 2026. Use a regular Pipeline for all new work. To move existing code over, see Migrating to Pipeline.Once it is removed, past SimplePipeline runs can no longer be fetched. Save any results you still need before then.
A SimplePipeline runs a workflow with at most one expensive element, meaning a single DataFit, ArrayDataFit, or Validation, and returns a flat result containing parameter_values, cost, and optional summary_stats. A regular Pipeline takes the same elements and covers the same case, so there is no longer a reason to start with SimplePipeline.

​
How it compares to Pipeline

A Pipeline’s data fit also stores its own model-vs-data overlay, so you can plot a fit without adding a separate Validation element.

​
How it works

This describes existing SimplePipeline runs. A SimplePipeline follows the same three conceptual steps as a full pipeline, just with a single expensive element and a flatter result:
  1. Build a typed config. SimplePipeline inherits everything from Pipeline, so you compose the same element types (a DirectEntry for known values plus one DataFit, ArrayDataFit, or Validation). It adds client-side validation that rejects configs with more than one expensive element. The error is raised immediately when you build it, so you never wait on a server-side rejection to find out.
  2. Submit fire-and-forget. The config is sent to Ionworks, which runs it in the background. Because there is at most one expensive element, there is no per-element status to track. You just wait for the whole job to finish.
  3. Read a flat result. A fit returns parameter_values and cost; a validation additionally returns summary_stats. There is no cumulative parameter threading to unpack, because everything is at the top level of the result.

​
Migrating to Pipeline

Because the elements are the same, migrating means swapping iws.SimplePipeline for iws.Pipeline, client.simple_pipeline for client.pipeline, and reading results by element name. The method-by-method mapping, a before/after example, and the remaining SimplePipeline reference for code that has not migrated yet are in the Documentation tab:

Migrating to Pipeline

Map each client.simple_pipeline call to its client.pipeline equivalent and read results by element name.
For the full schema API, see the ionworks-schema documentation.