[Gmsh] Gmsh produces meshes with different number of elements

Octavio Castillo Reyes ocastilloreyes at gmail.com
Fri Aug 10 08:49:32 CEST 2018


Dear all, thank you for your support and time.

Attached to this mail you will find the .geo file. Currently, I'm working
with gmsh-3.0.6 on a Linux system (64 bits). I used the GUI to load the
.geo and build the mesh.

Best regards

O.

On Fri, Aug 10, 2018 at 5:05 AM, Felix Salazar <felix.salazar at polymtl.ca>
wrote:

> My experience with this type of issue has been that, for the same
>> architecture, with a binary compiled with the same options, the meshes are
>> repeatable. Some minor differences might occur when some options are
>> missing in the binary in another computer. And I've seen that the numbers
>> associated with extruded entities sometimes change between different
>> computers. That was actually common.
>>
>> But I think all that was before version 3.0. At the time I was generating
>> meshes in different architectures and spotting those differences in mesh
>> was easier (frequently with errors in the geometry generation). I never
>> considered it a bug. I just tried to build robust .geo files where the
>> surface/volume numbers were implicit.
>>
>> Thanks to the devs for all the improvements throughout these years!
>>
>>
>> On Aug 9, 2018 4:18 PM, "Christophe Geuzaine" <cgeuzaine at uliege.be>
>> wrote:
>>
>>
>>
>> > On 9 Aug 2018, at 21:44, Juan E. Sanchez <juan.e.sanchez at gmail.com>
>> wrote:
>> >
>> > Hello,
>> >
>> > Are you saying that gmsh generated meshes are now repeatable for the
>> same inputs?
>>
>> Yes, with the latest snapshots they should be.
>>
>>
>> > That has never been my experience in the past.
>>
>> Correct. A lot has been happening since Gmsh 3.0 :-)
>>
>>
>> >
>> > Regards,
>> >
>> > Juan
>> >
>> > On 8/9/18 11:11 AM, Jean-François Remacle wrote:
>> >> Hello
>> >> This should NOT happen. Can you send the script ?
>> >>> Le 9 août 2018 à 17:27, Octavio Castillo Reyes <
>> ocastilloreyes at gmail.com> a écrit :
>> >>>
>> >>> Dear all,
>> >>>
>> >>> First I would like to say that gmsh is a great tool and I
>> congratulate the developers.
>> >>>
>> >>> I'm working with tetrahedral meshes and I have noticed that for the
>> same script, gmsh produces different meshes, that is, the number of
>> elements or nodes is different. This is without making changes to the .geo
>> file, does anyone have any idea how to fix it?
>> >>>
>> >>> Thank you very much
>> >>>
>> >>> O.
>> >>> _______________________________________________
>> >>> gmsh mailing list
>> >>> gmsh at onelab.info
>> >>> http://onelab.info/mailman/listinfo/gmsh
>> >> _______________________________________________
>> >> gmsh mailing list
>> >> gmsh at onelab.info
>> >> http://onelab.info/mailman/listinfo/gmsh
>> >
>> >
>> > _______________________________________________
>> > gmsh mailing list
>> > gmsh at onelab.info
>> > http://onelab.info/mailman/listinfo/gmsh
>>
>>>> Prof. Christophe Geuzaine
>> University of Liege, Electrical Engineering and Computer Science
>> http://www.montefiore.ulg.ac.be/~geuzaine
>>
>> Free software: http://gmsh.info | http://getdp.info | http://onelab.info
>>
>>
>>
>> _______________________________________________
>> gmsh mailing list
>> gmsh at onelab.info
>> http://onelab.info/mailman/listinfo/gmsh
>>
>>
>>
> _______________________________________________
> gmsh mailing list
> gmsh at onelab.info
> http://onelab.info/mailman/listinfo/gmsh
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://onelab.info/pipermail/gmsh/attachments/20180810/b07b805a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PREPROCESSING.geo
Type: application/octet-stream
Size: 3597 bytes
Desc: not available
URL: <http://onelab.info/pipermail/gmsh/attachments/20180810/b07b805a/attachment-0001.geo>


More information about the gmsh mailing list