Skip to content

Trace View

Trace View Page

The Trace View is the primary interface for detailed analysis of simulation results. It displays per-point data channels — speed, g-force, ride heights, power, and more — as interactive line plots against a configurable X axis (Distance, Time, or Velocity), with a configurable grid of supporting visualisations including track maps, scatter plots and distribution plots.


Overview

While the Metrics page shows summary numbers, the Trace View shows the full picture — every data point across the entire lap or speed range. You can overlay multiple simulation results (or uploaded telemetry) to compare them visually, zoom into specific sections, and read off exact values with a synchronised cursor.

The Trace View is built around a configurable grid layout with five cell types:

Cell Type Description
Trace Line plots of data channels vs. a configurable X axis — Distance, Time, or Velocity (the main analysis tool)
Track Map 3D track visualisation with car position markers
Scatter X-Y scatter or line plots of any two channels (e.g., g-g diagram)
Distribution Histogram and density plots showing value distributions
Video Onboard videos of uploaded results, and live animations of simulated ones, played in sync with the traces

How Racing Teams Use It

  • Lap analysis — Overlay simulation speed traces against telemetry to validate the vehicle model corner by corner
  • Setup comparison — Load two configurations and compare ride heights, aero platform, or tyre loads across the lap
  • Corner-by-corner review — Zoom into individual corners to examine braking points, minimum speeds, and throttle application
  • Time delta analysis — Enable the Δ time row to see exactly where one configuration gains or loses time relative to another
  • Powertrain analysis — Plot engine RPM, power output, and gear against distance to check shift points and power deployment

Getting Started

  1. Load one or more results into the Staging Area from the File Viewer (double-click a file, or select and click Stage Sim, or drag and drop files directly onto the staging area)
  2. A progress indicator shows loading status as results are processed
  3. Switch to the Traces tab in the results area
  4. The default layout shows a trace plot with speed (vCar) against distance (the default X-axis setting)

Sweep results

Sweep permutations plot like any other result. Their traces are read straight from storage as you stage them, so there is nothing to fetch first — see Staging a Sweep.


Comparing Two Simulations

The Trace View is where you compare the results of two or more simulations against each other:

  1. In the File Viewer, add both results to the Staging Area (double-click each one, or select them and click Stage Sim)
  2. Switch to the Traces tab, or click View Traces in the Staging Area
  3. Every staged result is overlaid on each trace plot in its own colour, with a shared cursor for reading values at the same point on the lap
  4. Enable Δ time on a trace cell to see where on the lap one result gains or loses time against the other

For lap time and other summary numbers side by side, use the Metrics page with the same staged results. The same workflow compares a simulation against uploaded telemetry.

The File Viewer's Compare button

The Compare button in the File Viewer opens Vehicle Compare, which compares the vehicle setups behind the selected results — which parameters differ — rather than their outputs.


Trace Plots

Trace Plot

Trace plots are the core of the Trace View. Each trace plot displays one or more data channels as line plots, with a configurable X axis and channel values on the Y axis. The X axis defaults to Distance (sRun) but can be switched to Time (tRun) or Velocity (vCar) from the layout editor. When multiple results are loaded, each result is drawn in a different colour. Results that do not contain the selected X-axis channel are automatically filtered out with a warning.

Channels and Rows

A trace plot is organised into rows. Each row has its own Y axis and can display one or more channels. Channels within the same row share the Y axis scale, while different rows are stacked vertically with independent scales.

For example, a typical setup might have:

  • Row 1: Speed (vCar)
  • Row 2: Longitudinal g-force (gLong) and lateral g-force (gLat)
  • Row 3: Front and rear ride heights (hRideF, hRideR)

Dual Axis

When a row contains channels with different units or scales (e.g., speed and RPM), the trace plot can use dual axes — one Y axis on the left and one on the right. Axis colours match the channel colours when a single result is loaded, making it clear which axis belongs to which channel.

Editing Trace Channels

Edit Trace Channels

Click Channels (top-right of a trace cell) to open the channel layout editor for that cell. From here you can:

  • Add or remove rows to control the vertical stacking
  • Add or remove channels within each row
  • Toggle channel visibility without removing them
  • Adjust row height weights (e.g., make the speed row taller than the g-force row)
  • Configure plot bounds — set manual min/max values for a channel's Y axis, or leave on auto-scale
  • Set decimal precision for cursor readout values

