From e796634c71a4d06a50be6d86f517a59b2d8a7bb1 Mon Sep 17 00:00:00 2001 From: Benjamin Uekermann Date: Mon, 6 Feb 2023 18:59:46 +0100 Subject: [PATCH] Fix typo in README --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 5ee67ea8..4ea61e05 100644 --- a/docs/README.md +++ b/docs/README.md @@ -111,7 +111,7 @@ precice-aste-run -p A --mesh fine_mesh --data "dummyData" precice-aste-run -p B --mesh coarse_mesh --data "mappedData" --output mappedMesh ``` -While the example above exexutes the mapping in serial, `precice-aste-run` can be executed in parallel (using MPI). However, this requires a partitioned mesh (one per parallel rank). In order to decompose a single mesh appropriately, the tools `precice-aste-partition` and `precice-aste-join` can be used. +While the example above executes the mapping in serial, `precice-aste-run` can be executed in parallel (using MPI). However, this requires a partitioned mesh (one per parallel rank). In order to decompose a single mesh appropriately, the tools `precice-aste-partition` and `precice-aste-join` can be used. {% tip %} If you want to reproduce a specific setup of your solvers, you can use the [export functionality](https://precice.org/configuration-export.html#enabling-exporters) of preCICE and use the generated meshes directly in `precice-aste-run`. If you run your solver in parallel, preCICE exports the decomposed meshes directly, so that no further partitioning is required.