lemonergy· battery engineering courses

Lemonergy · Studio block

Signal visibility scope

Allows one named sender to be resolved inside this scope and its descendants.

Implementation ID
goto-visibility
Reviewed
2026-10-27

Behavior

Makes one local named sender available to receivers in descendant submodels. The nearest enclosing visibility declaration determines the source.

Interface

Signal visibility scope interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Signal visibility scopeStudio block
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.

This reference describes a studio block; its configuration fields are listed below. It has no connected Studio ports.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
tag
tag		1signalExplicit tag 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

  • receiver = nearest visible named source

Worked example

Signal visibility scope — executable model

A root sensor value3 is received inside a child submodel and doubled 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

Signal visibility scope — executable model

Allows one named sender to be resolved inside this scope and its descendants.

  1. Signal visibility scope: Makes one local named sender available to receivers in descendant submodels. The nearest enclosing visibility declaration determines the source.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • A visibility declaration must match exactly one sender and its declared type in the same scope. No global lookup outside the model hierarchy.

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)