Start testing: Aug 23 09:38 CEST ---------------------------------------------------------- 1/39 Testing: precice.acceleration 1/39 Test: precice.acceleration Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=AccelerationTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/acceleration "precice.acceleration" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:22.428660] [0x00007faaded2f780] [debug] Initialize MPI [2022-08-23 09:38:22.429611] [0x00007fc0b8f99780] [debug] Initialize MPI [2022-08-23 09:38:22.430728] [0x00007f575bdb3780] [debug] Initialize MPI [2022-08-23 09:38:22.440188] [0x00007f99b9f92780] [debug] Initialize MPI This test suite runs on rank 2 of 4 Running This test suite runs on rank 3 of 4 Running 15 test cases... Setup up logging 15 test cases... Setup up logging This test suite runs on rank 1 of 4 Running This test suite runs on rank 0 of 4 Running 15 test cases... Setup up logging 15 test cases... Setup up logging Abort(336726543) on node 0 (rank 0 in comm 0): Fatal error in internal_Open_port: Other MPI error, error stack: internal_Open_port(86).......: MPI_Open_port(MPI_INFO_NULL, port_name=0x7fff58838910) failed MPID_Open_port(238)..........: MPIDI_UCX_get_local_upids(31): The function is currently not supported with ucx netmod Test time = 0.70 sec ---------------------------------------------------------- Test Failed. "precice.acceleration" end time: Aug 23 09:38 CEST "precice.acceleration" time elapsed: 00:00:00 ---------------------------------------------------------- 2/39 Testing: precice.action 2/39 Test: precice.action Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=ActionTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/action "precice.action" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:23.098388] [0x00007f0968fba780] [debug] Initialize MPI [2022-08-23 09:38:23.101867] [0x00007f6179203780] [debug] Initialize MPI [2022-08-23 09:38:23.105550] [0x00007f2f42a1d780] [debug] Initialize MPI [2022-08-23 09:38:23.109495] [0x00007f650e269780] [debug] Initialize MPI This test suite runs on rank 2 of 4 Running This test suite runs on rank 0 of 4 Running This test suite runs on rank 1 of 4 Running 11 test cases... Setup up logging 11 test cases... Setup up logging 11 test cases... Setup up logging This test suite runs on rank 3 of 4 Running 11 test cases... Setup up logging 09:38:24.045184||0|action::PythonAction|l250|initialize|WARNING: Python module "TestOmitAction1" does not define function vertexCallback(). 09:38:24.055714||0|action::PythonAction|l270|initialize|WARNING: Python module "TestOmitAction1" does not define function postAction(). 09:38:24.145632||0|action::PythonAction|l270|initialize|WARNING: Python module "TestOmitAction2" does not define function postAction(). 09:38:24.216442||0|action::PythonAction|l250|initialize|WARNING: Python module "TestOmitAction3" does not define function vertexCallback(). 09:38:24.219632||0|action::PythonAction|l270|initialize|WARNING: Python module "TestOmitAction3" does not define function postAction(). 09:38:24.297502||0|action::PythonAction|l238|initialize|WARNING: Python module "TestDeprecatedAction" does not define function performAction(). 09:38:24.356186||0|action::PythonAction|l258|initialize|WARNING: Python module "TestDeprecatedAction" defines the function vertexCallback with 3 arguments. The normal argument is deprecated and preCICE will pass None instead. Please use the following definition to silence this warning "def vertexCallback(id, coords):". 09:38:24.359588||0|action::PythonAction|l270|initialize|WARNING: Python module "TestDeprecatedAction" does not define function postAction(). vertex callback ... 09:38:24.619502||0|config::ActionConfiguration|l293|getTiming|WARNING: Regular-prior action timing is deprecated. Regular-prior will now revert to write-mapping-prior which performs the action before a write mapping and before the coupling update. 09:38:24.635615||0|config::ActionConfiguration|l293|getTiming|WARNING: Regular-prior action timing is deprecated. Regular-prior will now revert to write-mapping-prior which performs the action before a write mapping and before the coupling update. 09:38:24.655807||0|config::ActionConfiguration|l293|getTiming|WARNING: Regular-prior action timing is deprecated. Regular-prior will now revert to write-mapping-prior which performs the action before a write mapping and before the coupling update. 09:38:24.668228||0|config::ActionConfiguration|l293|getTiming|WARNING: Regular-prior action timing is deprecated. Regular-prior will now revert to write-mapping-prior which performs the action before a write mapping and before the coupling update. *** No errors detected  *** No errors detected  09:38:24.782212||0|config::ActionConfiguration|l293|getTiming|WARNING: Regular-prior action timing is deprecated. Regular-prior will now revert to write-mapping-prior which performs the action before a write mapping and before the coupling update.*** No errors detected  *** No errors detected  Test time = 1.78 sec ---------------------------------------------------------- Test Passed. "precice.action" end time: Aug 23 09:38 CEST "precice.action" time elapsed: 00:00:01 ---------------------------------------------------------- 3/39 Testing: precice.com 3/39 Test: precice.com Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=CommunicationTests:!CommunicationTests/MPIPorts:!CommunicationTests/MPISinglePorts" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/com "precice.com" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:24.873122] [0x00007f51949be780] [debug] Initialize MPI [2022-08-23 09:38:24.890407] [0x00007f5380e71780] [debug] Initialize MPI [2022-08-23 09:38:24.895615] [0x00007f63b2250780] [debug] Initialize MPI [2022-08-23 09:38:24.900747] [0x00007f5d8b798780] [debug] Initialize MPI This test suite runs on rank 2 of 4 Running This test suite runs on rank 0 of 4 Running 34 test cases... Setup up logging 34 test cases... Setup up logging This test suite runs on rank 1 of 4 Running This test suite runs on rank 3 of 4 Running 34 test cases... Setup up logging 34 test cases... Setup up logging *** No errors detected  *** No errors detected  *** No errors detected  *** No errors detected  Test time = 4.17 sec ---------------------------------------------------------- Test Passed. "precice.com" end time: Aug 23 09:38 CEST "precice.com" time elapsed: 00:00:04 ---------------------------------------------------------- 4/39 Testing: precice.com.mpiports 4/39 Test: precice.com.mpiports Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=CommunicationTests/MPIPorts:CommunicationTests/MPISinglePorts" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/com.mpiports "precice.com.mpiports" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:29.046987] [0x00007faf8e6e2780] [debug] Initialize MPI [2022-08-23 09:38:29.052681] [0x00007f7d2bb28780] [debug] Initialize MPI [2022-08-23 09:38:29.052861] [0x00007f05b7fd5780] [debug] Initialize MPI [2022-08-23 09:38:29.052953] [0x00007f16b90bf780] [debug] Initialize MPI This test suite runs on rank This test suite runs on rank 2 of 4 1 of 4 Running Running 35 test cases... 35Setup up logging test cases... Setup up logging This test suite runs on rank 0 of 4 Running This test suite runs on rank 3 of 4 Running 35 test cases... Setup up logging 35 test cases... Setup up logging Abort(68291087) on node 0 (rank 0 in comm 0): Fatal error in internal_Open_port: Other MPI error, error stack: internal_Open_port(86).......: MPI_Open_port(MPI_INFO_NULL, port_name=0x7ffdda2b18f0) failed MPID_Open_port(238)..........: MPIDI_UCX_get_local_upids(31): The function is currently not supported with ucx netmod Test time = 0.36 sec ---------------------------------------------------------- Test Failed. "precice.com.mpiports" end time: Aug 23 09:38 CEST "precice.com.mpiports" time elapsed: 00:00:00 ---------------------------------------------------------- 5/39 Testing: precice.cplscheme 5/39 Test: precice.cplscheme Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=CplSchemeTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/cplscheme "precice.cplscheme" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:29.398551] [0x00007fef5e255780] [debug] Initialize MPI [2022-08-23 09:38:29.401789] [0x00007f65511f8780] [debug] Initialize MPI [2022-08-23 09:38:29.409389] [0x00007f172b984780] [debug] Initialize MPI [2022-08-23 09:38:29.409687] [0x00007ff002309780] [debug] Initialize MPI This test suite runs on rank 1 of 4 Running This test suite runs on rank 2 of 4 Running 47 test cases... Setup up logging This test suite runs on rank 3 of 4 Running This test suite runs on rank 0 of 4 Running 47 test cases... Setup up logging 47 test cases... Setup up logging 47 test cases... Setup up logging *** No errors detected  *** No errors detected  *** No errors detected  *** No errors detected  Test time = 7.59 sec ---------------------------------------------------------- Test Passed. "precice.cplscheme" end time: Aug 23 09:38 CEST "precice.cplscheme" time elapsed: 00:00:07 ---------------------------------------------------------- 6/39 Testing: precice.io 6/39 Test: precice.io Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=IOTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/io "precice.io" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:36.978968] [0x00007f61dc023780] [debug] Initialize MPI [2022-08-23 09:38:36.980826] [0x00007f7291251780] [debug] Initialize MPI [2022-08-23 09:38:36.983066] [0x00007f30f9868780] [debug] Initialize MPI [2022-08-23 09:38:36.985231] [0x00007f00d34f5780] [debug] Initialize MPI This test suite runs on rank 1 of 4 Running This test suite runs on rank 2 of This test suite runs on rank 4 Running 0 of 4 Running 25 test cases... Setup up logging 25 test cases... Setup up logging 25 test cases... Setup up logging This test suite runs on rank 3 of 4 Running 25 test cases... Setup up logging 09:38:37.605751||0|io::ExportConfiguration|l63|xmlTagCallback|WARNING: You explicitly requested to export the vertex normals. This is deprecated, no longer functional, and the attribute will be removed in a future release. *** No errors detected  *** No errors detected  *** No errors detected  *** No errors detected  Test time = 2.12 sec ---------------------------------------------------------- Test Passed. "precice.io" end time: Aug 23 09:38 CEST "precice.io" time elapsed: 00:00:02 ---------------------------------------------------------- 7/39 Testing: precice.m2n 7/39 Test: precice.m2n Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=M2NTests:!M2NTests/MPIPorts:!M2NTets/MPISinglePorts" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/m2n "precice.m2n" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:39.098163] [0x00007fe362b11780] [debug] Initialize MPI [2022-08-23 09:38:39.102343] [0x00007fc1d9187780] [debug] Initialize MPI [2022-08-23 09:38:39.104093] [0x00007f67f74ab780] [debug] Initialize MPI [2022-08-23 09:38:39.119696] [0x00007ff172598780] [debug] Initialize MPI This test suite runs on rank 1 of 4 This test suite runs on rank 2 of 4 Running This test suite runs on rank 3 of 4 Running Running 8 test cases... Setup up logging This test suite runs on rank 8 test cases... Setup up logging 0 of 4 Running 8 test cases... Setup up logging 8 test cases... Setup up logging *** No errors detected  *** No errors detected  *** No errors detected  *** No errors detected  Test time = 1.85 sec ---------------------------------------------------------- Test Passed. "precice.m2n" end time: Aug 23 09:38 CEST "precice.m2n" time elapsed: 00:00:01 ---------------------------------------------------------- 8/39 Testing: precice.m2n.mpiports 8/39 Test: precice.m2n.mpiports Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=M2NTests/MPIPorts:M2NTests/MPISinglePorts" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/m2n.mpiports "precice.m2n.mpiports" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:40.951011] [0x00007f403de8c780] [debug] Initialize MPI [2022-08-23 09:38:40.951925] [0x00007f61874e2780] [debug] Initialize MPI [2022-08-23 09:38:40.952812] [0x00007f815a124780] [debug] Initialize MPI [2022-08-23 09:38:40.972053] [0x00007f18de3a2780] [debug] Initialize MPI This test suite runs on rank 1 of 4 This test suite runs on rank Running 0 of 4 Running This test suite runs on rank 2 of 4 Running 5 test cases... Setup up logging 5 test cases... Setup up logging This test suite runs on rank 5 test cases... Setup up logging 3 of 4 Running 5 test cases... Setup up logging Abort(873597455) on node 2 (rank 2 in comm 0): Fatal error in internal_Open_port: Other MPI error, error stack: internal_Open_port(86).......: MPI_Open_port(MPI_INFO_NULL, port_name=0x7ffec6b9e7c0) failed MPID_Open_port(238)..........: MPIDI_UCX_get_local_upids(31): The function is currently not supported with ucx netmod Test time = 0.45 sec ---------------------------------------------------------- Test Failed. "precice.m2n.mpiports" end time: Aug 23 09:38 CEST "precice.m2n.mpiports" time elapsed: 00:00:00 ---------------------------------------------------------- 9/39 Testing: precice.mapping 9/39 Test: precice.mapping Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=MappingTests:!MappingTests/PetRadialBasisFunctionMapping" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/mapping "precice.mapping" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:41.413892] [0x00007f5c375d8780] [debug] Initialize MPI [2022-08-23 09:38:41.416441] [0x00007f08caddd780] [debug] Initialize MPI [2022-08-23 09:38:41.417421] [0x00007f9006dcf780] [debug] Initialize MPI [2022-08-23 09:38:41.418163] [0x00007f8fadbea780] [debug] Initialize MPI This test suite runs on rank This test suite runs on rank This test suite runs on rank 3 of 4 Running 1 of 4 Running 0 of 4 Running 63 test cases63... Setup up logging test cases... Setup up logging 63 test cases... Setup up logging This test suite runs on rank 2 of 4 Running 63 test cases... Setup up logging 09:38:42.467986||0|mapping::NearestNeighborProjectionMapping|l75|computeMapping|WARNING: 3D Mesh "InMesh" does not contain triangles. Nearest projection mapping will map to primitives of lower dimension. 09:38:42.512060||0|mapping::NearestNeighborProjectionMapping|l75|computeMapping|WARNING: 3D Mesh "InMesh" does not contain triangles. Nearest projection mapping will map to primitives of lower dimension. *** No errors detected *** No errors detected *** No errors detected  *** No errors detected  Test time = 7.58 sec ---------------------------------------------------------- Test Passed. "precice.mapping" end time: Aug 23 09:38 CEST "precice.mapping" time elapsed: 00:00:07 ---------------------------------------------------------- 10/39 Testing: precice.mapping.petrbf 10/39 Test: precice.mapping.petrbf Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=MappingTests/PetRadialBasisFunctionMapping" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/mapping.petrbf "precice.mapping.petrbf" start time: Aug 23 09:38 CEST Output: ---------------------------------------------------------- [2022-08-23 09:38:48.977737] [0x00007f885f061780] [debug] Initialize MPI [2022-08-23 09:38:48.981558] [0x00007f05437b1780] [debug] Initialize MPI [2022-08-23 09:38:48.982083] [0x00007f24af630780] [debug] Initialize MPI [2022-08-23 09:38:48.983492] [0x00007f6a1aee7780] [debug] Initialize MPI This test suite runs on rank This test suite runs on rank 1 of 4 Running 0 of 4 Running This test suite runs on rank This test suite runs on rank 3 of 4 Running 2 of 4 Running 32 test cases... Setup up logging 32 test cases... Setup up logging 32 test cases... Setup up logging 32 test cases... Setup up logging Test time = 120.13 sec ---------------------------------------------------------- Test Failed. "precice.mapping.petrbf" end time: Aug 23 09:40 CEST "precice.mapping.petrbf" time elapsed: 00:02:00 ---------------------------------------------------------- 11/39 Testing: precice.math 11/39 Test: precice.math Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=MathTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/math "precice.math" start time: Aug 23 09:40 CEST Output: ---------------------------------------------------------- [2022-08-23 09:40:49.126093] [0x00007fa936724780] [debug] Initialize MPI [2022-08-23 09:40:49.129684] [0x00007f6b9f74e780] [debug] Initialize MPI [2022-08-23 09:40:49.133330] [0x00007feee0008780] [debug] Initialize MPI [2022-08-23 09:40:49.134340] [0x00007f668eac2780] [debug] Initialize MPI This test suite runs on rank 3 of 4 Running This test suite runs on rank 2 of 4 Running 64 test cases... Setup up logging This test suite runs on rank 1 of 4 Running 64 test cases... Setup up logging This test suite runs on rank 0 of 4 Running 64 test cases... Setup up logging 64 test cases... Setup up logging *** No errors detected  *** No errors detected *** No errors detected  *** No errors detected  Test time = 3.77 sec ---------------------------------------------------------- Test Passed. "precice.math" end time: Aug 23 09:40 CEST "precice.math" time elapsed: 00:00:03 ---------------------------------------------------------- 12/39 Testing: precice.mesh 12/39 Test: precice.mesh Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=MeshTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/mesh "precice.mesh" start time: Aug 23 09:40 CEST Output: ---------------------------------------------------------- [2022-08-23 09:40:52.882527] [0x00007f4a536b7780] [debug] Initialize MPI [2022-08-23 09:40:52.886789] [0x00007f3d5a2e4780] [debug] Initialize MPI [2022-08-23 09:40:52.888218] [0x00007f2a02fba780] [debug] Initialize MPI [2022-08-23 09:40:52.897501] [0x00007f8d4925b780] [debug] Initialize MPI This test suite runs on rank This test suite runs on rank 2 of 4 Running 3 of 4 Running This test suite runs on rank 1 of 4 Running 65 test cases... Setup up logging 65 test cases... Setup up logging 65 test cases... Setup up logging This test suite runs on rank 0 of 4 Running 65 test cases... Setup up logging *** No errors detected  *** No errors detected  *** No errors detected  *** No errors detected  Test time = 3.72 sec ---------------------------------------------------------- Test Passed. "precice.mesh" end time: Aug 23 09:40 CEST "precice.mesh" time elapsed: 00:00:03 ---------------------------------------------------------- 13/39 Testing: precice.partition 13/39 Test: precice.partition Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=PartitionTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/partition "precice.partition" start time: Aug 23 09:40 CEST Output: ---------------------------------------------------------- [2022-08-23 09:40:56.606105] [0x00007f31a25df780] [debug] Initialize MPI [2022-08-23 09:40:56.610761] [0x00007fab47f38780] [debug] Initialize MPI [2022-08-23 09:40:56.612457] [0x00007f531fe8d780] [debug] Initialize MPI [2022-08-23 09:40:56.613085] [0x00007f28b91f1780] [debug] Initialize MPI This test suite runs on rank 1 of 4 Running This test suite runs on rank This test suite runs on rank 2 of 40 of 4 Running 24 test cases... Setup up logging Running 24 test cases24... Setup up logging test cases... Setup up logging This test suite runs on rank 3 of 4 Running 24 test cases... Setup up logging 09:40:58.772301||1|partition::ReceivedPartition|l875|createOwnerInformation|WARNING: 2 of 6 vertices of mesh SolidzMesh have been filtered out since they have no influence on the mapping. 09:41:01.853039||1|partition::ReceivedPartition|l875|createOwnerInformation|WARNING: 1 of 3 vertices of mesh NastinMesh have been filtered out since they have no influence on the mapping. 09:41:02.551766||0|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 1 of 6 vertices of mesh mesh have been filtered out since they have no influence on the mapping. 09:41:02.556231||1|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 1 of 6 vertices of mesh mesh have been filtered out since they have no influence on the mapping. 09:41:02.563817||3|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 1 of 6 vertices of mesh mesh have been filtered out since they have no influence on the mapping. 09:41:02.715927||1|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 2 of 12 vertices of mesh mesh have been filtered out since they have no influence on the mapping. 09:41:02.719694||2|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 2 of 12 vertices of mesh mesh have been filtered out since they have no influence on the mapping. 09:41:02.727437||3|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 2 of 12 vertices of mesh mesh have been filtered out since they have no influence on the mapping. 09:41:02.959813||1|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 2 of 12 vertices of mesh mesh have been filtered out since they have no influence on the mapping. 09:41:02.963659||3|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 2 of 12 vertices of mesh mesh have been filtered out since they have no influence on the mapping. *** No errors detected 09:41:03.206429||1|partition::ReceivedPartition|l875|createOwnerInformation|WARNING: 2 of 6 vertices of mesh SolidzMesh have been filtered out since they have no influence on the mapping. *** No errors detected  *** No errors detected  *** No errors detected  Test time = 6.74 sec ---------------------------------------------------------- Test Passed. "precice.partition" end time: Aug 23 09:41 CEST "precice.partition" time elapsed: 00:00:06 ---------------------------------------------------------- 14/39 Testing: precice.interface 14/39 Test: precice.interface Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=PreciceTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/interface "precice.interface" start time: Aug 23 09:41 CEST Output: ---------------------------------------------------------- [2022-08-23 09:41:03.351247] [0x00007f8a876c4780] [debug] Initialize MPI [2022-08-23 09:41:03.353405] [0x00007fe4c8999780] [debug] Initialize MPI [2022-08-23 09:41:03.354819] [0x00007ff83e66a780] [debug] Initialize MPI [2022-08-23 09:41:03.356873] [0x00007f04b97b4780] [debug] Initialize MPI This test suite runs on rank 3 of 4 Running This test suite runs on rank This test suite runs on rank 1 of 4 Running 0 of 4 Running 40 test cases... Setup up logging 40 test cases... Setup up logging 40 test cases... Setup up logging This test suite runs on rank 2 of 4 Running 40 test cases... Setup up logging Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... No major issues detected Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... No major issues detected Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... No major issues detected No major issues detected Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... Checking /home/claudio/Projects/precice/precice-2.5.0/src/precice/tests/config-checker.xml for syntax and basic setup issues... No major issues detected No major issues detected No major issues detected No major issues detected 09:41:05.115958||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:05.167971||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:05.632669||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling.09:41:05.633387||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:05.644630||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling.09:41:05.645397||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:05.723577||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:05.727921||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:05.735963||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:05.747939||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:06.035874||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling.09:41:06.036380||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:06.139915||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. 09:41:06.143872||0|impl::WatchIntegral|l57|initialize|WARNING: Watch-integral is configured with scaling option on; however, mesh rectangle does not contain connectivity information. Therefore, the integral will be calculated without scaling. *** No errors detected  *** No errors detected  *** No errors detected  *** No errors detected  Test time = 3.79 sec ---------------------------------------------------------- Test Passed. "precice.interface" end time: Aug 23 09:41 CEST "precice.interface" time elapsed: 00:00:03 ---------------------------------------------------------- 15/39 Testing: precice.query 15/39 Test: precice.query Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=QueryTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/query "precice.query" start time: Aug 23 09:41 CEST Output: ---------------------------------------------------------- [2022-08-23 09:41:07.146051] [0x00007f61b0968780] [debug] Initialize MPI [2022-08-23 09:41:07.148578] [0x00007fb39384e780] [debug] Initialize MPI [2022-08-23 09:41:07.148860] [0x00007f2c8d127780] [debug] Initialize MPI [2022-08-23 09:41:07.157588] [0x00007f36b5963780] [debug] Initialize MPI This test suite runs on rank This test suite runs on rank 0 of 4 Running 1 of 4 Running 27 test cases... Setup up logging 27 test cases... Setup up logging This test suite runs on rank This test suite runs on rank 2 of 4 Running 3 of 4 Running 27 test cases... Setup up logging 27 test cases... Setup up logging *** No errors detected *** No errors detected  *** No errors detected  *** No errors detected  Test time = 1.64 sec ---------------------------------------------------------- Test Passed. "precice.query" end time: Aug 23 09:41 CEST "precice.query" time elapsed: 00:00:01 ---------------------------------------------------------- 16/39 Testing: precice.testing 16/39 Test: precice.testing Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=TestingTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/testing "precice.testing" start time: Aug 23 09:41 CEST Output: ---------------------------------------------------------- [2022-08-23 09:41:08.782528] [0x00007f53518e4780] [debug] Initialize MPI [2022-08-23 09:41:08.790137] [0x00007facd830e780] [debug] Initialize MPI [2022-08-23 09:41:08.792609] [0x00007fa9ec7e5780] [debug] Initialize MPI [2022-08-23 09:41:08.807878] [0x00007f5c7e893780] [debug] Initialize MPI This test suite runs on rank 1 of 4 This test suite runs on rank Running 3 of 4 Running 9 test cases... This test suite runs on rank 0 of 4 Running Setup up logging 9 test cases... Setup up logging This test suite runs on rank 2 of 4 Running 9 test cases... Setup up logging 9 test cases... Setup up logging *** No errors detected *** No errors detected  *** No errors detected  *** No errors detected  Test time = 1.27 sec ---------------------------------------------------------- Test Passed. "precice.testing" end time: Aug 23 09:41 CEST "precice.testing" time elapsed: 00:00:01 ---------------------------------------------------------- 17/39 Testing: precice.utils 17/39 Test: precice.utils Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=UtilsTests" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/utils "precice.utils" start time: Aug 23 09:41 CEST Output: ---------------------------------------------------------- [2022-08-23 09:41:10.050484] [0x00007f528c902780] [debug] Initialize MPI [2022-08-23 09:41:10.056079] [0x00007f6bfd41c780] [debug] Initialize MPI [2022-08-23 09:41:10.057398] [0x00007f1e75a38780] [debug] Initialize MPI [2022-08-23 09:41:10.060623] [0x00007f143fb0b780] [debug] Initialize MPI This test suite runs on rank 0 of 4 This test suite runs on rank 2 of 4 This test suite runs on rank 3 of 4 Running This test suite runs on rank 1 of 4 Running Running Running 42 test cases... Setup up logging 42 test cases... Setup up logging 42 test cases... Setup up logging 42 test cases... Setup up logging *** No errors detected  *** No errors detected  *** No errors detected  *** No errors detected  Test time = 3.23 sec ---------------------------------------------------------- Test Passed. "precice.utils" end time: Aug 23 09:41 CEST "precice.utils" time elapsed: 00:00:03 ---------------------------------------------------------- 18/39 Testing: precice.xml 18/39 Test: precice.xml Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=XML" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/xml "precice.xml" start time: Aug 23 09:41 CEST Output: ---------------------------------------------------------- [2022-08-23 09:41:13.285756] [0x00007f8eb21b7780] [debug] Initialize MPI [2022-08-23 09:41:13.288508] [0x00007f0b153ea780] [debug] Initialize MPI [2022-08-23 09:41:13.295847] [0x00007f1c18357780] [debug] Initialize MPI [2022-08-23 09:41:13.304150] [0x00007f697e478780] [debug] Initialize MPI This test suite runs on rank 3 of 4 Running This test suite runs on rank 2 of 4 Running This test suite runs on rank 1 of 4 Running 10 test cases... Setup up logging 10 test cases... Setup up logging This test suite runs on rank 0 of 4 Running 10 test cases... Setup up logging 10 test cases... Setup up logging *** No errors detected  *** No errors detected *** No errors detected  *** No errors detected  Test time = 1.60 sec ---------------------------------------------------------- Test Passed. "precice.xml" end time: Aug 23 09:41 CEST "precice.xml" time elapsed: 00:00:01 ---------------------------------------------------------- 19/39 Testing: precice.integration.Parallel 19/39 Test: precice.integration.Parallel Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=Integration/Parallel" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/integration.Parallel "precice.integration.Parallel" start time: Aug 23 09:41 CEST Output: ---------------------------------------------------------- [2022-08-23 09:41:14.878667] [0x00007f9d41ff9780] [debug] Initialize MPI [2022-08-23 09:41:14.881622] [0x00007f19e9d32780] [debug] Initialize MPI [2022-08-23 09:41:14.892861] [0x00007f36b5102780] [debug] Initialize MPI [2022-08-23 09:41:14.906016] [0x00007fdcc1762780] [debug] Initialize MPI This test suite runs on rank 1 of 4 Running This test suite runs on rank 0 of 4 47 test cases... Setup up logging Running 47 test cases... Setup up logging This test suite runs on rank 2 of 4 Running This test suite runs on rank 3 of 4 Running 47 test cases... Setup up logging 47 test cases... Setup up logging 09:41:46.174770|FluidSolver|0|config::ParticipantConfiguration|l621|finishParticipantConfiguration|WARNING: You are using the VTK exporter in the parallel participant FluidSolver. Note that this will export as PVTU instead. For consistency, prefer "" instead.09:41:46.185907|FluidSolver|2|config::ParticipantConfiguration|l621|finishParticipantConfiguration|WARNING: You are using the VTK exporter in the parallel participant FluidSolver. Note that this will export as PVTU instead. For consistency, prefer "" instead. 09:41:46.199861|FluidSolver|1|config::ParticipantConfiguration|l621|finishParticipantConfiguration|WARNING: You are using the VTK exporter in the parallel participant FluidSolver. Note that this will export as PVTU instead. For consistency, prefer "" instead. 09:41:46.293206|FluidSolver|0|partition::ReceivedPartition|l875|createOwnerInformation|WARNING: 17 of 34 vertices of mesh Nodes have been filtered out since they have no influence on the mapping. 09:41:47.442967|Structure|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless.09:41:47.443868|Structure|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless.09:41:47.444315|Fluid|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:47.451846|Fluid|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:47.952199|Fluid|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:47.953931|Structure|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:47.955182|Fluid|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:47.960470|Structure|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:47.987665|Fluid|0|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 1 of 4 vertices of mesh StructureMesh have been filtered out since they have no influence on the mapping. 09:41:47.995002|Fluid|1|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 1 of 4 vertices of mesh StructureMesh have been filtered out since they have no influence on the mapping. 09:41:48.835093|SolverOne|1|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm".09:41:48.837848|SolverOne|0|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm".09:41:48.839270|SolverTwo|0|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm". 09:41:48.841828|SolverOne|0|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm". 09:41:48.850220|SolverOne|1|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm". 09:41:48.856285|SolverTwo|0|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm". 09:41:48.864024|SolverTwo|1|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm". 09:41:48.866304|SolverTwo|1|config::ParticipantConfiguration|l377|xmlTagCallback|WARNING: Tag "master" is deprecated and will be removed in v3.0.0. Please use "intra-comm". 09:41:50.874830|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:50.880866|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:50.884928|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:50.893193|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:51.351102|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:51.366089|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:51.375692|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:51.387934|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:51.443818|SolverOne|0|partition::ReceivedPartition|l875|createOwnerInformation|WARNING: 2 of 5 vertices of mesh MeshTwo have been filtered out since they have no influence on the mapping. Associated data values of the filtered vertices will be filled with zero values in order to provide valid data for other participants when reading data. 09:41:51.825910|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:51.840061|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:51.845086|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:51.845839|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:51.883852|SolverOne|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:51.888387|SolverTwo|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:51.889168|SolverOne|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:51.895899|SolverTwo|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:52.301839|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:52.305240|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:52.306528|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:52.324358|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:52.746895|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:52.758828|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:52.763230|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:52.772533|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:52.807926|SolverOne|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:52.812525|SolverTwo|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:52.813357|SolverOne|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:52.817490|SolverTwo|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:53.219515|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:53.237569|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:53.245190|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:53.246263|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:53.712226|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:53.715719|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:53.720168|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:53.726098|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:54.206285|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:54.210978|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:54.220885|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:54.229484|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:54.283944|SolverOne|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.286228|SolverTwo|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.287035|SolverOne|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.287788|SolverTwo|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.349811|SolverOne|1|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 1 of 5 vertices of mesh MeshTwo have been filtered out since they have no influence on the mapping. 09:41:54.730924|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:54.740843|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:54.744612|SolverOne|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:54.744938|SolverTwo|1|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:54.779637|SolverOne|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.785086|SolverTwo|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.786347|SolverOne|0|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.791672|SolverTwo|1|impl::SolverInterfaceImpl|l58|preConnectSecondaryRanks|WARNING: Two-level initialization is still in beta testing. Several edge cases are known to fail. Please report problems nevertheless. 09:41:54.839621|SolverOne|1|partition::ReceivedPartition|l726|createOwnerInformation|WARNING: 1 of 5 vertices of mesh MeshTwo have been filtered out since they have no influence on the mapping. Abort(135399951) on node 2 (rank 2 in comm 0): Fatal error in internal_Open_port: Other MPI error, error stack: internal_Open_port(86).......: MPI_Open_port(MPI_INFO_NULL, port_name=0x7ffc8ebac3d0) failed MPID_Open_port(238)..........: MPIDI_UCX_get_local_upids(31): The function is currently not supported with ucx netmod Test time = 40.42 sec ---------------------------------------------------------- Test Failed. "precice.integration.Parallel" end time: Aug 23 09:41 CEST "precice.integration.Parallel" time elapsed: 00:00:40 ---------------------------------------------------------- 20/39 Testing: precice.integration.Serial 20/39 Test: precice.integration.Serial Command: "/usr/lib64/mpi/gcc/mpich/bin/mpiexec" "-n" "4" "/home/claudio/Projects/precice/precice-2.5.0/build/testprecice" "--run_test=Integration/Serial" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/integration.Serial "precice.integration.Serial" start time: Aug 23 09:41 CEST Output: ---------------------------------------------------------- [2022-08-23 09:41:55.311310] [0x00007f2f70a08780] [debug] Initialize MPI [2022-08-23 09:41:55.313143] [0x00007f45ecc43780] [debug] Initialize MPI [2022-08-23 09:41:55.313950] [0x00007f6df182e780] [debug] Initialize MPI [2022-08-23 09:41:55.314718] [0x00007f3915729780] [debug] Initialize MPI This test suite runs on rank 3 of 4 Running This test suite runs on rank 0 of 4 Running 95 test cases... Setup up logging This test suite runs on rank 1 of 4 Running 95 test cases... Setup up logging This test suite runs on rank 2 of 4 Running 95 test cases... Setup up logging 95 test cases... Setup up logging 09:41:56.873516|SolverSourceOne|0|config::ActionConfiguration|l297|getTiming|WARNING: Regular-post action timing is deprecated. Regular-post will now revert to read-mapping-prior which performs the action after the coupling update and before a read mapping.09:41:56.874066|SolverTarget|0|config::ActionConfiguration|l297|getTiming|WARNING: Regular-post action timing is deprecated. Regular-post will now revert to read-mapping-prior which performs the action after the coupling update and before a read mapping. 09:41:56.900854|SolverSourceTwo|0|config::ActionConfiguration|l297|getTiming|WARNING: Regular-post action timing is deprecated. Regular-post will now revert to read-mapping-prior which performs the action after the coupling update and before a read mapping. 09:41:58.451100|SolverTwo|0|config::ParticipantConfiguration|l358|xmlTagCallback|WARNING: You configured the read data with name "DataTwo" to use the waveform-order="1", which is currently still experimental. Use with care.09:41:58.460816|SolverOne|0|config::ParticipantConfiguration|l358|xmlTagCallback|WARNING: You configured the read data with name "DataTwo" to use the waveform-order="1", which is currently still experimental. Use with care. 09:41:58.462982|SolverOne|0|config::ParticipantConfiguration|l358|xmlTagCallback|WARNING: You configured the read data with name "DataOne" to use the waveform-order="1", which is currently still experimental. Use with care. 09:41:58.469278|SolverTwo|0|config::ParticipantConfiguration|l358|xmlTagCallback|WARNING: You configured the read data with name "DataOne" to use the waveform-order="1", which is currently still experimental. Use with care. 09:41:58.531228|SolverTwo|0|impl::SolverInterfaceImpl|l1477|readBlockVectorData|WARNING: Interpolation order of read data named "DataOne" is set to "1", but you are calling readBlockVectorData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readBlockVectorData or by setting interpolation order to 0.09:41:58.531978|SolverOne|0|impl::SolverInterfaceImpl|l1615|readBlockScalarData|WARNING: Interpolation order of read data named "DataTwo" is set to "1", but you are calling readBlockScalarData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readBlockScalarData or by setting interpolation order to 0. 09:41:58.532347|SolverOne|0|impl::SolverInterfaceImpl|l1683|readScalarData|WARNING: Interpolation order of read data named "DataTwo" is set to "1", but you are calling readScalarData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readScalarData or by setting interpolation order to 0. 09:41:58.534258|SolverTwo|0|impl::SolverInterfaceImpl|l1548|readVectorData|WARNING: Interpolation order of read data named "DataOne" is set to "1", but you are calling readVectorData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readVectorData or by setting interpolation order to 0. 09:41:58.544434|SolverOne|0|impl::SolverInterfaceImpl|l1615|readBlockScalarData|WARNING: Interpolation order of read data named "DataTwo" is set to "1", but you are calling readBlockScalarData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readBlockScalarData or by setting interpolation order to 0. 09:41:58.544926|SolverOne|0|impl::SolverInterfaceImpl|l1683|readScalarData|WARNING: Interpolation order of read data named "DataTwo" is set to "1", but you are calling readScalarData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readScalarData or by setting interpolation order to 0. 09:41:58.547390|SolverTwo|0|impl::SolverInterfaceImpl|l1477|readBlockVectorData|WARNING: Interpolation order of read data named "DataOne" is set to "1", but you are calling readBlockVectorData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readBlockVectorData or by setting interpolation order to 0. 09:41:58.548017|SolverTwo|0|impl::SolverInterfaceImpl|l1548|readVectorData|WARNING: Interpolation order of read data named "DataOne" is set to "1", but you are calling readVectorData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readVectorData or by setting interpolation order to 0. 09:41:58.556372|SolverOne|0|impl::SolverInterfaceImpl|l1615|readBlockScalarData|WARNING: Interpolation order of read data named "DataTwo" is set to "1", but you are calling readBlockScalarData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readBlockScalarData or by setting interpolation order to 0. 09:41:58.556754|SolverOne|0|impl::SolverInterfaceImpl|l1683|readScalarData|WARNING: Interpolation order of read data named "DataTwo" is set to "1", but you are calling readScalarData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readScalarData or by setting interpolation order to 0. 09:41:58.564685|SolverTwo|0|impl::SolverInterfaceImpl|l1477|readBlockVectorData|WARNING: Interpolation order of read data named "DataOne" is set to "1", but you are calling readBlockVectorData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readBlockVectorData or by setting interpolation order to 0. 09:41:58.567930|SolverTwo|0|impl::SolverInterfaceImpl|l1548|readVectorData|WARNING: Interpolation order of read data named "DataOne" is set to "1", but you are calling readVectorData without providing a relativeReadTime. This looks like an error. You can fix this by providing a relativeReadTime to readVectorData or by setting interpolation order to 0. 09:41:58.881970|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:58.889904|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:59.206090|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:59.209659|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:59.512409|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:59.517733|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:59.869088|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:59.876586|SolverTwo|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshOne" to use the option access-direct="true", which is currently still experimental. Use with care.09:41:59.879930|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshTwo" to use the option access-direct="true", which is currently still experimental. Use with care. 09:41:59.884598|SolverOne|0|config::ParticipantConfiguration|l298|xmlTagCallback|WARNING: You configured the received mesh "MeshOne" to use the option access-direct="true", which is currently still experimental. Use with care. 09:42:00.411945|SolverTwo|0|mapping::NearestNeighborProjectionMapping|l69|computeMapping|WARNING: 2D Mesh "MeshOne" does not contain edges. Nearest projection mapping falls back to nearest neighbor mapping. 09:42:00.856189|SolverTwo|0|mapping::NearestNeighborProjectionMapping|l69|computeMapping|WARNING: 2D Mesh "MeshOne" does not contain edges. Nearest projection mapping falls back to nearest neighbor mapping. Abort(806488591) on node 1 (rank 1 in comm 0): Fatal error in internal_Open_port: Other MPI error, error stack: internal_Open_port(86).......: MPI_Open_port(MPI_INFO_NULL, port_name=0x7ffe93f7f120) failed MPID_Open_port(238)..........: MPIDI_UCX_get_local_upids(31): The function is currently not supported with ucx netmod Test time = 7.40 sec ---------------------------------------------------------- Test Failed. "precice.integration.Serial" end time: Aug 23 09:42 CEST "precice.integration.Serial" time elapsed: 00:00:07 ---------------------------------------------------------- 21/39 Testing: precice.solverdummy.build.cpp 21/39 Test: precice.solverdummy.build.cpp Command: "/usr/bin/ctest" "--build-and-test" "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/cpp" "/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp" "--build-generator" "Unix Makefiles" "--build-options" "-Dprecice_DIR=/home/claudio/Projects/precice/precice-2.5.0/build" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_Fortran_COMPILER=/usr/bin/gfortran" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp "precice.solverdummy.build.cpp" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- Internal cmake changing into directory: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp ======== CMake output ====== The CXX compiler identification is GNU 7.5.0 Detecting CXX compiler ABI info Detecting CXX compiler ABI info - done Check for working CXX compiler: /usr/bin/c++ - skipped Detecting CXX compile features Detecting CXX compile features - done Looking for C++ include pthread.h Looking for C++ include pthread.h - found Performing Test CMAKE_HAVE_LIBC_PTHREAD Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed Looking for pthread_create in pthreads Looking for pthread_create in pthreads - not found Looking for pthread_create in pthread Looking for pthread_create in pthread - found Found Threads: TRUE Configuring done Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_C_COMPILER CMAKE_Fortran_COMPILER Build files have been written to: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp ======== End CMake output ====== Change Dir: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp Run Clean Command:/usr/bin/gmake -f Makefile clean Run Build Command(s):/usr/bin/gmake -f Makefile && [ 50%] Building CXX object CMakeFiles/solverdummy.dir/solverdummy.cpp.o /home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/cpp/solverdummy.cpp: In function ‘int main(int, char**)’: /home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/cpp/solverdummy.cpp:73:39: warning: ‘bool precice::SolverInterface::isReadDataAvailable() const’ is deprecated: Will be removed in 3.0.0. See https://github.com/precice/precice/issues/1223 and comment, if you need this function. [-Wdeprecated-declarations] if (interface.isReadDataAvailable()) { ^ In file included from /home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/cpp/solverdummy.cpp:3:0: /home/claudio/Projects/precice/precice-2.5.0/src/precice/SolverInterface.hpp:244:143: note: declared here [[deprecated("Will be removed in 3.0.0. See https://github.com/precice/precice/issues/1223 and comment, if you need this function.")]] bool isReadDataAvailable() const; ^~~~~~~~~~~~~~~~~~~ /home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/cpp/solverdummy.cpp:81:41: warning: ‘bool precice::SolverInterface::isWriteDataRequired(double) const’ is deprecated: Will be removed in 3.0.0. See https://github.com/precice/precice/issues/1223 and comment, if you need this function. [-Wdeprecated-declarations] if (interface.isWriteDataRequired(dt)) { ^ In file included from /home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/cpp/solverdummy.cpp:3:0: /home/claudio/Projects/precice/precice-2.5.0/src/precice/SolverInterface.hpp:266:143: note: declared here [[deprecated("Will be removed in 3.0.0. See https://github.com/precice/precice/issues/1223 and comment, if you need this function.")]] bool isWriteDataRequired(double computedTimestepLength) const; ^~~~~~~~~~~~~~~~~~~ [100%] Linking CXX executable solverdummy [100%] Built target solverdummy Test time = 1.67 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.build.cpp" end time: Aug 23 09:42 CEST "precice.solverdummy.build.cpp" time elapsed: 00:00:01 ---------------------------------------------------------- 22/39 Testing: precice.solverdummy.build.c 22/39 Test: precice.solverdummy.build.c Command: "/usr/bin/ctest" "--build-and-test" "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/c" "/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c" "--build-generator" "Unix Makefiles" "--build-options" "-Dprecice_DIR=/home/claudio/Projects/precice/precice-2.5.0/build" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_Fortran_COMPILER=/usr/bin/gfortran" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c "precice.solverdummy.build.c" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- Internal cmake changing into directory: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c ======== CMake output ====== The C compiler identification is GNU 7.5.0 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Looking for pthread.h Looking for pthread.h - found Performing Test CMAKE_HAVE_LIBC_PTHREAD Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed Looking for pthread_create in pthreads Looking for pthread_create in pthreads - not found Looking for pthread_create in pthread Looking for pthread_create in pthread - found Found Threads: TRUE Configuring done Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_CXX_COMPILER CMAKE_Fortran_COMPILER Build files have been written to: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c ======== End CMake output ====== Change Dir: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c Run Clean Command:/usr/bin/gmake -f Makefile clean Run Build Command(s):/usr/bin/gmake -f Makefile && [ 50%] Building C object CMakeFiles/solverdummy.dir/solverdummy.c.o [100%] Linking C executable solverdummy [100%] Built target solverdummy Test time = 0.75 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.build.c" end time: Aug 23 09:42 CEST "precice.solverdummy.build.c" time elapsed: 00:00:00 ---------------------------------------------------------- 23/39 Testing: precice.solverdummy.build.fortran 23/39 Test: precice.solverdummy.build.fortran Command: "/usr/bin/ctest" "--build-and-test" "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/fortran" "/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran" "--build-generator" "Unix Makefiles" "--build-options" "-Dprecice_DIR=/home/claudio/Projects/precice/precice-2.5.0/build" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_Fortran_COMPILER=/usr/bin/gfortran" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran "precice.solverdummy.build.fortran" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- Internal cmake changing into directory: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran ======== CMake output ====== The C compiler identification is GNU 7.5.0 The Fortran compiler identification is GNU 7.5.0 Detecting C compiler ABI info Detecting C compiler ABI info - done Check for working C compiler: /usr/bin/cc - skipped Detecting C compile features Detecting C compile features - done Detecting Fortran compiler ABI info Detecting Fortran compiler ABI info - done Check for working Fortran compiler: /usr/bin/gfortran - skipped Checking whether /usr/bin/gfortran supports Fortran 90 Checking whether /usr/bin/gfortran supports Fortran 90 - yes Looking for pthread.h Looking for pthread.h - found Performing Test CMAKE_HAVE_LIBC_PTHREAD Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed Looking for pthread_create in pthreads Looking for pthread_create in pthreads - not found Looking for pthread_create in pthread Looking for pthread_create in pthread - found Found Threads: TRUE Configuring done Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_CXX_COMPILER Build files have been written to: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran ======== End CMake output ====== Change Dir: /home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran Run Clean Command:/usr/bin/gmake -f Makefile clean Run Build Command(s):/usr/bin/gmake -f Makefile && Scanning dependencies of target solverdummy [ 50%] Building Fortran object CMakeFiles/solverdummy.dir/solverdummy.f90.o [100%] Linking Fortran executable solverdummy [100%] Built target solverdummy Test time = 1.04 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.build.fortran" end time: Aug 23 09:42 CEST "precice.solverdummy.build.fortran" time elapsed: 00:00:01 ---------------------------------------------------------- 24/39 Testing: precice.solverdummy.run.cpp-cpp 24/39 Test: precice.solverdummy.run.cpp-cpp Command: "/usr/bin/cmake" "-D" "WRAPPER=/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_B=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_RUN_DIR=/home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.cpp-cpp" "-D" "DUMMY_CONFIG=/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" "-P" "/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.cmake" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.cpp-cpp "precice.solverdummy.run.cpp-cpp" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverTwo". DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverOne". preCICE: This is preCICE version 2.5.0 preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" preCICE: Setting up primary communication to coupling partner/spreCICE: This is preCICE version 2.5.0 preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" 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: Receive global mesh MeshOne preCICE: Primary ranks are connected preCICE: Setting up preliminary secondary communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up secondary communication to coupling partner/s preCICE: Setting up secondary communication to coupling partner/s preCICE: Secondary ranks are connected preCICE: Secondary ranks are connected preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint DUMMY: Writing iteration checkpoint preCICE: Compute "read" mapping from mesh "MeshOne" to mesh "MeshTwo". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint DUMMY: Writing iteration checkpoint preCICE: Compute "write" mapping from mesh "MeshTwo" to mesh "MeshOne". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels DUMMY: Closing C++ solver dummy... DUMMY: Closing C++ solver dummy... Test time = 0.23 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.run.cpp-cpp" end time: Aug 23 09:42 CEST "precice.solverdummy.run.cpp-cpp" time elapsed: 00:00:00 ---------------------------------------------------------- 25/39 Testing: precice.solverdummy.run.c-c 25/39 Test: precice.solverdummy.run.c-c Command: "/usr/bin/cmake" "-D" "WRAPPER=/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_B=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_RUN_DIR=/home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.c-c" "-D" "DUMMY_CONFIG=/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" "-P" "/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.cmake" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.c-c "precice.solverdummy.run.c-c" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverTwo". DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverOne". preCICE: This is preCICE version 2.5.0preCICE: This is preCICE version 2.5.0 preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" preCICE: Setting up primary communication to coupling partner/s preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" 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 MeshOne preCICE: Gather mesh MeshOnepreCICE: Primary ranks are connected preCICE: Send global mesh MeshOne preCICE: Setting up preliminary secondary communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Prepare partition for mesh MeshTwopreCICE: Setting up secondary communication to coupling partner/s preCICE: Setting up secondary communication to coupling partner/s preCICE: Secondary ranks are connected preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint DUMMY: Writing iteration checkpoint preCICE: Secondary ranks are connected preCICE: Compute "read" mapping from mesh "MeshOne" to mesh "MeshTwo". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint DUMMY: Writing iteration checkpoint preCICE: Compute "write" mapping from mesh "MeshTwo" to mesh "MeshOne". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels DUMMY: Closing C solver dummy... DUMMY: Closing C solver dummy... Test time = 0.23 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.run.c-c" end time: Aug 23 09:42 CEST "precice.solverdummy.run.c-c" time elapsed: 00:00:00 ---------------------------------------------------------- 26/39 Testing: precice.solverdummy.run.fortran-fortran 26/39 Test: precice.solverdummy.run.fortran-fortran Command: "/usr/bin/cmake" "-D" "WRAPPER=/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_B=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_RUN_DIR=/home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.fortran-fortran" "-D" "DUMMY_CONFIG=/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" "-P" "/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.cmake" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.fortran-fortran "precice.solverdummy.run.fortran-fortran" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- DUMMY: Starting Fortran solver dummy... DUMMY: Starting Fortran solver dummy... preCICE: This is preCICE version 2.5.0preCICE: This is preCICE version 2.5.0 preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" preCICE: Setting up primary communication to coupling partner/s preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" 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 MeshOne preCICE: Gather mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Setting up secondary communication to coupling partner/spreCICE: Primary ranks are connected preCICE: Setting up preliminary secondary communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up secondary communication to coupling partner/s preCICE: Secondary ranks are connected preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint preCICE: initializeData is skipped since no data has to be initialized. DUMMY: Writing iteration checkpoint readData: 0.0000000000000000 0.0000000000000000 0.0000000000000000 1.0000000000000000 1.0000000000000000 1.0000000000000000 2.0000000000000000 2.0000000000000000 2.0000000000000000 preCICE: Secondary ranks are connected preCICE: Compute "read" mapping from mesh "MeshOne" to mesh "MeshTwo". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint preCICE: Compute "write" mapping from mesh "MeshTwo" to mesh "MeshOne". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: initializeData is skipped since no data has to be initialized. DUMMY: Writing iteration checkpoint readData: 1.0000000000000000 1.0000000000000000 1.0000000000000000 2.0000000000000000 2.0000000000000000 2.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 2.0000000000000000 2.0000000000000000 2.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 4.0000000000000000 4.0000000000000000 4.0000000000000000 preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 3.0000000000000000 3.0000000000000000 3.0000000000000000 4.0000000000000000 4.0000000000000000 4.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint readData: 4.0000000000000000 4.0000000000000000 4.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 6.0000000000000000 6.0000000000000000 6.0000000000000000 preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint readData: 5.0000000000000000 5.0000000000000000 5.0000000000000000 6.0000000000000000 6.0000000000000000 6.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 6.0000000000000000 6.0000000000000000 6.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 8.0000000000000000 8.0000000000000000 8.0000000000000000 preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 7.0000000000000000 7.0000000000000000 7.0000000000000000 8.0000000000000000 8.0000000000000000 8.0000000000000000 9.0000000000000000 9.0000000000000000 9.0000000000000000 preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels DUMMY: Closing Fortran solver dummy... DUMMY: Closing Fortran solver dummy... Test time = 0.25 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.run.fortran-fortran" end time: Aug 23 09:42 CEST "precice.solverdummy.run.fortran-fortran" time elapsed: 00:00:00 ---------------------------------------------------------- 27/39 Testing: precice.solverdummy.run.cpp-c 27/39 Test: precice.solverdummy.run.cpp-c Command: "/usr/bin/cmake" "-D" "WRAPPER=/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_B=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_RUN_DIR=/home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.cpp-c" "-D" "DUMMY_CONFIG=/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" "-P" "/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.cmake" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.cpp-c "precice.solverdummy.run.cpp-c" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverOne". DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverTwo". preCICE: This is preCICE version 2.5.0preCICE: This is preCICE version 2.5.0 preCICE: Revision info: no-info [git failed to run] preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" preCICE: I am participant "SolverOne" preCICE: Setting up primary communication to coupling partner/spreCICE: Setting up primary communication to coupling partner/s preCICE: Primary ranks are connected preCICE: Setting up preliminary secondary communication to coupling partner/spreCICE: Primary ranks are connected preCICE: Prepare partition for mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Setting up preliminary secondary communication to coupling partner/s preCICE: Send global mesh MeshOne preCICE: Setting up secondary communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up secondary communication to coupling partner/s preCICE: Secondary ranks are connected preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint preCICE: Secondary ranks are connected DUMMY: Writing iteration checkpoint preCICE: Compute "read" mapping from mesh "MeshOne" to mesh "MeshTwo". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint DUMMY: Writing iteration checkpoint preCICE: Compute "write" mapping from mesh "MeshTwo" to mesh "MeshOne". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels DUMMY: Closing C++ solver dummy... DUMMY: Closing C solver dummy... Test time = 0.23 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.run.cpp-c" end time: Aug 23 09:42 CEST "precice.solverdummy.run.cpp-c" time elapsed: 00:00:00 ---------------------------------------------------------- 28/39 Testing: precice.solverdummy.run.cpp-fortran 28/39 Test: precice.solverdummy.run.cpp-fortran Command: "/usr/bin/cmake" "-D" "WRAPPER=/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/cpp/solverdummy" "-D" "DUMMY_B=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_RUN_DIR=/home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.cpp-fortran" "-D" "DUMMY_CONFIG=/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" "-P" "/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.cmake" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.cpp-fortran "precice.solverdummy.run.cpp-fortran" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- DUMMY: Starting Fortran solver dummy... DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverOne". preCICE: This is preCICE version 2.5.0preCICE: This is preCICE version 2.5.0 preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: Revision info: no-info [git failed to run] preCICE: I am participant "SolverTwo" preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne" preCICE: Setting up primary communication to coupling partner/spreCICE: Setting up primary communication to coupling partner/s preCICE: Primary ranks are connectedpreCICE: Primary ranks are connected preCICE: Setting up preliminary secondary communication to coupling partner/s preCICE: Prepare partition for mesh MeshOne preCICE: Setting up preliminary secondary communication to coupling partner/s preCICE: Gather mesh MeshOne preCICE: Receive global mesh MeshOne preCICE: Send global mesh MeshOne preCICE: Setting up secondary communication to coupling partner/spreCICE: Prepare partition for mesh MeshTwo preCICE: Setting up secondary communication to coupling partner/s preCICE: Secondary ranks are connectedpreCICE: Secondary ranks are connected preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint DUMMY: Writing iteration checkpoint preCICE: Compute "read" mapping from mesh "MeshOne" to mesh "MeshTwo". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint preCICE: Compute "write" mapping from mesh "MeshTwo" to mesh "MeshOne". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: initializeData is skipped since no data has to be initialized. DUMMY: Writing iteration checkpoint readData: 1.0000000000000000 1.0000000000000000 1.0000000000000000 2.0000000000000000 2.0000000000000000 2.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 3.0000000000000000 3.0000000000000000 3.0000000000000000 4.0000000000000000 4.0000000000000000 4.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint readData: 5.0000000000000000 5.0000000000000000 5.0000000000000000 6.0000000000000000 6.0000000000000000 6.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 7.0000000000000000 7.0000000000000000 7.0000000000000000 8.0000000000000000 8.0000000000000000 8.0000000000000000 9.0000000000000000 9.0000000000000000 9.0000000000000000 preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels DUMMY: Closing C++ solver dummy... DUMMY: Closing Fortran solver dummy... Test time = 0.25 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.run.cpp-fortran" end time: Aug 23 09:42 CEST "precice.solverdummy.run.cpp-fortran" time elapsed: 00:00:00 ---------------------------------------------------------- 29/39 Testing: precice.solverdummy.run.c-fortran 29/39 Test: precice.solverdummy.run.c-fortran Command: "/usr/bin/cmake" "-D" "WRAPPER=/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.sh" "-D" "DUMMY_A=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/c/solverdummy" "-D" "DUMMY_B=/home/claudio/Projects/precice/precice-2.5.0/build/Solverdummies/fortran/solverdummy" "-D" "DUMMY_RUN_DIR=/home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.c-fortran" "-D" "DUMMY_CONFIG=/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" "-P" "/home/claudio/Projects/precice/precice-2.5.0/cmake/runsolverdummies.cmake" Directory: /home/claudio/Projects/precice/precice-2.5.0/build/TestOutput/solverdummy.run.c-fortran "precice.solverdummy.run.c-fortran" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- DUMMY: Starting Fortran solver dummy... DUMMY: Running solver dummy with preCICE config file "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" and participant name "SolverOne". preCICE: This is preCICE version 2.5.0preCICE: This is preCICE version 2.5.0 preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverOne"preCICE: Revision info: no-info [git failed to run] preCICE: Build type: Debug preCICE: Configuring preCICE with configuration "/home/claudio/Projects/precice/precice-2.5.0/examples/solverdummies/precice-config.xml" preCICE: I am participant "SolverTwo" preCICE: Setting up primary communication to coupling partner/spreCICE: Setting up primary communication to coupling partner/s preCICE: Primary ranks are connected preCICE: Setting up preliminary secondary communication to coupling partner/spreCICE: Primary ranks are connected preCICE: Prepare partition for mesh MeshOne preCICE: Gather mesh MeshOne preCICE: Setting up preliminary secondary communication to coupling partner/s preCICE: Send global mesh MeshOne preCICE: Setting up secondary communication to coupling partner/s preCICE: Receive global mesh MeshOne preCICE: Prepare partition for mesh MeshTwo preCICE: Setting up secondary communication to coupling partner/s preCICE: Secondary ranks are connected preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint preCICE: Secondary ranks are connected DUMMY: Writing iteration checkpoint preCICE: Compute "read" mapping from mesh "MeshOne" to mesh "MeshTwo". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: iteration: 1 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, write-iteration-checkpoint preCICE: Compute "write" mapping from mesh "MeshTwo" to mesh "MeshOne". preCICE: Mapping distance min:0 max:0 avg: 0 var: 0 cnt: 3 preCICE: initializeData is skipped since no data has to be initialized. DUMMY: Writing iteration checkpoint readData: 1.0000000000000000 1.0000000000000000 1.0000000000000000 1.0000000000000000 1.0000000000000000 1.0000000000000000 1.0000000000000000 1.0000000000000000 1.0000000000000000 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 1 of 2, time: 0, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 3.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 3.0000000000000000 preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: yes, write-iteration-checkpoint DUMMY: Advancing in time DUMMY: Writing iteration checkpoint readData: 5.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 5.0000000000000000 preCICE: min iteration convergence measure: #it = 1 of 5, conv = false preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint preCICE: iteration: 2 of 2, time-window: 2 of 2, time: 1, time-window-size: 1, max-timestep-length: 1, ongoing: yes, time-window-complete: no, read-iteration-checkpoint DUMMY: Reading iteration checkpoint readData: 7.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 7.0000000000000000 preCICE: min iteration convergence measure: #it = 2 of 5, conv = false preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels preCICE: Time window completed preCICE: iteration: 1 of 2, time-window: 3 of 2, time: 2, time-window-size: 1, max-timestep-length: 1, ongoing: no, time-window-complete: yes, DUMMY: Advancing in time preCICE: Synchronize participants and close communication channels DUMMY: Closing C solver dummy... DUMMY: Closing Fortran solver dummy... Test time = 0.23 sec ---------------------------------------------------------- Test Passed. "precice.solverdummy.run.c-fortran" end time: Aug 23 09:42 CEST "precice.solverdummy.run.c-fortran" time elapsed: 00:00:00 ---------------------------------------------------------- 30/39 Testing: precice.tools.noarg 30/39 Test: precice.tools.noarg Command: "/home/claudio/Projects/precice/precice-2.5.0/build/precice-tools" Directory: /home/claudio/Projects/precice/precice-2.5.0/build "precice.tools.noarg" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- Usage: Print XML reference : precice-tools xml Print DTD for XML config : precice-tools dtd Print Markdown reference : precice-tools md Print preCICE version : precice-tools version precice-tools --version Check configuration file : precice-tools check FILE [ PARTICIPANT [ COMMSIZE ] ] Test time = 0.01 sec ---------------------------------------------------------- Test Passed. "precice.tools.noarg" end time: Aug 23 09:42 CEST "precice.tools.noarg" time elapsed: 00:00:00 ---------------------------------------------------------- 31/39 Testing: precice.tools.invalidcmd 31/39 Test: precice.tools.invalidcmd Command: "/home/claudio/Projects/precice/precice-2.5.0/build/precice-tools" "invalidcommand" Directory: /home/claudio/Projects/precice/precice-2.5.0/build "precice.tools.invalidcmd" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- Usage: Print XML reference : precice-tools xml Print DTD for XML config : precice-tools dtd Print Markdown reference : precice-tools md Print preCICE version : precice-tools version precice-tools --version Check configuration file : precice-tools check FILE [ PARTICIPANT [ COMMSIZE ] ] Test time = 0.01 sec ---------------------------------------------------------- Test Passed. "precice.tools.invalidcmd" end time: Aug 23 09:42 CEST "precice.tools.invalidcmd" time elapsed: 00:00:00 ---------------------------------------------------------- 32/39 Testing: precice.tools.version 32/39 Test: precice.tools.version Command: "/home/claudio/Projects/precice/precice-2.5.0/build/precice-tools" "version" Directory: /home/claudio/Projects/precice/precice-2.5.0/build "precice.tools.version" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- 2.5.0;no-info [git failed to run];PRECICE_MPICommunication=Y;PRECICE_PETScMapping=Y;PRECICE_PythonActions=Y;PRECICE_ENABLE_C=Y;PRECICE_ENABLE_FORTRAN=Y;CXX=GNU;CXXFLAGS= -g;LDFAGS= Test time = 0.01 sec ---------------------------------------------------------- Test Pass Reason: Required regular expression found. Regex=[2.5.0] "precice.tools.version" end time: Aug 23 09:42 CEST "precice.tools.version" time elapsed: 00:00:00 ---------------------------------------------------------- 33/39 Testing: precice.tools.versionopt 33/39 Test: precice.tools.versionopt Command: "/home/claudio/Projects/precice/precice-2.5.0/build/precice-tools" "--version" Directory: /home/claudio/Projects/precice/precice-2.5.0/build "precice.tools.versionopt" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- 2.5.0;no-info [git failed to run];PRECICE_MPICommunication=Y;PRECICE_PETScMapping=Y;PRECICE_PythonActions=Y;PRECICE_ENABLE_C=Y;PRECICE_ENABLE_FORTRAN=Y;CXX=GNU;CXXFLAGS= -g;LDFAGS= Test time = 0.01 sec ---------------------------------------------------------- Test Pass Reason: Required regular expression found. Regex=[2.5.0] "precice.tools.versionopt" end time: Aug 23 09:42 CEST "precice.tools.versionopt" time elapsed: 00:00:00 ---------------------------------------------------------- 34/39 Testing: precice.tools.markdown 34/39 Test: precice.tools.markdown Command: "/home/claudio/Projects/precice/precice-2.5.0/build/precice-tools" "md" Directory: /home/claudio/Projects/precice/precice-2.5.0/build "precice.tools.markdown" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- # precice-configuration Main tag containing preCICE configuration. **Example:** ```xml ... ... ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | sync-mode | boolean | sync-mode enabled additional inter- and intra-participant synchronizations | `0` | none | **Valid Subtags:** * [log](#log) `0..1` * [solver-interface](#solver-interface) `1` ## log Configures logging sinks based on Boost log. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | enabled | boolean | Enables logging | `1` | none | **Valid Subtags:** * [sink](#sink) `0..*` ### sink Contains the configuration of a single log sink, which allows fine grained control of what to log where. Available attributes in filter and format strings are `%Severity%`, `%ColorizedSeverity%`, `%File%`, `%Line%`, `%Function%`, `%Module%`, `%Rank%`, and `%Participant%` **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | filter | string | Boost Log Filter String | `(%Severity% > debug) and not ((%Severity% = info) and (%Rank% != 0))` | none | | format | string | Boost Log Format String | `(%Rank%) %TimeStamp(format="%H:%M:%S")% [%Module%]:%Line% in %Function%: %ColorizedSeverity%%Message%` | none | | output | string | Depends on the type of the sink. For streams, this can be stdout or stderr. For files, this is the filename. | `stdout` | none | | type | string | The type of sink. | `stream` | `stream`, `file` | | enabled | boolean | Enables the sink | `1` | none | ## solver-interface Configuration of simulation relevant features. **Example:** ```xml ... ... ... ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | dimensions | integer | Determines the spatial dimensionality of the configuration | `2` | `2`, `3` | | experimental | boolean | Enable experimental features. | `0` | none | **Valid Subtags:** * [mesh](#mesh) `1..*` * [participant](#participant) `1..*` * coupling-scheme * [serial-explicit](#coupling-schemeserial-explicit) `0..*` * [parallel-explicit](#coupling-schemeparallel-explicit) `0..*` * [serial-implicit](#coupling-schemeserial-implicit) `0..*` * [parallel-implicit](#coupling-schemeparallel-implicit) `0..*` * [multi](#coupling-schememulti) `0..*` * data * [scalar](#datascalar) `0..*` * [vector](#datavector) `0..*` * m2n * [sockets](#m2nsockets) `0..*` * [mpi-multiple-ports](#m2nmpi-multiple-ports) `0..*` * [mpi](#m2nmpi) `0..*` * [mpi-singleports](#m2nmpi-singleports) `0..*` ### data:scalar Defines a scalar data set to be assigned to meshes. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Unique name for the data set. | _none_ | none | ### data:vector Defines a vector data set to be assigned to meshes. The number of components of each data entry depends on the spatial dimensions set in tag . **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Unique name for the data set. | _none_ | none | ### mesh Surface mesh consisting of vertices and (optional) of edges and triangles (only in 3D). The vertices of a mesh can carry data, configured by tag . The mesh coordinates have to be defined by a participant (see tag ). **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Unique name for the mesh. | _none_ | none | | flip-normals | boolean | Deprecated. | `0` | none | **Valid Subtags:** * [use-data](#use-data) `0..*` #### use-data Assigns a before defined data set (see tag ) to the mesh. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data set. | _none_ | none | ### m2n:sockets Communication via Sockets. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | port | integer | Port number (16-bit unsigned integer) to be used for socket communication. The default is "0", what means that the OS will dynamically search for a free port (if at least one exists) and bind it automatically. | `0` | none | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen, and both solvers have to be started in the same directory. | `` | none | | from | string | First participant name involved in communication. For performance reasons, we recommend to use the participant with less ranks at the coupling interface as "from" in the m2n communication. | _none_ | none | | network | string | Interface name to be used for socket communication. Default is the canonical name of the loopback interface of your platform. Might be different on supercomputing systems, e.g. "ib0" for the InfiniBand on SuperMUC. | `lo` | none | | to | string | Second participant name involved in communication. | _none_ | none | | enforce-gather-scatter | boolean | Enforce the distributed communication to a gather-scatter scheme. Only recommended for trouble shooting. | `0` | none | | use-two-level-initialization | boolean | Use a two-level initialization scheme. Recommended for large parallel runs (>5000 MPI ranks). | `0` | none | ### m2n:mpi-multiple-ports Communication via MPI with startup in separated communication spaces, using multiple communicators. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen, and both solvers have to be started in the same directory. | `` | none | | from | string | First participant name involved in communication. For performance reasons, we recommend to use the participant with less ranks at the coupling interface as "from" in the m2n communication. | _none_ | none | | to | string | Second participant name involved in communication. | _none_ | none | | enforce-gather-scatter | boolean | Enforce the distributed communication to a gather-scatter scheme. Only recommended for trouble shooting. | `0` | none | | use-two-level-initialization | boolean | Use a two-level initialization scheme. Recommended for large parallel runs (>5000 MPI ranks). | `0` | none | ### m2n:mpi Communication via MPI with startup in separated communication spaces, using a single communicator **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen, and both solvers have to be started in the same directory. | `` | none | | from | string | First participant name involved in communication. For performance reasons, we recommend to use the participant with less ranks at the coupling interface as "from" in the m2n communication. | _none_ | none | | to | string | Second participant name involved in communication. | _none_ | none | | enforce-gather-scatter | boolean | Enforce the distributed communication to a gather-scatter scheme. Only recommended for trouble shooting. | `0` | none | | use-two-level-initialization | boolean | Use a two-level initialization scheme. Recommended for large parallel runs (>5000 MPI ranks). | `0` | none | ### m2n:mpi-singleports Communication via MPI with startup in separated communication spaces, using a single communicator **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen, and both solvers have to be started in the same directory. | `` | none | | from | string | First participant name involved in communication. For performance reasons, we recommend to use the participant with less ranks at the coupling interface as "from" in the m2n communication. | _none_ | none | | to | string | Second participant name involved in communication. | _none_ | none | | enforce-gather-scatter | boolean | Enforce the distributed communication to a gather-scatter scheme. Only recommended for trouble shooting. | `0` | none | | use-two-level-initialization | boolean | Use a two-level initialization scheme. Recommended for large parallel runs (>5000 MPI ranks). | `0` | none | ### participant Represents one solver using preCICE. At least two participants have to be defined. **Example:** ```xml ... ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the participant. Has to match the name given on construction of the precice::SolverInterface object used by the participant. | _none_ | none | **Valid Subtags:** * [write-data](#write-data) `0..*` * [read-data](#read-data) `0..*` * [watch-point](#watch-point) `0..*` * [watch-integral](#watch-integral) `0..*` * [use-mesh](#use-mesh) `0..*` * action * [multiply-by-area](#actionmultiply-by-area) `0..*` * [divide-by-area](#actiondivide-by-area) `0..*` * [scale-by-computed-dt-ratio](#actionscale-by-computed-dt-ratio) `0..*` * [scale-by-computed-dt-part-ratio](#actionscale-by-computed-dt-part-ratio) `0..*` * [scale-by-dt](#actionscale-by-dt) `0..*` * [summation](#actionsummation) `0..*` * [compute-curvature](#actioncompute-curvature) `0..*` * [recorder](#actionrecorder) `0..*` * [python](#actionpython) `0..*` * export * [vtk](#exportvtk) `0..*` * [vtu](#exportvtu) `0..*` * [vtp](#exportvtp) `0..*` * [csv](#exportcsv) `0..*` * intra-comm * [sockets](#intra-commsockets) `0..1` * [mpi](#intra-commmpi) `0..1` * [mpi-single](#intra-commmpi-single) `0..1` * mapping * [rbf-thin-plate-splines](#mappingrbf-thin-plate-splines) `0..*` * [rbf-multiquadrics](#mappingrbf-multiquadrics) `0..*` * [rbf-inverse-multiquadrics](#mappingrbf-inverse-multiquadrics) `0..*` * [rbf-volume-splines](#mappingrbf-volume-splines) `0..*` * [rbf-gaussian](#mappingrbf-gaussian) `0..*` * [rbf-compact-tps-c2](#mappingrbf-compact-tps-c2) `0..*` * [rbf-compact-polynomial-c0](#mappingrbf-compact-polynomial-c0) `0..*` * [rbf-compact-polynomial-c6](#mappingrbf-compact-polynomial-c6) `0..*` * [nearest-neighbor](#mappingnearest-neighbor) `0..*` * [nearest-projection](#mappingnearest-projection) `0..*` * [nearest-neighbor-gradient](#mappingnearest-neighbor-gradient) `0..*` * [linear-cell-interpolation](#mappinglinear-cell-interpolation) `0..*` * master * [sockets](#mastersockets) `0..1` * [mpi](#mastermpi) `0..1` * [mpi-single](#mastermpi-single) `0..1` * [sockets](#mastersockets-1) `0..1` * [mpi](#mastermpi-1) `0..1` * [mpi-single](#mastermpi-single-1) `0..1` #### write-data Sets data to be written by the participant to preCICE. Data is defined by using the tag. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Mesh the data belongs to. If data should be read/written to several meshes, this has to be specified separately for each mesh. | _none_ | none | | name | string | Name of the data. | _none_ | none | #### read-data Sets data to be read by the participant from preCICE. Data is defined by using the tag. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | waveform-order | integer | Interpolation order used by waveform iteration when reading data. | `0` | none | | mesh | string | Mesh the data belongs to. If data should be read/written to several meshes, this has to be specified separately for each mesh. | _none_ | none | | name | string | Name of the data. | _none_ | none | #### mapping:rbf-thin-plate-splines Global radial-basis-function mapping based on the thin plate splines. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:rbf-multiquadrics Global radial-basis-function mapping based on the multiquadrics RBF. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | shape-parameter | float | Specific shape parameter for RBF basis function. | _none_ | none | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:rbf-inverse-multiquadrics Global radial-basis-function mapping based on the inverse multiquadrics RBF. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | shape-parameter | float | Specific shape parameter for RBF basis function. | _none_ | none | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:rbf-volume-splines Global radial-basis-function mapping based on the volume-splines RBF. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:rbf-gaussian Local radial-basis-function mapping based on the Gaussian RBF using a cut-off threshold. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | shape-parameter | float | Specific shape parameter for RBF basis function. | `nan` | none | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | support-radius | float | Support radius of each RBF basis function (global choice). | `nan` | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:rbf-compact-tps-c2 Local radial-basis-function mapping based on the C2-polynomial RBF. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | support-radius | float | Support radius of each RBF basis function (global choice). | _none_ | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:rbf-compact-polynomial-c0 Local radial-basis-function mapping based on the C0-polynomial RBF. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | support-radius | float | Support radius of each RBF basis function (global choice). | _none_ | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:rbf-compact-polynomial-c6 Local radial-basis-function mapping based on the C6-polynomial RBF. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | solver-rtol | float | Solver relative tolerance for convergence | `1e-09` | none | | support-radius | float | Support radius of each RBF basis function (global choice). | _none_ | none | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | polynomial | string | Toggles use of the global polynomial | `separate` | `on`, `off`, `separate` | | preallocation | string | Sets kind of preallocation for PETSc RBF implementation | `tree` | `estimate`, `compute`, `off`, `save`, `tree` | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | | use-qr-decomposition | boolean | If set to true, QR decomposition is used to solve the RBF system | `0` | none | | x-dead | boolean | If set to true, the x axis will be ignored for the mapping | `0` | none | | y-dead | boolean | If set to true, the y axis will be ignored for the mapping | `0` | none | | z-dead | boolean | If set to true, the z axis will be ignored for the mapping | `0` | none | #### mapping:nearest-neighbor Nearest-neighbour mapping which uses a rstar-spacial index tree to index meshes and run nearest-neighbour queries. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | #### mapping:nearest-projection Nearest-projection mapping which uses a rstar-spacial index tree to index meshes and locate the nearest projections. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | #### mapping:nearest-neighbor-gradient Nearest-neighbor-gradient mapping which uses nearest-neighbor mapping with an additional linear approximation using gradient data. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | #### mapping:linear-cell-interpolation Linear cell interpolation mapping which uses a rstar-spacial index tree to index meshes and locate the nearest cell. Only supports 2D meshes. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | constraint | string | Use conservative to conserve the nodal sum of the data over the interface (needed e.g. for force mapping). Use consistent for normalized quantities such as temperature or pressure. Use scaled-consistent for normalized quantities where conservation of integral values is needed (e.g. velocities when the mass flow rate needs to be conserved). Mesh connectivity is required to use scaled-consistent. | _none_ | `conservative`, `consistent`, `scaled-consistent` | | direction | string | Write mappings map written data prior to communication, thus in the same participant who writes the data. Read mappings map received data after communication, thus in the same participant who reads the data. | _none_ | `write`, `read` | | from | string | The mesh to map the data from. | _none_ | none | | timing | string | This allows to defer the mapping of the data to advance or to a manual call to mapReadDataTo and mapWriteDataFrom. | `initial` | `initial`, `onadvance`, `ondemand` | | to | string | The mesh to map the data to. | _none_ | none | #### action:multiply-by-area Multiplies data values with mesh area associated to vertex holding the value. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [target-data](#target-data) `1` ##### target-data Data to read from and write to. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### action:divide-by-area Divides data values by mesh area associated to vertex holding the value. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [target-data](#target-data-1) `1` ##### target-data Data to read from and write to. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### action:scale-by-computed-dt-ratio Multiplies source data values by ratio of last time step size / time window size, and writes the result into target data. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [source-data](#source-data) `1` * [target-data](#target-data-1) `1` ##### source-data Single data to read from. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | ##### target-data Data to read from and write to. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### action:scale-by-computed-dt-part-ratio Multiplies source data values by ratio of computed time window part / time window size, and writes the result into target data. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [source-data](#source-data-1) `1` * [target-data](#target-data-1) `1` ##### source-data Single data to read from. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | ##### target-data Data to read from and write to. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### action:scale-by-dt Multiplies source data values by the time window size, and writes the result into target data. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [source-data](#source-data-1) `1` * [target-data](#target-data-1) `1` ##### source-data Single data to read from. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | ##### target-data Data to read from and write to. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### action:summation Sums up multiple source data values and writes the result into target data. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [source-data](#source-data-1) `1..*` * [target-data](#target-data-1) `1` ##### source-data Multiple data to read from. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | ##### target-data Data to read from and write to. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### action:compute-curvature Computes curvature values at mesh vertices. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [target-data](#target-data-1) `1` ##### target-data Data to read from and write to. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### action:recorder Records action invocations for testing purposes. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | #### action:python Calls Python script to execute action. See preCICE file "src/action/PythonAction.py" for an overview. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Determines mesh used in action. | _none_ | none | | timing | string | Determines when (relative to advancing the coupling scheme) the action is executed. | _none_ | `regular-prior`, `regular-post`, `on-exchange-prior`, `on-exchange-post`, `on-time-window-complete-post`, `write-mapping-prior`, `write-mapping-post`, `read-mapping-prior`, `read-mapping-post` | **Valid Subtags:** * [path](#path) `0..1` * [module](#module) `1` * [source-data](#source-data-1) `0..1` * [target-data](#target-data-1) `0..1` ##### path Directory path to Python module, i.e. script file. If it doesn't occur, the current path is used **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | The path to the directory of the module. | `` | none | ##### module Name of Python module, i.e. Python script file without file ending. The module name has to differ from existing (library) modules, otherwise, the existing module will be loaded instead of the user script. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | ##### source-data Source data to be read is handed to the Python module. Can be omitted, if only a target data is needed. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | ##### target-data Target data to be read and written to is handed to the Python module. Can be omitted, if only source data is needed. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the data. | _none_ | none | #### export:vtk Exports meshes to VTK legacy format files. Parallel participants will use the VTU exporter instead. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | every-n-time-windows | integer | preCICE does an export every X time windows. Choose -1 for no exports. | `1` | none | | directory | string | Directory to export the files to. | `` | none | | every-iteration | boolean | Exports in every coupling (sub)iteration. For debug purposes. | `0` | none | | normals | boolean | Deprecated | `0` | none | #### export:vtu Exports meshes to VTU files in serial or PVTU files with VTU piece files in parallel. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | every-n-time-windows | integer | preCICE does an export every X time windows. Choose -1 for no exports. | `1` | none | | directory | string | Directory to export the files to. | `` | none | | every-iteration | boolean | Exports in every coupling (sub)iteration. For debug purposes. | `0` | none | | normals | boolean | Deprecated | `0` | none | #### export:vtp Exports meshes to VTP files in serial or PVTP files with VTP piece files in parallel. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | every-n-time-windows | integer | preCICE does an export every X time windows. Choose -1 for no exports. | `1` | none | | directory | string | Directory to export the files to. | `` | none | | every-iteration | boolean | Exports in every coupling (sub)iteration. For debug purposes. | `0` | none | | normals | boolean | Deprecated | `0` | none | #### export:csv Exports vertex coordinates and data to CSV files. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | every-n-time-windows | integer | preCICE does an export every X time windows. Choose -1 for no exports. | `1` | none | | directory | string | Directory to export the files to. | `` | none | | every-iteration | boolean | Exports in every coupling (sub)iteration. For debug purposes. | `0` | none | | normals | boolean | Deprecated | `0` | none | #### watch-point A watch point can be used to follow the transient changes of data and mesh vertex coordinates at a given point **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Mesh to be watched. | _none_ | none | | name | string | Name of the watch point. Is taken in combination with the participant name to construct the filename the watch point data is written to. | _none_ | none | | coordinate | vector | The coordinates of the watch point. If the watch point is not put exactly on the mesh to observe, the closest projection of the point onto the mesh is considered instead, and values/coordinates are interpolated linearly to that point. | _none_ | none | #### watch-integral A watch integral can be used to follow the transient change of integral data and surface area for a given coupling mesh. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | Mesh to be watched. | _none_ | none | | name | string | Name of the watch integral. Is taken in combination with the participant name to construct the filename the watch integral data is written to. | _none_ | none | | scale-with-connectivity | boolean | Whether the vertex data is scaled with the element area before summing up or not. In 2D, vertex data is scaled with the average length of neighboring edges. In 3D, vertex data is scaled with the average surface of neighboring triangles. If false, vertex data is directly summed up. | _none_ | none | #### use-mesh Makes a mesh (see tag available to a participant. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | safety-factor | float | If a mesh is received from another partipant (see tag ), it needs to bedecomposed at the receiving participant. To speed up this process, a geometric filter (see tag ), i.e. filtering by bounding boxes around the local mesh, can be used. This safety factor defines by which factor this local information is increased. An example: 0.5 means that the bounding box is 150% of its original size. | `0.5` | none | | from | string | If a created mesh should be used by another solver, this attribute has to specify the creating participant's name. The creator has to use the attribute "provide" to signal he is providing the mesh geometry. | `` | none | | geometric-filter | string | If a mesh is received from another partipant (see tag ), it needs to bedecomposed at the receiving participant. To speed up this process, a geometric filter, i.e. filtering by bounding boxes around the local mesh, can be used. Two different variants are implemented: a filter "on-master" strategy, which is beneficial for a huge mesh and a low number of processors, and a filter "on-slaves" strategy, which performs better for a very high number of processors. Both result in the same distribution (if the safety factor is sufficiently large). "on-master" is not supported if you use two-level initialization. For very asymmetric cases, the filter can also be switched off completely ("no-filter"). | `on-secondary-ranks` | `on-master`, `on-slaves`, `no-filter`, `on-primary-rank`, `on-secondary-ranks` | | name | string | Name of the mesh. | _none_ | none | | direct-access | boolean | If a mesh is received from another partipant (see tag ), it needs to bedecomposed at the receiving participant. In case a mapping is defined, the mesh is decomposed according to the local provided mesh associated to the mapping. In case no mapping has been defined (you want to access the mesh and related data direct), there is no obvious way on how to decompose the mesh, since no mesh needs to be provided by the participant. For this purpose, bounding boxes can be defined (see API function "setMeshAccessRegion") and used by selecting the option direct-access="true". | `0` | none | | provide | boolean | If this attribute is set to "on", the participant has to create the mesh geometry before initializing preCICE. | `0` | none | #### master:sockets A solver in parallel needs a communication between its ranks. By default, the participant's MPI_COM_WORLD is reused.Use this tag to use TCP/IP sockets instead. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | port | integer | Port number (16-bit unsigned integer) to be used for socket communication. The default is "0", what means that OS will dynamically search for a free port (if at least one exists) and bind it automatically. | `0` | none | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen. | `` | none | | network | string | Interface name to be used for socket communication. Default is the canonical name of the loopback interface of your platform. Might be different on supercomputing systems, e.g. "ib0" for the InfiniBand on SuperMUC. | `lo` | none | #### master:mpi A solver in parallel needs a communication between its ranks. By default, the participant's MPI_COM_WORLD is reused.Use this tag to use MPI with separated communication spaces instead instead. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen. | `` | none | #### master:mpi-single A solver in parallel needs a communication between its ranks. By default (which is this option), the participant's MPI_COM_WORLD is reused.This tag is only used to ensure backwards compatibility. **Example:** ```xml ``` #### master:sockets A solver in parallel needs a communication between its ranks. By default, the participant's MPI_COM_WORLD is reused.Use this tag to use TCP/IP sockets instead. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | port | integer | Port number (16-bit unsigned integer) to be used for socket communication. The default is "0", what means that OS will dynamically search for a free port (if at least one exists) and bind it automatically. | `0` | none | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen. | `` | none | | network | string | Interface name to be used for socket communication. Default is the canonical name of the loopback interface of your platform. Might be different on supercomputing systems, e.g. "ib0" for the InfiniBand on SuperMUC. | `lo` | none | #### master:mpi A solver in parallel needs a communication between its ranks. By default, the participant's MPI_COM_WORLD is reused.Use this tag to use MPI with separated communication spaces instead instead. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen. | `` | none | #### master:mpi-single A solver in parallel needs a communication between its ranks. By default (which is this option), the participant's MPI_COM_WORLD is reused.This tag is only used to ensure backwards compatibility. **Example:** ```xml ``` #### intra-comm:sockets A solver in parallel needs a communication between its ranks. By default, the participant's MPI_COM_WORLD is reused.Use this tag to use TCP/IP sockets instead. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | port | integer | Port number (16-bit unsigned integer) to be used for socket communication. The default is "0", what means that OS will dynamically search for a free port (if at least one exists) and bind it automatically. | `0` | none | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen. | `` | none | | network | string | Interface name to be used for socket communication. Default is the canonical name of the loopback interface of your platform. Might be different on supercomputing systems, e.g. "ib0" for the InfiniBand on SuperMUC. | `lo` | none | #### intra-comm:mpi A solver in parallel needs a communication between its ranks. By default, the participant's MPI_COM_WORLD is reused.Use this tag to use MPI with separated communication spaces instead instead. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | exchange-directory | string | Directory where connection information is exchanged. By default, the directory of startup is chosen. | `` | none | #### intra-comm:mpi-single A solver in parallel needs a communication between its ranks. By default (which is this option), the participant's MPI_COM_WORLD is reused.This tag is only used to ensure backwards compatibility. **Example:** ```xml ``` ### coupling-scheme:serial-explicit Explicit coupling scheme according to conventional serial staggered procedure (CSS). **Example:** ```xml ``` **Valid Subtags:** * [max-time](#max-time) `0..1` * [max-time-windows](#max-time-windows) `0..1` * [time-window-size](#time-window-size) `1` * [participants](#participants) `1` * [exchange](#exchange) `1..*` #### max-time Defined the end of the simulation as total time. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The value of the maximum simulation time. | _none_ | none | #### max-time-windows Defined the end of the simulation as a total count of time windows. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum count of time windows. | _none_ | none | #### time-window-size Defines the size of the time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The maximum time window size. | `-1` | none | | valid-digits | integer | Precision to use when checking for end of time windows used this many digits. \\(\phi = 10^{-validDigits}\\) | `10` | none | | method | string | The method used to determine the time window size. Use `fixed` to fix the time window size for the participants. | `fixed` | `fixed`, `first-participant` | #### participants Defines the participants of the coupling scheme. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | first | string | First participant to run the solver. | _none_ | none | | second | string | Second participant to run the solver. | _none_ | none | #### exchange Defines the flow of data between meshes of participants. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | data | string | The data to exchange. | _none_ | none | | from | string | The participant sending the data. | _none_ | none | | mesh | string | The mesh which uses the data. | _none_ | none | | to | string | The participant receiving the data. | _none_ | none | | initialize | boolean | Should this data be initialized during initializeData? | `0` | none | ### coupling-scheme:parallel-explicit Explicit coupling scheme according to conventional parallel staggered procedure (CPS). **Example:** ```xml ``` **Valid Subtags:** * [max-time](#max-time-1) `0..1` * [max-time-windows](#max-time-windows-1) `0..1` * [time-window-size](#time-window-size-1) `1` * [participants](#participants-1) `1` * [exchange](#exchange-1) `1..*` #### max-time Defined the end of the simulation as total time. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The value of the maximum simulation time. | _none_ | none | #### max-time-windows Defined the end of the simulation as a total count of time windows. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum count of time windows. | _none_ | none | #### time-window-size Defines the size of the time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The maximum time window size. | `-1` | none | | valid-digits | integer | Precision to use when checking for end of time windows used this many digits. \\(\phi = 10^{-validDigits}\\) | `10` | none | | method | string | The method used to determine the time window size. Use `fixed` to fix the time window size for the participants. | `fixed` | `fixed` | #### participants Defines the participants of the coupling scheme. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | first | string | First participant to run the solver. | _none_ | none | | second | string | Second participant to run the solver. | _none_ | none | #### exchange Defines the flow of data between meshes of participants. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | data | string | The data to exchange. | _none_ | none | | from | string | The participant sending the data. | _none_ | none | | mesh | string | The mesh which uses the data. | _none_ | none | | to | string | The participant receiving the data. | _none_ | none | | initialize | boolean | Should this data be initialized during initializeData? | `0` | none | ### coupling-scheme:serial-implicit Implicit coupling scheme according to block Gauss-Seidel iterations (S-System). Improved implicit iterations are achieved by using a acceleration (recommended!). **Example:** ```xml ... ``` **Valid Subtags:** * [max-time](#max-time-1) `0..1` * [max-time-windows](#max-time-windows-1) `0..1` * [time-window-size](#time-window-size-1) `1` * [participants](#participants-1) `1` * [exchange](#exchange-1) `1..*` * [absolute-convergence-measure](#absolute-convergence-measure) `0..*` * [relative-convergence-measure](#relative-convergence-measure) `0..*` * [residual-relative-convergence-measure](#residual-relative-convergence-measure) `0..*` * [min-iteration-convergence-measure](#min-iteration-convergence-measure) `0..*` * [max-iterations](#max-iterations) `1` * [extrapolation-order](#extrapolation-order) `0..1` * acceleration * [constant](#accelerationconstant) `0..1` * [aitken](#accelerationaitken) `0..1` * [IQN-ILS](#accelerationiqn-ils) `0..1` * [IQN-IMVJ](#accelerationiqn-imvj) `0..1` * [broyden](#accelerationbroyden) `0..1` #### max-time Defined the end of the simulation as total time. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The value of the maximum simulation time. | _none_ | none | #### max-time-windows Defined the end of the simulation as a total count of time windows. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum count of time windows. | _none_ | none | #### time-window-size Defines the size of the time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The maximum time window size. | `-1` | none | | valid-digits | integer | Precision to use when checking for end of time windows used this many digits. \\(\phi = 10^{-validDigits}\\) | `10` | none | | method | string | The method used to determine the time window size. Use `fixed` to fix the time window size for the participants. | `fixed` | `fixed`, `first-participant` | #### participants Defines the participants of the coupling scheme. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | first | string | First participant to run the solver. | _none_ | none | | second | string | Second participant to run the solver. | _none_ | none | #### exchange Defines the flow of data between meshes of participants. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | data | string | The data to exchange. | _none_ | none | | from | string | The participant sending the data. | _none_ | none | | mesh | string | The mesh which uses the data. | _none_ | none | | to | string | The participant receiving the data. | _none_ | none | | initialize | boolean | Should this data be initialized during initializeData? | `0` | none | #### acceleration:constant Accelerates coupling data with constant underrelaxation. **Example:** ```xml ``` **Valid Subtags:** * [relaxation](#relaxation) `1` ##### relaxation **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Constant relaxation factor. | _none_ | none | #### acceleration:aitken Accelerates coupling data with dynamic Aitken under-relaxation. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation) `1` * [data](#data) `1..*` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | #### acceleration:IQN-ILS Accelerates coupling data with the interface quasi-Newton inverse least-squares method. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [max-used-iterations](#max-used-iterations) `1` * [time-windows-reused](#time-windows-reused) `1` * [data](#data-1) `1..*` * [filter](#filter) `0..1` * [preconditioner](#preconditioner) `0..1` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | | enforce | boolean | Enforce initial relaxation in every time window. | `0` | none | ##### max-used-iterations Maximum number of columns used in low-rank approximation of Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### time-windows-reused Number of past time windows from which columns are used to approximate Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of time windows. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | ##### filter Type of filtering technique that is used to maintain good conditioning in the least-squares system. Possible filters: - `QR1-filter`: updateQR-dec with (relative) test \\(R(i,i) < \epsilon *\lVert R\rVert_F\\) - `QR1_absolute-filter`: updateQR-dec with (absolute) test \\(R(i, i) < \epsilon\\) - `QR2-filter`: en-block QR-dec with test \\(\lVert v_\text{orth} \rVert_2 < \epsilon * \lVert v \rVert_2\\) Please note that a QR1 is based on Given's rotations whereas QR2 uses modified Gram-Schmidt. This can give different results even when no columns are filtered out. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit eps of the filter. | `1e-16` | none | | type | string | Type of the filter. | _none_ | `QR1`, `QR1-absolute`, `QR2` | ##### preconditioner To improve the performance of a parallel or a multi coupling schemes a preconditioner can be applied. A constant preconditioner scales every acceleration data by a constant value, which you can define as an attribute of data. A value preconditioner scales every acceleration data by the norm of the data in the previous time window. A residual preconditioner scales every acceleration data by the current residual. A residual-sum preconditioner scales every acceleration data by the sum of the residuals from the current time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | freeze-after | integer | After the given number of time windows, the preconditioner weights are frozen and the preconditioner acts like a constant preconditioner. | `-1` | none | | type | string | The type of the preconditioner. | _none_ | `constant`, `value`, `residual`, `residual-sum` | #### acceleration:IQN-IMVJ Accelerates coupling data with the interface quasi-Newton inverse multi-vector Jacobian method. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | always-build-jacobian | boolean | If set to true, the IMVJ will set up the Jacobian matrix in each coupling iteration, which is inefficient. If set to false (or not set) the Jacobian is only build in the last iteration and the updates are computed using (relatively) cheap MATVEC products. | `0` | none | **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [imvj-restart-mode](#imvj-restart-mode) `0..1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` * [filter](#filter-1) `0..1` * [preconditioner](#preconditioner-1) `0..1` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | | enforce | boolean | Enforce initial relaxation in every time window. | `0` | none | ##### imvj-restart-mode Type of IMVJ restart mode that is used: - `no-restart`: IMVJ runs in normal mode with explicit representation of Jacobian - `RS-ZERO`: IMVJ runs in restart mode. After M time windows all Jacobain information is dropped, restart with no information - `RS-LS`: IMVJ runs in restart mode. After M time windows a IQN-LS like approximation for the initial guess of the Jacobian is computed. - `RS-SVD`: IMVJ runs in restart mode. After M time windows a truncated SVD of the Jacobian is updated. - `RS-SLIDE`: IMVJ runs in sliding window restart mode. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | truncation-threshold | float | If IMVJ restart-mode=RS-SVD, the truncation threshold for the updated SVD can be set. | `0.0001` | none | | chunk-size | integer | Specifies the number of time windows M after which the IMVJ restarts, if run in restart-mode. Default value is M=8. | `8` | none | | reused-time-windows-at-restart | integer | If IMVJ restart-mode=RS-LS, the number of reused time windows at restart can be specified. | `8` | none | | type | string | Type of the restart mode. | `RS-SVD` | `no-restart`, `RS-0`, `RS-LS`, `RS-SVD`, `RS-SLIDE` | ##### max-used-iterations Maximum number of columns used in low-rank approximation of Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### time-windows-reused Number of past time windows from which columns are used to approximate Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | ##### filter Type of filtering technique that is used to maintain good conditioning in the least-squares system. Possible filters: - `QR1-filter`: updateQR-dec with (relative) test \\(R(i,i) < \epsilon *\lVert R\rVert_F\\) - `QR1_absolute-filter`: updateQR-dec with (absolute) test \\(R(i, i) < \epsilon\\) - `QR2-filter`: en-block QR-dec with test \\(\lVert v_\text{orth} \rVert_2 < \epsilon * \lVert v \rVert_2\\) Please note that a QR1 is based on Given's rotations whereas QR2 uses modified Gram-Schmidt. This can give different results even when no columns are filtered out. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit eps of the filter. | `1e-16` | none | | type | string | Type of the filter. | _none_ | `QR1`, `QR1-absolute`, `QR2` | ##### preconditioner To improve the performance of a parallel or a multi coupling schemes a preconditioner can be applied. A constant preconditioner scales every acceleration data by a constant value, which you can define as an attribute of data. - A value preconditioner scales every acceleration data by the norm of the data in the previous time window. - A residual preconditioner scales every acceleration data by the current residual. - A residual-sum preconditioner scales every acceleration data by the sum of the residuals from the current time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | freeze-after | integer | After the given number of time windows, the preconditioner weights are frozen and the preconditioner acts like a constant preconditioner. | `-1` | none | | type | string | Type of the preconditioner. | _none_ | `constant`, `value`, `residual`, `residual-sum` | #### acceleration:broyden Accelerates coupling data with the (single-vector) Broyden method. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` ##### initial-relaxation **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | | _none_ | none | | enforce | boolean | | `0` | none | ##### max-used-iterations **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | | _none_ | none | ##### time-windows-reused **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | | _none_ | none | ##### data **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | | _none_ | none | | name | string | | _none_ | none | #### absolute-convergence-measure Absolute convergence criterion based on the two-norm difference of data values between iterations. \$$\left\lVert H(x^k) - x^k \right\rVert_2 < \text{limit}\$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \((0, 1]\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### relative-convergence-measure Relative convergence criterion based on the relative two-norm difference of data values between iterations. \$$\frac{\left\lVert H(x^k) - x^k \right\rVert_2}{\left\lVert H(x^k) \right\rVert_2} < \text{limit} \$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \\((0, 1]\\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### residual-relative-convergence-measure Residual relative convergence criterion based on the relative two-norm differences of data values between iterations. \$$\frac{\left\lVert H(x^k) - x^k \right\rVert_2}{\left\lVert H(x^{k-1}) - x^{k-1} \right\rVert_2} < \text{limit}\$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \((0, 1]\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### min-iteration-convergence-measure Convergence criterion used to ensure a miminimal amount of iterations. Specifying a mesh and data is required for technical reasons and does not influence the measure. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | min-iterations | integer | The minimal amount of iterations. | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### max-iterations Allows to specify a maximum amount of iterations per time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum value of iterations. | _none_ | none | #### extrapolation-order Sets order of predictor of interface values for first participant. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The extrapolation order to use. | _none_ | none | ### coupling-scheme:parallel-implicit Parallel Implicit coupling scheme according to block Jacobi iterations (V-System). Improved implicit iterations are achieved by using a acceleration (recommended!). **Example:** ```xml ... ``` **Valid Subtags:** * [max-time](#max-time-1) `0..1` * [max-time-windows](#max-time-windows-1) `0..1` * [time-window-size](#time-window-size-1) `1` * [participants](#participants-1) `1` * [exchange](#exchange-1) `1..*` * [absolute-convergence-measure](#absolute-convergence-measure-1) `0..*` * [relative-convergence-measure](#relative-convergence-measure-1) `0..*` * [residual-relative-convergence-measure](#residual-relative-convergence-measure-1) `0..*` * [min-iteration-convergence-measure](#min-iteration-convergence-measure-1) `0..*` * [max-iterations](#max-iterations-1) `1` * [extrapolation-order](#extrapolation-order-1) `0..1` * acceleration * [constant](#accelerationconstant-1) `0..1` * [aitken](#accelerationaitken-1) `0..1` * [IQN-ILS](#accelerationiqn-ils-1) `0..1` * [IQN-IMVJ](#accelerationiqn-imvj-1) `0..1` * [broyden](#accelerationbroyden-1) `0..1` #### max-time Defined the end of the simulation as total time. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The value of the maximum simulation time. | _none_ | none | #### max-time-windows Defined the end of the simulation as a total count of time windows. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum count of time windows. | _none_ | none | #### time-window-size Defines the size of the time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The maximum time window size. | `-1` | none | | valid-digits | integer | Precision to use when checking for end of time windows used this many digits. \\(\phi = 10^{-validDigits}\\) | `10` | none | | method | string | The method used to determine the time window size. Use `fixed` to fix the time window size for the participants. | `fixed` | `fixed` | #### participants Defines the participants of the coupling scheme. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | first | string | First participant to run the solver. | _none_ | none | | second | string | Second participant to run the solver. | _none_ | none | #### exchange Defines the flow of data between meshes of participants. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | data | string | The data to exchange. | _none_ | none | | from | string | The participant sending the data. | _none_ | none | | mesh | string | The mesh which uses the data. | _none_ | none | | to | string | The participant receiving the data. | _none_ | none | | initialize | boolean | Should this data be initialized during initializeData? | `0` | none | #### acceleration:constant Accelerates coupling data with constant underrelaxation. **Example:** ```xml ``` **Valid Subtags:** * [relaxation](#relaxation-1) `1` ##### relaxation **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Constant relaxation factor. | _none_ | none | #### acceleration:aitken Accelerates coupling data with dynamic Aitken under-relaxation. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [data](#data-1) `1..*` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | #### acceleration:IQN-ILS Accelerates coupling data with the interface quasi-Newton inverse least-squares method. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` * [filter](#filter-1) `0..1` * [preconditioner](#preconditioner-1) `0..1` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | | enforce | boolean | Enforce initial relaxation in every time window. | `0` | none | ##### max-used-iterations Maximum number of columns used in low-rank approximation of Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### time-windows-reused Number of past time windows from which columns are used to approximate Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of time windows. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | ##### filter Type of filtering technique that is used to maintain good conditioning in the least-squares system. Possible filters: - `QR1-filter`: updateQR-dec with (relative) test \\(R(i,i) < \epsilon *\lVert R\rVert_F\\) - `QR1_absolute-filter`: updateQR-dec with (absolute) test \\(R(i, i) < \epsilon\\) - `QR2-filter`: en-block QR-dec with test \\(\lVert v_\text{orth} \rVert_2 < \epsilon * \lVert v \rVert_2\\) Please note that a QR1 is based on Given's rotations whereas QR2 uses modified Gram-Schmidt. This can give different results even when no columns are filtered out. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit eps of the filter. | `1e-16` | none | | type | string | Type of the filter. | _none_ | `QR1`, `QR1-absolute`, `QR2` | ##### preconditioner To improve the performance of a parallel or a multi coupling schemes a preconditioner can be applied. A constant preconditioner scales every acceleration data by a constant value, which you can define as an attribute of data. A value preconditioner scales every acceleration data by the norm of the data in the previous time window. A residual preconditioner scales every acceleration data by the current residual. A residual-sum preconditioner scales every acceleration data by the sum of the residuals from the current time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | freeze-after | integer | After the given number of time windows, the preconditioner weights are frozen and the preconditioner acts like a constant preconditioner. | `-1` | none | | type | string | The type of the preconditioner. | _none_ | `constant`, `value`, `residual`, `residual-sum` | #### acceleration:IQN-IMVJ Accelerates coupling data with the interface quasi-Newton inverse multi-vector Jacobian method. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | always-build-jacobian | boolean | If set to true, the IMVJ will set up the Jacobian matrix in each coupling iteration, which is inefficient. If set to false (or not set) the Jacobian is only build in the last iteration and the updates are computed using (relatively) cheap MATVEC products. | `0` | none | **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [imvj-restart-mode](#imvj-restart-mode-1) `0..1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` * [filter](#filter-1) `0..1` * [preconditioner](#preconditioner-1) `0..1` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | | enforce | boolean | Enforce initial relaxation in every time window. | `0` | none | ##### imvj-restart-mode Type of IMVJ restart mode that is used: - `no-restart`: IMVJ runs in normal mode with explicit representation of Jacobian - `RS-ZERO`: IMVJ runs in restart mode. After M time windows all Jacobain information is dropped, restart with no information - `RS-LS`: IMVJ runs in restart mode. After M time windows a IQN-LS like approximation for the initial guess of the Jacobian is computed. - `RS-SVD`: IMVJ runs in restart mode. After M time windows a truncated SVD of the Jacobian is updated. - `RS-SLIDE`: IMVJ runs in sliding window restart mode. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | truncation-threshold | float | If IMVJ restart-mode=RS-SVD, the truncation threshold for the updated SVD can be set. | `0.0001` | none | | chunk-size | integer | Specifies the number of time windows M after which the IMVJ restarts, if run in restart-mode. Default value is M=8. | `8` | none | | reused-time-windows-at-restart | integer | If IMVJ restart-mode=RS-LS, the number of reused time windows at restart can be specified. | `8` | none | | type | string | Type of the restart mode. | `RS-SVD` | `no-restart`, `RS-0`, `RS-LS`, `RS-SVD`, `RS-SLIDE` | ##### max-used-iterations Maximum number of columns used in low-rank approximation of Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### time-windows-reused Number of past time windows from which columns are used to approximate Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | ##### filter Type of filtering technique that is used to maintain good conditioning in the least-squares system. Possible filters: - `QR1-filter`: updateQR-dec with (relative) test \\(R(i,i) < \epsilon *\lVert R\rVert_F\\) - `QR1_absolute-filter`: updateQR-dec with (absolute) test \\(R(i, i) < \epsilon\\) - `QR2-filter`: en-block QR-dec with test \\(\lVert v_\text{orth} \rVert_2 < \epsilon * \lVert v \rVert_2\\) Please note that a QR1 is based on Given's rotations whereas QR2 uses modified Gram-Schmidt. This can give different results even when no columns are filtered out. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit eps of the filter. | `1e-16` | none | | type | string | Type of the filter. | _none_ | `QR1`, `QR1-absolute`, `QR2` | ##### preconditioner To improve the performance of a parallel or a multi coupling schemes a preconditioner can be applied. A constant preconditioner scales every acceleration data by a constant value, which you can define as an attribute of data. - A value preconditioner scales every acceleration data by the norm of the data in the previous time window. - A residual preconditioner scales every acceleration data by the current residual. - A residual-sum preconditioner scales every acceleration data by the sum of the residuals from the current time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | freeze-after | integer | After the given number of time windows, the preconditioner weights are frozen and the preconditioner acts like a constant preconditioner. | `-1` | none | | type | string | Type of the preconditioner. | _none_ | `constant`, `value`, `residual`, `residual-sum` | #### acceleration:broyden Accelerates coupling data with the (single-vector) Broyden method. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` ##### initial-relaxation **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | | _none_ | none | | enforce | boolean | | `0` | none | ##### max-used-iterations **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | | _none_ | none | ##### time-windows-reused **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | | _none_ | none | ##### data **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | | _none_ | none | | name | string | | _none_ | none | #### absolute-convergence-measure Absolute convergence criterion based on the two-norm difference of data values between iterations. \$$\left\lVert H(x^k) - x^k \right\rVert_2 < \text{limit}\$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \((0, 1]\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### relative-convergence-measure Relative convergence criterion based on the relative two-norm difference of data values between iterations. \$$\frac{\left\lVert H(x^k) - x^k \right\rVert_2}{\left\lVert H(x^k) \right\rVert_2} < \text{limit} \$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \\((0, 1]\\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### residual-relative-convergence-measure Residual relative convergence criterion based on the relative two-norm differences of data values between iterations. \$$\frac{\left\lVert H(x^k) - x^k \right\rVert_2}{\left\lVert H(x^{k-1}) - x^{k-1} \right\rVert_2} < \text{limit}\$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \((0, 1]\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### min-iteration-convergence-measure Convergence criterion used to ensure a miminimal amount of iterations. Specifying a mesh and data is required for technical reasons and does not influence the measure. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | min-iterations | integer | The minimal amount of iterations. | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### max-iterations Allows to specify a maximum amount of iterations per time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum value of iterations. | _none_ | none | #### extrapolation-order Sets order of predictor of interface values for first participant. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The extrapolation order to use. | _none_ | none | ### coupling-scheme:multi Multi coupling scheme according to block Jacobi iterations. Improved implicit iterations are achieved by using a acceleration (recommended!). **Example:** ```xml ... ``` **Valid Subtags:** * [max-time](#max-time-1) `0..1` * [max-time-windows](#max-time-windows-1) `0..1` * [time-window-size](#time-window-size-1) `1` * [participant](#participant-1) `1..*` * [exchange](#exchange-1) `1..*` * [absolute-convergence-measure](#absolute-convergence-measure-1) `0..*` * [relative-convergence-measure](#relative-convergence-measure-1) `0..*` * [residual-relative-convergence-measure](#residual-relative-convergence-measure-1) `0..*` * [min-iteration-convergence-measure](#min-iteration-convergence-measure-1) `0..*` * [max-iterations](#max-iterations-1) `1` * [extrapolation-order](#extrapolation-order-1) `0..1` * acceleration * [constant](#accelerationconstant-1) `0..1` * [aitken](#accelerationaitken-1) `0..1` * [IQN-ILS](#accelerationiqn-ils-1) `0..1` * [IQN-IMVJ](#accelerationiqn-imvj-1) `0..1` * [broyden](#accelerationbroyden-1) `0..1` #### max-time Defined the end of the simulation as total time. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The value of the maximum simulation time. | _none_ | none | #### max-time-windows Defined the end of the simulation as a total count of time windows. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum count of time windows. | _none_ | none | #### time-window-size Defines the size of the time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | The maximum time window size. | `-1` | none | | valid-digits | integer | Precision to use when checking for end of time windows used this many digits. \\(\phi = 10^{-validDigits}\\) | `10` | none | | method | string | The method used to determine the time window size. Use `fixed` to fix the time window size for the participants. | `fixed` | `fixed` | #### participant **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | name | string | Name of the participant. | _none_ | none | | control | boolean | Does this participant control the coupling? | `0` | none | #### exchange Defines the flow of data between meshes of participants. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | data | string | The data to exchange. | _none_ | none | | from | string | The participant sending the data. | _none_ | none | | mesh | string | The mesh which uses the data. | _none_ | none | | to | string | The participant receiving the data. | _none_ | none | | initialize | boolean | Should this data be initialized during initializeData? | `0` | none | #### acceleration:constant Accelerates coupling data with constant underrelaxation. **Example:** ```xml ``` **Valid Subtags:** * [relaxation](#relaxation-1) `1` ##### relaxation **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Constant relaxation factor. | _none_ | none | #### acceleration:aitken Accelerates coupling data with dynamic Aitken under-relaxation. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [data](#data-1) `1..*` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | #### acceleration:IQN-ILS Accelerates coupling data with the interface quasi-Newton inverse least-squares method. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` * [filter](#filter-1) `0..1` * [preconditioner](#preconditioner-1) `0..1` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | | enforce | boolean | Enforce initial relaxation in every time window. | `0` | none | ##### max-used-iterations Maximum number of columns used in low-rank approximation of Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### time-windows-reused Number of past time windows from which columns are used to approximate Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of time windows. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | ##### filter Type of filtering technique that is used to maintain good conditioning in the least-squares system. Possible filters: - `QR1-filter`: updateQR-dec with (relative) test \\(R(i,i) < \epsilon *\lVert R\rVert_F\\) - `QR1_absolute-filter`: updateQR-dec with (absolute) test \\(R(i, i) < \epsilon\\) - `QR2-filter`: en-block QR-dec with test \\(\lVert v_\text{orth} \rVert_2 < \epsilon * \lVert v \rVert_2\\) Please note that a QR1 is based on Given's rotations whereas QR2 uses modified Gram-Schmidt. This can give different results even when no columns are filtered out. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit eps of the filter. | `1e-16` | none | | type | string | Type of the filter. | _none_ | `QR1`, `QR1-absolute`, `QR2` | ##### preconditioner To improve the performance of a parallel or a multi coupling schemes a preconditioner can be applied. A constant preconditioner scales every acceleration data by a constant value, which you can define as an attribute of data. A value preconditioner scales every acceleration data by the norm of the data in the previous time window. A residual preconditioner scales every acceleration data by the current residual. A residual-sum preconditioner scales every acceleration data by the sum of the residuals from the current time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | freeze-after | integer | After the given number of time windows, the preconditioner weights are frozen and the preconditioner acts like a constant preconditioner. | `-1` | none | | type | string | The type of the preconditioner. | _none_ | `constant`, `value`, `residual`, `residual-sum` | #### acceleration:IQN-IMVJ Accelerates coupling data with the interface quasi-Newton inverse multi-vector Jacobian method. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | always-build-jacobian | boolean | If set to true, the IMVJ will set up the Jacobian matrix in each coupling iteration, which is inefficient. If set to false (or not set) the Jacobian is only build in the last iteration and the updates are computed using (relatively) cheap MATVEC products. | `0` | none | **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [imvj-restart-mode](#imvj-restart-mode-1) `0..1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` * [filter](#filter-1) `0..1` * [preconditioner](#preconditioner-1) `0..1` ##### initial-relaxation Initial relaxation factor. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | Initial relaxation factor. | _none_ | none | | enforce | boolean | Enforce initial relaxation in every time window. | `0` | none | ##### imvj-restart-mode Type of IMVJ restart mode that is used: - `no-restart`: IMVJ runs in normal mode with explicit representation of Jacobian - `RS-ZERO`: IMVJ runs in restart mode. After M time windows all Jacobain information is dropped, restart with no information - `RS-LS`: IMVJ runs in restart mode. After M time windows a IQN-LS like approximation for the initial guess of the Jacobian is computed. - `RS-SVD`: IMVJ runs in restart mode. After M time windows a truncated SVD of the Jacobian is updated. - `RS-SLIDE`: IMVJ runs in sliding window restart mode. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | truncation-threshold | float | If IMVJ restart-mode=RS-SVD, the truncation threshold for the updated SVD can be set. | `0.0001` | none | | chunk-size | integer | Specifies the number of time windows M after which the IMVJ restarts, if run in restart-mode. Default value is M=8. | `8` | none | | reused-time-windows-at-restart | integer | If IMVJ restart-mode=RS-LS, the number of reused time windows at restart can be specified. | `8` | none | | type | string | Type of the restart mode. | `RS-SVD` | `no-restart`, `RS-0`, `RS-LS`, `RS-SVD`, `RS-SLIDE` | ##### max-used-iterations Maximum number of columns used in low-rank approximation of Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### time-windows-reused Number of past time windows from which columns are used to approximate Jacobian. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The number of columns. | _none_ | none | ##### data The data used to compute the acceleration. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | The name of the mesh which holds the data. | _none_ | none | | name | string | The name of the data. | _none_ | none | ##### filter Type of filtering technique that is used to maintain good conditioning in the least-squares system. Possible filters: - `QR1-filter`: updateQR-dec with (relative) test \\(R(i,i) < \epsilon *\lVert R\rVert_F\\) - `QR1_absolute-filter`: updateQR-dec with (absolute) test \\(R(i, i) < \epsilon\\) - `QR2-filter`: en-block QR-dec with test \\(\lVert v_\text{orth} \rVert_2 < \epsilon * \lVert v \rVert_2\\) Please note that a QR1 is based on Given's rotations whereas QR2 uses modified Gram-Schmidt. This can give different results even when no columns are filtered out. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit eps of the filter. | `1e-16` | none | | type | string | Type of the filter. | _none_ | `QR1`, `QR1-absolute`, `QR2` | ##### preconditioner To improve the performance of a parallel or a multi coupling schemes a preconditioner can be applied. A constant preconditioner scales every acceleration data by a constant value, which you can define as an attribute of data. - A value preconditioner scales every acceleration data by the norm of the data in the previous time window. - A residual preconditioner scales every acceleration data by the current residual. - A residual-sum preconditioner scales every acceleration data by the sum of the residuals from the current time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | freeze-after | integer | After the given number of time windows, the preconditioner weights are frozen and the preconditioner acts like a constant preconditioner. | `-1` | none | | type | string | Type of the preconditioner. | _none_ | `constant`, `value`, `residual`, `residual-sum` | #### acceleration:broyden Accelerates coupling data with the (single-vector) Broyden method. **Example:** ```xml ``` **Valid Subtags:** * [initial-relaxation](#initial-relaxation-1) `1` * [max-used-iterations](#max-used-iterations-1) `1` * [time-windows-reused](#time-windows-reused-1) `1` * [data](#data-1) `1..*` ##### initial-relaxation **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | float | | _none_ | none | | enforce | boolean | | `0` | none | ##### max-used-iterations **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | | _none_ | none | ##### time-windows-reused **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | | _none_ | none | ##### data **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | scaling | float | To improve the performance of a parallel or a multi coupling schemes, data values can be manually scaled. We recommend, however, to use an automatic scaling via a preconditioner. | `1` | none | | mesh | string | | _none_ | none | | name | string | | _none_ | none | #### absolute-convergence-measure Absolute convergence criterion based on the two-norm difference of data values between iterations. \$$\left\lVert H(x^k) - x^k \right\rVert_2 < \text{limit}\$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \((0, 1]\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### relative-convergence-measure Relative convergence criterion based on the relative two-norm difference of data values between iterations. \$$\frac{\left\lVert H(x^k) - x^k \right\rVert_2}{\left\lVert H(x^k) \right\rVert_2} < \text{limit} \$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \\((0, 1]\\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### residual-relative-convergence-measure Residual relative convergence criterion based on the relative two-norm differences of data values between iterations. \$$\frac{\left\lVert H(x^k) - x^k \right\rVert_2}{\left\lVert H(x^{k-1}) - x^{k-1} \right\rVert_2} < \text{limit}\$$ **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | limit | float | Limit under which the measure is considered to have converged. Must be in \((0, 1]\). | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### min-iteration-convergence-measure Convergence criterion used to ensure a miminimal amount of iterations. Specifying a mesh and data is required for technical reasons and does not influence the measure. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | min-iterations | integer | The minimal amount of iterations. | _none_ | none | | data | string | Data to be measured. | _none_ | none | | mesh | string | Mesh holding the data. | _none_ | none | | strict | boolean | If true, non-convergence of this measure ends the simulation. "strict" overrules "suffices". | `0` | none | | suffices | boolean | If true, convergence of this measure is sufficient for overall convergence. | `0` | none | #### max-iterations Allows to specify a maximum amount of iterations per time window. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The maximum value of iterations. | _none_ | none | #### extrapolation-order Sets order of predictor of interface values for first participant. **Example:** ```xml ``` | Attribute | Type | Description | Default | Options | | --- | --- | --- | --- | --- | | value | integer | The extrapolation order to use. | _none_ | none | Test time = 0.14 sec ---------------------------------------------------------- Test Pass Reason: Required regular expression found. Regex=[# precice-configuration] "precice.tools.markdown" end time: Aug 23 09:42 CEST "precice.tools.markdown" time elapsed: 00:00:00 ---------------------------------------------------------- 35/39 Testing: precice.tools.xml 35/39 Test: precice.tools.xml Command: "/home/claudio/Projects/precice/precice-2.5.0/build/precice-tools" "xml" Directory: /home/claudio/Projects/precice/precice-2.5.0/build "precice.tools.xml" start time: Aug 23 09:42 CEST Output: ---------------------------------------------------------- Test time = 0.09 sec ---------------------------------------------------------- Test Pass Reason: Required regular expression found. Regex=[