In this module, all parameter files are read in as lua script or a sample configuration is being loaded
Possible Parameter configuration - General Parameters - mus_scheme_layout_module "Scheme Definitions" - tem_debug_module "Debug Parameters"
This datatype describes the various settings to load from the configuration file.
| Type | Visibility | Attributes | Name | Initial | |||
|---|---|---|---|---|---|---|---|
| character(len=pathLen), | public | :: | prefix |
Location on disk to load the mesh data from. |
|||
| type(hvs_output_config_type), | public | :: | output |
Description of how the visualization output should be done. |
Read in LUA parameter file See http://www.lua.org for a reference on how to use Lua is a scripting language in itself which allows more complex parameter files including comments And load / create the mesh depending on the configuration
| Type | Intent | Optional | Attributes | Name | ||
|---|---|---|---|---|---|---|
| type(mus_hvs_config_type), | intent(out) | :: | me |
Musubi harvesting configuration to load when no tracking table is defined |
||
| type(mus_scheme_type), | target | :: | scheme |
scheme type |
||
| type(mus_varSys_solverData_type), | target | :: | solverData |
contains pointer to scheme, physics types |
||
| type(mus_geom_type), | intent(inout), | target | :: | geometry |
Treelmesh data |
|
| type(mus_param_type), | intent(inout), | target | :: | params |
Global parameters |
This routines load solver data from config file except tracking
| Type | Intent | Optional | Attributes | Name | ||
|---|---|---|---|---|---|---|
| type(mus_scheme_type), | target | :: | scheme |
scheme type |
||
| type(mus_varSys_solverData_type), | target | :: | solverData |
contains pointer to scheme, physics types |
||
| type(mus_geom_type), | intent(inout), | target | :: | geometry |
Treelmesh data |
|
| type(mus_param_type), | intent(inout), | target | :: | params |
Global parameters |