lisflood-model 3.0.2

LISFLOOD model python module

Lisflood OS

This repository hosts source code of LISFLOOD model. Go to Lisflood OS page for more information.

Other useful resources

Project	Documentation	Source code
Lisflood	Model docs	https://github.com/ec-jrc/lisflood-code (this repository)
	User guide
Lisvap	Docs	https://github.com/ec-jrc/lisflood-lisvap
Calibration tool	Docs	https://github.com/ec-jrc/lisflood-calibration
Lisflood Utilities		https://github.com/ec-jrc/lisflood-utilities
Lisflood Usecases		https://github.com/ec-jrc/lisflood-usecases

Notes for Release 3.0.0

With version 3.0.0, the computation of Qlimit has been edited.

This could lead to substantial differences in model output, and a new calibration of parameter QSplitMult is required. QLimit is a threshold value. Floodplain routing (i.e. the second line of routing) starts when the channel discharge exceeds the value QLimit (bankfull discharge).

The definition of QLimit was edited to allow a more physically based assessment of its value, which is now independent of the number of routing steps. QLimit is now defined as the product of AvgDis (average discharge value, as computed by the prerun) and QSplitMult.

The value of the coefficient QSplitMult can be calibrated or provided as input according to statistical relationships. It is here noted that this edited definition of QLimit is consistent with the computation of M3limit.

Quick start

You can use conda environment to easily install dependencies.

• Install miniconda
• Create a conda env named "lisflood" and install dependencies:

conda create --name lisflood python=3.7 -c conda-forge
conda activate lisflood
conda install -c conda-forge pcraster

• Install lisflood-model pypi package

pip install lisflood-model

Command above will also install the executable lisflood in the conda env, so that you can run LISFLOOD with the following:

lisflood /absolute_path/to/my/local/folder/TestCatchment/settings/cold_day_base.xml

You can also clone the repository which contains datasets to test the model. Follow this instruction for a basic test (included in this repository under tests/data/TestCatchment1)

• Clone the master branch of this repository (you need to have git installed on your machine).

git clone --single-branch --branch master https://github.com/ec-jrc/lisflood-code.git

• Install requirements into a python 3 conda env

conda create --name lisflood python=3.7 -c conda-forge
conda activate lisflood
conda install -c conda-forge pcraster
cd lisflood-code
pip install -r requirements.txt

If you don't use conda but a plain virtualenv, you need to install PCRaster and GDAL by your own and include its python interface in PYTHONPATH environment variable. For details, please follow instruction on official docs.

3. Compile the cython module kinematic_wave_parallel_tool

To compile this Cython module to enable OpenMP multithreading (parallel kinematic wave):

• Delete the files *.so (if any) in directory hydrological-modules

• Inside the hydrological_modules folder, execute "python compile_kinematic_wave_parallel_tools.py build_ext --inplace"

Important: the module has to be compiled on the machine where the model is run - the resulting binary is not portable.

Then in the settings file the option "numberParallelThreadsKinematicWave" may take the following values: - "0" : auto-detection of the machine/node's number of CPUs (all CPUs are used minus 1) (do not set it if other simulations are running on the same machine/node) - "1" : serial execution (not parallel) - "2", "3", ... : manual setting of the number of parallel threads. (if exceeding the number of CPUs, the option is set to "0") -->

<textvar name="numCPUs_parallelKinematicWave" value="3"/>

4. Run a cold run for the test catchment

Now your environment should be set up to run lisflood. Try with a prepared settings file for one of the two test catchments:

python src/lisf1.py tests/data/TestCatchment/settings/cold_day_base.xml

If the command above successed without errors, producing dis.nc into tests/data/TestCatchment1/outputs folder, your lisflood installation was correct.

Docker image

You can use the updated docker image to run lisflood, so without taking care to install dependencies on your system.

Pull image from repository:

docker pull efas/lisflood:latest

Run test catchments in image:

docker run -v /absolute_path/to/my/local/folder:/usecases efas/lisflood:latest usecases

After this command, you can find all files to run a test against a catchment under the directory you mapped: /absolute_path/to/my/local/folder/TestCatchment1

Now, you can run LISFLOOD as a docker container to test included catchments. Only thing you need to do is to map the TestCatchment1 folder to the container folder input, by using -v option. In the XML settings file, all paths are adjusted to be relative to the very same settings file, so you don't need to edit paths, as long as you keep same folders structure.

Execute lisflood with a Docker image:

docker run -v /absolute_path/to/my/local/folder/TestCatchment:/input efas/lisflood /input/settings/cold_day_base.xml

Once LISFLOOD finished, you find reported maps in /absolute_path/to/my/local/folder/TestCatchment/outputs/ folder.

Pypi packaged LISFLOOD

LISFLOOD is also distributed as a standard python package. You can install the pip package in your Python 3 virtualenv:

pip install lisflood-model

Command above will also install the executable lisflood in the virtualenv, so that you can run LISFLOOD with the following:

lisflood /absolute_path/to/my/local/folder/TestCatchment/settings/cold_day_base.xml

IMPORTANT NOTE

Please note that there are known issues when installing the LISFLOOD code on Windows (source code and pypi package). We cannot provide Windows support and strongly recommend using LINUX to install the LISFLOOD code. Windows users are recommended to execute LISFLOOD with a Docker image.

Collaborate

If you find an issue in our code, please follow the GitHub flow to propose your changes (Fork, commit your changes and ask for a Pull Request). You are required to run unit tests during your development and before to propose a pull request.

To execute unit tests:

pytest tests/

Furthermore, before to propose a pull request, there are additional tests we ask you to execute:

pytest tests/ -m "slow

These tests could take 30 minutes or several hours, depending on your machine.

You can find full description and implementation details at Test documentation page.

Note: If yuor pull request is about a new feature you may want to integrate in LISFLOOD, ensure to include tests with good coverage for it.

For more info about pytest, see official website.