|
[Sponsors] |
[snappyHexMesh] Snapping problem, non orthogonal faces |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
April 9, 2015, 06:21 |
Snapping problem, non orthogonal faces
|
#1 |
New Member
Francesco
Join Date: Jul 2014
Posts: 26
Rep Power: 12 |
Hi,
i have some very annoyng problem with SHM. I have to mesh a semi-elliptic body, created with solidWorks. The stl have a veri hig resolution, is binary and the surfaceCheck utility said that everything it's ok. When i snap (OF 2.2.0) the meshquality can't reduce the number of non orthogonal faces and the resulting mesh is very very rough, like a rasp... The SHMdict Code:
/*--------------------------------*- C++ -*----------------------------------*\ | ========= | | | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox | | \\ / O peration | Version: 2.3.0 | | \\ / A nd | Web: www.OpenFOAM.org | | \\/ M anipulation | | \*---------------------------------------------------------------------------*/ FoamFile { version 2.0; format ascii; class dictionary; object snappyHexMeshDict; } // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // // Which of the steps to run castellatedMesh true; snap true; addLayers false; // Geometry. Definition of all surfaces. All surfaces are of class // searchableSurface. // Surfaces are used // - to specify refinement for any mesh cell intersecting it // - to specify refinement for any mesh cell inside/outside/near // - to 'snap' the mesh boundary to the surface geometry { Geometry.stl { type triSurfaceMesh; name Geometry; } refinementBox { type searchableCylinder; point1 (-2 0 0); point2 ( 8.0 0 0); radius 1.25; } }; // Settings for the castellatedMesh generation. castellatedMeshControls { // Refinement parameters // ~~~~~~~~~~~~~~~~~~~~~ // If local number of cells is >= maxLocalCells on any processor // switches from from refinement followed by balancing // (current method) to (weighted) balancing before refinement. maxLocalCells 200000; // Overall cell limit (approximately). Refinement will stop immediately // upon reaching this number so a refinement level might not complete. // Note that this is the number of cells before removing the part which // is not 'visible' from the keepPoint. The final number of cells might // actually be a lot less. maxGlobalCells 16000000; // The surface refinement loop might spend lots of iterations refining just a // few cells. This setting will cause refinement to stop if <= minimumRefine // are selected for refinement. Note: it will at least do one iteration // (unless the number of cells to refine is 0) minRefinementCells 5; // Allow a certain level of imbalance during refining // (since balancing is quite expensive) // Expressed as fraction of perfect balance (= overall number of cells / // nProcs). 0=balance always. maxLoadUnbalance 0.10; // Number of buffer layers between different levels. // 1 means normal 2:1 refinement restriction, larger means slower // refinement. nCellsBetweenLevels 1; // Explicit feature edge refinement // ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // Specifies a level for any cell intersected by its edges. // This is a featureEdgeMesh, read from constant/triSurface for now. features ( { file "Geometry.eMesh"; level 0; } ); // Surface based refinement // ~~~~~~~~~~~~~~~~~~~~~~~~ // Specifies two levels for every surface. The first is the minimum level, // every cell intersecting a surface gets refined up to the minimum level. // The second level is the maximum level. Cells that 'see' multiple // intersections where the intersections make an // angle > resolveFeatureAngle get refined up to the maximum level. refinementSurfaces { Geometry { // Surface-wise min and max refinement level level (5 8); // Optional specification of patch type (default is wall). No // constraint types (cyclic, symmetry) etc. are allowed. patchInfo { type wall; inGroups (GeometryGroup); } } } // Resolve sharp angles resolveFeatureAngle 60; // Region-wise refinement // ~~~~~~~~~~~~~~~~~~~~~~ // Specifies refinement level for cells in relation to a surface. One of // three modes // - distance. 'levels' specifies per distance to the surface the // wanted refinement level. The distances need to be specified in // descending order. // - inside. 'levels' is only one entry and only the level is used. All // cells inside the surface get refined up to the level. The surface // needs to be closed for this to be possible. // - outside. Same but cells outside. refinementRegions { refinementBox { mode inside; levels ((1E15 4)); } } // Mesh selection // ~~~~~~~~~~~~~~ // After refinement patches get added for all refinementSurfaces and // all cells intersecting the surfaces get put into these patches. The // section reachable from the locationInMesh is kept. // NOTE: This point should never be on a face, always inside a cell, even // after refinement. locationInMesh (3.0001 3.0001 0.43); // Whether any faceZones (as specified in the refinementSurfaces) // are only on the boundary of corresponding cellZones or also allow // free-standing zone faces. Not used if there are no faceZones. allowFreeStandingZoneFaces true; } // Settings for the snapping. snapControls { //- Number of patch smoothing iterations before finding correspondence // to surface nSmoothPatch 4; //- Relative distance for points to be attracted by surface feature point // or edge. True distance is this factor times local // maximum edge length. tolerance 0.50; //- Number of mesh displacement relaxation iterations. nSolveIter 30; //- Maximum number of snapping relaxation iterations. Should stop // before upon reaching a correct mesh. nRelaxIter 50; // Feature snapping //- Number of feature edge snapping iterations. // Leave out altogether to disable. nFeatureSnapIter 15; //- Detect (geometric only) features by sampling the surface // (default=false). implicitFeatureSnap false; //- Use castellatedMeshControls::features (default = true) explicitFeatureSnap true; //- Detect points on multiple surfaces (only for explicitFeatureSnap) multiRegionFeatureSnap false; } // Settings for the layer addition. addLayersControls { // Are the thickness parameters below relative to the undistorted // size of the refined cell outside layer (true) or absolute sizes (false). relativeSizes true; // Per final patch (so not geometry!) the layer information layers { GeometryGroup { nSurfaceLayers 1; } } // Expansion factor for layer mesh expansionRatio 1.0; // Wanted thickness of final added cell layer. If multiple layers // is the // thickness of the layer furthest away from the wall. // Relative to undistorted size of cell outside layer. // is the thickness of the layer furthest away from the wall. // See relativeSizes parameter. finalLayerThickness 0.3; // Minimum thickness of cell layer. If for any reason layer // cannot be above minThickness do not add layer. // Relative to undistorted size of cell outside layer. minThickness 0.1; // If points get not extruded do nGrow layers of connected faces that are // also not grown. This helps convergence of the layer addition process // close to features. // Note: changed(corrected) w.r.t 17x! (didn't do anything in 17x) nGrow 0; // Advanced settings // When not to extrude surface. 0 is flat surface, 90 is when two faces // are perpendicular featureAngle 60; // At non-patched sides allow mesh to slip if extrusion direction makes // angle larger than slipFeatureAngle. slipFeatureAngle 30; // Maximum number of snapping relaxation iterations. Should stop // before upon reaching a correct mesh. nRelaxIter 3; // Number of smoothing iterations of surface normals nSmoothSurfaceNormals 1; // Number of smoothing iterations of interior mesh movement direction nSmoothNormals 3; // Smooth layer thickness over surface patches nSmoothThickness 10; // Stop layer growth on highly warped cells maxFaceThicknessRatio 0.5; // Reduce layer growth where ratio thickness to medial // distance is large maxThicknessToMedialRatio 0.3; // Angle used to pick up medial axis points // Note: changed(corrected) w.r.t 17x! 90 degrees corresponds to 130 in 17x. minMedianAxisAngle 90; // Create buffer region for new layer terminations nBufferCellsNoExtrude 0; // Overall max number of layer addition iterations. The mesher will exit // if it reaches this number of iterations; possibly with an illegal // mesh. nLayerIter 50; } // Generic mesh quality settings. At any undoable phase these determine // where to undo. meshQualityControls { #include "meshQualityDict" // Advanced //- Number of error distribution iterations nSmoothScale 6; //- amount to scale back displacement at error points errorReduction 0.1; } // Advanced // Write flags writeFlags ( layerFields // write volScalarField for layer coverage ); // Merge tolerance. Is fraction of overall bounding box of initial mesh. // Note: the write tolerance needs to be higher than this. mergeTolerance 1e-6; // ************************************************************************* // I have tried to reduce and increase the relative tollerance, the nSnapIter, the mesh stl quality, the refinment level.. but the problem is always present... |
|
April 14, 2015, 04:42 |
|
#2 |
Senior Member
|
Maybe you should spend some more work on your background mesh? Are the cells in the vicinity of the geometry surface cubic? If not, this is most likely the reason for your bad mesh quality.
__________________
Blog: sourceflux.de/blog "The OpenFOAM Technology Primer": sourceflux.de/book Twitter: @sourceflux_de Interested in courses on OpenFOAM? |
|
April 14, 2015, 07:51 |
|
#3 |
New Member
Francesco
Join Date: Jul 2014
Posts: 26
Rep Power: 12 |
No, i see that the cell is not cubic, but i don't know why.
This is the blockMesh dict Code:
/*--------------------------------*- C++ -*----------------------------------*\ | ========= | | | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox | | \\ / O peration | Version: 2.3.0 | | \\ / A nd | Web: www.OpenFOAM.org | | \\/ M anipulation | | \*---------------------------------------------------------------------------*/ FoamFile { version 2.0; format ascii; class dictionary; object blockMeshDict; } // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // convertToMeters 1; vertices ( (-10 10 -10) (-10 -10 -10) (30 -10 -10) (30 10 -10) (-10 10 10) (-10 -10 10) (30 -10 10) (30 10 10) ); blocks ( hex (0 1 2 3 4 5 6 7) (40 20 20) simpleGrading (1 1 1) ); edges ( ); boundary ( frontAndBack { type patch; faces ( (0 4 7 3) (2 6 5 1) ); } outlet { type patch; faces ( (3 7 6 2) ); } inlet { type patch; faces ( (1 5 4 0) ); } lowerWall { type patch; faces ( (0 3 2 1) ); } upperWall { type patch; faces ( (4 5 6 7) ); } ); // ************************************************************************* // |
|
April 15, 2015, 04:00 |
|
#4 |
Senior Member
|
You have to have cubic cells in the vicinity of the geometry, in order to get a good mesh quality after the snapping process. Read the Users Guide, it's mentioned even there .
__________________
Blog: sourceflux.de/blog "The OpenFOAM Technology Primer": sourceflux.de/book Twitter: @sourceflux_de Interested in courses on OpenFOAM? |
|
April 15, 2015, 04:39 |
|
#5 |
New Member
Francesco
Join Date: Jul 2014
Posts: 26
Rep Power: 12 |
I know that i need cubic mesh. But how can i get it? The only way i found to do that is to use a cubic domain, but is a veri high waste of memory
|
|
April 15, 2015, 05:29 |
|
#6 |
Senior Member
|
You don't have to use a cubic domain, in order to get cubic cells. A domain of 2m * 1m *1m would get cubic cells if the first direction gets twice as many cells as the other two. You can also use refineHexMesh, to refine the mesh locally or you can create a fairly sophisticated background mesh with blockMesh, where the center block has cubic cells. The surrounding blocks don't. You see, there are multiple options .
__________________
Blog: sourceflux.de/blog "The OpenFOAM Technology Primer": sourceflux.de/book Twitter: @sourceflux_de Interested in courses on OpenFOAM? |
|
April 16, 2015, 08:11 |
|
#7 |
New Member
Francesco
Join Date: Jul 2014
Posts: 26
Rep Power: 12 |
But i have a different nuber off cell in the domain, but the cell still be rectangular. Actually, i did not have a clear idea of what blockMesh did..
The domain is 30x10x10, the number of cell are 30 10 10, so i have to have cubic cell 1x1x1 meter no? But there is a lot of cell in the y directio, double than the Z, ad a very few cell in x.. |
|
April 17, 2015, 03:56 |
|
#8 |
Senior Member
|
If you have created the blockMeshDict on your own, I strongly suggest to double check it. Especially for the order of the vertices in the block definition. Make yourself familiar with the tools you use, otherwise you face a quite unpleasant time .
__________________
Blog: sourceflux.de/blog "The OpenFOAM Technology Primer": sourceflux.de/book Twitter: @sourceflux_de Interested in courses on OpenFOAM? |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Foam::error::PrintStack | almir | OpenFOAM Running, Solving & CFD | 92 | May 21, 2024 08:56 |
AMI speed performance | danny123 | OpenFOAM | 21 | October 24, 2020 05:13 |
decomposePar problem: Cell 0contains face labels out of range | vaina74 | OpenFOAM Pre-Processing | 37 | July 20, 2020 06:38 |
foam-extend_3.1 decompose and pyfoam warning | shipman | OpenFOAM | 3 | July 24, 2014 09:14 |
Problem in IMPORT of ICEM input file in FLUENT | csvirume | FLUENT | 2 | September 9, 2009 02:08 |