lemonergy· battery engineering courses

Lemonergy · Studio block

Variant branch end

Selects the active input at the end of a compile-time branch region.

Implementation ID
variant-end
Reviewed
2026-10-27

Behavior

Keeps one input path at the end of a statically selected branch region.

Interface

Variant branch end 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 endStudio blockin0in1out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Branch 0; real signal.
in1input1Branch 1; real signal.
out0output1Branch 0; 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

  • y = configured active input

Worked example

Variant branch end — executable model

The first input3 is selected and doubled downstream to6.

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 end — executable model

Selects the active input at the end of a compile-time branch region.

  1. Variant branch end: Keeps one input path at the end of a statically selected branch region.
    • 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 configured before compilation; inactive paths are omitted rather than dynamically merged.

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)