Particleworks for Ansys Manual

Release 1.4.0

Prometech Software, Inc.

Jun 05, 2023

 CONTENTS

1 Introduction 1
1.1 Supported Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Preparing Geometry Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3.1 Workflow for Particleworks-Ansys Mechanical One-way Coupling . . . . . . . . . 2
1.3.2 Workflow for Ansys Fluent-Particleworks One-way Coupling . . . . . . . . . . . . 3

2 Limitation 5

3 System Requirements 7

4 Folder Structure 9

5 Installing/Uninstalling Particleworks for Ansys Extension 11

5.1 Installing Particleworks for Ansys Extension . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2 Checking Installation Status of Particleworks for Ansys Extension . . . . . . . . . . . . . . 12
5.3 Uninstalling Particleworks for Ansys Extension . . . . . . . . . . . . . . . . . . . . . . . . 12

6 Loading/Unloading Particleworks for Ansys Extension 15

6.1 Loading Particleworks for Ansys Extension . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 Unloading Particleworks for Ansys Extension . . . . . . . . . . . . . . . . . . . . . . . . . 15

7 License Setup 17

8 Operation: Particleworks-Mechanical One-way Coupling 19

8.1 Operation in Ansys Workbench: part I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1.1 Creating and Saving Geometry Data . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1.2 Generating and Saving Mesh as Mapping Geometry Data (Optional) . . . . . . . . 20
8.1.3 Starting Particleworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.2 Operation in Particleworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.3 Operation in Ansys Workbench: Part II . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.4 Operation in Ansys Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.4.1 Analysis Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.4.2 Importing Mapping Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

9 Operation: Fluent-Particleworks One-way Coupling 27

i
 9.1 Operation in Fluent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.1.1 Calculating Airflow in Fluent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.1.2 Exporting Airflow Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.2 Operation in Ansys Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.2.1 Converting Fluent Airflow Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
9.2.2 Starting Particleworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
9.2.3 Importing and Setting Airflow Data . . . . . . . . . . . . . . . . . . . . . . . . . 32
9.2.4 Executing Simulation and Checking Result . . . . . . . . . . . . . . . . . . . . . 32

10 Tutorials 33

11 Technical Support 35

ii
 CHAPTER

ONE

INTRODUCTION

Particleworks for Ansys workflow enables engineers to quickly and intuitively set up a simulation project
which achieves the one-way coupling of Particleworks fluid simulation with Ansys Structural/Thermal anal-
ysis or Fluent airflow analysis.
• Particleworks calculates the fluid dynamics while its Mapping function maps the physical quantities,
namely local fluid pressure or heat transfer coefficient (HTC) and local fluid temperature, onto solid
(geometry data). The results are automatically imported by the pre-defined workflow in Ansys Work-
bench into Structural/Thermal analysis in Ansys Mechanical and used as boundary conditions.
• Airflow calculated by Fluent is converted in Ansys Workbench. Importing the converted airflow data
and using the air resistance model enables Particleworks to simulate the airflow influence on the fluid
behavior.
Particleworks for Ansys workflow minimizes necessary but redundant manual operations of data transfer
to help engineers focus on the essential parts of numerical analyses. It also integrates the advantages of
Particleworks and Ansys Mechanical/Fluent while complementing their simulation capabilities. Therefore,
it could solve complicated problems with multi-physics that span a large range.

1.1 Supported Analysis

Four types of simulation are supported in Ansys Mechanical:

• Static Structural: import pressure as boundary conditions
• Transient Structural: import pressure as boundary conditions
• Steady-State Thermal: import heat transfer coefficient and temperature as boundary conditions
• Transient Thermal: import heat transfer coefficient and temperature as boundary conditions
Two types of exported airflow data from Ansys Fluent are supported:
• Steady, averaged, or instant airflow
• Transient airflow

1
Particleworks for Ansys Manual, Release 1.4.0

1.2 Preparing Geometry Data

The required geometry data files in the one-way coupling of Particleworks and Ansys Structural/Thermal are
listed below. They can be created in either Ansys Workbench or other external CAD software.
• Geometry data for simulation: geometry data used for both fluid simulation and Structural/Thermal
simulation. They are imported into Particleworks and Ansys Workbench.
• Geometry data for mapping: geometry data used for Particleworks Mapping function, by which the
fluid simulation result is projected onto the geometry data. The geometry data for mapping can be the
same one used in the fluid simulation or a new independent geometry data. It is recommended to use
a geometry data with high resolution to improve Mapping function resolution.
The required geometry data in the one-way coupling of Ansys Fluent and Particleworks is listed below. It
can be created in either Ansys Workbench or other external CAD software.
• Geometry data for simulation: geometry data used for both fluid and airflow simulations. It is im-
ported into Particleworks and Ansys Fluent. Note that geometry data used for the simulation domain
in Ansys Fluent is NOT needed for simulation in Particleworks.

