Index > Inflow_AtoI.rsproj

Project File Inflow_AtoI.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 Physical System To ensure that daily time series data is correctly applied to a headwater inflow node, and to test the output statistics. To test extreme values. To test adding inflow data using the Expression Editor and multiplying to give small values To test adding inflow data using the Expression Editor and multiplying to give large values To test hourly time series data. To test how RM handles a short record of data To test time series data using m3/s and outputting in m3/s To test time series data using m3/s and outputting in ML/d To test how RM handles a long record of data Time series outputs seem correct, although there seems to be a problem in keeping the full data set once it has already been imported (ends at 30/12 not 31/12) (RM-1459). Statistics incorrectly reported - see Jira issue 1458. Time series outputs seem correct, although user has to select appropriate unit preferences for cumecs each time the project is opened (issue emailed to Ian and Geoff D). Statistical outputs incorrect in some cases - see Jira. Time series outputs seem correct, although user has to select appropriate unit preferences for cumecs each time the project is opened (issue emailed to Ian and Geoff D). Statistical outputs incorrect in some cases - see Jira.
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: 54
Jira Issues
Additional Files FULL_SolutionFile_physical_inflows_outputComparison.xls, Scenario A Daily time step_Summary.csv, Scenario B Extreme values_Summary.csv, Scenario C and D Expression Editor_Summary.csv, Scenario E Hourly instantaneous_Summary.csv, Scenario F_5 days data_Summary.csv, Scenario G and H m3s_Summary.csv, Scenario I daily long record_Summary.csv,
LogFile Inflow_AtoI.rsproj.txt
Scenarios
  • Scenario Name: Scenario A Daily time step
    • 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: 1
    • Nodes:
      • Inflow: 1
      • Gauge: 1
    • Constituent To Models:
  • Scenario Name: Scenario B Extreme values
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/1/1982 12:00:00 AM
    • Simulation End: 1/31/1984 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 1
    • Nodes:
      • Inflow: 1
      • Gauge: 1
    • Constituent To Models:
  • Scenario Name: Scenario C and D Expression Editor
    • 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: 2
    • Constituent To Models:
  • Scenario Name: Scenario E Hourly instantaneous
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Hourly
    • Simulation Start: 1/1/1984 12:00:00 AM
    • Simulation End: 12/31/1984 11:00:00 PM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 1
    • Nodes:
      • Inflow: 1
      • Gauge: 1
    • Constituent To Models:
  • Scenario Name: Scenario F_5 days data
    • 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: 1/5/1990 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 1
    • Nodes:
      • Inflow: 1
      • Gauge: 1
    • Constituent To Models:
  • Scenario Name: Scenario G and H m3s
    • 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: 1
    • Nodes:
      • Inflow: 1
      • Gauge: 1
    • Constituent To Models:
  • Scenario Name: Scenario I daily long record
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/1/1913 12:00:00 AM
    • Simulation End: 1/2/2004 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 1
    • Nodes:
      • Inflow: 1
      • Gauge: 1
    • Constituent To Models: