WRM web version, dynamic output variables
For each RUN of a scenario, all INPUT and OUTPUT time series are stored with the
respective NODE and SCENARIO IDs in the data base to facilitate subsequent
postprocessing, display and analysis.
This includes:
 display of detailed daily results for each node, including annual statistics;
 SUMMARY: annual and monthly summaries BY SECTOR or type of use/flow,
tabular and graphical (monthly time series, annual pie charts);
The following output time series are available for each node type:
StartNodes
 INPUT: inflow
 no output (only input, i.e., flow).

ConfluenceNodes
 INPUT: inflow 1
 INPUT: inflow 2
 outflow (combined inflows)

ControlNodes
 INPUT: inflow
 INPUT: target flow
 violation

BifurcationNodes
 INPUT: inflow
 main branch flow
 diversion flow

ReservoirNodes
 INPUT: inflow
 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
 depth/head/level
 surface area
 rainfeed;
 evptlosses.

DemandNodes
 INPUT: demand
 INPUT: downstream target flow
 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);
 shortfall (supply  demand, by demand node type).
 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 for RFLF (return flow loss factor MISSING !

DiversionNodes
INPUT: inflow
 INPUT: downstream target flow;
 diversion flow (amount extracted);
 mainstream flow (remaining flow, after extractions);
 violation (target  mainstreamflow);

TerminalNode
 INPUT: inflow = outflow
 INPUT: target flow
 outflow
 violation (optional, if a target flow was specified).

