Skip to content

Parameter Sweep

Sweep Page

The Parameter Sweep runs multiple simulations automatically while varying one or more vehicle parameters. It is the most powerful tool in ARD for understanding sensitivity, finding optimal setups, and exploring trade-offs across your vehicle configuration.

Which setup does this use?

This simulation runs against your current live vehicle setup — not a Setup Launcher setup sheet. Only the Run Sim button on the Setup Launcher page itself attaches a setup sheet to a run. See Setup Sheet vs. Live Vehicle.


Overview

A parameter sweep takes your current vehicle setup and systematically varies chosen parameters — running a full simulation for every combination. Instead of manually changing a spring rate, running a simulation, recording the result, changing it again, and repeating, the sweep automates the entire process and presents the results together for comparison.

Sweeps can run any of the three QSS-family simulation types:

  • Lap Time (QSS) — Evaluate how parameter changes affect lap time
  • Straight Line — Evaluate how changes affect the aero platform and ride heights across a speed range
  • Cornering (beta) — Evaluate how changes affect peak lateral acceleration across a speed range

How Racing Teams Use It

Parameter sweeps are central to systematic vehicle development:

  • Spring rate optimisation — Sweep front and rear spring rates to find the combination that minimises lap time or optimises aero platform behaviour
  • Ride height studies — Sweep ride heights to understand the sensitivity of downforce, drag, and balance to platform position
  • Aero configuration comparison — Sweep through saved aero setups (e.g., different wing angles or bodywork packages) to compare their lap time impact
  • Anti-roll bar tuning — Sweep ARB rates to understand the trade-off between cornering balance and mechanical grip
  • Weight sensitivity — Sweep ballast mass or fuel load to quantify the performance cost per kilogram
  • Multi-parameter interaction — Sweep two or more parameters simultaneously to find interactions (e.g., spring rate and ride height together)

Mass sweeps and Corner Weights

Sweeping driver mass, fuel mass, or ballast mass has no effect on total vehicle mass while Corner Weights are enabled on the Initialization page — measured corner weights override the computed total. The sweep configuration warns you when this applies. Disable Corner Weights if you want these sweeps to change vehicle mass.

Sweep Before You Iterate

A common mistake is to make setup changes one at a time based on intuition. A sweep across the realistic range of a parameter often reveals that the sensitivity is non-linear or that the optimum is not where expected. Spending credits on a sweep upfront can save many manual iterations.


Sweep Types

The sweep system supports three kinds of sweep dimension: component setups, whole vehicles and numeric values.

Parameter Sweeps

Parameter Sweep

Select a vehicle subsystem (e.g., aerodynamics, suspension) and choose from your saved setups for that component. The sweep will run a simulation with each selected setup applied in turn.

This is useful when you have discrete configurations to compare — for example, three different aero packages or four different spring sets.

Vehicle Sweeps

Choose Vehicle in the parameter picker, then pick two or more of your saved vehicles. Each picked vehicle replaces the current car for its runs, and every other dimension is applied on top of it: two vehicles swept with three wheelbases give six runs.

Every picked vehicle is checked when you preview the sweep, so problems show up before anything is billed.

Template vehicles

Template cars can't be swept. Load the template and save a copy first, then pick the copy.

Setup sheets

Vehicle is not offered when you sweep from a Setup Launcher setup sheet.

Numeric Sweeps (Fixed Value)

Numeric Sweep Numeric Sweep Dialog

Pick a specific numeric parameter (e.g., frontal area, spring rate, ride height) and define a range with minimum, maximum, and number of steps. The sweep generates evenly spaced values across the range and runs a simulation at each.

Setting Description
Min The lower bound of the sweep range
Max The upper bound of the sweep range
Steps The total number of values generated, evenly spaced from Min to Max inclusive (e.g., 4 steps from 0 to 100 gives 0, 33.3, 66.7, 100). Follows the same convention as numpy linspace. Steps must be a whole number — an inline error appears immediately if you enter a decimal, and the Run button stays disabled until it is valid.

Units

