Tuesday, December 20, 2016
#SWMM5 has very flexible control rules. The rules are shown in the controls.c code. However, one aspect I did not know was that if a rule is based on a control curve the RPT logging of the control actions is not shown. You can change by changing and compiling the code. You will need to get rid of the half rule
&& a1->curve < 0 so that the changing of the target setting is logged – see below for a snippet of the code.
Here is a sample curve tool
IF SIMULATION TIME > 4
AND SIMULATION TIME <= 6
THEN PUMP Gbp1 SETTING = CURVE myControl
And here is the control action log in the RPT file – it helps to see this log and verify the rules
Control Actions Taken
01/01/2013: 00:00:00 Link Gbp1 setting changed to 0.00 by Control MC1
01/01/2013: 00:00:01 Link Gbp1 setting changed to 0.00 by Control MC1
01/01/2013: 00:00:11 Link Gbp1 setting changed to 0.01 by Control MC1
01/01/2013: 00:00:21 Link Gbp1 setting changed to 0.01 by Control MC1
listItem = ActionList;
while ( listItem )
a1 = listItem->action;
if ( !a1 ) break;
if ( a1->link >= 0 )
if ( Link[a1->link].targetSetting != a1->value )
Link[a1->link].targetSetting = a1->value;
//if ( RptFlags.controls && a1->curve < 0 //(5.1.011) Original Rule
if ( RptFlags.controls //(5.1.011) New rule
&& a1->tseries < 0 && a1->attribute != r_PID ) //(5.1.011)
GIS Gateway – Create Shapefile T he Create Shapefile tool available from the GIS Gateway , allows you to create a new ESRI® Shapefile dir...
Soffit Level ( pipe technology ) The top point of the inside open section of a pipe or box conduit. The soffit is the ...
Comment: A really nice water analogy for the field properties Divergence, Curl and Gradient from the Blog Starts With a Bang ....it&...
Engine Error Number Description ERROR 101: memory allocation error. ...