TDSE Runtime
AvailableRequired coreThe embeddable execution library, with CPU execution and Builder tools to turn suitable response data into Runtime packs.
CPU execution + Builder authoring included; not separate purchases.
SDK / Platform integration
TDSE SDK for simulation platform developers.
Embed TDSE runtime capability in the simulation product you ship. Keep your solver, your workflow, and your customer experience.
From the Runtime handbookC / 01
Inside your time step.
// Begin. Query. Commit.tdse_step_begin(m, t0 + n * dt, dt);tdse_step_hr(m, hr, nq, &hr_required);tdse_step_ir(m, ir, nq, &ir_required);/* … host composes the response … */tdse_step_commit(m, primary, np);Tutorial impulse tapsh[k] · diagonal
Setup and host code omitted.Read the example
01 / Products & delivery
Start with Runtime. Add what you need.
TDSE Circuit
AvailableOptional domain componentCircuit analysis and subnetwork preparation, with workflows for Runtime qualification.
Requires TDSE Runtime
TDSE GPU Add-on
Limited previewOptional acceleratorGPU execution for supported workloads, qualified per provider and target.
Requires TDSE Runtime
TDSE FPGA Add-on
Limited previewOptional acceleratorFPGA execution for supported Runtime workloads, qualified per provider and target.
Requires TDSE Runtime
Already have suitable response data?
Start with Runtime and its included Builder. Circuit is optional when your existing workflow supplies that data.
Commercial product availability is shown above. Target-platform qualification is separate.
02 / Integration & deployment
From your engineering team to your product.
Prepare the model, connect the host, then package the agreed runtime payload.
- 01 / Development environment
Prepare
Suitable response data, or optional Circuit preparation, feeds Builder to create a Runtime pack.
Model artifactRuntime pack - 02 / Your simulation product
Integrate
Your host-specific adapter connects the solver to Runtime through its documented interfaces.
Inside your hostHost adapter + Runtime - 03 / Customer deployment
Deliver
Authorized partners include the agreed runtime payload and required dependencies in their own installer.
By OEM agreementPartner-embedded Redistributable
One complete engineering installation
Prepare, integrate, validate and inspect deployments with the same installation. End users do not need the full development installation.
- Public headers & libraries
- CMake / pkg-config integration
- CLI & installation diagnostics
- Examples & product manuals
TDSE provides
The SDK, model and data contracts, examples and diagnostics, plus the optional capabilities and Redistributable agreed for your delivery.
Your platform retains
Your solver, scheduling, I/O, front end, model acceptance policy, supported preparation workflow, installer and customer relationship.
Adapter responsibilities & delivery scope
Agree on host-adapter development, maintenance and target acceptance during evaluation. Optional components follow the contracted composition. An integration playbook or example does not establish a released vendor adapter.
03 / Availability & support
A clear starting point for technical review.
Confirm the release, integration surface and target your product will use.
- Engineering platforms
- Windows x86-64 installer and Linux x86-64 relocatable archive.
Other targets & platform notes
Other architectures and target environments need their own delivery and qualification confirmation. Platform notes
- Hardware acceleration
- GPU and FPGA add-ons are in limited preview, qualified per provider and target.
Device, precision & execution scope
Device and precision are selected at model creation; changing them requires a new model. Circuit does not currently execute on FPGA. Execution scope
- API & release compatibility
- The Runtime C ABI has a defined stability contract.
C++ & Circuit compatibility
C++ wrappers and Circuit have their own source and release boundaries; there is no blanket cross-toolchain binary guarantee. Public API overview
- Operational support
- Installation diagnostics and troubleshooting guidance support issue triage.
Release maintenance & support terms
Agree on supported releases, upgrade responsibilities, response terms and target-specific maintenance in your engagement. Troubleshooting guide
Performance evidenceRuntime timing & measurement scope →Public accuracy studiesCase results & reference comparisons →
How published evidence applies to your integration
Product availability, measured hardware performance and host-product qualification are distinct. Published results support the stated cases. Your model, host version and target hardware still need acceptance checks; runtime measurements alone do not establish a real-time deadline or vendor-native integration.
04 / Licensing & evaluation
Company licensing & OEM distribution.
Internal engineering
Annual company licensing
Unlimited internal use within the licensed company.
Unlimited seats and machines.
Company scope & term
Seats, machines, installations and concurrent use do not create additional SKUs. The agreement defines the licensed-company boundary and term.
Inside your commercial product
OEM distribution by agreement
Agree on redistribution rights for the runtime payload embedded in your product.
Redistribution & commercial terms
Redistribution rights come from a partner agreement, not from an internal-use license. OEM pricing, end-customer licensing and legal scope are defined in the contract; redistribution is not a separate SKU.
Begin with one representative model.
Scope the integration, verify the model, qualify the target, and agree on delivery. The evaluation brief brings acceptance criteria, test artifacts and responsibilities into one shared plan.
Read or download the evaluation brief →Documentation for technical review
Your next model is a good place to begin.
Tell us your host platform, target hardware, intended use and evaluation goals.
Keep the first inquiry high-level; do not send confidential models or restricted third-party material.