FA-89214 / Digital logic simulation / Member archive

Functional toggle taken from the first value of a cycle · case 04

Glitchy cycles report functional activity based on a transient value rather than the settled value.

Member previewVariant 4 · 3 implementations · 6 checks per implementation

Case contract

Input [init, waves, cap]: waves[net] is a list of cycles, each a list of sub-cycle values ('0','1','x'). A 0<->1 change costs 2 half-toggles, a change to or from x costs 1, no change 0. Total energy sums half-toggles times cap over every event, comparing each event with the previous event on that net (across cycle boundaries). Functional energy compares only the last value of each non-empty cycle with the previous such value. Nets without a cap entry are unloaded (cap 0). Return [functional, total].

Why this case matters

Power estimation from simulation activity separates functional toggles from glitch toggles; mis-counting either skews dynamic power reports.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
glitch inside a cycle	`[8, 20]`	`[4, 20]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.