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
GitLab community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Larry Price
gmsh
Commits
d289270f
Commit
d289270f
authored
22 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
Be more explicit about node ordering in transfinite definitions
parent
d576b3c6
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/texinfo/gmsh.texi
+13
-10
13 additions, 10 deletions
doc/texinfo/gmsh.texi
with
13 additions
and
10 deletions
doc/texinfo/gmsh.texi
+
13
−
10
View file @
d289270f
\input
texinfo.tex @c -*-texinfo-*-
@c
$
Id: gmsh.texi,v
1
.
4
5
2003
-
04
-
24
00
:
53
:
08
geuzaine Exp
$
@c
$
Id: gmsh.texi,v
1
.
4
6
2003
-
04
-
24
15
:
26
:
40
geuzaine Exp
$
@c
@c Copyright (C) 1997-2003 C. Geuzaine, J.-F. Remacle
@c
...
...
@@ -1924,18 +1924,21 @@ line. (A deprecated synonym for @code{Progression} is @code{Power}.)
@item Transfinite Surface @
{
@var
{
expression
}
@
}
= @
{
@var
{
expression-list
}
@
}
;
Selects the surface @var
{
expression
}
to be meshed with the 2D transfinite
algorithm. The @var
{
expression-list
}
should contain the identification
numbers of the points on the boundary of the surface. The ordering of these
point numbers defines the ordering and orientation of the mesh
elements. Note that a transfinite surface can only have three or four sides.
algorithm (the surface can only have three or four sides). The
@var
{
expression-list
}
should contain the identification numbers of the
points on the boundary of the surface. The ordering of these point numbers
defines the ordering and orientation of the mesh elements, and should thus
follow the node ordering for triangles or quadrangles given in @ref
{
Gmsh
node ordering
}
.
@item Transfinite Volume @
{
@var
{
expression
}
@
}
= @
{
@var
{
expression-list
}
@
}
;
Selects the volume @var
{
expression
}
to be meshed with the 3D transfinite
algorithm. The @var
{
expression-list
}
should contain the identification
numbers of the points on the boundary of the volume. The ordering of these
point numbers defines the ordering and orientation of the mesh
elements. Note that a transfinite volume can only have six or eight
faces.
algorithm (the volume can only have six or eight faces). The
@var
{
expression-list
}
should contain the identification numbers of the
points on the boundary of the volume. The ordering of these point numbers
defines the ordering and orientation of the mesh elements, and should thus
follow the node ordering for prisms or hexahedra given in @ref
{
Gmsh node
ordering
}
.
@end ftable
@c .........................................................................
...
...
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