WRM web version, summary of output variables by node
For each RUN of a scenario, all INPUT and OUTPUT time series are stored with the
respective NODE IDs in the data base to facilitate subsequent postprocessing,
display and analysis.
For each individual NODE display, the header should show:
 Location and project name;
 scenario name, date of computation, user.
In addition to the network diagram with the current node highlighted,
a small overview MAP of the basin is also shown.
Whenever a NODE is linked to a georeferenced RiverBasinObject,
its position can be highlighted in the map as well.
For each time series (input and output) associated with a node, a summary table of
statistics should be generated, including, for each variable:
 average (arithmetic mean);
 median
 min and max;
 SD (standard deviation)
For the main variables we can also show for each node the % of the total:
 INFLOW (from all start nodes);
 DIVERSION FLOW (gross extractions)
 SUPPLY (net demand satisfied)
 Consumptive use
The following time series are available for each node type, can be displayed
as statistical summary, daily time series, monthly time series, monthly table:
StartNodes
 INPUT: outflow.

RechargeNodes
 INPUT: total input
 infiltration flo (capacity constrained);
 bypass flow.

ConfluenceNodes
 outflow (combined inflows)

ControlNodes
 INPUT: inflow
 INPUT: target flow
 violation

BifurcationNodes
 main branch flow
 diversion flow

DiversionNodes
diversion flow (amount extracted);
 mainstream flow (remaining flow, after extractions).
 violation (target  minstreamflow)

DemandNodes
 diversion flow (demand, compensated for conveyance losses);
 mainstream flow (remaining downstream flow after subtraction of diversion flow);
Please note: the mainstream flow time series is only generated or meaningful for
the instream configuration of a demand node; else, it is part of the diversion
node upstream of the demand node.
 supply (diversion minus conveyance loss, useful demand);
 conveyance loss (water lost in supplying the demand)
 consumptive use (fraction of supply taken our of the system);
 return flow (supply minus consumptive use * loss factor) DATA MISSING !

TreatmentNodes
 dynamic inflow
 bypass flow

ReservoirNodes
 release or outflow:
 actual outflow, which is depending on strategy either demand
(subject to availability constraints);
 rule based release (as a function of level);
 combined strategy (see below) subject to lower
and upper bounds.
 violation or shortfall (target  actual release);
 storage volume (in the dynamic case, also level and surface area)
 rainfeed (effective precipitation onto the reservoirs surface and possibly immediate
beach area directly contributing to volume);
 evptlosses (evapotranspiration, function of temperature, but also possibly vegetation such as
macrophytes growth).

AquiferNodes
 extraction
 deep percolation
 evapotranspiration
 natural recharge
 infiltration balance from losses and in/exfiltration of reaches
 artificial recharge
 sum of inputs
 sum of outputs
 volume
 head

TerminalNode
 outflow
 violation (optional, if a target flow was specified).


