Skip to content

Pointwise as a Pre-processor for CFD

Introduction

In this month’s blog we use Pointwise as a pre-processor for performing a CFD analysis with ANSYS Fluent and OpenFOAM from the same Pointwise mesh. The geometry (Figure 1) is that of a glider and comes from the examples provided with Pointwise automatic meshing github repo called GeomToMesh.

For OpenFOAM in particular this is handy as OpenFOAM requires text based setup of boundaries conditions types, as well as manually specifying the location of boundary conditions within the boundary file.

Figure 1 - Glider geometry used for meshing and CFD airflow analysis
Figure 1 – Glider geometry used for meshing and CFD airflow analysis

The Mesh

Preparing the geometry (database in Pointwise terminology) for meshing required cleaning up the surface geometry and assembling into quilts: regions that will be meshed with a single surface mesh. The benefit of quilting is that a mesh topology is vastly simpler than the underlying geometry model topology. Finally a watertight database model is created ready for surface meshing (Figure 2) and volume meshing.

Figure 2 - Glider surface mesh (called Domain)
Figure 2 – Glider surface mesh (called Domains)

Pointwise as a Pre-processor for Fluent

With the surface mesh and volume mesh created, we can see how Pointwise is used to create boundary conditions and volume conditions (zones), for Fluent and OpenFOAM.

Let’s start with Fluent

Step 1 – Select Fluent as CAE Solver

Within Pointwise select the solver by going to menu CAE-> Select Solver… and choose Fluent (Figure 3).

Figure 3 - Select the CAE solver  as ANSYS Fluent
Figure 3 – Select the CAE solver as ANSYS Fluent

Step 2 – Create and Locate BCs

Create a BC for each boundary condition by clicking New, Select the patch and tick the associated box. Chose CAE types (eg Wall, Pressure Outlet etc) (Figure 4).

Figure 4 - Create a BC and slect the domain (surface mesh) for each boundary condition
Figure 4 – Create a BC and slect the domain (surface mesh) for each boundary condition

Step 3 – Export CAE to a .cas file

Select the volume blocks and go to menu File -> Export -> CAE and select the name of the cas file to export (Figure 5).

Figure 5 - Export CAE by selecting volume blocks and go to menu File -> Export -> CAE
Figure 5 – Export CAE by selecting volume blocks and go to menu File -> Export -> CAE

Step 4 – Import CAE to Mesh Fluent and Run

In Fluent import the cas file (which is the mesh), and define the values for the already named inlet and outlet, wall boundary conditions. Also define any other solver settings (Figure 6).

Figure 6 - Use Fluent to import the cas file and provide values for boundary conditions, and other solver setting
Figure 6 – Use Fluent to import the cas file and provide values for boundary conditions, and other solver setting

Pointwise as a Pre-processor for OpenFOAM

With the same Pointwise mesh, we can also switch to OpenFOAM as the solver. Then we can change the boundary conditions types to OpenFOAM types.

Step 1 – Select OpenFOAM as the CAE Solver

Within Pointwise select the solver by going to menu CAE-> Select Solver… and choose OpenFOAM (Figure 7).

Figure 7 - Select the CAE solver and choose OpenFoam
Figure 7 – Select the CAE solver and choose OpenFOAM

Step 2 – Define and Select OpenFOAM boundary conditions

Create a BC for each boundary condition by clicking New, Select the patch and tick the associated box. Chose CAE types (eg Wall, Pressure Outlet etc ) (Figure 8).

Note: if the BCs were setup for another solver the names will remain, and the type of BC will need to be adjusted

Figure 8 - Create/modify BCs for each boundary condition
Figure 8 – Create/modify BCs for each boundary condition

Step 3 – Export CAE to constant/polyMesh

Select the volume blocks and go to menu File -> Export -> CAE and select the constant/polyMesh directory to export (Figure 9). After export, the boundary file will be written with the boundary conditions types and names all set by Pointwise from the earlier specification (see Figure 10).

Figure 9 - Export CAE to polyMesh directory, where boundary, points, faces, owner neighbour etc will be written
Figure 9 – Export CAE to polyMesh directory, where boundary, points, faces, owner neighbour etc will be written
Figure 10 -  Exported boundary file, with types and names set in Pointwise
Figure 10 – Exported boundary file, with types and names set in Pointwise

Thanks for reading, the next edition will be later in November. Until then, happy meshing!

To see more about our Pointwise distribution go here, or for a free trial of Pointwise, go here.

Don’t forget to register for next month’s webcast on Mesh Adaption with Pointwise and Caelus.

Monthly Mesh
1. Cricket bat meshing
2. Twin box bridge deck meshing
3. Golf Driver Meshing
4. Frigate Helipad Pointwise unstructured mesh
5. Frigate Helipad – Structured O-H mesh
6. Horizontal wind turbine near a bridge
7. Meshing a Raspberry Pi
8. Scripting Pointwise Meshing
9. 2D meshing with sources in Pointwise
10. Pointwise as a Pre-processor for CFD
11. Mesh Adaption with Caelus and Pointwise
12. Meshing Santa’s Pod Racer Sled
13. Scripting Structured-Unstructured Meshes for Aerospace
14. Mesh Adaptation With Pointwise, Caelus & Python
15. Normal Extrusion Hybrid Meshes for Multi-Element Airfoils
16. Car park Ventilation CFD with Pointwise, Caelus, CFX and FDS
17. Mesh Independence for Car Park Ventilation
18. It’s all in the numbering – mesh renumbering may improve simulation speed
19. Voxel Transition Cell Recombination for OpenFOAM meshes
20. Meshing Santa’s Hat
21. 2D Sources in Meshes in Pointwise 18.4R1
Back To Top
Search