Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 413
    • Issues 413
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1100
Closed
Open
Issue created Nov 27, 2018 by Kutalmış Berçin@kutiMaintainer

Possible Deprecation of turbulentInlet Boundary Condition

Hi,

turbulentInlet boundary condition generates fluctuating velocity fields by superimposing (pseudo-)random number sets (scaled by a given turbulence intensity) onto a reference (mean) velocity field.

https://www.openfoam.com/documentation/cpp-guide/html/classFoam_1_1turbulentInletFvPatchField.html

Although this approach was proposed in the literature as the first turbulence inflow method, numerous studies quantified its ineffectiveness (refs can be provided if need be). Unfortunately, turbulence is fully deterministic and involving various spatial/temporal coherent structures, yet is random in a sense that its stochastic development cannot be predicted, again due to its acute sensitivity to initial/boundary conditions.

For example, in detail, for turbulentInlet the energy of generated time-series is equally distributed over the whole wavenumber range, that means the spectrum is approximately a horizontal line. Therefore, due to a lack of energy in the low wave number range, the pseudo turbulence is immediately damped to zero when enters into a CFD domain, and the result is virtually identical with a laminar inflow.

For these reasons, I kindly suggest a discussion as to this module's deprecation since customers/developers/users could be misled by its name and offerings.

Assignee
Assign to
Time tracking