Dataset is the key component of scenarios, and used to represent any difference such as pipe diameter, tank size, and pump curve.
To change data sets for a scenario, open the Scenario Explorer, and select the Dataset tab.
Data Sets
-
Demand Set - Modeling data associated with junction nodes. Demand sets are used to save modeling data on junction node demands and demand pattern identifiers and retrieve those data as part of a scenario. The only attributes stored in a demand set are the baseline demands and the associative pattern. The Auto-Demand Reset preference governs how demands are assigned when activating demand sets.
-
Tank Set - Modeling data associated with storage nodes. Tank sets are used to save modeling data on storage nodes and retrieve those data as part of a scenario. Tank sets contain modeling information including type of storage node (tank, fixed-grade reservoir, variable head reservoir, and variable-area tank) and related storage node characteristic data such as bottom elevation, initial water level, tank dimensions including diameter, minimum and maximum levels, minimum volume, curves defining variable area tanks, and patterns defining grade in variable-head reservoirs.
-
Reservoir Set - Modeling data associated with Reservoirs. Reservoir sets are used to save modeling data on reservoirs and retrieve those data as part of a scenario. Reservoir sets contain modeling information including type of storage node (fixed-grade reservoir or variable head reservoir) and related storage node characteristic data such as head and patterns defining grade in variable-head reservoirs.
-
Pump Set - Modeling data associated with pumps. Pump sets are used to save modeling data on pumps and retrieve those data as part of a scenario. Pump sets contain modeling information including pump curve type and pump curve parameters.
-
Valve Set - Modeling data associated with control valves. Valve sets are used to save modeling data on control valves and retrieve those data as part of a scenario. Valve sets contain modeling information including valve type and related valve characteristic data such as pressure setting for PRVs, flow setting for FCVs, tank grades for float valves, etc.
-
Pipe Set - Modeling data associated with pipes. Pipe sets are used to save modeling data on pipes and retrieve those data as part of a scenario. Pipe sets contain modeling information including pipe diameters, lengths, roughness coefficients, minor loss coefficients, and presence or absence of check valves and flow totalizers.
-
Control Set - Initial link status (open, closed, setting) and any operational control rules defined at the time the control set was created. Controls apply to links, pumps, and valves.
-
Energy Set - Energy data for pumps including pump efficiency, energy charging rate patterns, and demand charge patterns.
-
Fireflow Set - Fireflow demands for junction nodes.
-
Logical Set -Logical controls used for rule based logic controls. Logical controls are created and maintained with the Rule-Based Control command (see InfoWater Pro Model Explorer- >Command Center - >Edit Menu and select Rule-Based Control). Use the Edit Logic Set to store logical controls in a logic set and to maintain those logic sets.
-
SCADA Set - All the SCADA information for the InfoWater Pro project.
-
Pattern Set - All pattern data in the InfoWater Pro project.
-
Curve Set - All curves data in the InfoWater Pro project.
-
Quality Set - Water quality modeling parameters including quality source nodes, initial water quality at junction and storage nodes, and reaction rate coefficients for pipes and tanks. Water quality parameters are maintained with the Create, Edit, or Edit Group commands. Use the Edit Quality Set command to create and manage quality sets.
-
Surge Set - All surge data in the InfoWater Pro project. Surge sets are used in simulating transient events caused by turbine operation, and Pressure Reducing Valve (PRV)/Flow Control Valve (FCV) responses to transients.
Datasets for a child scenario can be set to be either
Inherited from the Parent Scenario or they can use a Scenario Specific Dataset. An Inherited Dataset will update automatically in the child scenario to match if changed in the Parent Scenario, while a Scenario Specific Dataset will not change if the Parent scenario is changed. The Icon shown next to the dataset will indicate which type has been selected for that dataset (see image 5). To Change from a Scenario Specific dataset to Inherited, right click on the dataset in question and select "Inherited". If you open the specific Dataset browser with a double click on the dataset Category name or by right clicking and choosing the
Select option and select a specific dataset so it is highlighted and select the green
OK
button, it will reset the dataset type to be Scenario Specific.
Edit Active Scenario
The Active Scenario dialog box allows you to select any of the scenarios created in an InfoWater Pro project and make it active. Once a scenario is made active, each of the three facets that comprise a scenario also become active.
Click on the
Edit Active Scenario
button from the Model Explorer - Baseline Data Scenario toolbar (see above) to open the Active Scenario dialog box and to make edits to your Active Scenario.
Active Scenario
The Active Scenario shows you which scenario is currently active.
Inheritance Path
The Inheritance Path shows which parent this scenario is dependent upon.
Data Sets
The Data Sets also show which data sets are currently being assigned to this particular scenario. Here, you can change the Data Sets of the active scenario by doubling-clicking on the desired data set. A dialog box will appear showing all of the data sets available to you.
Apply
Click
Apply
to accept the various changes and selections made in this dialog box.
Reset
Reset all the changes made.
Close
Click
Close
to close out of the dialog box.