You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a face-nodes-based mesh, one point of the 2D solver has two equally-distanced neighbors on the 3D mesh (in most cases). This makes the nearest-neighbor mapping to act arbitrarily.
Further numerical issues with the coupling schemes (@uekerman).
If a solver needs to assume the dimension of its partner (potentially scaling any received data), then the black-box assumption of preCICE weakens.
Proposed solution
We are working on making preCICE compatible with mixed dimensions, but this feature will not be available anytime soon. Also, OpenFOAM is clearly the solver of choice of our users for the role of the Fluid participant, right now.
As an easier solution, @uekerman suggested that we have an option in the OpenFOAM adapter to define 3D or 2D preCICE interfaces. This would require multiple changes in the code, for which @davidscn already did some research.
Context
We currently have several users that couple OpenFOAM (which only works in 3D) with 2D solvers. We usually treat this case as follows:
<solver-interface dimensions="3">
.Examples are e.g.:
Problem
This approach has the following problems:
Proposed solution
We are working on making preCICE compatible with mixed dimensions, but this feature will not be available anytime soon. Also, OpenFOAM is clearly the solver of choice of our users for the role of the Fluid participant, right now.
As an easier solution, @uekerman suggested that we have an option in the OpenFOAM adapter to define 3D or 2D preCICE interfaces. This would require multiple changes in the code, for which @davidscn already did some research.
Related to #30.
The text was updated successfully, but these errors were encountered: