-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Volume Mesher #369
Volume Mesher #369
Conversation
Nice, that looks like it could be very useful! Thanks for the PR! A few suggestions:
|
Hi, Just remember that a 200K elements surface mesh can easily generate a few millions elements of volumetric mesh (it an be memory pit even in Fortran codes and python can be memory hungry). I would leave it to file. If you return it and save it memory to do what? It should be export to be viewed, analysed and maybe optimized in order codes, right? |
No worries, yeah I totally get not wanting to load a 20gb tet mesh into memory. Maybe a compromise would be:
|
Hi, something like this code could be added:
but it will be ascii since it is a input file for nastran or gmsh... I do not know how to work around this... |
Cool looks good! I'll try to merge this later this week, I want to play with it a bit more. |
I am been digging a little more in gmsh api. It should be possible to save the mesh in binary format using *.msh file extension. But it not working maybe i have an old SDK... i do not know... For binary form it should be just gmsh.option.setNumber("Mesh.Binary",1) but doesn't work... The Enhancement #206 is coved by this one and many other formats... |
Hi Michael
Its a small code that generates volume mesh from a surface mesh...
This was a issue i had and looking ate forums it quite frequent....
This code needs:
pip install gmsh-sdk
or since this sdk is so small it can included inside module!
Let me know what you think...
I hope his helps...
regards