Prediction
Prediction takes a Digital Twin and an input scenario, and returns the most likely value of a target variable with a confidence interval.
For the workflow that produces a Digital Twin in the first place, see Step 5: Build Digital Twin.
Why a Digital Twin prediction beats an LLM prediction
A prediction from a Digital Twin gives you three things an LLM cannot.
Repeatable. The same input always produces the same output.
Explainable. The prediction comes from a DAG — a system of equations whose causal logic can be inspected end-to-end.
Calibrated. Every prediction carries a known confidence interval and an understood distribution of outcomes.
A completed Prediction looks like this.

Starting a simulation
Open a Digital Twin from the Digital Twins list, open its Simulations row (or click Run Simulation in the toolbar), then click New Simulation. This opens the type picker — choose Prediction.

Step 1: Choose target variables
Target variables are the outcomes you want to predict. Selecting a target removes it from the input table on the next step — you supply its drivers, not the target itself.

Step 2: Provide input records
Each row is one scenario. RootCause filters the columns to variables with a causal path to the target.
The form starts empty; you cannot run the simulation until a target is chosen and the required inputs are filled.

Numeric fields take values directly; categorical fields offer dropdowns. Pick <MISSING> for any field you don't have a value for.

The tabs above the form offer three other input methods:
File Upload — a CSV (or tab-separated) file with one row per scenario.
Dataset — pull rows directly from a saved dataset. Each dataset also carries a button to score every row on the server instead of loading them into the browser, which is the way to run a prediction over a large one. At most 10,000 rows are read, and the button names the figure when the dataset is bigger than that. The step then names the dataset in place of the input table, with Enter records instead to go back.
Field Input (default) — the form view shown above.
Rows loaded from a dataset or a source keep their id column even though it is not a variable of the twin, so the result names each record rather than numbering it.
Step 3: Confidence level
The default of 0.95 means the model is 95% confident the actual value falls within the shown range. Higher confidence widens the interval; lower narrows it. Leave the default unless you have a specific reason to change it.
Reading the result
Clicking Run Simulation opens the result page: the run's title and status pills, then the predictions table — the run shown at the top of this page. The run's configuration is shown under its row in the run list. The table gives each input scenario, the predicted class or value, and the confidence interval, and exports as CSV or JSON from its own button. For a PDF, tick the run in the list, click Export 1 as report, and use Export PDF in the report editor.
Who's at risk
A run with a categorical target opens with Who's at risk above the predictions table: every record ranked by the model's chance of one value, lowest first, so the records in most trouble come first. Where the run predicted more than one categorical target, a picker chooses which one ranks the list, and a second control chooses the value — Churn = No, Approved = Yes — whose chance is read.
At risk below is the line, a slider running from 50% up to 95% and starting at 50%, the model's own line between outcomes. A histogram under it shows how the records are spread across the range, and a sentence counts how many fall below the line.
Each row names the record by its id column, with its position in the run beside it, then its chance of the chosen value, the value the model predicts for it, and up to four of the target's direct causes for context. Records below the line start ticked; the checkboxes adjust the selection, Select the N below the line restores it, and Clear selection empties it. Moving the slider re-selects everything below the new line.
Find best actions for N records hands the ticked records to Best Action as a new run, already set to the same target and value, and titled after them — "Best actions for 21 records below 50% Churn = No". A line raised above 50% comes along as the target's success line, so the solver has to get each record over the same bar. A single run takes at most 500 records; tick more and the 500 most at risk are the ones carried over. The records travel as a reference to this prediction rather than as copied values, so the Best Action run names this run as its parent in the twin's lineage bar.
Past simulations
The Simulations panel lists every run against the twin, with a search field and a Filter button. Runs triggered by an Application are listed too, marked with an App badge; set the filter's Ran by to Apps or People to narrow to one or the other. Whenever a search or a filter is holding runs back, the panel header says so — 1 of 2 · 1 hidden — and a Show all button beside it clears the search and the filters in one click. The Simulations row on the twin's Home opens the same list.

Outside the UI
This simulation runs from the Python SDK and from the REST API, with the same configuration the wizard collects.
Over REST it is a scenario on POST /api/v1/workspaces/{workspaceId}/simulations with "type": "prediction". Prediction is a static-twin family: a temporal twin projects forward with a Forecast instead. The result carries one row per input record, in the order you sent them. sampleFrom predicts a whole dataset on the server rather than sending its rows, and GET /simulations/{id}/predictions reads a completed run back as the same ranked worklist the result page shows.
See Working with Digital Twins for the SDK, and Running Simulations over REST for the request body.
Other Simulation Types
Intervention — change a single variable and observe propagation.
Optimization — find the input combination that maximizes or minimizes a target.
Best Action — find the minimum change needed to reach a target outcome.
Explanation — understand the drivers and impacts behind an outcome.
Root Cause Analysis — diagnose the cause of a specific abnormal value.
Anomaly Scan & Diagnosis — scan every variable for anomalies and diagnose each one.
See Step 6: Run Simulations — general overview.
Last updated

