Lemonergy · Studio block

Dynamic dead zone

Applies a dead zone whose lower and upper edges arrive through input ports.

Implementation ID
native-dynamic-deadzone
Reviewed
2026-10-27

Behavior

Dead-zone edges are connected lower and upper inputs. The worked example connects this operation to signals in Lemonergy Studio.

Interface

Dynamic dead zone interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Dynamic dead zoneStudio blockin0in1in2out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Value; real scalar.
in1input1Lower; real scalar.
in2input1Upper; real scalar.
out0output1Output; real scalar.

Parameters

No configurable parameters for this component.

Equations and rules

  • Dead-zone edges are connected lower and upper inputs

Worked example

Dynamic dead zone — worked example

Value = 3; Lower = -1; Upper = 1. Output at 0 s = 2.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Output
out0
0211e-08

Explore the recorded outputs

Dynamic dead zone recorded example

Dynamic dead zone
Dynamic dead zone against timeRecorded synthetic simulation values. Time in seconds; output in —.1.501.750.2520.52.250.752.51—Time (s)
Dynamic dead zone: 2 — at 0 s

2 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

Dynamic dead zone — worked example

Applies a dead zone whose lower and upper edges arrive through input ports.

  1. Dynamic dead zone: Dead-zone edges are connected lower and upper inputs. 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.
Open Studio example after release

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)