Project File |
M1Eb.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?
Test that Maximum constraint is not applied to upstream extractor
new functionality as a result of ordering spec
may be added as a result of ordering spec
|
Model Information |
|
Output |
|
Functionality |
|
Specification |
|
Created In |
0.8.2 |
Last Saved In |
|
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: 46
|
Jira Issues |
|
Additional Files |
Scenario 2_Summary.csv, |
LogFile |
M1Eb.rsproj.txt
|
Scenarios |
Scenario Name: Scenario 2
- Description:
- Ordering System Type: New rules based ordering system
- 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: 5
- Nodes:
- Storage: 1
- Supply Point: 1
- Water User: 1
- Maximum Order Constraint: 1
- Minimum Flow Requirement: 1
- Gauge: 1
- Constituent To Models:
|