Project File |
M1C.rsproj
|
Categories |
- Maximum Order Constraint Node
|
Created By |
Linda |
Created Date |
03/02/2015 |
Tested By |
Linda |
Tested Date |
03/02/2015 |
Maintained By |
|
Additional Details |
Correct Rate applied to orders?
It is assumed that the result returned from EE is ML/D however this has not been clarified in the interface.
Lili Zhang: updated storage as node to accommodate no one can use storage as links in source.
|
Model Information |
|
Output |
|
Functionality |
|
Specification |
|
Created In |
0.8.2 |
Last Saved In |
3.5.0.682 |
Works In Flow Phase |
|
Test Objective |
Maximum order constraint - single storage
|
Status |
|
Team City Result |
Passed
|
Execution Time (Minutes) |
Days: 0, Hours: 0, Minutes: 0, Seconds: 38
|
Jira Issues |
|
Additional Files |
Scenario 2_Summary.csv, |
LogFile |
M1C.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: 4
- Nodes:
- Inflow: 1
- Gauge: 1
- Maximum Order Constraint: 1
- Minimum Flow Requirement: 1
- Storage: 1
- Constituent To Models:
|