Note: Particleworks does not support geometry data creation or modification.

1.3 Workflow

1.3.1 Workflow for Particleworks-Ansys Mechanical One-way Coupling

1. Start Ansys Workbench.

2. Install and load Particleworks for Ansys extension.
3. Create Particleworks for Ansys workflow and Structural/Thermal workflow on Project Schematic.
4. Link Geometry and Particle Mapping tasks in Particleworks for Ansys to Geometry and Setup
task in Structural/Thermal workflow, respectively.
5. Import/Create geometry in Geometry task and save the geometry data for fluid and Structural/Thermal
simulation.
6. Generate mesh and save the meshed geometry in Model task in Structural/Thermal workflow used for
mapping in Particleworks (optional).
7. Start Particleworks from Particleworks GUI task. Execute fluid simulation by applying the simulation
geometry data and run Mapping postprocessing.
8. Import fluid simulation result through Particle Mapping task.
9. Set simulation conditions in Setup task and execute Structural/Thermal simulation.
10. View result and execute postprocessing in Ansys Mechanical.

2 Chapter 1. Introduction
 Particleworks for Ansys Manual, Release 1.4.0

1.3.2 Workflow for Ansys Fluent-Particleworks One-way Coupling

1. Start Ansys Workbench.

2. Install and load Particleworks for Ansys extension.
3. Create Particleworks for Ansys workflow on Project Schematic.
4. Import Fluent airflow data in Airflow Generation/Conversion task and convert Fluent airflow data
into a format that is compatible with Particleworks.
5. Start Particleworks from Particleworks GUI task. Execute fluid simulation by applying the air resis-
tance model.

1.3. Workflow 3
Particleworks for Ansys Manual, Release 1.4.0

4 Chapter 1. Introduction
 CHAPTER

TWO

LIMITATION

Particleworks for Ansys extension has below limitations:

• Environment
– Only English/Japanese environment in Ansys is supported.
– No support for changing Parameters or Design Points. All files are stored in dp0 folder.
• Operation
– Multiple Particleworks for Ansys workflows are allowed in the same project.
– However, only one Particleworks for Ansys workflow is allowed for coupling with one or more
Structural and Thermal systems.
– Couplings of multiple Particleworks for Ansys workflow with the same one Structural/Thermal
system are not allowed.
• Limitation in Particleworks:
– The imported geometry data to Particleworks must be STL, OBJ, or Nastran files.
– Only the three-dimensional Cartesian coordinate is supported.
– The unit system of the simulation must be set according to the unit system of the imported ge-
ometry data.

5
Particleworks for Ansys Manual, Release 1.4.0

6 Chapter 2. Limitation
 CHAPTER

THREE

SYSTEM REQUIREMENTS

• Ansys 2020R2, 2021R2

• Particleworks 6.2.0 or later

Note:
• The supported versions of Ansys or Particleworks may be changed in the future version upgrade.
• All hardware requirements are based on the lowest requirements by Ansys Workbench, Mechanical,
and Particleworks.
• Please refer to the installation guides of Ansys and Particleworks for more details.

7
Particleworks for Ansys Manual, Release 1.4.0

8 Chapter 3. System Requirements

 CHAPTER

FOUR

FOLDER STRUCTURE

• Save all geometry files in PwModels folder.

• Save all Particleworks projects in PwProject folder.
• For details of structure of Particleworks project file, see Particleworks UserManual.

9
Particleworks for Ansys Manual, Release 1.4.0

10 Chapter 4. Folder Structure

 CHAPTER

FIVE

INSTALLING/UNINSTALLING PARTICLEWORKS FOR ANSYS

EXTENSION

5.1 Installing Particleworks for Ansys Extension

1. Click Extensions > Install Extension. . . from the toolbar.

2. In Open dialog, select <install_path>/share/AnsysIF/ParticleworksforAnsys_en.wbex
then click Open.

Fig. 1: Installation of Particleworks for Ansys extension.

If the extension is successfully installed, an Install dialog will prompt out.

11
Particleworks for Ansys Manual, Release 1.4.0

5.2 Checking Installation Status of Particleworks for Ansys Extension

Once the extension Particleworks for Ansys has been successfully installed, it will appear in the list of Ex-
tension Manager. The installation status can be checked by either method below:
• On menu bar, click Extensions > Manage Extensions. . . to open Extensions Manager.
• On menu bar, click Extensions > ACT Start Page > Manage Extensions to open Extension Man-
ager.

