TDSE Circuit
Circuit product scope, prerequisites, reading paths, and Runtime handoff.
Scope
TDSE Circuit is an optional circuit-domain component that requires TDSE Runtime. This manual starts at circuit inputs and ends at a validated Runtime handoff or a Circuit-owned host-simulation result. It does not redefine the Runtime lifecycle, complete cross-platform installation model, or hardware Add-ons. Current compatibility rules for product/SKU terminology, release profile aliases, CLI placement, and customer JSON identity are recorded in Installation.
The normal commercial compositions are:
| Use case | Required products and Add-ons |
|---|---|
| Circuit authoring or execution on CPU | TDSE Runtime + TDSE Circuit |
| Circuit execution on a qualified GPU provider | TDSE Runtime + TDSE Circuit + TDSE GPU Add-on |
| Circuit FPGA execution | Not currently offered |
CPU capability is included in TDSE Runtime. GPU remains an Add-on and its build presence, device visibility, authorization, product runtime, and qualification must be evaluated separately.
Circuit authoring and execution authorize the runtime and circuit
technical capabilities. Explicit GPU solver selection also authorizes gpu.
The trusted host owns the mapping from products or SKUs to those capability
strings. Configure the process-wide provider as described in the Runtime guide's
Product Authorization chapter before
concurrent Circuit calls.
Choose a Reading Path
| Starting point | Read first | Then continue with |
|---|---|---|
| SPICE-like netlist | Circuit Overview | Circuit Authoring Workflows |
| PSS/E RAW and SEQ data | RAW Import | ModelSpace v1 Native Import |
| Embedded C or C++ integration | Circuit API and Host Integration | Circuit Co-Simulation Workflow |
| Solver or accelerator selection | Circuit Solver Selection and Performance | Runtime Backend Support Matrix (SDK source: docs/user-guide/runtime-backend-support-matrix.md) |
| RTDS, OPAL-RT, Synopsys, or Cadence | Integration Playbooks (SDK source: docs/integrations/README.md) | the partner-specific playbook |
Before using Circuit, complete Runtime installation and first-run verification from the separate TDSE Runtime. Authoring and deployment use the same complete TDSE installation and are not separate products or configurations.
Documentation Boundaries
- Exact command flags belong to the CLI Reference.
- Exact C and C++ declarations belong to the
API Reference (SDK source:
docs/api-reference/c-api.md). - Current support and qualification claims belong to the
Runtime Backend Support Matrix (SDK source:
docs/user-guide/runtime-backend-support-matrix.md). - Partner topology and acceptance steps belong to
Integration Playbooks (SDK source:
docs/integrations/README.md). - Internal architecture, release checks, and evidence-capture procedures remain developer documentation and are not customer product claims.