znetsixe 0d7af6bfff
Some checks failed
CI / lint-and-test (push) Has been cancelled
refactor(examples): split pumpingstation demo across 4 concern-based tabs + add layout rule set
The demo was a single 96-node tab with everything wired directly. Now
4 tabs wired only through named link-out / link-in pairs, and a
permanent rule set for future Claude sessions to follow.

Tabs (by concern, not by data flow):

  🏭 Process Plant   only EVOLV nodes (3 pumps + MGC + PS + 6 measurements)
                     + per-node output formatters
  📊 Dashboard UI   only ui-* widgets, button/setpoint wrappers, trend
                     splitters
  🎛️ Demo Drivers   random demand generator + state holder. Removable
                     in production
  ⚙️ Setup & Init   one-shot deploy-time injects (mode, scaling,
                     auto-startup, random-on)

Cross-tab wiring uses a fixed named-channel contract (cmd:demand,
cmd:mode, cmd:setpoint-A, evt:pump-A, etc.) — multiple emitters can
target a single link-in for fan-in, e.g. both the slider and the random
generator feed cmd:demand.

Bug fixes folded in:

1. Trend chart was empty / scrambled. Root cause: the trend-feeder
   function had ONE output that wired to BOTH flow and power charts,
   so each chart received both flow and power msgs and the legend
   garbled. Now: 2 outputs (flow → flow chart, power → power chart),
   one msg per output.

2. Every ui-text and ui-chart fell on the (0, 0) corner of the editor
   canvas. Root cause: the helper functions accepted x/y parameters
   but never assigned them on the returned node dict — Node-RED
   defaulted every widget to (0, 0) and they piled on top of each
   other. The dashboard render was unaffected (it lays out by group/
   order), but the editor was unreadable. Fixed both helpers and added
   a verification step ("no node should be at (0, 0)") to the rule set.

Spacing convention (now codified):
- 6 lanes per tab at x = [120, 380, 640, 900, 1160, 1420]
- 80 px standard row pitch, 30-40 px for tight ui-text stacks
- 200 px gap between sections, with a comment header per section

New rule set: .claude/rules/node-red-flow-layout.md
- Tab boundaries by concern
- Link-channel naming convention (cmd:/evt:/setup: prefixes)
- Spacing constants
- Trend-split chart pattern
- Inject node payload typing pitfall (per-prop v/vt)
- Dashboard widget rules (every ui-* needs x/y!)
- Do/don't checklist
- Link-out/link-in JSON cheat sheet
- 5-step layout verification before declaring a flow done

CLAUDE.md updated to point at the new rule set.

Verified end-to-end on Dockerized Node-RED 2026-04-13: 168 nodes across
4 tabs, all wired via 22 link-out / 19 link-in pairs, no nodes at
(0, 0), pumps reach operational ~5 s after deploy, MGC distributes
random demand, trends populate per pump.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-13 16:13:27 +02:00

EVOLV — Edge-Layer Evolution for Optimized Virtualization

Node-RED custom nodes package voor de automatisering van afvalwaterzuiveringsinstallaties. Ontwikkeld door het R&D-team van Waterschap Brabantse Delta. Volgt de ISA-88 (S88) batch control standaard.

Nodes

Node Functie S88-niveau
rotatingMachine Individuele pomp/compressor/blower aansturing Equipment
machineGroupControl Multi-pomp optimalisatie (BEP-Gravitation) Unit
pumpingStation Pompgemaal met hydraulische context Unit
valve Individuele klep modellering Equipment
valveGroupControl Klep groep coordinatie Unit
reactor Biologische reactor (ASM kinetiek) Unit
settler Nabezinker / slibscheiding Unit
monster Multi-parameter biologische monitoring Equipment
measurement Sensor signaalconditionering Control Module
diffuser Beluchting aansturing Equipment
dashboardAPI InfluxDB telemetrie + FlowFuse dashboards
generalFunctions Gedeelde bibliotheek (predict, PID, convert, etc.)

Architectuur

Elke node volgt een drie-lagen patroon:

  1. Entry file (<naam>.js) — registratie bij Node-RED, admin endpoints
  2. nodeClass (src/nodeClass.js) — Node-RED adapter (tick loop, routing, status)
  3. specificClass (src/specificClass.js) — pure domeinlogica (fysica, toestandsmachines)

Drie output-poorten per node: Port 0 = procesdata, Port 1 = InfluxDB telemetrie, Port 2 = registratie/besturing.

Installatie

git clone --recurse-submodules https://gitea.wbd-rd.nl/RnD/EVOLV.git
cd EVOLV
npm install

Submodules updaten:

git submodule update --remote --merge

Enkel bouwblok installeren in Node-RED:

mkdir -p ~/.node-red/nodes
cp -r nodes/<bouwblok-naam> ~/.node-red/nodes/

Testen

# Alle nodes
bash scripts/test-all.sh

# Specifieke node
node --test nodes/<nodeName>/test/basic/*.test.js
node --test nodes/<nodeName>/test/integration/*.test.js
node --test nodes/<nodeName>/test/edge/*.test.js

Documentatie

  • wiki/ — Projectwiki met architectuur, bevindingen en metrics (index)
  • CLAUDE.md — Claude Code projectgids
  • manuals/node-red/ — FlowFuse en Node-RED referentiedocumentatie
  • .agents/ — Agent skills, beslissingen en function-anchors

Licentie

Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)

Gebruik, aanpassing en verspreiding is toegestaan voor niet-commerciele doeleinden, mits naamsvermelding naar Waterschap Brabantse Delta. Voor commercieel gebruik is voorafgaande toestemming vereist.

Contact

rdlab@brabantsedelta.nl

Description
No description provided
Readme 32 MiB
Languages
HTML 59.5%
Shell 16.6%
JavaScript 13.1%
Python 9%
Dockerfile 1.8%