5.3 Uninstalling Particleworks for Ansys Extension

The extension Particleworks for Ansys can be uninstalled from Extension Manager if it is no longer used.
The uninstallation must be done by rebooting Ansys first, then follow the steps below.
1. On menu bar, click Extensions > ACT Start Page > Manage Extensions to open Extension Man-
ager.
2. Click the reversed triangle at the lower right corner to open the list of actions.
3. Click Uninstall to uninstall the extension.

12 Chapter 5. Installing/Uninstalling Particleworks for Ansys Extension

 Particleworks for Ansys Manual, Release 1.4.0

Fig. 2: Uninstalling Particleworks for Ansys extension.

5.3. Uninstalling Particleworks for Ansys Extension 13

Particleworks for Ansys Manual, Release 1.4.0

14 Chapter 5. Installing/Uninstalling Particleworks for Ansys Extension

 CHAPTER

SIX

LOADING/UNLOADING PARTICLEWORKS FOR ANSYS EXTENSION

6.1 Loading Particleworks for Ansys Extension

To use Particleworks for Ansys extension, the extension must be loaded to the Toolbox. Loading can be done
by either method below.
• Check Particleworks for Ansys in Extensions Manager.
• Click Load extension in the pull-down list of ParticleworksforANSYS icon in Extension Manager.
If the extension is successfully loaded, the background color of the icon in Extension Manager will change
from white to light green.

6.2 Unloading Particleworks for Ansys Extension

To remove Particleworks for Ansys extension from Ansys Workbench, the extension must be unloaded. Un-
loading can be done by either method below:
• Uncheck Particleworks for Ansys in Extensions Manager.
• Click Unload extension in the pull-down list of ParticleworksforANSYS icon in Extension Man-
ager.
If the extension is successfully unloaded, the background color of the icon in Extension Manager will change
from light green to white.

15
Particleworks for Ansys Manual, Release 1.4.0

Fig. 1: Loading Particleworks for Ansys extension.

16 Chapter 6. Loading/Unloading Particleworks for Ansys Extension

 CHAPTER

SEVEN

LICENSE SETUP

• A license (.lic file) is required to operate Particleworks for Ansys extension.

• If the license cannot be checked out correctly, a dialog shows the error message while no further
operations can be executed on Ansys Workbench.
• For details of licenses of Particleworks, see Particleworks InstallGuide

17
Particleworks for Ansys Manual, Release 1.4.0

18 Chapter 7. License Setup

 CHAPTER

EIGHT

OPERATION: PARTICLEWORKS-MECHANICAL ONE-WAY

COUPLING

Each section explains procedures for Fluid-Structural/Thermal one-way coupling simulation through Parti-
cleworks for Ansys.
• Ansys Workbench, Part I: import/create geometry data for simulations (and Mapping)
• Particleworks : not be covered here. See Particleworks UserManual.
• Ansys Workbench, part II: import mapping result
• Ansys Mechanical: execute Structural/Thermal analysis

8.1 Operation in Ansys Workbench: part I

8.1.1 Creating and Saving Geometry Data

1. Create a new project for Ansys Workbench.

2. Create Particleworks for Ansys workflow and Structural/Thermal workflow onto Project Schematic by
dragging icons from Toolbox.
3. Link Geometry and Particle Mapping of Particleworks for Ansys workflow to Geometry and Setup
task of Structural/Thermal workflow, respectively.

Fig. 1: Workflow creation example

19
Particleworks for Ansys Manual, Release 1.4.0

4. Right-click Geometry task of Particleworks for Ansys to create or import geometry.

• If the geometry is created then exported in Ansys, save geometry
• If the geometry is imported into then exported in Ansys, it is necessary to make sure that it can
generate mesh correctly in Ansys Mechanical before being exported to STL or OBJ file.
• All necessary geometry data files for Particleworks and Particleworks for Ansys simulation need
to be saved in dp0/PwModels.

Note: It is necessary to make sure that all geometry data files used in Particleworks (simulation and Map-
ping) are created or exported in the same unit system.

8.1.2 Generating and Saving Mesh as Mapping Geometry Data (Optional)

The saved geometry data (STL/OBJ file) in Creating and Saving Geometry Data usually has a low resolution
on an extended smooth surface. Therefore, Mapping function in Particleworks also has a low resolution.
To improve the simulation precision in Mechanical, it is necessary to generate finer meshes for Mapping
function. There are several ways to generate finer grids, such as:
• Generating facets and saving in STL or OBJ file in SpaceClaim
1. Go to Facets and set the appropriate size for facets.
2. Click Convert to generate facets.
3. Save the facets as a new STL/OBJ file.
• Generating meshes and saving in STL or OBJ file in Mechanical
1. Double-click Model task in Structural/Thermal workflow to open Mechanical.
2. Generate mesh for the created geometry and export the mesh into a new file.
3. Only the unit of length in ‘Meter’ is supported.
Remeshing can be done by other software. Save created geometry data for Mapping function in dp0/
PwModels.

