[Gmsh] EssaiGmsh_v1.java:775: error: method add_physical in class WrapGmsh cannot be applied to given types;

Hi everyone, When compiling the nightly sources from Gmsh, I'm getting ``` «PKGBUILDDIR»/wrappers/java/WrappingJava/src/main/java/com/artenum/sample/EssaiGmsh_v1.java:775: error: method add_physical in class WrapGmsh cannot be applied to given types; WrapGmsh.add_physical(str, lst1, m.get

Re: [Gmsh] EssaiGmsh_v1.java:775: error: method add_physical in class WrapGmsh cannot be applied to given types;

pr 28, 2016 at 9:48 PM, Christophe Geuzaine wrote: > >> On 28 Apr 2016, at 19:36, Nico Schlömer wrote: >> >> Hi everyone, >> >> When compiling the nightly sources from Gmsh, I'm getting >> ``` >> «PKGBUILDDIR»/wrappers/java/WrappingJava/src/

[Gmsh] mesh I/O in memory?

Hi everyone, As the author of pygmsh [1] I sometimes get user complaints about how slow mesh generation is. The way pygmsh works is that it generates a geo-file in memory, writes that out, has gmsh run over it to generate a msh-file, then read in and parse that file to generate the nodes and cells

Re: [Gmsh] mesh I/O in memory?