Adding or swapping a channel uses a single picker with Standard and Math tabs, so you can search across both data channels and math channels in one place. Click Add Channel to open the picker, or click directly on an existing channel row to swap it in place. Math channels are marked with a function icon so you can tell them apart from standard channels at a glance.

For layouts with many columns, the grid preview scrolls horizontally instead of compressing each column, so wide layouts stay readable while you configure them.

A channel's sign is backwards (e.g. damper travel positive in compression instead of extension)

Trace View plots a channel's values as imported — it doesn't invert them for you. If an uploaded telemetry channel logs the opposite sign convention to ARD, use the Flip checkbox when mapping that column during telemetry upload, then re-upload.

Hiding Channels and Metrics

Hiding Channels

You can hide specific channels or metrics from view without removing them from your configuration:

  • Hide from Trace Plot: Click a channel name in the legend band above its row to hide it from the plot. Hidden channels are grayed out and can be restored by clicking the icon again.
  • Hide from Metrics: Use the visibility toggle in the Metrics panel to hide specific metrics from the summary view.
  • Bulk Hide: In the Channels dialog, use the visibility toggle next to each channel to quickly show or hide multiple channels.

Hidden channels and metrics are not deleted — they are simply hidden from view and can be restored at any time.

X-Axis Channel

The X-axis channel for each trace cell can be set in two ways: click the X-axis label directly on the chart to switch inline, or open Channels (top-right of the trace cell) to configure it alongside the cell's rows and channels. The setting is saved per cell with the layout.

If a result does not include the currently selected X-axis channel, Trace View prompts you to switch to an available axis such as Distance (sRun), Time (tRun), or Velocity (vCar). Results with no trace channels show a no-traces message instead of an empty plot.

Math Channels

Trace View supports calculated math channels that can reference existing data channels, other math channels, and vehicle setup parameters. This lets you build layered calculations such as normalised signals, derived balance metrics, or team-specific analysis channels without exporting to a spreadsheet first. You can also build cumulative integrals, sums, and derivatives directly in the equation editor — see the dedicated Math Channels page for the full function reference.

Math channels are selectable on every chart type in Trace View — trace lines, scatter, distribution, and the track heat map — from the metrics axis selector. Each math channel can also carry its own display unit.

Math channels that are visible in Trace View are included when results are exported from the File Viewer. Bundle permissions can also include math channels so shared result packages carry the calculated channels your team expects.

Cursor and Statistics

Cursor and Statistics

Move your mouse across the trace plot to activate the cursor. A vertical line follows the cursor position and the current values for each channel and result are displayed in the legend band above each row.

The legend band shows:

  • Channel name and unit
  • Current value at the cursor position for each loaded result
  • X-axis value at the cursor position, with the active distance, time, or velocity unit when available

Click Stats on a trace cell to add a block in each row's top-right with every result's min, max and mean over the visible range. The numbers update as you zoom, and the setting is saved with the cell.

Zoom and Pan

Action Behaviour
Shift + Click and Drag Zoom into a rectangular region
Click and Drag Pan the view when zoomed in
Double-click Reset zoom to show the full distance range

Zoom Persistence

Zoom state is preserved when you add or remove channels, change result references, adjust line width, modify grid opacity, or change distance offsets. It resets when the X-axis channel changes, since the zoomed range means nothing on another axis.

Shared Y-Axis Scaling

Channels grouped onto the same Y axis remain scaled together while zooming, so related channels stay comparable within the same trace row.


Track Map

Track Map

The track map cell shows the circuit layout, flat from above by default or as an orbitable 3D scene, with car position markers. As you move the cursor across the trace plot, the car markers update to show where on track each result is at that distance point. Each marker is a dot with a soft glow in its result's colour, drawn at a fixed size on screen so it stays easy to spot whether you are zoomed in on a corner or out to the whole circuit.

Camera Controls

