lemonergy· battery engineering courses

Lemonergy · Studio block

Submodel input boundary

Makes one named parent input available inside a submodel without changing its value or timing.

Implementation ID
inport
Reviewed
2026-10-27

Behavior

The boundary refers to one input in the child definition interface. The compiler resolves it to the signal supplied by the parent instance. Physical quantity, numeric element type and dimensions must agree, including when the declared input is an entire named bus.

Interface

Submodel input 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 input boundaryStudio blocku
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
uoutput1The parent-provided scalar is available as an internal child signal.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
Input interface identifier
port		1uStable identifier of an input declared on this submodel definition. Each declared input has exactly one boundary.

Equations and rules

  • internal u(t) = parent instance input u(t)
  • example input = 3

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

Makes one named parent input available inside a submodel without changing its value or timing.

  1. Submodel input boundary: The boundary refers to one input in the child definition interface. The compiler resolves it to the signal supplied by the parent instance. Physical quantity, numeric element type and dimensions must agree, including when the declared input is an entire named bus.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • This block belongs inside a submodel definition, not at the root model scope. Missing, duplicate and undeclared boundary identifiers are rejected.
  • A bus boundary carries its complete declared bus. It does not define or select individual external bus fields as a field-oriented boundary block would.
  • The boundary introduces no delay, resampling, cast or unit conversion.

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)