Index > Inflow in series.rsproj

Project File Inflow in series.rsproj
Categories
  • River Management Inflow Node
Created By Kerrie Tomkins
Created Date 09/03/2012
Tested By
Tested Date 09/03/2012
Maintained By
Additional Details The two inflow nodes use different record lengths to test how RM handles them RiverManager only runs for the period of overlap. Are there any cases where it may be desirable to run for the period of the longest data set? Geoff P - this is the best way of handling this. Need to also check for gaps.
Model Information
Output
Functionality
Specification
Created In 0.8.2
Last Saved In 2.13.1
Works In Flow Phase
Test Objective Inflow
Status
Team City Result Passed
Execution Time (Minutes) Days: 0, Hours: 0, Minutes: 0, Seconds: 47
Jira Issues
Additional Files FULL_SolutionFile_physical_inflows_outputComparison.xls, Scenario 1 daily time series_Summary.csv, Scenario 2 daily ts diff record lengths_Summary.csv, Scenario 3 monthly pattern_Summary.csv,
LogFile Inflow in series.rsproj.txt
Scenarios
  • Scenario Name: Scenario 1 daily time series
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/1/1990 12:00:00 AM
    • Simulation End: 7/24/1991 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 2
    • Nodes:
      • Inflow: 2
      • Gauge: 1
    • Constituent To Models:
  • Scenario Name: Scenario 2 daily ts diff record lengths
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 9/1/1990 12:00:00 AM
    • Simulation End: 7/24/1991 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 2
    • Nodes:
      • Inflow: 2
      • Gauge: 1
    • Constituent To Models:
  • Scenario Name: Scenario 3 monthly pattern
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/1/1990 12:00:00 AM
    • Simulation End: 7/24/1991 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 2
    • Nodes:
      • Inflow: 2
      • Gauge: 1
    • Constituent To Models: