We have a HYPE model with a multi-basin outlet lake which does run anymore with versions 5.34.0 or higher. In the release notes it is mentioned that a multi basin lake is not compatible with floodplains. We have not implicitely defined flood plains (no flooddata.txt file, no flood plain related parameters). Our tests also stop when floodplain info are to be assessed.
How to deal with this? Can a multi basin lake model be shared as a demo?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As default floodplains are not used. Then no FloodData.txt file need to be present.
To model floodplains the modeloption floodmodel need to be set (larger than 0), and then a FloodData.txt file is necessary.
On wiki for info.tx:
floodmodel 0/1/2/3 defines which model to use for floodplains. Default is none (0), alternatives are a simple model (1) and a model with soilroutines (2). A fourth option (3) is to use the model with soil routines and connecting floodplains. All requires floodplain information in input file FloodData.txt).
Regarding multi-basin lakes and floodplains, you should be safe with your multi-basin lake if you not turn on modeloption floodmodel.
/Lotta
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have a HYPE model with a multi-basin outlet lake which does run anymore with versions 5.34.0 or higher. In the release notes it is mentioned that a multi basin lake is not compatible with floodplains. We have not implicitely defined flood plains (no flooddata.txt file, no flood plain related parameters). Our tests also stop when floodplain info are to be assessed.
How to deal with this? Can a multi basin lake model be shared as a demo?
We found the solution in the meantime. We suggest mentioning that the file flooddata.txt should always be present :)
Hi,
I'm not sure I understand the problem here.
As default floodplains are not used. Then no FloodData.txt file need to be present.
To model floodplains the modeloption floodmodel need to be set (larger than 0), and then a FloodData.txt file is necessary.
On wiki for info.tx:
floodmodel 0/1/2/3 defines which model to use for floodplains. Default is none (0), alternatives are a simple model (1) and a model with soilroutines (2). A fourth option (3) is to use the model with soil routines and connecting floodplains. All requires floodplain information in input file FloodData.txt).
Regarding multi-basin lakes and floodplains, you should be safe with your multi-basin lake if you not turn on modeloption floodmodel.
/Lotta