[Gmsh] Gmsh Issue for constraint volume meshing

[Sanghavi, Chaitanya]

Dear Sir,

Good morning,

I would like to generate a 3D mesh for a cube from a predefined 2D surface mesh on one of the faces of the 3D cube.

This is very similar to the post below, and I was made aware that this functionality is included in the latest Gmsh version.

Link : http://onelab.info/pipermail/gmsh/2006/001866.html

I tried this methodology, without much success.

The process I try:


  1.  Create a Duct.geo file which meshes a unit sized cube 1x1x1 [m] and produces mesh.msh file.

[cid:image002.jpg at 01D58283.6AFB2BF0]


  1.  Create a surface mesh which contains the nodes, elements, physical surfaces.  (duct_interface.msh)



  1.  Merge the .msh file into the another geo file, Liner.geo. Importing this file in the latest version of Gmsh results in some errors, LinerLog. These errors or bugs are due to lack of default options specification in the geo file. However I see the mesh imported on the surface.

[cid:image008.jpg at 01D58283.6AFB2BF0]

  1.  Generate a surface mesh with the above file. This produces a surface mesh without any issues and warnings and also avoids meshing on the pre-defined discrete surface mesh.

[cid:image009.jpg at 01D58283.6AFB2BF0]



  1.  Meshing in produces errors saying the element facet intersect.  (Refer ErrorBug file)


I have one question regarding this:


  1.  Is there a way to use the nodes defined in the duct_interface.msh to define the line  and surface loops for the second geometry ?

I can see the nodes duplicated in the surface mesh.



Could this be the reason to not produce the volume mesh in the second cube ?




I would like to thank and appreciate your efforts for the help provided.


Regards
Chaitanya




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 13213 bytes
Desc: image002.jpg
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 8033 bytes
Desc: image008.jpg
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.jpg
Type: image/jpeg
Size: 18749 bytes
Desc: image009.jpg
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mesh.msh
Type: application/octet-stream
Size: 45544 bytes
Desc: mesh.msh
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0002.msh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: duct_interface.msh
Type: application/octet-stream
Size: 3931 bytes
Desc: duct_interface.msh
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0003.msh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Liner.geo
Type: application/octet-stream
Size: 2401 bytes
Desc: Liner.geo
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0001.geo>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LinerLog
Type: application/octet-stream
Size: 3826 bytes
Desc: LinerLog
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ErrorBug
Type: application/octet-stream
Size: 1848 bytes
Desc: ErrorBug
URL: <http://onelab.info/pipermail/gmsh/attachments/20191014/c0221b8d/attachment-0003.obj>