Executable model
Canonical dynamic model for simulation and rollout.
NDC Model Compiler
Executable nonlinear dynamics from measurements
Provide time-ordered data, one target and the inputs available at runtime. NDC searches alternative dynamic structures, challenges them in held-out free-run and packages the selected result as an executable, verifiable artifact.
From €390 · one target · standard processing allowance · additional usage, when required, is shown in the account before launch.
No supplied equationsHeld-out free-runExplicit support boundaryExecutable delivery
INPUT
Prepared trajectories
Chronological observations, one target, measured inputs or controls, and stable sample timing or timestamps.
→
COMPILER
Build, challenge, select
Alternative dynamics, memory and cross-signal structures are tested under the declared data boundary.
→
OUTPUT
Verified artifact
Runtime, validation evidence, Nonlinearity Passport, support boundary, manifest and checksums.
Why NDC
A useful dynamic model must survive its own predictions
One-step fit can look strong while a model drifts or becomes unstable as soon as it feeds back its own output. NDC therefore records both one-step evidence and a chronological held-out free-run.
HELD-OUT TAIL
Truth is removed after the initial history
The model receives allowed future inputs, but not the true future target. Each predicted target becomes part of the next state. Accumulated error is visible rather than hidden by teacher forcing.
- Drift and instability are exposed
- Supported prediction coverage is recorded
- Unsupported operating regions remain explicit
observed historyheld-out free-run
held-out targetfree-run prediction
Illustration of a free-run comparison, not a measured benchmark. Published measurements are linked below.
Published model results
Six published cases below the declared stable baseline
The six published cases report free-run NRMSE ratios from 0.10× to 0.91× against the declared baselines. They are recorded benchmark cases, not a guarantee for a new dataset or a statement that every case was recompiled in the present release.
6 / 6recorded wins
0.10×best current ratio
0.91×closest current ratio
free-runprimary dynamic check
Automated compile
Six stages from data to a hand-off package
01 · CHECK
Validate structure
Chronology, target availability, selected signals and usable sample count.
02 · SNAPSHOT
Build trajectories
Align selected views and create a reproducible fit and validation boundary.
03 · SEARCH
Explore structures
Evaluate dynamics, lags, memory, self-effects and cross-signal interactions.
04 · ESTIMATE
Fit and identify
Estimate coefficients, numerical rank and weakly identifiable directions.
05 · CHALLENGE
Run dynamic tests
Measure one-step and held-out free-run behaviour with accumulated error.
06 · DELIVER
Bind the artifact
Package the selected runtime, Passport, support boundary and verifier.
What you receive
More than a coefficient file
Lightweight runtime
Run the delivered model without rebuilding the compiler pipeline.
Validation evidence
One-step and free-run metrics, baseline comparison and rollout behaviour.
Nonlinearity Passport
Structure, nonlinear order profile, rank and uncertainty where estimable.
Support boundary
Observed operating ranges and explicit behaviour outside them.
Manifest and checksums
Versioned request, input identity and hash-bound delivery files.
From model to action
Use the same verified dynamics downstream
After a model passes its declared free-run and support checks, the next product route is control: real-time SDRE for a strict update cadence or full-model NMPC where a slower optimisation loop is acceptable.
BOUNDARY
A compiled model is not automatically control-ready
Controller compatibility still depends on measured state, actual applied commands, update cadence, declared limits and the requested objective. Unsupported configurations must remain rejected.
Pricing
Start with one verified model
NDC is a productised compile, not a consulting engagement. The account confirms the current input limits and any additional processing before the job is launched.
NDC COMPILEfrom €390
One model for one target under the standard processing allowance.
- Executable model and runtime
- One-step and held-out free-run validation
- Nonlinearity Passport
- Support / OOD boundary
- Manifest, checksums and verifier
Questions
Before you compile
Can NDC work with my CSV?
Yes when the file represents ordered trajectories with a target and the inputs needed for future rollout. General cleaning and gap recovery are separate automated products; battery cycler data uses the Battery workflow.
What is one target?
The measured response the model must reproduce—for example temperature, voltage, position, flow or a quality indicator. Each target produces a separate verified model.
Does the interaction map prove causality?
No. It reports predictive relationships—signals and lags that improve prediction. Causal conclusions require a separate experimental design.
What happens outside the observed support?
The current workspace offers “Refuse unsupported inputs” and “Refuse extrapolation”. The selected policy is included in the compile request. Follow the policy recorded in the delivered artifact; an output outside validated conditions is not a validated prediction.
NDC