Skip to content

Scenario Catalog ​

The Scenario Catalog lists the scenarios of all your projects, the examples in your account included. It keeps no copy of its own: scenarios live in their projects, so editing a project changes its scenarios in the catalog, and deleting a project removes them.

Browse the scenarios ​

Open Scenario Catalog in the top bar of the Projects page. Each card shows a square of the scenario's color before its name, then its project, how many nodes it holds, its description and its project's graph; the strip at the top is the same on every card. Search by name, description or project, sort by Recently edited, Name or Project, and filter by project or by origin (Your dataflows or Examples) in the left rail. The drawer on the right sums up the selected scenario.

The Scenario Catalog page
The Scenario Catalog: the scenarios of example 06 and of the SCOUT dataflows. Baseline is selected, and the drawer on the right shows its project's graph and how many nodes each of its three parts holds.

View details shows the scenario's set and its project's graph, with the scenario's nodes in its color and its shared context outlined, and three lists: Shared context, Scenario-specific nodes and Shared outcomes. Each shared outcome, each of the scenario's last nodes and each context node that feeds it shows the output its project saved. A node with No saved output has not run since the scenario was defined. Open source project opens the project on the canvas.

The details of the Baseline scenario
View details for Baseline: its nodes in blue on the project's graph, the Data Pool it reads outlined, then the three lists, with the outputs its project saved.

Bring a scenario into another dataflow ​

On the canvas, click Scenario in the top bar to open the catalog's drawer, and drag a scenario's card from its Browse all tab onto the canvas. Browse all lists the scenarios in a panel for each scenario set, headed by its name, how many of the listed scenarios are in it, and Open source project; the sort orders the groups by their first card, and the cards within each group. Its In project tab holds the open dataflow's own scenarios (see Scenarios).

The Scenario Catalog drawer with its cards in two groups
The Scenario Catalog drawer's Browse all tab, searched for Elm Grove: two scenarios under Elm Grove heat and one under Elm Grove flood, each card ready to drag onto the canvas.

One card brings one scenario, as a copy, where you dropped it:

  • the first scenario of a set makes a copy of its set, named as that set is, with a number added when the dataflow has a set of that name; each scenario of the same set dragged in after it joins that copy;
  • it keeps its name, and its color unless a scenario of the dataflow already wears it;
  • its scenario-specific nodes are copied, each naming the node it was copied from;
  • the context it reads arrives once for the set, as Data Loading nodes named for the nodes they stand for, which read copies of what its project saved, wired where the context was; a scenario of the set dragged in later reads the ones already there and brings only the context they lack;
  • a context node with no saved output runs first, on the server and in the scenario's project, which saves its output there; a notice names it while it runs;
  • a shared outcome comes once every scenario it reads is in: a chart comparing three scenarios comes with the last of the three;
  • its results show what its project saved, before anything runs;
  • the packages its nodes use are added to the dataflow.

Everything arrives collapsed: the scenario's box, and the shared context and shared outcomes of its set's copy. Double-click a box to open it.

A dropped scenario: a Data Loading node wired to a collapsed box
Twice as tall from example 06, dropped: a Data Loading node reads a copy of the Data Pool's saved output, and the collapsed box shows Roads by sunlight done, before anything runs.

Editing the copy leaves the original as it is.

An agent that reads your dataflow tells which project and scenario a copy came from, or that they are gone. Asked for a scenario of another project, the Dataflow Builder names it and its project for you to drag in from Browse all.

To compare the scenario with your own work, connect a node of its box and one of yours to one chart or map, as in Compare scenarios. To run it on your own data, double-click the shared context's box, delete a Data Loading node, and connect your node to the scenario node it fed; Run scenario then runs your node first.

A drop is refused, and nothing is added, when:

  • the dataflow holds that scenario already; the message says so;
  • a node feeding it has no saved output and cannot run on the server: only the browser runs it, such as an Autark compute node, you are a guest on a hosted Curio, or Curio runs with --no-project. Run the scenario in its project, then drag it again;
  • running a node feeding it fails; the message says why;
  • its nodes need a package, a dataset or a model your account does not have, or a package your account cannot add; the message names it.

Share scenarios ​

Scenarios travel with their dataflow. Duplicate on a project's card copies its scenarios as they are at that moment. A dataflow someone shares with you lists its scenarios in your catalog once you save it to your projects with File > Save dataflow.