CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Meshing & Mesh Conversion

[snappyHexMesh] Background Mesh in snappy with multi domain (CHT)

Register Blogs Community New Posts Updated Threads Search

Like Tree18Likes

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   May 22, 2013, 19:04
Default
  #21
New Member
 
Jackie Chou
Join Date: Mar 2013
Posts: 12
Rep Power: 13
jackeyhust is on a distinguished road
To post #16

Hello, Bruno,

as you said, after successful snappyhexmesh, I used surfaceToPatch to get the boundary. However, some of boundaries still have "nFaces 0", I change the tolerence from 1e-8 to 1e-5, a few faces still have "nFaces 0". Normally, boundary faces "nFaces number" will increase as the tolerence increases. Will this increase have impact on the final calculation? Some boundary faces have very low "nFaces number". I am not sure how high for this "nFaces number" is a suitable choice for the final calculation.

Do you have any experience and suggestions for this problem?

Thank you for your replies!

with best regards, good night!


Jackie
jackeyhust is offline   Reply With Quote

Old   May 22, 2013, 19:48
Default
  #22
Retired Super Moderator
 
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,982
Blog Entries: 45
Rep Power: 128
wyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to allwyldckat is a name known to all
Hi Jackie,

My guess is that the surface is inside the mesh, which leads to it not being associated to existing boundary faces... because inside the mesh there are no boundary faces.

If I remember correctly, you're trying to re-assign patch names back to the interfaces between regions. Have you split the mesh into the separate regions?

Best regards,
Bruno
__________________
wyldckat is offline   Reply With Quote

Old   May 23, 2013, 03:05
Default
  #23
New Member
 
Jackie Chou
Join Date: Mar 2013
Posts: 12
Rep Power: 13
jackeyhust is on a distinguished road
Quote:
Originally Posted by wyldckat View Post
Hi Jackie,

My guess is that the surface is inside the mesh, which leads to it not being associated to existing boundary faces... because inside the mesh there are no boundary faces.

If I remember correctly, you're trying to re-assign patch names back to the interfaces between regions. Have you split the mesh into the separate regions?

Best regards,
Bruno
Hi, Bruno,

Thank you for the quick reply.You remember correctly. I have got the internal mesh and they are several regions, but i do not split them, I am going to re-assign patch names only for the outlets, like inlet and then outlet. It is just a box, flow in and then another outlet out. Because of some porous zones inside of the box, I have to make them several regions. But I do not split them up.

Actually, I tried to get back the internal boundary, some of them succeeds. If I only do for outlets and inlet, it is also not totally getting back the boundary .
do you think I should increase the tolerance ? Or must I split them up firstly?

Another strange thing is that when I finish snappyhexmesh and then
Use setSet to keep the needed regions, namely, delete the block. I get most of the needed mesh , but there is a small part which does not belong to my model. It is also not connected to my model. Do you know where it could come from? How can I avoid this part?

Thanks again! Look forward to your reply.

Morning!

Jackie
jackeyhust is offline   Reply With Quote

Old   June 17, 2016, 11:28
Default
  #24
Senior Member
 
Derek Mitchell
Join Date: Mar 2014
Location: UK, Reading
Posts: 172
Rep Power: 13
derekm is on a distinguished road
Here is a solution that removes the region and moves exposed cells to an existing patch e.g. myexistingpatch

use topoSetDict to select the wanted cellsets of the wanted regions in to a single cellset e.g. mywantedregionscellset and use
Code:
topoSet
subsetMesh -patch myexistingpatch  mywantedregionscellset -overwrite
splitMeshRegions -cellZones -overwrite
here is an example case where I took the tutorial snappyMultiRegionSimpleHeater
and then removed the region bottomAir and moved all the exposed internal faces to patch minY using the above technique. tested in OF3.0+.


Attached Files
File Type: zip snappyMultiRegionSimpleHeaterRemovingBottomAir.zip (86.2 KB, 30 views)
salad likes this.
__________________
A CHEERING BAND OF FRIENDLY ELVES CARRY THE CONQUERING ADVENTURER OFF INTO THE SUNSET

Last edited by derekm; June 17, 2016 at 16:20.
derekm is offline   Reply With Quote

Old   January 29, 2017, 07:36
Default
  #25
New Member
 
Smrutimaya Pattanaik
Join Date: May 2016
Location: Chennai, India
Posts: 11
Rep Power: 0
smrutimaya is on a distinguished road
Thank you very much, Bruno. It was very useful to me.
smrutimaya is offline   Reply With Quote

Old   November 5, 2020, 08:29
Default
  #26
Member
 
Bineet Mehra
Join Date: Aug 2013
Posts: 61
Rep Power: 13
bineet_aero is on a distinguished road
Quote:
Originally Posted by wyldckat View Post
Greetings Antonello,

Attached is your case fixed to eliminate the "domain0" zone. I had to look into the tutorial case and noticed that the "snappyMultiRegionHeater" case has a tight wrap of the "blockMeshDict" over the STL files, which explains why you were having this problem with "domain0".
I've used OpenFOAM 2.1.x, but I think the changes I've made should work in 1.7.1 as well.

Basically, the fixes were:
  • Had to fix several files in "0" where "MaxX" was defined as "nonuniform" and defined it as "uniform".
  • Had to add two options to "snappyHexMeshDict" for working in OpenFOAM 2.1.x.
  • Used setSet to define a cell set that only included the desired mesh zones:
    Code:
    setSet -batch batch.setSet
    Where "batch.setSet" has this inside:
    Code:
    cellSet isolation new zoneToCell SOLIDO
    cellSet isolation add zoneToCell FLUIDO
    cellSet isolation subset
  • Then write only this cellSet has the whole mesh
    Code:
    subsetMesh -overwrite isolation
  • Then it's business as usual with splitMeshRegions.
Best regards,
Bruno

Hii great solution !!! I tried for a similar conjugate heat transfer problem of mine but it did not work as for me the fluid domain encapsulates multiple solid components !!! Thanks anyways
bineet_aero is offline   Reply With Quote

Reply


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 Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
sliding mesh problem in CFX Saima CFX 46 September 11, 2021 08:38
how to set periodic boundary conditions Ganesh FLUENT 15 November 18, 2020 07:09
[snappyHexMesh] SnappyHexMesh for internal Flow vishwa OpenFOAM Meshing & Mesh Conversion 24 June 27, 2016 09:54
[Gmsh] STL on Gmsh + Mesh on Snappy adrieno OpenFOAM Meshing & Mesh Conversion 3 May 20, 2016 13:22
injection problem Mark New FLUENT 0 August 4, 2013 02:30


All times are GMT -4. The time now is 15:40.