6.7. Drag Prediction of Common Research Model

6.7.1. Introduction

The purpose of this case study is to compute the turbulent flow past NASA’s Common Research Model (CRM) (a transonic wing-body-tail model) from the 4th AIAA CFD Drag Prediction Workshop. The goal of the workshop is to assess the state-of-the-art computational methods as practical aerodynamic tools for aircraft force and moment prediction of industry relevant geometries. The workshop allows comparisons to be made between different solvers and equation sets, and for performance and accuracy to be assessed.

In this case study, we will use mesh created in Pointwise and run it through the Flow360 CFD solver developed by Flexcompute Inc. We will demonstrate how to upload a mesh, run a case and view results. Performance of results from Flow360 will be compared with flow solutions from FUN3D, which were presented at the 4th AIAA CFD Drag Prediction Workshop (DPW-4).

6.7.2. Problem Description

The problem considers the flow around the CRM at a freestream Mach number of 0.85 (\(M_{\infty} = 0.85\)) to achieve a target lift coefficient of 0.5 (C_L= 0.5). The geometry of the CRM with a wing-body-tail configuration can be downloaded from here, and is shown in Fig. 6.7.1. The aircraft has a mirror symmetry. Summary of the geometric parameters is given below.

Fig. 6.7.1 Test geometry of the Drag Prediction Workshop

• Mean aerodynamic chord (MAC) = 275.8 in, located at y=468.75 in.

• Wing semi-span (b/2) = 1156.75 in.

• Reference area of the semi-span model = Sref/2 = 297,360.0 in².

• Moment reference center (MRC): x = 1325.90 in, y = 468.75 in, z = 177.95 in.

• Aspect Ratio (AR) = b²/Sref = 9.0.

And the corresponding flow conditions are:

• Freestream Mach Number, \(M_{\infty} = 0.85\).

• Target Lift Coefficient, C_L= 0.5.

• Tail Incidence angle = 0°.

• Reynolds Number (based on MAC) = 5 Million.

• Reference Temperature = 310.93 K.

6.7.3. Mesh

Grids were developed using Pointwise. Flow360 supports mesh file formats in ugrid, cgns, and their .gz or .bz2 compressions. For the purpose of this case study a cgns mesh file format and a medium-resolution mesh, with mixed hexahedral, tetrahedral, prism, and pyramid elements and with about 11.3M nodes was used.

Fig. 6.7.2 Medium-resolution mesh of the CRM

6.7.4. Setup and Solution

6.7.4.1. Upload the Mesh File

The first thing you need to do is to upload the mesh file and the mesh configuration file to Flow360 cloud. These files can be obtained from here:

• Mesh file: mesh

• Mesh configuration file: Flow360Mesh.json

We will do this step-by-step using the Python API. Open your Python interpreter and import the Flow360 client, json module and read the configuration of mesh.

python3
import flow360client
import json

meshJson = json.load(open('/path/to/Flow360Mesh.json')

Now upload the mesh using the following command:

meshId = flow360client.NewMesh(fname='/path/to/dpw4.cgns',
                               meshJson=meshJson,
                               meshName='DPW4_medium',
                               tags=[]
                              )

Replace the file paths in meshJson and NewMesh with your own file paths. Mesh name and tags are optional. Executing this command will return a meshId, which can be used in the next step to run the case.

6.7.4.2. Run the Case

To run a case, first download the CFD solverconfiguration file named Flow360.json. This file has been configured to run for this medium-resolution mesh. The case can be submitted using the following command:

caseId = flow360client.NewCase(meshId=meshId,
                               config='/output/path/for/Flow360.json',
                               caseName='DPW4_case',
                               tags=[]
                              )

Replace the file path in config with your own. You could provide a caseName, which is “Flow360” by default. The tags are optional.

If you decide to run a case with another mesh or flow condition, the command parameters need to be adjusted accordingly. A detailed description of the command parameters can be found in our API Reference section.

6.7.4.3. Downloading the Results

To download the solver log for your case, use the following command:

flow360client.case.DownloadSolverOut(caseId, fileName='path/to/log')

The second argument fileName is optional, its default value is ‘solver.out’.

The surface data (surface distributions and slices) and the entire flow field can be downloaded, respectively, using:

flow360client.case.DownloadSurfaceResults(caseId, fileName='path/to/surfaceSol')
flow360client.case.DownloadVolumetricResults(caseId, fileName='path/to/volumeSol')

The second argument fileName is optional, its default value is “volumes.tar.gz” for volume solution and “surfaces.tar.gz” for surface/slice solution.

The residuals history and total forces can be downloaded, respectively, using the following commands:

flow360client.case.GetCaseResidual(caseId)
flow360client.case.GetCaseTotalForces(caseId)

Finally, you can download the surface forces by their component names using the following commands:

flow360client.case.GetCaseSurfaceForcesByNames(caseId, <list of boundaryNames>)

Replace the caseId with your own case’s ID and <list of boundaryNames> with names of the boundaries. There is a script to download all of the above stuff by: python3 downloadAll.py caseId.

6.7.5. Grid Convergence

The grid convergence of the chosen mesh in this case study has been done by comparing the angles of attack, coefficients of total drag, pressure drag, skin friction drag and pitching moment obtained from Flow360 with solutions presented by FUN3D at the Drag Prediction Workshop. This grid convergence is presented in Fig. 6.7.3, and the number of nodes and cells for a coarse, medium and fine grids are presented in Table 6.7.1.

Table 6.7.1 Mesh Statistics for different grid sizes

	# of Nodes	# of Cells
Coarse	5.5 M	10.2 M
Medium	11.3 M	18.7 M
Fine	43 M	84.4 M

Fig. 6.7.3 Grid convergence of Flow360 compared with FUN3D results from the 4th AIAA CFD Drag Prediction Workshop in 2009. The x-axis is the number of mesh grid points N. The scale of the expected numerical error is also labeled for N^-2/3; the y-axis shows the total drag (top-left plot), pressure and skin friction drag (top-right plot), pitching moment (bottom-left plot) coefficients and angles of attack (bottom-right plot).

6.7.6. Results

The results data obtained from the previous step can be postprocessed in either ParaView or Tecplot. You may specify your preference in the Flow360.json configuration file under the outputFormat argument. The coefficients of skin friction (C_f) and pressure (C_p) can be viewed on our Web UI under the visualization tab.

Fig. 6.7.4 shows the contour plots of coefficient of skin friction

Fig. 6.7.4 Coefficient of Skin Friction

Fig. 6.7.5 shows contour plots of coefficient of pressure

Fig. 6.7.5 Coefficient of Pressure

Fig. 6.7.6 shows the Q-criterion plot, colored by Mach number. The threshold for Q-criterion for this case is 1.35e-7, which can be calculated using:

(6.7.1)\[Q_{threshold} = (\frac{Freestream\ Mach\ Number}{Wing\ Span})^2 = (\frac{M_{\infty}}{b})^2\]

Fig. 6.7.6 Q-criterion plot, colored by Mach Number

6.7.7. Summary

This tutorial demonstrated how to set up, solve and present results of an external aerodynamics flow over NASA’s Common Research Model (CRM) from the Drag Prediction Workshop using Flow360’s Python API. The Angle of Attack, C_D, C_D,p, C_D,vis, and C_My data for a target C_L of 0.5 obtained through Flow360 has been compared with the FUN3D solutions presented at the 4th Drag Prediction Workshop for accuracy.