gt; Regards, > > Dave > > -- > David Colignon, Ph.D. > 1er Logisticien de Recherche > Université de Liège > ACE - Applied & Computational Electromagnetics > Quartier POLYTECH 1 - Montefiore B28 > Allée de la découverte 10 > 4000 Liège - BELGIQUE > Tél: +32 (0

[Gmsh] mesh smoothing, voropy

Hi everyone, I spent some time getting a Lloyd-type smoother for 2D meshes to work, it's now part of voropy [1]. You can check out some video footage [2] and try it out yourself: ``` $ pip install voropy $ mesh_smoothing your.msh out.msh -t 1.0e-3 -v ``` It's substantially faster than Gmsh's smoot

[Gmsh] Lloyd smoothing broken?

Hi everyone, When using `-optimize_lloyd`, I noticed that gmsh doesn't produce centroidal tesselations but for some reason favors right angles. For the simple circle geometry ``` // Points p1 = newp; Point(p1) = {0, 0, 0, 0.1}; p2 = newp; Point(p2) = {1, 0, 0, 0.1}; p3 = newp; Point(p3) = {0, 1, 0

[Gmsh] interleaving refinement and optimization?

Hi everyone, I'm reading [1] that mesh quality may increase significantly if refinement steps are interleaved with mesh optimization (e.g., Lloyd in the case of [1]). Is a similar mechanism possible with gmsh? Cheers, Nico [1] ftp://ftp-sop.inria.fr/geometrica/alliez/imr16-meshing.pdf __

Re: [Gmsh] Lloyd smoothing broken?

> context. > > Christophe > > > On 8 Mar 2017, at 09:46, Nico Schlömer wrote: > > > > Hi everyone, > > > > When using `-optimize_lloyd`, I noticed that gmsh doesn't produce > centroidal tesselations but for some reason favors right angles. For the

[Gmsh] extrude surface with hole

Hi everyone, I noticed that when extruding surfaces with holes, the surface at the end of the extrusion will plug the hole. How to avoid that? Example attached. Cheers, Nico swh.geo Description: Binary data ___ gmsh mailing list gmsh@onelab.info http

[Gmsh] notes on the file format

Hi everyone, Since I've come to tinker with Gmsh once again lately, I've had to deal with the shortcomings of the format as well. I've found the format hard to work with for one particular reason: The element table has no fixed size element types are mixed and tags are provided with the element. A

Re: [Gmsh] Python wrapper in gmsh

Hi Andreas, pygmsh [1], a small Python wrapper of Gmsh that I wrote a while ago, might be useful to you. Cheers, Nico [1] https://github.com/nschloe/pygmsh On Wed, Mar 15, 2017 at 9:37 PM wrote: > Hello, > > > > I’ve tried to build Gmsh from the source code with Cmake and the Microsoft > Vi

Re: [Gmsh] Switch to Git

This is great news! The GitHub clone [1] works again as well for anyone who needs HTTPS access. Cheers, Nico [1] https://github.com/live-clones/gmsh On Fri, Mar 24, 2017 at 6:56 AM Christophe Geuzaine wrote: > > Dear all, > > Gmsh development has moved to Git: http://gitlab.onelab.info/gmsh/

Re: [Gmsh] Swiss cheese with filled cavities

Incidentally, swiss cheese is one of the examples for pygmsh [1]. It produces the geo-file, too. Cheers, Nico [1] https://github.com/nschloe/pygmsh/blob/master/test/examples/swiss_cheese.py On Fri, Mar 31, 2017 at 12:54 AM Achille Pluplu wrote: > Dear all, > > I'm quite new to GMSH so, please,

[Gmsh] gmsh versioning scheme

Hi everyone, A few quick questions on Gmsh's versioning scheme: * When do you bump the major version? * When do you bump the minor version? * Is API change reflected by version bumps? Cheers, Nico ___ gmsh mailing list gmsh@onelab.info http://onelab

Re: [Gmsh] gmsh versioning scheme

Thanks Christophe, this info will help me getting the version numbers and file names for Debian straight. Cheers, Nico On Wed, Sep 27, 2017 at 12:09 PM Christophe Geuzaine wrote: > > > > On 26 Sep 2017, at 15:24, Nico Schlömer > wrote: > > > > Hi everyone, >

[Gmsh] extrude OpenCASCADE Boolean union doesn't work

Hi everyone, The following code forms a union of a rectangle and two disks, and aims to extrude the resulting shape. ``` SetFactory("OpenCASCADE"); Mesh.CharacteristicLengthMin = 0.1; Mesh.CharacteristicLengthMax = 0.1; s0 = news; Rectangle(s0) = {-1.0, -1.0, 0.0, 2.0, 2.0}; s1 = news; Disk(s1)

Re: [Gmsh] extrude OpenCASCADE Boolean union doesn't work

> ex1[] = Extrude{0,0,1}{Surface{bo1()};}; As a general rule, do OpenCASCADE entities always only work with round brackets? Cheers, Nico On Wed, Sep 27, 2017 at 2:07 PM Christophe Geuzaine wrote: > > > > On 27 Sep 2017, at 14:03, Nico Schlömer > wrote: > > >

Re: [Gmsh] gmsh versioning scheme

m (or if they work at all). I'll forward your recommendation. Cheers, Nico On Wed, Sep 27, 2017 at 12:18 PM Christophe Geuzaine wrote: > > > > On 27 Sep 2017, at 12:11, Nico Schlömer > wrote: > > > > Thanks Christophe, this info will help me getting the version

Re: [Gmsh] extrude OpenCASCADE Boolean union doesn't work

> > > > On 27 Sep 2017, at 14:09, Nico Schlömer > wrote: > > > > > ex1[] = Extrude{0,0,1}{Surface{bo1()};}; > > > > As a general rule, do OpenCASCADE entities always only work with round > brackets? > > > > No, it's just that "bo1(

[Gmsh] pygmsh 4.0

Hi everyone, I've just released pygmsh 4.0 [1], a Python frontend for Gmsh. The major enhancement this time is support for Gmsh 3.0's OpenCASCADE capabilties. Install or upgrade with ``` pip install -U pygmsh ``` I'll be happy about feedback of any kind. Cheers, Nico [1] https://github.com/nsch

[Gmsh] opencascade: union, disregard seams

Hi everyone, When combining two domains using an opencascade union, the seams will still be respected by the mesher. As an example, check out the geometry of a union of two overlapping circles: ``` SetFactory("OpenCASCADE"); s0 = news; Disk(s0) = {-5.0, 0.0, 0.0, 10.0}; s1 = news; Disk(s1) = {5.0,

Re: [Gmsh] opencascade: union, disregard seams

py), which you might find useful. Very interesting! I might switch pygmsh's backend to it once this is more mature. Cheers, Nico [1] https://github.com/nschloe/pygmsh On Fri, Dec 8, 2017 at 8:58 PM Christophe Geuzaine wrote: > > > > On 8 Dec 2017, at 16:24, Nico Schlö