lemonergy· battery engineering courses

Lemonergy · Studio block

Bounded for iterator

Processes the requested prefix of an input vector through one scalar child, at a single sample time.

Implementation ID
native-for-iterator-submodel
Reviewed
2026-10-27

Behavior

Processes the requested prefix of an input vector through one scalar child, at a single sample time. Outputs are held between accepted samples; numerical evaluation does not commit hidden state.

Interface

Bounded for iterator interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Bounded for iteratorStudio blockin0in1out0out1
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input—Iteration values; real vector [4].
in1input—Iterations; u32 scalar.
out0output—Integral; real scalar.
out1output—Invocations this sample; u32 scalar.

Parameters

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

Configuration fields
ParameterUnitDefaultMeaning and limits
Sample period
sampleTimeS		s1Positive interval between accepted control samples. Outputs hold between these instants.
Minimum 0
Maximum iterations
params[0]		—41–256; also the fixed input vector length.
Reset for each invocation
params[1]		—11 reset child memory/output before the loop; 0 retain between calls.
Child operation
nested		—Discrete integratorOne configurable native computation operation. Its declared input/output types must match the wrapper.
Initial held outputs
tables[0]		—[0]Initial values for all child output lanes, in output order. For independent elements, supply one value per element.

Equations and rules

  • For i = 0 to N − 1: (state, output) ← child(state, input[i])
  • Optionally restore initial state/output before each outer invocation

Worked example

Bounded for iterator worked example

Default editable example at the first accepted sample (t = 0 s). Child operation: discrete integrator. The output checks below are execution oracles for this example.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Integral
out0		010—1e-08
Invocations this sample
out1		04—1e-08

Explore the recorded outputs

Bounded for iterator recorded example

Bounded for iterator / Integral
Bounded for iterator / Integral against timeRecorded synthetic simulation values. Time in seconds; output in —.9.509.750.510110.251.510.52—Time (s)
Bounded for iterator / Integral: 10 — at 0 s

3 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

Bounded for iterator worked example

Processes the requested prefix of an input vector through one scalar child, at a single sample time.

  1. Bounded for iterator: Processes the requested prefix of an input vector through one scalar child, at a single sample time. Outputs are held between accepted samples; numerical evaluation does not commit hidden state.
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Control executes on an explicit sampled clock. Continuous states, history/delay kernels, residual equations, and event-source children are not supported.
  • The wrapper contains one original computation operation; arbitrary multi-block submodels are not supported.
  • A sampled child advances once per invocation using its own declared period. Repeated calls share the same outer timestamp and do not advance physical time.
  • The child has one scalar input and one scalar output. Only the requested prefix of the fixed input vector is processed.

Scientific and mathematical references

These sources explain the scientific and mathematical background. The behavior, interface and limits above define the Lemonergy implementation; a citation does not imply every model option in the source is implemented.

  1. Synchronous Data Flow

    Edward A. Lee, David G. Messerschmitt · Proceedings of the IEEE, 75(9), 1235–1245 · 1987

    Technical reference · Background on actor firing and explicit dataflow. The sampled conditional semantics documented here are Lemonergy design choices, not a claim of a complete SDF implementation.

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)