Index > C4_AtoC.rsproj

Project File C4_AtoC.rsproj
Categories
  • River Management Confluence Node
Created By Linda
Created Date 03/02/2015
Tested By Linda
Tested Date 03/02/2015
Maintained By
Additional Details Forecasting of inflows from tributary A: To test that during the order phase that orders are reduced when there is a forecasted inflow from unregulated inflow joined via a confluence. Using the daily model approach as per test I3A B: check to make sure that forecast on inflow node does not interact with confluence forecast - run C4A with different k on trib inflow node C: use a loss etc on unreg stream to make sure that the correct inflow at previous timestep is used Has been converted to storage as node and replaced in teamCity
Model Information
Output
Functionality
Specification
Created In 0.12.1
Last Saved In 2.13.1
Works In Flow Phase Yes
Test Objective Confluence A: timeseries inflow B: timeseries inflow C: simulated inflow
Status
Team City Result Passed
Execution Time (Minutes) Days: 0, Hours: 0, Minutes: 0, Seconds: 51
Jira Issues
Additional Files C4A_solution.xls, C4B_solution.xls, C4c_solution.xls, Scenario 1 C4a_Summary.csv, Scenario 2 C4b_Summary.csv, Scenario 3 C4c_fixedDemand_Summary.csv, Scenario 4 C4c_monthlyPattern_Summary.csv,
LogFile C4_AtoC.rsproj.txt
Scenarios
  • Scenario Name: Scenario 1 C4a
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/27/1971 12:00:00 AM
    • Simulation End: 2/20/1971 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Lagged Flow Routing: 1
      • Straight-Through Routing: 6
    • Nodes:
      • Inflow: 2
      • Gauge: 2
      • Confluence: 1
      • Supply Point: 1
      • Water User: 1
      • Storage: 1
    • Constituent To Models:
  • Scenario Name: Scenario 2 C4b
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/27/1971 12:00:00 AM
    • Simulation End: 2/20/1971 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Lagged Flow Routing: 1
      • Straight-Through Routing: 6
    • Nodes:
      • Inflow: 2
      • Gauge: 2
      • Confluence: 1
      • Supply Point: 1
      • Water User: 1
      • Storage: 1
    • Constituent To Models:
  • Scenario Name: Scenario 3 C4c_fixedDemand
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/27/1971 12:00:00 AM
    • Simulation End: 2/20/1971 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 8
    • Nodes:
      • Inflow: 2
      • Gauge: 2
      • Confluence: 1
      • Supply Point: 1
      • Loss: 1
      • Water User: 1
      • Storage: 1
    • Constituent To Models:
  • Scenario Name: Scenario 4 C4c_monthlyPattern
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/27/1971 12:00:00 AM
    • Simulation End: 2/20/1971 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 8
    • Nodes:
      • Inflow: 2
      • Gauge: 2
      • Confluence: 1
      • Supply Point: 1
      • Loss: 1
      • Water User: 1
      • Storage: 1
    • Constituent To Models: