Generalised Multi Run Configuration dialog
Use this dialog to set up a simulation that runs multiple test cases.
To open the dialog for a new configuration, right-click Generalised Multi Run Group in the Model Group window and select New | Generalised Multi Run Config.
To open the dialog for an existing configuration, select an item from the Generalised Multi Run Group in the Model Group window.
Test Cases page
You use this page to specify test cases in the grid on the right side. You can enter the test cases manually, although a wizard is provided on the left side to make the creation of multiple test cases quicker.
Generalised Multi Run (GMR) is setup by specifying test cases. The following image shows a very simple case. There are three test cases and so there will be three runs. Each run involves closing a single pipe, and the run takes the name of the pipe.
To make this simple list of test cases, use the “wizard” section on the left pane of the dialog.
-
Start with a selection list of three pipes. Drop this into the drop target.
-
From the drop-down menu, select Pipe (Control). This exposes the fields for the pipe control fields.
-
Find Pipe Closed and check the box (i.e. closed)0
-
Check the box Append Object ID to test case name. Leave the Test case name blank.
-
Click the Add - - > button. Three test cases are created. Each takes the name of its pipe, and each test case involves closing the pipe.
To add multiple objects in one test case:
-
Start with a selection list of three pipes. Drop this into the drop target.
-
From the drop-down menu, select Pipe (Control). This exposes the fields for the pipe control fields.
-
Find Pipe Closed and check the box (i.e. closed).
-
Set the test case name to RED.
-
Click Add - - >.
A single test case is created. The GMR would run single simulation called RED, in which three pipes are closed.
-
Repeat the steps above but with the name YELLOW.
-
Click Add - - >.
-
Delete one of the rows of the YELLOW test case
Now the GMR has two simulations called RED and YELLOW with three and two closures, respectively. Continue in this way to make two further test cases called ORANGE and BLUE.
For the set-up of a more complex GMR. Take the three pipes, and for each pipe, set up a burst. The burst involves setting several Control fields. But go beyond this and set up three different burst sizes.
-
Start with a selection list of three pipes. Drop this into the drop target.
-
From the drop-down menu, select Pipe (Control). This exposes the fields for the pipe control fields.
-
Set the burst fields: enable the burst; for the entire simulation; a flow type burst; a fixed flow; a flow value of 0.5 l/s. So, there are five Control fields.
-
For test case, give the name SmallLeak and check the box Append object ID to test case name.
-
Click Add - - >.
-
Modify the leak value to 1.0 l/s and change the name to MediumLeak. Click Add - ->.
In this way you have multiple tests cases for each object. And each test case involves the setting of multiple fields.
As can be seen, the wizard offers a lot of flexibility. In addition, you can export the test cases to CSV, manipulate them and reimport them. For even greater power, you can use SQL to generate a table which is imported into the test case grid. See GMR Mapped CSV Import dialog for more information.
Results page
You can use this page to specify a subset of results to keep. You might want to do this to save storage space.
The minimum for the retention of results is to keep the summary data cube, Keep summary report only. This allows the generation of grid reports, as well as thematic colouration in the GeoPlan. This summary report is always retained
At the other extreme, Keep all TVD results allows individual simulations to be examined but of course the volume of data may cause performance and storage problems.
Intermediate approaches are:
-
Keep individual test cases if a query returns a “positive”. For example, you might have a query to select a reservoir if its level drops below 20% full. Any test case that includes results like this will be retained.
-
Keep summaries for individual test cases, but discard time varying results.
Analysis page
You can use this page to specify analysis options.
The Analysis tab decides what values go into the summary table. The summary table is structured as follows:
The Test Case and Object ID fields will form a primary key within the summary table.
As an example, if using a query to populate the report, Result-1 could be pressure at time T1, Result-2 could be pressure at time T2 and Result-3 might be Max Pressure. This table will be “sliced and diced” for final display in the grid or GeoPlan. Aggregation will take place across Object ID or Test case name to give minima to Result-1 or maxima for Result-3.
The summary table is constructed from pre-existing summary fields or from a query.
-
Pre-existing summary fields- Use a selection list or use the list of test case objects. Choose some summary result fields; these will appear in the summary table.
-
Run a query - For this you can also request that a Base Run is used (i.e., the original run with no test case instructions) and both Test Case and Base Run would be available in the query.
An example of a query is seen below. It is designed for pipes. The query returns an object id (as the result column object_id) and a result column called SeriousReversal, which will be 0 or 1 if there is a large number of flow reversals. Test case ID is automatically output.
select OID AS object_id , IIF( (sim.pctflowf > 20 and sim.pctflowf < 80 and sim.vnegmax < -0.15 and sim.vposmax > 0.15 and sim.reversal > 10),1,0) AS SeriousResersval
The summary table will contain three columns: test_case, object_id, SeriousReveral
Save button
Click to save the configuration.