8.1.3 Starting Particleworks

1. Invoke Particleworks license server before starting Particleworks.

2. Click Particleworks GUI task in Particleworks for Ansys workflow.
3. Select Property > Particleworks Start > Particleworks Version Selection.
4. Specify Particleworks path:
• v6: <install_path>/Particleworks.cmd
• v7: <install_path>/bin/app.viewer.float.exe
5. Double-lick Particleworks GUI task to start Particleworks.

20 Chapter 8. Operation: Particleworks-Mechanical One-way Coupling

 Particleworks for Ansys Manual, Release 1.4.0

8.2 Operation in Particleworks

The fluid simulation by Particleworks is executed externally. See Particleworks UserManual for details.

8.3 Operation in Ansys Workbench: Part II

Return to Ansys Workbench. Click Particle Mapping task to edit properties below:
• File Selection
– Number of Independent Mapping Surfaces
∗ The number of sets of mapping data on independent surfaces will be imported.
∗ These independent surfaces can be surfaces on the same object or different objects.
∗ Each surface requires manual input of its first mapping file path and corresponding mapping
model.
∗ The maximum number of imported independent mapping surfaces is 4.
– Initial Mapping File Path
∗ Specify the first mapping file path for a certain surface from dp0/PwProjects/
<Particleworks_Project>/<scene_name>/mapping/<mapping_name>.
∗ <mapping_name> is the name specified at Mapping runtime.
– Mapping Object
∗ Select the geometry file specified by Animation Reference at Mapping runtime.
∗ All existing geometry data in dp0/PwModels is displayed as a list.
– Transient Mapping Input:
∗ When disabled: averaged or instant mapping data file import. Only import the file specified
by Initial Mapping File Path for each surface.
∗ When enabled: transient mapping data file import. The imported files range from the file
specified by Initial Mapping File Path to the final one in the same folder for each surface.
· Reading Cadence: input mapping data file reading cadence. The default value is 1.
• Mapping Data Coordinate Adjustment (optional)
– Adjust Mapping Coordinate:
∗ When disabled: no coordinate adjustment of mapping data relative to Mapping Object.
∗ When enabled: enables coordinate adjustment of mapping data relative to Mapping Object.
· Adjust by dX/dY/dZ: input translational shift distance along the X/Y/Z direction in the
same unit as Mapping Object.
• Heat Transfer from Ambient Air to Solid (Only Valid in Thermal Analysis) (optional)

8.2. Operation in Particleworks 21

Particleworks for Ansys Manual, Release 1.4.0

– Include Heat Transfer from Ambient Air to Solid (Common): valid only when the tempera-
ture and HTC are included in the mapping data.
∗ When disabled: Disables the heat transfer from the ambient air to the solid on either surface
where Particleworks mapping data is imported. The temperature and HTC at the position
where no fluid exists are set to be 22℃ and 0℃, respectively.
∗ When enabled: Enables the heat transfer from the ambient air to the solid on all surfaces
where Particleworks mapping data is imported.
· HTC of Ambient Air to Solid (Unit = W m^-2 K^-1): input a common HTC value of
the heat transfer from the ambient air to the solid at the position where no fluid exists.
· Ambient Air Temperature (Unit = ℃): input a common ambient air temperature at
the position where no fluid exists.
– Include Heat Transfer from Ambient Air to Solid (Independent): valid only when the tem-
perature and HTC are included in the mapping data.
∗ When disabled: Disables the heat transfer from the ambient air to the solid on either surface
where Particleworks mapping data is imported. The temperature and HTC at the position
where no fluid exists are set to be 22℃ and 0℃, respectively.
∗ When enabled: Enables the heat transfer from the ambient air to the solid on all surfaces
where Particleworks mapping data is imported.
· The following two inputs are added to File Selection > Mapping Object.
· HTC of Ambient Air to Solid - # (Unit = W m^-2 K^-1): input an HTC value of the
heat transfer from the ambient air to the solid at the position where no fluid exists in
the imported Particleworks mapping data. The HTC number corresponds to each set of
imported mapping data.
· Ambient Air Temperature - # (Unit = ℃): input an ambient air temperature at the
position where no fluid exists in the imported Particleworks mapping data. The ambient
air temperature number corresponds to each set of imported mapping data.
By right-clicking Particle Mapping task and selecting Update, the mapping data is imported to Ansys. The
progress of updating can be tracked by clicking Show Progress.

