CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Post-Processing

Possible bug or limitation in stl-generated surface for sampling analysis

Register Blogs Community New Posts Updated Threads Search

 
 
LinkBack Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old   April 27, 2016, 06:26
Default Possible bug or limitation in stl-generated surface for sampling analysis
  #1
Member
 
Join Date: Jun 2015
Posts: 30
Rep Power: 10
Ali Blues is on a distinguished road
Hi,
In sampling results over surfaces, openfoam allows for using an stl-generated surface. For example in line 312 of $FOAM_UTILITIS/postProcessing/sampling/sample/sampleDict


Code:
 triSurfaceSampling   
 {     
    // Sampling on triSurface 
        type        sampledTriSurfaceMesh;      
        surface     integrationPlane.stl;       
        source      boundaryFaces;  // What to sample: cells (nearest cell)        
                           // insideCells (only triangles inside cell)   
                           // boundaryFaces (nearest boundary face)     
    interpolate true;   
  }
I'm currently working on the simulation of an impeller rotating in a cylindrical tank. Prior to applying the above method for sampling on complicated surfaces, I thought of first “validating” it by comparing the results with those obtained by using the cuttingPlane type. Since I have a cylindrical tank, the cutting plane along the cross-section, is a disk. So I made a disk in salome and exported it as stl. Here is the file for surface sampling:


Code:
surfaceSampling
{
    type            surfaces;
    functionObjectLibs ("libsampling.so");
    outputControl   outputTime;

    surfaceFormat   vtk;
    fields          (U);

    interpolationScheme cellPoint;

    
    surfaces
    (

     cuttingPlaneBase
     {
        // Cutingplane using iso surface
        type            cuttingPlane;
        planeType       pointAndNormal;
        pointAndNormalDict
        {
            basePoint       (0 0 1);
            normalVector    (0 0 1);
        }
        interpolate     true;

      }

    stlBased
        {
        
        // Sampling on triSurface
        type        sampledTriSurfaceMesh;
        surface     znormal.stl;
        source      cells;  
  
            interpolate     true;

       }


     ); 
  
 }
The results are attached.

As it can be seen the stl approach completely fails. For some reason it doesn't really cut through the cells, rather keeps the original triangles form the stl. In the sampleDict, it's mentioned that the first approach using plane or cutting plane always generates a triangulated surface as well. So now I'm a bit confused as how to deal with this. Is this a bug in the type sampledTriSurfaceMesh which doesn't perform a topoSet analysis automatically? Like creating cellSet from the stl surface? or limitation of the approach or I missed something out?



Thanks
Ali
Attached Images
File Type: png stlSurfaceSamling.png (92.1 KB, 104 views)
File Type: png cuttingPlaneSurfaceUtil.png (129.3 KB, 100 views)
Ali Blues is offline   Reply With Quote

 


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
Spillway Analysis Fixed Water Surface Boundary Condition mgdenno OpenFOAM Running, Solving & CFD 17 December 9, 2018 17:37
[swak4Foam] funkyDoCalc mass flow over stl surface? lourencosm OpenFOAM Community Contributions 0 November 28, 2014 07:50
[snappyHexMesh] Problem with Sanpper, surface still Rough Zephiro88 OpenFOAM Meshing & Mesh Conversion 7 November 5, 2014 12:05
[snappyHexMesh] Add additional boundary layers to complex stl surface tobijingles OpenFOAM Meshing & Mesh Conversion 1 October 26, 2011 10:45
Normal - Helical Surface m. malik Main CFD Forum 3 February 3, 2006 12:56


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