LEMONERGY SIMULATION STUDIO

About the subsystem workbench

Early access

Build a model from named subsystems, open its internals, and trace scalar inputs and outputs across model boundaries. Each instance has its own parameter overrides and native state. The compiler expands the hierarchy into the existing scalar equation graph before execution.

This is a separate guest workspace. Edits and simulation results remain in the current tab; they are not saved to account projects or a shared library. Export the model as JSON before leaving or reloading. Import that file to resume, and export solved traces as CSV.

What you can use

  • Nested Subsystem, Inport and Outport structures over the 26 retained scalar primitive types.
  • Named interfaces, versioned definitions, instance parameters, grouping and expansion, validation and diagnostic paths.
  • Two independent batteries and a Roadster battery-system example, executed with the pinned Rust/WASM solver.

Current limits

Interfaces carry individual scalar signals. Bus signals, acausal physical networks, account project storage and reusable shared libraries are not available here. The workbench does not replace the main Simulation Studio.

A new definition can contain up to 128 nodes. Compilation permits up to 2,048 expanded primitives, 4,096 contexts, 32,768 wires and 16 hierarchy levels. Larger existing root models can be imported within the expanded primitive budget.

Numerical verification

The source includes 25 hierarchy/compiler tests and seven native integration tests. They check independent instance state, analytical Coulomb-counting solutions, export/import, nested aliases, model expansion and the complete Roadster comparison.

The Roadster example expands to 390 primitives and 557 connections. Its native traces are compared with the flat reference at every returned sample and primitive, using an absolute tolerance of 10−6 plus a relative tolerance of 10−8. These are software regression and numerical checks, not validation against a physical vehicle or battery.

The native loader verifies the WASM SHA-256 before executing. The retained authoring contracts compile to scalar transport version 2 and run against the separately pinned deployed solver; this release does not introduce a new numerical kernel.