The map's view decides how the camera behaves; there is no separate camera setting.

  • Flat is a fixed top-down image, true to scale across the whole circuit. Drag to pan and scroll (or pinch) to zoom; it never rotates or tilts. Fit to Scene in the top-right corner brings the whole track back into view.
  • 3D is a scene you can orbit: drag to rotate, right-drag to pan, scroll to zoom. Fit to Scene brings the whole track back into view.

Beside Fit to Scene, the top-right pill has a button for each thing that can be drawn on the ground: the globe for satellite imagery and, in 3D, the mountain for the elevation profile. A button is highlighted while its layer is on; one that cannot draw for the loaded track is dimmed, and hovering it says why.

Satellite Imagery

Click the globe in the top-right camera pill to draw the real ground under the circuit instead of the grid, so the lanes and driven lines can be read against the actual kerbs, run-off and buildings. The imagery sharpens as you zoom in, and it is saved with the track cell like its other settings. It pairs especially well with the Flat view, which then reads like a map.

It needs a track that has been placed on a map in the Satellite Track Editor — that georeference is what tells the map where on Earth the coordinates sit. Tracks imported before alignment existed do not have one: the globe is dimmed, and hovering it says why, and a map saved with imagery on says so rather than silently showing the grid. When that track is the one loaded in the track setup, the notice links straight to the track editor to place it.

With results from different tracks loaded at once, only one set of imagery can be correct. The map uses the reference result's track and says so, because every result is drawn in its own coordinate frame and the others will not line up with the ground.

Elevation Profile

Click the mountain in the top-right camera pill to lift the 3D map onto the track's real elevation — the lanes, lines and car markers all ride the road. The road sits on a translucent body that reaches down to the ground, so climbs and drops read even from above, and the plinths and car markers stand on the road at its true height. Heights are exaggerated five times so that gentle gradients stay visible, and every result on the map shares one datum, so results on the same track sit at the same altitude.

It needs a track that carries road heights — a Road Height column (or Z_cord) in its data. For a track without them the button is dimmed, and hovering it says why; and a map saved with it on says so rather than staying flat silently. The button only appears in the 3D view: Flat is a top-down image with no relief to show. Like the other layers, it is saved with the track cell.

Sectors

Click Sectors in the map's top-left controls to mark the track's sectors — on the map and on every trace plot in the layout together (see Sectors on trace plots). It is one setting for the whole layout: clicking it again, or the flag on any trace plot, turns them off everywhere. A white tick crosses the road where each sector starts, and a small numbered badge sits beside each sector. Where there is room, the badge also lists each result's time difference to the reference result through that sector, marked with its legend colour — negative is faster. In a small cell, badges without room show just their number.

Hover a sector — its badge, or anywhere on it, lanes included — to light up its stretch of road and see all of its times: every loaded result on that track, each with its time through the sector and its difference to the reference. Sectors are timed on the first complete lap shown, so an out-lap never times a sector it didn't drive; a result without a complete lap shows –. If the reference's track has no sectors, the sectors (and the times they are compared against) are those of the first loaded result that has them, and the tooltip names it.

Click a sector to focus it. The map zooms to that sector, and every other cell in the layout narrows to it: trace plots zoom to the sector's distance (or time) window and hold it there (a drag on them scrubs the videos instead of panning, and a double-click doesn't zoom out), and scatter and distribution plots keep only the samples inside it, from every loaded lap, leaving out results on another track — they show the sector's name top-left while they do, and clicking it clears the focus. The focused sector is named beside the Sectors button; click its ×, or the same sector again, to return to the full lap. A trace plotted against velocity has no window for a stretch of track, so it stays as it is.

It needs a track with sectors defined in the track editor. A result carries its track's sectors as they were when it ran, so editing them takes effect for new runs. When the map cannot show sectors — a track without any defined, say — the button is dimmed and does nothing, and hovering it says why.

Sectors on trace plots

The Sectors button in a trace cell's control row (top-left, beside Δ time) is the same switch as the map's Sectors button — it turns the sectors on or off for the map and every trace plot at once. On a trace plot they show as a faint dashed line at each sector boundary through every row, and a sector bar under the plot — below the lap bar, when there is one — with a segment per sector on every lap, named S1, S2 and so on. The focused sector is highlighted in both, so zooming back out still shows which sector the other plots are narrowed to. Click a segment to focus that sector, exactly as clicking it on the map does; click it again, or double-click the bar, to clear it. It is saved with the layout, and works in a layout without a track map too. The button is dimmed, and says why, on a track without sectors or a plot against velocity.

