lemonergy· battery engineering courses

Lemonergy · Studio block

Vector assembly

Collects separate scalar inputs into one real vector.

Implementation ID
vector-assemble
Reviewed
2026-10-27

Behavior

Input order defines vector order. The shaped signal can connect directly to compatible native array operations.

Interface

Vector assembly interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Vector assemblyStudio blockelement-0element-1element-2vector
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
element-0input1Element 0; real signal.
element-1input1Element 1; real signal.
element-2input1Element 2; real signal.
vectoroutput1Vector; real signal.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
Vector length
n		13Explicit n used by this worked model.
Physical quantity
quantity		1dimensionlessExplicit quantity used by this worked model.

Equations and rules

  • vector[i] = scalar input i

Worked example

Connect scalar and vector blocks

A = 1; B = 2; C = 3. Result at 1 s = 24.

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

Use in a workflow

Connect scalar and vector blocks

Collects separate scalar inputs into one real vector.

  1. Vector assembly: Input order defines vector order. The shaped signal can connect directly to compatible native array operations.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Inputs are real scalars sharing one quantity; the vector has a fixed declared length.

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)