GEOtop 0.9375Lavagna, branches under development of the Distributed Hydrological Model GEOtop

1. GEOtop 0.9375Lavagna:
a new branch of the Distributed
Hydrological Model GEOtop 0.9375
(Rigon et al.)
Emanuele Cordano et al.
GEOFRAME Cafe’, 6 Novembre 2008
Emanuele Cordano

2. OUTLINE
1) Brief Introduction to Distributed Hydrological
physically-based model GEOtop 0.9375 and some
application
2) Input and output data files
3) A proposal: the GEOtop 0.9375Lavagna version (the
system of keywords)
4) How can we prepare the input files for a simulation?
5) Your opinion about this!

3. GEOtop 0.9375 (www.geotop.org)
• Distributed, terrain based, physically based ✴MACRO-CLIMATE: geographic
model of the hydrological cycle (Rigon et al, 2006, location (latitude, solar
Bertoldi et al, 2006 )
radiation, air temperature)
• coupled solution of energy and water balance ✴MICRO-CLIMATE: vegetation,
(Richards Equation for subsurface flow): the
snow depth, aspect
balance are applied at different layers
• solves soil-snow energy and mass exchange at
the surface ( Endrizzi 2007 )
IN-BASED, Horton
Dunne
model of THE Saturatio
LE
ration of a
d a land surface
Surface
e (from 2 m to
Unsaturat
model it deals
BUTION OF
ORECASTING Modified from VIC (Liang et al., 1994)
Saturate
d Layer:
ACE MODEL it
Modified from Abbot et
sphere
nsing)

4. DTM
GEOMORPHOLOGICAL ANALYSIS
Horton Machine, Rigon et al.
Aspect
www.jgrass.org

5. INPUT DATA in GEOtop 0.9375
MORPHOLOGY: Elevation, slope, drainage directions, etc...
INITIAL CONDITIONS: initial 3D distribution of soil water pressure
head , soil temperature and soil ice content, etc ...
SOIL TYPE: hydraulic and thermal soil properties (soil water retention
and conductivity curves)
LAND USE: parameteriation of low atmosphere turbolence, surface runoff,
vegetation canopy,surface roughness
METEO: rain, air temperature, wind velocity, relative humidity short-wave
and long-wave radiation, longwave emissivity, albedo,
ADDITIONAL PARAMETERS: parameters related to snow, channel routing,
infiltration, etc.

6. OUTPUT DATA in GEOTop 0.9375
LOCAL INFORMATION vs time: soil temperature , pressure head, water
and heat fluxes,
2D MAP (every prefixed time step) : precipitation, latent (evaporation)
and sensible heat fluxes snow depth, glacier depth, surface water depth,
radiation, etc.
3D MAP : soil (liquid) water and ice content, soil pressure head, soil
temperature, subsurface lateral fluxes, etc...
RIVER FLOW DISCHARGE AT THE OUTLET VS TIME

7. METHODS in GEOTop 0.9375 (time loop)
ALLOCATE STRUCT AND READ DATA
TIME LOOP
spatialization of meteo forcings
heat balance (1D)
water balance (1D Richards’Equation)
lateral water flow
WRITE TEMPORARY OUTPUTS
DEALLOCATE STRUCT

8. What about input files in
0.9375 version
Going into details...
developed in 2007 by Stefano Endrizzi

9. FILE TYPES in 0.9375 (1)
text! : ascii standart file (ANSI) often written with the
!
FluidTurlte formalism
text_m: series ascii standard file (ANSI) files related to
some control pixels (the name must not contain the
extension) Example: the file name is po_point , tha ascii
files po_point0001.txt,
po_point0002.txt,po_point0003.txt , etc. for every
control pixel .! ! ! ! ! !! ! ! !

10. FILE TYPES in 0.9375 (2)
map2D! : ascii file contained in a raster map with a
format recognized by GEOtop (the name must not
contain the extension,the format is given by the
extension, for instance .asc=grassasci or esriiasci)
Example: the map name is slope , the ascii file is
slope.asc
tensor3D : ascii files contained in a raster map with
a format recognized by GEOtop (the name must not
contain the extension,the format is given by the
extension, for instance .asc=grassasci or esriiasci)!
Example: the tensor name is theta, the ascii files are
theta0001.asc, theta0002.asc, theta0003.asc, ... for
each layer.

11. FILE TYPES in 0.9375 (3)
map2D plus time: ascii files contained in a raster map
with a format recognized by GEOtop (the name must
not contain the extension,the format is given by the
extension, for instance .asc=grassasci or esriiasci)
Example: the tensor name is snowdepth, the ascii files
are snowdepth001.asc, snowdepth002.asc,
showdepth003.asc, ... for each printing time step.

12. FILE TYPES in 0.9375 (4)
tensor3D plus time: ascii files contained in a raster map
with a format recognized by GEOtop (the name must
not contain the extension,the format is given by the
extension). Example: the tensor name is pressurehead,
the ascii files are pressurehead001L0001.asc,
pressurehead001L0002.asc, ... ,
pressurehead004L0001.asc, ... for each printing time
step (before L) and layer (after L).!! ! ! !
! ! ! ! !

13. Input and output data files: some problems
Geotop should describe terrestrial
hydrological cycle and can be applied to
different watersheds with different climates!!
A lot of parameters were often assigned in
the same file. Some maps were preprocessed
by GEOtop, as a “black box” .
The user should known hydrological processes
which can be unuseful for a specific
simulations.
The code is a little bit “monolitic”

