You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
window-union: a valid placement with no host selections divides by zero #656
A valid placement that leaves no selected expert on the host makes tools/ref/window-union.py terminate with ZeroDivisionError while printing its prediction column.
Observed on unchanged main 69b66367 and on my #637 placement-input branch. This is separate from the negative/duplicate input and exception-identity fixes; those do not change the report arithmetic.
The placement admits 16 experts on each of two layers, all within the valid range. The command prints host slots per row 0.0 of 4, then exits 1 with ZeroDivisionError: float division by zero.
Cause / expected behavior
report, at the pinned main unconditionally formats pu / ps; ps is zero when there are no host selections. The adjacent summary already treats undefined ratios as NaN. The report should represent the no-host-work case explicitly, rather than crash or pretend a meaningful ratio was measured. A no-host-selection case can also arise without every expert being card-resident.
The separate #637 work remains limited to its three claimed CPU-tool items. No performance or NVIDIA execution claim.
I will take this report-only boundary fix. I will keep the no-host-work ratio representation consistent with the existing summary contract, preserve nonzero-work results, and cover the real CLI. This is separate from the placement-input validation in #659; no GPU or model is needed.
Implemented in #663. Zero-host predictions use the existing nan convention; actual zero work remains 0.0. The adjacent empty-window denominator is handled as well. Numeric report regressions and actual CLI checks pass; four positive-work controls are unchanged, and the five owning T0/static checks are green. Placement parsing remains separate in #659.
Activity
Burntgogi commentedon Oct 22, 2026
I will take this report-only boundary fix. I will keep the no-host-work ratio representation consistent with the existing summary contract, preserve nonzero-work results, and cover the real CLI. This is separate from the placement-input validation in #659; no GPU or model is needed.
Burntgogi commentedon Oct 22, 2026
Implemented in #663. Zero-host predictions use the existing
nanconvention; actual zero work remains0.0. The adjacent empty-window denominator is handled as well. Numeric report regressions and actual CLI checks pass; four positive-work controls are unchanged, and the five owning T0/static checks are green. Placement parsing remains separate in #659.