Terrain-Aware Immersed Forcing Method

[hgopalan]

Summary

This draft PR introduces an immersed forcing method for representing terrain within AMR-Wind. The terrain is generated outside amr-wind and this method does not rely on the existing immersed boundary method. The terrain runs are performed in steps:

1. Run precursor
2. Generate the terrain using the included utility from the mmctools project and SRTM data
3. Generate roughness using NLCD database (under development and not fully integrated)
4. Run the terrain simulation with the terrain-related forcing terms included in the amp-wind input file and a terrain file created using the utilities.

The method can also be used to run cases without terrain such as an array of bluff bodies. The user has to create a XYZ file with the relevant information to do perform these simulations. The user can also use the stl2XYZ.py in tools/terrain folder to convert a STL file to XYZ file for AMR-Wind. It is recommended to have a smooth boundary near the inflow and outflow to reduce the number of iterations of the nodal and Mac projections.

The terrain modules have been designed to run with the Kosovic turbulence model. To use other turbulence models, the terrainBlanking information should be used to set the turbulent viscosity to zero in the solid region. It is also possible to specify a roughness file to include non-uniform roughness in the simulations.

The method is first-order accurate.

Reference Paper: https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2020MS002141
Implemented Code: FastEddy for urban microclimate without log-law. handling

Not included in the current PR:

1. Support for stratification with terrain
2. RANS model support for terrain
3. General turbulence model support (works only with the Kosovic model in non-hybrid mode).

Pull request type

PR is almost ready to be reviewed.

Please check the type of change introduced:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

Checklist

The following is included:

• new unit-test(s)
• new regression test(s)
• documentation for new capability

This PR was tested by running:

• the unit tests
  • on GPU
  • on CPU (Kestrel and MacOS)
• the regression tests
  • on GPU
  • on CPU (Kestrel and MacOS)

[marchdf]

Can you update the branch please? Looks like there are conflicts.