Lemonergy · Studio block

Signal terminator

Consumes a declared signal without forwarding its numeric value. The connected flag confirms that validation and execution succeeded.

Implementation ID
native-terminator
Reviewed
2026-10-27

Behavior

connected = true after the input contract is validated.

Interface

Signal terminator interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Signal terminatorStudio blockin0out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Unused signal; real 3 array.
out0output1Connected; bool scalar.

Parameters

No configurable parameters for this component.

Equations and rules

  • connected = true after the input contract is validated

Worked example

Signal terminator — worked example

Unused signal = [2,4,6]. Connected at 0 s = 1.

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

Explore the recorded outputs

Signal terminator recorded example

Signal terminator
Signal terminator against timeRecorded synthetic simulation values. Time in seconds; output in —.0.500.750.2510.51.250.751.51—Time (s)
Signal terminator: 1 — at 0 s

2 actual recorded samples. Lines are visual guides between samples. Synthetic example, not measured cell data.

Download the recorded samples (JSON) · Open this Studio example after release

Use in a workflow

Signal terminator — worked example

Consumes a declared signal without forwarding its numeric value. The connected flag confirms that validation and execution succeeded.

  1. Signal terminator: connected = true after the input contract is validated.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Reports a Boolean connection flag; no numeric downstream copy of the consumed input is produced.

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)