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
9002c0e7
Commit
9002c0e7
authored
23 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
*** empty log message ***
parent
b4d53955
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/FAQ
+18
-1
18 additions, 1 deletion
doc/FAQ
with
18 additions
and
1 deletion
doc/FAQ
+
18
−
1
View file @
9002c0e7
GMSH FREQUENTLY ASKED QUESTIONS ($Date: 2001-0
9
-0
5
1
9:14:05
$)
GMSH FREQUENTLY ASKED QUESTIONS ($Date: 2001-
1
0-0
6
1
6:32:40
$)
1. GENERAL
1. GENERAL
==========
==========
...
@@ -65,6 +65,23 @@ Disable opaque move in your window manager.
...
@@ -65,6 +65,23 @@ Disable opaque move in your window manager.
Not yet.
Not yet.
4.2) Gmsh is very slow when I use many transformations (Translate,
Rotate, Symmetry, Extrude, etc. ). What's wrong?
The default behavior of Gmsh is to check and suppress all duplicate
entities (points, lines and surfaces) each time a transformation
command is issued. This can slow down things a lot if many
transformations are performed. There are two solutions to this
problem:
- you may save the flattened geometry in another file (e.g. with
gmsh file.geo -0 > flat.geo), and use this new file for subsequent
computations;
- you may set the 'Geometry.AutoCoherence' option to 0. This will
prevent any automatic duplicate check/replacement. If you still
need to remove the duplicates entities, simply add 'Coherence;' at
strategic locations in your geo files (e.g. before the creation of
line loops, etc.).
5. MESH PROBLEMS
5. MESH PROBLEMS
================
================
...
...
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