Index > MSP_C3C_1_monthly.rsproj

Project File MSP_C3C_1_monthly.rsproj
Categories
  • River Management Confluence Node
Created By Yong Li
Created Date 03/02/2015
Tested By
Tested Date 03/02/2015
Maintained By
Additional Details To test whether the downstream order can be satisfied from upstreanm storages in parrarrel 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 storage/confluence/min flow node, forecast inflow volume of inflow node, storage volume, extracted volume of extraction point Lili Zhang: 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 Both Inflow regulated
Status
Team City Result Passed
Execution Time (Minutes) Days: 0, Hours: 0, Minutes: 0, Seconds: 40
Jira Issues
Additional Files MSP_C3C_1-v2.6.2.xls, Scenario 1_Summary.csv,
LogFile MSP_C3C_1_monthly.rsproj.txt
Scenarios
  • Scenario Name: Scenario 1
    • Description: Default break points are used for each storage. Base cost: Storage 1 - 11011, Storage 2 - 11000, Zero inflows; downstream constant demand (5000ML/month) Note that: Supplier on EP should be one of the upstream storages. If selecting upstream confluence as supplier on EP, RM will not supply water to EP in ver 0.14.1.
    • Ordering System Type: Multiple Supply Path Solver
    • OwnerShip Enabled: False
    • Time Step: Monthly
    • Simulation Start: 7/1/2000 12:00:00 AM
    • Simulation End: 6/1/2002 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 7
      • Lagged Flow Routing: 2
    • Nodes:
      • Inflow: 4
      • Confluence: 1
      • Gauge: 1
      • Supply Point: 1
      • Water User: 1
      • Storage: 2
    • Constituent To Models: