Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
gmsh
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Larry Price
gmsh
Commits
a89ed7a9
Commit
a89ed7a9
authored
21 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
removed obsolete (and wrong) description of the physical entity numbering requirements.
parent
96329139
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/texinfo/gmsh.texi
+6
-7
6 additions, 7 deletions
doc/texinfo/gmsh.texi
with
6 additions
and
7 deletions
doc/texinfo/gmsh.texi
+
6
−
7
View file @
a89ed7a9
\input
texinfo.tex @c -*-texinfo-*-
@c
$
Id: gmsh.texi,v
1
.
10
1
2004
-
0
3
-
30
18
:
17
:
11
geuzaine Exp
$
@c
$
Id: gmsh.texi,v
1
.
10
2
2004
-
0
4
-
01
22
:
21
:
26
geuzaine Exp
$
@c
@c Copyright (C) 1997-2004 C. Geuzaine, J.-F. Remacle
@c
...
...
@@ -1330,12 +1330,11 @@ Compound groups of elementary geometrical entities can also be defined and
are called ``physical'' entities. These physical entities cannot be modified
by geometry commands: their only purpose is to assemble elementary entities
into larger groups, possibly modifying their orientation, so that they can
be referred to by the mesh module as single entities. Each physical entity
is assigned a unique identification number when it is created. That is, no
two physical entities (even of different types, like a physical line and a
physical surface) can share identical identification numbers. See @ref
{
Mesh
module
}
, for more information about how physical entities affect the way
meshes are saved.
be referred to by the mesh module as single entities. As is the case with
elementary entities, each physical point, physical line, physical surface or
physical volume must be assigned a unique identification number. See
@ref
{
Mesh module
}
, for more information about how physical entities affect
the way meshes are saved.
@menu
* Geometry commands::
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment