Project File |
MSP_M1D_daily.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 maximum rate applied when orders are lagged
Run the model in NetLP mode using different optimised algorithms including RELAX IV / Travel Time Replicates, PPRN Without Side-Constraints/Travel Time Replicates, PPRN With Side-Constraints/Travel Time Replicates
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: 36
|
Jira Issues |
|
Additional Files |
M1D_Summary.csv, MSP_M1D-v2.6.2.xls, |
LogFile |
MSP_M1D_daily.rsproj.txt
|
Scenarios |
Scenario Name: M1D
- Description:
- Ordering System Type: Multiple Supply Path Solver
- OwnerShip Enabled: False
- Time Step: Daily
- Simulation Start: 1/27/1971 12:00:00 AM
- Simulation End: 6/2/1971 12:00:00 AM
- Catchments: 0
- FunctionalUnits:
- Rainfall Runoff Model:
- Filtering Model:
- Links:
- Straight-Through Routing: 3
- Lagged Flow Routing: 1
- Nodes:
- Inflow: 1
- Maximum Order Constraint: 1
- Gauge: 1
- Minimum Flow Requirement: 1
- Storage: 1
- Constituent To Models:
|