Numeric sweep values are entered in the displayed unit for that parameter (e.g., N/mm for spring rates, mm for ride heights). The system converts values to SI units internally before running the simulation.

Symmetric Parameters

For parameters that should be mirrored left-to-right (e.g., left and right spring rates), enable the symmetric option. The sweep will automatically apply the same value to both sides.

Parameters Not Used by This Car

Parameters the vehicle doesn't use in its current setup can't be swept, because every run would come out the same: for example, motor and battery values on an ICE powertrain, fixed aero coefficients while aero is set to Map, kinematic values that are computed from pickup points, bump stop gaps while bump stops are off, a heave spring that is switched off, or an optional value that is disabled. The same applies to swapping components, such as a heave spring that is off or an engine on an electric powertrain.

The parameter list hides these by default. Tick Show … not used by this car to list them with a lock and the reason; hover a locked row to see what to change on the setup page. A sweep never changes a component's mode for you. If a saved sweep includes one, the warning appears on that sweep item.

Geometry Adjustments

The fitted setting of a geometry adjustment (which shim or hole is used on a pickup point) can be swept, even though values computed from the pickup points cannot. Each adjustment is swept and compared by its name.

Symmetry Flags

When a component's symmetry is turned on (springs, dampers, bump stops, calipers or tyres), the right-hand side copies the left. Sweep the left side: Symmetry is ticked automatically, so every run applies the value to both sides.

Ambient Conditions

Numeric ambient conditions (for example temperature and pressure) can be swept just like vehicle parameters. The same values are also selectable directly in the setup sheet. See Ambient Conditions.


Grouping

Group Sweep Parameters

By default, each sweep dimension is independent — the sweep generates every possible combination of all parameter values. For example, sweeping 3 aero setups and 4 spring rates produces 3 x 4 = 12 simulations.

Groups change this behaviour. Components within a group move through their values together, index by index, rather than generating all combinations. This is useful when you have paired configurations that should always be tested together.

For example, if you group a front spring sweep (3 values) with a rear spring sweep (3 values), the sweep runs 3 simulations (pairing the first front with the first rear, second with second, etc.) rather than 9.

Group Size Consistency

All components in a sweep group must have the same number of values. For parameter sweeps, this means the same number of selected setups. For numeric sweeps, this means the same number of steps. The sweep will warn you if a group is inconsistent.


Constraints

Sweep constraints let you define conditions on a combination's results: a combination whose results fall outside them is invalidated. Use them to keep large sweeps focused on physically meaningful configurations, such as limiting ride height, aero balance, or any other parameter relationship your team wants to enforce.

Invalid combinations are marked as DNF in the sweep configuration rather than silently disappearing, so the combination table still shows what was generated and why certain permutations will not produce results.

Constraint ranges are one-sided where you need them — you can define just a minimum, just a maximum, or both. A range with only a lower (or only an upper) bound is valid.

Each constraint can have multiple conditions, chained together with AND — a combination is only constrained when every condition is true at once. For example, you can limit ride height only when speed is between 190–210 km/h and lateral acceleration is above 1.5g.

A combination that breaks a constraint has still been simulated, so its credits are not refunded. Other failures, such as a simulation that cannot be solved, are refunded.


Simulation Type Configuration

After defining your sweep parameters, choose which simulation type to run for each combination:

Configure the same settings as a single Lap Time Simulation:

  • Flying Lap or Standing Start
  • Lap Count (for EV/hybrid energy tracking)
  • Energy budget, push-to-pass and racing line re-optimisation now live on the Race Conditions page, and are swept as their own Race Conditions dimension rather than as part of the Lap Time configuration

Configure a speed range for the Straight Line Simulation:

  • Min Speed and Max Speed
  • Speed Unit (km/h, m/s, mph)

Beta Feature

Cornering sweeps are currently in beta. Behaviour may change in future releases.

Configure a speed range for the Cornering Simulation:

  • Min Speed and Max Speed (minimum 10 m/s)
  • Speed Unit (km/h, m/s, mph)

The Combination Table

Combination Table

