Gmsh material ID edits

diff --git a/examples/step-49/doc/intro.dox b/examples/step-49/doc/intro.dox
index 69aa56f8c2cd9cc381ad0fd827a3b6f997d66349..2790e1109b61f948aec3038ff868f71fdfd91354 100644 (file)
--- a/examples/step-49/doc/intro.dox
+++ b/examples/step-49/doc/intro.dox
@@ -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};

diff --git a/include/deal.II/grid/grid_in.h b/include/deal.II/grid/grid_in.h
index 3015ecd2402d58e086523d3e6c2e9273fa4c8962..0311c1ed58950265227f88a327f4dbd97490f6c1 100644 (file)
--- a/include/deal.II/grid/grid_in.h
+++ b/include/deal.II/grid/grid_in.h
@@ -572,7 +572,8 @@ public:
    *
    * 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
    */