Diagram of workflow in this example.

A repository for examples using Ascent, in-situ creation of Cinema databases, and post-processing analysis.

Build instructions embedded in this workflow are derived from the Ascent build instructions here. This workflow uses spack to build all executables, from a specific commit.

This workflow will pull cached builds from a E4S repository, if they exist to speed up the build/install of requisite applications. If no cached builds are available, it will use spack to build applications.

Images from the resulting Cinema database (used to validate run)

The workflow does the following:

• Creates a Pantheon environment and build location
• Clones a specific commit of Spack
• Uses spack to build Ascent and set up a coupled app/in-situ workflow
• Runs the workflow to produce a Cinema database
• Adds a Cinema viewer, and packages up the results.
• Verifies the Cinema database

First, clone the repository, then:

1. edit the bootstrap.env file to include your compute allocation ID and workflow path.
2. ./execute will execute the workflow