Ansys Assistant will be unavailable on the Learning Forum starting January 30. An upgraded version is coming soon. We apologize for any inconvenience and appreciate your patience. Stay tuned for updates.
LS Dyna

LS Dyna

Topics related to LS-DYNA, Autodyn, Explicit STR and more.

ICFD mesh Initialization issue

    • ah3616
      Subscriber

      Hi - I am running an FSI simulation and my ICFD mesh cannot initialize.  I have a very fine mesh and mesh controls, MESH_BL, ICFD_CONTROL_GAP and other controls for the FSI mesh.  I am running into this error. "


       Implicit dynamics is now active
       ICFD::Mesh -> Start Mesh Generation
       ICFD::Mesh: Initializing.

      ===================================================================================
      =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
      =   RANK 1 PID 3849779 RUNNING AT g040
      =   KILLED BY SIGNAL: 9 (Killed)
      ===================================================================================

       

      I think it may be due to some of the folds in my parts (which is why I added the ICFD_CONTROL_GAP parameter). but I have not had this issue before until now. Any ideas? thanks

    • igandiko
      Ansys Employee

      Hello, could you please let me know the version? It seems the solver is terminating abruptly, do you see any traceback in the standard output? You may see some output in the cluster log file or on the terminal (for a local linux run).

    • ah3616
      Subscriber

      this is my library path: "openmpi-4.1.1_ucx_cuda_11.0.3_support/lib:$LD_LIBRARY_PATH"

      my openMPI: "/lsDyna/r1502i/ls-dyna_mpp_d_R15_0_2_x64_centos79_ifort190_sse2_intelmpi-2018"

      I can run other files with no issue incluing FSI. this specific FSI model is the only one that fails however it is a new file that has never been run with this mesh or specific parameters combination. 

       

      Here is my error file: 

      [g040:3849778:0:3849778] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x8)
      ==== backtrace (tid:3849778) ====
       0 0x0000000000012990 __funlockfile()  :0
       1 0x0000000009f77524 ms_remeshsurf_()  ???:0
       2 0x0000000009f6a9d7 msuite_trisurf_()  ???:0
       3 0x000000000a0f8e33 pfem_trisurf_()  ???:0
       4 0x000000000a100ade pfem_surf_ini_()  ???:0
       5 0x0000000009f48f9c pfem_mk_points_()  ???:0
       6 0x0000000009eacc78 pfem_meshgen2_()  ???:0
       7 0x00000000069d3177 lso_and_d3plot_extended_()  ???:0
       8 0x00000000015a591e wd3plot_()  ???:0
       9 0x00000000015e8839 dynai_()  ???:0
      10 0x00000000018c0047 overly_()  ???:0
      11 0x00000000007d5c4b lsinput_()  ???:0
      12 0x00000000007d1335 MAIN__()  ???:0
      13 0x000000000042bf62 main()  ???:0
      14 0x000000000003a7e5 __libc_start_main()  ???:0
      15 0x000000000042be6f _start()  ???:0
      =================================
      forrtl: severe (174): SIGSEGV, segmentation fault occurred
      Image              PC                Routine            Line        Source             
      ls-dyna_mpp_d_R15  000000000EEF1263  Unknown               Unknown  Unknown
      libpthread-2.28.s  0000155554B79990  Unknown               Unknown  Unknown
      ls-dyna_mpp_d_R15  0000000009F77524  Unknown               Unknown  Unknown
      ls-dyna_mpp_d_R15  0000000009F6A9D7  msuite_trisurf_          6463  mk_points.F
      ls-dyna_mpp_d_R15  000000000A0F8E33  pfem_trisurf_            1291  surfmesh.F
      ls-dyna_mpp_d_R15  000000000A100ADE  pfem_surf_ini_           3402  surfmesh.F
      ls-dyna_mpp_d_R15  0000000009F48F9C  pfem_mk_points_            42  mk_points.F
      ls-dyna_mpp_d_R15  0000000009EACC78  pfem_meshgen2_           1170  geo.F
      ls-dyna_mpp_d_R15  00000000069D3177  lso_and_d3plot_ex       15335  lso_and_d3plot_extended.f
      ls-dyna_mpp_d_R15  00000000015A591E  wd3plot_                 6825  wd3plot.f
      ls-dyna_mpp_d_R15  00000000015E8839  dynai_                  30409  dynai.f
      ls-dyna_mpp_d_R15  00000000018C0047  overly_                  3460  overly.f
      ls-dyna_mpp_d_R15  00000000007D5C4B  lsinput_                 3129  lsinput.f
      ls-dyna_mpp_d_R15  00000000007D1335  MAIN__                   5097  lsdyna.f
      ls-dyna_mpp_d_R15  000000000042BF62  Unknown               Unknown  Unknown
      libc-2.28.so       00001555525457E5  __libc_start_main     Unknown  Unknown
      ls-dyna_mpp_d_R15  000000000042BE6F  Unknown               Unknown  Unknown

    • ah3616
      Subscriber

      I also have run these FSI parameters on a different mesh that has less folds and complexities (overall smoother shape).  I have no issues with the mesh initilizing with the smoother mesh.  My new mesh has wrinkles which make it more complex - it could be that the version i am using of LSDYNA cannot handle the parameters with the new mesh. I also worry it could be a mesh issue and not a software issue but the more complex the model the more the software issue seems plausible to me. 

    • igandiko
      Ansys Employee

      Thank you, it is difficult to debug this issue wihtout the input file. MESH_BL, ICFD_CONTROL_GAP and FSI have been enhanced after R15, could you please try R16? You can also try to identify which feature is causing the issue? Is it MESH_BL? If so, have you tried different MESH_BL options?

    • ah3616
      Subscriber

      I do have a MESH_BL assigned. I use the same as the examples online and add my parts. I will check my version I believe its saved as R15 right now. 

      *MESH_BL
      $#     pid     nelth      blth      blfe      blst      bldr     iside
               1         1       0.0       0.0         0         0         0
               2         1       0.0       0.0         0         0         0
               3         1       0.0       0.0         0         0         0
      *MESH_BL_SYM
      $#    pid1      pid2      pid3      pid4      pid5      pid6      pid7      pid8
               4         0         0         0         0         0         0         0
               5         0         0         0         0         0         0         0

Viewing 5 reply threads
  • You must be logged in to reply to this topic.
[bingo_chatbox]