Index > I3F.rsproj

Project File I3F.rsproj
Categories
  • River Management Inflow Node
  • Ownership
Created By Linda
Created Date 03/02/2015
Tested By
Tested Date 03/02/2015
Maintained By
Additional Details test passing up of total demand through inflow node where demand nodes have different lags Lili Zhang: updated storage as node to accommodate no one can use storage as links in source.
Model Information
Output
Functionality
Specification
Created In 0.12.1
Last Saved In 3.5.0.682
Works In Flow Phase Yes
Test Objective Inflow
Status
Team City Result Passed
Execution Time (Minutes) Days: 0, Hours: 0, Minutes: 0, Seconds: 38
Jira Issues
Additional Files I3F_solution.xls, Scenario 1_Summary.csv,
LogFile I3F.rsproj.txt
Scenarios
  • Scenario Name: Scenario 1
    • Description:
    • Ordering System Type: Multiple Supply Path Solver
    • 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: 7
      • Lagged Flow Routing: 1
    • Nodes:
      • Inflow: 2
      • Gauge: 2
      • Supply Point: 2
      • Water User: 2
      • Storage: 1
    • Constituent To Models: