D-FlowFM + preC-SUMO coupling: serial explicit coupling with changing FM 3D mesh (resetMesh) possible?

Is preCICE for me?
1

Hi preCICE community,

We are building a coupled workflow between:

  1. A far-field hydrodynamic model (FM)
  2. A near-field plume model (preC-SUMO)

We want to check whether our intended coupling approach is compatible with preCICE.

Background (in plain terms):

  • FM provides flow/environment information to preC-SUMO.
  • preC-SUMO computes resulting source/sink terms.
  • Those source/sink terms are sent back to FM and applied in the next step.
  • There can be multiple discharge locations (“diffusers”) per time step.
  • FM horizontal mesh (2D) stays fixed.
  • FM vertical 3D representation can change over time (due to changing water level and bed level), so FM may need mesh reset/update calls during the run.

What we want to do:

  • Use serial explicit coupling (run D-FlowFM part, then near-field part, then continue).
  • Keep doing this while FM’s 3D mesh can change during the simulation. FM will only write the new 3D data in new 3D mesh at end of coupling time step.

Our questions:

  1. Is this scenario supported in preCICE: serial explicit coupling with runtime mesh changes on one participant?
  2. If not, what is the main reason?
  3. Is the issue mainly related to mapping consistency, mesh re-registration timing, participant state/lifecycle, or checkpoint/restart assumptions?
  4. What is the recommended approach for this case?
    • Keep a fixed coupling mesh and remap internally in the adapter?
    • Reinitialize at controlled points?
    • Use a different coupling scheme/configuration?

Any guidance, best practices, or references to similar setups would be greatly appreciated.

precice_config.xml (7.1 KB)

2

Hi @Aabhas,

to directly answer your questions:

In principle, yes, but this is a new/experimental feature in active development (in the context of @fsimonis work), see the documentation.

The remeshing feature sounds to me exactly fit for this use case.

By the way, this is the visualization of your attached config:

precice-config
precice-config2108×799 204 KB

P.S.: I edited your post to fix the Markdown syntax. In case you copy-paste, check that this looks as intended.