dc27a569d9be6e1d0e1d2c7538c30a6bb794c945
PS subscribes to MGC's flow.predicted.downstream and uses it as the outflow estimate for net-flow computation. MGC was only writing to DOWNSTREAM inside optimalControl (the optimizer's bestFlow TARGET, not the achieved aggregate), and to AT_EQUIPMENT in handlePressureChange. During transients — e.g. demand dropping to dead-band keep-alive while pumps are still ramping down from full throttle — PS saw a stale 25 m³/h target on DOWNSTREAM while pumps were physically delivering 500+ m³/h. NetFlow looked small and stable when the basin was actually draining fast. flow.act = sum of every pump's current predicted output = achieved aggregate. Mirror it onto DOWNSTREAM so PS gets a live signal on every pump flow/pressure update, not just every MGC.handleInput. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
EVOLV
Edge-Layer Evolution for Optimized Virtualization
Description
Languages
JavaScript
97.8%
HTML
2.2%