Map Contour

Colour the track by a map channel (e.g., speed, g-force, ride height) to see how it varies around the circuit, and where results differ. Click Colour by… in the top-left corner of the map to pick the channel; the × beside it clears it.

The track's width is split into one lane per result, side by side from boundary to boundary, in the same order as the staging area. Each lane is coloured by its result's value at that point of the lap, so where two results differ, neighbouring lanes change colour at the same corner — even when both drove the same line, which used to hide one result under the other. The lanes fill the whole track rather than following anyone's line: they are a display of the track, not a trajectory, and every lane sits at the same point of the lap as its neighbours, however differently each result drove it. A border in each result's own colour — the same as its car marker, legend entry and staging row — says which lane is whose, and with a contour on, each result's car marker rides its own lane so the value under every car is read side by side. Where a result carries no track boundaries, the lanes split a fixed 7.5 m band around the reference result's line instead.

Every lane is measured against one shared scale, so the same colour means the same value whichever result it came from. The key in the bottom-left corner shows the scale in the channel's units.

Track Map Cell Options

Like every chart, the map keeps what it shows on the left of its top row and how you look at it on the right, beside the camera controls:

  • Abs / vs Ref (left, beside the channel) — what the lanes measure; see below.
  • Flat / 3D (right, beside the camera controls) — Flat (the default) is a top-down image, with or without a channel selected. 3D is an orbitable scene, and with a channel it also raises each lane by its value; the height button beside it sets how tall a lane stands at the top of the scale, in metres (1–60, default 15). From a low angle, taller outer lanes can hide the inner ones, which is why Flat is the default for comparing.
  • Colours — click the key in the bottom-left corner to change the palette: Rainbow, Viridis (colourblind-safe, and prints well) or Blue – Red (diverging — a good match for vs Ref, neutral where a result is level with the reference). Reverse flips it end for end, and Smooth / Banded switches between a continuous gradient and 2–12 distinct colours, so equal-coloured stretches read as equal.

These are saved with the track cell in the layout, so they stay as you left them, and two track maps — in one layout or in different layouts — can differ: a flat delta map beside a 3D absolute one, say.

Absolute vs. Reference

The Abs / vs Ref toggle decides what the lanes measure.

Absolute spends the whole colour and height scale on the channel's own range. That is the right answer for a single result, and close to useless for a sweep: speed spans 250 km/h round a lap, so the 2 km/h that separates two runs of the same setup is under 1% of the scale, and every lane comes out the same colour.

vs Reference subtracts the reference result instead, so the scale covers only the spread between results — that same 2 km/h now spans it end to end. Zero sits dead centre, so the colours have fixed meanings: the cold end of the scale is below the reference, the middle is level with it, and the hot end is above — with Rainbow, blue, green and red. The reference's own lane is drawn grey, off the scale, so it is never mistaken for a value; the key names it. A sample with no value is drawn as a dark gap. The subtraction is aligned by distance, so a corner in one run is always compared against the same corner in another, however differently the two laps were sampled.

Load a second result to use it — with only one there is nothing to compare against, and the map falls back to Absolute. It also falls back when the reference result does not carry the channel; the key always says which one you are looking at.


Scatter Plots

Scatter Plot

Scatter plot cells display two channels plotted against each other as an X-Y scatter or connected line plot. The most common use is the g-g diagram (lateral acceleration vs. longitudinal acceleration), which shows the tyre usage envelope.

Configuring Axes

