Lemonergy · Studio block

Vector concatenate

Joins input arrays in their declared order into one output vector.

Implementation ID
native-vector-concatenate
Reviewed
2026-10-27

Behavior

y = [u₁; u₂; …]. The worked example connects this operation to signals in Lemonergy Studio.

Interface

Vector concatenate interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Vector concatenateStudio blockin0in1out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1A; real 2 array.
in1input1B; real 2 array.
out0output1Combined; real 4 array.

Parameters

No configurable parameters for this component.

Equations and rules

  • y = [u₁; u₂; …]

Worked example

Vector concatenate — worked example

A = [1,2]; B = [3,4]. Combined at 0 s = [1,2,3,4].

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

Explore the recorded outputs

Vector concatenate recorded example

Vector concatenate [1]
Vector concatenate [1] against timeRecorded synthetic simulation values. Time in seconds; output in —.0.500.750.2510.51.250.751.51—Time (s)
Vector concatenate [1]: 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

Vector concatenate — worked example

Joins input arrays in their declared order into one output vector.

  1. Vector concatenate: y = [u₁; u₂; …]. 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)