---[preciceAdapter] Loaded the OpenFOAM-preCICE adapter - v1.2.2. ---[preciceAdapter] Reading preciceDict... ---[precice] This is preCICE version 2.5.0 ---[precice] Revision info: no-info [git failed to run] ---[precice] Build type: Release (without debug log) ---[precice] Configuring preCICE with configuration "precice-config.xml" ---[precice] I am participant "Fluid" ---[precice] Connecting Primary rank to 7 Secondary ranks ---[precice] Setting up primary communication to coupling partner/s ---[precice] Primary ranks are connected ---[precice] Setting up preliminary secondary communication to coupling partner/s ---[precice] Prepare partition for mesh Fluid-Mesh-Faces ---[precice] Prepare partition for mesh Fluid-Mesh-Nodes ---[precice] Receive global mesh Solid-Mesh ---[precice] Broadcast mesh Solid-Mesh ---[precice] Filter mesh Solid-Mesh by mappings ---[precice] Feedback distribution for mesh Solid-Mesh ---[precice] Setting up secondary communication to coupling partner/s ---[precice] Secondary ranks are connected ---[precice] Compute "read" mapping from mesh "Solid-Mesh" to mesh "Fluid-Mesh-Nodes". ---[precice] Using tree-based preallocation for matrix C ---[precice] Using tree-based preallocation for matrix A ---[precice] Using rescaling. Solver converged after 38 of 10000 iterations due to sufficient relative convergence. Last residual norm: 2.55813e-08, limits: relative 4.37607e-08 (rtol 1e-09), absolute 1e-50, divergence 4.37607e+31(dtol 1e+30) ---[precice] Mapping "Displacements0" consistent from "Solid-Mesh" (ID 2) to "Fluid-Mesh-Nodes" (ID 1) for dimension 0 with polynomial set to separate ---[precice] Mapping "Displacements0" consistent from "Solid-Mesh" (ID 2) to "Fluid-Mesh-Nodes" (ID 1) for dimension 1 with polynomial set to separate ---[precice] Mapping "Displacements0" consistent from "Solid-Mesh" (ID 2) to "Fluid-Mesh-Nodes" (ID 1) for dimension 2 with polynomial set to separate ---[precice] iteration: 1 of 50, time-window: 1, time: 0 of 5, time-window-size: 0.001, max-timestep-length: 0.001, ongoing: yes, time-window-complete: no, write-iteration-checkpoint ---[precice] Compute "write" mapping from mesh "Fluid-Mesh-Faces" to mesh "Solid-Mesh". ---[precice] Using tree-based preallocation for matrix C ---[precice] Using tree-based preallocation for matrix A ---[precice] Using rescaling. Solver converged after 38 of 10000 iterations due to sufficient relative convergence. Last residual norm: 2.55813e-08, limits: relative 4.37607e-08 (rtol 1e-09), absolute 1e-50, divergence 4.37607e+31(dtol 1e+30) ---[precice] Mapping "Forces0" conservative from "Fluid-Mesh-Faces" (ID 0) to "Solid-Mesh" (ID 2) for dimension 0 with polynomial set to separate ---[precice] Mapping "Forces0" conservative from "Fluid-Mesh-Faces" (ID 0) to "Solid-Mesh" (ID 2) for dimension 1 with polynomial set to separate ---[precice] Mapping "Forces0" conservative from "Fluid-Mesh-Faces" (ID 0) to "Solid-Mesh" (ID 2) for dimension 2 with polynomial set to separate ---[precice] initializeData is skipped since no data has to be initialized. ---[precice] Mapping "Displacements0" consistent from "Solid-Mesh" (ID 2) to "Fluid-Mesh-Nodes" (ID 1) for dimension 0 with polynomial set to separate ---[precice] Mapping "Displacements0" consistent from "Solid-Mesh" (ID 2) to "Fluid-Mesh-Nodes" (ID 1) for dimension 1 with polynomial set to separate ---[precice] Mapping "Displacements0" consistent from "Solid-Mesh" (ID 2) to "Fluid-Mesh-Nodes" (ID 1) for dimension 2 with polynomial set to separate [4]PETSC ERROR: ------------------------------------------------------------------------ [4]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [4]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [4]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [4]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [4]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [4]PETSC ERROR: to get more information on the crash. [4]PETSC ERROR: User provided function() at unknown file:0 -------------------------------------------------------------------------- MPI_ABORT was invoked on rank 4 in communicator MPI_COMM_WORLD with errorcode 59. NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes. You may or may not see output from other processes, depending on exactly when Open MPI kills them. -------------------------------------------------------------------------- [0]PETSC ERROR: ------------------------------------------------------------------------ [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [0]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [0]PETSC ERROR: to get more information on the crash. [0]PETSC ERROR: User provided function() at unknown file:0 [1]PETSC ERROR: ------------------------------------------------------------------------ [1]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [1]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [1]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [1]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [1]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [1]PETSC ERROR: to get more information on the crash. [1]PETSC ERROR: User provided function() at unknown file:0 [2]PETSC ERROR: ------------------------------------------------------------------------ [2]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [2]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [2]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [2]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [2]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [2]PETSC ERROR: to get more information on the crash. [2]PETSC ERROR: User provided function() at unknown file:0 [3]PETSC ERROR: ------------------------------------------------------------------------ [3]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [3]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [3]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [3]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [3]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [3]PETSC ERROR: to get more information on the crash. [3]PETSC ERROR: User provided function() at unknown file:0 [5]PETSC ERROR: ------------------------------------------------------------------------ [5]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [5]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [5]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [5]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [5]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [5]PETSC ERROR: to get more information on the crash. [5]PETSC ERROR: User provided function() at unknown file:0 [6]PETSC ERROR: ------------------------------------------------------------------------ [6]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [6]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [6]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [6]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [6]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [6]PETSC ERROR: to get more information on the crash. [6]PETSC ERROR: User provided function() at unknown file:0 [7]PETSC ERROR: ------------------------------------------------------------------------ [7]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range [7]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger [7]PETSC ERROR: or see https://petsc.org/release/faq/#valgrind [7]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors [7]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run [7]PETSC ERROR: to get more information on the crash. [7]PETSC ERROR: User provided function() at unknown file:0 ---[preciceAdapter] preCICE was configured and initialized