Lemonergy · Studio block
Float32 bit pattern
Exposes the binary32 representation of a numeric value as an unsigned word.
- Implementation ID
native-float32-bits- Reviewed
- 2026-10-27
Behavior
y = binary32 bit pattern of rounded input, represented as exact u32. The worked example connects this operation to signals in Lemonergy Studio.
Interface
| Name | Direction | Unit | Meaning |
|---|---|---|---|
in0 | input | 1 | Value; real scalar. |
out0 | output | 1 | Bit pattern; u32 scalar. |
Parameters
No configurable parameters for this component.
Equations and rules
y = binary32 bit pattern of rounded input, represented as exact u32
Worked example
Float32 bit pattern — worked example
Value = 1. Bit pattern at 0 s = 1065353216.
Open Studio example after release →| Output | Time (s) | Expected value | Unit | Absolute tolerance |
|---|---|---|---|---|
Bit patternout0 | 0 | 1065353216 | 1 | 1e-08 |
Explore the recorded outputs
Float32 bit pattern recorded example
Float32 bit pattern2 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
Float32 bit pattern — worked example
Exposes the binary32 representation of a numeric value as an unsigned word.
- Float32 bit pattern: y = binary32 bit pattern of rounded input, represented as exact u32. 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
- Finite f64 values are rounded to binary32 then exposed as an exact u32 bit pattern. Binary64 decomposition and configurable sign/exponent/mantissa fields are not implemented.
- 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)