Gmsh Download

[Demeter Exekutor]

Thisapproach is particularly useful when packages cannot be installed in separate virtual environments. For instance, Gmsh has DLLs that are not copied during package installation, and pip does not flag this as an issue.

As ignorant in this matter, what does that mean and/or what did you meant with that?

It means that gmsh cannot be integrated in rhino?

What about keeping it as an external installed library in the system but accessing it through compiled plugins for Rhino? Would that be ok?

The TriRemesh component is indeed excellent. However, what I demonstrated is more aligned with what the Remesh By Color component can achieve. TriRemesh tends to create meshes with edges of similar lengths, although @DanielPiker has mentioned plans to introduce support for variable mesh sizing.

I have many questions, but one I'm struggling with right now is how to export a mesh with a surface area labeled? I want to import the mesh into another program, but I want to be able to say "this surface is surface 1", "this surface is surface 2", etc. : (

I am making a rotor for an induction eletric machine so there is the outer circle and the iner hole where the shaft goes through. Also there is the induction rotor bars for that I made a code that generates a circular padron to automaticaly generate them but I am new to Gmsh and never handle mutiple surfaces and subdomains. They are being bunch up togheter afther the first one and if I mesh it the rotor bar geometries are being ignored the error is : Error Error Error

I tried mutiple ways do separate into surfaces and check the indices and the order for anti clock wise rotation. I don't have experience with gmsh errors. But I am glad to learn, it must have better ways to do what I have done so far. Also any sugestion into the 2D mesh genaration would be more them welcome.

usually I am creating a more or less coarse 2nd or 1st order tetmesh with refinements depending on how much interessed I am in the part results. So far I was happy with the results that netgen provided. Now in 2.0.0 version gmsh is there as an advanced mesher. Does gmsh has any advantages over netgen in terms of tetrahedral mesh? In some older forum thread multiprocesser capabilities were discussed for example.

In general, both meshers give appropriate results. Both meshers work differently regarding internal element size definitions, but I tried to generalize them so that the effect would be the same. In most of my tests, both meshers created meshes of similar sizes. But Netgen supports element size grading while Gmesh does not, so sometimes different results are created.

The problem with Gmsh is that if you use fine mesh on the curved edges, the mesh size is propagated to the surface internals. This is a setting that can be turned off but then the mesh goes from fine to coarse very quickly since no mesh grading limit can be used.

By the way, you are doing a fantastic job. I think Prepomax is even nicer to mesh than Gmsh itself.

NOTE: I would suggest not closing the messages where you post new versions. I think most of us are left wanting to congratulate you when new revisions come out.

Then when I export the mesh in gmsh-format version 2 ascii without the include all elements option and import it in Freefem++ then I get the three labels 2, 3, 4. Label 1 is assigned to channel in the msh-file.

3a8082e126