Lemonergy · Studio block
Accepted solver-step memory
Returns the input from the previous accepted solver step.
- Implementation ID
native-step-memory- Reviewed
- 2026-10-27
Behavior
y at an accepted major point = input from the previous accepted point. The worked example connects this operation to signals in Lemonergy Studio.
Interface
| Name | Direction | Unit | Meaning |
|---|---|---|---|
in0 | input | 1 | Input; real scalar. |
out0 | output | 1 | Previous accepted input; real scalar. |
Parameters
Defaults are initial model values. Select values for your own model and operating conditions.
| Parameter | Unit | Default | Meaning and limits |
|---|---|---|---|
Initial outputtables[0] | 1 | [0] | Configured coefficients or initial values in column-major order. |
Equations and rules
y at an accepted major point = input from the previous accepted point
Worked example
Accepted solver-step memory — worked example
Input = 5. Previous accepted input at 0 s = 0.
Open Studio example after release →| Output | Time (s) | Expected value | Unit | Absolute tolerance |
|---|---|---|---|---|
Previous accepted inputout0 | 0 | 0 | 1 | 1e-08 |
Explore the recorded outputs
Accepted solver-step memory recorded example
Accepted solver-step memory2 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
Accepted solver-step memory — worked example
Returns the input from the previous accepted solver step.
- Accepted solver-step memory: y at an accepted major point = input from the previous accepted point. 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
- Previous accepted major-step input with explicit initial output; pure trial reads and transactional accepted-step commits. Rejected steps do not advance memory.
- 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)