CheckMesh 실행 중 오류

Main Forums Mesh Generation CheckMesh 실행 중 오류

This topic contains 1 reply, has 2 voices, and was last updated by Dongjin Dongjin 1 year, 8 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #1113

    AmericaBS
    Participant

    안녕하세요.. 혹시 제 문제를 해결해 주실 분 안 계신가요?
    3차원 형상의 개수로를 격자 생성을 위해 blockMesh를 편집하고 checkMesh를 확인해 보았습니다만
    다음의 log로 fail이 뜹니다.

    /*---------------------------------------------------------------------------*\
    | ========= | |
    | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
    | \\ / O peration | Version: 2.2.2 |
    | \\ / A nd | Web: www.OpenFOAM.org |
    | \\/ M anipulation | |
    \*---------------------------------------------------------------------------*/
    Build : 2.2.2-9240f8b967db
    Exec : checkMesh
    Date : Jan 04 2016
    Time : 11:35:20
    Host : "fatemeh-Lenovo-IdeaPad-P400-Touch"
    PID : 3975
    Case : /home/fatemeh/Desktop/B23
    nProcs : 1
    sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
    fileModificationChecking : Monitoring run-time modified files using timeStampMaster
    allowSystemOperations : Disallowing user-supplied system call operations
    
    // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
    Create time
    
    Create polyMesh for time = 0
    
    Time = 0
    
    Mesh stats
    points: 689931
    faces: 1929200
    internal faces: 1790800
    cells: 620000
    faces per cell: 6
    boundary patches: 4
    point zones: 0
    face zones: 0
    cell zones: 0
    
    Overall number of cells of each type:
    hexahedra: 620000
    prisms: 0
    wedges: 0
    pyramids: 0
    tet wedges: 0
    tetrahedra: 0
    polyhedra: 0
    
    Checking topology...
    Boundary definition OK.
    Cell to face addressing OK.
    Point usage OK.
    Upper triangular ordering OK.
    Face vertices OK.
    Number of regions: 1 (OK).
    
    Checking patch topology for multiply connected surfaces...
    Patch Faces Points Surface topology 
    inlet 1000 1111 ok (non-closed singly connected) 
    walls 74400 75141 ok (non-closed singly connected) 
    outlet 1000 1111 ok (non-closed singly connected) 
    atmosphere 62000 62721 ok (non-closed singly connected) 
    
    Checking geometry...
    Overall domain bounding box (0 -5 -0.012948) (13 5 0.2)
    Mesh (non-empty, non-wedge) directions (1 1 1)
    Mesh (non-empty) directions (1 1 1)
    Boundary openness (-7.98207e-17 1.53335e-16 6.11549e-15) OK.
    ***High aspect ratio cells found, Max aspect ratio: 4.38289e+196, number of cells 10286
    <<Writing 10286 cells with high aspect ratio to set highAspectRatioCells
    Minimum face area = 1.24047e-07. Maximum face area = 0.00601414. Face area magnitudes OK.
    Min volume = 2e-300. Max volume = 4.4999e-05. Total volume = 9.19087. Cell volumes OK.
    Mesh non-orthogonality Max: 179.968 average: 44.4666
    *Number of severely non-orthogonal (> 70 degrees) faces: 214015.
    ***Number of non-orthogonality errors: 31660.
    <<Writing 245675 non-orthogonal faces to set nonOrthoFaces
    ***Error in face pyramids: 68843 faces are incorrectly oriented.
    <<Writing 37384 faces with incorrect orientation to set wrongOrientedFaces
    ***Max skewness = 81.1396, 119 highly skew faces detected which may impair the quality of the results
    <<Writing 119 skew faces to set skewFaces
    Coupled point location match (average 0) OK.
    
    Failed 4 mesh checks.
    
    End

    블록메쉬 딕트는 링크로 첨부하겠습니다.
    http://www.mediafire.com/view/zz9jam3n2y49l00/blocMesh.docx

    #1114
    Dongjin
    Dongjin
    Participant

    반갑습니다. AmericaBS님,
    checkMesh에서 -allGeometry, -allTopology 옵션을 이용하여 훑어보니 만드신 격자가
    음의 부피를 가지고 있었습니다. 이는 대체로 블록 정의 시 순서를 잘못 입력하여 생긴 오류로
    checkMesh 로그에서도 incorrectly oriented라고 명시되어 있습니다.
    OpenFOAM은 법선벡터 방향 등으로 인해 정의 순서에 굉장히 민감하므로 오른손 법칙을 이용하여 정의하시면
    도움이 될 것입니다.
    이외에도 0.149004와 같은 좌표보다는 0.15와 같은 값으로 통일한다면 더욱 오류를 줄일것 이라 생각됩니다.

    답변이 도움이 되었으면 좋겠습니다.
    수고하세요~

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.