Closed MakisH closed 11 months ago
I think what's triggering this assertion is that we have multiple data sets living on the same interface and writing to the same buffer. We need to split the buffer reading/writing in the adapter according to the data sets
I can take a closer look later.
Makes sense, we are reusing the dataBuffer_
, and previously we were specifying the number of locations separately. But now, it is extracted from the size of dataBuffer_
.
Essentially, this means we need a separate buffer for each mesh (already the case) and for scalars vs vectors.
I guess we get this issue in the FF tutorials because in these tutorials we have both scalars and vectors on the same mesh. In the flow-over-heated-plate we only have scalars, while in the perpendicular-flap we only have vectors.
Edit: I can confirm that I get the same behavior with preCICE commit 39429b4, i.e., before the dimensions PR.
I guess we get this issue in the FF tutorials because in these tutorials we have both scalars and vectors on the same mesh. In the flow-over-heated-plate we only have scalars, while in the perpendicular-flap we only have vectors.
It's not so much about the mixture of scalars/vectors, but more about the various data fields on the same interface. In the fluid-fluid module, we have for example pressure and velocity gradients on the same read side. One could easily reproduce this issue by splitting one of single-data interfaces in the perpendicular-flap tutorial into two separate fields, e.g., Stress1 and Stress2
I guess we get this issue in the FF tutorials because in these tutorials we have both scalars and vectors on the same mesh. In the flow-over-heated-plate we only have scalars, while in the perpendicular-flap we only have vectors.
Actually, that's exactly the issue, I had something slightly different in mind.
Describe your setup
Operating system (e.g. Linux distribution and version): Ubuntu 22.04 preCICE Version: f7289a67
Describe the problem
Trying to merge
develop
intoff-develop
, and while running some tutorials, I noticed the following output:This comes from
tutorials/flow-over-heated-plate-partitioned-flow/fluid2-openfoam
.Similarly from
tutorials/partitioned-backwards-facing-step/fluid1-openfoam
:Affected tutorials:
Potentially affected:
Not affected:
Additional context
The tutorial
partitioned-pipe
does not throw this error, but instead runs into an assertion:Maybe related to https://github.com/precice/openfoam-adapter/pull/297, to #255, or to https://github.com/precice/precice/pull/1742. I guess that somewhere in the code we are mixing up some data and mesh dimensions, or that in the
Interface.C
we are giving the wrong number of locations.cc @thesamriel