what would the resulting "script.geo" be?
On Wed, 2018-03-07 at 19:41 +0100, Octavio Castillo Reyes wrote: > Dear gmsh users and support team, > > I'm working on meshing for geophysical applications using gmsh. I have > special interest in tetrahedral meshes. Since last November I'm trying to > build "scripts.geo" in an automatic way, namely, given basic information like > coordinates of the origin, model dimensions, material interfaces, write the > resulting "script.geo". > > The aim of this effort is reduce the user intervention in mechanical tasks as: > > 1. Declaration of spatial points, lines, line loops, surfaces, surface loops, > volumes. > 2. Inclusion of stl surfaces > > For this purpose, I assuming that all surfaces are perfectly matching and > there are no overlapping between them. For the sake of clarity, I attached > the simplest case of my models. > > Do you have some ideas to deal with this issue? Can you give me some tips? > > Thank you in advance for your time and support. > > O. > > > _______________________________________________ > gmsh mailing list > [email protected] > http://onelab.info/mailman/listinfo/gmsh >
_______________________________________________ gmsh mailing list [email protected] http://onelab.info/mailman/listinfo/gmsh
