Lemonergy · Studio block
Array step
Changes an entire signal from its before value to its after value at an exact time.
- Implementation ID
native-step- Reviewed
- 2026-10-27
Behavior
y(t) = before, t < change time; after, t ≥ change time. The worked example connects this operation to signals in Lemonergy Studio.
Interface
| Name | Direction | Unit | Meaning |
|---|---|---|---|
out0 | output | 1 | Value; real scalar. |
Parameters
Defaults are initial model values. Select values for your own model and operating conditions.
| Parameter | Unit | Default | Meaning and limits |
|---|---|---|---|
Change timeparams[0] | s | 0.5 | Configured finite numerical parameter. |
Before valuestables[0] | 1 | [0] | Configured coefficients or initial values in column-major order. |
After valuestables[1] | 1 | [1] | Configured coefficients or initial values in column-major order. |
Equations and rules
y(t) = before, t < change time; after, t ≥ change time
Worked example
Array step — worked example
Uses the configured source values. Value at 0 s = 0; Value at 0.5 s = 1.
Open Studio example after release →| Output | Time (s) | Expected value | Unit | Absolute tolerance |
|---|---|---|---|---|
Valueout0 | 0 | 0 | 1 | 1e-08 |
Valueout0 | 0.5 | 1 | 1 | 1e-08 |
Explore the recorded outputs
Array step recorded example
Array step3 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
Array step — worked example
Changes an entire signal from its before value to its after value at an exact time.
- Array step: y(t) = before, t < change time; after, t ≥ change time. 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
- Before and after arrays must have exactly the same shape and element type.
- 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)