skip to main content
Agg Reach Water Quality
Water Quality
Agg Reach Water Quality
Agg Reaches have water quality methods to model salt by calculating the total salt mass of the inflow and outflow. The actual water quality work is done on the reach elements. Links are automatically created between reaches within the aggregate and to the aggregate.
Slots
Following are descriptions of the slots (on the aggregate) associated with Salinity.
Inflow Salt Concentration
Type: Series Slot
Units: Concentration
Description: Salt concentration associated with the inflow to the Agg Reach
I/O: Input, set by a rule, output or propagated via a link
Inflow Salt Mass
Type: Series Slot
Units: Mass
Description: Salt mass associated with the inflow to the Agg Reach
I/O: Output only
Outflow Salt Concentration
Type: Series Slot
Units: Concentration
Description: Salt concentration associated with the outflow from the Agg Reach
I/O: Input, set by a rule, output or propagated via a link
Outflow Salt Mass
Type: Series Slot
Units: Mass
Description: Salt mass associated with the outflow from the Agg Reach
I/O: Output Only
User Methods
Following are the user-selectable methods on the Agg reach.
Agg Reach Water Quality
Methods in this category specify how you wish to model water quality parameters.
* None
This is the default, no-action method for this category. No slots are instantiated by this method. When this method is selected, all of the member elements are configured to also not model water quality. That is, the None method is selected on each reach. See “None” for details.
* Discretized Salt
The aggregate controls whether the member elements model salinity. Reach elements of the aggregate either model salt or doesn’t. But they all perform the same. Also, the Water Quality Routing category is made invisible on the reach.
* Well Mixed Salt
The aggregate controls whether the member elements model salinity. Reach elements of the aggregate either model salt or doesn’t. But they all perform the same. Also, the Water Quality Routing category is made invisible on the reach.
WQ on Reach Elements
The WQ on Reach Elements category allows you to choose whether to model salinity on the member elements.
* None
This is the default, no-action method for this category. No slots are instantiated by this method. When this method is selected, all of the member elements are configured to not model salt. That is, the None method is selected on each reach. See “None” for details.
* Salinity
When this method is selected, all of the member elements are configured to model salt. That is, the Salinity method is selected on each reach; see “Salinity” for details. Also, concentration links are created between the aggregate and the first and last element and between successive reach elements. For example Element1.Salt Concentration Outflow is linked to element2.Salt Concentration Inflow. These links are made automatically.
Note:  The reach element must have No Routing selected, or an error will be issued.
* Mass Balance Salinity
When this method is selected, all of the member elements are configured to model salt. That is, the Mass Balance Salinity method is selected on each reach; see “Mass Balance Salinity” for details. Also, concentration links are created between the aggregate and the first and last element and between successive reach elements. For example Element1.Salt Concentration Outflow is linked to element2.Salt Concentration Inflow. These links are made automatically.
Note:  The reach element must have No Routing selected, or an error will be issued.
Dispatch Methods
Following is the available dispatch method when the solution approach is Well Mixed Salt or Discretized Salt.
* Solve Salt
This method computes the total inflow and outflow salt mass only. The salt concentrations should come from the linked element objects or from upstream/downstream objects (or via input or rules).
Required Known slots
• Inflow
• Outflow
• Inflow Salt Concentration
• Outflow Salt Concentration
Required Unknown slots
• None
Method Details
This method does the following:
(4.1)    
(4.2)    
 
Revised: 06/03/2019