- Generated on Sun Dec 7 2025 00:13:44 for Alpine3D by
1.9.8
|
Alpine3D
Spatially distributed alpine surface processes model
|
Here, we expose the core principles underlying the Alpine3D model. This should just give a quick overview of the model and help you understand the global architecture of Alpine3D.
The individual modules are described here below and contain references to the relevant papers.
Here we expose the very foundations of Alpine3D. These remain valid independently of which modules are enabled when running the model.
At the core of the model, is the SNOWPACK model, a physically based, energy balance model for a 1D soil/snow/canopy column. This gives us a very detailed description of the snow stratigraphy and a very good evaluation of the mass and energy balance (therefore also of quantities such as Snow Water Equivalent (SWE) or temperature profile). This 1D energy balance is performed for each pixel of the domain (therefore it is a distributed SNOWPACK simulation) and for one time step (usually one hour). Any quantity that the user would like to get out of the simulation can be written out from this module.
In order to perform a SNOWPACK simulation at every pixel of the domain, it is necessary to get the meteorological forcing for each pixel. But the measured meteorological parameters are usually measured by a set of stations, which means that the data is available at a set of points. Interpolating these points measurements to every pixels of the domain is performed by the means of statistical interpolations with MeteoIO. if the forcing data is coming out of another model (such as a meteorological model), most probably the input grids have a resolution that is very insufficient for Alpine3D and therefore need downscaling. If the downscaling factor is very large, we often end up with only a few points from the meteorological model that are part of the Alpine3D domain, therefore such points can be considered as "virtual stations" and spatially interpolated similarly to weather stations.
The core principles laid out in the previous section rely on the assumption that there are no lateral fluxes, which is too strong of an assumption. Therefore the lateral fluxes deemed relevant are introduced by other modules:
Once the albedo of each pixels of the domain have been initialized or taken from the last time step, the radiation balance is computed. First, the incoming short wave radiation measured at one reference station is used to compute the splitting (between direct and diffuse). This splitting will be assumed to be constant over the whole domain. Then, according to the meteorological parameters and elevation of each pixel, the direct and diffuse radiation fields are computed. Since the position of the sun has been computed, it is used to compute the topographic shading for each pixel. If the terrain reflections have been enabled, a radiosity approach is used to compute the reflections by the surrounding terrain. Finally, the direct and diffuse radiation fields are returned.
Externally computed wind fields (for example with ARPS) are assigned to each time steps. If the surface shear stress exceeds a given threshold at a given pixel, the saltation will be computed. This in turn can feed the suspension if the saltation layer is saturated. While in suspension, some of the mass will sublimate and contribute to the relative humidity field.
Several options are available for collecting the melt water or precipitation running out of each pixel. The historical approach relies on the PREVAH hydrological modeling system to perform on-the-fly hydrological simulation. Another approach consists of collecting the runoff sums for each sub-catchments defined by the user. Finally, it is also possible to output the hourly distributed runoff (ie the runoff for each pixel, once per hour) and process this runoff in an external model. This approach enables the external model to be calibrated without having to re-run Alpine3D.
1.9.8