Skip to content

Commit 2c0ffeb

Browse files
authored
Typo Fix in implicit coupling instructions (#386)
1 parent 2ea40ef commit 2c0ffeb

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

pages/docs/couple-your-code/couple-your-code-implicit-coupling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Step 6 – Implicit coupling
33
permalink: couple-your-code-implicit-coupling.html
44
keywords: api, adapter, coupling schemes, checkpoint, fixed-point
5-
summary: "In previous steps, we only considered explicit coupling. We now move onto implicit coupling, so sub-iterating each time step multiple times until a convergence threshold is reached. This stabilzes strongly-coupled problems."
5+
summary: "In previous steps, we only considered explicit coupling. We now move onto implicit coupling, so sub-iterating each time step multiple times until a convergence threshold is reached. This stabilizes strongly-coupled problems."
66
---
77

88
The main ingredient needed for implicit coupling is move backwards in time. For that, we need a [flux capacitor](https://www.youtube.com/watch?v=VcZe8_RZO8c). Just kidding 😉. What we really need is that your solver can write and read iteration checkpoints. An iteration checkpoint should contain all the information necessary to reload a previous state of your solver. What exactly is needed depends solely on your solver. preCICE tells you when you need to write and read checkpoints. To this end, preCICE uses the following interface:

0 commit comments

Comments
 (0)