Alpine3D

Alpine3D is a spatially distributed (surface), three dimensional (atmospheric) model for analyzing and predicting dynamics of snow-dominated surface processes in mountainous topography.

spatially distributedthree dimensionalsnow-dominatedmountainous

Contributor(s)

Initial contribute: 2019-12-30

Authorship

:  
View
Is authorship not correct? Feed back

Classification(s)

Application-focused categoriesNatural-perspectiveLand regions
Application-focused categoriesNatural-perspectiveFrozen regions

Detailed Description

English {{currentDetailLanguage}} English

Quoted from: https://models.slf.ch/docserver/alpine3d/html/model_principles.html 

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. If you want to go deeper into the details, please have a look at the publications covering the whole model (M. Lehning et al. "ALPINE3D: a detailed model of mountain surface processes and its application to snow hydrology", Hydrological Processes, 20.10, 2006, pp 2111-2128; and P. Kuonen, M. Bavay, M. Lehning, "POP-C++ and ALPINE3D: petition for a new HPC approach", Advanced ICTs for disaster management and threat detection: collaborative and distributed frameworks, IGI Global, 2010, pp 237-61.) The individual modules are described here below and contain references to the relevant papers.

At the core...

Here we expose the very foundations of Alpine3D. These remain valid independently of which modules are enabled when running the model.

Distributed 1D soil/snow/canopy column

distributed_sn.png
Distributed SNOWPACK over the domain taking into account the land cover

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.

 

Distributed meteo fields

2d_interpolations.png
Spatially interpolating the meteorological fields

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.

 

Lateral fluxes

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:

  • the EBalance module computes the radiation fields, taking into account atmospheric cloudiness, topographic shading effects and reflections by the surrounding terrain.
  • the SnowDrift module that simulates the transport of snow by the wind. It performs a 3D simulation of the saltation, suspension and diffusion processes.
  • the runoff module that collects the precipitation and/or melt water at each pixel to transfer it to an hydrological routing module

Radiation balance

ebalance.png
Radiation balance with shading and terrain reflections

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, see D. G. Erbs, S.A. Klein, J.A. Duffie, "Estimation of the diffuse radiation fraction for hourly, daily and monthly-average global radiation", Solar Energy, 28, 4, 1982, Pages 293-302 and summarized in M. Iqbal, "An introduction to solar radiation", 1983, Academic Press, ISBN: 0-12-373750-8). 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 ( J. Meeus, "Astronomical Algorithms", 1998, 2nd ed, Willmann-Bell, Inc., Richmond, VA, USA, ISBN 0-943396-61-1), 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 ( N. Helbig, H. Löwe, M. Lehning, "Radiosity Approach for the Shortwave Surface Radiation Balance in Complex Terrain", Journal of the Atmospheric Sciences, 66.9, 2009). Finally, the direct and diffuse radiation fields are returned.

 

Snowdrift

snowdrift.png
Snowdrift: saltation, suspension, sublimation

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 ( C. D. Groot Zwaaftink et al. "Drifting snow sublimation: A high‐resolution 3‐D model with temperature and moisture feedbacks", Journal of Geophysical Research: Atmospheres (1984–2012), 116.D16, 2011).

 

Runoff

runoff.png
Runoff: simple bucket approach with PREVAH or sub-catchments sums

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 ( D. Viviroli et al. "An introduction to the hydrological modelling system PREVAH and its pre-and post-processing-tools", Environmental Modelling & Software, 24.10, 2009, pp 1209-1222) to perform on-the-fly hydrological simulation. Another approach consists of collecting the runoff sums for each sub-catchments defined by the user (M. Bavay, T. Grünewald, M. Lehning, "Response of snow cover and runoff to climate change in high Alpine catchments of Eastern Switzerland", Advances in Water Resources, 55, 2013, pp 4-16). 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 ( F. Comola et al. "Comparison of hydrologic response between a conceptual and a travel time distribution model for a snow-covered alpine catchment using Alpine3D", EGU General Assembly Conference Abstracts, Vol. 15, 2013; J. Magnusson et al. "Quantitative evaluation of different hydrological modelling approaches in a partly glacierized Swiss watershed", Hydrological Processes, 25.13, 2011, pp 2071-2084). This approach enables the external model to be calibrated without having to re-run Alpine3D.

模型元数据

{{htmlJSON.HowtoCite}}

{{htmlJSON.Copy}}

Contributor(s)

Initial contribute : 2019-12-30

{{htmlJSON.CoContributor}}

Authorship

:  
View
Is authorship not correct? Feed back

QR Code

×

{{curRelation.overview}}
{{curRelation.author.join('; ')}}
{{curRelation.journal}}









{{htmlJSON.RelatedItems}}

{{htmlJSON.LinkResourceFromRepositoryOrCreate}}{{htmlJSON.create}}.

Drop the file here, orclick to upload.
Select From My Space
+ add

{{htmlJSON.authorshipSubmitted}}

Cancel Submit
{{htmlJSON.Cancel}} {{htmlJSON.Submit}}
{{htmlJSON.Localizations}} + {{htmlJSON.Add}}
{{ item.label }} {{ item.value }}
{{htmlJSON.ModelName}}:
{{htmlJSON.Cancel}} {{htmlJSON.Submit}}
名称 别名 {{tag}} +
系列名 版本号 目的 修改内容 创建/修改日期 作者
摘要 详细描述
{{tag}} + 添加关键字
* 时间参考系
* 空间参考系类型 * 空间参考系名称

起始日期 终止日期 进展 开发者
* 是否开源 * 访问方式 * 使用方式 开源协议 * 传输方式 * 获取地址 * 发布日期 * 发布者



编号 目的 修改内容 创建/修改日期 作者





时间分辨率 时间尺度 时间步长 时间范围 空间维度 格网类型 空间分辨率 空间尺度 空间范围
{{tag}} +
* 类型
图例


* 名称 * 描述
示例描述 * 名称 * 类型 * 值/链接 上传


{{htmlJSON.Cancel}} {{htmlJSON.Submit}}
Title Author Date Journal Volume(Issue) Pages Links Doi Operation
{{htmlJSON.Cancel}} {{htmlJSON.Submit}}
{{htmlJSON.Add}} {{htmlJSON.Cancel}}

{{articleUploading.title}}

Authors:  {{articleUploading.authors[0]}}, {{articleUploading.authors[1]}}, {{articleUploading.authors[2]}}, et al.

Journal:   {{articleUploading.journal}}

Date:   {{articleUploading.date}}

Page range:   {{articleUploading.pageRange}}

Link:   {{articleUploading.link}}

DOI:   {{articleUploading.doi}}

Yes, this is it Cancel

The article {{articleUploading.title}} has been uploaded yet.

OK
{{htmlJSON.Cancel}} {{htmlJSON.Confirm}}
D4Lr6.hXgxWU