Click on the X axis or Y axis label to open the channel selector and change the plotted channel. An optional colour channel can map a third variable to point colour: click Colour by… at the top-left of the cell (or the colour legend's title) to pick one, and the × beside it to stop colouring.

Heatmap Background

Scatter cells can display a 2D heatmap background derived from your vehicle's aero or setup maps, overlaid behind the scatter points. Click Map… at the top-left of any scatter cell to open the background map selector. A colour legend appears on the right side of the cell when a map is active. The aero maps offered are the solver's own composed maps for the result's vehicle, with every offset and mode (map, expression or coefficients) already applied, so the background matches what the simulation used. Other map and expression fields of the setup are offered too. To remove the heatmap, click the × beside the map's name.

Plot Type

The Dots / Line toggle at the top-right switches between scatter (individual points) and line (connected path) modes. Scatter mode is better for showing the overall envelope; line mode shows the sequence of points around the lap.

Cursor Synchronisation

The scatter plot cursor is synchronised with the trace plots. As you move the cursor across the trace, the corresponding point is highlighted on the scatter plot, and vice versa.


Distribution Plots

Distribution Plot

Distribution plot cells show a histogram of values for a single channel across the full lap. An optional kernel density estimation (KDE) overlay smooths the histogram into a continuous curve.

This is useful for understanding:

  • Speed distribution — How much time is spent at different speeds (helps characterise the circuit)
  • G-force usage — Whether the car is consistently near the grip limit or has untapped potential
  • Damper velocity distribution — Check how much time is spent in low-speed vs. high-speed damper regions

Configuration

  • Channel — click the x-axis title to pick which data channel to plot
  • Plot Type — histogram bars, density curve, or both, from the toggle at the top-right
  • Bin Count — number of histogram bins (more bins = finer resolution), from the settings cog beside it; it applies to the histogram only

Each loaded result is shown as a separate coloured distribution, with a togglable legend to show or hide individual results.


Video

A video cell plays a tile for every staged result, one to three to a row, in step with the traces:

  • Uploaded results play the onboard video attached to them — see Adding a Video. One without a video, or with its video switched off by the video icon beside its name, is animated instead, as a simulated one is, when it carries the car's position (xCar and yCar); without them it says it has no video, or no position to animate. Switching a video off is how its lap joins the others as a ghost; which ones are off isn't saved with the layout. Logged data has no track edges, so the lap is fitted onto its result's track by its shape: turned and moved until its line lies along the track's centreline. The track's own road, with its edges, kerbs, road heights and banking, is then drawn under it, and the car moves across the road as it did, wherever its logged position put it. This needs only the car's position, not its GPS origin, and laps from different uploads land on the same road, so they can be ghosted together. A lap with no track, or one whose shape doesn't fit its track, gets a road 7.5 m wide drawn round its own line instead, with no kerbs. Without ride heights, roll or pitch the car rides level.
  • Simulated results play a live 3D animation of the lap, drawn from the sim data on its track: the road with its elevation and banking, kerbs, the racing line, and the car with its wheels steering and turning.

A multi-lap result with a clip per lap plays them in turn when it is staged as a session, moving to the next lap's clip as each lap ends; staged as laps, each lap's tile plays its own clip.

A layout can have one video cell.

Playback

The bar under the tiles plays and scrubs every tile together. Where it is shows on every trace plot as the playhead, a violet line with a tab on top, apart from the cursor that follows your mouse; off the plots, the legend values, the scatter plots and the track map follow the playhead. Click a trace plot to move every tile to that point, or drag along it to scrub them, whether playing or paused; hovering alone leaves them where they are. The speed button beside the clock (1× to start) slows playback down or speeds it up, videos and animations alike: drag its slider between ¼× and 4×, or type any speed from 0.0625× to 16×. The speed isn't saved with the layout. A shorter video holds its last frame while the others carry on. Videos start muted; the speaker icon in a tile's corner unmutes it.

Syncing on Time or Distance

The tiles follow the X axis of the first trace cell:

  • Time — every tile shows the same time from the start of its lap.
  • Distance — every tile shows where its car was when the reference result was at that distance, so the cars stay level on the road just as the traces do, Distance Alignment offsets included. The reference's lap sets the clock, the other videos speed up or slow down to keep pace, and the bar shows the distance.

Focusing a sector jumps playback to the sector's start. Synced on time, every tile then counts from the moment its car was level with the reference's at the sector's start, as if the lap started there: the videos show the gap building through it. Level means by where the cars are, not by their logged distance, which on two laps of one run can be metres apart at the same spot. Ghosts start level with the full-colour car on its road, as drawn. A lap whose position can't be compared, such as one from another upload in a frame of its own with no track, starts by its logged distance instead.

The Bar Above the Tiles

The video cell's controls are along its top, as on every other chart:

  • On the left, the line colour: the channel the animation's racing lines are coloured by (vCar to start), on one scale for every lap in the tile. Click it to pick another, or × to draw each line in its result's colour instead. The Arrange dialog's video card picks it too. Each animation's colour key sits in its bottom-left corner; click it to pick the palette (rainbow, viridis or blue–red), reverse it, or split it into 2–12 bands, as on the track map.
  • In the middle, the results in the cell, each with its colour and name, long names cut short (hover one for all of it). It scrolls sideways when there are more than fit. A ghost's entry is a little faded. The video icon beside a result with a video switches it between its video and the animation.
  • On the right, how the tiles are shown, then the cell's fullscreen button. A switch that can't do anything yet, such as ghosts with only one animated result, is dimmed, and hovering it says why. The layout remembers them all:
    • Camera: in the cockpit (the eye) or behind the car (the car). Behind the car, the data overlay moves to the bottom-right corner.
    • Live data (the gauge): speed, gear and RPM, throttle and brake bars and a steering wheel over every tile, real videos included. Without a brake pressure channel the brake bar is estimated from deceleration. On to start.
    • Tyre forces (the arrow): an arrow on each tyre for its grip along the road (Fx, Fy) and its load pointing up (Fz), both to the same scale of a metre for every 10 kN. Each is coloured from green through yellow to red as it nears the most grip, or the most load, any tyre sees in the lap.
    • Ghosts (the ghost), with two or more animated results staged: one animation instead of a tile each. The reference result's car is drawn in full colour (or the first animated result's, when the reference has a video). The others are see-through cars in their own colours, each with its racing line on the same colour scale. When the traces plot distance, each ghost is drawn level with the full-colour car, which compares the lines through each corner. It is placed by where it is on the road, not by its logged distance, which can be metres off another lap's at the same spot. When the traces plot time, each is at its own time, like a race. Every ghost rides on the full-colour car's road, at its height, so on a hilly circuit none sinks into the track or floats above it.
    • Satellite road (the globe), when the track has been placed on a map in the Satellite Track Editor: the road and 5 m either side are cut out of the satellite imagery and printed onto the animation's road, up its hills and round its banking. The real kerbs, painted lines, run-off and grass edges are then where the car passes them, as reference points a driver would use. The drawn edge lines, kerbs and start line give way to the real ones. The imagery comes in over a few seconds the first time, a stretch at a time, with the navy road showing until it does. Beyond each edge it is printed level with the edge, not shaped to the real ground. How well it lines up depends on how carefully the track was placed on the map.

