LISVAP use cases

We have included three test cases for you to try to run LISVAP. Two tests allow the potential evapo(transpi)ration in Europe. The first test makes use of the meteorological input data from the EFAS project, the second test makes use of the data from the CORDEX project. The third test case allow the modelling of the potential evapo(transpi)ration at the global scale, according to the GloFAS set-up. Each test case includes all the data necessary to do a 15 day simulation, meaning the base maps, meteorological input data and also the prefilled settings file: tests_efas.xml,tests_cordex.xml, and tests_glofas.xml. Additionally we also provide the corresponding output files for you to verify your own results.

In order to run the test cases follow the following steps:

Step 1. Grab the data

You can easily get that data from the Docker container or just by cloning the repository.

From Docker

For example, to copy those files from Docker image to your host (e.g. in the folder /local/folder/lisvap/input)

docker run -v /local/folder/lisvap/input:/input jrce1/lisvap:latest usecases

Then you will receive:

Copying basemaps to /input/...
copy input files to /input/cordex......
copy cordex settings to /input/...
copy input files to /input/efas......
copy efas settings to /input/...

After executed the command, you will find data under /local/folder/lisvap/input directory, in three subfolders efas, cordex, and glofas.

From source code

If you clone/download LISVAP github repository, you find relevant files under basemaps and tests/data folder:

  1. input and settings files
  2. basemaps

Step 2. Adjust settings file

You will find the settings files (test_efas.xml and test_cordex.xml) in your local directory /local/folder/lisvap/input. The only thing you need to adjust are paths specifications in the FILE PATHS section. As the paths definition depends on the execution environment (i.e. Docker or local host), we specified the file path specification in the comment section of each variable


        FILE PATHS

    <textvar name="PathOut" value="/output">
            Output path
            for Docker: /output
            from local host: e.g. E:/lisflood_test/Lisvap/output

    <textvar name="PathBaseMapsIn" value="/input/basemaps">
            Path to input base maps
            for Docker: /input/basemaps
            from local host: e.g. E:/lisflood_test/Lisvap/input/basemaps

    <textvar name="PathMeteoIn" value="/input/efas">
            Path to input raw meteo maps
            for Docker: /input/efas or /input/cordex or /input/glofas
            from local host: e.g. E:/lisflood_test/Lisvap/input/efas or E:/lisflood_test/Lisvap/input/cordex or E:/lisflood_test/Lisvap/input/glofas


Step 3. Run

From Docker

docker run -v /:/tmp -v /local/folder/lisvap/input:/input -v /local/folder/lisvap/output:/output jrce1/lisvap:latest /input/test_efas.xml -v -t

From source code

Assuming you copied the edited settings file in /local/folder/lisvap/input/ folder:

cd src
python /local/folder/lisvap/input/test_efas.xml -v

Step 4. Verify the output

You will find output maps under the folder you set up in PathOut. These maps are netCDF mapstacks and can be viewed with a netCDF reader like Panoply ncview. You can compare your output to the reference files for EFAS, CORDEX, and GloFAS found on github repository.