Project File |
MSP_M1A_monthly.rsproj
|
Categories |
- Ownership
- Maximum Order Constraint Node
|
Created By |
Yong Li |
Created Date |
03/02/2015 |
Tested By |
|
Tested Date |
03/02/2015 |
Maintained By |
|
Additional Details |
To test that rate specified correctly for maximum flow node. Flow target as fixed rate via constraint value field
Run the model in NetLP mode using different optimised algorithms including RELAX IV , PPRN Without Side-Constraints, PPRN With Side-Constraints;
Downstream flow volume of max flow constraint, storage volume
updated by Lili Zhang on 15/11/2013: updated storage as node to accommodate no one can use storage as links in source
|
Model Information |
|
Output |
|
Functionality |
|
Specification |
|
Created In |
2.6.2 |
Last Saved In |
3.5.0.682 |
Works In Flow Phase |
|
Test Objective |
Ownership off
|
Status |
|
Team City Result |
Passed
|
Execution Time (Minutes) |
Days: 0, Hours: 0, Minutes: 0, Seconds: 35
|
Jira Issues |
|
Additional Files |
MSP_M1A-v2.6.2.xls, Scenario 1_Summary.csv, |
LogFile |
MSP_M1A_monthly.rsproj.txt
|
Scenarios |
Scenario Name: Scenario 1
- 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: 4
- Nodes:
- Inflow: 1
- Gauge: 1
- Maximum Order Constraint: 1
- Minimum Flow Requirement: 1
- Storage: 1
- Constituent To Models:
|