Lemonergy · Studio block

Signal scope

Plots the connected signal from the engine trace. Every array element has its own named trace channel.

Implementation ID
native-scope
Reviewed
2026-10-27

Behavior

The input passes through unchanged and the Studio chart plots each output channel against simulation time.

Interface

Signal 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 scopeStudio blockin0out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Signal; real 3 array.
out0output1Observed signal; real 3 array.

Parameters

No configurable parameters for this component.

Equations and rules

  • y = u, with an identical shape, element type and quantity

Worked example

Signal scope — worked example

Signal = [2,4,6]. Observed signal at 0 s = [2,4,6].

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Observed signal
out0
0[2, 4, 6]11e-09

Explore the recorded outputs

Signal scope recorded example

Signal scope [1]
Signal scope [1] against timeRecorded synthetic simulation values. Time in seconds; output in —.1.501.750.2520.52.250.752.51—Time (s)
Signal scope [1]: 2 — 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 scope — worked example

Plots the connected signal from the engine trace. Every array element has its own named trace channel.

  1. Signal scope: The input passes through unchanged and the Studio chart plots each output channel against simulation time.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Does not cast values, resample signals or convert units.

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)