Note:
• In Particleworks for Ansys, each mapping surface is automatically named by the name of its corre-
sponding mapping object.
• In order to differentiate surfaces on the same mapping object, a number counts from 0 is also used in
the surface name labeling.

Once the task is updated, outputs are refreshed in Properties > Outputs (Units) and Outputs (Files):
• Outputs (Units)
– Length Unit: the length unit used in Particleworks simulation.
– Angle Unit: the angle unit used in Particleworks simulation.

22 Chapter 8. Operation: Particleworks-Mechanical One-way Coupling

 Particleworks for Ansys Manual, Release 1.4.0

– Temperature Unit: the temperature unit used in Particleworks simulation. Only Celsius is sup-
ported.
• Outputs (Files)
– Output Path: the path of the folder contains all outputs from Particleworks for Ansys.
∗ PwMappingconfiguration.xml: the configuration file of all mapping data.
∗ <SurfaceName>_PwMappingtxtdata_######.txt: the mapping data, where ‘######’ corre-
sponds to the file number.
∗ <SurfaceName>_PwHTClist.txt: the HTC and temperature file list. This is created only
when HTC data exists.
∗ <ModelName>_PwPolygonT.txt: contains solid (polygon) temperature of the corresponding
mapping model and unit set in Particleworks. This is created only when HTC data exists.
∗ <SurfaceName>_PwPressureList.txt: the pressure file list.
∗ <SurfaceName>_PwTimeList.txt: the time list of mapping data.
– Number of Mapping Files / Set: the number of mapping files in each set imported to Ansys.
– Pressure: the flag of pressure data existence in the imported mapping files.
– Heat transfer coefficient: the flag of HTC in the imported mapping files. If Data exists is
shown, thermal analysis is executable in Ansys.
– Mapping Object Temperature (Unit = ℃): the solid temperature set in Physics > Details >
Initial Temperature in Particleworks for each object.
Double-click Setup task in Structural/Thermal workflow to start Mechanical.

8.4 Operation in Ansys Mechanical

After Particleworks for Ansys is installed, two buttons and are shown in the group Particle
Mapping in the toolbar of Mechanical. The Imported Load object in the tree needed to be active by clicking
Imported Load in the tree before clicking these two buttons.

8.4.1 Analysis Settings

By clicking , the following actions are executed automatically.

• Imported loads are added to Imported Load folder.
• Structural analysis
– PwImportPressure_SurfaceName: Imported Pressure corresponds to the pressure mapping
on the surface named SurfaceName. Details of “PwImportPressure_SurfaceName” > Defini-
tion > Tabular Loading = Ramped is set.

8.4. Operation in Ansys Mechanical 23

Particleworks for Ansys Manual, Release 1.4.0

• Thermal analysis
– PwImportHTC_SurfaceName: Imported Convection corresponds to the HTC and tem-
perature (fluid and ambient air) on the surface named SurfaceName. Details of “PwIm-
portHTC_SurfaceName” > Definition > Tabular Loading = Ramped is set.
– PwImportSolidT_ModelName: Imported Temperature corresponds to the temperature of the
object named ModelName. Details of “PwImportSolidT_ModelName” > Definition > Apply
As = Initial Condition is set.
• Analysis Settings > Tabular Data is imported from SurfaceName0_PwTimeList.txt, where Surface-
Name0 is the surface that corresponds to Initial Mapping File Path - 1.
• Details of “Analysis Settings” > Step Controls of all steps is set as:
– Auto Time Stepping: Off
– Define By: Substeps
– Number of Substeps: 1
End Time in Tabular Data and Number of Substeps in Details of “Analysis Settings” > Step Controls
are as below:
• Transient Mapping Input is disabled:
– Number of Steps = 1:
∗ End Time: 1 [s]
• Transient Mapping Input is enabled:
– Number of Steps = 𝑛:
∗ End Time: ∼ 𝑛 × 𝑑𝑡0
where 𝑑𝑡0 is the mapping file reading time cadence into Ansys.
Further change of Analysis Settings or Imported Load is available by manual input.

Note:
• The list time in Tabular Data is shifted from the original mapping file time output from Particleworks.
– initial mapping file number = 0: all times are shifted by 𝑑𝑡0 forwards, as files must be imported
from non-zero time into Mechanical.
– initial mapping file number ̸= 0: all times are shifted by 𝑡init (initial mapping file time) backward
then 𝑑𝑡0 forwards.
• Do NOT change the name of Imported Loads before clicking Import List.

24 Chapter 8. Operation: Particleworks-Mechanical One-way Coupling

 Particleworks for Ansys Manual, Release 1.4.0

