ModelSpace v1 Native Import

The installed TDSE Circuit CLI imports a supported native file into the Circuit-owned ModelSpace technical case representation. PSS/E RAW v33 is the locally tested native path. Optional SEQ input is attached as paired metadata evidence; it is not claimed as independently imported topology.

Customer command

tdse circuit import \
  --format psse_raw \
  --input case.raw \
  --seq case.seq \
  --out case.json \
  --approximation-policy warn \
  --out-json import-report.json

The import report identifies the format and revision, source hash, record families, exact mappings, approximations, preserved metadata, rejected records, issue codes, and the generated case identity.

Use allowlist-based acknowledgement only after reviewing a disclosed approximation:

tdse circuit import \
  --format psse_raw \
  --input case.raw \
  --out case.json \
  --approximation-policy forbid \
  --allow-approximation RAW_APPROXIMATION_LOAD_MODEL \
  --out-json import-report.json

With forbid, every disclosed approximation must appear in the allowlist; an unsupported required record, an unallowlisted approximation, or invalid source content fails closed.

Portable directory package reference path

The source-tree qualification tool can assemble the imported technical case and its evidence into the portable ModelSpace v1 directory package:

python tools/modelspace/modelspace_cli.py import \
  --format psse_raw \
  --input case.raw \
  --seq case.seq \
  --tdse-exe path/to/tdse \
  --out case.modelspace

This Python entry point is SOURCE_TREE_REFERENCE tooling. It is not installed as a customer CLI and must not be presented as an additional TDSE executable. ModelSpace import does not expose a retained migration command.

The native RAW mapper supplies the package's authoritative Circuit case. The Python tool projects domain/study views and provenance from that case; it does not convert RAW into a second electrical model. Native registry entries provide model IDs and EMT capabilities. Package validation checks these views against the complete case before execution. RAW equivalent policies are recorded in that case. All execution consumes ModelSpace or its native compiled handle.

Conversion semantics

The package-local conversion report uses tdse.modelspace.conversion_report.v2. Each source and target object has a stable identity, and mappings use the common EXACT, SEMANTICALLY_EQUIVALENT, APPROXIMATED, PRESERVED_AS_OPAQUE, or UNSUPPORTED vocabulary. Unit conversions, inserted defaults, dropped information, vendor extensions, source/output hashes, execution eligibility, and round-trip eligibility are machine-readable.

PRESERVED_AS_OPAQUE data cannot be executed. Unsupported required executable semantics make the package ineligible for execution. A v1 conversion report must be explicitly migrated; it is not silently treated as v2.

Scope boundary

Native ideal voltage/current sources and fixed Thevenin equivalents carry their LTI and region eligibility declarations directly from SDK import. Source waveforms and planning approximation disclosures are separate from that classification. Preserve those declarations when assembling a case; see Independent Sources.

The same native construction rule covers every supported fixed LTI model, including controlled sources, fixed G/B loads and series RC snubbers. load_zip.static_v1 represents a constant-impedance approximation; its name does not imply execution of constant-current or constant-power feedback. SPICE controlled switches retain their actual control terminals or branch, and SPICE BJT/MOSFET imports execute through the corresponding native Q/M models. See ModelSpace Native Model Contracts for the complete installed model scope.

PSS/E RAW v33 is locally tested. Broader RAW/SEQ revisions and native ModelSpace outputs for SPICE, ATP, OpenDSS, GridLAB-D, MATPOWER, PowerWorld, PSCAD, RSCAD, EMTP, HYPERSIM, and other formats are not implied. A commercial simulator bridge requires a real licensed version, source artifact, adapter, execution, result comparison, provenance, and qualification evidence before a compatibility claim can be made.