14. Input and output data files: what it is needed
The user should put only parameters useful
for the problem analyzed
Preprocessing by external programs (ex.
Jgrass or grass for maps) and should be
removed from GEOtop.
A developer/modeler should modify the
descriptions of the investigated physical
processes without affecting the core of the
source code.

15. Can we study these two different mountain
catchments in Italy with the same model
(GEOtop or GEOframe) ?
3000 m sea level
... “whithout the agonizing pain!!” (J.R.S.)

16. The 0.9375Lavagna version
The 0.9375Lavagna contains a new way of
giving input data;
In the 0.9375Lavagna the user queries the
model by a system of keywords;
Actually only the READ DATA block was
modified, the core (methods used for solving
the equation) of the code is equal to the
“elder” code of 0.9375;
Equations and descriptions of some
processes were being developed in other
branches which will be merged as soon.

17. Why the name Lavagna?
Slate is the stone from Lavagna,
Liguria!!

18. The goal of 0.9375Lavagna in
the Geotop Project
Only used data and
methods used must
declared in a
blackboard. A file
name bust be followed
by a keyword for
identification.
This is a joke from www.hetemeel.com

19. 0.9375Lavagna : date file and
model component classes
DATA FILE (e.g. map of rainfall,...) MODEL COMP. (e.g. soil water rention cure , ...)

20. DATA FILE (e.g. map of rainfall,...) MODEL COMP. (e.g. soil water rention cure , ...)
Set of possible files Set of possible submodels
F Subsets of utilized
M
files and
submodels for
Fs the specific
Ms
simulation
(CONFIGURATION)

21. 3 necessary input files:
geotop.init It defines all the possible
elements of F and M (file and
submodels)
It defines all the possible
geotop.struct methods by which each
submodel can be solved
It declares only the file and the
geotop.inpts submodels used for the
simulation

22. The blackboard : geotop.inpts
/**
geotop.inpts
author ....
date November 2008
THIS FILE MUST BE MODIFIED BY THE USER TO DEFINE THE SIMULATION
*/
index{2}
/** I/O FILE STRING USED IN THE SIMULATION S2 */
1: string array files {
morphology/04piDTM,I_MORPHO_ELEVATION,
morphology/05pi_draindir,I_MORPHO_DD,
....}
/**
I/O FILE STRING USED IN THE SIMULATION S2
*/
2: string array submodels {
0.9375ELDER, VERTICAL_WATER_BALANCE,
0.9375ELDER,ENERGY_BALANCE, ...}

23. The keyword glossary (1):
/**
geotop.init
geotop.inpts
author ....
date November 2008
THIS FILE CANNOT BE MODIFIED BY THE USER!!!*/
index{2}
/** Keyword for all optional I/O files which occur to run GEOtop
All keyword are precede as follows:
I_* INPUT FILE
O_*OUTPUT FILE
C_* CONTROL RESUMING FILE ....}
*/
1: string array keyword_files {
I_MORPHO_ELEVATION, Digital Terrain Model of the basin (without extension),
O_WATERCONTENT_CONTROLPIXELS, output text files with time series of soil water
content at the control pixels (whitout extension) , ....}
/** submodels */
2: string array submodels {
VERTICAL_WATER_BALANCE, keywords for vertical water balance,
ENERGY_BALANCE, keywords for energy balance, ...}

24. The keyword glossary (2):
geotop.struct, an example
/**
geotop.struct
author ....
date November 2008
THIS FILE CANNOT BE MODIFIED BY THE USER!!!*/
index{2}
1: string array model option water_balance {
VERTICAL_WATER_BUCGET, keywords for vertical water budget,
0.9375ELDER, vertical water balance solved according to the the quot;classicquot; version of 0.9375,
OFF, energy balance turned off
}
2: string array model option energy_balance {
ENERGY_BALANCE, keywords for energy balance,
0.9375ELDER, energy budeget solved according to the the quot;classicquot; version of 0.9375,
OFF, energy balance turned off
}

25. 3 necessary input files:
geotop.init It is modified by the developers
or the advenced users
It is modified by the developers
geotop.struct or the advanced users. Now it is
not still used!!
It is modified by the user, this
geotop.inpts
is the “blackboard”

26. Let’s try to describe with UML...

27. An Example...

29. Some tips
The system of keywords is not still applied to
the model components: we are expecting
future developments of geotop.
The input or output files can be modified (new
format for file of meteo data time series !).
For each added file, we must add a suitable
keyword in the list in the geotop.init file and
in the source code.

30. For starting users, how
can we make some input
files ?
Text files: we can easily modify them from the
template
Meteo Data Time Series: suitable formats are being
developed for the future release (see
0.9375Andromeda) . Under construction.
2D Maps and 3D tensor: Jgrass Console (see some
scrips on http://jgrass.wiki.software.bz.it/jgrass/
Example_scripts_from_users

31. http://jgrass.wiki.software.bz.it/jgrass/
Example_scripts_from_users (thanks to HydroloGis)

32. Further information about the use of
0.9375Lavagna will be updated in the wikies
www.geotop.org and www.jgrass.org.
The code can be found in the branches
folder of our SVN repository and some parts
are Doxygen documented.

33. What do you want to do with this?