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
bab4617e
Commit
bab4617e
authored
12 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
explain impact of non-continuous node/element tags
parent
02c91c3e
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
+10
-0
10 additions, 0 deletions
doc/texinfo/gmsh.texi
with
10 additions
and
0 deletions
doc/texinfo/gmsh.texi
+
10
−
0
View file @
bab4617e
...
@@ -3249,6 +3249,16 @@ before the @code{$Elements} section. Currently only one @code{$Nodes}
...
@@ -3249,6 +3249,16 @@ before the @code{$Elements} section. Currently only one @code{$Nodes}
and one @code
{$
Elements
}
section are allowed per file.
(
This might
/
will
and one @code
{$
Elements
}
section are allowed per file.
(
This might
/
will
change in the future.
)
change in the future.
)
Important note about efficiency. Node and element tags can be "sparse",
i.e., do not have to constitute a continuous list of indexes starting at
1
. However, using non
-
continuous tags will lead to performance
degradation. For meshes, non
-
continuous indexing forces Gmsh to use a
map instead of a vector to access nodes and elements. The performance
hit is on speed. For post
-
processing datasets, which always use vectors
to access data, the performance hit is on memory. A @code
{
NodeData
}
with
two nodes, tagged
1
and
1000000
, will allocate a
(
mostly empty
)
vector
of
1000001
elements.
Any section with an unrecognized header is simply ignored: you can thus
Any section with an unrecognized header is simply ignored: you can thus
add comments in a @file
{
.msh
}
file by putting them e.g. inside a
add comments in a @file
{
.msh
}
file by putting them e.g. inside a
@code
{$
Comments
}
/@code
{$
EndComments
}
section.
@code
{$
Comments
}
/@code
{$
EndComments
}
section.
...
...
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