Rene De Ren 4889fdaaf0 docs(contract): close output-contract gaps — mode/manualDemand, Port-2 topic, output manifest
- wiki/Reference-Contracts.md: regenerate data-model (npm run wiki:all) so the
  two live getOutput() keys `mode` and `manualDemand` are documented; refresh
  stale sample values; bump code-ref badge -> a83a85e; add human note describing
  the two control-state keys.
- CONTRACT.md: fix Port-2 outgoing topic registerChild -> child.register
  (registerChild is the deprecated *input* alias, not what the node emits).
- test/_output-manifest.md: add the mandatory output manifest (Port 0/1/2 +
  emitter events + the 15-way fn_status_split fan-out) with honest coverage gaps.
- test/integration/basic-dashboard-flow.test.js: fix stale fan-out count 14->15
  (output 14 = percControl chart added upstream); assert out[14].

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 13:13:11 +02:00
2025-10-07 18:05:54 +02:00

pumpingStation

Wet-well basin model and pump orchestration node for EVOLV.

The detailed documentation lives in wiki/:

  • wiki/functional-description.md defines the shared basin model, pipe reference semantics, safety points, net-flow selection, and child registration behaviour.
  • wiki/modes/ documents control-mode-specific behaviour. For v1.0 the editor exposes levelbased and manual; levelbased supports linear and log curves with separate rising/falling ramp semantics.
  • wiki/diagrams/basin-model.drawio.svg is the current source of truth for the generic basin model.
  • examples/basic-dashboard.flow.json provides a simple Node-RED Dashboard 2 flow with level, volume, demand, net-flow, and safety-state trends.
Description
No description provided
Readme 54 MiB
Languages
JavaScript 89.5%
HTML 10.5%