Benjamin Rodenberg

Allow to read data from interpolant in time

2

**Please describe the problem you are trying to solve.** In #133 the idea of waveform relaxation is drafted. By providing an interpolant instead of a single sample per window higher-order...

Write data, when subcycling is used

3

**Please describe the problem you are trying to solve.** Currently only data at the end of the coupling window is exchanged. This means that all calls of `write...data(...)` are ignored...

Add tutorial: partitioned oscillator

2

* Tutorial illustrates a simple case which can be used for convergence studies and waveforms * Case is taken from V. Schüller, B. Rodenberg, B. Uekermann and H. Bungartz, A...

In https://github.com/precice/precice/pull/1664 I introduced bulk send/recv of multiple substeps. The main motivation is to support multirate time stepping and higher-order interpolation. This, however, came with some technical debt, because I...

Allow constant underrelaxation with individual relaxation factors per data

2

**Please describe the problem you are trying to solve.** For experiments with optimal relaxation factors like done by @valentinaschueller it would be helpful to offer an API that allows to...

Allow `advance(dt)` with `dt > time_window_size`

2

**Please describe the problem you are trying to solve.** Sometimes we run into a situation where the time step size defined in the config file does not exactly fit into...

Allow `time::Storage` to keep data from past windows

1

**Please describe the problem you are trying to solve.** With the functions `trim` and `move` the `time::Storage` can currently only keep data of the current window. In the future, we...

Let preCICE only exit on critical errors

1

**Please describe the problem you are trying to solve.** I'm trying to use preCICE in an interactive fashion via the python bindings. Here, even non fatal but erroneous calls to...

Provide access to interpolating function instead of evaluations?

2

**Please describe the problem you are trying to solve.** I'm using the [ODE solver of `scipy`](https://docs.scipy.org/doc/scipy/reference/generated/scipy.integrate.solve_ivp.html#scipy.integrate.solve_ivp) for some experiments. Here, the user is expected to provide a `f(t, y)`, i.e....

Update actions to use `mesh::Data::_waveform`

2

We originally decided to enforce identical time meshes for actions here: https://github.com/precice/precice/blob/6929aabb62eaca2363a848f6a67d55fd3f7f2af5/src/action/SummationAction.cpp#L42 However, this restriction is not necessary anymore, because we changed ownership of the waveform in https://github.com/precice/precice/pull/1714.