8.4.2 Importing Mapping Data

Click each imported load and wait until the table of Data View shows. Click in the toolbar to load
tabular data for the specified imported load. The tabular data can be viewed from Data View:
• Structural analysis
– PwImportPressure_SurfaceName: data is imported from SurfaceName_PwPressureList.txt
∗ Magnitude: a list of pressure files and data identifiers.
∗ Analysis Time: a time list, which is the same as Details of “Analysis Settings” > Tabular
Data.
• Thermal analysis
– PwImportHTC_SurfaceName: data is imported from SurfaceName_PwHTCList.txt
∗ Film Coefficient: a list of HTC files and data identifiers.
∗ Ambient Temperature: a list of temperature files and data identifiers.
∗ Analysis Time: a time list, which is the same as Details of “Analysis Settings” > Tabular
Data.
– PwImportSolidT_ModelName:
∗ Magnitude: the initial temperature file of the object.
∗ Analysis Time: 0, since it is set to be an initial condition.
After defining Scope > Geometry, right-click the imported load and update if no further edition on the im-
ported load is needed. Check the result of mapping in Mechanical with Particleworks. Apply other necessary
conditions before executing Structural/Thermal analysis.

8.4. Operation in Ansys Mechanical 25

Particleworks for Ansys Manual, Release 1.4.0

26 Chapter 8. Operation: Particleworks-Mechanical One-way Coupling

 CHAPTER

NINE

OPERATION: FLUENT-PARTICLEWORKS ONE-WAY COUPLING

Each section explains procedures for Airflow-Fluid one-way coupling simulation through Particleworks for
Ansys.
• Fluent: execute airflow simulation
• Ansys Workbench: import and convert airflow data
• Particleworks: execute fluid simulation by applying air resistance model

9.1 Operation in Fluent

9.1.1 Calculating Airflow in Fluent

Create Fluent workflow onto Project Schematic by dragging from Toolbox. See Fluent manual for detailed
operations in calculating airflow.

9.1.2 Exporting Airflow Data

1. Click File > Export > Solution Data. . . to export airflow data calculated by Fluent.
2. The required settings in Export window are as follows:
• File Type: ASCII
• Location: Cell Center
• Delimiter: Comma
• Quantities: X/Y/Z Velocity
3. Click Write. . . .
4. Name the airflow data, and click OK to save the file in the selected path.

Note: Note that the export settings need to be specified before executing transient Fluent simulation.

27
Particleworks for Ansys Manual, Release 1.4.0

9.2 Operation in Ansys Workbench

9.2.1 Converting Fluent Airflow Data

1. Create Particleworks for Ansys workflow onto Project Schematic by dragging from Toolbox.
2. Click Airflow Generation/Conversion task to edit properties.
3. The input properties are:
• Airflow Data Generation Type
– Airflow Data Generation/Conversion:
∗ Fluent Airflow Conversion: converting Fluent airflow data.
∗ Uniform Airflow Generation: generating an airflow dataset with a uniform velocity field.
• Input Airflow Data Settings (Fluent)
– Initial Airflow File Path: specify the first airflow data path, which was output by Fluent.
– Transient Airflow Input:
∗ When disabled: steady, averaged, or instant airflow import; only import the file identified
by Initial Airflow File Path.
∗ When enabled: transient airflow import; the imported files range from the file identified by
Initial Airflow File Path to the final one in the same folder.
· Airflow Calculation Time Step (Unit = sec): input the value of Time Step Size (s) in
Fluent.
· Reading Cadence: input Fluent airflow data file reading cadence. The default value is
1.
– Domain Clipping > Domain Clipping (X/Y/Z-direction):
∗ When disabled: all Fluent airflow data points along X/Y/Z-direction will be used in the
conversion.
∗ When enabled: the Fluent airflow data points inside the clipped range along X/Y/Z-direction
will be used in the conversion.
· Clipped X/Y/Z min (Unit = m): the lower threshold of the clipped range along X/Y/Z-
direction. The length unit is meter.
· Clipped X/Y/Z max (Unit = m): the upper threshold of the clipped range along X/Y/Z-
direction. The length unit is meter.
– Direct Mesh Size Input (Optional): the length used to determine the bucket size.
∗ When disabled: an averaged mesh size in Fluent airflow data spatial distribution will be
roughly estimated.

28 Chapter 9. Operation: Fluent-Particleworks One-way Coupling

 Particleworks for Ansys Manual, Release 1.4.0

