parameter database: Include reservoir/river tables

[tpilz]

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]

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

[tpilz]

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

[TillF]

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]

Should be treated as three issues:

1. strategic reservoirs:

   • [x] db_create() / db_update()
   • [x] db_fill() based on output of function wasa_reservoir_par()
   • [x] db_check()

2. small reservoirs:

   • [x] db_create() / db_update()
   • [x] db_fill() based on output of function ...()
   • [x] db_check()

3. river (UHG-routing):

   • [x] db_create() / db_update()
   • [x] db_fill() based on output of function ...()
   • [x] db_check()

4. river (Muskingum-routing):

   • [ ] db_create() / db_update()
   • [ ] db_fill() based on output of function ...()
   • [ ] db_check()