CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM Running, Solving & CFD

Query on SnappyHexMesh

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

Reply
 
LinkBack Thread Tools Display Modes
Old   July 7, 2013, 11:59
Default Query on SnappyHexMesh
  #1
Senior Member
 
Vishal Nandigana
Join Date: Mar 2009
Location: Champaign, Illinois, U.S.A
Posts: 206
Rep Power: 9
nandiganavishal is on a distinguished road
Dear Foamers,

I have mapped and meshed a user defined structure (generated as .stl file) inside my cylindrical geometry using SnappyHexMesh. I would like to know, if OpenFOAM describes the mapped geometry only as a boundary (or patch). Is it possible to define this structure as part of the internal domain. The reason I am asking this is because I would like to solve the following equation in the entire domain (both mapped geometry and the cylindrical domain)

fvm::laplacian(eps_r(r),Phi(r)) == rho (r)

where, eps_r is 80 when r != r_map (r is the mesh point location and r_map is the mesh point of the mapped structure)
eps_r = 2 when r == r_map

rho(r) = user defined input value depending on r

Hence, I would like to know if we can define the entire system (mapped structure + cylindrical geometry) as a single domain so as to solve the problem in a single domain.

Please let me know

Thanks

Regards,
Vishal
nandiganavishal is offline   Reply With Quote

Old   July 9, 2013, 11:19
Default
  #2
Senior Member
 
Artur's Avatar
 
Artur
Join Date: May 2013
Location: Southampton, UK
Posts: 226
Rep Power: 6
Artur is on a distinguished road
I did something similar the other day to define an AMI (arbitrary mesh interface) using an .stl file of a cylinder I generated by my own script. Here are the steps I followed:

1. import the .stl in the snappyHexMeshDict as per usual:

Code:
    amiCylinder.stl
    {
        type        triSurfaceMesh;
        name        amiCylinder;
        regions
        {
            amiCylinder
            {
                name       amiCylinder;
            }
        }
    }
2. refine the edges as per usual as well:

Code:
    features
    (
        {
            file        "amiCylinder.eMesh";
            level       1;
        }
     );
3. in refinement surfaces define a cell zone inside the cylinder:

Code:
        amiCylinder
        {
            level       (4 4);
            cellZone    amiCylinder;
            faceZone    amiCylinder;
            cellZoneInside  inside;
        }
4. select the point in mesh to be OUTSIDE of the cylinder

Hopefully this will work for you too.
Artur is offline   Reply With Quote

Old   July 15, 2013, 21:11
Default
  #3
Senior Member
 
Vishal Nandigana
Join Date: Mar 2009
Location: Champaign, Illinois, U.S.A
Posts: 206
Rep Power: 9
nandiganavishal is on a distinguished road
Quote:
Originally Posted by Artur View Post
I did something similar the other day to define an AMI (arbitrary mesh interface) using an .stl file of a cylinder I generated by my own script. Here are the steps I followed:

1. import the .stl in the snappyHexMeshDict as per usual:

Code:
    amiCylinder.stl
    {
        type        triSurfaceMesh;
        name        amiCylinder;
        regions
        {
            amiCylinder
            {
                name       amiCylinder;
            }
        }
    }
2. refine the edges as per usual as well:

Code:
    features
    (
        {
            file        "amiCylinder.eMesh";
            level       1;
        }
     );
3. in refinement surfaces define a cell zone inside the cylinder:

Code:
        amiCylinder
        {
            level       (4 4);
            cellZone    amiCylinder;
            faceZone    amiCylinder;
            cellZoneInside  inside;
        }
4. select the point in mesh to be OUTSIDE of the cylinder

Hopefully this will work for you too.
Hi Arthur,

Thanks for your reply.

1. If I understand your message, the command cellzone and faceZone in the refinement surfaces when defined, would incorporate the .stl file (in your case cylinder) as part of the initial geometry defined in the blockMesh, and the combined geometry (initial geometry and .stl file) would be treated as single domain?

2. Currently, this is how my SnappyHexMesh file looks like

refinementSurfaces
{
ssdna_equilibrated_transformed_vmd_new // NOTE: SAME NAME AS THAT GIVEN IN type triSurfaceMesh
{
// Surface-wise min and max refinement level
level (4 5);
}
}

I would incorporate your suggestions and would get you posted.

Thanks

Regards,
Vishal
nandiganavishal 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
Some problems about using snappyHexMesh xiaow_g OpenFOAM Native Meshers: snappyHexMesh and Others 1 April 13, 2012 05:56
Strange Results With snappyHexMesh calebamiles OpenFOAM Running, Solving & CFD 0 August 14, 2011 16:02
stitchMesh and snappyHexMesh gdbaldw OpenFOAM 0 December 23, 2009 03:09
SnappyHexMesh query vw.cfd OpenFOAM Native Meshers: snappyHexMesh and Others 2 August 14, 2009 07:54
SnappyHexMesh not generate mesh first time mavimo OpenFOAM Mesh Utilities 4 August 26, 2008 07:08


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