lemonergy· battery engineering courses

Lemonergy · Studio block

Variant submodel

Selects one compatible submodel definition before compilation.

Implementation ID
variant-subsystem
Reviewed
2026-10-27

Behavior

Only the selected compatible definition is expanded into the execution model. The authoring model retains every choice.

Interface

Variant submodel interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Variant submodelStudio blockuy
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
uinput1Input; real signal.
youtput1Output; real signal.

Parameters

Defaults are initial model values. Select values for your own model and operating conditions.

Configuration fields
ParameterUnitDefaultMeaning and limits
selected
selected		10Explicit selected in the worked model.
choices
choices		1[{"definition": "double", "version": "1", "parameters": {}}, {"definition": "triple", "version": "1", "parameters": {}}]Explicit choices in the worked model.

Equations and rules

  • execution model = selected definition with its own configured parameters

Worked example

Variant submodel — executable model

A3-unit input enters the selected doubling model and produces6. Selecting the tripling model in a new run produces9.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Result
Result		0.2611e-09

Use in a workflow

Variant submodel — executable model

Selects one compatible submodel definition before compilation.

  1. Variant submodel: Only the selected compatible definition is expanded into the execution model. The authoring model retains every choice.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Selection is fixed before the run. Choices must have identical named interfaces; arbitrary symbolic activation expressions and runtime switching are not supported.

Reference basis

This compiler and software type contract is defined by the documented behavior and executable example; no external research result or full external API parity is claimed.

Implementation sources

This reference follows the public interface and locally verified numerical checks for an upcoming release.

Contract: Lemonergy Studio public contract · Verification record: verification-2026-10-27

  • docs/glossary/native-block-verification.json

This implementation and its workflow uses (JSON) · Knowledge graph (JSON-LD)