Performing a generalized multi run simulation

Step-by-step guide

Once a configuration for a generalized multi run has been set up in InfoWorks WS Pro with test cases created and the result and analysis settings configured, you can perform the run.

1. Right-click Model Group and select New > Run Group.
2. Right-click the Run Group and select New > Run.
3. In the Schedule Hydraulic Run dialog box, in the Title type box, name this run “Valve Closures”.
4. Enable Experimental.

Note that if you do not enable Experimental, then the resulting GMR object will be locked to the run and read-only, and you will not be able to make small changes.

5. Expand the Run Type drop-down and select Normal.
6. From the Run Type group, select Generalized Multi Run.

7. In the Generalized Multi Run Options dialog box, to specify the previously created “Valve Closures” configuration, drag it from the Model Group and drop it into the Generalized Multi Run Config pane.
8. OR, select Browse (>>), navigate to the configuration you want, and select it.
9. Enter the number of test cases you wish to run for parallel processing. The default is set to 20.

Note: if you have a significantly powerful computer, you may wish to increase the number of test cases.

10. Click OK.

11. Back in the Schedule Hydraulic Run dialog box, drag the network (Network!) into the Network pane.
12. Drag a control (Control!) into the Control pane.
13. Drag a demand diagram (BridgeTown ADAW) into the Demand Diagram pane.
14. Click Run.

After a few minutes, the run displays in the Model Group window.

Notice that there is only one simulation in the Run Group. This is because when these test cases were configured, the option to keep only the summary results was selected.

15. Right-click the run and select Open as.
16. In the Select Results dialog box, select Summary report.
17. Click OK.

A Summary Report appears that includes a table summary of each test case where the maximum pressure is below 20m.

It also includes columns for the minimum, average, and maximum pressures, as well as the ID of the customer point it occurs at. This data represents the constraints you applied through the CP<20m stored query.