Gmsh is crashing after change Extrude value from 10 to 100

  • Thread starter Thread starter Motox1982
  • Start date Start date
  • Tags Tags
    Mesh
Click For Summary
SUMMARY

The discussion centers on a GMSH crashing issue when changing the Extrude value from 10 to 100 in a geo script. The problem was traced back to the definition of Line(4), which incorrectly referenced the same point number as Line(7) and Line(8). This redundancy caused GMSH to crash instead of providing an error message. After correcting the line definitions, the script executed successfully without further issues.

PREREQUISITES
  • Familiarity with GMSH scripting and geometry definitions
  • Understanding of 3D mesh generation concepts
  • Knowledge of point and line definitions in GMSH
  • Basic troubleshooting skills in computational geometry software
NEXT STEPS
  • Review GMSH documentation on geometry scripting
  • Learn about error handling and debugging in GMSH
  • Explore best practices for defining points and lines in GMSH
  • Investigate mesh generation techniques and their impact on performance
USEFUL FOR

GMSH users, computational geometry enthusiasts, and developers working on mesh generation and optimization in engineering applications.

Motox1982
Messages
3
Reaction score
1
Hello,

here is my geo script of gmsh: (windows10 64bit)
Code:
Point(1) = {0,-35,20};
Point(2) = {0,-35,-10};
Line(1) = {1, 2};
Point(3) = {0,35,-10};
Line(2) = {2, 3};
Point(4) = {0,35,20};
Line(3) = {3, 4};
Line(4) = {4, 4};
Point(5) = {0,0,0};
Line(5) = {4, 5};
Line(6) = {5, 1};
Line(7) = {1, 1};
Line(8) = {1, 1};
Curve Loop(1) = {1,2,3,4,5,6,7,8};
Plane Surface(1) = {1};
Extrude {10, 0, 0} { Surface{1};  }
ReverseMesh Surface{1};
Mesh 2;
it works fine!

but if i change the line to: Extrude {100, 0, 0} { Surface{1}; }

(only changing value 10 to 100)

gmsh is crashing!
what is the problem, anyone any ideas?

regards, mario
 
Last edited by a moderator:
Technology news on Phys.org
omg, already fixed!

Line(4) = {4, 4}; and some stuff, it was a long day ;-)
 
Welcome to PF. :smile:

Motox1982 said:
omg, already fixed!

Line(4) = {4, 4}; and some stuff, it was a long day ;-)
Can you post your updated script so we can see what-all you changed to eliminate the errors? Was it just the definition of Line(4) that was the problem? And why did it work like that with the coarser mesh for Extrude?

Thanks.
 
The Problem was the Line which have the same Point Numbers such as:
Line(4) = {4, 4};
Line(7) = {1, 1};
Line(8) = {1, 1};

It was auto generated by my tool which uses gmsh, i though it was a gmsh error, but it was mine, everything works fine now!
 
  • Informative
Likes   Reactions: berkeman
Still, the program should return an error instead of crashing. But man does it crashes quite often!
 

Similar threads

  • · Replies 4 ·
Replies
4
Views
2K
  • · Replies 12 ·
Replies
12
Views
2K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 17 ·
Replies
17
Views
2K
  • · Replies 1 ·
Replies
1
Views
4K
Replies
1
Views
3K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 1 ·
Replies
1
Views
1K
  • · Replies 1 ·
Replies
1
Views
2K
Replies
9
Views
3K