Find answers, ask questions, and connect with our <br>community around the world.

Home Forums OpenFOAM Forum error

  • Posted by Srinivas K on February 1, 2023 at 9:51 am

    Iam simulating one UAV and get this error.

    what is the solution

     

    displacementMedialAxis : Iteration 5
    Moving mesh using displacement scaling : min:0 max:1
    Checking faces in error :
    non-orthogonality > 65 degrees : 50
    faces with face pyramid volume < 1e-13 : 9
    faces with face-decomposition tet quality < 1e-15 : 250
    faces with concavity > 80 degrees : 0
    faces with skewness > 4 (internal) or 20 (boundary) : 0
    faces with interpolation weights (0..1) < 0.02 : 0
    faces with volume ratio of neighbour cells < 0.01 : 0
    faces with face twist < 0.02 : 3
    faces on cells with determinant < 0.001 : 20
    displacementMedialAxis : Finished moving mesh …
    truncateDisplacement : Unextruded 43 faces due to non-consecutive vertices being extruded.
    truncateDisplacement : Unextruded 18 faces due to stringed edges with inconsistent extrusion.
    truncateDisplacement : Unextruded 0 faces due to non-consecutive vertices being extruded.
    truncateDisplacement : Unextruded 0 faces due to stringed edges with inconsistent extrusion.

    Setting up information for layer truncation …
    Killed

    Barış Bicer replied 1 year, 4 months ago 3 Members · 5 Replies
  • 5 Replies
  • Vivek

    Administrator
    February 1, 2023 at 11:28 am

    Hi Srinivas,

    May I know which lesson is this from?

    Please elaborate on your question.

     

    Regards,

    Vivek

  • Srinivas K

    Member
    February 2, 2023 at 9:03 am

    this is not from the lesson.

    i take one geometry of UAV,  and run surfacefeatureextract, then blockMesh, they run successfully

    but when i run snappyHexMesh it run for half hour then above error came “killed”.

  • Barış Bicer

    Moderator
    February 2, 2023 at 4:00 pm

    did you checkyour memory???

  • Srinivas K

    Member
    February 3, 2023 at 4:28 am

    below is my CPU information

    about memory C drive have 19 GB space and D drive have 150GB

    shri@UNLRNDSVR03:~$ lscpu
    Architecture: x86_64
    CPU op-mode(s): 32-bit, 64-bit
    Byte Order: Little Endian
    Address sizes: 39 bits physical, 48 bits virtual
    CPU(s): 8
    On-line CPU(s) list: 0-7
    Thread(s) per core: 2
    Core(s) per socket: 4
    Socket(s): 1
    Vendor ID: GenuineIntel
    CPU family: 6
    Model: 142
    Model name: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Stepping: 10
    CPU MHz: 1992.000
    BogoMIPS: 3984.00
    Virtualization: VT-x
    Hypervisor vendor: Microsoft
    Virtualization type: full
    L1d cache: 128 KiB
    L1i cache: 128 KiB
    L2 cache: 1 MiB
    L3 cache: 8 MiB
    Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
    Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
    Vulnerability Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
    Vulnerability Meltdown: Mitigation; PTI
    Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
    Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
    Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB f illing
    Vulnerability Srbds: Unknown: Dependent on hypervisor status
    Vulnerability Tsx async abort: Not affected
    Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxs r sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpui d pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c r drand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti ssbd ibrs ibpb stibp tpr_ shadow vnmi ept vpid ept_ad fsgsbase bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap c lflushopt xsaveopt xsavec xgetbv1 xsaves flush_l1d arch_capabilities
    shri@UNLRNDSVR03:~$

  • Barış Bicer

    Moderator
    February 3, 2023 at 7:09 am

    Then can you decrease refinement level a bit and try to create very coarse mesh then we can understand that your memory is enough to create mesh or not

Log in to reply.

error: Content is protected !!