∗ When enabled: the input value of Largest Mesh Size (Approximate Input, Unit = m) will
be used. This is the largest mesh size of Fluent airflow spatial distribution. The length unit
is meter.
• Converted Airflow Data Settings (Particleworks)
– Data Output Folder: specify the path for the converted airflow data.
– Length Unit: the length unit used in Particleworks simulation.
– Re-plot Airflow onto Uniform Grids:
∗ When disabled: Fluent airflow data will be directly converted into files compatible with
Particleworks without uniformizing the spatial distribution.
∗ When enabled: Fluent airflow data will be re-plotted onto spatially uniform grids in the data
range.
· Uniform Grid Size: uniform grid size of spatially uniformed Fluent airflow data.
· Number of Threads for Parallelization: input the number of threads for parallelization
in re-plotting. The default value is the number of physical cores in the local machine.
· Advanced Setup (Optional) > Largest Airflow Data Point Detection Range (multi-
ple of grid size): the value which determines the maximum airflow data point detection
range when re-plotting Fluent airflow data from non-uniform meshes to uniform grids.
This number is dimensionless and the multiple of Converted Airflow Data Settings
(Particleworks) > Uniform Grid Size. The default value is 5.
· Advanced Setup (Optional) > Maximum Neighboring Airflow Data Points: the
value determines the number of sampling points for re-plotting. The default value is
16.
– Re-scale Airflow:
∗ When disabled: the airflow data will be converted with its original length scale and velocity.
∗ When enabled: the coordinates and the velocity fields of the airflow data can be re-scaled.
· Length Multiple: input the multiple 𝑚𝐿 for re-scaling the length that all coordinates
are multiplied by 𝑚𝐿 after the conversion.
· Velocity Multiple: input the multiple 𝑚𝑉 for re-scaling the velocity field that all veloc-
ity components are multiplied by 𝑚𝑉 after the conversion.
– Mirror Airflow:
∗ When disabled: the original airflow data will be converted.
∗ When enabled: copy the original airflow data and mirror it about the specified mirror plane.
The output will be the combination of the original airflow data and that of mirrored data.
· Mirror Plane: select the mirror plane.
· Mirror Plane Position: input the position of the mirror plane along its perpendicular
direction. The mirror plane must be outside of the original airflow data.

9.2. Operation in Ansys Workbench 29

Particleworks for Ansys Manual, Release 1.4.0

• Created Airflow Data Settings (Particleworks): only shown if Uniform Airflow Generation is
selected.
– Data Output Folder: specify the path for the created airflow data.
– Length Unit: the length unit used in Particleworks simulation.
– Uniform Grid Size: uniform grid size in the unit of Length Unit.
– Uniform Airflow Vx/Vy/Vz (Unit = m/s): uniform airflow velocity.
– Range X/Y/Z min: the lower threshold of the airflow spatial range along X/Y/Z-direction in the
unit of Length Unit.
– Range X/Y/Z max: the upper threshold of the airflow spatial range along X/Y/Z-direction in the
unit of Length Unit.
After updating the task, outputs are refreshed in Property > Outputs (Fluent) and Outputs (Particleworks):
• Outputs (Fluent)
– Data Range (X/Y/Z-direction):
∗ the spatial range of Fluent airflow data for conversion along X/Y/Z-direction.
∗ The returned value is in the format of ‘[X/Y/Z min, X/Y/Z max] (Unit = m/mm).’
∗ The unit system is determined in Converted Airflow Data Settings (Particleworks) >
Length Unit.
– Number of Fluent Airflow Data File(s): the number of Fluent airflow files for conversion.
– Number of Fluent Airflow Data Points / File: the number of data points in each imported
Fluent airflow file for conversion.
– Bucket Size: the approximate length of a bucket along X/Y/Z-direction. The returned value is
in the format of ‘bucket size (Unit = m/mm).’
∗ Direct Mesh Size Input (Optional): When disabled: 4× (the estimated averaged mesh size
in Fluent airflow data).
∗ Direct Mesh Size Input (Optional): When enabled: 4× (the unit converted value input in
Largest Mesh Size (Approximate Input, Unit = m)).
– Number of Buckets: the number of sub-domains that are used at re-plotting. The returned
value is in the format of ‘(number of buckets along X-direction) × (number of buckets along
Y-direction) × (number of buckets along Z-direction) = (total number of buckets)’.
• Outputs (Particleworks)
– Total Calculation Time: the total time cost for converting Fluent airflow data. The unit is
second. The returned value is in the format of ‘total calculation time (seconds).’
– Data Range (X/Y/Z-direction): the spatial range of converted airflow data to be imported into
Particleworks. The returned value is in the format of ‘[X/Y/Z min, X/Y/Z max] (Unit = m/mm)’.
– Number of Files (List + Data): the number of sampling data files (PwAirflow_data_####.
csv) plus the description file (PwAirflow_file.csv).

