Index > Carryover_Loddon Type Test.rsproj

Project File Carryover_Loddon Type Test.rsproj
Categories
  • Resource Assessment - Annual Accounting
Created By Lili Zhang
Created Date 30/05/2014
Tested By
Tested Date 03/02/2015
Maintained By
Additional Details Lili Zhang: this project is a test case attached to jira RM-12171 by Yong Lili Zhang: updated project to change evap loss adjustment trigger at timestep beginning at start of water year and give them higher priority than reassess triggers. Updated results of carry over start of water year which shows consistent value for the entire water year. Lili Zhang: 02/09/2014, updated account balance, available water and carry over to accommodate changes of these recorders related to value before triggers. And we have got separated recorders called "account balance post trigger", "available water post trigger" and "carry over post trigger" to recorder value after triggers. Lili Zhang: 07/10/2017, updated project and results to accommodate changes of recorders' name change: "Carryover start of water year", "Total Usage Carryover Water Year" and "Total spill from account to date"
Model Information
Output
Functionality
Specification
Created In 3.6.5.1556
Last Saved In 3.8.5.2122
Works In Flow Phase
Test Objective test carryover trigger
Status
Team City Result Passed
Execution Time (Minutes) Days: 0, Hours: 0, Minutes: 1, Seconds: 54
Jira Issues
Additional Files Example 1-1 - Carry-over Triggers at Account Type Level_Summary.csv, Example 1-2 - Carry-over Triggers at Account Type Level - 1_Summary.csv, Example 1-3 - Carry-over Triggers at Account Type Level - 1_Summary.csv, Example 1-4 - Carry-over Triggers at Account Type Level - 1 - 1_Summary.csv, Example 1-5 - Carry-over Triggers at Account Type Level - 1_Summary.csv,
LogFile Carryover_Loddon Type Test.rsproj.txt
Scenarios
  • Scenario Name: Example 1-1 - Carry-over Triggers at Account Type Level
    • Description: Carryover at account type level, evap loss deducted at the end of water year; Transfer all water to Hrws account balance and then carry over at end of water year; Max carryover 50%; Max Effective Allocation 100%
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 7/1/2000 12:00:00 AM
    • Simulation End: 10/2/2013 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 9
    • Nodes:
      • Storage: 1
      • Inflow: 1
      • Water User: 4
      • Supply Point: 4
    • Constituent To Models:
  • Scenario Name: Example 1-2 - Carry-over Triggers at Account Type Level - 1
    • Description: Transfer all water to Lrws account balance and then carry over at end of water year; Max carryover 50%;Max Effective Allocation 100%
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 7/1/2000 12:00:00 AM
    • Simulation End: 10/2/2013 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 9
    • Nodes:
      • Storage: 1
      • Inflow: 1
      • Water User: 4
      • Supply Point: 4
    • Constituent To Models:
  • Scenario Name: Example 1-3 - Carry-over Triggers at Account Type Level - 1
    • Description: Carryover at account type level, evap loss deducted at the end of water year; Transfer all water to Hrws account balance and then carry over at end of water year; Unlimited carryover;Max Effective Allocation 100%
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 7/1/2000 12:00:00 AM
    • Simulation End: 10/2/2013 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 9
    • Nodes:
      • Storage: 1
      • Inflow: 1
      • Water User: 4
      • Supply Point: 4
    • Constituent To Models:
  • Scenario Name: Example 1-4 - Carry-over Triggers at Account Type Level - 1 - 1
    • Description: Carryover at account type level, evap loss deducted at the end of water year; Transfer all water to Hrws account balance and then carry over at end of water year; Unlimited carryover;Max Effective Allocation 150%
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 7/1/2000 12:00:00 AM
    • Simulation End: 10/2/2013 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 9
    • Nodes:
      • Storage: 1
      • Inflow: 1
      • Water User: 4
      • Supply Point: 4
    • Constituent To Models:
  • Scenario Name: Example 1-5 - Carry-over Triggers at Account Type Level - 1
    • Description: Carryover at account type level, evap loss deducted at the end of water year; Transfer all water to Hrws account balance and then carry over at end of water year; Max carryover 100%; Max Effective Allocation 150%
    • Ordering System Type: New rules based ordering system
    • OwnerShip Enabled: False
    • Time Step: Daily
    • Simulation Start: 7/1/2000 12:00:00 AM
    • Simulation End: 10/2/2013 12:00:00 AM
    • Catchments: 0
    • FunctionalUnits:
    • Rainfall Runoff Model:
    • Filtering Model:
    • Links:
      • Straight-Through Routing: 9
    • Nodes:
      • Storage: 1
      • Inflow: 1
      • Water User: 4
      • Supply Point: 4
    • Constituent To Models: