Index > OperationsE.rsproj

Project File OperationsE.rsproj
Categories
  • River Management Storages
  • Expression Editor
  • Weirs
  • Training
  • River Operations
Created By Shaun Kim
Created Date 09/03/2012
Tested By
Tested Date 09/03/2012
Maintained By
Additional Details Expression Editor, unaccounted differences, wetland Lili Zhang: 27/02/2015, deleted categories "continuous accounting" and "wetland", added "river mangement storages" and "weirs"
Model Information
Output
Functionality
Specification
Created In 2.15.1
Last Saved In
Works In Flow Phase
Test Objective River_Operator
Status
Team City Result Passed
Execution Time (Minutes) Days: 0, Hours: 0, Minutes: 0, Seconds: 49
Jira Issues
Additional Files Scenario 1_Summary.csv,
LogFile OperationsE.rsproj.txt
Scenarios
  • Scenario Name: Scenario 1
    • Description:
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 1/4/2011 12:00:00 AM
    • Simulation End: 2/19/2011 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Lagged Flow Routing: 2
      • Straight-Through Routing: 8
    • Nodes:
      • Storage: 2
      • Inflow: 1
      • Supply Point: 1
      • Water User: 1
      • Gauge: 3
      • Minimum Flow Requirement: 3
    • Constituent To Models: