[standingVortex]

Hello foamers,

As far I know, OpenFOAM v2212 I am using has a great degree of flexibility in specifying the time-varying BC through the timeVaryingMappedFixedValue BC. Essentially, it allows to perform the 1:1 mapping of a specified location-value pair defined by the following case structure:

<rootCase>/constant/boundaryData/<patchName>:
--> points
--> <time>/<field>

It should also allow the interpolation of these values in space and time through the PatchFunction1 capabilities.
However, according to my understanding, the current implementation is still limited to the mapping of the same set of location points. What I am saying is that the current implementation does not allow for reading different sets of points for every single time step, and is therefore not capable of mapping the dynamically moving patches (e.g. in dynamic meshes).

But as I have the moving inlet case, and would like to perform the LES simulation (by feeding the turbulent structures in my simulation generated by a separate precursor simulation), the modified version of the timeVaryingMappedFixedValue BC seems to be the reasonable approach.

What I would like to operate on is the case structure like this:

<rootCase>/constant/boundaryData/<patchName>:
--> <time>/<field>
--> <time>/points

I have done some BC modifications in the past without any problems, but these BCs were rather simple. The timeVaryingMappedFixedValue seems a bit more challenging to modify. Based on my understanding, it seems like the MappedFile.C of the PatchFunction1 has to be modified to allow reading points file every single timestep, and from the new path. Since everything became heavily templated recently to facilitate easier code maintenance, it also became bit more challenging for non-expert C++ user like me to navigate around. Not sure if there is anything else required...

I would really appreciate if experienced users could shed some light and provide the foam wisdom on this topic and confirm if I am indeed on the right track.

Thank you very much.

[olesen]

The coding with templating is obviously one thing, but handling moving input data points will also be a bit costly. Inside of the Mapped function, a delaunay triangulation is performed for the cloud of input points. This is used to determine interpolation weights for mapping input values (at the those points) to the patch face centres. This triangulation is not the cheapest.