![]() ![]() | |
![]() ![]() | Return the library version |
![]() ![]() | This module contains the routines to perform profile aggregation |
![]() ![]() | |
![]() ![]() | BoundCond is used to set Neumann boundary conditions |
![]() ![]() | Reading snow profile data in CAAML format. Reads in CAAML snow profile data, the CAA-IACS international standard |
![]() ![]() | Computes interception of precipitation and radiation, and reduction of windspeed in a canopy layer above thesnow or soil surface. This has been published in Gouttevin, I., M. Lehning, T. Jonas, D. Gustafsson, and Meelis Mölder, "A two-layer canopy model with thermal inertia for an improved snowpack energy balance below needleleaf forest (model SNOWPACK, version 3.2. 1, revision 741).", Geoscientific Model Development 8.8, pp 2379-2398, 2015 |
![]() ![]() | Canopy data used as a pointer in the SnowStation structure
|
![]() ![]() | CurrentMeteo is the class of interpolated meteo data for the current calculation time step It contains some additional and very important derived parameters such as the roughness length or running mean values |
![]() ![]() | ELEMENT DATA used as a pointer in the SnowStation structure NOTE on M below: this is the mass of an element that is neither changed by phase changes nor densification. It is set in the data initialization and used to compute the stress field. It can ONLY be changed by the WATER TRANSPORT or SURFACE SUBLIMATION or WIND TRANSPORT routines |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | Parameters of the different layers of the snowpack The layers form a vector within the SSdata (profile) data structure |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | NODAL DATA used as a pointer in the SnowStation structure |
![]() ![]() | |
![]() ![]() | This class contains the phase change routines for the 1d snowpack model It also updates the volumetric contents of each element |
![]() ![]() | Structure of double values for output to SDB |
![]() ![]() | |
![]() ![]() | This module contains the solver for the 1d Richards Equation for the 1d snowpack model |
![]() ![]() | Class to collect the information about the current simulation (version, date) |
![]() ![]() | This module contains the saltation model of Judith |
![]() ![]() | |
![]() ![]() | The CHUNK_DATA is used to keep track of allocated memory chunks ( block of memory ). For each allocated chunk we store the pointer returned from the memory allocator, so that a later deallocation of the memory will be possible |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | When the user define a matrix, the software return a pointer to an opaque type i.e. a pointer to void as index to reference the matrix. This pointer is actually the pointer to the SD_MATRIX_DATA data structure. This date structure is defined as a union of differnet matrix data representations, and the type of data actually stored depend on the evolution of the algorithn |
![]() ![]() | The data structure to store the matrix for numerical factorization is a simple one. The matrix structure is after the mmd sorting algorithm and the symbolic factorization mainly composed of clustered non-zero matrix coefficients which form blocks. In this case we use a data strucutre to represent these row and column blocks. NOTE: The row blocks are simply what in the literature is specified as supernodes. We have kept the data structure as simple as possible to minimize the numerical operations and so the execution time. NOTE: When we define a system we have the possibility to define a multiplicity factor. This allows us to perform all initialization tasks ( input of incidences, symbolic factorization, block format calculation ) with all indices modulo the multiplicity factor to save time and memory. Thus the computed block format is always the same for any specified multiplicity factor only the block bounds are different. ATTENTION: The size of the permutation vector is only Dim/(Multiplicity Factor) |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | SN_SNOWSOIL_DATA includes all important station parameters as well as LayerData This data structure will have to be replaced by something a little more complicated soon ??? For now it is simply an efficient way of creating a snowpack to investigate |
![]() ![]() | |
![]() ![]() | Optical Properties of snow |
![]() ![]() | This class contains the computation of local snow drift and the associated erosion |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | |
![]() ![]() | Defines structure for snow profile layers |
![]() ![]() | Station data including all information on snowpack layers (elements and nodes) and on canopy This is the PRIMARY data structure of the SNOWPACK program It is used extensively not only during the finite element solution but also to control the post-processing writes. It is initialized from SN_SNOWSOIL_DATA (at present) |
![]() ![]() | This class contains the stability routines for the snowpack model. Stability is found for each LAYER (i.e. finite element) and INTERFACE (i.e. node). Subsequently, the element data contains a variable S_dr (layer stability for direct action avalanches) and the nodal data contains the varialble S_i (interface stability). The station data contain S_class an overall stability estimation for the profile based on hand hardness, grain class and a slab characterization. At the end, the stability index approach is compared to this profile characterization to check consistency/reliability |
![]() ![]() | Implementations of various algorithms useful for evaluating the stability. These algorithms fall within the following categories: |
![]() ![]() | Layer shear strength evaluation parameters. This class contains layer properties useful for the shear strength evaluation |
![]() ![]() | |
![]() ![]() | Class for recording reference properties of tagged elements |
![]() ![]() | |
![]() ![]() | This module contains water transport routines for the 1d snowpack model |
![]() ![]() | Spectrum of incoming solar radiation |
![]() ![]() | ZwischenData contains "memory" information mainly for operational use It is used to prepare some parameters of qr_Hdata. This data is read from and written to *.sno or .haz files respectively |