CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM Native Meshers: snappyHexMesh and Others

Base mesh is not removed completely

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old   June 16, 2017, 09:11
Default Base mesh is not removed completely
  #1
New Member
 
DANG
Join Date: Apr 2016
Location: Lyon 1, France
Posts: 26
Rep Power: 3
doubledang is on a distinguished road
Hi Guys,

I am trying to use snappyhexmesh utility to generate mesh for a CSTR.
I found a kind of annoying thing:
When I set base meshing below in the blockMeshdict, the snappyhexmesh utility
works well:

blocks
(
hex (0 1 2 3 4 5 6 7) ( 64 75 65) simpleGrading (1 1 1)
);


But when I wanted to increase the base mesh density like below, the snappy fails to remove the base mesh completely (see the pic in the attached case file).

blocks
(
hex (0 1 2 3 4 5 6 7) (84 95 88) simpleGrading (1 1 1)
);

I have uploaded the case file to the link:
https://www.dropbox.com/s/dxn5lhlug8go0mt/help.zip?dl=0

Hope you guys could take a look, and see if you have some tips!!

Many thanks!

Best regards,
doubledang is offline   Reply With Quote

Old   June 16, 2017, 15:12
Post
  #2
Member
 
Lasse Brams Vinther
Join Date: Oct 2015
Posts: 44
Rep Power: 4
Swagga5aur is on a distinguished road
Hello Dang,
I briefly tested your case with both blockMesh specifications and I was wondering what patch the issuing cells are stored in for for the paraview figure?

I initially assumed that they were stored in allBoundary patch, however, this patch exist for both blockMesh specifications when I run the Allrun.pre script, being inconsistent with your initial issue.

I'll look further into it in the next week as I'm quite busy the next three days.
Swagga5aur is offline   Reply With Quote

Old   June 16, 2017, 16:09
Default
  #3
New Member
 
DANG
Join Date: Apr 2016
Location: Lyon 1, France
Posts: 26
Rep Power: 3
doubledang is on a distinguished road
Hi Swagga5aur,

Thanks for your response.

I re-run it again, the problem could be reproduced.
You just need to run the Allrun.pre script, after it is done you will find the allBoundary
patch still exists in the final mesh. Normally the allBoundary patch should be gone after the final mesh is obtained.
Hope I have made my problem clear to you.

Best regards,


Quote:
Originally Posted by Swagga5aur View Post
Hello Dang,
I briefly tested your case with both blockMesh specifications and I was wondering what patch the issuing cells are stored in for for the paraview figure?

I initially assumed that they were stored in allBoundary patch, however, this patch exist for both blockMesh specifications when I run the Allrun.pre script, being inconsistent with your initial issue.

I'll look further into it in the next week as I'm quite busy the next three days.
doubledang is offline   Reply With Quote

Old   June 20, 2017, 08:02
Post
  #4
Member
 
Lasse Brams Vinther
Join Date: Oct 2015
Posts: 44
Rep Power: 4
Swagga5aur is on a distinguished road
Hello again DANG,
I just ran the two blockMeshes resulting in the following two figures with a remaining background mesh in both so I am wondering what openFOAM version you are using, I am using 4.1.

I'll try lower background mesh densities to try and pinpoint when the issue occurs.

Left figure is the blockMesh of (64 75 65) and the right is the (84 95 88).
Attached Images
File Type: jpg low.jpg (29.8 KB, 7 views)
File Type: jpg high.jpg (32.9 KB, 8 views)
Swagga5aur is offline   Reply With Quote

Old   June 20, 2017, 08:15
Default
  #5
New Member
 
DANG
Join Date: Apr 2016
Location: Lyon 1, France
Posts: 26
Rep Power: 3
doubledang is on a distinguished road
Hi Swagga5aur,

I use version 4.0, it is interesting problem, I still get no answer to this.
Let's see if you can get more information...

Best regards,



Quote:
Originally Posted by Swagga5aur View Post
Hello again DANG,
I just ran the two blockMeshes resulting in the following two figures with a remaining background mesh in both so I am wondering what openFOAM version you are using, I am using 4.1.

I'll try lower background mesh densities to try and pinpoint when the issue occurs.

Left figure is the blockMesh of (64 75 65) and the right is the (84 95 88).
doubledang is offline   Reply With Quote

Old   June 20, 2017, 10:12
Post
  #6
Member
 
Lasse Brams Vinther
Join Date: Oct 2015
Posts: 44
Rep Power: 4
Swagga5aur is on a distinguished road
Hello again,
I believe the issue lies in the stl files that you use as misalignment is observed of the surface triangulations as well as unenclosed surfaces. This is probably the cause to this unremoved backgroundmesh as the cells aren't part of the domain and can't be snapped to a nonexisting connecting surface.

This is shown in the below figure where a gap is noticed as well as misaligned vertices.

This has already been discussed how to solve in posts such as Trouble with stl file: surface not closed (snappyHexMesh)
and Creating waterproof STL using snappyHexMesh or salome

Hope its of some help, let me know if you have any questions.
Attached Images
File Type: jpg notclosedsurfaces.jpg (37.3 KB, 7 views)
Swagga5aur is offline   Reply With Quote

Old   June 21, 2017, 11:14
Default
  #7
New Member
 
DANG
Join Date: Apr 2016
Location: Lyon 1, France
Posts: 26
Rep Power: 3
doubledang is on a distinguished road
Hello Swagga5aur,


After increasing the quality of the stl file, the problem is solved.

Thank you very much for your information.

Best regards,

Quote:
Originally Posted by Swagga5aur View Post
Hello again,
I believe the issue lies in the stl files that you use as misalignment is observed of the surface triangulations as well as unenclosed surfaces. This is probably the cause to this unremoved backgroundmesh as the cells aren't part of the domain and can't be snapped to a nonexisting connecting surface.

This is shown in the below figure where a gap is noticed as well as misaligned vertices.

This has already been discussed how to solve in posts such as Trouble with stl file: surface not closed (snappyHexMesh)
and Creating waterproof STL using snappyHexMesh or salome

Hope its of some help, let me know if you have any questions.
doubledang is offline   Reply With Quote

Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[ICEM] 2D hybrid mesh (unstructured mesh highly dependent on structured mesh parameters) shubham jain ANSYS Meshing & Geometry 1 April 10, 2017 05:03
snapphexmesh with not quite orthogonal base mesh derekm OpenFOAM Native Meshers: snappyHexMesh and Others 1 January 20, 2017 02:27
Snappyhex mesh: poor inlet mesh Swagga5aur OpenFOAM Native Meshers: snappyHexMesh and Others 1 December 3, 2016 17:59
snappyHexMesh won't work - zeros everywhere! sc298 OpenFOAM Native Meshers: snappyHexMesh and Others 2 March 27, 2011 21:11
Convergence moving mesh lr103476 OpenFOAM Running, Solving & CFD 30 November 19, 2007 15:09


All times are GMT -4. The time now is 18:32.