Skip to content

Set a baseline

A Run's baseline is the Run it's compared against. Bramble copies the baseline's setup into new Attitudes, compares the pre-checks against it and generates delta postpro. For how baselines work, see baselines and deltas.

Before you start

  • The baseline can be any Run you can open, in this Project or another one.
  • Restricted Users can't set baselines or create child Runs.

Choose a baseline for a Run

You can set the baseline when you create the Run, or change it later in Edit Run.

  1. In Create Run (or Edit Run), find Baseline Run. It shows the current baseline, or No baseline selected.
  2. Click Select Baseline.
  3. Choose the Baseline Project, then the Baseline Run. Both lists can be filtered by typing.
  4. Click Apply Selection, or Cancel Selection to keep the current baseline.
  5. Bramble copies the baseline's Map and Kinematic Setup into the form. When you're editing a Run whose Map or Kinematic Setup differs from the baseline's, Update Map and Kinematic Setup asks which to keep:
    • Keep Current Values keeps the Run's own Map and Kinematic Setup.
    • Use Baseline Values switches to the baseline's.
  6. Click Create Run (or save the Run).

To remove the baseline, click Clear next to Baseline Run.

If the Project has a Project baseline (below), Create Run starts with it already selected.

Changing the baseline later

A new baseline isn't applied to delta postpro that has already finished. To regenerate it, use Re-run in the Create Delta PostPro row. See re-run post-processing.

How Attitudes are matched

Each Attitude is compared with the Attitude in the baseline Run whose Map entry has the same name. The names are matched, so the baseline can use a slightly different Map. If neither Run has a Map, their single Attitudes are matched.

An Attitude with no match shows Attitude not in baseline at the top of its column on the Summary tab. It gets no deltas. That's fine if the Attitude is new in this Run.

The Summary tab also shows the baseline's Map next to the Run's, as "(Baseline Map: …)", when they differ, or (Baseline has no Map). The Run page header links to the baseline, or shows (No Baseline Selected).

Set the Project baseline

A Project can have a default baseline Run. New Runs in the Project start with it, and Create Child uses it.

  1. In the sidebar, under Simulation Admin, click Runs.
  2. In the toolbar, click Project baseline: … (it reads click to set when there's none).
  3. In Select Project Baseline, choose the Baseline Project and Baseline Run.
  4. Click Select Baseline. To remove the Project baseline, click Clear Baseline instead.

The Project baseline controls are disabled until the Programme has a Template Case, and in example Programmes.

Create a child Run

A child Run (sometimes called a modification Run) is a copy of an existing Run's setup with that Run as its baseline. Use it to test a change, such as new geometry, against a Run you've already solved.

  1. Start from one of these:
    • the Create Child Run button on a Run's row in the Runs table
    • Create Child in the Runs toolbar, which uses the Project baseline as the parent
    • Create Child in the Attitude Status dialog on the Results page
  2. In Create Child Run, check the details. The Map and Kinematic Setup come from the parent, and you can change them. The Kinematic Setup must be complete.
  3. Optionally tick Copy setup without Baseline to copy the setup without making the parent the baseline.
  4. Click Create Child.

The child Run gets all the parent's Assemblies, and each Attitude copies its CFD setup, checks template and postpro selections from the matching parent Attitude. Change the Assemblies and setup as needed before you launch.

You can't create a child from:

  • a Run with archived Attitudes ("Cannot create child with archived run", "Cannot create child because some attitudes are archived")
  • an optimisation Run ("Child cases can not be created from an optimisation run.")

The Runs table's Baseline column links each Run to its baseline.

When a child finishes before its baseline

Delta postpro needs the baseline Attitude's solution. If an Attitude reaches Create Delta PostPro before its baseline Attitude has finished Mesh & Solve:

  1. The stage shows Waiting, with the tooltip "Waiting for Baseline to complete Mesh & Solve". The rest of the lifecycle carries on.
  2. When the baseline's Mesh & Solve completes, Bramble runs the waiting delta postpro automatically. You don't need to do anything.

If the stage still shows Waiting after the baseline has finished Mesh & Solve, use Re-run in the Create Delta PostPro row (see re-run post-processing). If you can't, contact support@bramblecfd.com.

Related: Baselines and deltas · Create a Run · Configure pre-checks · CFD setup options