Lemonergy · Studio block

Dynamic upper-bound check

Checks a scalar against a connected inclusive upper bound.

Implementation ID
native-check-dynamic-upper
Reviewed
2026-10-27

Behavior

pass = (value ≤ connected upper).

Interface

Dynamic upper-bound check interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Dynamic upper-bound checkStudio blockin0in1out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Value; real scalar.
in1input1Upper bound; real scalar.
out0output1Pass; bool scalar.

Parameters

No configurable parameters for this component.

Equations and rules

  • pass = (value ≤ connected upper)

Worked example

Dynamic upper-bound check — worked example

Value = 2; Upper bound = 3. Pass at 0 s = 1.

Open Studio example after release →
Numerical checks for the bundled synthetic example
OutputTime (s)Expected valueUnitAbsolute tolerance
Pass
out0
0111e-09

Explore the recorded outputs

Dynamic upper-bound check recorded example

Dynamic upper-bound check
Dynamic upper-bound check against timeRecorded synthetic simulation values. Time in seconds; output in —.0.500.750.2510.51.250.751.51—Time (s)
Dynamic upper-bound check: 1 — 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 upper-bound check — worked example

Checks a scalar against a connected inclusive upper bound.

  1. Dynamic upper-bound check: pass = (value ≤ connected upper).
    • Use the block reference for settings and connections.
    • Implementation tested locally; public release pending.
Open Studio example after release

Connected concepts

Limits and interpretation

  • Scalar real inputs with the same quantity; equality passes.

Reference basis

This software operation is defined by its 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)