lemonergy· battery engineering courses

Lemonergy · Studio block

Compare to zero

Compares each input value with zero.

Implementation ID
native-compare-zero
Reviewed
2026-10-27

Behavior

y = (u comparison 0). The worked example connects this operation to signals in Lemonergy Studio.

Interface

Compare to zero interfaceInputs or arguments on the left, observed outputs on the right. Conserving terminals appear below the component. The tables give units and behavior.Compare to zeroStudio blockin0out0
Original Lemonergy interface view. Lines identify ports; they are not a completed simulation circuit.
Ports and observed outputs
NameDirectionUnitMeaning
in0input1Value; real scalar.
out0output1Result; bool scalar.

Parameters

Defaults are initial model values. Select values for your own model and operating conditions.

Configuration fields
ParameterUnitDefaultMeaning and limits
Comparison
params[0]		100 <; 1 ≤; 2 =; 3 ≠; 4 ≥; 5 >.

Equations and rules

  • y = (u comparison 0)

Worked example

Compare to zero — worked example

Value = -2. Result at 0 s = 1.

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

Explore the recorded outputs

Compare to zero recorded example

Compare to zero
Compare to zero against timeRecorded synthetic simulation values. Time in seconds; output in —.0.500.750.2510.51.250.751.51—Time (s)
Compare to zero: 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

Compare to zero — worked example

Compares each input value with zero.

  1. Compare to zero: y = (u comparison 0). 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)