tpilz/lumpR

parameter database: Include reservoir/river tables

Opened this issue · 4 comments

tpilz commented

Include reservoir table into parameter database.

Possibly affects:

  • db_create()
  • db_update() as this comes with a new database version
  • db_fill() based on output of function wasa_reservoir_par()
  • db_check() ?!
TillF commented

Same for river routing information (response.dat), which could also be accommodated in the db.

tpilz commented

But river routing information are contained within table 'subbasins' (columns 'lag_time' and 'retention')?!

TillF commented

This is the original (i.e. old) WASA routing scheme. For the Muskingum-option and sediment transport, more data is needed (friction values, erodibilities, etc.). Therefore, probable a related table (instead of more columns) would be my favourite choice.

TillF commented

Should be treated as three issues:

  1. strategic reservoirs:
  • db_create() / db_update()
  • db_fill() based on output of function wasa_reservoir_par()
  • db_check()
  1. small reservoirs:
  • db_create() / db_update()
  • db_fill() based on output of function ...()
  • db_check()
  1. river (UHG-routing):
  • db_create() / db_update()
  • db_fill() based on output of function ...()
  • db_check()
  1. river (Muskingum-routing):
  • db_create() / db_update()
  • db_fill() based on output of function ...()
  • db_check()