Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specifying material IDs on Gmsh imports #13514

Merged
merged 1 commit into from
Mar 13, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 4 additions & 1 deletion examples/step-49/doc/intro.dox
Original file line number Diff line number Diff line change
Expand Up @@ -263,7 +263,10 @@ The other four surfaces are declared in a similar way.

Next we define the physical surface itself. This line is what makes our mesh 2D.
The values in the braces on the right hand side are the tags for the `Plane Surface`s
we declared above.
we declared above. The number in the parentheses of physical surfaces will become the
material ID of the mesh as well. For more information about material IDs, check the
glossary entry
@ref GlossMaterialId "material indicators" .

@code
Physical Surface(2) = {1, 2, 3, 4};
Expand Down
3 changes: 2 additions & 1 deletion include/deal.II/grid/grid_in.h
Original file line number Diff line number Diff line change
Expand Up @@ -572,7 +572,8 @@ class GridIn
*
* If the physical groups are not named, then the behavior is the same as
* the other read_msh() function, i.e., the physical tag itself is interpreted
* as a boundary or material id.
* as a boundary or material id. Physical surface numbers created in Gmsh,
* which can be seen in the .geo file, become material IDs.
*
* @ingroup simplex
*/
Expand Down