lemonergy· battery engineering courses

Lemonergy · Studio block

Variant branch start

Starts a statically selected output branch with inactive-branch elimination.

Implementation ID
variant-start
Reviewed
2026-10-27

Behavior

Starts a statically selected branch region by activating one output path.

Interface

Variant branch start interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Variant branch startStudio blockin0out0out1
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Branch 0; real signal.
out0output1Branch 0; real signal.
out1output1Branch 1; 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.
count
count		12Explicit count in the worked model.
signal quantity
signal.quantity		1dimensionlessExplicit signal quantity in the worked model.
signal shape
signal.shape		1[]Explicit signal shape in the worked model.
signal element Type
signal.elementType		1realExplicit signal elementType in the worked model.

Equations and rules

  • active branch = configured selection

Worked example

Variant branch start — executable model

The first branch takes input3 through gain2, producing6.

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 branch start — executable model

Starts a statically selected output branch with inactive-branch elimination.

  1. Variant branch start: Starts a statically selected branch region by activating one output path.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Selected branch paths must remain consistent with the corresponding end selection. There are no symbolic condition expressions.

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)