Skip to content
Snippets Groups Projects
Commit fa2be41c authored by Christophe Geuzaine's avatar Christophe Geuzaine
Browse files

doc

parent a5705453
No related branches found
No related tags found
No related merge requests found
...@@ -3612,9 +3612,12 @@ physical group names (@code{$PhysicalName}), the entities ...@@ -3612,9 +3612,12 @@ physical group names (@code{$PhysicalName}), the entities
elements (@code{$GhostElements}) and post-processing datasets elements (@code{$GhostElements}) and post-processing datasets
(@code{$NodeData}, @code{$ElementData}, @code{$ElementNodeData}). (@code{$NodeData}, @code{$ElementData}, @code{$ElementNodeData}).
To represent a mesh, the minimal sections that should be present in the To represent a simple mesh, the minimal sections that should be present
file are @code{$MeshFormat}, @code{$Nodes} and @code{$Elements}. Nodes in the file are @code{$MeshFormat}, @code{$Nodes} and
are assumed to be defined before elements. Sections can be repeated in @code{$Elements}. Nodes are assumed to be defined before elements. To
represent a mesh with the full topology (BRep) of the model and
associated physical groups, an @code{$Entities} section should be
present before the @code{$Nodes} section. Sections can be repeated in
the same file, and post-processing sections can be put into separate the same file, and post-processing sections can be put into separate
files (e.g. one file per time step). Any section with an unrecognized files (e.g. one file per time step). Any section with an unrecognized
header is simply ignored: you can thus add comments in a @file{.msh} header is simply ignored: you can thus add comments in a @file{.msh}
...@@ -3932,8 +3935,8 @@ $MeshFormat ...@@ -3932,8 +3935,8 @@ $MeshFormat
4.1 0 8 @emph{MSH4.1, ASCII} 4.1 0 8 @emph{MSH4.1, ASCII}
$EndMeshFormat $EndMeshFormat
$Nodes $Nodes
1 6 1 6 @emph{1 bloc, 6 nodes total, min/max node tags: 1 and 6} 1 6 1 6 @emph{1 entity bloc, 6 nodes total, min/max node tags: 1 and 6}
2 1 0 6 @emph{surface 1, no parametric coordinates, 6 nodes} 2 1 0 6 @emph{2D entity (surface) 1, no parametric coordinates, 6 nodes}
1 0. 0. 0. @emph{ node #1: coordinates (0., 0., 0.)} 1 0. 0. 0. @emph{ node #1: coordinates (0., 0., 0.)}
2 1. 0. 0. @emph{ node #2: coordinates (1., 0., 0.)} 2 1. 0. 0. @emph{ node #2: coordinates (1., 0., 0.)}
3 1. 1. 0. @emph{ etc.} 3 1. 1. 0. @emph{ etc.}
...@@ -3942,8 +3945,8 @@ $Nodes ...@@ -3942,8 +3945,8 @@ $Nodes
6 2. 1. 0. 6 2. 1. 0.
$EndNodes $EndNodes
$Elements $Elements
1 2 1 2 @emph{1 bloc, 2 elements total, min/max element tags: 1 and 2} 1 2 1 2 @emph{1 entity bloc, 2 elements total, min/max element tags: 1 and 2}
2 1 3 2 @emph{surface 1, element type 3 (4-node quad), 2 elements} 2 1 3 2 @emph{2D entity (surface) 1, element type 3 (4-node quad), 2 elements}
1 1 2 3 4 @emph{ quad #1: nodes 1 2 3 4} 1 1 2 3 4 @emph{ quad #1: nodes 1 2 3 4}
2 2 5 6 3 @emph{ quad #2: nodes 2 5 6 3} 2 2 5 6 3 @emph{ quad #2: nodes 2 5 6 3}
$EndElements $EndElements
...@@ -3969,27 +3972,28 @@ The 4.1 revision of the format includes the following modifications with ...@@ -3969,27 +3972,28 @@ The 4.1 revision of the format includes the following modifications with
respect to the initial 4.0 version: respect to the initial 4.0 version:
@itemize @bullet @itemize @bullet
@item @item
All the @code{unsigned long} entries are changed to @code{size_t}. All All the @code{unsigned long} entries have been changed to
the entries designating counts which were previsouly encoded as @code{size_t}. All the entries designating counts which were previsouly
@code{int} are also changed to @code{size_t}. (This only impacts binary encoded as @code{int} have also been changed to @code{size_t}. (This
files.) only impacts binary files.)
@item @item
The @code{$Entities} section is now optional. The @code{$Entities} section is now optional.
@item @item
The bounding box for point entities is simply replaced by the 3 The bounding box for point entities has been replaced simply by the 3
coordinates of the point (instead of the six bounding box values). coordinates of the point (instead of the six bounding box values).
@item @item
The @code{entityDim} and @code{entityTag} values are switched in the The @code{entityDim} and @code{entityTag} values have been switched in the
@code{$Nodes} and @code{$Elements} sections (for consistency with the @code{$Nodes} and @code{$Elements} sections (for consistency with the
ordering used elsewhere). ordering used elsewhere).
@item @item
The minimum and the maximum tag of nodes (resp. elements) is added in The minimum and the maximum tag of nodes (resp. elements) have been
the header of the @code{$Nodes} (resp. @code{$Elements}) section, to added in the header of the @code{$Nodes} (resp. @code{$Elements})
facilitate the detection of sparse or dense numberings when reading the section, to facilitate the detection of sparse or dense numberings when
file. reading the file.
@item @item
The @code{$Periodic} section has been changed to always provide the The @code{$Periodic} section has been changed to always provide the
number of values in the affine transform (which can be zero). number of values in the affine transform (which can be zero, if the
transform is not provided).
@end itemize @end itemize
@c ------------------------------------------------------------------------- @c -------------------------------------------------------------------------
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment