Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Stage/Level and Tidal Input mode #54

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Conversation

dvalters
Copy link
Owner

@dvalters dvalters commented Dec 15, 2022

Summary

Several users would like to be able to input river level data (Stage) and tidal levels into the model, instead of having to use discharge as an input source for reach mode style simulations.

Details

  • This uses the same algorithm for levels/tidal input as was added in Caesar 1.9s and later versions.
  • The user specifies a "bounding box" where the level data (water height) is applied to the model inputs
  • The input file is a single column list of water heights, listed in order of time step for the stage/levels/tide data source
  • The time step in minutes is set in the .params file.
  • Levels are updated every timestep. It does this by setting the water depth directly from the input file, rather than having to calculate discharge from the discharge file, then applies that to the water_depths array.

Testing

This was tested on the Idealsied_stage.params test case in the test folder, and also some real data using the Beverley Ship Yard gauging station (levels) on the River Hull, UK, with a DEM covering the Hull from Beverley down to hull, run over 118 days.

Parameter File

# STAGE INPUTS
#==============

stage_mode_input_on:           yes
stage_input_timestep:          60
fromx:                         5
tox:                           10
fromy:                         272
toy:                           274
stage_inputfile:               stage_mode_input.csv

Note

Note: this still features the "bug" in #53, but the workaround is simple (treat x and y as i and j matrix indices rather than coordinates - a fix for that will be made available too shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant