Lemonergy · Studio block
Invocation count fan-out
Copies one accepted-sample call count to fixed typed branches. It does not impose side-effect order between independent downstream models.
- Implementation ID
native-call-count-split- Reviewed
- 2026-10-27
Behavior
Copies one accepted-sample call count to fixed typed branches. It does not impose side-effect order between independent downstream models. Outputs are held between accepted samples; numerical evaluation does not commit hidden state.
Interface
| Name | Direction | Unit | Meaning |
|---|---|---|---|
in0 | input | — | Calls; u32 scalar. |
out0 | output | — | Branch 1; u32 scalar. |
out1 | output | — | Branch 2; u32 scalar. |
Parameters
Defaults are initial model values. Select values for your own model and operating conditions.
| Parameter | Unit | Default | Meaning and limits |
|---|---|---|---|
Sample periodsampleTimeS | s | 1 | Positive interval between accepted control samples. Outputs hold between these instants. Minimum 0 |
Branch countparams[0] | — | 2 | 1–32. Downstream consumers must use the same declared sample clock. |
Equations and rules
branch[i] = accepted input call count, for every configured branch
Worked example
Invocation count fan-out worked example
Default editable example at the first accepted sample (t = 0 s). The output checks below are execution oracles for this example.
Open Studio example after release →| Output | Time (s) | Expected value | Unit | Absolute tolerance |
|---|---|---|---|---|
Branch 1out0 | 0 | 3 | — | 1e-08 |
Branch 2out1 | 0 | 3 | — | 1e-08 |
Explore the recorded outputs
Invocation count fan-out recorded example
Invocation count fan-out / Branch 13 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
Invocation count fan-out worked example
Copies one accepted-sample call count to fixed typed branches. It does not impose side-effect order between independent downstream models.
- Invocation count fan-out: Copies one accepted-sample call count to fixed typed branches. It does not impose side-effect order between independent downstream models. Outputs are held between accepted samples; numerical evaluation does not commit hidden state.
- Use the block reference for settings and connections.
- Implementation tested locally; public release pending.
Connected concepts
Limits and interpretation
- Control executes on an explicit sampled clock. Continuous states, history/delay kernels, residual equations, and event-source children are not supported.
- Fan-out does not impose execution or side-effect order on independent downstream models. Counts are limited to 0–256; 1–32 branches are supported.
Scientific and mathematical references
These sources explain the scientific and mathematical background. The behavior, interface and limits above define the Lemonergy implementation; a citation does not imply every model option in the source is implemented.
- Synchronous Data Flow
Edward A. Lee, David G. Messerschmitt · Proceedings of the IEEE, 75(9), 1235–1245 · 1987
Technical reference · Background on actor firing and explicit dataflow. The sampled conditional semantics documented here are Lemonergy design choices, not a claim of a complete SDF implementation.
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)