Batch 19: VAV VPACC CUSUM trio (VAV-FC-101/102/103) - #39
Merged
Conversation
…loop topology Two-sided CUSUM charts over the three per-box VPACC error signals (NIST/CEC PIER Project 2.3 §5.1): airflow tracking (101), zone temperature piecewise (102), reheat-off discharge rise (103). The accumulators are the library's first Discrete.UnitDelay feedback loops — the engine's block-level sort admits them without workarounds — with in-graph occupancy reset and first-hour exclusion per the source, and 103 adds a reheat-off arming gate (reset-not-hold, pinned by vectors). Parameter defaults: 102 ships Figure 9's illustrative pair with the vavcal finding that healthy Temperror is identically zero (sigma is a floor, not a statistic); 103 ships the vavcal-measured 0.44/0.39 degC baseline and Table 5's Iowa-campaign k=3 with an alarm limit in its published range. All commissioning values per §5.1.5. points/vav.points.json gains vav_dat, sat, occ_scheduled; harness gains the vavcal calibration mode. 92 rules verify green at the pin. The three authoring agents were killed mid-write by server-side API errors (500/529); rules and vectors survived and verified, the missing cards/diagrams were completed from their output. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The VPACC family (NIST/CEC PIER Project 2.3 §5.1) as three two-sided CUSUM rules — the library's first feedback-loop topology (Discrete.UnitDelay accumulators; the engine's emit-before sort admits the cycle because UnitDelay declares no feedthrough):
All three gate occupancy in-graph (Switch reset + TrueDelay first-hour exclusion) because CUSUM needs state cleared, not output muted; yOccupiedOk/yReheatOk are evaluability flags, yHigh/yLow sub-condition directions per SCHEMA.
Also: vav README index + VPACC section, vav-min-flow-reheat Applies-To wiring, points dict (vav_dat / sat / occ_scheduled with batch contracts), simharness vavcal mode, root README count 89 → 92.
Verification
cargo verify --all green at e2ff2f8 (92 rules); svg fitment + id-band lints clean. Authoring agents were killed by server-side API errors mid-batch; their verified rules/vectors survived and the remaining cards/diagrams were completed from that output.
🤖 Generated with Claude Code