30 Chapter 9. Operation: Fluent-Particleworks One-way Coupling

 Particleworks for Ansys Manual, Release 1.4.0

– Number of Grids / File: the number of converted airflow data points in each sampling file
(PwAirflow_data_####.csv).
– Number of Grids with Few Neighboring Fluent Data Points (less than 4): the total number
of re-plotted airflow data points which have few neighboring Fluent data points (less than 4) in
the calculation of re-plotting.
The generated files by the conversion are saved in the sub-folder under Data Output Folder. The contents
are listed as follows:
• Data Output Folder: the specified output folder in Properties.
– PwAir_yyyymmdd_hhmmss: a sub-folder contains the converted airflow data, while the name is
labeled by the date and time when the conversion started.
∗ PwAirflow_data_####.csv: a sampling data file describes airflow velocity at the corre-
sponding time.
∗ PwAirflow_file.csv: a file that describes the relationship between the sampling data file
and its corresponding time.
∗ FF2Pw_FileList.txt: a list of converted Fluent airflow data files.
∗ FF2Pw_Settings.txt: a list of settings in Airflow Generation/Conversion task.
∗ FF2Pw_ExternalLog.txt: a log file of the external converter.

9.2.2 Starting Particleworks

See Starting Particleworks.

Note:
• It is recommended to maintain the converted airflow file size to be < 2GB. If the converted airflow
file size is larger, please consider using Domain Clipping to remove the unnecessary part or set larger
Uniform Grid Size.
• It is recommended to set Uniform Grid Size to be less than 1/3 of the typical length of the narrow-
est flow path considered in the simulation. If Uniform Grid Size is much smaller than the largest
mesh size in the Fluent airflow data, please consider enlarging Largest Airflow Data Point Detection
Range (multiple of grid size) to make sure that sufficient Fluent airflow points can be referred in the
conversion.
• For a highly non-uniformly distributed Fluent airflow data set, if Direct Mesh Size Input is disabled
or the input value of Largest Mesh Size is inappropriate, Bucket Size might be comparable to or even
smaller than the practically largest mesh size in the whole domain. In buckets where Fluent airflow data
distribution is sparse, it is likely that too few Fluent airflow data can be referred to in the re-plotting.
Thus Number of Grids with Few Neighboring Fluent Data Points (less than 4) will return a large
value, and the conversion in these buckets may give an incorrect result. If the fluid-air interaction is
considered to be important also in the region where airflow data is sparse, please check Direct Mesh
Size Input and input larger value of Largest Mesh Size to make sure that sufficient Fluent airflow
points can be referred in each bucket during the re-plotting.

9.2. Operation in Ansys Workbench 31

Particleworks for Ansys Manual, Release 1.4.0

• Increasing/Decreasing Largest Mesh Size will increase/decrease the re-plotting accuracy and the cal-
culation time simultaneously.
• All input values of length in Input Airflow Data Settings (Fluent) should be in the unit of meter.
All input values of length in Converted Airflow Data Settings (Particleworks) should be in the unit
of Converted Airflow Data Settings (Particleworks) > Length Unit.
• All returned values of length in Outputs (Fluent) and Outputs (Particleworks) are shown in the unit
of Converted Airflow Data Settings (Particleworks) > Length Unit.
• Fluent does not output airflow data at 𝑡 = 0. However, when Repeat Airflow Data is selected, Particle-
works requires an input of a sampling file at 𝑡 = 0. So in the case that Transient Airflow Input is se-
lected, a sampling file PwAirflow_data_0000.csv with 𝑣 = 0 is generated automatically by Airflow
Generation/Conversion task. The corresponding time of each sampling file in PwAirflow_file.
csv is adjusted by considering the time of the file identified by Initial Airflow File Path and the time
difference between the first two converted files. Meanwhile, PwAirflow_file.csv can be edited
manually.

9.2.3 Importing and Setting Airflow Data

See Airflow in Particleworks UserManual.

9.2.4 Executing Simulation and Checking Result

See Running Simulation and Visualization in Particleworks UserManual.

32 Chapter 9. Operation: Fluent-Particleworks One-way Coupling

 CHAPTER

TEN

TUTORIALS

Tutorials are saved in <install_path>/share/samples/AnsysIF.

33
Particleworks for Ansys Manual, Release 1.4.0

34 Chapter 10. Tutorials

 CHAPTER

ELEVEN

TECHNICAL SUPPORT

Please send the following log files to the support team if users need supports.
• Extension log file: copy the content of the log file in Menu bar > Extension > View Log File and save
it as a text file.
• FF2Pw_ExternalLog.txt: needed when the airflow conversion is executed.

35