Re: [Gmsh] Interpolating mesh values

To add on to the previous email: I figured out "2.", and I am able to use the GUI to write out a grid. My remaining questions are A :: "1" from prev. email :: what interpolation kernel/ method is gmsh using? [I wanted to use an interpolation scheme such that if I specify a point outside

Re: [Gmsh] Interpolating mesh values

This is awesome! 2 Quick questions : 1. When I use probe to get value @ a point, what interpolation kernel/ method is gmsh using? [I wanted to use an interpolation scheme such that if I specify a point outside the mesh (which can happen when I spec a regular grid), I don't want gmsh to

Re: [Gmsh] Interpolating mesh values

> On 27 Nov 2017, at 23:41, Mayank Jog wrote: > > Hello, > I've started using gmsh recently, and I wonder if there is a functionality to > interpolate data. > > I have a mesh, and a value associated with each element of the mesh (electric > potential)*. > I want to

Re: [Gmsh] Interpolating mesh values

Hi Mayank I have written that functionality into my own framework called wasora (www.seamplex.com/wasora) Say you have a .msh file with point-wise defined data as inhttps://bitbucket.org/seamplex/wasora/src/0321d32894d66056e64b2035ac98887b7aa4f29b/examples/tiny.msh?at=master=file-view-default

[Gmsh] Periodic mesh

Hello, I'm trying to build a mesh in 2D for which I need periodic boundary conditions. I'm not sure about the correctness of my *.geo script. As result, I don't understand how read the $Periodic section in the *.mesh file. Please, can you help me to understand the process? My scripts are

[Gmsh] (no subject)

issue regarding hexahedral meshing in gmsh , i did tetrahedral meshing in gmsh but i do for hexahedral meshing for cylinderical object //+ Point(1) = {2.5, 0, 0, 3}; //+ Point(2) = {5.25, 0, 0, 3}; //+ Point(3) = {8, 0, 0, 3}; //+ Line(1) = {1, 2}; //+ Line(2) = {2, 3}; //+ Extrude {0, 0, 14} {

Re: [Gmsh] BooleanFragments output identification

Dear all, I do not really understand why the BoundingBox command does not give the expected results for "complex" volumes. I developped a small workaround consisting in looping over the volume boundary faces and each time evaluating the BoundingBox of the surface. In case other might be