Lemonergy · Studio block
Variable integer delay
Selects an input from a connected number of previous sample ticks.
- Implementation ID
native-variable-delay- Reviewed
- 2026-10-27
Behavior
y[k] = u[k − connected integer delay]. The worked example connects this operation to signals in Lemonergy Studio.
Interface
| Name | Direction | Unit | Meaning |
|---|---|---|---|
in0 | input | 1 | Value; real scalar. |
in1 | input | 1 | Delay samples; u32 scalar. |
out0 | output | 1 | Delayed; real scalar. |
Parameters
Defaults are initial model values. Select values for your own model and operating conditions.
| Parameter | Unit | Default | Meaning and limits |
|---|---|---|---|
Sample periodsampleTimeS | s | 0.1 | Exact sample grid period. Elapsed-time integration begins after initialization. Minimum 1e-06 |
Maximum delay samplesparams[0] | 1 | 4 | Configured finite numerical parameter. |
Initial valuestables[0] | 1 | [0] | Configured coefficients or initial values in column-major order. |
Equations and rules
y[k] = u[k − connected integer delay]
Worked example
Variable integer delay — worked example
Value = 5; Delay samples = 0. Delayed at 0 s = 5.
Open Studio example after release →| Output | Time (s) | Expected value | Unit | Absolute tolerance |
|---|---|---|---|---|
Delayedout0 | 0 | 5 | 1 | 1e-08 |
Explore the recorded outputs
Variable integer delay recorded example
Variable integer delay11 actual recorded samples. Lines are visual guides between samples. Synthetic example, not measured cell data.
Read the selected signal as a table
| Time (s) | Value |
|---|
Download the recorded samples (JSON) · Open this Studio example after release
Use in a workflow
Variable integer delay — worked example
Selects an input from a connected number of previous sample ticks.
- Variable integer delay: y[k] = u[k − connected integer delay]. The worked example connects this operation to signals in Lemonergy Studio.
- Use the block reference for settings and connections.
- Implementation tested locally; public release pending.
Connected concepts
Limits and interpretation
- Shapes and element types are explicit. Values must be finite; automatic reshaping and unit conversion are not performed.
Reference basis
This software operation and its numerical conventions are defined by the 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)