Triple-deck and direct numerical simulation analyses of high-speed subsonic flows past a roughness element

Triple-deck and direct numerical simulation analyses of high-speed subsonic flows past a roughness element
DOI: 10.1017/jfm.2015.281
Abstract: This paper is concerned with the boundary-layer separation in subsonic and transonic flows caused by a two-dimensional isolated wall roughness. The process of the separation is analysed by means of two approaches: the direct numerical simulation (DNS) of the flow using the Navier–Stokes equations, and the numerical solution of the triple-deck equations.

Nektar++ on ARCHER

Nektar++ on ARCHER

The ​ARCHER national supercomputer is intended for very large-scale computations and is the successor to ​HECToR. These instructions are preliminary in nature and an up-to-date version of the master branch is required as support for the compilation environment has only been added recently.

A Guide to the Implementation of Boundary Conditions in Compact High-Order Methods for Compressible Aerodynamics

A Guide to the Implementation of Boundary Conditions in Compact High-Order Methods for Compressible Aerodynamics
DOI: 10.2514/6.2014-2923
Abstract: The nature of boundary conditions, and how they are implemented, can have a significant impact on the stability and accuracy of a Computational Fluid Dynamics (CFD) solver. The objective of this paper is to assess how different boundary conditions impact the performance of compact discontinuous high-order spectral element methods (such as the discontinuous Galerkin method and the Flux Reconstruction approach), when these schemes are used to solve the Euler and compressible Navier-Stokes equations on unstructured grids.

Nektar++ on the Imperial College CX2 cluster

Nektar++ on the Imperial College CX2 cluster

CX2 is intended for large-scale production runs. For runs smaller than 64-processes, use CX1. CX2 does not support the same range of modules as CX1, requiring a different configuration procedure. Since CX1 and CX2 share home directories, you should clone Nektar++ into a new directory, rather than sharing with the CX1 build. Even using different build directories is not sufficient as ThirdParty libraries are built differently.