|
[Sponsors] |
[snappyHexMesh] SHM for CHT: it is meshing where it shouldnt be |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
April 30, 2016, 14:54 |
SHM for CHT: it is meshing where it shouldnt be
|
#1 |
Member
Lisandro Maders
Join Date: Feb 2013
Posts: 98
Rep Power: 13 |
Hi everybody,
I am trying to make a mesh for a CHT problem. The problem is show in Figure attached, this is a cut in the symmetry plane. I want to have a fluid mesh between the internal blue surface and red one; and want to have a solid mesh between the red surface and the external blue one. What is snappyHexMesh doing for now: it is meshing everything, including the bounding box created with blockMesh; or there are cases in which it does not mesh the internal blue, which is correct, but keep meshing the bounding box; I believe it is not recognizing well the external surface. I am new in SHM so it is possible I am not using proper refine values. My big doubts are: there is only one place to set the location point of the mesh in SHMdict. I have looked at the tutorial of CHT mesh and it is placed inside any of the domains (it seems that does not matter). So I think it is possible that it will create 3 regions of mesh, and I need to delete the most internal one (inside the internal blue surface, which i do not want). Is it right? If so, how to do so.. OBS: I have followed some instructions and hints of other threads here in the forum but it did not work for me.. Regards, Lisandro Maders |
|
April 30, 2016, 15:26 |
|
#2 |
Member
Lisandro Maders
Join Date: Feb 2013
Posts: 98
Rep Power: 13 |
I will put some pictures of what it is doing and also what it should do. I did mesh the regions separately to test the parameters, so the final mesh should be a sum of the 2..
|
|
April 30, 2016, 17:21 |
Improving a bit but still needing some help with SHM
|
#3 |
Member
Lisandro Maders
Join Date: Feb 2013
Posts: 98
Rep Power: 13 |
Here is where I am at the moment..
I was able to at least have separated regions for fluid and solid zones, that is what I want. However, I still have 2 extra domains which I do not want. They can be seen in Figure "internalMesh_BlueSurface", which is the yellow region meshed, inside the internal cylinder; and in the Figure "blockMesh_boundingBoxMesh". The latter I really do not understand, why is it meshing between the blockMesh bounding box and my external surface? Any way, is it ok to delete the regions I do not want and rename the patches like fluidZone_to_domain3, for example? Regards, Lisandro Maders |
|
April 30, 2016, 20:01 |
|
#4 |
Member
Lisandro Maders
Join Date: Feb 2013
Posts: 98
Rep Power: 13 |
Trying and learning. I do not know if this is the correct way of doing so, but what worked for me was:
1. Specify the location point inside any place between any surfaces. 2. Specify locationInMesh parameter in snappyHexMeshDict for each cellZone you want (in my case, fluid and solid zones) 3. Then, it will generate 4 domains: fluid, solid (which I want), domainX (bounding box of blockMesh until external surface) and domainY (inside my internal cylinder, which I do not want a mesh). 4. Then, I did what is specified in http://www.cfd-online.com/Forums/ope...tml#post341623 , using setSet to specify the zones I want. I am not sure if this is really necessary, maybe I could jump to step 5. 5. Once in my constant/regionProperties it is said which cellZones are fluid and solid, it will only calculate such regions, so I believe the solver is blind for domainX and domainY regions.. If anyone with more experience could confirm it, it would be good. Regards, Lisandro Maders |
|
May 10, 2016, 07:15 |
Not able to use STL regions for patches
|
#5 |
Member
Lisandro Maders
Join Date: Feb 2013
Posts: 98
Rep Power: 13 |
I have a STL file with multiple regions, like:
"solid region1 ... endsolid region1 solid region2 ..... endsolid region2" But I am not being able to use them to create patches. I am specifying them as regions in snappyHexMeshDict like below. What am I doing wrong? I have attached the entire snappyHexDict file as well. Code:
raiox.stl { type triSurfaceMesh; name raiox; regions { calor_emissao { name calor_emissao; } calor_fonte { name calor_fonte; } furos { name furos; } sup_raiox { name sup_raiox; } ventilador { name ventilador; } } I think I can be setting something wrong in snappyHexMeshDict, but I do not know what it can be.. Looking forward for some answer. Cheers |
|
May 10, 2016, 12:42 |
|
#7 |
Member
Lisandro Maders
Join Date: Feb 2013
Posts: 98
Rep Power: 13 |
Yes because it is meshing properly. I have the regions now in the way I want. The only thing is bothering me is that it creates 2 extra "domain" regions. But I read in some threads here that I can just ignore because in the regionProperties file I say which are the regions I really want to make the calculations.
So, if this "issue" of creating extra domains is not really an issue, my problem now is to use the separated stl regions as boundary conditions... |
|
Tags |
cht, shm |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Meshing Process | sidharth9426 | STAR-CCM+ | 4 | September 15, 2015 04:31 |
[ICEM] Flow channel meshing problems | StefanG | ANSYS Meshing & Geometry | 19 | May 15, 2012 07:44 |
[ANSYS Meshing] Meshing strategy for External Flows | Hybrid | ANSYS Meshing & Geometry | 0 | January 24, 2012 15:27 |
Best Meshing scheme for Cylinder | Nutrex | Main CFD Forum | 4 | July 29, 2008 12:03 |
Volume Meshing & Face Meshing? singularity of grid | ken | FLUENT | 0 | September 4, 2003 12:08 |