Scalable Interfaces for Geometry and Mesh based Applications

OECD/NEA-Vattenfall T-Junction Benchmark

Posted by on Jun 24, 2014 in Meshes, Meshkit

The T-Junction mesh was generated for the OECD Vettenfahl T-Junction benchmark; this exercise was a blind benchmark of various CFD codes.  The Argonne code Nek5000 participated in this benchmark, using the mesh shown below.  The mesh was generated with Cubit 10.2, then modified to extend the (top) inflow and (side) outflow pipes.


Cutaway view of volume mesh

Shape quality metric for this mesh. Probably low due to
high aspect-ratio elements in boundary layer.


The benchmark specification.
Aleksandr V. Obabko, Paul F. Fischer, Timothy J. Tautges, “CFD Validatgion in OECD/NEA T-Junction Benchmark”, ANL-NE-11-25, Argonne National Laboratory, Sept. 30, 2011.

Mesh/Geometry Files

Cubit 10.2 journal file that generates geometry & mesh
Cubit (10.2) .cub file (contains geometry and mesh)
ACIS .sat file for this geometry.
Mesh, in ExodusII format.

Adding Boundary Layers Using MeshKit’s PostBL Tool

Figure (a) shows the original model, figure (b) shows a zoomed-in view of the T-junction in the original mesh. MeshKit‘s PostBL  tool uses only one normal direction on this T-intersection point to create new boundary layer elements; this allows for creation of a smooth mesh with similar-sized elements. The shape quality metric of this mesh is shown in Figure (c); elements with lower but acceptable quality elements are on the boundary because of low aspect ratio of the mesh. A close-up in Figure (d) shows three new layers as a separate material.

Hex meshed T-junction example: (a) Original mesh. (b) Close-up of original mesh intersection of cylinders. (c) Mesh with 3 boundary layers showing shape quality metric, smoothened using MESQUITE. (d) 3 boundary layers mesh close-up.

Copyright © 2014--2020 SIGMA. All Rights Reserved.