Lemonergy · Studio block

Complex to real and imaginary

Separates each complex value into real and imaginary components.

Implementation ID
native-complex-parts
Reviewed
2026-10-27

Behavior

z = real + i imaginary. The worked example connects this operation to signals in Lemonergy Studio.

Interface

Complex to real and imaginary interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Complex to real and imaginaryStudio blockin0out0out1
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Complex; complex 1 array.
out0output1Real; real 1 array.
out1output1Imaginary; real 1 array.

Parameters

No configurable parameters for this component.

Equations and rules

  • z = real + i imaginary

Worked example

Complex to real and imaginary — worked example

Complex = [3,4]. Real at 0 s = [3]; Imaginary at 0 s = [4].

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Real
out0
0[3]11e-08
Imaginary
out1
0[4]11e-08

Explore the recorded outputs

Complex to real and imaginary recorded example

Complex to real and imaginary / Real [1]
Complex to real and imaginary / Real [1] against timeRecorded synthetic simulation values. Time in seconds; output in —.2.502.750.2530.53.250.753.51—Time (s)
Complex to real and imaginary / Real [1]: 3 — 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

Complex to real and imaginary — worked example

Separates each complex value into real and imaginary components.

  1. Complex to real and imaginary: z = real + i imaginary. The worked example connects this operation to signals in Lemonergy Studio.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Shapes and element types are explicit. Values must be finite; automatic reshaping and unit conversion are not performed.

Reference basis

This software operation and its numerical conventions are defined by the 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)