TDSE Runtime

Scope

TDSE Runtime is the required core product for every customer. CPU capability is included. GPU and FPGA are optional hardware Add-ons whose build presence, device visibility, authorization, product runtime, and qualification are reported separately.

This manual covers authoring, integration, deployment preparation, target operation, and support from one complete TDSE installation. These are usage scenarios, not products, SKUs, or installation configurations. Builder is the Runtime API and workflow for pack creation; it is not a separate product, library, or package. CLI, Profiler, Telemetry, and plugin integration are technical surfaces delivered around Runtime. TDSE Circuit is a separately purchased domain component with its own user and integration guide.

How To Use This Manual

Follow the shortest path that matches the current task:

For a closed-source evaluation package:

1. verify the installed package and product identity;
2. complete one Builder-to-Runtime tutorial;
3. select the example closest to the intended host;
4. validate CPU behavior before enabling a hardware Add-on;
5. qualify the final host target and payload independently.

Book Structure

• Onboarding: installation, tutorial, examples, and concepts.
• Authoring: Builder inputs, validation, and Runtime Pack creation.
• Runtime integration: lifecycle, step order, variable timestep, concurrency, threading, and multi-model use.
• Hardware and performance: CPU, GPU Add-on, FPGA Add-on, Profiler, Telemetry, backend policy, and tuning.
• Deployment and operations: platform constraints, plugins, diagnostics, troubleshooting, and acceptance checklists.

Exact declarations belong to the API Reference (SDK source: docs/api-reference/c-api.md). Exact command flags belong to the CLI Reference. Current capability and qualification claims belong to the Runtime Backend Support Matrix (SDK source: docs/user-guide/runtime-backend-support-matrix.md). These references are not additional formal user manuals.

Runtime Flow

Runtime consumes an identified Runtime Pack and participates in a host-owned simulation step:

Validated data -> Builder -> Runtime Pack -> TDSE Runtime -> host trial/commit

• Builder creates the reusable pack during model preparation.
• Runtime loads the pack and evaluates the packaged operator.
• The host owns time, scheduling, acceptance, rollback, and global solving.
• A partner target uses the supported Redistributable Payload containing the Runtime binary, selected providers, product identity, dependency records, and notices.

TDSE Runtime is not a general-purpose circuit simulator. Customers whose starting point is a circuit netlist, RAW/SEQ case, or Circuit-owned ModelSpace workflow use TDSE Circuit before the Runtime handoff.

Document Conventions

Typographic conventions used throughout this guide:

The guide uses four callout styles. Each appears here exactly as it does in the rest of the book:

WARNING: Critical information that prevents data loss or incorrect results.

IMPORTANT: Information essential to correct usage.

NOTE: Supplementary information or clarification.

TIP: Shortcut or recommended practice.

Key Terminology

The terminology below covers the technical abbreviations and runtime terms used most often in the handbook.

Core Terms

Lifecycle Terms

Diagnostics Terms

Concurrency Terms

Revision History