Project File |
Mn1B.rsproj
|
Categories |
- Minimum Flow Requirement Node
|
Created By |
|
Created Date |
09/03/2012 |
Tested By |
|
Tested Date |
09/03/2012 |
Maintained By |
|
Additional Details |
as per Mn1B however inflow expressed as a volume rather than a rate.
Updated by juanita in May 2013 to accommodate changes that happened when 'End of Time Step' evaluation was moved to after values have been recorded.
Lili Zhang: 29/07/2013, changed categories.
|
Model Information |
|
Output |
|
Functionality |
|
Specification |
|
Created In |
0.11.2 |
Last Saved In |
2.0.2 |
Works In Flow Phase |
|
Test Objective |
Minimum flow requirement
- Rate specified with expression editor - updated to Function Manager (May 2013)
|
Status |
|
Team City Result |
Passed
|
Execution Time (Minutes) |
Days: 0, Hours: 0, Minutes: 0, Seconds: 36
|
Jira Issues |
|
Additional Files |
Scenario 2_Summary.csv, |
LogFile |
Mn1B.rsproj.txt
|
Scenarios |
Scenario Name: Scenario 2
- Description:
- Ordering System Type: Multiple Supply Path Solver
- OwnerShip Enabled: False
- Time Step: Monthly
- Simulation Start: 1/1/2005 12:00:00 AM
- Simulation End: 5/1/2007 12:00:00 AM
- Catchments: 0
- FunctionalUnits:
- Rainfall Runoff Model:
- Filtering Model:
- Links:
- Straight-Through Routing: 3
- Nodes:
- Inflow: 1
- Gauge: 1
- Minimum Flow Requirement: 1
- Storage: 1
- Constituent To Models:
|