[Mesh] Optional neighbour computations
In some tools the computation of element neighbour information isn't necessary. Since this neighbour computation is expensive the following MR introduces a flag to make the computation optional. Time measurements for two of the changed tools:
| tool | current master | without neighbour computation |
|---|---|---|
| identifySubdomain | 18 min | 11 min |
| ReorderMesh | 10 min | 2 min |
Tools with changed behavior:
- Mesh2Raster
- OGS2VTK
- PVD2XDMF
- VTK2OGS
- VTK2TIN
- generateMatPropsFromMatID
- AddFaultToVoxelGrid
- AddLayer
- CreateBoundaryConditionsAlongPolylines
- ExtractMaterials
- Layers2Grid
MapGeometryToMeshSurface- MeshMapping
- MoveMesh
- NodeReordering
- PVTU2VTU
- ReorderMesh
- ResetPropertiesInPolygonalRegion
- convertToLinearMesh
- createLayeredMeshFromRasters
- createTetgenSmeshFromRasters
- editMaterialID
- ipDataToPointCloud
- removeMeshElements
- swapNodeCoordinates
- AssignRasterDataToMesh
- IntegrateBoreholesIntoMesh
- computeSurfaceNodeIDsInPolygonalRegion
- identifySubdomains
- ComputeNodeAreasFromSurfaceMesh
- PartitionMesh
- convertVtkDataArrayToVtkDataArray
- createNeumannBc
- scaleProperty
- createMeshElemPropertiesFromASCRaster
Tools without changed behavior:
- AddElementQuality
- createQuadraticMesh
- queryMesh
- reviseMesh
- constructMeshesFromGeometry
- postLIE
- MapGeometryToMeshSurface
-
Feature description was added to the changelog -
Tests covering your feature were added? -
Any new feature or behavior change was documented?
Edited by Tom Fischer