What the Animation Shows

  • The car is a generic single-seater with a see-through body, so the wishbones from the chassis to each wheel show. The wheels stay on the road and the body moves against them, so the suspension's travel shows as the body heaving, rolling and pitching over the wheels.

  • The car rolls, pitches and points as the data has it. It rolls by its chassis roll against the road (aRollTotal, or aRollSprung where that is all there is), and with the road on top of that where it is banked. It pitches by aPitch and with the slope. Tipped over in the data, as in a crash, it turns as one piece, wheels and all, and rests on the road. A simulated car points off its path by its sideslip (aSlipCar), its nose into a corner. An uploaded lap's heading is the logger's own, so it points where that does.

  • The track is the result's track itself, as the solver drove it: a navy road with white edges, closed round the whole lap with no seam at the start line, at its real elevation and banking. It stands on see-through grey walls, the same as the track map's elevation, down to a flat dark grid at the circuit's lowest point, like the Great Wall: on a hilly circuit the walls show how far the road has climbed. With the satellite road on, the walls stand under the printed ground's outer edges. A result whose track can't be shown, such as a hidden one, gets a road drawn round its own line instead, unbanked.
  • Kerbs, the slate bands, mark each corner: on the inside round the apex, where the racing line comes closest to that edge, and on the outside where the line turns in and where it tracks out. A corner turns at least 40° at under 200 m radius on average, so a straight or a fast kink such as Eau Rouge gets none. The line uses a kerb within a quarter of the track's width of the edge, and each kerb runs 8 m past it.
  • The racing line is the car's path, a low plinth standing on the road. Its top is coloured by the Line colour channel, and its sides and a border along each top edge are in the result's own colour, so where the lines cross you can still tell whose each is. The reference's line is the one on top.

