com9MoTVoellmy: NGI MoT-Voellmy =============================== .. Note:: This module (as well as this documentation) is currently under development and highly experimental! The parameter settings are completely untested and unchecked. Do not expect sensible results with the included settings! :py:mod:`com9MoTVoellmy` allows to run the MoT-Voellmy code by Norwegian-Geotechnical-Institute (`MoT-Voellmy github repository `_). More information and background can be found there as well `MoT-Voellmy Documentation `_ **This documentation covers issues related directly to running MoT-Voellmy with the help of AvaFrame** There are 2 ways of running, please choose below. MoT Voellmy via QGis -------------------- Installation on Windows: ^^^^^^^^^^^^^^^^^^^^^^^^ #. Start QGis and go to `Plugins` -> `Manage and install plugins` #. Choose `All`, search for `OpenNHM` and install/update #. You find the `OpenNHM` toolset in the `Processing Toolbox` #. Go to `AvaFrame_experimental` and start `MoTVoellmy (com9)` Input ^^^^^ For additional info, see also `NGI Documentation `_. Required is * digital elevation model as raster file with `ESRI grid format `_. ONE of the following: * release area scenario as (multi-) polygon shapefile - the release area polygon must not contain any "holes" or inner rings - the release area name should not contain an underscore. - recommended attributes are *name*, *thickness* (see :ref:`moduleCom1DFA:Release-, entrainment thickness settings`) - ALL features within one shapefile are released at the same time (and interact), this is what we refer to as *scenario* - if you want to simulate different scenarios with the same features, you have to copy them to separate shapefiles * release area scenario as raster file - same specifications as the DEM (extent, cellsize) And the following optional raster files, in the same specification as the DEM (extent, cellsize): * mu / Dry friction coefficient. If this is given, k needs to be set as well. * k / Turbulent friction coefficient. If this is given, mu needs to be set as well. * b0 / Erodible snow depth. If this is given, tau_c needs to be set as well. * tau_c / Snow shear strength. If this is given, b0 needs to be set as well. * nd / Forest density. If this is given, bhd needs to be set as well. * bhd / Tree diameter. If this is given, nd needs to be set as well. The `Destination Folder` should be empty! Outputs ^^^^^^^ After you ran the simulation, the peak fields will be loaded in QGis and the `Destination Folder` will contain, results, plots, and configuration files. MoT Voellmy via the script variant ---------------------------------- Binary ^^^^^^ The MoT-Voellmy binary is compiled automatically during ``pip install`` and in released wheelsm, no manual steps needed. The build process fetches the latest C source from the `upstream repository `_ and compiles it with ``gcc``. To compile manually (e.g. after updating the upstream source): .. code-block:: bash pixi run compilemot To compile from a local C source file instead of downloading from GitHub: .. code-block:: bash pixi run compilemot /path/to/MoT-Voellmy.c If ``gcc`` is not available, download the precompiled binary from the upstream repository and copy it to ``avaframe/com9MoTVoellmy/``. On Windows, install MinGW to use ``gcc``. The expected binary names are ``MoT-Voellmy_linux.exe``, ``MoT-Voellmy_win.exe``, or ``MoT-Voellmy_mac.exe`` depending on your platform. To run ^^^^^ * go to ``AvaFrame/avaframe/com9MoTVoellmy`` * copy ``com9MoTVoellmy/com9MoTVoellmyCfg.ini`` to ``com9MoTVoellmy/local_com9MoTVoellmyCfg.ini`` and edit (if not, default values are used) * make sure all the required inputs are available in the avalanche directory * enter the path to the desired dataset in ``local_avaframeCfg.ini`` * run:: pixi run python runCom9MoTVoellmy.py