Index > I3Avariabledemand.rsproj

Project File I3Avariabledemand.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 NOTE that water user uses forward looking orders to account for travel time (as per RM-1487) however this forward looking functionality has not been implemented for the old time series extraction node Lili Zhang: updated storage to accommodate using storage as links is not available.
Model Information
Output
Functionality
Specification
Created In 0.14.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 I3Avariabledemand_solution.xls, Scenario 1_Summary.csv,
LogFile I3Avariabledemand.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: 3/1/1971 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Lagged Flow Routing: 1
      • Straight-Through Routing: 5
    • Nodes:
      • Inflow: 2
      • Gauge: 2
      • Water User: 1
      • Supply Point: 1
      • Storage: 1
    • Constituent To Models: