The one place for your designs
To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.
setting of [grid]extensions seems to not work with gmsh grids
Setting of [grid]extensions seems to not work with gmsh grids.
Summary
The configuration file guide states for the extensions setting in the configuration file:
Physical extensions of the domain in meters. Given in x, then y, then z-direction. If a mesh file is imported, they have to match its maximum extensions.
However, if I import a mesh file, the extensions seem to not matter (I only checked this qualitatively).
Steps to reproduce
The appended example has a gmsh file with extensions 2x2x2.1, the config file only has extensions of 1x1x1.
The results seem to have extensions of 2x2x2.1.
(The example is merely the case I was working on. If you need a minimal example, let me know).
What is the current bug behaviour?
Extensions in the config file seem to not matter when loading a gmsh file. However, the extensions are required. Without specifying them the following error is thrown:
Aborting DORiE after exception: RangeError [get:/Users/hbauser/DORiE/dune-common/dune/common/parametertree.hh:183]: Cannot parse value "NONE" for key "richards..grid.extensions"RangeError [parseRange:/Users/hbauser/DORiE/dune-common/dune/common/parametertree.hh:237]: as a range of items of type double (0 items were extracted successfully)
What is the expected correct behaviour?
If the extensions do indeed not matter, it should not be required to specify them.
If they do matter, I think it would be good to have a check whether they match the gmsh file (since the impact is not immediately obvious).