About "compute mapping" function in precice

[ilovenili]

hi,precice:

I’m currently using the ALE method to implement a moving mesh that implements fluent, and I see that the official website says that precice’s mesh mapping is based on a reference domain, so I have two questions:
1 Fluent’s reference domain changes every time step when using dynamic mesh, which means it needs to do mesh mapping every time step to be reasonable, but precice only calls “compute mapping” once, how to explain this?
2 For perpendicular flap case, is it necessary to calculate the mesh mapping matrix at every time step, Similar to calls “compute mapping” every time step, and why?

[fsimonis]

Hi,

@ilovenili

Fluent’s reference domain changes every time step when using dynamic mesh

Meaning that you aren’t using a static reference domain. This isn’t ALE.

@ilovenili

For perpendicular flap case, is it necessary to calculate the mesh mapping matrix at every time step, Similar to calls “compute mapping” every time step, and why?

RBF mappings require solving a system when mapping data. The mapping section of our latest reference paper explains this in detail.