lemonergy· battery engineering courses

Lemonergy · Studio block

Owned signal copy

Materializes a typed signal as an independent native output, including declared bus leaves.

Implementation ID
signal-copy
Reviewed
2026-10-27

Behavior

Creates separate native output storage for every signal lane. Bus copies preserve named fields and create independent outputs for every leaf.

Interface

Owned signal copy interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Owned signal copyStudio blockin0out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Owned signal; real signal.
out0output1Owned signal; real signal.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
signal quantity
signal.quantity		1dimensionlessExplicit signal quantity in the worked model.
signal shape
signal.shape		1[3]Explicit signal shape in the worked model.
signal element Type
signal.elementType		1realExplicit signal elementType in the worked model.

Equations and rules

  • copy[i] = input[i], with a distinct native output buffer

Worked example

Owned signal copy — executable model

Copying [2,4,6] preserves all three values on distinct output storage.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Result
Result		0.2211e-09
Second copied value
Result/out0/1		0.2411e-09
Third copied value
Result/out0/2		0.2611e-09

Use in a workflow

Owned signal copy — executable model

Materializes a typed signal as an independent native output, including declared bus leaves.

  1. Owned signal copy: Creates separate native output storage for every signal lane. Bus copies preserve named fields and create independent outputs for every leaf.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Copies fixed typed signals and declared buses. It does not create an opaque packed object or support variable-sized data.

Reference basis

This compiler and software type contract is defined by the documented behavior and executable example; no external research result or full external API parity 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)