lemonergy· battery engineering courses

Lemonergy · Studio block

Submodel output boundary

Exposes one internal signal as a named typed output of a submodel.

Implementation ID
outport
Reviewed
2026-10-27

Behavior

The boundary connects an internal signal to one declared output interface identifier. Parent wires address that public output. Fixed shaped outputs retain all lanes; virtual vectors are materialized when a native array output is needed.

Interface

Submodel output boundary interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Submodel output boundaryStudio blocky
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
yinput1Internal child signal delivered to the parent through the named output.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
Output interface identifier
port		1yStable identifier of an output declared on this submodel definition. Each declared output has exactly one boundary.

Equations and rules

  • parent instance output y(t) = internal signal y(t)
  • example output = 2 × 3 = 6

Worked example

Typed input and output of a reusable submodel

The example selects the doubling submodel. The parent supplies a constant 3 through the named input u. Inside the child, gain 2 produces 6 and the named output y returns it to the parent. The parent Result signal is 6 at 0.2 seconds. Selecting the alternate tripling definition for another run produces 9.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Parent result after the child output boundary
Result		0.2611e-09

Use in a workflow

Typed input and output of a reusable submodel

Exposes one internal signal as a named typed output of a submodel.

  1. Submodel output boundary: The boundary connects an internal signal to one declared output interface identifier. Parent wires address that public output. Fixed shaped outputs retain all lanes; virtual vectors are materialized when a native array output is needed.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Exactly one boundary is required for each declared child output; private internal nodes cannot be wired directly across the boundary.
  • An entire declared bus may cross the boundary. This does not assemble an external bus hierarchy from separate field-oriented output-boundary nodes.
  • The boundary introduces no sample delay or numerical conversion; scalar, shaped and bus type declarations must match.

Reference basis

Model hierarchy, named interfaces and instance isolation are software contracts verified by the executable example. No external research result or 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)