As you add sweep dimensions, the Combination Table on the right side of the page shows every parameter combination that will be simulated. Each row represents one simulation run, and each column shows the parameter value for that run.

When a sweep dimension steps through saved setups rather than numeric values, each cell shows a version badge next to the setup's name, so you can tell exactly which version of that component was used in the combination.

The Number of Permutations displayed at the top tells you exactly how many simulations will be queued. This directly affects credit cost — each permutation costs the same as running a single simulation of that type (for Lap Time sweeps, that includes the Lap Count: each permutation costs credits per run × Lap Count). A permutation that fails a constraint still counts, because its simulation ran.


Running a Sweep

  1. Navigate to the Sweep page under Simulations
  2. Add one or more sweep dimensions using the Parameter or Fixed Value buttons
  3. For each dimension, select the parameter path and configure its values or setups
  4. Optionally create Groups to pair dimensions that should move together
  5. Review the Combination Table to verify the permutations look correct
  6. Select the simulation type (Lap Time, Straight Line, or Cornering) and configure its settings
  7. Enter a Simulation Name and optional notes
  8. Click Run Simulation

The simulation name also names the component copies

A sweep copies every component it varies and names each copy after the simulation, so the name must not clash with components already in your team. If it would, the sweep is blocked before it starts with a message asking you to choose a different simulation name. Rename the sweep and run it again.

Save Your Sweep Configuration

Use the config bar at the top of the sweep page to save and load sweep configurations. This lets you re-run the same sweep after making vehicle changes, or share sweep setups with your team.


Understanding Results

Sweep results are designed for comparison across configurations:

  • Metrics — View summary metrics (lap time, max speed, sector times) for all permutations side by side
  • Parallel Coordinate Plots — Visualise how swept parameters relate to performance outcomes across all permutations simultaneously
  • Trace View — Inspect the full trace data of any individual permutation, ready as soon as the sweep has finished and you have staged it

Trace Data for Sweeps

Every permutation in a sweep keeps its full trace data — the per-point channels like speed, g-force, and ride heights. When a sweep finishes, those traces are pulled in for the whole sweep automatically, so there is nothing to retrieve by hand before you can plot them.

Staging a permutation loads only its metrics and configuration, which keeps the Staging Area quick even for large sweeps. The heavier time-series data is loaded when you actually plot it in the Trace View.

If a trace is still being fetched from storage, you will see a short Retrieving Results notice rather than an empty chart. The Trace View plots the results you have selected and tells you when you have selected more than it can draw at once — deselect a few to choose which are rendered. The Metrics table and Parallel Coordinates are unaffected, since they only need metric values.


Tips & Best Practices

Start Coarse, Then Refine

Begin with a wide range and few steps (e.g., 3-5 values) to understand the general sensitivity. Once you identify the interesting region, run a second sweep with a narrower range and more steps to find the precise optimum.

Sweep One Thing at a Time First

Before running multi-dimensional sweeps, sweep each parameter individually. This gives you a clear picture of each parameter's sensitivity before introducing interaction effects.

Use Groups for Paired Changes

If you always change front and rear springs together (e.g., maintaining a stiffness ratio), group them so they step together rather than creating a full factorial combination.

Check Permutation Count Before Running

Multi-dimensional sweeps grow quickly. Sweeping 5 parameters with 5 steps each creates 5^5 = 3,125 simulations. Use groups and smaller step counts to keep the permutation count manageable and cost-effective.

Credit Cost

Each permutation in a sweep costs the same as a single simulation. A sweep with 20 permutations costs 20x the single-simulation credit cost. For Lap Time sweeps with a Lap Count above 1, multiply again by the lap count (20 permutations of 3 laps costs 60x a single-lap run). Check the permutation count and your remaining credits before launching a large sweep.

Subscription Limits

Your subscription tier determines the maximum number of permutations per sweep and the maximum number of sweep dimensions you can add. If you exceed either limit, the Run button will be disabled and a message will indicate which limit has been reached. Upgrade your subscription to increase these limits. A sweep that takes your team over its result storage limit still finishes, but the next simulation is blocked until you free space.