Benjamin Rodenberg

Added https://github.com/precice/python-bindings/pull/207 and https://github.com/precice/python-bindings/pull/213 to the list due to compatibility problems.

Added https://github.com/precice/python-bindings/commit/a6d3a80222f85f8c0d87be755ea445d20b721fa3 and https://github.com/precice/python-bindings/pull/215 to fix the spack testing for this release.

I just did the release (see #212)

Do we also want to be able to test for warnings? This just came up while discussing https://github.com/precice/precice/issues/531 with @Fujikawas. (maybe testing for warnings is also a bad idea in...

> The primarily reason for the current format is the consistency with our existing [`BoundingBox`](https://github.com/precice/precice/blob/019162f721b179aab8e05edca213b0ac6d524a00/src/mesh/BoundingBox.cpp#L17) class and I would would not like to break this consistency. https://github.com/precice/precice/blob/019162f721b179aab8e05edca213b0ac6d524a00/src/mesh/BoundingBox.cpp#L17 I don't think...

To just give an example, why I believe this data structure is non optimal: If I have a bounding box with (1,2,3) and (4,5,6) as min and max this results...

This feature was already discussed in the past within the thesis of @Dominanz. See [here, section 3.4.1](https://mediatum.ub.tum.de/doc/1520580/1520580.pdf): > When communicating the data from and to the ray tracer via preCICE,...

> I assume there is a motivating application example for this enhancement? Currently, I do not yet understand the user perspective. The motivation for this is that we have to...

We can also leave this issue open until we see that this feature is really needed. At the moment it's a hypothetical and nice-to-have feature. Theoretically possible, but I don't...

> If the API allows to specify the length of the **next** time window, then this information can be held onto by precice until the end of the current time...