Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coupling OpenFOAM to 2D solvers could be easier #94

Closed
MakisH opened this issue Aug 9, 2019 · 1 comment · Fixed by #96
Closed

Coupling OpenFOAM to 2D solvers could be easier #94

MakisH opened this issue Aug 9, 2019 · 1 comment · Fixed by #96

Comments

@MakisH
Copy link
Member

MakisH commented Aug 9, 2019

Context

We currently have several users that couple OpenFOAM (which only works in 3D) with 2D solvers. We usually treat this case as follows:

  • Use a 3D solver interface: <solver-interface dimensions="3">.
  • In the 3D solver, use only one cell in the out-of-plane direction (pseudo-2D) and define the interface as points on a line.
  • In the 2D solver, give zero values for the out-of-plane field components (e.g. force in z-direction).

Examples are e.g.:

Problem

This approach has the following problems:

  • 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.
  • RBF mapping, which is the usual workaround to the equal-distance issue, needs to be configured to set a dead dimension.
  • 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.

Related to #30.

@BenjaminRodenberg
Copy link
Member

There are two additional tutorials that are coming soon, where the 2D-3D issue is very relevant: FSI with OpenFOAM and FEniCS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants