Skip to content

Commit e796634

Browse files
authored
Fix typo in README
1 parent d698831 commit e796634

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ precice-aste-run -p A --mesh fine_mesh --data "dummyData"
111111
precice-aste-run -p B --mesh coarse_mesh --data "mappedData" --output mappedMesh
112112
```
113113

114-
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.
114+
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.
115115

116116
{% tip %}
117117
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.

0 commit comments

Comments
 (0)