Submitting a full 3D inflow plane data

[SRkumar97]

Hello!
I'm trying to run a long domain, boundary layer case by splitting the simulation into parts. In the first part, the domain length would be only one half or one third of its actual length, while the next one will have the remaining portion.
For this, the entire flow field data from the outlet plane of the first simulation should be fed to the inlet plane of the second simulation.
Essentially it would be something like exporting the entire flow snapshot of the x=x_hi plane of 3D simulation of domain 1, something like the exit plane contours of the images of this channel flow issue. And prescribe it for my domain 2 inlet.
#263

How do I go about this? Is this even possible?

[baperry2]

This capability is not available by default right now. We do allow inflows that have spatially and temporally varying velocity read from a file (turbInflow), but right now that file is generated from an independent synthetic turbulence script. You could probably adapt that capability for your needs by extracting outflow data from your first simulation and writing it into the appropriate file format. This may be something that people have done, but hasn't made it back into the core code.

https://amrex-combustion.github.io/PelePhysics/Utility.html#turbulent-inflows

[SRkumar97]

Ohh, understood. Thanks! Do any of the test cases use this turbInflow feature?

[SRkumar97]

Found it. There is the homogeneous turbulence decay testcase https://amrex-combustion.github.io/PeleC/validation/validation.html#decay-of-homogeneous-isotropic-turbulence
Thanks!

[baperry2]

That case uses turbulence as an initial condition rather than a boundary condition. Exec/Production/JetFlame allows turbulence as a boundary condition. There's also a TurbInflow example in PeleLMeX that uses the same capability

[SRkumar97]

Ohh, thanks a lot. Will definitely check these.