So far, the parallel FEM scheme with PETSc cannot be used by the all processes using linear and quadratic function spaces simultaneously. They are
scripts/env/eve/cli.shpartmeshcmake <path_to_source> -DOGS_BUILD_UTILS=ONscripts/env/eve/petsc.shcmake <path_to_source> -DOGS_USE_PETSC=ONmakeIn order to discretize the domain of a unit cube do bin/generateStructuredMesh -o cube_1x1x1_hex_axbxc.vtu -e hex --lx 1 --ly 1 --lz 1 --nx a --ny b --nz c where a, b, and c should be choosen according to the needs.
a |
b |
c |
#cells in 10^6 | compute cores | success |
|---|---|---|---|---|---|
| 150 | 150 | 150 | ~ 3.38 | 20 | yes |
| 175 | 175 | 175 | ~ 5.36 | 20 | yes |
| 190 | 190 | 190 | ~ 6.86 | 20 | yes |
| 196 | 196 | 196 | ~ 7.59 | 20 | no |
| 216 | 216 | 216 | ~ 10.08 | 40 | yes |
| 236 | 236 | 236 | ~ 13.14 | 40 | yes |
| 292 | 292 | 292 | ~ 24.90 | 80 | yes |
| 368 | 368 | 368 | ~ 49.84 | 160 | yes |
| 422 | 422 | 422 | ~ 75.15 | 240 | yes |
| 465 | 465 | 465 | ~ 100.54 | 320 |
For the boundary conditions, if they are simple (_i.e._ homogeneous), the simplest .gml file is sufficient for the serial case, but for heterogeneous boundary conditions and parallelization boundary mesh files are needed. There are two possibilities to create such files:
.gml file, use constructMeshesFromGeometry tool which takes the mesh file and geometry and creates all the boundaries which are named in the .gml file with the required bulk_node_ids and bulk_element_ids mappings.identifySubdomains tool to create or verify the needed bulk_node_ids and bulk_element_ids mappings.partmeshbin/partmesh -i cube_1x1x1_hex_axbxc.vtu --ogs2metis cube_1x1x1_hex_axbxc.meshbin/partmesh -n number_of_partitions -m -i cube_1x1x1_hex_axbxc.vtu -- boundary_meshes*.vtu .bin files.This article was written by Thomas Fischer. If you are missing something or you find an error please let us know.
Generated with Hugo 0.64.1. Last revision: February 9, 2020
Commit: [web] Fixed links. c9e2550cc
| Edit this page on