Moving the Camera

Drag an animation to move its camera; every animation in the cell moves with it. Behind the car, a drag swings the camera round and over the car, always aimed at it, the scroll wheel moves it in or out, and it keeps its place round the car as the lap plays. In the cockpit, a drag turns the driver's head, up to looking over a shoulder. A double-click puts the camera back, and so does switching between the two views. The layout doesn't save it.


Toolbar

Toolbar

The toolbar along the top of the Trace View provides access to the layout and global options. The Traces and Metrics pages share the same toolbar style:

Button Function
Layout Selector Switch between saved layouts (see Layout Management)
Arrange Open the layout arranger, a full-width dialog for setting the grid's rows, columns, cell types and sizes
Math Channels Define channels from expressions — see Math Channels
Align Shift overlaid traces along the distance axis so laps line up — see Distance Alignment. Only shown when two or more results are loaded.
Settings Open the settings dialog for colours, line widths, grid opacity, and other visual properties
Tutorial Open a popover summarising the layout, cursor and legend, zoom, results, math channels and settings

Everything about a single plot is set on the trace cell itself:

Control Function
Δ time (top-left) Add a row with each result's time delta to the reference. Inert while only one result is loaded
Sectors (top-left) Mark the track's sectors on the map and every trace plot — see Sectors on trace plots
Stats (top-left) Show each result's min, max and mean over the visible range in each row
Fill (top-right) Shade under the reference's traces — see Fill
Channels (top-right) Choose the cell's rows and channels, each channel's precision and range — see Editing Trace Channels
Fullscreen (last) Expand the cell — see Fullscreen Cells

The lap bar under the traces zooms to a lap.


Fullscreen Cells

