Model architecture · native execution · test evidence
Roadster blocks and submodels
Follow signals across named subsystem boundaries, inspect reusable components and run the authored equations. Download a model to change it in the main Studio.
Inspect and run a model
Loading model catalog.
| Block | Type | Inputs / outputs | Inspect |
|---|
Connections and declared interfaces
Selected block parameters
Choose a block to inspect its parameters.
Native results
Run identity and diagnostics
What the benchmark covers
The reference post informs the capability comparison. Its complete source model, controller matrices, calibrated parameters and proprietary toolboxes were not supplied. These are inspectable Lemonergy models and tests, not a claim to reproduce the post's hidden implementation or establish a real vehicle's manoeuvre safety.
How to use the model
- Open a subsystem to inspect only its immediate blocks. Named input and output ports form the boundary; nested definitions retain their own paths.
- Run the native model, select a result signal, and download the full trace as CSV. The record identifies the exact model checksum and engine SHA-256.
- Download the model and import it into Studio to change parameters, group blocks, reuse a versioned submodel or assemble a physical network.
- Read the retained evidence and assumptions before comparing two runs. A solver result validates the authored equations within the tested envelope; measured hardware data is a separate requirement.
Causal signals and conserving connections
Causal wires carry explicit quantities from output ports to input ports. Typed buses and vectors organize related signals across subsystem boundaries and lower to the native graph. Physical models use a separate network: voltage and current, gas pressure and mass/energy flow, shaft speed and torque, and spatial frame attachments. Sensors and command adapters connect quantities explicitly.
The physical library supports the documented electrical, perfect-gas, shaft and multibody components. Singular circuits, unsupported higher-index equations, invalid initial joints and resource-limit violations refuse rather than produce a success result. The spatial contact and vehicle models use declared lumped assumptions; they are not arbitrary CAD contact or a full Simscape library.
Sources and reproducibility
Capability observations: the reference post. Conserving-network concepts: physical-network principles and gas-system modeling. The implementation, equations, test fixtures and page prose are original Lemonergy work.
This page's runtime is isolated and versioned together with the new benchmark models. Earlier published examples retain their recorded historical engine identities. The source supplement contains the exact benchmark runtime, dependency-free Rust engine source, build instructions, model files, tests and evidence. No external controller code or video media is redistributed.