Lemonergy · Studio block

Named signal sender

Names a local typed signal so receivers can use it without a long visible wire.

Implementation ID
goto
Reviewed
2026-10-27

Behavior

Named routing compiles to the original connected source. It adds no delay, copy or hidden storage.

Interface

Named signal sender interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Named signal senderStudio blocksignal
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
signalinputvoltagecell-voltage; real signal.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
Local signal tag
tag
1cell-voltageExplicit tag used by this worked model.
Physical quantity
quantity
1voltageExplicit quantity used by this worked model.
Signal dimensions
shape
1[]Explicit shape used by this worked model.
Element type
elementType
1realExplicit elementType used by this worked model.

Equations and rules

  • local tag = connected source

Worked example

Route a local named signal

Sensor = 3. Scaled-voltage at 1 s = 6.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Scaled-voltage
Scaled-voltage
16voltage1e-09

Use in a workflow

Route a local named signal

Names a local typed signal so receivers can use it without a long visible wire.

  1. Named signal sender: Named routing compiles to the original connected source. It adds no delay, copy or hidden storage.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Exactly one sender per tag in a scope; cross-scope visibility and global tags are not supported.

Reference basis

This software operation is defined by its public contract and worked example; no external research result 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)