Every cell in the grid — trace plots, the track map, scatter, distribution, video, contour and table cells — carries an expand icon (the track map's sits inside its camera-control pill). Click it to open that one cell in a large overlay, for a closer look at a single trace or to share one chart on a call without the rest of the grid competing for space. The same control is available on the Metrics page. Close it as you would any dialog to return to the grid exactly as you left it.


Layout Management

Layout Swapper

The Trace View uses the same layout management system as the Metrics page. You can:

  • Save the current layout (grid arrangement, cell types, channel configuration) for reuse
  • Switch between saved layouts using the layout selector dropdown
  • Create new layouts, rename existing ones, or delete layouts you no longer need
  • Search for layouts by name

Layouts persist across sessions. Common workflows include saving layouts for:

  • Speed and ride height — A two-row trace with speed on top and ride heights below, plus a track map
  • Powertrain — Engine RPM, power, torque, and gear in stacked rows
  • G-g analysis — A trace plot alongside a scatter plot configured as a g-g diagram
  • Full overview — A large trace plot with multiple rows, a track map, and a scatter plot

Distance Alignment

Overlaid results do not always start from the same point on track — a telemetry lap's beacon crossing, or a different selected lap, can leave corners and braking zones offset against each other. The Align button in the toolbar (shown whenever two or more results are loaded) opens an alignment panel above the traces — it no longer covers the charts, so you can watch the effect of an adjustment as you make it. Alignment can be computed automatically or set by hand per result.

Control Function
Reference Result The result everything else is aligned to. The longest loaded trace is selected automatically; if it has multiple laps, choose which lap to align against
Alignment Channel The channel used to find the best match. Commonly informative channels (speed, lateral and longitudinal g, steering angle, throttle, engine speed) are listed first, followed by every other channel shared by all loaded results
Lap For multi-lap results, which lap of that result to align
Auto-Align All Computes the best distance offset for every result by cross-correlating the alignment channel. Each shows the resulting shift in metres with a confidence badge — green for a strong match, amber for moderate, red for weak
Manual offset Each non-reference result also has its own slider, nudge buttons and a type-in offset in metres, so you can hand-tune an alignment the automatic pass did not get right
Reset All Clears every alignment. Individual results can also be reset on their own

Alignment Can Wrap Around the Lap

The offset is circular, so a trace can be shifted across the start/finish line. A small negative shift and a large positive one can describe the same physical adjustment.

Missing Channels

A warning appears if any loaded result lacks the selected alignment channel or a distance (sRun) channel — those results cannot be aligned.


Time Delta

Time Delta

When comparing two or more results, enable Δ time on a trace cell to add a row showing the cumulative time difference between the reference result and all other results. This reveals exactly where on the lap one configuration gains or loses time:

  • Positive values — The comparison result is slower than the reference
  • Negative values — The comparison result is faster than the reference
  • Flat sections — No time being gained or lost (similar performance)
  • Steep slopes — Large time differences (e.g., significant speed advantage on a straight or through a corner)

Reference Result

The reference result is marked Ref in the Staging Area, and is the first result loaded by default. Set it with Ref on a row of the Staging Area.


Legend

Each trace plot has a legend band above it, with one line per channel. Every result has an item in the line: a swatch in the result's colour, its value at the cursor, and its Δ to the reference. The reference reads ref ■ value and has no Δ, since everything else is measured against it. Min, max and mean (see Cursor and Statistics) update as you zoom.

Items wrap onto further lines when the results do not fit on one. In a short row the band thins itself out to stay clear of the curves: it drops the Δ first, then the values, down to a line of swatches so you can still tell which colour is which.

Result colours

When multiple results are loaded, a colour legend appears below the toolbar showing the name and colour of each result. Click the colour swatch to change a result's display colour. Click the name to toggle the result on and off — a result toggled off stays in the legend, dimmed, so you can click it straight back on.

The custom colour field in the swatch picker accepts plain CSS colour names such as pink as well as hex codes.

When more than ten results are loaded, the legend collapses into a Results dropdown button (showing the count) rather than wrapping across several rows. Open it to see a scrollable list of every result, each still toggleable individually.

When only a single result is loaded, the legend shows the result name without colour swatches.

Fill

Click Fill in a trace cell's top-right controls to shade under the reference's trace, down to zero. Only the reference is filled, so it reads as a shape that the other results' lines are compared against. The setting is saved with the cell.

Toggling Channel Visibility

In the legend band of each row, click any channel name to toggle its visibility on or off. Hidden channels remain in the configuration but are not displayed in the plot. This is useful for:

  • Temporarily hiding channels without removing them from the layout
  • Quickly comparing different channel combinations
  • Focusing on specific data without reconfiguring rows

Click the hidden channel again to restore visibility.


Settings

Settings Dialog

The Settings dialog (gear icon in the toolbar) has two tabs. Appearance holds everything about how the charts look, set once for every chart:

  • Colours — Change the colour palette used for results and channels
  • Grid Opacity — How visible the grid is on every chart: trace plots, scatter, distribution and the metrics charts, and the ground grid under the 3D track maps. One setting, applied the same way everywhere
  • Line Width — Adjust the thickness of trace lines
  • Sync Trace Cursors — Mirror the hovered cursor across trace chart columns

Units sets the display unit for each channel.


Tips & Best Practices

Start with Speed

Speed (vCar) is the most informative single channel. Start with a speed trace to understand the overall lap structure, then add channels to investigate specific sections.

Use Rows for Related Channels

Group related channels in the same row to share a Y axis — for example, front and rear ride heights together. Put unrelated channels in separate rows so they have independent scales.

Zoom for Detail

The full-lap view gives you the big picture, but most engineering insights come from zooming into specific corners or sections. Use Shift+drag to zoom into a braking zone or corner exit.

Save Purpose-Built Layouts

Create and save layouts for different analysis tasks. A "Quick Overview" layout with speed and g-force is different from a "Suspension Deep Dive" layout with damper velocities, spring travel, and ride heights.

Time Delta for Comparison

When comparing configurations, always enable Δ time. It immediately shows where the lap time difference is coming from — a 0.3s improvement might come entirely from one corner complex, or be spread across the whole lap.

Overlay Telemetry

Upload telemetry from the Results Upload page and load it alongside simulation results. The trace view overlays them directly, making it easy to correlate simulation predictions with real-world data.