ANSYS FENSAP-ICE User Manual

ANSYS, Inc. Release 2021 R1

Southpointe January 2021
2600 ANSYS Drive
Canonsburg, PA 15317 ANSYS, Inc. and
ansysinfo@[Link] ANSYS Europe,
Ltd. are UL
[Link] registered ISO
(T) 724-746-3304 9001: 2015
(F) 724-514-9494 companies.
Copyright and Trademark Information

© 2021 ANSYS, Inc. Unauthorized use, distribution or duplication is prohibited.

ANSYS, ANSYS Workbench, AUTODYN, CFX, FLUENT and any and all ANSYS, Inc. brand, product, service and feature
names, logos and slogans are registered trademarks or trademarks of ANSYS, Inc. or its subsidiaries located in the
United States or other countries. ICEM CFD is a trademark used by ANSYS, Inc. under license. CFX is a trademark
of Sony Corporation in Japan. All other brand, product, service and feature names or trademarks are the property
of their respective owners. FLEXlm and FLEXnet are trademarks of Flexera Software LLC.

Disclaimer Notice

THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFID-
ENTIAL AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software products
and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement
that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting
laws, warranties, disclaimers, limitations of liability, and remedies, and other provisions. The software products
and documentation may be used, disclosed, transferred, or copied only in accordance with the terms and conditions
of that software license agreement.

ANSYS, Inc. and ANSYS Europe, Ltd. are UL registered ISO 9001: 2015 companies.

U.S. Government Rights

For U.S. Government users, except as specifically granted by the ANSYS, Inc. software license agreement, the use,
duplication, or disclosure by the United States Government is subject to restrictions stated in the ANSYS, Inc.
software license agreement and FAR 12.212 (for non-DOD licenses).

Third-Party Software

See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software
and third-party software. If you are unable to access the Legal Notice, contact ANSYS, Inc.

Published in the U.S.A.

Table of Contents
1. Introduction ........................................................................................................................................... 1
1.1. Known Limitations in ANSYS FENSAP-ICE 2020 R2 ............................................................................. 1
1.2. List of Symbols ................................................................................................................................. 1
1.3. About ANSYS .................................................................................................................................... 4
1.4. The ANSYS Product Improvement Program ....................................................................................... 5
1.5. FENSAP-ICE System ........................................................................................................................... 9
1.5.1. Flow Solver (FENSAP) ............................................................................................................... 9
1.5.2. Mesh Adaptation and CAD Reconstruction (OptiGrid) ............................................................. 10
1.5.3. Water Droplet/Ice Crystal Impingement (DROP3D) .................................................................. 10
1.5.4. Ice Accretion and Water Runback (ICE3D) ................................................................................ 11
1.5.5. Conjugate Heat Transfer (CHT3D, C3D) .................................................................................... 11
[Link]. Icing Simulations ........................................................................................................... 11
1.6. FENSAP-ICE-TURBO ......................................................................................................................... 13
1.7. Layout of this Manual ...................................................................................................................... 13
1.8. Contact Information ........................................................................................................................ 14
2. The FENSAP-ICE Project Manager ........................................................................................................ 15
2.1. The Project Manager ....................................................................................................................... 15
2.1.1. Create a New Project .............................................................................................................. 16
2.1.2. Open an Existing Project ........................................................................................................ 17
2.1.3. Display Projects ...................................................................................................................... 17
2.1.4. Assign Units to a Project ......................................................................................................... 17
2.1.5. Close a Project ....................................................................................................................... 18
2.1.6. Mouse Options ....................................................................................................................... 19
2.2. The Run Manager ............................................................................................................................ 19
2.2.1. Create a New Run ................................................................................................................... 19
2.2.2. List of Runs ............................................................................................................................ 20
2.2.3. Chronological and Hierarchical Views ..................................................................................... 22
2.2.4. Search Box ............................................................................................................................. 23
2.2.5. Select a File, Drag & Drop or Copy-Paste .................................................................................. 24
2.2.6. Archive a Calculation .............................................................................................................. 25
2.2.7. Mouse Options ....................................................................................................................... 25
2.2.8. Information and Properties ..................................................................................................... 27
2.3. The Grid File .................................................................................................................................... 28
2.3.1. Cylindrical to Cartesian Coordinates Conversion ...................................................................... 29
2.3.2. Converting the Grid Coordinates to Meters ............................................................................. 29
2.3.3. Importing a Grid from Fluent or Other Solvers ......................................................................... 29
2.3.4. Menu Options ........................................................................................................................ 30
2.4. Input Parameters ............................................................................................................................ 31
2.5. Solution Files .................................................................................................................................. 32
2.5.1. List of Output Files ................................................................................................................. 32
2.5.2. Post-Processing ...................................................................................................................... 34
2.5.3. Mouse Options ....................................................................................................................... 35
2.6. Preferences ..................................................................................................................................... 37
2.6.1. Font Size ................................................................................................................................ 37
2.7. Quit FENSAP-ICE ............................................................................................................................. 37
3. The FENSAP-ICE Solver Manager .......................................................................................................... 39
3.1. The Graphical Window .................................................................................................................... 40
3.1.1. Graphical Display ................................................................................................................... 40
3.1.2. Add/Remove Details from View .............................................................................................. 41

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. iii
User Manual

[Link]. Remove/Activate the Graphical Display .......................................................................... 41

[Link]. Full and Simple Views .................................................................................................... 41
[Link]. Configure ...................................................................................................................... 42
[Link]. Axis Display and Alignment ........................................................................................... 42
[Link]. Fit to View ..................................................................................................................... 43
[Link]. Apply Translational and Rotational Periodicity ................................................................ 43
[Link]. Panning/Rotation .......................................................................................................... 45
[Link]. Selection ....................................................................................................................... 45
3.1.3. Advanced Graphical Operations ............................................................................................. 45
3.2. The Run Window ............................................................................................................................. 45
3.2.1. Calculation Settings ............................................................................................................... 46
[Link]. Parallel Calculations ....................................................................................................... 46
[Link]. Queuing Systems ........................................................................................................... 48
[Link]. Save Your Preferences .................................................................................................... 48
3.2.2. Start the Calculation ............................................................................................................... 48
[Link]. Compute Drag Polar Curves ........................................................................................... 48
3.2.3. Monitoring a Run ................................................................................................................... 49
[Link]. The Solver Log File ......................................................................................................... 50
[Link]. The Convergence Graphs ............................................................................................... 50
4. FENSAP - Flow Solution ......................................................................................................................... 53
4.1. The Physical Model ......................................................................................................................... 53
4.1.1. Grid File Assignment .............................................................................................................. 53
4.1.2. The Continuity and Momentum Equations .............................................................................. 54
4.1.3. The Energy Equation .............................................................................................................. 55
[Link]. Adiabatic Flows ............................................................................................................. 55
[Link]. Conservative Energy Equation ....................................................................................... 56
[Link] Flows ...................................................................................................................... 56
[Link]. The Spalart-Allmaras Model ........................................................................................... 56
[Link]. The Low Reynolds k-ω Model ......................................................................................... 58
[Link]. The k-ω SST Model ......................................................................................................... 59
4.1.5. Surface Roughness ................................................................................................................. 60
[Link]. Sand-Grain Roughness .................................................................................................. 60
[Link]. The NASA Roughness Model .......................................................................................... 60
[Link]. The Shin et al. Roughness Model .................................................................................... 61
[Link]. Variable Roughness from a File ....................................................................................... 61
[Link]. Variable Roughness from the Boundary Conditions ........................................................ 62
[Link]. Variable Roughness from the Beading Model ................................................................. 62
4.1.6. Transition to Turbulence ......................................................................................................... 62
4.1.7. Body Forces ........................................................................................................................... 64
[Link]. Gravity .......................................................................................................................... 64
[Link]. Rotating Frame of Reference .......................................................................................... 66
4.2. Flow Conditions .............................................................................................................................. 67
4.2.1. Reference Conditions ............................................................................................................. 67
4.2.2. Setting Pressure from Altitude ................................................................................................ 69
4.2.3. Initial Solution ........................................................................................................................ 69
[Link]. Velocity Components ..................................................................................................... 70
[Link]. Velocity Angles .............................................................................................................. 70
[Link]. Displaying the Initial Velocity Vector ............................................................................... 72
4.2.4. Restarting a Calculation .......................................................................................................... 72
4.3. Boundary Conditions ...................................................................................................................... 73
4.3.1. Inlets and Far-fields – 1000-BCs ............................................................................................... 74

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
iv of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

[Link]. Subsonic ....................................................................................................................... 75

[Link]. Supersonic or Far-Field .................................................................................................. 75
[Link]. Stagnation .................................................................................................................... 76
[Link]. Mass Flow ..................................................................................................................... 77
[Link]. Riemann ........................................................................................................................ 77
[Link]. Engine Inlet – Mass Flow Rate ........................................................................................ 78
[Link]. Engine Inlet – Mach Number .......................................................................................... 78
[Link]. From Restart .................................................................................................................. 79
4.3.2. Walls – 2000-BCs .................................................................................................................... 79
[Link]. No-Slip .......................................................................................................................... 79
[Link]. Slip ................................................................................................................................ 79
[Link]. Sand-Grain Roughness Distribution on a Wall ................................................................. 80
[Link]. Rotating Walls (Axisymmetric) ........................................................................................ 80
4.3.3. Exits and Outlets – 3000-BCs ................................................................................................... 81
[Link]. Subsonic ....................................................................................................................... 82
[Link].1. Radial Equilibrium ................................................................................................. 82
[Link]. Supersonic .................................................................................................................... 83
[Link]. Mass Flow ..................................................................................................................... 83
[Link]. From Restart .................................................................................................................. 84
4.3.4. Symmetry – 4000-BCs ............................................................................................................ 84
4.3.5. Periodic – 5000-BCs ................................................................................................................ 85
4.3.6. Internal Surfaces – 6000-BCs ................................................................................................... 85
[Link]. Actuator Disks ............................................................................................................... 85
[Link]. Screen Models ............................................................................................................... 88
[Link].1. Pressure Drop from Brundrett ................................................................................ 90
[Link].2. Pressure Drop from Idelchik, Diagram 8-1 .............................................................. 90
[Link].3. Pressure Drop from Idelchik, Equation 8-3 .............................................................. 90
[Link]. Disabled (Transparent) Boundary Conditions ................................................................. 91
4.3.7. Non-Conformal Interfaces – 7000-BCs ..................................................................................... 91
4.3.8. Importing Boundary Conditions from Reference Conditions .................................................... 92
4.3.9. Boundary Conditions Varying in Space .................................................................................... 92
[Link]. Inlet Profiles for Turbulence ............................................................................................ 94
4.4. Domains ......................................................................................................................................... 94
4.4.1. Unsteady Rotor-Fuselage Interaction ...................................................................................... 95
[Link]. Initial Rotor Acceleration ................................................................................................ 96
4.4.2. Multi-Domain Initialization ..................................................................................................... 97
4.5. Solver Parameters ........................................................................................................................... 99
4.5.1. Steady-State Flows ................................................................................................................. 99
[Link]. Variable Relaxation ...................................................................................................... 100
4.5.2. Unsteady Flows .................................................................................................................... 101
[Link]. Constant Time Stepping ............................................................................................... 101
[Link]. Dual-Time Stepping ..................................................................................................... 101
4.5.3. Artificial Dissipation ............................................................................................................. 102
[Link]. The Streamline Upwind (SU) Scheme ............................................................................ 102
[Link]. Streamline Upwind for Shocks ..................................................................................... 103
[Link]. Central Schemes .......................................................................................................... 103
4.5.4. Advanced Solver Settings ..................................................................................................... 104
[Link]. Residual Convergence ................................................................................................. 104
[Link]. Dissipation Scaling ...................................................................................................... 104
[Link]. Solver Settings ............................................................................................................. 105
4.6. Output ......................................................................................................................................... 106

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. v
User Manual

4.6.1. Log Files ............................................................................................................................... 107

4.6.2. Solution File ......................................................................................................................... 107
4.6.3. Extended Icing Data (EID) ..................................................................................................... 107
4.6.4. ALE Formulation ................................................................................................................... 109
4.6.5. Lift, Drag and Moments ........................................................................................................ 109
4.6.6. Probe Point Interpolation ..................................................................................................... 111
5. DROP3D - Droplet and Ice Crystal Impingement ................................................................................ 113
5.1. The Physical Model ....................................................................................................................... 113
5.1.1. Assigning the Grid and Air Solution Files ............................................................................... 113
5.1.2. The Particle Transport ........................................................................................................... 114
5.1.3. Particle Drag Correlations ..................................................................................................... 114
5.1.4. Ice Crystal Drag Correlations ................................................................................................. 116
5.1.5. Droplets and Crystals ........................................................................................................... 117
5.1.6. Vapor Transport Equation ..................................................................................................... 117
[Link]. Vapor Nucleation ......................................................................................................... 118
[Link].1. Introduction ....................................................................................................... 118
[Link].2. Model Description .............................................................................................. 118
[Link].3. Activating Nucleation in Vapor Transport ............................................................. 119
[Link].4. Capturing Supersaturation .................................................................................. 122
5.2. Supercooled Large Droplets (SLD) ................................................................................................. 122
5.2.1. Droplet Break-Up ................................................................................................................. 123
5.2.2. Droplet Deformation ............................................................................................................ 125
5.2.3. Splashing and Bouncing by Post-Processing ......................................................................... 125
5.2.4. Splashing and Bouncing by Body Force ................................................................................. 126
5.2.5. Mundo Model ...................................................................................................................... 127
[Link]. Splashing .................................................................................................................... 127
[Link]. Bouncing ..................................................................................................................... 128
5.2.6. Honsek-Habashi Model ........................................................................................................ 128
[Link]. Splashing .................................................................................................................... 128
[Link]. Bouncing ..................................................................................................................... 128
[Link]. Spreading or Disintegration ......................................................................................... 129
5.2.7. Wright-Potapczuk Model ...................................................................................................... 129
[Link]. Splashing .................................................................................................................... 129
[Link]. Bouncing ..................................................................................................................... 130
5.2.8. Terminal Velocity .................................................................................................................. 130
5.3. Particle Conditions ........................................................................................................................ 131
5.3.1. Reference Flow Conditions ................................................................................................... 131
5.3.2. Droplets Reference Conditions ............................................................................................. 132
5.3.3. Ice Crystals Reference Conditions .......................................................................................... 135
5.3.4. Appendix C .......................................................................................................................... 135
5.3.5. Appendix O - Supercooled Large Droplets ............................................................................ 139
[Link]. Choosing the SLD Icing Condition ................................................................................ 142
[Link]. Choosing the SLD Droplet Distribution ......................................................................... 148
5.3.6. Appendix D - Ice Crystals ...................................................................................................... 153
5.3.7. Droplet Initial Solution ......................................................................................................... 158
5.3.8. Initial Velocity Display ........................................................................................................... 161
5.3.9. Restarting DROP3D .............................................................................................................. 162
5.4. DROP3D Boundary Conditions ...................................................................................................... 163
5.4.1. Inlets and Far Fields .............................................................................................................. 163
5.4.2. Vapor Transport – Wet Walls .................................................................................................. 164
5.4.3. LWC Reduction Across Screens ............................................................................................. 164

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
vi of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

5.5. Droplets Solver Parameters ........................................................................................................... 164

5.5.1. Steady-State Solution ........................................................................................................... 164
5.5.2. Artificial Viscosity ................................................................................................................. 165
5.5.3. Advanced Solver Settings ..................................................................................................... 166
[Link]. Convergence Criteria ................................................................................................... 166
[Link]. Dissipation Scaling ...................................................................................................... 166
5.6. Output ......................................................................................................................................... 166
5.6.1. Solution Files with SLD ......................................................................................................... 167
5.7. Particle Reinjection in External Flows ............................................................................................. 167
5.7.1. Crystal Reinjection in External Flows ..................................................................................... 168
5.7.2. SLD Reinjection .................................................................................................................... 169
5.8. The DROP3D Run Environment ...................................................................................................... 169
6. ICE3D - Ice Accretion and Water Runback ........................................................................................... 171
6.1. Governing Equations .................................................................................................................... 171
6.2. Icing Model ................................................................................................................................... 173
6.2.1. Grid and Air/Droplets Solution Files ...................................................................................... 173
6.2.2. Restart Conditions ................................................................................................................ 174
[Link]. Glaze Ice ...................................................................................................................... 175
[Link]. Rime Ice ...................................................................................................................... 175
[Link]. Water Film ................................................................................................................... 175
6.2.3. Extended Icing Data (EID) in ICE3D ........................................................................................ 176
[Link]. EID Setup for Versions Starting with R18.2 and Forward ................................................ 176
[Link]. EID Backward Compatibility with Pre-R18.2 Flow Solutions ........................................... 176
6.2.4. Concavity Check ................................................................................................................... 178
6.2.5. Sand-Grain Roughness Output ............................................................................................. 178
6.2.6. Impact of Beading ................................................................................................................ 179
6.2.7. Crystal Bouncing Models ...................................................................................................... 180
[Link]. NTI Bouncing Model .................................................................................................... 180
[Link]. NRC Bouncing Model ................................................................................................... 180
[Link]. Custom Bouncing Model ............................................................................................. 180
[Link]. User Defined Functions ................................................................................................ 180
[Link]. Variables ...................................................................................................................... 181
[Link]. UDF Syntax .................................................................................................................. 181
[Link]. Error Handling ............................................................................................................. 183
[Link]. UDF Template .............................................................................................................. 184
6.2.8. Body Forces .......................................................................................................................... 185
[Link]. Effect of Gravity ........................................................................................................... 185
[Link]. Rotating Frame of Reference ........................................................................................ 186
6.2.9. Ice Shedding on Rotating Components ................................................................................. 187
[Link]. Introduction ................................................................................................................ 187
[Link]. Ice Shedding Model in ICE3D ....................................................................................... 187
[Link]. Ice-Surface Interface .................................................................................................... 188
[Link]. Crack Detection Criteria ............................................................................................... 190
[Link]. Ice Material Properties ................................................................................................. 191
[Link]. Shedding Evaluation and Outputs ................................................................................ 191
6.3. Icing Conditions ............................................................................................................................ 192
6.3.1. Reference Air and Droplets Conditions .................................................................................. 192
[Link]. The Recovery Factor ..................................................................................................... 193
6.3.2. The Icing Parameters ............................................................................................................ 193
[Link]. The Icing Air Temperature ............................................................................................ 194
[Link]. Fluid Properties ........................................................................................................... 194

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. vii
User Manual

[Link]. Relative Humidity ........................................................................................................ 194

[Link]. Radiation ..................................................................................................................... 195
[Link]. Ice Density ................................................................................................................... 195
[Link]. Appendix C ................................................................................................................. 196
6.3.3. Advanced Settings ............................................................................................................... 196
6.4. Boundary Conditions .................................................................................................................... 196
6.4.1. Sink Boundaries ................................................................................................................... 197
6.4.2. Rotating Spinners ................................................................................................................. 197
6.4.3. Sliding Wall Boundaries ........................................................................................................ 198
6.5. Screen .......................................................................................................................................... 199
6.6. Solver ........................................................................................................................................... 202
6.6.1. Time Integration ................................................................................................................... 202
6.6.2. Maximum Ice Thickness ........................................................................................................ 203
6.7. Output ......................................................................................................................................... 204
6.7.1. Generate a 3D Displaced Grid ............................................................................................... 204
6.7.2. Compute IPS Load Requirements .......................................................................................... 205
7. C3D - Unsteady Heat Conduction ........................................................................................................ 209
7.1. The Physical Model ....................................................................................................................... 209
7.2. C3D Configuration ........................................................................................................................ 210
7.3. Settings ........................................................................................................................................ 210
7.3.1. Initial Conditions .................................................................................................................. 210
7.3.2. Electrothermal Model ........................................................................................................... 211
7.3.3. Thermostats ......................................................................................................................... 212
7.4. Properties ..................................................................................................................................... 212
7.5. Materials ....................................................................................................................................... 213
7.6. Boundary Conditions .................................................................................................................... 214
7.6.1. Walls .................................................................................................................................... 215
[Link]. Thermal Boundary Conditions ...................................................................................... 216
[Link]. Electrical Boundary Conditions .................................................................................... 218
7.6.2. Thermostat .......................................................................................................................... 218
7.6.3. Heater Pads .......................................................................................................................... 219
[Link]. Specified Heat Flux ...................................................................................................... 219
[Link]. Specified Power Density .............................................................................................. 220
7.7. Boundary Conditions Cycles .......................................................................................................... 221
7.7.1. Cycle .................................................................................................................................... 222
7.7.2. Functional Input .................................................................................................................. 222
7.7.3. Examples ............................................................................................................................. 223
7.7.4. Sequence ............................................................................................................................. 223
7.8. Numerical Parameters ................................................................................................................... 223
7.9. Output ......................................................................................................................................... 224
7.9.1. Temperature Probes ............................................................................................................. 224
8. CHT3D - 3D Conjugate Heat Transfer .................................................................................................. 225
8.1. Best Practices ................................................................................................................................ 225
8.2. CHT3D Run Settings ...................................................................................................................... 230
8.3. Dry Air Regime .............................................................................................................................. 233
8.3.1. Input Parameters .................................................................................................................. 233
8.3.2. Initial Flow Solutions ............................................................................................................ 235
8.4. Wet Air Regime ............................................................................................................................. 236
8.4.1. Input Parameters .................................................................................................................. 236
8.4.2. Initial Flow and Droplet Solutions ......................................................................................... 236
8.5. CHT3D Input Parameters ............................................................................................................... 237

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
viii of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

8.5.1. Anti-Icing Parameters ........................................................................................................... 237

8.5.2. De-Icing Parameters ............................................................................................................. 239
8.5.3. Domain Interfaces ................................................................................................................ 240
8.5.4. Reference Temperatures ....................................................................................................... 242
9. FENSAP-ICE-TURBO ............................................................................................................................. 245
9.1. Multi-Component Simulations ...................................................................................................... 246
9.1.1. Adding a Turbo Run .............................................................................................................. 247
9.1.2. The Turbo Panel .................................................................................................................... 249
[Link]. Grid File Assignment .................................................................................................... 249
[Link]. Specifying Component Rotation .................................................................................. 250
[Link]. Reviewing Periodicity .................................................................................................. 251
[Link]. Component Interfaces ................................................................................................. 251
[Link]. Advanced Settings ....................................................................................................... 252
9.1.3. Turbo Part ............................................................................................................................ 253
9.2. Airflow Through a Turbomachine .................................................................................................. 253
9.2.1. Physical Model for Static and Rotating Components .............................................................. 253
9.2.2. Airflow Setup in FENSAP-TURBO ........................................................................................... 255
[Link]. Reference Conditions ................................................................................................... 256
[Link]. Initial Conditions and Restarting a Calculation .............................................................. 256
9.2.3. Boundary Conditions ............................................................................................................ 257
[Link]. Engine Inlet ................................................................................................................. 258
[Link]. Counter-Rotating Walls ................................................................................................ 259
[Link]. Radial Equilibrium at the Exit Boundary ........................................................................ 260
9.2.4. Extended Icing Data for Turbomachinery Applications .......................................................... 260
9.2.5. Importing a CFX Flow Calculation ......................................................................................... 260
[Link]. Auto-Configure a Run from a CFX File ........................................................................... 261
9.3. Multiphase Droplet and Ice Crystal Simulations ............................................................................. 265
9.3.1. Assigning an Airflow Solution ............................................................................................... 266
9.3.2. The DROP3D-TURBO Physical Model ..................................................................................... 266
[Link]. The Particle Equations .................................................................................................. 267
[Link]. Particle Thermal Equation ............................................................................................ 267
9.3.3. Particle Reference Conditions ............................................................................................... 268
9.3.4. Particle Initial Solution .......................................................................................................... 268
[Link]. Initial Velocity Components ......................................................................................... 269
[Link]. Specifying Velocity Angles ........................................................................................... 269
[Link]. Vapor Initialization ....................................................................................................... 269
[Link]. Restarting from a Previous Solution .............................................................................. 269
[Link]. User Defined Input Profile ............................................................................................ 270
[Link]. Restart + Input Profile .................................................................................................. 270
[Link]. Dry Initialization .......................................................................................................... 271
9.4. Ice Accretion in Turbomachines ..................................................................................................... 271
9.4.1. ICE3D-TURBO Physical Models .............................................................................................. 272
[Link]. Icing on Rotating Components .................................................................................... 272
[Link]. Effect of Ice Crystals ..................................................................................................... 273
9.4.2. Boundary Conditions ............................................................................................................ 273
[Link]. Enabled and Disabled Walls ......................................................................................... 273
[Link]. Counter-Rotating Walls ................................................................................................ 273
[Link]. Sliding Wall Boundaries ................................................................................................ 277
[Link]. Water Pooling and Sinks ............................................................................................... 280
9.5. Computing Re-Injected Particles ................................................................................................... 281
9.5.1. Simplified Reinjection .......................................................................................................... 281

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. ix
User Manual

9.5.2. Complete Reinjection ........................................................................................................... 282

9.6. Output Files .................................................................................................................................. 282
9.7. Specification of Mixed-Type Boundary Conditions ......................................................................... 283
9.8. Completing a Run ......................................................................................................................... 286
10. Automated Sequences and Multishot Icing Calculations ................................................................. 289
10.1. Multishot Run Creation and Basic Configuration .......................................................................... 290
10.1.1. Creating the Run ................................................................................................................ 290
10.1.2. Defining the Input Grid ....................................................................................................... 293
10.1.3. Configuring the Solvers ...................................................................................................... 293
10.1.4. Setting up the Initial Solution ............................................................................................. 294
10.1.5. Multishot Primary Configuration ......................................................................................... 295
[Link]. Multishot Iterations ................................................................................................... 295
[Link]. Variable Values ........................................................................................................... 296
[Link]. Variables .................................................................................................................... 296
[Link]. Restart Types ............................................................................................................. 296
10.1.6. Execution ........................................................................................................................... 297
10.1.7. Post-Processing .................................................................................................................. 297
10.2. Multishot Icing Sequences .......................................................................................................... 298
10.2.1. Multishot with FENSAP ....................................................................................................... 298
[Link]. MULTI-FENSAP ........................................................................................................... 299
10.2.2. Multishot with Fluent ......................................................................................................... 300
[Link]. Input Grid Configuration ............................................................................................ 300
[Link]. Fluent Configuration .................................................................................................. 302
[Link]. Recommendations to Set up a Fluent Calculation ....................................................... 303
[Link]. DROP3D and ICE3D Configuration .............................................................................. 307
[Link]. Multishot Configuration ............................................................................................. 307
[Link]. Execution .................................................................................................................. 307
[Link]. Post-Processing ......................................................................................................... 308
10.2.3. Multishot with CFX ............................................................................................................. 309
[Link]. Input Grid Configuration ............................................................................................ 309
[Link]. CFX Configuration ..................................................................................................... 311
[Link]. Recommendations to Set up a CFX Calculation ........................................................... 312
[Link]. DROP3D and ICE3D Configuration .............................................................................. 320
[Link]. Multishot Configuration ............................................................................................. 320
[Link]. Execution .................................................................................................................. 320
[Link]. Post-Processing ......................................................................................................... 322
10.2.4. Multishot with Custom Remeshing ..................................................................................... 322
[Link]. Automatic Remeshing Using Fluent Meshing ............................................................. 323
10.3. Optigrid Feedback Loop .............................................................................................................. 332
11. FENSAP-ICE-Unsteady ....................................................................................................................... 333
11.1. Two-Phase Flows: Coupling Flow and Droplets ............................................................................. 333
11.1.1. The Physical Model ............................................................................................................. 334
11.1.2. Steady-State Multiphase Flows ........................................................................................... 334
11.1.3. Unsteady Multiphase Flows ................................................................................................ 335
[Link]. Constant Time Step .................................................................................................... 335
[Link]. Dual-Time Stepping ................................................................................................... 336
11.1.4. Output Files ....................................................................................................................... 336
11.2. Three-Phase Flows: Coupling Flow, Droplets and Ice ..................................................................... 337
11.2.1. Rime Ice ............................................................................................................................. 337
11.2.2. Glaze Ice ............................................................................................................................. 338
11.2.3. Output Files ....................................................................................................................... 338

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
x of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

11.2.4. View Ice Accretion in Time .................................................................................................. 339

11.3. Rime Ice Accretion on Screens ..................................................................................................... 339
11.3.1. Mass Loss in the Droplet Continuity Equation ...................................................................... 341
11.4. Rigid Motion ............................................................................................................................... 341
12. OptiGrid - Mesh Adaptation .............................................................................................................. 343
12.1. Theoretical Background .............................................................................................................. 343
12.1.1. Error Estimation in 1D ......................................................................................................... 343
12.1.2. Error Estimation in 3D ......................................................................................................... 344
12.1.3. Adaptation Strategies in 3D ................................................................................................ 345
[Link]. Node Movement ........................................................................................................ 346
[Link]. Refinement and Coarsening ....................................................................................... 346
[Link]. Edge Swapping .......................................................................................................... 347
12.1.4. Adaptation Sequence ......................................................................................................... 347
12.2. Input Files ................................................................................................................................... 348
12.2.1. Initial and Adapted Grids ................................................................................................... 348
12.2.2. Initial Flow Solution ............................................................................................................ 349
12.2.3. Assign Flow Variables for Error Estimation ........................................................................... 349
[Link]. Scalar Variables .......................................................................................................... 350
[Link]. Edit Variable Labels .................................................................................................... 351
[Link]. Guidelines ................................................................................................................. 352
12.2.4. Geometry (CAD) ................................................................................................................. 353
12.3. Boundaries ................................................................................................................................. 353
12.3.1. View and Edit the Boundary Surfaces .................................................................................. 353
12.3.2. Y+ Adaptation .................................................................................................................... 354
[Link]. Number of Layers ...................................................................................................... 354
[Link]. Y+ Label .................................................................................................................... 354
[Link]. Constraints on Hexahedral/Prismatic Elements ........................................................... 354
[Link]. Transition .................................................................................................................. 355
[Link]. Constraints on Tetrahedral Elements .......................................................................... 356
12.3.3. Advanced Options .............................................................................................................. 356
[Link]. Dead Zones ............................................................................................................... 356
[Link]. No-Slip Wall ............................................................................................................... 356
[Link]. Floating Periodicity .................................................................................................... 357
12.4. Adaptation Strategy .................................................................................................................... 357
12.4.1. Mesh Operations ................................................................................................................ 357
12.4.2. Number of Adaptation Iterations ........................................................................................ 358
12.4.3. Error Control ...................................................................................................................... 358
12.4.4. Advanced Options .............................................................................................................. 361
[Link]. Node Movement Algorithm ....................................................................................... 361
[Link]. Error Computation ..................................................................................................... 361
12.5. Mesh Constraints ........................................................................................................................ 362
12.5.1. Minimum and Maximum Edge Lengths ............................................................................... 362
12.5.2. Quality of Tetrahedral Elements .......................................................................................... 363
12.5.3. Quality of Prism Elements ................................................................................................... 363
12.5.4. Quality of Hexahedral Elements .......................................................................................... 364
12.5.5. Other Mesh Constraints ...................................................................................................... 364
12.6. Performing Mesh Adaptation ...................................................................................................... 366
12.6.1. Post-Processing the Adapted Grid ....................................................................................... 366
12.6.2. Viewmerical Display ........................................................................................................... 369
12.6.3. Solver-Adaptation Coupling ............................................................................................... 369
12.6.4. Tips for a Successful Adaptation .......................................................................................... 369

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. xi
User Manual

12.7. Troubleshooting ......................................................................................................................... 370

13. OptiGrid - CAD Reconstruction ......................................................................................................... 377
13.1. GUI-Assisted CAD Reconstruction ................................................................................................ 379
13.2. The CAD Reconstruction Process ................................................................................................. 379
13.2.1. Input/Output Geometry Files .............................................................................................. 380
13.2.2. Initial Edge Detection ......................................................................................................... 381
13.2.3. Edge Edition ....................................................................................................................... 381
13.2.4. View the Reconstructed CAD .............................................................................................. 383
13.2.5. CAD Attributes ................................................................................................................... 384
13.2.6. Periodicity .......................................................................................................................... 385
13.2.7. Save the Geometry File ....................................................................................................... 385
13.3. Advanced CAD Edition ................................................................................................................ 385
13.3.1. Edge Tolerance ................................................................................................................... 385
13.3.2. Edge Filtering ..................................................................................................................... 386
13.3.3. Edge Edition – Edge by Edge .............................................................................................. 388
13.3.4. Add a Group of Edges ......................................................................................................... 389
13.3.5. Prescribed Points ................................................................................................................ 391
13.3.6. Delete an Edge ................................................................................................................... 391
13.3.7. Refresh the Geometry ......................................................................................................... 391
14. FENSAP-ICE File Formats ................................................................................................................... 393
14.1. The Grid File - ASCII Format ......................................................................................................... 394
14.1.1. The Grid Header ................................................................................................................. 395
14.1.2. The Coordinate Table .......................................................................................................... 396
14.1.3. The Connectivity Table ........................................................................................................ 397
14.1.4. The Boundary Face Table .................................................................................................... 398
[Link] Domains Table ............................................................................................................. 399
14.2. The Grid File – Binary Format ....................................................................................................... 399
14.3. The FENSAP Solution File – Binary Format .................................................................................... 400
14.4. The Actuator Disk File .................................................................................................................. 403
14.5. The Probe Coordinate File ([Link]) .......................................................................................... 405
14.6. The Probe Output File ([Link]) ............................................................................................... 406
14.7. The [Link] file ...................................................................................................................... 407
14.8. The Sand-Grain Roughness Distribution File ([Link]) ........................................................ 408
15. Tools Reference ................................................................................................................................. 411
15.1. Environment Setup ..................................................................................................................... 411
15.1.1. Command-Line Tools .......................................................................................................... 411
15.2. Expression Syntax ....................................................................................................................... 411
15.2.1. Operators ........................................................................................................................... 412
15.2.2. Functions ........................................................................................................................... 412
15.3. Grid Operations .......................................................................................................................... 413
15.3.1. Convertgrid ........................................................................................................................ 414
[Link]. Description ................................................................................................................ 414
[Link]. Command Line Reference .......................................................................................... 414
[Link]. Examples ................................................................................................................... 417
15.3.2. fluent2fensap ..................................................................................................................... 418
[Link]. Description ................................................................................................................ 418
[Link]. Command Line Reference .......................................................................................... 418
[Link]. Reference Values ........................................................................................................ 420
[Link]. Examples ................................................................................................................... 421
15.3.3. fensap2fluent ..................................................................................................................... 421
[Link]. Description ................................................................................................................ 421

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
xii of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

[Link]. Command Line Reference .......................................................................................... 422

15.3.4. cfx2fensap ......................................................................................................................... 422
[Link]. Description ................................................................................................................ 422
[Link]. Command Line Reference .......................................................................................... 423
[Link]. Boundary and Reference Conditions .......................................................................... 424
15.3.5. Conversion from FENSAP to CFX ......................................................................................... 424
15.4. Solution File Operations .............................................................................................................. 425
15.4.1. solnEdit .............................................................................................................................. 425
[Link]. Description ................................................................................................................ 425
[Link]. Command Line Reference .......................................................................................... 425
[Link]. Examples ................................................................................................................... 426
15.4.2. soln2soln ........................................................................................................................... 427
[Link]. Description ................................................................................................................ 427
[Link]. Command Line Reference .......................................................................................... 428
[Link]. Examples ................................................................................................................... 429
15.5. TimeBC Operations ..................................................................................................................... 429
15.5.1. TimeBC Files ....................................................................................................................... 429
15.5.2. interpTimeBC ..................................................................................................................... 430
[Link]. Description ................................................................................................................ 430
[Link]. Command Line Reference .......................................................................................... 430
[Link]. Examples ................................................................................................................... 431
15.5.3. genTimeBC ........................................................................................................................ 431
[Link]. Description ................................................................................................................ 431
[Link]. Command Line Reference .......................................................................................... 431
15.5.4. interpTurboDropTimeBC (TURBO) ....................................................................................... 433
[Link]. Description ................................................................................................................ 433
[Link]. Command Line Reference .......................................................................................... 433
[Link]. Examples ................................................................................................................... 435
15.5.5. mergebcs ........................................................................................................................... 435
15.5.6. generateRoughnessDat ...................................................................................................... 436
[Link]. Description ................................................................................................................ 436
[Link]. Command Line Reference .......................................................................................... 436
[Link]. Examples ................................................................................................................... 437
16. Post-Processing ................................................................................................................................. 439
16.1. Post-processing .......................................................................................................................... 439
16.2. Viewmerical ................................................................................................................................ 440
16.2.1. Introduction to Viewmerical ............................................................................................... 440
[Link]. Launch from the FENSAP-ICE Project Manager ............................................................ 442
[Link]. Setup in FENSAP-ICE as Primary Post-Processor .......................................................... 442
[Link]. Launch from FENSAP-ICE - Secondary Post-Processor ................................................. 443
[Link].1. From the Run View ............................................................................................ 443
[Link].2. From the Execution Panel .................................................................................. 444
[Link]. Launch from the Command Line/Start Menu .............................................................. 444
16.2.2. 3D Display .......................................................................................................................... 444
[Link]. Mouse Controls ......................................................................................................... 445
[Link]. Toolbar ...................................................................................................................... 446
[Link]. Axis Display ............................................................................................................... 447
[Link]. Interactive Menu ........................................................................................................ 449
[Link]. Keyboard Shortcuts ................................................................................................... 450
16.2.3. Data Management ............................................................................................................. 451
[Link]. Open Files Dialog ....................................................................................................... 451

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. xiii
User Manual

[Link]. Adding/Removing Datasets ....................................................................................... 453

[Link]. Dataset Visibility ........................................................................................................ 453
[Link]. Current Selection ....................................................................................................... 453
[Link]. Multiple Selection ...................................................................................................... 454
[Link]. Lock Selection ........................................................................................................... 454
16.2.4. Object Panel ....................................................................................................................... 455
[Link]. Shading Mode ........................................................................................................... 455
[Link]. Object Color .............................................................................................................. 462
[Link]. Repetition (Mirror/Periodicity) .................................................................................... 462
[Link]. Split Screen ............................................................................................................... 464
16.2.5. Cutting Plane Panel ............................................................................................................ 467
16.2.6. Scalar Solution Visualization ............................................................................................... 470
[Link]. Files Panel .................................................................................................................. 470
[Link].1. Unsteady or Numbered Solutions ...................................................................... 471
[Link].2. Color Range ...................................................................................................... 472
[Link].3. Shared Range .................................................................................................... 472
[Link].4. Global Range .................................................................................................... 473
[Link].5. Advanced Options ............................................................................................ 474
[Link]. IsoValues Panel .......................................................................................................... 476
[Link]. Vector Data Panel ....................................................................................................... 477
[Link].1. Vector Scaling ................................................................................................... 477
[Link].2. Coordinate Clamping ........................................................................................ 478
[Link]. Displacement Panel ................................................................................................... 478
[Link].1. Real-Time Update ............................................................................................. 478
[Link].2. Advanced Settings ............................................................................................ 479
16.2.7. View Options ...................................................................................................................... 479
[Link]. Window Panel ............................................................................................................ 479
[Link]. Anaglyph 3D Display .................................................................................................. 480
16.2.8. Query Mode ....................................................................................................................... 480
[Link]. 2D Plot ...................................................................................................................... 480
[Link]. Selection Panel .......................................................................................................... 483
[Link]. Computation/Integration ........................................................................................... 484
[Link].1. Surface Integration ........................................................................................... 484
[Link].2. Mass Flow Integration ....................................................................................... 484
[Link].3. Volume Integration ........................................................................................... 485
16.2.9. ICE3D Solutions .................................................................................................................. 485
[Link]. The ICE3D Panel ......................................................................................................... 486
[Link]. CAD Output ............................................................................................................... 487
[Link].1. CAD Surface Cleanup ........................................................................................ 488
[Link].2. Boundary Edge Smoothing ............................................................................... 488
[Link].3. Output .............................................................................................................. 489
16.2.10. Command Line Usage ....................................................................................................... 490
16.3. CFD-Post Macros ......................................................................................................................... 490
16.3.1. Introduction to CFD-Post Macros ........................................................................................ 490
16.3.2. FENSAP-ICE Turbo .............................................................................................................. 491
[Link]. Requirements ............................................................................................................ 491
[Link]. Usage ........................................................................................................................ 492
16.3.3. Ice Cover – 3D-View ............................................................................................................ 493
[Link]. Usage ........................................................................................................................ 494
[Link]. Features .................................................................................................................... 494
[Link]. Input Parameters ....................................................................................................... 494

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
xiv of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

16.3.4. Ice Cover – 2D-Plot ............................................................................................................. 503

[Link]. Usage ........................................................................................................................ 504
[Link]. Features .................................................................................................................... 504
[Link]. Input Parameters ....................................................................................................... 504
16.3.5. Ice Cover – Turbo 3D-View .................................................................................................. 511
[Link]. Usage ........................................................................................................................ 511
[Link]. Features .................................................................................................................... 512
[Link]. Input Parameters ....................................................................................................... 512
[Link]. Extended Usage ......................................................................................................... 514
17. References ......................................................................................................................................... 517
17.1. Journal Publications in Mesh Adaptation ..................................................................................... 517
17.2. Conference Publications in Mesh Adaptation ............................................................................... 518
17.3. Von Karman Lecture Series in Mesh Adaptation ........................................................................... 520
17.4. Chapters in Books in In-Flight Icing .............................................................................................. 520
17.5. Refereed Journal Publications in In-Flight Icing ............................................................................ 520
17.6. Conference Publications in In-Flight Icing .................................................................................... 521
17.7. Referenced within this manual .................................................................................................... 524

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. xv
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
xvi of ANSYS, Inc. and its subsidiaries and affiliates.
List of Figures
2.1. Main Run Window ................................................................................................................................. 21
2.2. CHT3D Run Contains Multiple Modules ................................................................................................. 22
2.3. Minimized CHT3D Run .......................................................................................................................... 22
2.4. FENSAP-ICE Project Window .................................................................................................................. 23
2.5. Archive Run Window ............................................................................................................................. 25
2.6. Grid Selection Menu ............................................................................................................................. 28
2.7. Grid Converter ...................................................................................................................................... 29
4.1. Spinner Axis of Rotation ........................................................................................................................ 81
4.2. Surface Velocity Vectors ........................................................................................................................ 81
5.1. Vapor Nucleation Distribution ............................................................................................................. 121
5.2. Relative Humidity Distribution ............................................................................................................ 121
5.3. Static Temperature Distribution with Nucleation off (Top) and on (Bottom) .......................................... 122
5.4. Typical SLD Options, Freezing Drizzle Environment .............................................................................. 140
5.5. Typical SLD Options, Freezing Rain Environment .................................................................................. 141
5.6. Appendix O (FAA AC 25-28) Droplet Distribution Graph and Table ........................................................ 149
5.7. Appendix O (Refined) Droplet Distribution Graph and Table (25 Diameters) .......................................... 150
5.8. Comparison of Collection Efficiency for Different Simulated Distributions ............................................ 152
5.9. Cumulative Weight Distribution Represented Using Different Discretizations ....................................... 153
5.10. Initialization Using Vapor Concentration ............................................................................................ 159
5.11. Initialization Using Relative Humidity ................................................................................................. 159
5.12. Initialization Using Wet-Bulb Temperature ......................................................................................... 159
5.13. Crystal Reinjection Inside a Channel. Primary Impingement Result (Left), Composite Solution Combining
Primary and Subdivision Calculations (Right). ............................................................................................ 168
6.1. Nodes on the Engine Pylon ................................................................................................................. 198
6.2. Nodes on the Fuselage ........................................................................................................................ 199
6.3. Helicopter Intake Screen ..................................................................................................................... 201
6.4. Wire Diameter on Iced Screen of a Helicopter Intake ............................................................................ 202
6.5. Running Wet Required Heat Flux Distribution over Generic Aircraft ...................................................... 206
6.6. Fully Evaporative Required Heat Flux Distribution over Generic ............................................................ 206
6.7. Heat Tables of Fully Evaporative and Running Wet Conditions .............................................................. 208
[Link] Simulation Setup Featuring Rotationally Periodic Internal Components with a Full 3D External
Grid That Contains a Wing-Body-Nacelle-Pylon Configuration .................................................................... 247
9.2. Components in a Sequential Arrangement .......................................................................................... 250
9.3. Components in a Staggered Arrangement ........................................................................................... 250
9.4. Initialization Using Vapor Concentration .............................................................................................. 269
9.5. Initialization Using Relative Humidity .................................................................................................. 269
9.6. Initialization Using Wet-Bulb Temperature ........................................................................................... 269
9.7. Convective Heat Flux on the Turbofan Splitter Section Belonging to the Rotor Stage Showing the Wake
of the Rotor .............................................................................................................................................. 274
9.8. Corresponding Pitch-Averaged Heat-Flux in ICE3D .............................................................................. 275
9.9. Collection Efficiency on the Turbofan Splitter Section Belonging to the Rotor Stage Showing the Wake
of the Rotor .............................................................................................................................................. 276
9.10. Pitch-Averaged Collection Efficiency in ICE3D .................................................................................... 277
9.11. Rotor Blade with the Hub Defined as a Sliding Surface ....................................................................... 278
9.12. Blade Leading Edge Ice Displacement Along the Sliding Surface ........................................................ 278
9.13. Displaced Mesh (Red) on the Hub After 3D Mesh Movement .............................................................. 279
9.14. Inlet Profile for Liquid Water Content Using the fileData1D Option ..................................................... 285
9.15. Boundaries Panel in DROP3D-TURBO, with Checkboxes to Activate or Deactivate the Imposition of User-
Specified Boundary Conditions ................................................................................................................. 286

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. xvii
User Manual

10.1. Single Run ........................................................................................................................................ 289

10.2. Multiple Runs .................................................................................................................................... 289
10.3. Multishot Ice Accretion ...................................................................................................................... 290
10.4. 45-Minute Glaze Icing on a Full Aircraft with Slats and Flaps Deployed, 9 Shots ................................... 331
10.5. 22-Minute Glaze Ice on a Swept Wing, 22 Shots .................................................................................. 331
10.6. 22-Minute Icing on a Swept Wing, Mid-Span Surface Mesh, Pressure Side (Top) and Suction Side (Bot-
tom) ......................................................................................................................................................... 332
11.1. Collection Efficency on the Intake Screen of a Helicopter Engine ........................................................ 340
11.2. Wire Diameter on the Intake Screen of a Helicopter Engine ................................................................ 340
12.1. Distribution of the Normalized Error Density ...................................................................................... 345
13.1. CAD of a Circle .................................................................................................................................. 377
13.2. Coarse Mesh ..................................................................................................................................... 377
13.3. Refined Mesh Using CAD Information ................................................................................................ 378
13.4. Initial Mesh Edges ............................................................................................................................. 387
13.5. After Filtering Edges of Length <= 3 .................................................................................................. 387
13.6. After Filtering Edges of Length <= 10 ................................................................................................. 387
13.7. Initial Mesh Edges ............................................................................................................................. 388
13.8. After Filtering .................................................................................................................................... 388
13.9. Initial Mesh, with No Edges. The X Mark Is the Edge Selected with Define Curves ................................. 389
[Link] Group of Edges Detected Is Shown in Red. Parallel Edges Connected to the Initial Edge Were Se-
lected Automatically ................................................................................................................................. 390
[Link] Tolerance Control Allows Connecting Edges That Are Not Parallel, as Shown Below ..................... 390
16.1. Zoom in ............................................................................................................................................ 445
16.2. Zoom out .......................................................................................................................................... 446
16.3. Wireframe ......................................................................................................................................... 456
16.4. Colored ............................................................................................................................................. 456
16.5. Colored+Wireframe ........................................................................................................................... 457
16.6. Shaded ............................................................................................................................................. 458
16.7. Shaded+Wireframe ........................................................................................................................... 459
16.8. Smooth Shaded ................................................................................................................................ 460
16.9. Metallic ............................................................................................................................................. 461
16.10. Metallic+Smooth ............................................................................................................................ 462
16.11. No Repetition (Z-Symmetric Grid) .................................................................................................... 463
16.12. Z-Axis Repetition Enabled ............................................................................................................... 464
16.13. Grid Adaptation, Before Adaptation/After Adaptation ...................................................................... 465
16.14. CHT Solution – Static Temperature. External Wall/Internal Wall .......................................................... 466
16.15. Relative Scaling ............................................................................................................................... 478
16.16. Normalized Scaling ......................................................................................................................... 478
16.17. 2D Plot Menu .................................................................................................................................. 483
16.18. Node Selection Tool ........................................................................................................................ 484
16.19. Compute Panel Window .................................................................................................................. 484
16.20. Post-Processed Particle Solution of DROP3D TURBO Inside CFD-Post Turbo ....................................... 491
16.21. Ice Cover – 3D-View UI in CFD-Post .................................................................................................. 495
16.22. Ice Cover ......................................................................................................................................... 496
16.23. Ice Cover - Shaded ........................................................................................................................... 496
16.24. Ice Cover - No Orig .......................................................................................................................... 496
16.25. Ice Cover (only) ............................................................................................................................... 496
16.26. Ice Cover (only) – shaded ................................................................................................................. 497
16.27. Ice Solution – Overlay ...................................................................................................................... 497
16.28. Ice Solution ..................................................................................................................................... 497
16.29. Surface Solution .............................................................................................................................. 498

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
xviii of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

16.30. Isoclip Variable (Ice Growth), Isoclip Value (0.01 kg/m2) ..................................................................... 498
16.31. Isoclip Variable (Ice Growth), Isoclip Value (2 kg/m2) ......................................................................... 498
16.32. Isoclip Variable (Ice Growth), Isoclip Value (15 kg/m2) ........................................................................ 499
16.33. Transparency: 0 ............................................................................................................................... 499
16.34. Transparency: 0.5 ............................................................................................................................. 499
16.35. Transparency: 1 ............................................................................................................................... 500
16.36. Display Variable (Instant. Ice Growth) ............................................................................................... 500
16.37. Display Variable (Ice Thickness) ........................................................................................................ 500
16.38. Lines of Contour (Off ) ...................................................................................................................... 501
16.39. Lines of Contour (On) ...................................................................................................................... 501
16.40. Number of Contour: 8 ...................................................................................................................... 501
16.41. Number of Contour: 32 .................................................................................................................... 502
16.42. Display Mesh (Off ) ........................................................................................................................... 502
16.43. Display Mesh (On) ........................................................................................................................... 502
16.44. Ice Cover – 3D-View UI in CFD-Post .................................................................................................. 505
16.45. 2D-Plot with Single Shot (Shot No.3) ................................................................................................ 506
16.46. 2D-Plot with Multishots (Shot No.4 -> 8) .......................................................................................... 506
16.47. 2D-Plot with Selected Shots (Shot No. 2, 5, 6, and 8) .......................................................................... 506
16.48. Mode: Geometry ............................................................................................................................. 507
16.49. Mode: Solution (on Ice Surfaces) ...................................................................................................... 507
16.50. Mode: Solution (on Map Surfaces) .................................................................................................... 507
16.51. Cutting X Plane at Point 0.5, (0.5, 0, 0) ............................................................................................... 508
16.52. Cutting Y Plane at Point 0, (0, 0, 0) ..................................................................................................... 508
16.53. Cutting Z Plane at Point 0.5, (0, 0, 0.5) ............................................................................................... 509
16.54. Cutting Plane: Point (0.291, 0.017, 0.512) and Normal (0.5, 0, 0.866) .................................................... 510
16.55. Ice Cover – Turbo 3D-View User Interface in CFD-Post ....................................................................... 513
16.56. View of Multiple Stages in Full Cycle Mode ....................................................................................... 515
16.57. Improved View of Multiple Stages in Full Cycle Mode ....................................................................... 516

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. xix
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
xx of ANSYS, Inc. and its subsidiaries and affiliates.
List of Tables
1.1. List of Symbols ....................................................................................................................................... 1
1.2. Greek Symbols ........................................................................................................................................ 3
1.3. Subscripts and Superscripts .................................................................................................................... 3
1.4. Influence of Various Parameters on Unprotected Icing Simulations ......................................................... 12
1.5. Influence of Various Parameters on Thermal Ice Protection Simulations .................................................. 12
2.1. Mouse Options ..................................................................................................................................... 19
2.2. Expressions ........................................................................................................................................... 23
2.3. Menu Options ....................................................................................................................................... 26
2.4. Menu Options ....................................................................................................................................... 30
2.5. Mouse Options ..................................................................................................................................... 36
2.6. Settings ................................................................................................................................................ 37
3.1. Configure Menu Options ....................................................................................................................... 42
4.1. Actuator Disk Geometry ........................................................................................................................ 87
4.2. Default Values ..................................................................................................................................... 106
4.3. Pull Down Menu Options .................................................................................................................... 107
5.1. Droplet Break-Up ................................................................................................................................ 123
6.1. ICE3D Solution Files ............................................................................................................................ 204
7.1. Defining Materials and Properties ........................................................................................................ 213
7.2. Thermal Boundary Conditions ............................................................................................................. 216
7.3. Electrical Boundary Conditions ............................................................................................................ 218
9.1. Interface Algorithm Methods .............................................................................................................. 252
[Link] Choices Are: .................................................................................................................................. 261
9.3. Commands ......................................................................................................................................... 264
9.4. DROP3D-TURBO Physical Model .......................................................................................................... 266
9.5. Output Files ........................................................................................................................................ 282
10.1. Multishot Types ................................................................................................................................. 292
10.2. Solvers .............................................................................................................................................. 298
10.3. Fluent Configuration Window ............................................................................................................ 302
14.1. Elements ........................................................................................................................................... 393
14.2. Boundary Condition Indices .............................................................................................................. 398
14.3. Boundary Condition Priorities ............................................................................................................ 399
14.4. List of Variable Numbers in [Link] ............................................................................................... 408
15.1. Functions .......................................................................................................................................... 412
15.2. Range Operations ............................................................................................................................. 412
15.3. File Data ........................................................................................................................................... 412
15.4. Convertgrid ...................................................................................................................................... 414
15.5. Options ............................................................................................................................................ 414
15.6. Output File Formats .......................................................................................................................... 414
15.7. Input File Format ............................................................................................................................... 415
15.8. Stats ................................................................................................................................................. 415
15.9. Grid Scaling/Operations .................................................................................................................... 415
15.10. Optimization ................................................................................................................................... 415
15.11. Boundary Condition Operations ...................................................................................................... 415
15.12. Volume Operations ......................................................................................................................... 416
15.13. Material Operations ......................................................................................................................... 416
15.14. Periodicity Operations ..................................................................................................................... 416
15.15. Example Commands ....................................................................................................................... 417
15.16. Example Commands Continued ...................................................................................................... 417
15.17. Options ........................................................................................................................................... 419

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. xxi
User Manual

15.18. Icing Options .................................................................................................................................. 419

15.19. Output Files .................................................................................................................................... 419
15.20. Multi-Zone Options ......................................................................................................................... 420
15.21. Solution Options ............................................................................................................................. 420
15.22. Boundary Conditions ...................................................................................................................... 420
15.23. The Following Values are Important ................................................................................................. 420
15.24. The Following Values are Optional ................................................................................................... 420
15.25. Variables with a Default Value .......................................................................................................... 421
15.26. Variables Continued ........................................................................................................................ 421
15.27. fluent2fensap Commands ............................................................................................................... 421
15.28. General Commands ......................................................................................................................... 422
15.29. Input File Options ............................................................................................................................ 422
15.30. Output File Options ......................................................................................................................... 422
15.31. Output Options ............................................................................................................................... 423
15.32. Boundary Condition Identifier ......................................................................................................... 424
15.33. solnEdit .......................................................................................................................................... 425
15.34. Options ........................................................................................................................................... 426
15.35. Options ........................................................................................................................................... 428
15.36. Optimizations ................................................................................................................................. 428
15.37. Interpolating Solutions .................................................................................................................... 429
15.38. Interpolating swimsol Files and 3D Airflow Wall Values ..................................................................... 429
15.39. interpTimeBC Command ................................................................................................................. 430
15.40. Options for DROP3D (Droplets) ........................................................................................................ 430
15.41. Options for DROP3D (Crystals) (TURBO Specific) .............................................................................. 430
15.42. genTimeBC Command .................................................................................................................... 432
15.43. The Expression Can Make Use of the Following Variables .................................................................. 432
15.44. The Variable Parameter Is Ignored for Roughness ............................................................................. 433
15.45. Reading a DROPLET Solution ........................................................................................................... 433
15.46. Mandatory Parameters .................................................................................................................... 434
15.47. Optional Parameters ....................................................................................................................... 434
15.48. Examples ........................................................................................................................................ 435
15.49. Interpolation of Droplet Values with Temperature Modification ........................................................ 435
15.50. Interpolation of Both Drop and Crystals ........................................................................................... 435
15.51. Usage ............................................................................................................................................. 436
15.52. Creating a [Link] File ........................................................................................................... 436
15.53. Options ........................................................................................................................................... 436
15.54. Set up Roughness Values from Ice Thickness in Solution ................................................................... 437
16.1. Other File Formats ............................................................................................................................. 442
16.2. Mouse Control Examples ................................................................................................................... 445
16.3. Controls ............................................................................................................................................ 445
16.4. Toolbar ............................................................................................................................................. 446
16.5. Axis Display ...................................................................................................................................... 447
16.6. Additional View Options .................................................................................................................... 448
16.7. Interactive Menu ............................................................................................................................... 449
16.8. Keyboard Shortcuts ........................................................................................................................... 450
16.9. Grid File Formats Notes ..................................................................................................................... 452
16.10. Solution File Notes .......................................................................................................................... 452
16.11. Display Options ............................................................................................................................... 467
16.12. Files Panel ....................................................................................................................................... 470
16.13. Window Panel ................................................................................................................................. 479
16.14. Target ............................................................................................................................................. 481

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
xxii of ANSYS, Inc. and its subsidiaries and affiliates.
 User Manual

16.15. 2D Window Panel Modes ................................................................................................................. 482

16.16. ICE3D Output Files .......................................................................................................................... 485
16.17. Display Mode .................................................................................................................................. 486

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. xxiii
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
xxiv of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Introduction
The following sections of this chapter are:
1.1. Known Limitations in ANSYS FENSAP-ICE 2020 R2
1.2. List of Symbols
1.3. About ANSYS
[Link] ANSYS Product Improvement Program
1.5. FENSAP-ICE System
1.6. FENSAP-ICE-TURBO
1.7. Layout of this Manual
1.8. Contact Information

1.1. Known Limitations in ANSYS FENSAP-ICE 2020 R2

This section lists limitations that are known to exist in ANSYS FENSAP-ICE. Where possible, suggested
workarounds are provided.

• When Multishot with remeshing and screen model is enabled, the built-in custom remeshing script
is not copying the wire diameter to the roughness file that will be used by FENSAP for the next shot.
To correct this, change the roughness interpolation section in custom_remeshing.sh file in the
multishot run directory to the following:
if test -f [Link].$shot1
then
"$NTI_PATH/rough2rough" $GP [Link].$shot1
$GM [Link] -bc=2 -field=20
"$NTI_PATH/rough2rough" $GI [Link]
$GO [Link].$[Link] -flat -bc=2 -field=20
"$NTI_PATH/rough2rough"
$GO [Link].$[Link] -bc=6 -field=60
"$NTI_PATH/mergebcs" [Link].$[Link]
[Link].$[Link] [Link].$[Link]
rm -f [Link] [Link].$[Link]
[Link].$[Link]
fi

1.2. List of Symbols

Table 1.1: List of Symbols

Symbol Description
A Reference area (m2)
AoA Angle of attack (deg.)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 1
Introduction

Symbol Description
CD Drag coefficient, CD

CL Lift coefficient, CL

Cp Specific heat (J/kg K)

c Chord length (m)
D Drag force vector (N)
d Droplet diameter (μm)
f Freezing fraction
Fr Froude number, Fr

g Gravity vector (m/s2)

H Enthalpy (J/kg)
h Water film height (m)
hc Convective heat transfer coefficient (W/m2 K)
K Droplet inertia parameter

k Thermal conductivity (W/m K)/Turbulence kinetic energy (J)/Equivalent sand-grain roughness

(m)
L∞ Characteristic length (m)
L Lift force vector (N) or latent heat (J/kg)
LWC Liquid water content (kg/m3)
M Mach number
MVD Median Volumetric Diameter (μm)
m Mass flow (kg/s)
n Surface normal vector
p Static pressure (Pa)
Q Heat flux (W/m2)
R Gas constant (287.053763 J/kg K) or residual vector

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
2 of ANSYS, Inc. and its subsidiaries and affiliates.
 List of Symbols

Symbol Description
Re Flow Reynolds number
Red Droplet Reynolds number
REC Recovery factor
t Time (s)
T Static temperature (K)
Tu Turbulence intensity
V Velocity vector (m/s)
x,y,z Grid coordinates (m)
+
y Non-dimensional wall distance

Table 1.2: Greek Symbols

Greek Symbol Description

α Local LWC (kg/m3)
β Collection efficiency

βtot Total collection efficiency

ε Solid emissivity or artificial viscosity parameter or

turbulent dissipation rate (m2/s3)
γ Ratio of specific heats
κ Thermal conductivity (W/m K)
μ Kinematic viscosity (kg/m s)
ρ Density (kg/m3)
σ Boltzmann constant (s= 5.67 x10-8 W/m2 K4)
Ω Rotation speed vector (radian/s) or turbulent
frequency (1/s)
Shear stress tensor (N/m2)

Table 1.3: Subscripts and Superscripts

Subscripts/Superscripts Description
a Air

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 3
Introduction

Subscripts/Superscripts Description
d Droplet
dim Dimensional
f Fluid
i Ice
L Laminar
s Solid
T Turbulent
w Wall
° Temperature in Celsius
∞ Reference (freestream)

1.3. About ANSYS

ANSYS, Inc. is the leading provider of scientific CFD software in the world. ANSYS, Inc. acquired the assets
of Newmerical Technologies International (NTI) in February 2015 with the intent of continuing to provide
comprehensive design and engineering services for ice protection systems of aircraft, rotorcraft, jet
engines and wind turbines, and related systems in cars, trucks and high-speed trains.

The in-flight icing specialists at ANSYS, Inc. remain a one-stop-shop for all aspects of in-flight icing,
ranging from engineering services, the licensing of their state-of-the-art icing simulation systems ANSYS
FENSAP-ICE™ and ANSYS FENSAP-ICE-TURBO™ and icing protection systems design.

Today, icing protection still remains an arduous exercise that utilizes an eclectic amalgam of empiricism
and freeware, collated through technologies developed in a different era, often leading to confusion
for manufacturers and regulators alike. FENSAP-ICE and FENSAP-ICE-TURBO distinguish themselves by
their ability to bring scientific rigor and methodology to the hitherto heuristic and empirical icing pro-
tection design methodology.

In-flight icing simulation, and consequently ice protection, still remains as much of an art as a science,
making icing certification a difficult engineering process in the production of a new aircraft or engine.
The ANSYS, Inc. in-flight icing specialists provide a rigorous, sequential, verifiable and integrated approach
that views ice protection as a system, rather than a disjoint series of steps that are difficult, if not alto-
gether impossible, to link. FENSAP-ICE and FENSAP-ICE-TURBO are the only modular icing simulation
systems available on the market today and are the only 3D, CAD-based software of their kind. They are
perfectly compatible with ANSYS CFD tools, as well as other third-party CFD tools used in aerodynamic
departments, and hence allow a complete integration of aerodynamic design and ice protection, a
hitherto impossible endeavor.

In addition, while several other companies and governmental agencies may also offer icing simulation
services, our specialists are the only ones who have completely developed their own software, with a
total mastery of their much more modern technology and the ability to rapidly deploy it to new situations
and new applications.

FENSAP-ICE and FENSAP-ICE-TURBO are systems that are continuously evolving to cost effectively resolve
undetected operational difficulties or meet new regulations as they arise. Examples would be Supercooled
Large Droplets and Ice Crystals ingestion into jet engines. Enough science is built into the system to

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
4 of ANSYS, Inc. and its subsidiaries and affiliates.
 The ANSYS Product Improvement Program

view current and evolving certification standards as minimum objectives, as they are meant to be, and
go beyond them to further increase safety.

The ANSYS icing groups' services include, but are not limited to:

• Icing simulation software licensing

• Icing simulation engineering services

• Ice protection system design

1.4. The ANSYS Product Improvement Program

This product is covered by the ANSYS Product Improvement Program, which enables ANSYS, Inc., to
collect and analyze anonymous usage data reported by our software without affecting your work or
product performance. Analyzing product usage data helps us to understand customer usage trends
and patterns, interests, and quality or performance issues. The data enable us to develop or enhance
product features that better address your needs.

How to Participate
The program is voluntary. To participate, select Yes when the Product Improvement Program dialog
appears. Only then will collection of data for this product begin.

How the Program Works

After you agree to participate, the product collects anonymous usage data during each session. When
you end the session, the collected data is sent to a secure server accessible only to authorized ANSYS
employees. After ANSYS receives the data, various statistical measures such as distributions, counts,
means, medians, modes, etc., are used to understand and analyze the data.

Data We Collect
The data we collect under the ANSYS Product Improvement Program are limited. The types and amounts
of collected data vary from product to product. Typically, the data fall into the categories listed here:

Hardware: Information about the hardware on which the product is running, such as the:

• brand and type of CPU

• number of processors available

• amount of memory available

• brand and type of graphics card

System: Configuration information about the system the product is running on, such as the:

• operating system and version

• country code

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 5
Introduction

• time zone

• language used

• values of environment variables used by the product

Session: Characteristics of the session, such as the:

• interactive or batch setting

• time duration

• total CPU time used

• product license and license settings being used

• product version and build identifiers

• command line options used

• number of processors used

• amount of memory used

• errors and warnings issued

Session Actions: Counts of certain user actions during a session, such as the number of:

• project saves

• restarts

• meshing, solving, postprocessing, etc., actions

• times the Help system is used

• times wizards are used

• toolbar selections

Model: Statistics of the model used in the simulation, such as the:

• number and types of entities used, such as nodes, elements, cells, surfaces, primitives, etc.

• number of material types, loading types, boundary conditions, species, etc.

• number and types of coordinate systems used

• system of units used

• dimensionality (1-D, 2-D, 3-D)

Analysis: Characteristics of the analysis, such as the:

• physics types used

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
6 of ANSYS, Inc. and its subsidiaries and affiliates.
 The ANSYS Product Improvement Program

• linear and nonlinear behaviors

• time and frequency domains (static, steady-state, transient, modal, harmonic, etc.)

• analysis options used

Solution: Characteristics of the solution performed, including:

• the choice of solvers and solver options

• the solution controls used, such as convergence criteria, precision settings, and tuning options

• solver statistics such as the number of equations, number of load steps, number of design points,
etc.

Specialty: Special options or features used, such as:

• user-provided plug-ins and routines

• coupling of analyses with other ANSYS products

Data We Do Not Collect

The Product Improvement Program does not collect any information that can identify you personally,
your company, or your intellectual property. This includes, but is not limited to:

• names, addresses, or usernames

• file names, part names, or other user-supplied labels

• geometry- or design-specific inputs, such as coordinate values or locations, thicknesses, or other

dimensional values

• actual values of material properties, loadings, or any other real-valued user-supplied data

In addition to collecting only anonymous data, we make no record of where we collect data from. We
therefore cannot associate collected data with any specific customer, company, or location.

Opting Out of the Program

You may stop your participation in the program any time you wish. To do so, select ANSYS Product
Improvement Program from the Help menu. A dialog appears and asks if you want to continue parti-
cipating in the program. Select No and then click OK. Data will no longer be collected or sent.

The ANSYS, Inc., Privacy Policy

All ANSYS products are covered by the ANSYS, Inc., Privacy Policy.

Frequently Asked Questions

1. Am I required to participate in this program?

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 7
Introduction

No, your participation is voluntary. We encourage you to participate, however, as it helps us create
products that will better meet your future needs.

2. Am I automatically enrolled in this program?

No. You are not enrolled unless you explicitly agree to participate.

3. Does participating in this program put my intellectual property at risk of being collected or discovered
by ANSYS?

No. We do not collect any project-specific, company-specific, or model-specific information.

4. Can I stop participating even after I agree to participate?

Yes, you can stop participating at any time. To do so, select ANSYS Product Improvement Program
from the Help menu. A dialog appears and asks if you want to continue participating in the program.
Select No and then click OK. Data will no longer be collected or sent.

5. Will participation in the program slow the performance of the product?

No, the data collection does not affect the product performance in any significant way. The amount
of data collected is very small.

6. How frequently is data collected and sent to ANSYS servers?

The data is collected during each use session of the product. The collected data is sent to a secure
server once per session, when you exit the product.

7. Is this program available in all ANSYS products?

Not at this time, although we are adding it to more of our products at each release. The program
is available in a product only if this ANSYS Product Improvement Program description appears in the
product documentation, as it does here for this product.

8. If I enroll in the program for this product, am I automatically enrolled in the program for the other ANSYS
products I use on the same machine?

Yes. Your enrollment choice applies to all ANSYS products you use on the same machine. Similarly,
if you end your enrollment in the program for one product, you end your enrollment for all ANSYS
products on that machine.

9. How is enrollment in the Product Improvement Program determined if I use ANSYS products in a cluster?

In a cluster configuration, the Product Improvement Program enrollment is determined by the host
machine setting.

10. Can I easily opt out of the Product Improvement Program for all clients in my network installation?

Yes. Perform the following steps on the file server:

a. Navigate to the installation directory: [Drive:]\v211\commonfiles\globalsettings

b. Open the file [Link].

c. Change the value from "on" to "off" and save the file.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
8 of ANSYS, Inc. and its subsidiaries and affiliates.
 FENSAP-ICE System

1.5. FENSAP-ICE System

FENSAP-ICE is a 3D, state-of-the-art, complete, modular, design and aid-to-certification simulation system
conceived to provide enhanced aerodynamic and in-flight icing protection solutions in a cost-effective
manner. FENSAP-ICE distinguishes itself by its ability to unify CFD to in-flight icing physics and therefore
brings a comprehensive and robust methodology to the aerospace industry.

FENSAP-ICE addresses five major aspects of in-flight icing: airflow (CFD), droplets impingement limits
and shadow zones, ice shapes, aerodynamic degradation and anti- and de-icing heat loads. It is com-
patible with widely-used CAD-based mesh generators and other ANSYS CFD codes, therefore enhancing
workflow, has no geometric limitations and is applicable to aircraft, rotorcraft, UAVs, jet engines, nacelles,
probes, detectors and installed systems. FENSAP-ICE runs on a wide variety of computer platforms,
ranging from PCs and workstations to massively parallel machines.

FENSAP-ICE is a system containing six main modules that form a complete, versatile, flexible in-flight
icing system: is a system containing six main modules that form a complete, versatile, flexible in-flight
icing system:

• FENSAP: 3D Finite Element Navier-Stokes Analysis Package

• OptiGrid: 3D mesh adaptation and CAD reconstruction tool

• DROP3D: 3D finite element Eulerian water droplet impingement solver

• ICE3D: 3D finite volume ice accretion and water runback solver

• CHT3D: 3D Conjugate Heat Transfer solver, including C3D for heat conduction

FENSAP-ICE-TURBO 3D Solvers tailored to handle turbomachinery applications:

• FENSAP-TURBO: 3D Finite Element Navier-Stokes Analysis Package for rotor/stator

• DROP3D-TURBO: 3D finite element Eulerian water droplet/ice crystal impingement solver for rotor/stator

• ICE3D-TURBO: 3D finite volume ice accretion and water runback solver for rotor/stator

An advanced Graphical User Interface (GUI) links these modules seamlessly. Each module is compatible
with unstructured and hybrid grids (hexahedral, tetrahedral, pyramid and prism elements), the same
grid being shared by all the modules during the analysis process. Furthermore, high quality mesh- and
user-independent results can easily be obtained with ANSYS automatic mesh optimizer OptiGrid.

Compatibility with 3D CFD codes technology also enhances productivity by capitalizing on the wealth
of CFD data (meshes and solutions) generated during aerodynamic design, therefore lowering the in-
cremental cost of any icing analyses. Finally, output for different commercial data visualization packages
is provided and the built-in automatic data archival system simplifies and enhances extensibility, repeat-
ability, and traceability of results.

1.5.1. Flow Solver (FENSAP)

The complete analysis of an in-flight icing problem typically begins with an airflow solution over a
clean geometry and ends with a series of airflow solutions over a contaminated geometry to assess
the performance degradation caused by ice build-up.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 9
Introduction

FENSAP solves the steady and unsteady compressible 3D Navier-Stokes equations. The fluid may be
inviscid or viscous, in which case the flow may be laminar or turbulent, turbulence being modeled
by one-equation or two-equation models. The heat fluxes at walls, of paramount importance for glaze
icing, can be computed directly with second order accuracy by re-solving the energy equation on
the solid surfaces.

Additionally, for propeller-driven aircraft, helicopter or tiltrotor geometries, a flow-through actuator

disk can model the important propeller wake effects in a cost-effective manner. For more accurate
predictions, unsteady rotor-fuselage interactions can be computed by considering fixed and rotating
grid domains and by automatically stitching the two grids together after each rotor displacement.

1.5.2. Mesh Adaptation and CAD Reconstruction (OptiGrid)

OptiGrid is a comprehensive, automatic mesh adaptation and CAD reconstruction software which
helps achieve the most accurate CFD simulations at the lowest computational cost. OptiGrid works
in a fully-coupled manner with FENSAP and Fluent, or by using the generic file format introduced in
this manual.

One of the most important features of OptiGrid lies in its innovative CAD reconstruction functionality,
allowing mesh adaptation on grids generated by different mesh generators. A simple graphical interface
allows you to regenerate the CAD automatically from the initial surface grid, and to define boundary
conditions (such as symmetry and periodicity) before mesh adaptation.

OptiGrid assesses the mesh quality on each individual element edge, via a posteriori error estimator,
given a solution on an initial mesh. Subsequently, OptiGrid systematically modifies the mesh in order
to equalize the error to the given target throughout the solution domain. The grid is adapted by
moving nodes, refining and coarsening edges, for example adding and removing grid points, and
swapping edges. All operations are edge-based and therefore OptiGrid can be coupled with any finite
volume or finite element flow code that uses unstructured meshes composed of any combination of
hexahedral, tetrahedral, prismatic and pyramidal elements. The strength of OptiGrid lies in its ability
to yield anisotropic (stretched) meshes which are able to capture high-resolution, three-dimensional
features such as shocks, boundary layers, wakes, vortices and slip lines while fully respecting the re-
constructed CAD.

Finally, OptiGrid can be used as a mesh smoothing tool before any calculations to set the desired
number of grid points provided by you and align cells with the curvature of the surfaces.

1.5.3. Water Droplet/Ice Crystal Impingement (DROP3D)

DROP3D is the 3D Eulerian (one-shot) water droplet/ice crystal impingement module of the FENSAP-
ICE system. DROP3D works seamlessly in conjunction with FENSAP, Fluent and CFX or accepts flow
solutions from other CFD codes of equivalent capabilities. It handles impingement for both external
and internal flows.

DROP3D solves fine-grain partial differential equations for particle velocity and water concentration.
DROP3D therefore provides, in a single shot, water concentration, droplet velocity vectors, water
catch efficiency distributions, impingement patterns, shadow zone characteristics and impingement
limits over the entire domain without the laborious iterative procedure of seeding droplets at injection
points.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
10 of ANSYS, Inc. and its subsidiaries and affiliates.
 FENSAP-ICE System

DROP3D can also be used for a wide variety of other demanding situations where particles are sus-
pended in a carrier fluid, such as screens, pollutant dispersal, collection and condensation rates on
HVAC components, etc.

1.5.4. Ice Accretion and Water Runback (ICE3D)

ICE3D is the 3D ice accretion module of the FENSAP-ICE system, also based on fine-grain partial dif-
ferential equations for the complex thermodynamics of ice formation. It yields 3D ice shape, water
film thickness and surface temperature on any number of complex 3D surfaces.

ICE3D can output the displaced 3D grid after ice accretion. Performance degradation due to ice ac-
cretion can be easily computed by simply restarting FENSAP on this new grid. The 3D ice shape is
also saved in .stl and TETIN CAD formats to allow manual grid re-generation after each ice accretion
period.

ICE3D's range of applicability also extends to a wide variety of other demanding film thickness and
accretion rate prediction situations, such as: windshield and radiator grille icing on vehicles, chemical
vapor deposition on semiconductor chips, water runback on car geometries, etc.

1.5.5. Conjugate Heat Transfer (CHT3D, C3D)

CHT3D is the 3D Conjugate Heat Transfer (CHT) module of the FENSAP-ICE system that couples airflow
convection (from FENSAP) and heat conduction through solids (from C3D) for dry-air heat transfer
calculations and, in conjunction with DROP3D (droplets impact) and ICE3D (ice accretion), for wet-air
anti-icing calculations. CHT3D can also be operated in steady or unsteady de-icing modes, and also
provides three different levels of fidelity, depending on the application and the tradeoff between
execution time and the required accuracy.

CHT3D is applicable to a wide variety of other demanding fluid-solid interface heat transfer situations,
such as piccolo tubes embedded in wing leading edges, engine nacelle leading edge heating, electro-
thermal heating, gas turbine blade cooling, heat dissipation in car or airplane brakes, automotive
engine cooling and casting processes.

[Link]. Icing Simulations

The modular approach of the FENSAP-ICE system allows you to easily investigate the impact of
various parameters on icing. When considering a change in a given parameter in an existing simu-
lation, the following tables show which calculations (tasks) must be repeated to obtain a new pre-
diction. Table 1.4: Influence of Various Parameters on Unprotected Icing Simulations (p. 12) sum-
marizes the influence of various parameters for unprotected components icing calculations.
Table 1.5: Influence of Various Parameters on Thermal Ice Protection Simulations (p. 12) shows the
tasks required for thermal ice protection simulations. It should be noted that Table 1.4: Influence
of Various Parameters on Unprotected Icing Simulations (p. 12) is a subset of Table 1.5: Influence
of Various Parameters on Thermal Ice Protection Simulations (p. 12) for the external domain.

For example, assuming that a CHT calculation was performed for a piccolo tube system, changing
the piccolo jet temperature alone requires a repeat of the internal flow and CHT3D calculation, as
shown in Table 1.5: Influence of Various Parameters on Thermal Ice Protection Simulations (p. 12).
On the other hand, a change in incidence or true airspeed means repeating all external domain
calculations, for example FENSAP, DROP3D and ICE3D and repeating the CHT calculation. The initial

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 11
Introduction

internal flow calculation, however, can be reused as the basis for the new CHT calculation and does
not need to be recomputed.

Note:

The examples above consider only a change in a single parameter while everything else
remains constant. If a parameter change affects other conditions, for example a change
in OAT that affects engine mass flow, true airspeed, and bleed temperature, then these
parameters must also be considered to decide which calculations must be repeated.

Table 1.4: Influence of Various Parameters on Unprotected Icing Simulations

Parameters/Tasks FENSAP External DROP3D ICE3D

Incidence ✔ ✔ ✔
True Airspeed (TAS) ✔ ✔ ✔
Altitude ✔ ✔ ✔
Outside Air ✔
Temperature (OAT)
MVD ✔ ✔
LWC ✔

Table 1.5: Influence of Various Parameters on Thermal Ice Protection Simulations

Parameters FENSAP DROP3D ICE3D MESH FENSAP CHT3D

External Internal Internal
Incidence ✔ ✔ ✔ ✔
True ✔ ✔ ✔ ✔
Airspeed
(TAS)
Altitude ✔ ✔ ✔ ✔
Outside Air ✔ ✔ ✔
Temperature
(OAT)
MVD ✔ ✔ ✔
LWC ✔ ✔
Piccolo jet ✔ ✔
mass flow
Piccolo jet ✔ ✔
temperature
Spent air ✔ ✔
exit
pressure
Piccolo ✔ ✔ ✔
hole size &
pattern

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
12 of ANSYS, Inc. and its subsidiaries and affiliates.
 Layout of this Manual

Parameters FENSAP DROP3D ICE3D MESH FENSAP CHT3D

External Internal Internal
Skin ✔
material
Electric ✔
heater
on/off
cycle

1.6. FENSAP-ICE-TURBO
FENSAP-ICE-TURBO is the 3D turbomachinery module that fully integrates the capabilities of FENSAP-
TURBO, CFX, DROP3D-TURBO, ICE3D-TURBO and C3D/CHT3D-TURBO to compute the steady-state airflow,
droplet/ice crystal impingement and ice accretion solutions in multistage turbomachinery components.
Each component is solved independently, and the interaction between components is updated at every
iteration using interfaces. The use of mixing planes to transfer boundary conditions at the interfaces
provides the flexibility to handle multi-component grids with non-matching nodes, as well as unequal
pitch.

1.7. Layout of this Manual

The objective of this document is to assist you in configuring and running FENSAP-ICE's solution modules.
It is organized in the following manner:

The FENSAP-ICE Project Manager (p. 15) and The FENSAP-ICE Solver Manager (p. 39) introduce the
FENSAP-ICE graphical user interface common to all modules.

FENSAP - Flow Solution (p. 53), DROP3D - Droplet and Ice Crystal Impingement (p. 113), ICE3D - Ice Ac-
cretion and Water Runback (p. 171), C3D - Unsteady Heat Conduction (p. 209), CHT3D - 3D Conjugate
Heat Transfer (p. 225) describe how to use FENSAP-ICE to configure the input parameters for in-flight
icing calculations (FENSAP-ICE suite of modules) or, separately, for the flow (FENSAP), droplets impinge-
ment (DROP3D), ice accretion & water runback (ICE3D), as well as the configuration of the heat conduction
(C3D) and conjugate heat transfer (CHT3D) modules.

FENSAP-ICE-TURBO (p. 245) outlines the use of FENSAP-TURBO, DROP3D-TURBO and ICE3D-TURBO for
simulating multi-stage components in rotating or stationary turbomachinery components.

Automated Sequences and Multishot Icing Calculations (p. 289) outlines the configuration of a quasi-
steady, or multishot, ice accretion simulations using FENSAP, DROP3D and C3D, or alternately Fluent,
DROP3D and C3D.

FENSAP-ICE-Unsteady (p. 333) introduces FENSAP-ICE-Unsteady, the unsteady multi-phase model that
combines flow and droplets with ice accretion into a single calculation and shows how to configure it
through FENSAP-ICE.

OptiGrid - Mesh Adaptation (p. 343) and OptiGrid - CAD Reconstruction (p. 377) describe the configuration
of the input parameters required for mesh adaptation and CAD reconstruction (OptiGrid), respectively.

FENSAP-ICE File Formats (p. 393) introduces the FENSAP-ICE file formats.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 13
Introduction

Tools Reference (p. 411) describes operators and functions used within FENSAP-ICE.

Post-Processing (p. 439) introduces Viewmerical, a simple data post-processor that enables the visualiz-
ation of FENSAP-ICE grids and solution files.

References (p. 517) provides an extensive list of references of in-flight icing, mesh adaptation and CFD
publications by FENSAP-ICE's scientists.

1.8. Contact Information

Technical Support for ANSYS, Inc. products is provided either by ANSYS, Inc. directly or by one of our
certified ANSYS Support Providers. Please check with the ANSYS Support Coordinator (ASC) at your
company to determine who provides support for your company, or go to [Link] and select
Contacts → Contacts and Locations. If your support is provided by ANSYS, Inc. directly, Technical
Support can be accessed quickly and efficiently from the ANSYS customer site, which is available from
the ANSYS Website ([Link]) under Support → customer site. The direct URL is: [Link]-
[Link]/customercommunity. One of the many useful features of the ANSYS customer site is the
Knowledge Resources Search, which can be found on the Home page of the ANSYS customer site. To
use this feature, enter relevant text (error message, etc.) in the Knowledge Resources Search box and
click the magnifying glass icon. These Knowledge Resources provide solutions and guidance on how
to resolve installation and licensing issues quickly.

NORTH AMERICA

All ANSYS Products except Esterel, Apache and Reaction Design products

Web: Go to the ANSYS customer site and select the appropriate option.

Toll-Free Telephone: 1.800.711.7199 (Please have your Customer or Contact ID ready.) Support for
University customers is provided only through the ANSYS customer site.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
14 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 2: The FENSAP-ICE Project Manager
The following sections of this chapter are:
[Link] Project Manager
[Link] Run Manager
[Link] Grid File
2.4. Input Parameters
2.5. Solution Files
2.6. Preferences
2.7. Quit FENSAP-ICE

The FENSAP-ICE suite of modules makes extensive use of graphical interfaces to simplify the task of
configuring and running the various modules. The graphical interfaces are based on a Project/Run
hierarchy: Projects allow compartmentalization of different analyses, which in turn may contain multiple
runs using different modules. The graphical interfaces have been kept as simple and informative as
possible; the emphasis is on enabling quick and effective solution setup with a minimum of parameters
to configure.

2.1. The Project Manager

A typical view of the Project Manager is shown below:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 15
The FENSAP-ICE Project Manager

The Project Manager permits the organization of different projects ( ) and calculations using the
same graphical interface.

2.1.1. Create a New Project

To create a new project directory, select the File → New project menu at top left, or click the New
project icon:

A window opens to prompt for the new project name and directory.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
16 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Project Manager

Browse the list of directories under the Directory menu. Click the parent directory of the new project,
enter the new Project name and press OK.

Note:

You must be in the project window to create a new project. This window can be accessed

directly by clicking the Home icon .

2.1.2. Open an Existing Project

To load a project directory, select File → Open project menu or click the Open project icon .

A new window opens to prompt for the project directory. The project is then added to the list of
available projects shown in the project window.

2.1.3. Display Projects

By default, projects are shown within folders. They can also be listed in a hierarchical view by clicking

the View icon .

All directories are then listed by type, size, creation and modification dates. Click again on the View
icon to return to the original folder display.

2.1.4. Assign Units to a Project

A window opens to assign units when creating a new project. Units can also be changed at any time
with the Settings → Units menu.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 17
The FENSAP-ICE Project Manager

The unit system applies to all runs within the same project directory. You can select either the Metric
or Imperial system for which all units are pre-defined. The unit of each physical variable can also be
set manually using the Custom option and saved by clicking the disk icon.

If units have been previously assigned to a project, their names will be listed under Current settings.
You can either select these units again or delete them using the following icon .

Note:

Grid files and all initial solutions must be provided in metric units (SI).

2.1.5. Close a Project

To close a project, select File → Close project.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
18 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Manager

2.1.6. Mouse Options

Some actions can be performed by right-mouse clicking a Project icon. The following menu appears:

Table 2.1: Mouse Options

View with... Opens the file viewer.

Rename Changes the name of the project.
Delete Deletes the project icon from the list of available
projects also deletes the project directory.
Remove invalid icons Deletes all project icons with no associated
directories. These are displayed graphically as
broken folder icons.
Remove icon Removes the project icon from the list of available
projects without deleting the project directory.
Set category Groups similar projects under common categories
(effective only in hierarchical view).

2.2. The Run Manager

The run manager provides a graphical interface to configure the specific parameters required to execute
a module, such as type of equations to solve, initial and boundary conditions, artificial viscosity and
matrix solver settings.

2.2.1. Create a New Run

Many separate runs or calculations can be saved within each project. To create a new run, use File
→ New run or click the new run icon:

A window opens to prompt for the selection of the desired software module. Click the solver name
for its selection. The specific name of the calculation should be set in the New run name box, otherwise
FENSAP-ICE will select a default, consecutively numbered name. The following figure shows the
solver selection interface:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 19
The FENSAP-ICE Project Manager

2.2.2. List of Runs

Each run is usually represented by a string of icons that appear to be surrounded by an outline box
when the run is selected. The input files, such as the grid and a restart solution (if required), appear
at the left of the config icon (blue gear). The output and solution files appear at the right of the
config icon. These are usually the current solution file, the heat flux file, the shear stress file, the dis-
placed grid file, the iced geometry tetin file, etc. Their types depend on the solver module.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
20 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Manager

Figure 2.1: Main Run Window

It is possible to create many different runs within the same project, as shown above. The files for each
run are saved in a unique directory. To select one run, simply click its name. The selected run is then
highlighted.

Note:

When more than two runs are displayed, their order can be changed by simply clicking
one run and dragging it with the mouse to another location.

A CHT3D run (Conjugate Heat Transfer) contains a group of modules, each appearing on a separate
line. Each line corresponds to either a fluid or a solid domain, with its own config icon. Multiple fluid
and solid domains can be assigned in this version. The first line, the lone config icon, represents the
CHT3D input parameters that govern the sequence of module execution.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 21
The FENSAP-ICE Project Manager

Figure 2.2: CHT3D Run Contains Multiple Modules

To reduce clutter in the run window, multi-line runs can be folded and unfolded by clicking the
or button next to the main config icon.

Figure 2.3: Minimized CHT3D Run

A similar tree structure is used for FENSAP-F/S (aero-elasticity); multishot ice accretion, automatic
mesh adaptation cycles with OptiGrid, Sequences, etc.

2.2.3. Chronological and Hierarchical Views

The list of runs in large projects can be displayed more compactly in hierarchical mode using the
View icon:

By clicking this icon, the runs and their corresponding files are listed in a hierarchical view. All input
and output files are then shown as subsets of their respective run and project directories. File type,
size, creation and modification dates are also displayed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
22 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Manager

Figure 2.4: FENSAP-ICE Project Window

A second click switches the view icon to chronological view. The next click toggles the icon back to
the default icon view.

Note:

Right-mouse clicking inside any of the runs opens a menu that permits to toggle the view
mode.

2.2.4. Search Box

If the project contains a long list of runs, use the Search box at the top of the FENSAP-ICE window
to quickly filter the displayed runs by name.

Table 2.2: Expressions

DROP MVD

Displays runs containing all terms entered into search criteria (equivalent to Boolean expression
AND).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 23
The FENSAP-ICE Project Manager

FENSAP, DROP

Displays runs containing any terms entered into search criteria (equivalent to Boolean OR).

FENSAP, DROP restart 0.1

Multiple arguments used to search for runs containing either FENSAP or DROP AND restart
0.1.

dir: drop/ice/FENSAP

Search with special operators. Runs of type FENSAP will be displayed from those located in
drop/ice/.

2.2.5. Select a File, Drag & Drop or Copy-Paste

All icons listed to the left of the config icon (blue gear) should be linked to the appropriate files before
setting the input parameters.

Note:

If a file has already been assigned in another run, for example, a grid to be reused, or a
solution file to be used as restart, you can simply drag & drop the icon from that run. A
link is then created between these two files and a different icon is used to underline that
it is a link to another file:

Tip:

To ease data entry, you can also drag & drop the configuration file from one run to another.
As a precaution, the input parameters, especially the boundary conditions, should be
double-checked before running the new calculation, particularly when the grids are different.

To copy-paste an output file to be used as a restart file in another run:

1. Select the output file icon of the source run.

2. Copy (Ctrl+C).

3. Select the restart file icon of the target run.

4. Paste (Ctrl+V).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
24 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Manager

2.2.6. Archive a Calculation

When a calculation is restarted and result files are already present in the run directory, you will be
asked to decide if the existing files should be archived for safe-keeping. If selected, the existing files
are saved (using the .tar and .zip) in the run directory with a user-defined suffix. Archives are
shown in the run with the following icon:

To rename, compress or delete archived solutions, click the archive icon. The existing run can also
be replaced with a previously archived one. To perform this operation, click the To current button.

Figure 2.5: Archive Run Window

2.2.7. Mouse Options

Some actions can be performed by right-mouse clicking a run. The following menu will appear:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 25
The FENSAP-ICE Project Manager

Table 2.3: Menu Options

View Opens the graphical and input parameter

windows.
Options Allows restarting the calculation using the
current solution file as a restart.
Run Opens the graphical window to start the
calculation.
View previous log/graph Opens the graphical window and displays the
convergence of a previous calculation saved
in the run directory.
Copy Copy the current run or input/output file
Paste Paste the copied item to its destination.
Copy/Paste is equivalent to the drag & drop
operation.
Runs (Default View) Changes the listing of runs to the default
mode.
Hierarchical view Changes the listing of runs to the hierarchical
mode.
Chronological view Changes the listing of runs to the
chronological mode.
Open Terminal Opens a shell terminal in the selected
directory. The terminal properties can be
customized in Settings → Preferences →
Applications → TERMINAL.
Rename Allows changing the name of the run
directory.
Archive run Allows archiving a previous run. This is helpful
if you want to rerun one calculation and keep

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
26 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Manager

track of all previous calculations saved in the

same directory.
Import Imports a run directory (grid file, input
parameters, solutions).
Delete Removes the run directory from your account.

2.2.8. Information and Properties

The right side of the Project Manager window provides some extra information on these subjects:

When selecting a file, the Info menu indicates file location, summary, creation and modification dates.

When selecting a grid or solution file, the Properties menu (Read option) lists some of the important
variables in these files (for example, number of nodes, elements, etc.).

The file permission can be changed with Properties. Comments can be added in the Notes field.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 27
The FENSAP-ICE Project Manager

2.3. The Grid File

When a run is first created, or when the grid file is removed from an existing run, double-click the
icon (or right-click to open a drop-down menu) to assign it to the grid file:

A window then opens for the grid file selection. Supported formats are recognized automatically from
the filename terminator. The supported filename terminators are: .cas(.h5) (Fluent); .msh (Fluent,
mesh only); .res (CFX); [Link] (CFD++), .case (CCM+ via EnSight), .uns (ICEM CFD domain
file). If the previous file name terminators are omitted, the file will be treated as a FENSAP format file.
For the description of the FENSAP file format, refer to FENSAP-ICE File Formats (p. 393).

Figure 2.6: Grid Selection Menu

The grid file can either be copied into the run directory, or a link to it can be created to save disk space,
particularly if the same grid is used for multiple runs. Once the grid file is assigned, the broken grid
icon will be replaced with a pristine icon, and the name of the associated file will appear underneath.

Note:

Should the grid not be defined, the config icon of the run turns grey.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
28 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Grid File

2.3.1. Cylindrical to Cartesian Coordinates Conversion

FENSAP-ICE supports grids in both Cartesian and Cylindrical coordinates. However, the menu File
→ Import grid/data with the FENSAP option can be used to convert the coordinates from Cylindrical
to Cartesian before starting the calculation.

2.3.2. Converting the Grid Coordinates to Meters

Important:

The grid coordinates provided to FENSAP-ICE should be in meters. If the coordinates are
in inches or feet, they should be converted using the File → Import grid/data menu, with
the FENSAP option. Follow the sequence of prompts to convert the grid coordinates to
meters.

Figure 2.7: Grid Converter

2.3.3. Importing a Grid from Fluent or Other Solvers

Grid and solution files generated by Fluent can also be imported. Select the File → Import grid/data
menu and use the Fluent option. Follow the sequence of steps to automatically convert the Fluent
grid and/or the solution file into FENSAP format. Fluent is a registered trademark of ANSYS, Inc..

Note:

Recommendations to set up a Fluent air calculation for icing purposes are provided in
Recommendations to Set up a Fluent Calculation (p. 303). Both .dat(.h5) and .cas(.h5)
files must be in the same directory.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 29
The FENSAP-ICE Project Manager

2.3.4. Menu Options

The following list of actions appears when right-mouse clicking a Grid icon:

Table 2.4: Menu Options

Define Opens the graphical and input parameter windows.

View with... Opens a visualization tool browser.
View with FIELDVIEW Opens the Viewmerical post-processor for grid
visualization.
Copy Copy the current run or input/output file.
Paste Paste the copied item to its destination.
Copy/Paste is equivalent to the drag & drop
operation.
Runs (Default view) Changes the listing of runs to the default mode.
Hierarchical view Changes the listing of runs to the hierarchical
mode.
Chronological view Changes the listing of runs to the chronological
mode.
Open terminal Opens a shell terminal in the selected directory.
The terminal properties can be customized in
Settings → Preferences → Applications →
TERMINAL.
Import grid/data Allows grid file conversion.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
30 of ANSYS, Inc. and its subsidiaries and affiliates.
 Input Parameters

Export grid/data Allows conversion of grid and data to other

formats. This option is only valid when a solution
icon is selected.
Archive run Renames and saves existing files in a run by adding
a user-defined suffix to prevent overwriting. This
option is only active when the whole run is
selected.
Delete Deletes the entire run.

2.4. Input Parameters

Click the config icon to assign the input parameters. The input parameter window is split into two
sections:

1. A graphical window on the left.

2. The solvers runs on the right.

The graphical window, common to all solvers, will be described in The FENSAP-ICE Solver Manager (p. 39).
The format and content of the input parameter files vary from solver to solver.

The next chapters of this manual contain detailed information on how to configure these parameters.

Note:

The input parameters can only be defined once the grid file is assigned, since features such
as boundary conditions are grid-dependent. The config icon turns blue when all necessary
files have been properly assigned.

To import an input parameter file, right-click the config icon and select Import.

Tip:

You can drag & drop the Input Parameter icons from FENSAP into DROP3D, and from FENSAP
or DROP3D into ICE3D. Parameters common to the various runs are then set to the same
values.

To copy paste the config file:

• Select the config icon of the source run

• Copy (Ctrl+C)

• Select the config icon of the target run

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 31
The FENSAP-ICE Project Manager

• Paste (Ctrl+V)

Important:

You are strongly encouraged to review the input parameters before launching the calculation.

2.5. Solution Files

All solution files are shown to the right of the config icon. Their icons will appear to be broken until
the files are saved.

2.5.1. List of Output Files

Over and above the log files, each solver module will write specific solution files (default names shown
in brackets):

• The log file.

• The converg and [Link] files containing overall flow solver convergence data and matrix
solver convergence data, respectively.

• The solution file (soln) with the flow variables saved at each grid point.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
32 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solution Files

• If the energy equation is activated, the heat flux file ([Link]) containing the heat fluxes on
all wall element faces.

• If the drag direction is set, the shear stress file ([Link]) containing the forces acting on all
wall element faces.

The flow solution file (soln) is a required DROP3D and ICE3D input file. The other two files
([Link] and [Link]) are required ICE3D input files.

The DROP3D module writes the following output files:

• The log file.

• The converg and [Link] files containing overall flow solver convergence data and matrix
solver convergence data, respectively.

• The solution file (droplet) containing the droplet variables saved at each grid point.

The droplet solution file (droplet) is a required ICE3D input file.

The ICE3D module writes the following output files:

• – The log file ([Link]).

– The solution file (swimsol) containing the icing variables at the surface grid points.

– The initial wall surface grid ([Link], FENSAP format).

– The ice growth surface grid ([Link], FENSAP format).

– If automatic mesh displacement is activated, the 3D volume grid ([Link], FENSAP format)
displaced by the ice growth.

– The CAD file ([Link], ICEM CFD tetin format) of the wall surface displaced by the ice growth.

– The CAD file ([Link], .stl format) of the wall surface displaced by the ice growth.

The C3D module writes:

• The solution file ([Link]) containing the temperature at each grid point.

The FENSAP-ICE-Unsteady module writes:

• The same files as FENSAP and DROP3D (in biphasic mode)

• If the icing option is selected, the displaced grid and the CAD files of the iced geometry (ICEM CFD
TETIN and .stl formats).

The solutions are saved in time at specified intervals.

The OptiGrid module writes:

• The adapted grid file.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 33
The FENSAP-ICE Project Manager

• The flow solution interpolated on the adapted grid to facilitate a restart calculation.

Note:

If the icons do not refresh automatically, place the mouse pointer in the run window and
press the F5 key to update the icons.

2.5.2. Post-Processing
The default FENSAP-ICE post-processing tool is Viewmerical, the built-in post-processor to natively
view FENSAP-ICE solution files.

To change the default post-processing tool, select Settings → Preferences → Postprocessing to

open the configuration window.

Write CFD-Post launch files: At the start of each solver run, a [Link] file is set up in the
run directory, this file is a CFD-Post setup file and can be used to load the data of this folder, directly
from CFD-Post. Alternatively, when CFD-Post is selected as the default post-processor, the View action
will launch CFD-Post with the selected file. For more information regarding this setup file, consult
View Set-up File in the CFD-Post User's Guide.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
34 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solution Files

CFD-Post can also be launched from FENSAP-ICE using the View - Open CFD-Post menu, this command
will launch CFD-Post with the start-up folder being the current project or selected run directory. The
Icing macros are automatically loaded, the *.fsp files from the run folders can be loaded manually.

Note:

CFD-Post can read FENSAP grid and solution files and the .fsp view set-up file, see the
CFD-Post manual entry: FENSAP-ICE Files.

When a different option is selected, the pull-down menu will change to respect the new default setting.
For example, after selecting Viewmerical as the default post-processor, the pull-down menu will show
View with VIEWMERICAL.

A tool to convert the FENSAP-ICE grid and solution files into the TECPLOT ASCII file format is also
available. The converter nti2tecplot can be found in the FENSAP-ICE installation directory.

Note:

• The FENSAP-ICE grid file should be named grid.

• The FENSAP solution file should be named soln.

• The DROP3D solution file should be named droplet.

• The ICE3D solution file should be named swimsol.

• The ICE3D initial and displaced grid files should be named, respectively, [Link] and
[Link].

2.5.3. Mouse Options

Some operations can be performed by right-mouse clicking a solution icon.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 35
The FENSAP-ICE Project Manager

Table 2.5: Mouse Options

Define Opens a file browser to assign a solution file.

View Opens a simple graphical editor to visualize the
grid and solution.
View with VIEWMERICAL Opens the Viewmerical post-processor for
visualization.
Copy Copy the current run or input/output file.
Paste Paste the copied item to its destination.
Copy/Paste is equivalent to the drag & drop
operation.
Runs Changes the runs display mode to the Default
mode.
Hierarchical view Changes the listing of runs to the Hierarchical
mode.
Chronological view Changes the listing of runs to the Chronological
mode.
Open terminal Opens a shell terminal in the selected directory.
The terminal properties can be customized in
Settings → Preferences → Applications →
TERMINAL.
Import grid/data Allows grid file conversion. Only active when a
grid file is selected.
Export grid/data Allows conversion of grid and data to other
formats. This option is only valid when a solution
icon is selected.
Archive run Renames and saves existing files in a run by adding
a user-defined suffix to prevent overwriting. This
option is only active when the whole run is
selected.
Delete Deletes the entire run.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
36 of ANSYS, Inc. and its subsidiaries and affiliates.
 Quit FENSAP-ICE

2.6. Preferences
Some settings can be configured and changed using the Settings → Preferences menu.

Table 2.6: Settings

General Change the font size, type, icon width, etc.

Display Change the level of details to be shown by the
graphical window (grid, geometry, etc.).
Project Change the default project directory.
Applications Change the external executables used by the
graphical interface, including post-processors, text
editors, postscript editors, etc.

2.6.1. Font Size

To change the font size used throughout FENSAP-ICE, go to the Settings → Preferences → General
tab, and adjust the font and its size.

2.7. Quit FENSAP-ICE

To quit FENSAP-ICE, select File → Exit, then confirm.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 37
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
38 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 3: The FENSAP-ICE Solver Manager
The following sections of this chapter are:
[Link] Graphical Window
[Link] Run Window

The FENSAP-ICE solver manager groups the grid display, the parameter editor, the launch configuration
and the run monitor into a single window. A separate solver manager can be started for each individual
run. Double-click the Input Configuration icon (blue gear) to open the solver manager. Click the Run
button at the bottom right of the window to display the execution options and launch a calculation.

The Graphical Window (left) displays the geometry and grid. Some of the input parameters can be
displayed directly in this window. For example, the initial velocity vector and boundary conditions can
be displayed graphically to prevent possible errors.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 39
The FENSAP-ICE Solver Manager

The Parameter Window (right) allows access to the input parameters. The display of configurable
module parameters is module-dependent. Refer to subsequent chapters of this manual for guidelines
on how to configure the input parameters.

The Calculation Window can be accessed by clicking the Run button. It lists all the parameters required
to launch a calculation, and shows the convergence monitors in real-time.

Switch between the Parameter and Calculation Windows using the Run button.

Note:

Input parameters cannot be edited once a calculation has started.

3.1. The Graphical Window

The following sections of this chapter are:
3.1.1. Graphical Display
3.1.2. Add/Remove Details from View
3.1.3. Advanced Graphical Operations

3.1.1. Graphical Display

By default, selected boundaries of the computational domain are shown in white, inlets in red, other
boundaries in blue and all solid surfaces in grey.

The Boundary conditions section of the parameter window can be used to add more geometrical
details in the graphical window. This menu varies from one solver to another; refer to subsequent
chapters of this manual for selecting the boundary conditions tags.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
40 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Graphical Window

3.1.2. Add/Remove Details from View

The level of detail displayed in the graphical window can be defined using the display box icon located
on the left below the graphical window:

Clicking this icon opens a menu that provides access to the configuration of the display settings:

[Link]. Remove/Activate the Graphical Display

Select Remove 3D Panel to remove the graphical display. The display box icon changes to .

Click again on the display box icon and select either Full view or Simple view to reactivate the
graphical display.

[Link]. Full and Simple Views

The Full view mode displays all geometrical features that have been defined with the Configure
option. In Full view mode, the graphical box icon is shown in blue:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 41
The FENSAP-ICE Solver Manager

The Simple view displays all geometrical features as bounding boxes. This option may be useful
to speed-up the graphical refresh time on some computers. In Simple view mode, the graphical
box icon is shown in grey:

[Link]. Configure
Both display modes can be customized using the Configure menu option:

Table 3.1: Configure Menu Options

Shaded Shows the selected boundaries of the

computational domain as a colored surfaces.
Shaded + Wireframe Adds the surface grid to the Shaded surface.
Wireframe Only displays the grid on each selected boundary.
Shaded Box Displays the selected boundary as a colored
boundary box.
Wireframe Box Displays the selected boundary as a transparent
bounding box.

The menu Full view, mouse motion applies to the graphical display when the mouse is in move-
ment. The menu Simple view only offers the shaded and wireframe box options.

[Link]. Axis Display and Alignment

The axis display shows the current view direction:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
42 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Graphical Window

It can also be used to align the display along prescribed directions:

Click any axis to align the view along that axis;

Click the central gray box (at origin of the axis) to reset the view to its original 45 deg. Isometric
view;

Right-mouse click the axis area to open a new menu proposing 6 preset view directions and two
isometric views.

[Link]. Fit to View

Right-mouse click in the axis area and select Fit to view to center the graphical features currently
displayed in the graphical window.

[Link]. Apply Translational and Rotational Periodicity

This option displays the grid by applying either translational or rotational periodicity:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 43
The FENSAP-ICE Solver Manager

Right-click in the axis area to open the display menu, and select View symmetry. The X=0, Y=0
and Z=0 symmetry planes are used for translational periodicity:

The Rot. around X,Rot. around Y or Rot. around Z rotation options are used with rotational
periodicity:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
44 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Window

For rotational periodicity, both the rotation angle (in degrees) and the number of repetitions are
required.

[Link]. Panning/Rotation

Click the first icon at the top left of the graphical window to enable object displacement . To
rotate (left-click), pan (center-click), and zoom (right-click) on the object. You can also zoom on the
object with a bounding box by holding down the Ctrl key while pressing the left mouse button.

Click the second icon (zoom) button for an interactive zoom (left-click). Center-click to undo
the zoom.

[Link]. Selection

Click the selection icon to select a geometrical feature in the graphical window by clicking it
with the mouse.

This can be useful for selecting a specific boundary interactively from the graphical window, partic-
ularly when many surfaces are grouped into a family, instead of cycling through the list of boundary
conditions shown in the Boundary conditions menu.

3.1.3. Advanced Graphical Operations

More advanced graphical operations can be performed using the advanced graphical icon .

These include color and camera management, as well as some operations on the grid file (reloading
the grid, etc.).

3.2. The Run Window

Once the grid and input parameters have been defined, click the Run icon to launch the calculation.

A new window opens to control and monitor the calculation. If you are already in the FENSAP-ICE

Solver Manager window, click the Run button at the bottom of the window to switch to

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 45
The FENSAP-ICE Solver Manager

the Run environment. You can always return to the input parameter environment by clicking the Config
button at the bottom of the window.

The input parameters cannot be modified after the execution has started.

3.2.1. Calculation Settings

The run configuration window shows the configurable execution settings:

[Link]. Parallel Calculations

FENSAP, DROP3D, ICE3D, OptiGrid all use the Open MPI (Message Passing Interface) library to signi-
ficantly shorten the solution time for large-scale problems. The grid is first partitioned with ParMETIS
(courtesy of George Karypis, Kirk Schloegel and Vipin Kumar, copyright University of Minnesota).
Then each processor operates on its own (smaller) subdomain grid and exchanges information with
the other processors through the Open MPI interface.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
46 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Window

Enter the Number of CPUs to be used by the solver.

The mpirun command is used by default to launch the MPI solvers. On some machines, however,
this command must be customized. To do so, click the Configure... button. A new window opens
to prompt for the MPI command line:

If necessary, override the standard mpirun command and browse to select the appropriate mpirun
wrapper to be used by MPI.

If necessary, add the appropriate optional parameters required by the mpirun wrapper to manage
the parallel calculation.

The resulting complete command line is displayed for verification before the execution is started.

Additional custom settings can be defined in the Advanced section. Group MPI jobs on a minimum
of compute-nodes is useful for CHT3D computations where the flow solver executes on more
processors and for longer times before inter-processor synchronization than either ICE3D or C3D.
This option allows ICE3D and C3D to run compactly and more efficiently on fewer cores than the
flow solver, without being broken-up across all the nodes. A custom machinefile is required to
enable this option. The custom machinefile is assigned in the Additional mpirun parameters

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 47
The FENSAP-ICE Solver Manager

box by specifying the MPI option -machinefile machinefile_name. The custom machine
file should list the cores of each node in sequential order.

Note:

Refer to MPI for additional information and troubleshooting help concerning the config-
uration of MPI on clusters and multi-core machines.

The last two options, Custom compute-node size and Custom master-node size are
only active for OptiGrid. If either of the two values is set to a value smaller than the
number of cores per node, fewer cores per node will be used and more memory is
available to the active cores.

[Link]. Queuing Systems

The application can be launched using different queuing systems (PBS, SGE, MOAB, AT, GUI, NULL,
CUSTOM). If no queuing system is installed on the machine, select None.

Additional parameters can be added for each queuing system by clicking the Configure button.
These parameters are specific to each queuing system. See MPI for more information.

[Link]. Save Your Preferences

The solver settings can be saved for subsequent use by clicking the Save button. This setting applies
to all runs saved in the same project directory.

3.2.2. Start the Calculation

Calculations are launched by clicking the Start button. Once the calculation is launched, the back-
ground color of the run in the main window will change.

Note:

Refer to License Server Setup for considerable information and troubleshooting help con-
cerning the configuration of MPI on clusters and multi-core machines.

[Link]. Compute Drag Polar Curves

FENSAP can automate the computation of the drag polar curves by launching a sequence of com-
putations with different angles of attack (or yaw angle). To do so, enter the minimum and maximum
angles of attack (or yaw angles), as well as the number of increments, in the appropriate Sweep
variable boxes. The step is automatically displayed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
48 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Window

To speed-up the solution process, set the total number of CPUs and distribute them equally for
each calculation. In the example shown above, 8 FENSAP runs will be computed using 4 CPUs each.
Since only 16 CPUs have been assigned in Settings, FENSAP-ICE will run 2 sequential sets of 4
concurrent angles of attack (or runs).

3.2.3. Monitoring a Run

The main solver execution steps can be monitored: read grid, read initial solution, compute each time
step, etc. Successful completion or error messages, if any, are displayed in the window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 49
The FENSAP-ICE Solver Manager

[Link]. The Solver Log File

The log section shows the output file of the solver. Its contents vary from solver to solver. The
output file should be kept in the run directory since it can be essential in obtaining quick technical
support from ANSYS.

[Link]. The Convergence Graphs

The graph mode monitors the convergence graphs. Different variables can be plotted depending
on the solver. For example:

• Residuals of the momentum, energy and turbulence equations (FENSAP)

• Residuals of the continuity and momentum equations (DROP3D)

• Lift and drag coefficients (FENSAP)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
50 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Run Window

• Classical and Gresho total heat (FENSAP)

• Total collection efficiency (DROP3D)

• Convergence of the GMRES linear matrix solver (FENSAP, DROP3D)

• Probe point values (FENSAP, DROP3D)

• Mass and energy conservation (FENSAP)

• Total mass of accreted ice (ICE3D)

• Time variation of the film height, temperature and, rate of ice accretion (ICE3D)

• Minimum and maximum temperatures (C3D, CHT3D)

• Number of nodes and elements (OptiGrid)

• Error distributions before and after mesh adaptation (OptiGrid)

The axis of the graph can be changed and the convergence curve saved and printed by clicking
the Options button.

Click the convergence window to display the exact value at the cursor location (vertical red line).
Dragging while holding the left mouse button allows the cursor to move along the curve. The X-
and Y-axis values are shown below the graph. Clicking the right mouse button cancels the graph
probe.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 51
The FENSAP-ICE Solver Manager

Hold Shift and drag horizontally to zoom along the X-axis. Hold Shift and drag vertically to zoom
along the Y-axis. The zoom region is then highlighted in yellow until the mouse button is released.

Hold Shift and click the left mouse button in the convergence window to zoom out, or click the
middle mouse button.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
52 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 4: FENSAP - Flow Solution
The following sections of this chapter are:
[Link] Physical Model
4.2. Flow Conditions
4.3. Boundary Conditions
4.4. Domains
4.5. Solver Parameters
4.6. Output

This chapter describes the input parameters of FENSAP, the flow solver module of the FENSAP-ICE
package.

4.1. The Physical Model

Select the Air option in the Physical model menu to enable the FENSAP flow solver.

Additional physical models are Droplets, Air + Droplets and EID (Extended Icing Data), which will be
explained in the following chapters.

4.1.1. Grid File Assignment

The grid file should be assigned before setting up the input parameters, since some of them, such
as the boundary conditions, are grid-dependent.

The grid file should be assigned using the grid icon in the run window, however it can also be reset
in this panel. In this case, however, only grids in FENSAP format are allowed, FENSAP-ICE will not

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 53
FENSAP - Flow Solution

automatically verify the format of the grid file and prompt for conversion. The grid file is then read
to detect the boundary conditions. Note that if the grid is replaced with a different one, it is imperative
to review the configuration of the boundary conditions.

4.1.2. The Continuity and Momentum Equations

The flow field is modeled by partial differential equations for the conservation of mass, momentum
and energy. The conservation of mass for a compressible flow, for example one where the density of
the fluid is not a linear function of both pressure and velocity, can be written as:

where is the density and is the velocity vector. The subscript refers to the air solution. This
equation is also known as the continuity equation.

For a Newtonian fluid, Newton second law of motion states that the total force acting on a fluid
particle is equal to the time rate of change of its momentum. This can be written in 3D using a set
of 3 non-linear equations, shown here in vector form:

which are known as the Navier-Stokes equations, where is the stress tensor, or:

is the static pressure and is the dynamic viscosity. The special case of inviscid fluid flows, where
the dynamic viscosity is set to zero, yields the Euler equations.

For a viscous laminar flow, the viscosity is defined empirically by Sutherland law:

where refers to the static air temperature in Kelvin, and where the subscript ∞ indicates reference
values for air: = 288 K and = 17.9 10-6 Pa s.

This laminar viscosity is constant and is computed using the reference air static temperature of the
Conditions panel of FENSAP-ICE.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
54 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

For viscous flows, select Navier-Stokes. For inviscid flows, select Euler in the Physical model section.

4.1.3. The Energy Equation

The third physical principle concerns the conservation of energy and states that the total energy of
the system must be conserved, or:

where and are the total internal energy and enthalpy, respectively, is the ratio of specific heats
which equals 1.4 for air (perfect gas), and κ is the thermal conductivity, computed in a similar way
to the laminar dynamic viscosity:

where refers to the static air temperature in Kelvin, and where the C1 is equal to
.

The laminar dynamic viscosity is constant and is computed using the reference air static temperature
of the Conditions panel of FENSAP-ICE.

To solve for the energy equation, select Full PDE.

The set of eight flow equations with nine unknowns, expressed in a primitive variable form
( ), describes the steady laminar (viscous, non-turbulent) flow.
The equation required to close the system is the equation of state for an ideal gas:

where = 287.053763 KJ/kg is the Gas Constant for air. This equation can be transformed into the
algebraic constant stagnation enthalpy equation for steady-state inviscid flows, shown below.

If the Ideal Gas option is selected (default), the properties of the fluid are defined using the reference
static temperature and remain constant everywhere. If the Real Gas option is selected, the fluid
properties are a function of the local static temperature and vary throughout the solution domain.

[Link]. Adiabatic Flows

If the following assumptions are true:

• The flow is adiabatic.

• No heat is absorbed nor radiated from the volume.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 55
FENSAP - Flow Solution

• No heat is conducted in the fluid.

• The fluid is chemically inert.

• No work is done on the fluid.

• The potential energy of the fluid is constant.

Then the full energy equation in PDE form can be converted to an algebraic equation that implies
that the stagnation enthalpy remains constant along streamlines:

To select this option, choose Constant enthalpy.

Note:

This option reduces the computational effort, but can only be applied to flows that sat-
isfy the conditions listed above.

[Link]. Conservative Energy Equation

By default, FENSAP solves the energy equation in non-conservative form, which results in robust
convergence especially when the momentum and energy systems are uncoupled. It is also possible
to solve this equation in Conservative Form, which increases heat flux accuracy for transonic flows.
This is currently a beta feature, pending full integration with actuator disks and unsteady flows
with mesh displacement (ALE). To have it visible in the energy equation options in the model
panel, Show advanced / beta solver options in the Settings → Preferences → General tab must
be checked. This will bring the two additional options Full PDE – Conservative and Energy-only
– Conservative in the Energy equation selection box.

4.1.4. Turbulent Flows

A variety of turbulence models have been implemented in FENSAP. All models are based on the
statistical approach to turbulence, for example all the variables are time-averaged and a steady flow
is computed. The effect of turbulence is represented in the momentum equations via the eddy viscosity
hypothesis. The turbulence models provide the spatial distribution of the eddy viscosity which is then
used in the momentum equations.

[Link]. The Spalart-Allmaras Model

To select this turbulence model, choose Spalart-Allmaras in the turbulence models section.

The Spalart-Allmaras turbulence model is a one-equation model. It is based on the transport of a

modified eddy viscosity from which the effective eddy viscosity coefficient is [Link]
modified eddy viscosity is related to the effective eddy viscosity such that:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
56 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

where is obtained from the transport equation:

with

and d is the distance to the nearest wall. The two functions and are defined as

where

and is the laminar kinematic viscosity. The destruction term is:

where

The closure coefficients of the model are set as follows:

The eddy/laminar viscosity ratio is used to compute the initial turbulent viscosity coefficient when
starting the calculation. For external flow calculations, and if the incoming flow is not turbulent,
this parameter should be set to a low (but not zero) value, for example 10-5 (default). For internal
flows, it should be increased to approximately 50 to 100.

The turbulence equations are solved separately from the Navier-Stokes equations. The Number of
iterations is the number of turbulence iterations per Navier-Stokes iteration. You should select a
value between 1 (default) and 3 (difficult situations).

The Relaxation factor is used when updating the turbulence variables. For Spalart-Allmaras, a value
of unity (default) is strongly recommended. However, a lower value should be used if the turbulence
equation becomes unstable (erratic convergence).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 57
FENSAP - Flow Solution

[Link]. The Low Reynolds k-ω Model

The turbulence model is based on the transport of the turbulent kinetic energy , and the
second transported scalar can be interpreted as a frequency because of its dimension equivalent
to 1/time.

The transport equations are:

The default model coefficients are set as follows:

and the eddy viscosity is given by:

To select this turbulence model, choose Low-Reynolds K-omega in the list of turbulence models.

The eddy/laminar viscosity ratio is used to compute the initial turbulent viscosity coefficient when
starting the calculation. For external flow calculations, and if the incoming flow is not turbulent,
this parameter should be set to a low (but not zero) value, for example 1 (default value) or below.
For internal flows, it should be increased to 50 to 100.

Turbulence intensity ( ) represents the level of turbulence and is usually shown in percentage. It
is defined as the ratio of the root-mean-square of velocity fluctuations to the mean velocity mag-
nitude. The default value of turbulence intensity in FENSAP is 1%. For low-turbulence case, for ex-
ample an incoming external flow approaching an aircraft, the turbulence intensity can be well below
1%. In this case, = 0.08% is recommended. For internal flows, the turbulence intensity is typically
high, which may vary from 1% to 5% for medium-turbulence cases and increase up to 20% for
high-turbulence cases. The local turbulent kinetic energy is computed from :

The turbulence equations are solved separately from the Navier-Stokes equations. The number of
iterations is the number of turbulence iterations per Navier-Stokes iteration. You should select a
value between 1 (default) and 3 (difficult situations).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
58 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

The relaxation factor is used in the update of the turbulence variables. For the model, a value
of 1 (default) is recommended. However, a lower value should be selected if the turbulence equations
become unstable (erratic convergence).

[Link]. The k-ω SST Model

The transport equations of Menter’s SST model are

where the blending function is defined by

with

and is the distance to the nearest wall. is equal to zero away from the surface ( ), and
switches over to one inside the boundary layer ( ).

The turbulent eddy viscosity is defined as follows:

where is the invariant measure of the strain rate, for example, and is a second
blending function defined by

A production limiter is used in the SST model to prevent the build-up of turbulence in stagnation
regions:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 59
FENSAP - Flow Solution

All constants are computed by a blend from the corresponding constants of the and the
models via . The constants for this model are:

4.1.5. Surface Roughness

Select No roughness for a smooth wall, otherwise several sand-grain roughness options are available.
All three turbulence models currently available in FENSAP-ICE can simulate constant and variable
sand-grain roughness distributions.

[Link]. Sand-Grain Roughness

If the Specified sand grain-roughness option is selected, the Nikuradse equivalent sand-grain
roughness height, (in meters) should be provided.

The roughness is set to a value of 0.5 mm by default when activated, but can be modified if required.

Tip:

Although it is possible to specify arbitrary roughness values, past a certain limit (~ 5-10
mm for a wing) where the roughness height would trigger macroscopic flow separation
effects, roughness should be simulated at the surface geometry and grid level, rather
than through the turbulence model.

[Link]. The NASA Roughness Model

If NASA sand-grain roughness is selected, the surface sand-grain roughness is computed with an
empirical NASA correlation for icing.

The sand-grain roughness value is computed from the product of the following coefficients:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
60 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

where LWC is the liquid water content, and . The corresponding value of
sand-grain roughness is obtained from the formula:

and is shown by the graphical interface in the Height field.

[Link]. The Shin et al. Roughness Model

If the Shin et al. sand-grain model is selected, the empirical correlation for the surface sand-grain
roughness is computed with the Shin and Bond formula, which modifies the NASA correlation with
the following factor:

where is the droplet mean diameter, in microns. The corresponding value of sand-grain
roughness is obtained from:

and is displayed by the graphical interface in the Height box.

[Link]. Variable Roughness from a File

If the Sand-grain roughness - file option is selected, the sand-grain roughness will be read from
a node-based input file (See The Sand-Grain Roughness Distribution File ([Link]) (p. 408)).
The input file must be named [Link] and copied in the FENSAP run directory.

ICE3D writes a [Link] file that can be used for multishot ice accretion.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 61
FENSAP - Flow Solution

[Link]. Variable Roughness from the Boundary Conditions

If the Sand-grain roughness - BC type option is selected, individual sand-grain roughness values
can be assigned to any wall surfaces listed in the Boundaries panel.

When this option is selected, an additional sand-grain roughness value assignment box appears
for each wall family listed in the Boundaries conditions panel. The [Link] file will then
be created automatically by FENSAP-ICE.

[Link]. Variable Roughness from the Beading Model

The FENSAP-ICE system provides a very unique and powerful means of accounting for the roughness
of the ice shapes through the beading model. Strictly speaking, the roughness due to the water
beading process is computed by the ICE3D module based on local conditions on the contaminated
surface (See Impact of Beading (p. 179)).

In multishot ice accretion simulations, the roughness data can be transferred to the flow solver to
compute the appropriate shear stresses and heat fluxes. The roughness due to the freezing of the
beads is both spatially- and temporally-dependent, hence it is useful only in the context of a fully
unsteady calculation, or in the multishot approach, which is a more cost-effective quasi-steady ap-
proximation of the fully unsteady simulation.

The multishot configuration procedure is described in Multishot Run Creation and Basic Configura-
tion (p. 290). With this approach, when the beading model is selected in the ICE3D configuration,
FENSAP-ICE will automatically perform all the necessary steps to link the roughness data with the
flow solver.

4.1.6. Transition to Turbulence

Two transition mechanisms are available in FENSAP with the Spalart-Allmaras turbulence model.
The transition is enabled in the Transition section of the Model panel.

If the Spalart-Allmaras turbulence model is selected, transition can be imposed. If no transition is

selected, the boundary layer will be fully turbulent.

With the Fixed transition option, transition is imposed in the turbulence model through tripping
functions and a special boundary index set in the grid file (See FENSAP-ICE File Formats (p. 393)) at
the fixed transition location. At least one wall boundary face in the grid must be assigned to this index.
This index (2,000 to 2,999) is specified with the Transition BC index. The Fixed transition model
injects a small amount of turbulence in the boundary layer to trigger transition.

The tripping intensity is set by default to 10-5. To compute transition length, the orientation of the
chord should be given, either along the X-, Y- or Z-axis.

With the Free transition option, transition from laminar to turbulent is automatically set by FENSAP
based on adverse pressure gradients. This option requires an eddy/laminar viscosity ratio smaller or
equal to 1.e-5 (very low far-field turbulence).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
62 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

For the SST turbulence model, a one-equation local correlation-based intermittency transition
model is available. It integrates experimental correlations into standard convection-diffusion transport
equation using local variables. The transport equation of intermittency is

In the production term, the function determines the length of transition. The formulation of
the function , which is used to trigger the intermittency production, contains the ratio of the
local vorticity Reynolds number to the critical Reynolds number :

The absolute value of stain rate and vorticity are defined as

The critical Reynolds number is computed algebraically using local variables:

in which

In the formulation of , where is the velocity vector and is the wall-normal

vector. The model constants are:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 63
FENSAP - Flow Solution

The coupling between the transition model and the SST turbulence model is accomplished by
modifying the production and destruction term of turbulent kinetic energy equation:

Moreover, an additional production term has been introduced into the -equation to ensure
proper generation of at transition points for arbitrary low level. It is designed to turn itself off
when the transition process is completed and the boundary layer has reached the fully turbulent
state. The expression for the additional source term reads as

where the constants are

The blending function in SST that is responsible to switching between the and models
is reformulated as follows:

4.1.7. Body Forces

Two different types of body force can be applied during simulations.

[Link]. Gravity

Select None to neglect gravity (typical of most CFD applications). For convection-driven problems,
the force of gravity can be included by adding the following source term to the right-hand side of
the Navier-Stokes equations:

To do so, select Gravity in the list of body forces. Enter the components of the gravity vector in
the body force window. Click the display icon to display the gravity vector in the graphical
window as shown in the following figure.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
64 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

Click the display icon again to remove the gravity vector from the graphical window.

Important:

When gravity is activated, the pressure applied at the exits will be automatically calculated
using the barometric formula to account for the pressure gradient that naturally occurs
in the stratified atmosphere and the static pressure set at the far field or exit boundary.
In external air flow simulations with large far fields, failure to do so would result in sig-
nificant inaccuracies in the boundaries and possibly cause divergence.

Finally, the gravity vector should be adjusted with respect to the angle of attack specification.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 65
FENSAP - Flow Solution

[Link]. Rotating Frame of Reference

For CFD calculations in a steadily rotating frame of reference (for example rotors), select the Rotation
speed option in the Body forces section.

The three components of the rotation speed Ω should then be entered in the Body force window.

The center of rotation is located at the origin (0,0,0). Source terms are added to the momentum
equations to introduce the Coriolis and centrifugal forces acting on the fluid in the relative frame:

If at least one of the three components is non-zero, a reminder that the frame of reference has
been switched to relative will appear at the bottom of the FENSAP window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
66 of ANSYS, Inc. and its subsidiaries and affiliates.
 Flow Conditions

Note:

The default frame of reference is absolute. If a rotational velocity is specified, the frame
of reference becomes relative, for example, the entire grid is rotating. The velocity vectors
are written in absolute components in the solution file. If the solution is used as a restart,
the presence of the rotational velocity components in the header of the FENSAP solution
file will automatically trigger conversion to relative components. When visualizing the
solution with Viewmerical, both the absolute and relative velocities will be available for
display.

Tip:

In some cases to accelerate convergence of steady-state flows it is beneficial to initialize

the domain inside rotating components with the rotation rate of the component. More
details can be found in Multi-Domain Initialization (p. 97).

4.2. Flow Conditions

FENSAP and DROP3D solve the system of governing equations in non-dimensional form. For this reason,
it is important to specify accurate reference conditions.

Important:

When performing icing calculations, it is extremely important that all solvers be initialized
with the same set of reference conditions. The drag & drop feature of FENSAP-ICE will
transfer the reference conditions automatically and is therefore the easiest way to ensure
that all solvers are properly initialized.

4.2.1. Reference Conditions

These reference values are used to transform the Navier-Stokes equations to non-dimensional form.

The four reference values to define are:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 67
FENSAP - Flow Solution

• The characteristic length,

• The magnitude of the velocity vector,

• The static pressure,

• The static temperature,

Other non-dimensional reference variables are automatically computed by FENSAP, such as:

Reynolds number

Reference Mach number

Adiabatic stagnation temperature

The grid coordinates are scaled by the characteristic length.

The fluid properties (laminar viscosity, conductivity, etc.) are initialized using the reference air density,
temperature and pressure. The relevant properties are printed in the header of the log file at the start
of the execution process.

Note:

When carrying out icing simulations with FENSAP-ICE, it is highly recommended that the
reference conditions represent the icing cloud conditions and the true air speed (TAS) of
the aircraft or test article. In case of helicopter rotor analysis, the blade tip speed is the
ideal choice for reference velocity. The reference conditions are used to non-dimensionalize
the model equations and the collection efficiency. Certain numerical aspects in DROP3D
that are used to improve stability and convergence in the shadow zones will be affected
by these settings. Characteristic length should have no impact on the solution other than
changing the scale of the residual plots.

Tip:

Both Reynolds and Mach numbers should match those of the flight conditions or the ex-
perimental data to be compared to. FENSAP computes these two reference quantities and
lists them in its Conditions panel and in the log file. It they do not match, the values of
the reference pressure, temperature, characteristic length, or the norm of the velocity
vector should be adjusted.

The Adiabatic stagnation temperature is particularly useful for glaze ice simulations. In
order to obtain meaningful heat fluxes for ICE3D, the temperature that should be imposed
on the walls should be a few degrees above this value.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
68 of ANSYS, Inc. and its subsidiaries and affiliates.
 Flow Conditions

4.2.2. Setting Pressure from Altitude

The value of the reference static pressure can be imposed from altitude values according to the US
Standard Atmosphere (1976) correlation.

To do so, click the Air static pressure arrow point and select Altitude. FENSAP automatically computes
the pressure based on the U.S. Standard Atmosphere (1976). Click again on the Altitude arrow to
revert to Air static pressure.

The units for altitude can be changed either to meters or feet by clicking the arrow next to the units.

4.2.3. Initial Solution

The Navier-Stokes equations are a non-linear system of equations. The discretized equations are lin-
earized with respect to the primitive variables and then an iterative process is started from an initial
guess. If the initial solution is reasonably close to the final one, the iterative process should converge
to an accurate solution sooner. For some problems with wide temperature variations (for example a
hot jet in cold air), the convergence may be improved by starting the calculation using an initial
static temperature more representative of the physics to be solved. To do so, check the box at the
bottom of the menu and set the desired initial temperature value.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 69
FENSAP - Flow Solution

[Link]. Velocity Components

If the Velocity components option is selected, the three components of the initial velocity vector
are imposed throughout the computational domain.

Right-mouse click in any of the three boxes to display a menu that present options to copy velocity
values already set during the run configuration process.

[Link]. Velocity Angles

If the Velocity angles option is selected, the three components of the initial velocity are obtained
from the two angles and the norm of the reference velocity (See Reference Conditions (p. 67)).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
70 of ANSYS, Inc. and its subsidiaries and affiliates.
 Flow Conditions

Note:

The angle of attack is the angle of the velocity in the X-Y plane. The yaw angle is the
angle of the velocity in the X-Z plane. Both angles are in degrees. The exact formula to
convert the angles of attack into velocity components and the inverse transformations
are:

where is the angle of attack (X-Y plane), is the Yaw angle (X-Z plane) and is the reference
air velocity.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 71
FENSAP - Flow Solution

[Link]. Displaying the Initial Velocity Vector

Click the display icon to display the initial velocity vector in the graphical window, as shown in
the following figure.

Click the blue icon again to remove the velocity vector from the graphical window.

4.2.4. Restarting a Calculation

If the option Solution restart is selected, the flow field is initialized with a previous flow solution
read from a file. This option is used to restart a calculation or to perform calculations at different flow
conditions starting from an already converged result.

Note:

It is still possible to change the inflow conditions.

Click the browse button to open the file browser and select the solution file to be used for restarting
the calculation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
72 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

The restart solution can be post-processed using Fieldview by clicking the View with FIELDVIEW
button. FENSAP-ICE automatically converts the grid and restart solution file into Fieldview unstructured
format and opens the post-processor.

Note:

If the grid file is in cylindrical coordinates, the velocity components should be specified as
Vr (m/s), Vθ (rad/s) and Vz (m/s).

4.3. Boundary Conditions

All FENSAP-ICE modules solve systems of partial differential equation and therefore require sets of
suitable boundary conditions.

The Boundary conditions panel lists all boundary condition indices present in the grid file. The possible
indices and their usage are:

Index Boundary Condition Type

BC_1000 to BC_1999 Inlet/Far field
BC_2000 to BC_2999 Wall
BC_3000 to BC_3999 Outlet
BC_4000 Generalized symmetry
BC_4100 X-symmetry

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 73
FENSAP - Flow Solution

Index Boundary Condition Type

BC_4200 Y-symmetry
BC_4300 Z-symmetry
BC_5000 to BC_5099 Periodic – translational and rotational
BC_6000 to BC_6999 Internal surface – actuator disks, screens, heater
pads, custom post processing, etc...
BC_7000 to BC_7999 Non-conformal interfaces, Rotor/fuselage gap
boundaries

Inlets, walls, outlets and internal surfaces have subtypes that need to be set in their respective menus,
which are explained in the sections below.

The name of each boundary condition tag can be modified in the Label box. The name of a boundary
is for bookkeeping purposes only, it does not change the type nor the function of the boundary. To
view the boundary surface in the graphical window, check the square box next to its label.

Multiple boundary conditions can be selected as a group with the Shift or Ctrl keys. If the visibility
check box is toggled, the action will apply to the whole selection. If the selected boundary conditions
are of the same type, such as inlet, wall or outlet, any setting changes will be applied to all the selected
boundary conditions.

4.3.1. Inlets and Far-fields – 1000-BCs

Inlet boundary indices can range from 1,000 to 1,999. Indices ranging from 10 to 19 are still supported
for backward compatibility but are converted to the four-digit format. Several inlet types are supported:

In general, velocity components and static temperature are imposed at subsonic inlets and static
pressure specification is done on subsonic exits. The different inlet types listed below recast the for-
mulation to allow imposition of these variables through total conditions, mass flow rates, or Mach
number.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
74 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

To display the boundary velocity vector in the graphical window, Click the display icon:

If a turbulence model is selected, an inlet profile of turbulent viscosity (for Spalart-Allmaras),

or (for two-equation models) can be imposed on some inlet types. Refer to Inlet Profiles for Turbu-
lence (p. 94) for more information.

When solving in rotational frame of reference by enabling rotation in body forces menu in the model
panel, an additional setting appears on all inlets to specify if the velocity components that entered
the domain are for the absolute or the rotating frame. In general, the known conditions are in the
form of absolute velocity for the primary inflow boundary condition to the domain. However, for
secondary inlets attached to rotating components in the domain (turbomachinery rotor blade vents,
etc.), the Reference frame should be set to Relative.

[Link]. Subsonic
Subsonic inlets require the three velocity components and the static temperature. These values are
imposed as Dirichlet conditions on all boundary nodes without the possibility to change them
during iterations. You must check that the assigned velocity vector is in fact pointing into the
computational domain at every node on the boundary, otherwise the calculations will diverge.
Import reference conditions button can be used to copy the velocity vector and the temperature
from the initial/reference conditions specified in the Conditions tab.

In subsonic inlets, the pressure is set free and cannot be adjusted while static temperature and
velocity components are specified. The pressure of the domain will be set by the conditions on
subsonic outlets.

[Link]. Supersonic or Far-Field

This inlet boundary type is a more generic, which covers subsonic, supersonic, and far-field situations.
In addition to static temperature and velocity, static pressure is also needed. The boundary auto-
matically determines the inflow/outflow state of the boundary nodes using node normal vectors
and the velocity direction to impose proper Dirichlet/free states for flow variables. In this manner,
inflow nodes will act the same way as if they were set as subsonic, and outflow nodes will only
impose pressure similar to a subsonic exit boundary. Clicking Import reference conditions button
will copy all values from the Conditions panel.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 75
FENSAP - Flow Solution

In the case of supersonic flow, all flow variables are imposed at the inflow nodes, and they are all
set free on the outflow nodes.

Note:

It is possible to have secondary subsonic inlets in supersonic flows (engine turbine ex-
hausts before flow expansion) and supersonic inlets in subsonic flows (piccolo tube holes
simulated as Mach = 1 inlets). The user should make sure that in the domain there are
boundaries where pressure is set one way or another.

[Link]. Stagnation
The stagnation inlet boundary is used to specify total pressure and temperature, along with the
velocity direction. This boundary is suitable when the total conditions are known and the velocity
is not available. The Import of reference conditions feature is not available for this subtype, therefore
the button is disabled.

The current implementation of the stagnation inlet boundary condition is marginally stable and
requires significantly lower CFL numbers. Engine inlet subtypes are recommended instead when
the total pressure and temperature plus either the Mach number or the mass flow rate is known.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
76 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

[Link]. Mass Flow

The mass flow inlet allows the specification of a mass flow rate with a given direction. Keep in mind
that the area considered for the mass flow is the actual area of the boundary inlet as it appears in
the grid, and not the full annular area, in case of rotationally periodic grids, or the full cross-section,
in the case of symmetric grids. The static temperature also must be specified in a mass flow inlet.

The angles alpha and beta set the flow direction at the inlet. The icon can be clicked to visualize
the flow direction that will be imposed.

The mass flow inlet is a subsonic boundary condition, and the pressure is set free like so. Therefore,
in the domain, there must be an outlet boundary where the pressure is specified. You should pay
attention to the value of the mass flow rate not to exceed sonic conditions at this boundary.

[Link]. Riemann
This is a non-reflective boundary condition based on 1D Riemann characteristics, and it is meant
for far fields that are placed away from the solid. All five flow variables are provided, and they can
float during the solution process.

The purpose of this boundary condition is to provide better convergence for transonic flows and
to allow some variation in the inflow velocity components when they are not known exactly. Use
this inlet type if the far-field boundary condition has trouble converging or produces noise in the

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 77
FENSAP - Flow Solution

solution. Riemann boundary condition works better for high speed flows and may not converge as
well for very low speed flows.

[Link]. Engine Inlet – Mass Flow Rate

This is a variation of the stagnation inlet boundary condition that makes use of the 1D-Riemann
formulation, and it can accept total temperature and total pressure with a ball-park mass flow rate.
The alpha and beta angles are used to set the flow direction. All values can slightly float to adapt
to the conditions that establish downstream of the inlet.

The engine inlet – mass flow boundary condition is best suited for turbomachine inflow boundaries,
hot air sources like the inlets of ducts and piccolo tubes, etc. It converges significantly better
compared to the stagnation inlet boundary condition.

[Link]. Engine Inlet – Mach Number

This is a variation of the Engine inlet – Mass flow rate condition, where instead of the mass flow
rate the Mach number is specified.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
78 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

[Link]. From Restart

When an inlet boundary is set as From restart, it is treated as a supersonic or far-field boundary
condition with the nodal values of all flow variables being assigned directly form the restart flow
solution that was used to initialize the calculations. This is desirable in many occasions when the
boundary conditions are not readily available or non-uniform and difficult to formulate.

4.3.2. Walls – 2000-BCs

Wall boundary indices range from 2,000 to 2,999. Wall indices ranging from 20 to 29 are still supported
for backward compatibility, but are converted to the four-digit format. The surface type can be set
to Slip for an inviscid flow (Euler equations), or to No-slip for a viscous flow (Navier-Stokes equations).

[Link]. No-Slip
No-slip walls impose zero velocity on all nodes of the wall, unless the wall is rotating

No-slip walls in rotating frames get zero velocity relative to the frame, meaning they rotate with
the frame. Turbomachine rotors, hubs, helicopter blades are examples. For static walls in rotational
frames of reference like shrouds of turbomachinery rows, the Counter-rotating condition should
be selected. It is possible to use slip walls in rotating frame, then the velocity on the surface will
be tangent.

The thermal conditions on a no-slip wall are either temperature or heat flux specifications. For
adiabatic walls, the heat flux should be set to 0.

Note:

When the no-slip walls and the inlet intersect for internal flows, the nodes at the inter-
section will experience a large velocity gradient and therefore the results at these points
may be noisy. To mitigate this noise, set the inlet type to Mass flow. This is a weak-form
boundary type and permits a boundary layer velocity profile to form naturally.

[Link]. Slip
Slip walls are used in inviscid flows in general, however there are times when they can be of use
for viscous flows as well. In case of internal flow simulations where the inlet and exit boundaries
might be too close to the region of interest, you should extend the inlet and exit passages via slip
walls to prevent large flow variations and to provide uniform boundary conditions. The slip walls

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 79
FENSAP - Flow Solution

will not contribute to the boundary layer formation and the domain extensions will help obtain a
smooth transition between the local and the boundary conditions.

Slip walls are not considered in the wall distance and y+ calculations in order not to interfere with
the turbulence production/destruction terms of turbulence models.

[Link]. Sand-Grain Roughness Distribution on a Wall

The Sand-grain Roughness – BC type option is set in the Model → Roughness panel, as outlined
in outlined in Variable Roughness from the Boundary Conditions (p. 62), an additional box for the
specification of the sand-grain roughness height on each wall surface will appear.

[Link]. Rotating Walls (Axisymmetric)

Rotating axisymmetric surfaces such as propeller spinners and engine nose cones can be simulated
in steady-state computations by applying a tangential velocity at the grid nodes of the rotating
surface. Given the rate of rotation, the components of the tangential velocity are automatically
computed at each node of the surface according to its normal distance from the axis of rotation.
This is useful if other non-rotating components are present, such as the engine nacelle, or even a
complete aircraft, in which case the relative frame of reference could not be used.

Note:

The rotating spinner must be a surface of revolution. The orientation of the axis of
rotation of the spinner can be arbitrary, and it will be automatically detected by
FENSAP-ICE.

To enable rotation for a (wall) surface, set Rotation to Enabled in the boundary conditions panel
of the selected surface and specify the rotation rate in rpm. Click the Apply button.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
80 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

The axis of rotation of the selected surface is detected automatically and it is displayed in the 3D
viewer panel for verification. The direction of rotation follows the right-hand rule convention. To
reverse the direction of rotation, add a minus (-) sign in front of the magnitude of the rotation rate
and click the Apply button. This boundary condition can be applied to any number of spinners
with any arbitrary orientation, even if the incoming flow is not parallel to their rotation axes.

Figure 4.1: Spinner Axis of Rotation

Figure 4.2: Surface Velocity Vectors

4.3.3. Exits and Outlets – 3000-BCs

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 81
FENSAP - Flow Solution

Outlet boundary indices range from 3,000 to 3,999. The indices 30 to 39 are supported for backward
compatibility. There are four subtypes of outlet boundaries:

[Link]. Subsonic
The subsonic outlet boundary condition specifies the pressure on the boundary nodes. In subsonic
flows, these boundaries are the ones that set the final pressure for the whole domain since the
only unchanging pressure values are found on subsonic outlets. By default the pressure is set as
101,325 Pa, and it is possible to set it to the reference pressure specified on the Conditions panel
by clicking Import reference conditions.

Normally the outlet boundary condition applies the pressure as a Dirichlet boundary condition. By
turning on the Weak form option, the pressure can be applied as a contour integral instead. This
permits the pressure values to locally float and partially adjust to the pressure variations reaching
the outlets (wake of a rotor for example).

[Link].1. Radial Equilibrium

For subsonic exits with swirling flow, the radial equilibrium option is available to provide the
necessary force balance between pressure and centrifugal forces that the fluid is experiencing.
The outlet should be circular and flat, but can be oriented arbitrarily. The pressure set on the
boundary can be specified at the largest or the smallest radius, depending on the case, using the
Rad-eq. reference menu. Usually for turbomachinery exit boundaries it is convenient to set the
hub as the reference pressure location. However, for external flows the perimeter of the exit
boundary should be the reference point since this is where the far-field boundary with the same
pressure would intersect.

The radial equilibrium formulation allows a piece-wise continuous implementation of the pressure
gradient, helpful for cases where the angular velocity is non-uniform along the radius, especially
in the case of external flows. The Rad-eq. bands setting allows you to set the number of bands

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
82 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

to specify the piece-wise continuous distribution. Setting this to 1 means a standard linear distri-
bution of dP/dr.

[Link]. Supersonic
When the outlet is set as Supersonic, there is nothing to set and the pressure field at this location
is free. The entire outlet boundary must be supersonic otherwise calculations can diverge.

[Link]. Mass Flow

The Mass flow outlet boundary condition takes a mass flow rate as the input for the entire
boundary. This is a variation of the subsonic boundary where the uniform pressure is automatically
adjusted until the desired mass flow rate is reached. The direction of the flow is dictated by upstream
conditions as in the subsonic outlet case.

You should activate the Use variable relaxation option in the Solver panel, which ramps the CFL
number from 1 to a target value using a specified number of iterations, when using this outlet

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 83
FENSAP - Flow Solution

boundary condition. This, in general, allows the pressure to settle more smoothly on the outlet
boundary condition.

If the mass flow rate specified is too high and choking conditions occur at the outlet, the target
mass flow rate will be automatically lowered to keep the flow at Mach 1.

Note:

Mass flow inlet and Mass flow exit boundary conditions cannot be used simultaneously
if they are the only inlet and exit boundaries in the domain. This would make the pressure
completely free and result in a non-unique solution. Somewhere in the domain, there
must be a regular exit boundary condition with a specified pressure, or the inlet must
be of Riemann or Engine Inlet type which will impose an external pressure to influence
the free inlet pressure.

[Link]. From Restart

When From restart is selected for an outlet boundary condition, the pressure found on the restart
solution is kept on the outlet nodes in Dirichlet form. This is useful when there is a restart file
available with a non-uniform pressure distribution on the boundary (i.e. outlets of turbomachinery
rows).

4.3.4. Symmetry – 4000-BCs

The Symmetry boundary condition can be used to reduce the mesh and domain size when the flow
is perfectly symmetric across one or more planes. The boundary condition is applied through the use
of pseudo elements also known as ghost cells that are exact copies of grid elements from the inner
side of the symmetry plane, mirrored across the boundary. These elements serve to mimic the flow
on the other side of the symmetry plane. They are included in the assembly of the finite element in-
tegrals on the symmetry planes, using vectors that are mirrored copies of the internal nodes. The
new nodes on the pseudo elements are not included as degrees of freedom in the solution process,
and they do not add to the solution time.

Traditionally 4000 – 4099 boundary conditions are of type General, 4100-4199 of type X-Symmetry,
4200-4299 of type Y-Symmetry, and 4300-4399 of type Z-symmetry, but with the introduction of
the pseudo element technique all symmetry boundary conditions are treated in the same way. It is

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
84 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

still important that individual symmetry boundary conditions are planar, and symmetry boundary
conditions with different orientations should be numbered separately.

Note:

FENSAP will not accept a curved symmetry boundary.

4.3.5. Periodic – 5000-BCs

FENSAP-ICE supports both rotational and translational periodicity. The 5000 boundary family is desig-
nated for periodic boundaries, although this is only for CAD and flow visualization purposes. There
are no boundary conditions imposed on periodic boundaries, instead, the implementation is similar
to the symmetry boundary condition where grid elements from one (secondary) side are copied with
translation or rotation to the other side (primary). The grid nodes on the primary side get full volume
integrals for the FEM assembly as if a copy of the grid was there, without knowing about the periodicity
condition. This ensures that the solution process is perfectly periodic.

Note:

At the moment FENSAP-ICE requires that the periodic boundaries on either side are con-
formal, i.e. node to node matching.

4.3.6. Internal Surfaces – 6000-BCs

The 6000 boundary condition family is reserved for internal surfaces, which can be used as actuator
disk for momentum sources, screens for momentum and particle sinks, heater pads in the case of
solid conduction, or simply custom user set boundaries for flow visualization and quantity integration
purposes.

[Link]. Actuator Disks

The actuator disk model is a source term introduced directly in the surface integrals of the element
faces lying on the disk to simulate rotor effects. To activate this model, select Actuator disk in the
Type box.

The disk loading data is organized in (r, ) coordinates in a series of pressure loads and swirl velocity
distributions as a function of the radial coordinate ri (1 ≤ i ≤ n) for an arbitrary number of constant
angular positions θj (1 ≤ j ≤ m). The same number of radial coordinates ri must be specified for

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 85
FENSAP - Flow Solution

each angular position θj, however the number (n) of radial coordinates ri and number (m) of angular
positions θj may vary from disk to disk when multiple disks are present.

Note:

The total temperature source for the energy equation is calculated internally based on
the total pressure sources.

The boundary conditions can be imported from a user-supplied input file. To do so, click the disk
icon and select the actuator disk boundary condition file. The format of this file is presented in The
Actuator Disk File (p. 403).

The actuator disk data can also be entered manually. A schematic illustration of the actuator disk
is shown below:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
86 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

The surface of the actuator disk may not necessarily be flat. In this case the loading data is specified
on the pseudo-disk resulting from the projection of the actual disk on a flat surface perpendicular
to the axis of rotation. FENSAP will take care of re-projecting the data back on the non-planar disk.

The vector represents the fluid velocity as it passes through the disk.

Note:

The velocity through the disk is continuous, however it may not necessarily be perpen-
dicular to the disk surface. The thrust will be applied in the specified thrust direction
which does not have to be perpendicular to the disk, and the incoming flow may be at
an angle to the disk.

The vector denotes the unit vector perpendicular to the disk surface in the general direction of
the thrust generated by the disk. The vector is the rotation axis which is used with the angular
velocity data provided in the disk file to calculate local tangential swirl velocity components. The
vector denotes the radial position on the disk, whose angular position with respect to the 12
o'clock mark is . Finally, the vector is the swirl velocity of the wake at that point.

Enter the geometry of the actuator disk:

Table 4.1: Actuator Disk Geometry

Origin The (X,Y,Z)-coordinates of the center of the disk

12 o’clock The (X,Y,Z)-coordinates of the 12 o'clock mark on
the actuator disk's outer boundary
Thrust vector The components of the thrust vector
Angular velocity The components of the angular velocity vector,
in rpm

Click the display icon to display the center of the actuator disk, the thrust vector and the 12
o’clock mark in the graphical window. Click again to remove them from the graphical window.

Note:

The rotational velocity vector Ω follows the right-hand rule. The swirl velocity is not im-
posed as a Dirichlet boundary condition.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 87
FENSAP - Flow Solution

You should also set up the angular and radial distributions of disk loading and swirl velocity. Add
a new radial distribution by clicking +. The angular location should be given in degrees with respect
to the 12 o'clock mark (coordinate in the direction of rotation; the orientation of the radial lines
follows the right-hand rule with respect to the direction of the rotational velocity). Use the - button
to delete a selected radial distribution.

Enter the distribution of radial positions (Radius (m)), disk loading (Load (Pa)) and swirl velocities
(Ang. Velocity (rad/s)) along this angular location. See The Actuator Disk File (p. 403) for the format
of the actuator disk input file.

Important:

The swirl velocity is not necessarily equal to the velocity of rotation of the actual rotor.
The wake of a rotor rotates slower than the rotor itself, as induced by the drag at each
blade section. The disk loading is the local force per unit area, and has the units of
pressure (Pa).

The angular positions to for data specification must start at the 0˚ line and there should
be at least four sectors defined in the disk data file. If the distribution is axisymmetric
simply copy the same data to for the other sectors.

Data should not be provided at the 360˚ line, since it is identical to the 0˚ line.

User must ensure that the disk loading, integrated over the surface of the actuator disk,
produces the desired thrust. Similarly, the total enthalpy jump ( ) integrated
over the disk surface must yield the work done on the fluid.

Use the two arrows to expand or restrict the size of the table.

[Link]. Screen Models

Effects of screens on air and droplet flows can be simulated using face based sink terms on mo-
mentum and droplet/crystal contents across the boundary. A screen boundary introduces pressure
drop or liquid water content drop due to the blockage created by the wire mesh. The screen is
modeled by a sink term in the surface integrals of the momentum equations FENSAP, or by an LWC
sink term in the continuity equation of DROP3D. To activate this model, the screen must be repres-
ented as an internal surface with a boundary index in the BC_6000 family in the grid file, similar
to the convention shown in Actuator Disks (p. 85). Unlike the circular actuator disk, the screen can
be an internal surface of any shape. Select Screen in the Type box of the screen surface.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
88 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

The generic screen geometry is described by a non-dimensional porosity parameter defined as:

where:

- Wire diameter

- Wire spacing

Presently, only screens with square mesh patterns can be simulated, however both planar and
curved screens are supported.

Click the display icon:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 89
FENSAP - Flow Solution

to check the input data and display the screen in the graphical window. Click the icon again to
hide this information from the graphical window.

A selection of pressure drop correlations is available in the Screen model section. They are described
in the following sections.

[Link].1. Pressure Drop from Brundrett

The experimental correlation from Brundrett expresses the non-dimensional pressure drop across
a screen as a function of the wire Reynolds number as:

where:

The incoming flow direction is assumed to be normal to the screen. To select this correlation,
choose Brundrett in the Model box.

[Link].2. Pressure Drop from Idelchik, Diagram 8-1

The second model follows Diagram 8-1 in Idelchik for a thin-walled grid of perforated sheets or
strips with sharp-edged orifices: Idelchik, I.E., Handbook of Hydraulic Resistance, Second Edition, p.
402.

To select this correlation, choose Idelchik – sharp-edged orifices in the Model box.

[Link].3. Pressure Drop from Idelchik, Equation 8-3

This model is based on Equation 8-3 in Idelchik for screens made of circular metal wires, with
correction factors based on wire diameter:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
90 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

where is obtained by interpolation shown below:

To select this correlation, choose Idelchik – circular metal wires in the Model box.

Note:

Due to the simplicity of Idelchik models, they are numerically more stable and robust.
Idelchik models are quite standard in the industry for modeling hydraulic resistance
and they are the recommended options for modeling screen pressure drop within
FENSAP. For more information on these models, consult Handbook of Hydraulic Resist-
ance, 3rd edition, by Idelchik.

[Link]. Disabled (Transparent) Boundary Conditions

If the boundary condition type is set to Disabled (instead of Screen or Actuator disk), the surface
will be ignored in the computation.

4.3.7. Non-Conformal Interfaces – 7000-BCs

The 7000 boundary condition family is reserved for non-conformal interfaces in a domain. The interface
pairing is detected as odd/even consecutive numbers, that is, 7001-7002 is a pair, 7005-7006 is a pair,
and so on. ANSYS file converters from ICEM CFD, CFX, or Fluent will be able to automatically assign
these numbers, however, if the grid is created by a third-party method then you must pay attention
to establish this odd/even pairing of interface boundaries. There are no settings to provide in the
case of non-conformal interfaces.

The grid density on both sides of a non-conformal interface is recommended to be similar, especially
if the edges of the interfaces are curved. Otherwise, the edge nodes of the finer side may physically

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 91
FENSAP - Flow Solution

reside outside of the elements of the coarser side and solution quality and convergence may be
compromised as a result of poor interpolation between these two interfaces.

Ice displacement and mesh deformation do not support non-conformal interfaces, and nodes on
these boundaries are static. Placing these interfaces close to icing walls is not recommended.

4.3.8. Importing Boundary Conditions from Reference Conditions

To ease data entry, the boundary conditions can be set by importing the reference conditions. For
this, click Import reference conditions.

Note:

The velocity components will not be set properly when starting a calculation from a previous
solution (restart). In this case, the values should be entered manually.

4.3.9. Boundary Conditions Varying in Space

The f(x) button indicates that the variable distribution is imposed through a function of the spatial
coordinates.

For example, to impose a Velocity-X profile, click the f(x) button to open the formula window.

Enter a spatial distribution by using the Insert button:

using the variables, functions and operators provided:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
92 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

The equation can be a function of any combination of spatial coordinates, however it can only be
displayed as 2D graphs in either X, Y or Z, selected with the buttons:

The other spatial coordinates are then set to zero to ease visualization.

The following equation

can be entered as follows

The Boolean operator (X<=30) assumes a value of either 1 or 0 depending on whether the condition
is true or false. The function f(x) is displayed in the graphical window for visual validation. Click the
icon:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 93
FENSAP - Flow Solution

to refresh the display

[Link]. Inlet Profiles for Turbulence

Any profile of the turbulent variables can be imposed at the inlet. To do so, select Impose turbulence
profile, click and enter a profile for:

Turbulent viscosity (if using the Spalart-Allmaras one-equation model)

and (if using the - two-equation models)

and (if using - models)

Note:

When this option is not activated, the uniform, constant turbulent variables values are
automatically imposed on inlets from the input Eddy/laminar viscosity ratio set in the
Model panel.

4.4. Domains
This section is only activated if more than one domain is present in the grid file (See FENSAP-ICE File
Formats (p. 393) for the FENSAP grid file format). A domain is composed of two or more volume elements
flagged with the same material ID number.

Note:

A zero (0) domain index should be assigned to all fixed domains.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
94 of ANSYS, Inc. and its subsidiaries and affiliates.
 Domains

4.4.1. Unsteady Rotor-Fuselage Interaction

Domain indices can be used to simulate rotor-fuselage interactions by separating the grid into regions
that are either fixed in space, such as the fuselage, or rotating with the rotors. The calculation is always
performed in the absolute frame of reference system (fixed grid), in which the rotor blades are rotating
in time.

In the Rotor (unsteady) section, each domain can be configured either as Rotating or Fixed. The
Rotating option should be applied only to domains with the suitable topology with a gap and inter-
faces boundary conditions (see Important (p. 96)). This will only affect the state of the initial solution
vectors. When the domain is selected, the bounding box of the domain is shown in the 3D panel. For
Rotating domains, the Rotation speed (in rpm), Rotation axis and Rotation center must be defined.

The transfer of flow information between rotating and fixed domains could generally be performed
using either sliding boundaries or Chimera grids, but these approaches are not fully conservative. In
FENSAP-ICE, a different approach has been adopted in which the fixed and rotating domains are
separated in space by a small gap (similar to two concentric cylinders, one inside the other). At each
time step the rotor grid is rotated by the appropriate angular displacement and the gap is remeshed,

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 95
FENSAP - Flow Solution

or stitched with tetrahedral elements. No new nodes are created during the stitching process, therefore
this method ensures flow conservation without any special treatment.

Important:

For the stitching algorithm to work properly, the inner and outer surface of each gap must
be identified in the grid file with a boundary condition index ranging from 7,000 to 7,999.
All gap surfaces must have unique boundary condition indices.

To ensure optimal performance of the stitching algorithm, the gap between the two surfaces
should be of the same size as the element faces on the two surfaces and the mesh transition
between the two domains should be as smooth as possible.

Rotor/fuselage interactions can only be computed with the unsteady flow solver, as shown
later in the Solver section. Since many segregated equations are involved, time accuracy
is ensured by the Newton sub-iterations at each time step.

Click the display icon to check the input data and display the material properties:

Click again to remove the graphical display.

[Link]. Initial Rotor Acceleration

In the Solver section, select Gradually accelerate to full speed to progressively accelerate the
rotor to full speed over the first few time steps.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
96 of ANSYS, Inc. and its subsidiaries and affiliates.
 Domains

This is useful when starting the calculation from an initial uniform solution to ensure good stability
and convergence of the Newton sub-iteration procedure.

4.4.2. Multi-Domain Initialization

Some internal flow calculations may require different initial conditions than the reference parameters
to provide a better starting point for the solution algorithm. For example, the piccolo tube chambers
will benefit from starting with a higher static pressure than the value set at the exit. Inside of the
piccolo tubes themselves it is preferable to set total pressure and temperatures initial conditions that
match their inlet boundary conditions to help jump-start the supersonic jets. Cavities inside rotating
components, such as engine nose cones, experience a swirling flow driven by wall shear. To accelerate
convergence, the airflow in these domains can be initialized with a rotational velocity.

To enable multi-domain initialization, the grid file must contain more than one domain ID for the
Domains panel to become visible. See The Domains Table (p. 399) for the format of the domain IDs
in the grid file.

In the in the Domain Parameters in the Domains panel, Initialization can be set to Default, Rotating
or Custom. The Default option uses the reference static temperature, pressure and the velocity
components set in the initial conditions section of the conditions panel.

The Rotating domain initialization sets the axial velocity to zero and the angular velocity to that of
the rotational frame of reference. In other words, in the rotating frame of reference the relative velo-
cities are initialized as zero (rotating with the domain).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 97
FENSAP - Flow Solution

The Custom option permits the specification of an alternate set of flow conditions for that domain:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
98 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solver Parameters

4.5. Solver Parameters

Default values are provided for the time-marching procedure, the artificial viscosity and the matrix
solver that should be able to handle most cases. Some parameters can be changed if more accuracy is
desired or stability problems are encountered during the solution process.

4.5.1. Steady-State Flows

Several time-marching options are provided to control execution. To improve the performance of the
iterative matrix solver in for steady-state solutions, a local temporal operator can be added to the
Jacobian matrix of the Navier-Stokes equations.

These terms, proportional to , improve the diagonal dominance of the Jacobian matrix and
therefore the convergence of the iterative matrix solver.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 99
FENSAP - Flow Solution

However, the convergence rate of Newton’s method will deteriorate for large . The flow solution
is advanced in time, with a local Δt that varies according to the size of the element, until steady-state
is reached. If the Steady option is selected, only one Newton iteration is required to linearize the
system at each time step.

Select the Steady option and enter the CFL number (from 1 to 1,000, default 50) and the maximum
number of time steps. FENSAP stops the calculation if either the Maximum number of time steps
or the convergence residual level has been reached.

Tip:

Reduce the CFL number if convergence problems are encountered. If this does not help,
the quality of the mesh and the correctness of the boundary conditions should be verified.
Note that inconsistent settings in inlet and exit conditions yielding inappropriate inlet and
exit mass flow rates will cause the computations to diverge. When setting up internal flows,
make sure that the boundary conditions are properly defined.

[Link]. Variable Relaxation

Convergence problems may be encountered when starting from a uniform initial solution with
some complex geometries. In many cases the solution instability can be traced to grid problems
or incorrect boundary conditions. In some cases, however, the solution may begin to diverge after
a few iterations due to numerical instabilities. In this case, to improve robustness, click the Use
variable relaxation box.

This option gives access to a mechanism to linearly increase the CFL number from CFL=1 to its
full value within a set number of time steps. Define the maximum number of time steps in which
relaxation will be applied to the CFL number and the relaxation factor on the flow variables.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
100 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solver Parameters

Since the relaxation factor is permanent and affects all flow variables, it can have a strong effect
on the convergence rate and therefore it should be reduced from the default value (1) only in ex-
treme cases. Values greater than 1 would amplify instabilities and therefore are not permitted.

Tip:

Variable relaxation can stabilize the solution very effectively at the beginning of the
computation and permits larger CFL values and faster convergence once the flow becomes
sufficiently well-established.

In case of a restart with the same conditions, the relaxation should be turned off so that
CFL does not start from 1 again. However, if restarting from a solution with different
boundary conditions, CFL relaxation may still be needed.

4.5.2. Unsteady Flows

Two different time marching procedures are available for the simulation of time-accurate unsteady
flows.

[Link]. Constant Time Stepping

Select Unsteady - Constant time step to solve for an unsteady flow using a constant time step.
Set the time step and the total solution time, both in seconds. FENSAP advances in time using a
second-order Gear scheme. The non-linear governing equations are linearized by performing, at
each time step, a given number of Newton linearization loops (default 3). FENSAP then moves to
the next time step if either the number of Newton iteration per time step is reached or the residual
convergence level is reached. FENSAP stops the calculation at the end of the total time.

Note:

The convergence of the matrix solver (GMRES) is closely linked to the time step,
since the time derivative term affects the diagonal dominance of the linear matrix
system. Reduce the time step if the GMRES solver is not converging more than one
order of magnitude.

This strategy is not suggested for viscous turbulent flows where the small element size close to the
walls limits the time step to a very small value.

[Link]. Dual-Time Stepping

Select Unsteady - Dual time stepping to solve for an unsteady flow using a dual time step approach.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 101
FENSAP - Flow Solution

Set the physical time step and the total solution time, both in seconds. FENSAP advances in phys-
ical time using a second-order Gear scheme. At each physical time step, the non-linear governing
equations are converged in pseudo-time using a local time stepping technique with a constant
CFL number (default 50, same as steady-state strategy). This increases the robustness of convergence
even if larger physical time steps are selected. A sufficient number of pseudo-time iterations (default
= 4) are required to ensure convergence at each physical time step. The calculation will stop at the
end of the total physical time.

4.5.3. Artificial Dissipation

The discrete convective terms of the Navier-Stokes equations may cause numerical instability. The use
of equal interpolation functions for the velocity and the pressure also leads to oscillations of the
solution. To remedy this problem, artificial viscosity is added to the equations in order to stabilize
them.

[Link]. The Streamline Upwind (SU) Scheme

In order to eliminate the drawbacks caused by scalar dissipation, a streamline upwind technique
has been introduced that concentrates the artificial dissipation mainly along the streamline direction.

The balancing operator, again in the form of a diffusive term, acts exclusively in the streamline
direction as an anisotropic artificial diffusivity. The artificial diffusivity therefore assumes a tensorial
character and could be expressed as follows:

where

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
102 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solver Parameters

This artificial diffusivity is added to the right-hand-side of the continuity, momentum and energy
equations. Select this artificial viscosity scheme with the Streamline upwind option.

Note:

The amount of Cross-wind dissipation required is largely influenced by the grid quality.
A value of 10-7 is set as default, the recommended value for most grids and applications.
Larger values result in smoother convergence of the residual while lower values improve
accuracy of shear stress and heat fluxes.

Excessive artificial viscosity will thicken boundary layers and produce inaccurate shear
stresses and heat fluxes.

The parameter Order varies from 0% (first-order scheme in the upwind direction) to
100% (fully second-order scheme in the upwind direction). A value of 100% is recommen-
ded.

[Link]. Streamline Upwind for Shocks

This is a modified version of the Streamline-Upwind scheme with an automatic switch between 1st
and 2nd order terms that is triggered in the vicinity of the shocks, to prevent spurious oscillations.
In transonic cases where the shock stands on the wall boundary, such oscillations can contaminate
the heat flux and shear stress distributions before and after the shock. Currently this feature is
provided as a beta option pending comprehensive testing. To access it, the Show advanced / beta
solver options must be checked in the main project window Settings → Preferences → General
tab.

[Link]. Central Schemes

Other artificial viscosity schemes are proposed in FENSAP.

For all of them, the contribution to the right-hand-side of the governing equations is as follows:

The option 1st order corresponds to proportional to AV coefficient and the local cell length,
and set to 0. This scheme is quite viscous and should be used only if stability problems are en-
countered when the initial solution is far from the expected final one.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 103
FENSAP - Flow Solution

The option 2nd order for shocks corresponds to and proportional to AV coefficient and the
second derivative of pressure. This scheme is less viscous than first order and should be used only
if the solution is close to the expected final one and when shocks are present in the flow solution.

The option 2nd order corresponds to and made proportional to AV coefficient and the local
cell length. This scheme is less viscous and should be used only if the solution is close to the expec-
ted final one.

Tip:

1st order with an artificial viscosity of 10-2 is a good starting point as it will add enough
artificial viscosity to enhance residual convergence, even if the calculation is started from
an inappropriate initial guess. However, the 2nd order option with low artificial viscosity
coefficients (10-2 and below), or preferably the Streamline-Upwind (SU) scheme, should
be used in the final solution to ensure a flow solution that closely satisfies the conserva-
tion of mass, momentum and energy.

Excessive artificial viscosity will thicken boundary layers, smear shock waves, and result
in incorrect shock positions. A sufficiently small coefficient should be used that crisply
captures the solution while still suppressing oscillations. You must be aware that restarting
the computations from a uniform flow with the lowest artificial viscosity coefficient may
not work, since the Newton algorithm converges robustly only when the initial guess is
reasonably close to the final solution.

4.5.4. Advanced Solver Settings

Double-click Advanced solver settings to open the advanced menu.

[Link]. Residual Convergence

FENSAP execution stops when the norm of the residuals reaches this convergence level (default =
1e-10).

[Link]. Dissipation Scaling

This is an expert user option that is only available if Show advanced / beta solver options is ac-
tivated in the Settings → Preferences → General tab. They are maintained for backward compat-
ibility and for legacy reasons. FENSAP flow solver verification and validation is done with these
values set at default level (default = 1). They should be lowered if central artificial dissipation
schemes are used in order to reach the same level of accuracy as the Streamline-Upwind scheme.

The artificial viscosity coefficients are set for the continuity equation. In the momentum equations,
the amount of artificial viscosity is taken as the Dissipation scaling → Momentum times the vis-
cosity in the continuity equation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
104 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solver Parameters

The defaults values of these parameters are set to unity. In this case, the artificial viscosity coefficients
are identical in the momentum and continuity equations.

In the energy equation, the amount of artificial viscosity is taken as the Dissipation scaling → Energy
times the viscosity in the continuity equation. For most applications, this parameter is set to unity.
In this case, the artificial viscosity coefficients are identical in the energy and continuity equations.

In the turbulence model equations, the amount of artificial viscosity is Dissipation scaling → Tur-
bulence times the viscosity in the continuity equation. For most applications, this parameter is set
to unity. In this case, the artificial viscosity coefficients are identical in the turbulence and continuity
equations.

Note:

The default values of 1 should produce stable and accurate results in conjunction with
a cross-wind artificial viscosity coefficient of 10-7 for most applications, given that
everything else is configured properly (grid with a decent quality, appropriately set
boundary and initial conditions, etc.).

[Link]. Solver Settings

This section is intended for expert users that want to optimize the GMRES convergence of their
calculation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 105
FENSAP - Flow Solution

The linear system is solved at each Newton iteration using an iterative GMRES solver. This approach
searches for solutions along each Krylov space, and iterates until either the number of iterations
or the convergence criterion is satisfied.

Ideally, the GMRES solver should converge at least by an order of magnitude at each Newton iter-
ation for the overall system of equations to converge as well. The GMRES convergence is shown in
the convergence window. If a particular system of equations is not converging enough (say below
0.1), one can then try to increase the number of iterations, at the cost of extra solution time. Increas-
ing the Krylov space may also help the convergence of GMRES, but this option is not recommended
as it increases drastically computer memory requirement.

The convergence criteria are set at 1e-24 in the current release, which means that all the iterations
will be done. The reason for this is that in certain flow simulations where the grid is not fine enough
in a location that contains strong flow features that are difficult to resolve, the rest of the domain
can make the average residual fall below the specified criteria and stop the calculations, whereas
such problematic regions require more iterations to converge. In such cases the computations may
appear to be converging for a while before the truncation error of a few unconverged nodes can
finally become sufficiently amplified that the computations begin to diverge globally. Only experi-
enced users should modify these values to reduce the number of iterations in the linear system
and accelerate their calculations.

Energy sub-iterations setting controls the number of times the energy equation is solved within a
time step. Doing two energy iterations can help certain problematic cases to converge better espe-
cially in the initial transient phase of the solution. In general, two iterations of energy reduce the
overall number of iterations by 25%, with an additional calculation cost of 15%. Doing more than
two sub-iterations has no significant advantage.

Table 4.2: Default Values

Krylov space 20
Number of iterations for momentum 10
Number of iterations for turbulence 8 (only for turbulent flows)
Number of iterations for energy 8 (not shown with the Constant enthalpy option)

The convergence criteria are set at 1e-24 in the current release, which means that all the iterations
will be done. The reason for this is that in certain flow simulations where the grid is not fine enough
in a location that contains strong flow features that are difficult to resolve, the rest of the domain
can make the average residual fall below the specified criteria and stop the calculations, whereas
such problematic regions require more iterations to converge. In such cases the computations may
appear to be converging for a while before the truncation error of a few unconverged nodes can
finally become sufficiently amplified that the computations begin to diverge globally. Only experi-
enced users should modify these values to reduce the number of iterations in the linear system
and accelerate their calculations.

4.6. Output
Several options are available to customize FENSAP's output to suit your particular needs.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
106 of ANSYS, Inc. and its subsidiaries and affiliates.
 Output

4.6.1. Log Files

The output log level is configurable in the Out page.

Table 4.3: Pull Down Menu Options

Minimal Reduces log size to a minimum, less printout at

each iteration.
Default Regular log output.
Detailed Includes extra information, such as timing for each
subroutine.

4.6.2. Solution File

The FENSAP solution is saved in FENSAP format (See FENSAP-ICE File Formats (p. 393) for format details).

The solution can be saved either at the end of the calculation (Final solution) or at fixed intervals
during the iterative solution process. When saving the output file every N iterations, the solution
can be either overwritten (Overwrite) or saved in separate files numbered with the iteration/time
step number (Do not overwrite).

Tip:

If turbulence is enabled, computing the y+ and u+ data on large grids could be costly. If
these variables are not important, their computation can be disabled by clearing the box:
Write Y+ to solution.

When solving for unsteady flows, the solution can be saved at fixed intervals in time to
enable animations.

4.6.3. Extended Icing Data (EID)

The Extended Icing Data (EID) is a feature that improves the accuracy of icing calculations for high
Mach number flows. It extracts additional flow features for use with the Glaze Advanced icing
model of ICE3D to enable calculation of uncommon ice shapes like beak-ice, which are usually char-
acterized by well-defined horns growing at a short distance from the stagnation point on a mostly
uncontaminated surface. EID is required to correctly simulate icing on rotating components like heli-

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 107
FENSAP - Flow Solution

copter and turbomachine rotors where the outboard sections of the blades are always in high speed
regime.

EID can be extracted from flow solutions provided by any flow solver, given that a restart solution
file can be converted and then used to start a FENSAP flow calculation. CFX and Fluent air flow
solutions can be used directly as restart files for the EID calculation, while FENSAP can move onto
EID extraction as soon as the flow calculation stops due to convergence or reaching the total number
of iterations.

An EID run requires that the source air flow solution is computed with all walls set as adiabatic walls.
In addition to calculating EID, heat transfer coefficients will also be extracted from this solution as a
post processing step to calculate the convective and evaporative heat fluxes in ICE3D’s energy
equation.

There are 2 modes of operation for EID:

1. Inline with FENSAP:

EID run is automatically executed right after the main FENSAP flow calculation. To use this option
with FENSAP, select Enabled in the Extended Icing Data box in the Out panel.

2. EID-Only with flow restart:

EID run is executed standalone using a restart adiabatic air flow solution obtained with
FENSAP/Fluent/CFX or third-party CFD solvers. To use EID in standalone mode, select the EID
option in the Physical model pull-down menu of the Model panel.

In both modes, a FENSAP solution file (i.e. soln) that contains the original flow solution fields in
addition to EID will be written. EID is not formatted for visualization in a post processing tool like
Viewmerical or CFD-Post, therefore, it is not available among the list of fields that can be shown.

Important:

The solution produced by the third-party CFD solver will be converted by FENSAP-ICE. It
is necessary to provide all the information requested regarding the reference freestream
conditions. These reference values must also be used in the ICE3D Conditions panel.

The same procedure regarding the initialization of the reference values must also be fol-
lowed when converting the solution and running ICE3D in batch mode.

EID makes use of laminar viscosity, laminar conductivity, and turbulent viscosity. These
fields have to be present in the supplied air solution file for EID to function properly. If
laminar conductivity is missing, it will be calculated from the local temperature using
Sutherland’s law.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
108 of ANSYS, Inc. and its subsidiaries and affiliates.
 Output

4.6.4. ALE Formulation

For moving boundaries, for example, mesh displacement due to ice accreting in time or body motion,
FENSAP uses the ALE (Arbitrary Lagrangian Eulerian) formulation.

There are two displacement methods, coupled and uncoupled. The coupled method solves for the
displacements in the x-, y-, and z-direction simultaneously, providing a better distribution of the effect
of surface displacement into the interior of the computational domain. This approach yields good
mesh orthogonality and element quality near the surface, however it is somewhat more computationally
expensive than the uncoupled solution. The default Coupled option is therefore recommended.

Mesh movement can be performed in two cases:

1. In the case of multishot ice accretion, the surface displacement due to ice accretion is obtained
as an output from ICE3D. The [Link] file from ICE3D should be assigned to FENSAP using
the Browse button. In this quasi-steady mode, the displacement velocity is not included in the
flow solution.

2. With aero-elasticity (unsteady flows with moving boundaries), the displacement velocity is computed
at each time step and the mesh is automatically displaced by FENSAP. In this unsteady mode, the
displacement velocity is included in the flow solution.

Important:

The 6000 and 7000 boundary condition families, which are actuator disks, screens, heater
pads, and interfaces are not allowed to deform due to mesh displacement from icing.
Therefore it is important to make sure these boundaries are not in contact with ice accreting
walls to begin with.

4.6.5. Lift, Drag and Moments

FENSAP computes the resultant force F acting on all solid surfaces of the grid. This force can be split
into lift and drag. If your grid contains symmetry planes that touch wall boundaries, the force com-
ponents in the symmetry directions will be removed from this resultant force before splitting it into
lift and drag components.

Note:

The lift calculation is not accurate for periodic grids.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 109
FENSAP - Flow Solution

The positive lift direction represents the up direction which will help determine the sign of the final
reported lift. The lift coefficient is computed as follows:

where the lift is equal to resultant force along the lift direction, and is the reference area.

The drag vector is the projection of the resultant force along the drag direction. The drag coeffi-
cient is computed as follows:

The moment is the summation over all wall faces of the local force times the normal distance
between its point of action and the moment center specified in Moment reference point -X, -Y and
-Z.

Important:

FENSAP writes extensive information on the lift and the drag and their coefficients. The
intermediate and final values appear in the log file, along with their breakdown by surface
index. Intermediate values of the lift and drag coefficients are also displayed in the conver-
gence graphs. You should pay special attention to these two quantities to ensure proper
convergence of the flow solver.

• Drag direction based on inlet BC: The drag direction is set in the same direction as
the velocity of the inlet boundary selected in the Drag BC window.

• Drag direction provided by user: The non-dimensional direction components are

provided by you in the Drag direction vector -X, -Y and -Z boxes.

• No lift and drag: The lift and drag are not computed by FENSAP.

Note:

The sign of the lift coefficient depends on the orientation of the body. You should specify
the approximate positive lift direction.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
110 of ANSYS, Inc. and its subsidiaries and affiliates.
 Output

Click the blue icon to display the drag vector in the graphical window. Click again to remove the
display.

4.6.6. Probe Point Interpolation

Probe points can be defined in the computational domain to monitor the flow solution at specific
locations during convergence.

To do so, click the Add button and enter the (X,Y,Z) coordinates of each probe point.

Click the blue icon to view the probes in the graphical window. Click again to remove the probes
from the graphical view.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 111
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
112 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 5: DROP3D - Droplet and Ice Crystal
Impingement
The following sections of this chapter are:
[Link] Physical Model
5.2. Supercooled Large Droplets (SLD)
5.3. Particle Conditions
5.4. DROP3D Boundary Conditions
5.5. Droplets Solver Parameters
5.6. Output
5.7. Particle Reinjection in External Flows
[Link] DROP3D Run Environment

This chapter describes the input parameters of DROP3D, the Eulerian droplet, ice crystal impingement
and vapor transport module of the FENSAP-ICE package. See Create a New Run (p. 19) on how to create
a new DROP3D run. The run name can be assigned in the New run name box at the bottom of the
solver selection window, or renamed after the run has been created.

In the following sections the particle type is usually denoted by droplet, but where appropriate it may
refer to ice crystals.

5.1. The Physical Model

Select the option Droplets in the Physical model pull down menu of the Model panel to access the
DROP3D configuration environment.

5.1.1. Assigning the Grid and Air Solution Files

DROP3D requires an air solution as input. Both the grid and solution files should be assigned using
the grid and solution icons in the run window. You can also set (or reset) them using the Input files
tab in the configuration window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 113
DROP3D - Droplet and Ice Crystal Impingement

The grid file is then read to detect the boundary conditions.

Note:

If the grid is replaced with a different one, it is imperative to review the parameters assigned
to the boundary conditions, described in DROP3D Boundary Conditions (p. 163).

5.1.2. The Particle Transport

The general Eulerian two-fluid model consists of the Euler or Navier-Stokes equations augmented by
the particle (droplets or crystals) continuity and momentum equations:

Where the variables and are mean field values of, respectively, the particle concentration and
velocity. The first term on the right-hand-side of the momentum equation represents the drag acting
on particles of mean diameter . It is proportional to the relative particle velocity, its drag coefficient
and the droplets Reynolds number:

And an inertial parameter:

The second term represents buoyancy and gravity forces, and is proportional to the local Froude
number:

These governing equations describe the same physical particle transport phenomena as current
Lagrangian codes. Only the mathematical form in which these equations are derived changes, using
Partial Differential Equations instead of Ordinary Differential Equations.

5.1.3. Particle Drag Correlations

Different particle types, and their related drag correlations, are supported by DROP3D.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
114 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

The Water - default drag coefficient is based on an empirical correlation for flow around spherical
droplets, or:

The range of validity of this drag coefficient is not limited by the , but it is generally observed
that water droplets start to deform at values above 250.

The second choice is based on Water - Stokes law for flow around an isolated sphere. It is valid for
very small number (<1).

The third choice is an extended version of the default law, referred to here as Water - extended
Reynolds, defined with w = as:

The fourth drag coefficient correlation, Snowflakes, applies to oblate spheroids and is useful for cal-
culating the collection efficiency of snowflakes:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 115
DROP3D - Droplet and Ice Crystal Impingement

With

5.1.4. Ice Crystal Drag Correlations

The second Particle type model, Ice crystals, applies to oblate spheroids and computes the collection
efficiency of ice crystals. The inertia parameter in this case is:

The common practice in evaluating the drag force is to assume that the particles are spherical and
rigid. This is indeed a valid approach for small water droplets, but may not necessarily apply to ice
crystals. Previous studies have shown that the hydrodynamic behavior of a plate-like hexagon can
be sufficiently approximated by that of a circular disk. Pitter et al showed that a disk of a finite aspect
ratio , where is the semi-major axis length and is the semi minor axis length, has properties
similar to a thin oblate spheroid at low to intermediate Reynolds numbers. The drag coefficient is
therefore calculated for a range of crystal Reynolds numbers from the following correlations derived
by Pitter for crystals with aspect ratios of about 0.05, but also works reasonably well for values up
to 0.5.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
116 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

where the oblate spheroidal drag, for low Reynolds numbers, formulated by Happel and Brenner
is:

Mixed Particle Phase with

5.1.5. Droplets and Crystals

When both particle types (for example, droplets and crystals) are present, the inter-phase coupling
for mass, momentum and energy transfer due to melting or freezing is handled within each individual
system. Therefore both sets of dispersed-phase equations are treated in an uncoupled manner. If
Particle Thermal Equation is not enabled, melting and evaporation are not modeled.

The Droplet drag model can be selected as in Particle Drag Correlations (p. 114). The drag correlations
of the ice crystals, outlined in Ice Crystal Drag Correlations (p. 116), depend on the crystal type, which
will be described in Appendix O - Supercooled Large Droplets (p. 139).

5.1.6. Vapor Transport Equation

DROP3D can model vapor transport and simulate the mass and energy transfer between vapor and
droplets/crystals. Select Enabled in the Vapor model option to activate this functionality. The Particle

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 117
DROP3D - Droplet and Ice Crystal Impingement

thermal equation under Particle parameters must be Enabled to allow the phase change. Besides
the coupled mode, DROP3D can run vapor transport in a standalone mode. It can be activated by
selecting Vapor only in the Vapor model. Droplet and crystal modeling will then be disabled.

The vapor transport equation can be written as follows:

where and are the vapor concentration and the air velocity, respectively. is a volumetric
mass flux source or sink that represents vapor condensation, droplet evaporation or crystal sublimation.
is the effective mass diffusion coefficient that combines laminar and turbulent diffusion coeffi-
cients, for example, . The turbulent mass diffusion coefficient is computed by
where is the turbulent viscosity and is the turbulent Schmidt number. The default value of
turbulent Schmidt number is 0.7.

[Link]. Vapor Nucleation

[Link].1. Introduction
Local water vapor pressure affects the rates of droplet and crystal evaporation, film evaporation
at walls, and condensation onto walls and existing particles. Obtaining a valid solution for the
humidity level and the vapor pressure is therefore important especially for engine icing simulations.
Until now the vapor transport model of FENSAP-ICE did not consider condensation of vapor in
the form of nucleation in the regions where local humidity is greater than 100%. With the addition
of the nucleation feature, this gap in the model is addressed.

[Link].2. Model Description

The current version of the nucleation model simplifies the nucleation process by assuming that
all vapor above saturation is immediately converted to liquid state in the form of nuclei. The
model does not capture supersaturation. The rate of nucleation is calculated based on the resulting
mass transfer rate between vapor concentration and nucleation solution fields, and is applied
directly to the air flow energy equation as a source term. The numerical benefit of this assumption
is the simplicity of the formulation which helps in creating a robust and reliable computational
tool. Vapor and nuclei transport are modeled with the same species equation, avoiding additional
computational cost.

Nuclei are tiny droplets with diameters in the order of a micron or less and assumed to move
with the air velocity around objects at the scale of typical aircraft components. The nucleating
mass is contained within the vapor transport system, and exchanged with vapor depending on
local air temperature and humidity conditions. The release of enthalpy due to nucleation is ex-
changed with the air flow solution through a source term which calculates the rate of nucleation
from the prescribed nuclei concentration in the volume.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
118 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

When running vapor transport coupled with the air flow in FENSAP-ICE, an increase in air temper-
ature will be observed where there is nucleation, and vice versa. If running DROP3D only with
vapor transport enabled, this change in air temperature will not be captured and applied in the
icing simulation. The removal of mass from the gas phase in the vapor transport equation will
reduce local vapor pressure, vapor diffusion rate, and wall condensation, for regions where relative
humidity was over 100%.

[Link].3. Activating Nucleation in Vapor Transport

The option to enable nucleation is found in the model panel of a run configuration window. It
is listed under Vapor model:

By default, this option is enabled when a new run is created. When enabled, there will be a new

solution field in the vapor solution file called Nucleation (kg/m3), which shows the nuclei con-
centration in the computational domain. Together with the vapor concentration, the sum of the
two quantities represent the total mass conserved with the vapor transport model. The relative
humidity will be maximum 100% as any vapor over saturation is collected in liquid form in the
nucleation field.

To observe the change in air temperature due to nucleation/evaporation within the vapor transport
system,

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 119
DROP3D - Droplet and Ice Crystal Impingement

Particle-Airflow thermal coupling (See Particle-Airflow Thermal Coupling) should be used. It is

possible to calculate air flow in energy only mode, following a restart with CFX or Fluent solution.

Note:

Currently,the reduction in total pressure of air mixture due to nucleation is not modeled.
This interaction will not be observed in the coupled vapor-air-particle-energy simula-
tions. The convergence of the coupled air-vapor system may not be as monotonous
as before since the energy coupling creates a feedback mechanism between air tem-
perature, vapor saturation pressure, local humidity, and rate of nucleation. It may be
required to reduce the CFL numbers for both systems if difficulty in convergence is
observed.

Example 5.1: Solving a Coupled System of Air Flow, Crystals, and Vapor with Nucleation

The example below solves a coupled system of air flow, crystals, and vapor with nucleation. The
computational domain is a rotational periodic slice of a circular converging nozzle as shown in
the figure below. The conditions on the inlet boundary which is at the left end of the domain
are:

Air properties
Static temperature 279.43 K
Speed 2.85 m/s
Relative humidity 80%
Crystal Properties
Content 1.07g/m3
Diameter 35 microns
Aspect ratio 1
Temperature 250 K

The only condition applied at the exit boundary to the right is the back pressure which is 42747.5
Pa.

The high level of inflow humidity will suppress sublimation of crystals, and induce melting. The
excess vapor will reach saturation as local static temperature drops due to air flow acceleration
through the narrowing passage, and nucleation will happen. The figures below vapor nucleation,

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
120 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Physical Model

relative humidity, and air temperature with nucleation on and off. With the added heat of con-
densation of nuclei, air temperature increases several degrees.

Figure 5.1: Vapor Nucleation Distribution

Figure 5.2: Relative Humidity Distribution

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 121
DROP3D - Droplet and Ice Crystal Impingement

Figure 5.3: Static Temperature Distribution with Nucleation off (Top) and on (Bottom)

[Link].4. Capturing Supersaturation

It is possible to capture supersaturation if droplets are substituted for nuclei and the standard
diffusion based condensation acts to transfer mass from the vapor system onto the droplets. This
would be done by setting the droplet size to a value presentative of aerosols (i.e. 0.04 microns),
and the LWC to a very low value that would represent a realistic aerosol concentration (i.e.
50000/cm3).

Such a simulation will make use of 3 additional equations – droplet concentration, size, and energy
– and will require significantly more number of iterations due to the high energy flux rates asso-
ciated with such small size particles driving down the local time steps. Therefore the simplified
nucleation model is currently offered as the default method.

5.2. Supercooled Large Droplets (SLD)

This section describes different models for droplet splashing, bouncing and, break-up. These models
only apply to water droplet distributions with a mean diameter greater than 40 microns. Select Enabled
to activate the SLD models.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
122 of ANSYS, Inc. and its subsidiaries and affiliates.
 Supercooled Large Droplets (SLD)

5.2.1. Droplet Break-Up

Break-up is the process by which a large droplet is broken up into a number of smaller stable droplets
by aerodynamic forces. The non-dimensional parameter that is used to determine the probability of
droplet break-up is the Weber Number.

Pilch and Erdman define a correlation based critical Weber number that must be exceeded for break-
up to occur:

The Ohnesorge number (Oh) is a dimensionless number that relates the viscous forces to inertial and
surface tension forces:

is the droplets viscosity, the droplets diameter and the droplets surface tension.

Table 5.1: Droplet Break-Up

Weber Number Break-up Type Description

We < 13 Vibrational break-up Oscillations grow inside the
droplet; if some conditions are
met, the droplet can eventually
split into two large droplets. The
time to break-up is much longer
than for other break-up
mechanisms. For this reason, this
break-up mechanism is
neglected in FENSAP-ICE.
13 < We < 50 Bag break-up The droplet is first deformed into
a disk shape, whose center thins
and forms a bag. The bag then
disintegrates into multiple
fragments. Eventually the thick
ring to which the bag was
suspended splits into different
parts.
50 < We < 100 Bag & stamen break-up Similar to the bag mechanism,
except that a residual droplet
persists at the ring center. The
central droplet and the ring
break up at the same time.
100 < We < 350 Sheet stripping break-up Slightly different break-up
mechanism. Water is
continuously shed from the
oblate-shaped droplet borders.
During this process, the main
droplet persists, while a cloud of

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 123
DROP3D - Droplet and Ice Crystal Impingement

Weber Number Break-up Type Description

very small droplets scatters away
from the droplet periphery.
350 < We < 2670 At higher Weber numbers, a
wave is generated by the flow
on the droplet surface, slowly
eroding it.
2670 < We When the Weber number is
extremely high, wavelets forming
on the droplet surface penetrate
the droplet. The droplet breaks
up into large fragments that may
also be subjected to further
break-up.

Select Pilch & Erdman to activate the break-up model. In this case, a new governing equation is
solved for the local diameter, :

This equation models the evolution in time of the diameter , which becomes stable, after a charac-
teristic time . The source term is the speed at which the droplet reaches a stable diameter . In
this transport equation the diameter is imposed on the inflow boundaries.

The total break-up time depends on the break-up mechanism, or the local Weber number, according
to the following relationships:

The dimensional time is obtained from using the relative velocity between air and droplets, :

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
124 of ANSYS, Inc. and its subsidiaries and affiliates.
 Supercooled Large Droplets (SLD)

The maximum stable diameter is estimated considering that the droplet break-up ceases when
their Weber number drops below 13:

When the Pilch & Erdman model is enabled, the Droplets parameter - Particle type cannot be
changed since the break-up mechanism is tied to the deformation phenomenon, for which a specific
drag relation is required (See Droplet Deformation (p. 125)).

5.2.2. Droplet Deformation

A droplet can reach a critical condition where its shape starts to deform due to the aerodynamic
forces. These non-uniform pressure forces create surface waves on the droplet, while the surface
tension tries to hold it together. Its shape begins to deviate from spherical to an oblate disk (not
aligned with the flow). The drag coefficient of the droplet then begins to increase. At a critical moment,
surface integrity can no longer be maintained and the droplet begins to break up.

Since deformation and break-up are strongly coupled, the following droplet deformation model is
automatically activated if droplet break-up is selected (See Droplet Break-Up (p. 123)).

Below a Weber number of 13, the drag on a droplet is interpolated between that of a spherical drop
and a disc (Schmel):

where:

and is computed using an experimental correlation from Hsiang & Faeth:

5.2.3. Splashing and Bouncing by Post-Processing

This model modifies the droplet collection efficiency on the surface by predicting if all the impinging
water bounces, or if a part of it splashes. In either case, no splashed or bounced droplets are re-intro-
duced into the computational domain. The models used to predict the change in collection efficiency
are described in Splashing and Bouncing by Body Force (p. 126), Mundo Model (p. 127) and Honsek-
Habashi Model (p. 128).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 125
DROP3D - Droplet and Ice Crystal Impingement

To activate this model, select the Post-processing option in the Splashing and bouncing menu.

5.2.4. Splashing and Bouncing by Body Force

The Splashing and bouncing By body force model is a modification of the original droplet equations
in which additional body forces are added in the vicinity of solid surfaces to simulate the effect of
wall- droplet interactions on the droplet flow. It is activated by selecting the By body force option
in the Splashing and bouncing menu:

The governing equations for the droplets become:

Where D, B and G are the forces due to drag, buoyancy and gravity per unit mass. The impact of
splashing on the droplet momentum is modeled via a body force term applied on the elements
connected to the impinging surface:

where is the impact velocity of the primary droplets, is the velocity of the splashed droplets
and is the collision time.

Since the body force model is based on the primary droplet impingement characteristics, it is activated
only when the change of the primary droplet impingement reaches convergence. Convergence is
detected when the change in total collection efficiency drops below the Activation trigger. The
parameter Delay controls the number of iterations below the Activation trigger level before the
activation of the body force model.

Note:

Tetrahedral or pyramidal elements should not be placed on wall surfaces when the
splashing-by-body-force model is activated.

The model is restricted to steady-state simulations.

To facilitate restarts after the body forces have been introduced in the simulation, an inter-
mediate droplet solution file is saved when the change in total collection efficiency drops
below the Activation trigger and the specified Delay is completed (See Solution Files
with SLD (p. 167)).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
126 of ANSYS, Inc. and its subsidiaries and affiliates.
 Supercooled Large Droplets (SLD)

5.2.5. Mundo Model

The Mundo model is the default model for use with Splashing and bouncing by Post-processing.
To select this model, set Splashing model to Mundo.

The Mundo model determines the probability of splashing or bouncing based on a Mundo parameter
kM:

Where kC is the Cossali parameter defined by Weber and Ohnesorge number:

[Link]. Splashing
Splashing is said to occur when:

where R is the roughness height and is set to 0.5 mm for all droplet sizes.

The secondary-to-primary droplet diameter ratio (ds/di) and the number of secondary particles (ns)
is calculated as:

Subscripts s and i stand for secondary and primary particles respectively.

The secondary-to-primary droplet concentration can be defined as:

The Mundo model assumes that the collision between droplets and the wall is elastic, and the
splashed droplet velocities are equal to the impingement velocities (see Referenced within this
manual (p. 526)):

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 127
DROP3D - Droplet and Ice Crystal Impingement

where subscripts n and t correspond to the normal and tangential orientations of the velocity
vector.

[Link]. Bouncing

5.2.6. Honsek-Habashi Model

The Honsek model is the default model for use with Splashing and bouncing by Body force. To
select this model, set Splashing model to Honsek.

The Honsek-Habashi model determines the probability of splashing, bouncing or disintegration based
on a threshold computed by Trujillo and Lee.

[Link]. Splashing
Splashing if the Cossali parameter . The number of splashed particles are defined as:

The secondary to primary droplet concentration is calculated as:

The droplet diameter ratio, normal and tangential velocity ratio is calculated as:

[Link]. Bouncing
Bouncing occurs if and is characterized within a Weber number range:

The secondary to primary droplet parameters are calculated as:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
128 of ANSYS, Inc. and its subsidiaries and affiliates.
 Supercooled Large Droplets (SLD)

[Link]. Spreading or Disintegration

Spreading or disintegration occurs if and is also characterized by Weber number:

5.2.7. Wright-Potapczuk Model

To select this model, set Splashing model to Wright.

The Wright model determines the probability of splashing or bouncing based on corrections made
to the Mundo parameter described in Mundo Model (p. 127):

The Wright parameter is defined from by considering impingement velocity angle with respect
to the surface normal:

[Link]. Splashing
Splashing occurs if . The secondary to primary droplet parameters are calculated as:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 129
DROP3D - Droplet and Ice Crystal Impingement

[Link]. Bouncing
Bouncing if . The secondary to primary droplet parameters are calculated as:

5.2.8. Terminal Velocity

In Body forces → Gravity, select Enabled in the Terminal velocity box to activate this option, oth-
erwise, select Disabled. If this option is enabled, the magnitude and direction of the gravity vector
must be specified.

Note:

The gravity vector should be perpendicular to free stream velocity if level-flight conditions
are being simulated.

Due to their larger MVD, SLD droplets cannot be assumed to remain in static atmospheric suspension
but rather they behave like rain drops falling with a terminal velocity. Hence, an additional vector
component is introduced in the droplets initial approach velocity, resulting in an altered impingement
trajectory.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
130 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Since the droplet velocity appears in both the drag coefficient and the droplet Reynolds number,
there is a general difficulty in establishing correlations expressing a droplet's terminal velocity in terms
of the corresponding Reynolds number. Hence, a dimensionless quantity known as the Galileo number
may be defined as a function of physical properties of the gas and liquid phase in order to eliminate
the unknown terminal velocity:

Khan & Richardson derive a comprehensive correlation expressing the Reynolds number as a function
of the Galileo number:

Once the terminal Reynolds number is evaluated, the corresponding terminal velocity may be obtained
from:

which is added to the inflow droplet velocity.

The gravity vector components must be set in order to enable the terminal velocity. Furthermore,
the Galileo number is computed from reference properties that are constant over the computational
domain, hence the use of terminal velocity with space or time-dependent boundary conditions has
no relevance.

5.3. Particle Conditions

Since the set of discrete particle equations is in non-dimensional form, a set of suitable reference con-
ditions are required.

5.3.1. Reference Flow Conditions

The air and particle equations could be solved simultaneously (as in a two-phase flow). However,
since the density of a water droplet is 1,000 times greater than the density of air and the water fraction
is dilute, the equations are solved in a segregated manner. The airflow is solved first, followed by the
particle equations. In other words, the effect of the air on the particle is considered, but not the reverse.

It is important, however, to ensure that the reference conditions for the particle calculation, for example
the reference Reynolds and Mach numbers, remain the same as in the associated airflow calculation.

Note:

When carrying out icing simulations with FENSAP-ICE, it is highly recommended that the
reference conditions represent the icing cloud conditions and the true air speed (TAS) of
the aircraft or test article. In case of helicopter rotor analysis, the blade tip speed is the
ideal choice for reference velocity. The reference conditions are used to non-dimensionalize

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 131
DROP3D - Droplet and Ice Crystal Impingement

the model equations and the collection efficiency. Certain numerical aspects in DROP3D
that are used to improve stability and convergence in the shadow zones will be affected
by these settings. Characteristic length should have no impact on the solution other than
changing the scale of the residual plots.

5.3.2. Droplets Reference Conditions

The main physical parameters describing the droplets are:

The Liquid Water Content (LWC): the density of water droplets in the air.

The Droplet diameter, : spherical droplets are assumed to be of a single, uniform size, usually equal
to the median volume diameter (MVD) of the sample size distribution. The Droplet diameter is in
microns.

The Water density, : generally set to 1,000 kg/m3 for water.

The Droplet distribution: Built-in or user-defined.

Droplet Distributions
Several built-in droplet size distributions can be selected in the Droplet distribution pull-down menu
of the Droplets reference conditions section of the Conditions panel:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
132 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Monodisperse indicates a calculation performed for a single diameter, specified in the Droplet dia-
meter.

Langmuir B to Langmuir E distributions can be simulated by computing the droplet concentration

and speed for each individual diameter of the discrete distribution, which are subsequently automat-
ically weight- averaged at the end of the simulation. The various Langmuir diameter distributions and
their corresponding weights are pre-defined in FENSAP-ICE.

Custom distribution can also be selected (for example, in order to solve the same droplets distribution
found in an icing tunnel).

Click Set distribution to enter the droplet diameters and weights of the distribution. A window will
then open to permit the definition the parameters.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 133
DROP3D - Droplet and Ice Crystal Impingement

Important:

Cumulative droplet diameter values must be entered from largest to smallest size.

Enter the Number of samples and define, for each of them, the Droplet Diameter (micron) and
Weight (%) as percentage of LWC (the sum of this column should always be 100%). This distribution
is simulated by computing the droplets concentration and speed for each diameter, and by applying
the proper weighted averaging (%) to the individual droplets solutions. The graph shows the Weight
(blue) and Cumulative Weight (red) curves of the distribution.

Note:

The cumulative weight distribution appearing in the graph does not reach 100% at the
last diameter, since it is computed as:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
134 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

5.3.3. Ice Crystals Reference Conditions

The ice crystals reference conditions require setting the Freestream crystal content, analogous to
the Liquid water content, and the selection of a Crystal type and its Size.

Several predefined crystal types can be selected:

• Hexagonal plate:

Predefined aspect ratio, only size can be configured.

• Crystal-flat branches:

Predefined aspect ratio, only size can be configured.

• Dendritic crystal:

Predefined aspect ratio, only size can be configured.

• Solid thick plate:

Predefined aspect ratio, only size can be configured.

• Custom:

Both size and aspect ratio can be configured.

5.3.4. Appendix C
Appendix C contains three graphs per cloud environment type, which are built into FENSAP-ICE. The
first graph from Appendix C can be viewed by selecting the Appendix C option in the Choose Ap-
pendix drop-down menu in the Droplets reference conditions section.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 135
DROP3D - Droplet and Ice Crystal Impingement

Clicking the Configure button opens the configuration environment, which shows graphically the
extent of the envelope covered by Appendix C.

The first graph relates to OAT (Outside Air Temperature), LWC and MVD. Since OAT is usually fixed
in the airflow calculation, once the droplets size is selected FENSAP-ICE calculates the corresponding
LWC. FENSAP-ICE displays both the isothermal curve in blue on the graph as well as the selected
condition with a red cross symbol.

The original graphs from Appendix C can also be displayed by clicking on the right in the Air
temperature, Altitude and Droplet diameter boxes in the Configuration section shown in the fol-
lowing figure.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
136 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

The second graph of Appendix C relates pressure altitude to OAT. It can be viewed by pressing the
question mark button (?) in the Altitude row. FENSAP-ICE will issue a warning if the chosen combin-
ation of altitude and temperature is outside the envelope of Appendix C.

The third graph from Appendix C relates LWC to the cloud extent. It can be viewed by pressing the
question mark button (?) at the right of the scroll-down menu in the LWC correction section. The
two icing cloud extent types, CM for Continuous Maximum and IM for Intermittent Maximum, have
standard cloud extents of 33 and 5 nautical miles, respectively. Appendix C specifies that if the cloud
extent considered differs from these values, the LWC must be corrected to maintain condition
severity. A shorter cloud extent, therefore, leads to a higher LWC and conversely for longer horizontal
extents.

Two environments are available: Continuous maximum, designed to represent stratiform clouds and
Intermittent maximum for cumuliform clouds.

Click the LWC correction check box to display the LWC correction. If you are considering a component
or system in forward flight, then the cloud extent is related to exposure time and true airspeed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 137
DROP3D - Droplet and Ice Crystal Impingement

Therefore, if exposure time is specified, FENSAP-ICE will calculate the equivalent cloud extent from
the true airspeed and correct the LWC to reflect the change in severity. The other option is for FENSAP-
ICE to calculate the exposure time required to traverse a cloud of standard extent.

Note:

Air temperature, Altitude or Droplet diameter values outside the envelope of Appendix C
will be displayed as red numerals.

To avoid conflicts with the reference conditions of the airflow solution when running the ice accretion
simulation with ICE3D, it is not possible to override the Air static pressure and Air static temperature
values set in the Reference conditions section. It is possible to edit the Altitude and Air temperature
values to explore the envelope, but the new values will not be saved if they override the reference
conditions. You should always make sure that the Reference conditions sections of the FENSAP,
DROP3D and ICE3D configurations are identical.

Several drop diameter distributions can be selected with the Droplet distribution pull-down menu
in the Droplets reference conditions section. The following figure shows the Langmuir D distribution.

The droplet diameters and weights of the distribution are shown in the three columns on the left of
the graph. The two curves show the weight distribution (blue) and cumulative weight distribution
(red) as functions of the droplet diameter.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
138 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Two options are available in the pull-down menu at the bottom of the window:

1. 7 diameters

2. 4 diameters, enriched

If the 7 diameters option is selected, all diameters will be computed. If the 4 diameters, enriched
option is selected, only four of the diameters will be computed and the remainder will be interpolated
using Reduced Order Modeling.

Note:

Reduced Order Modeling will reduce the execution time, however you must ensure that
the technique is acceptable for their own needs. The legend below the graph indicates
which diameters are computed and which diameters are interpolated.

Tip:

You can edit the distribution by selecting Custom distribution in the Droplets reference
conditions panel.

5.3.5. Appendix O - Supercooled Large Droplets

Appendix O is the proposed FAA aircraft certification regulation describing the Supercooled Large
Droplets (SLD) icing conditions that may occur in and/or below the stratiform clouds defined in Ap-
pendix C of the FAA 14 CFR Part 25 certification guidelines. The FAA SLD environment is divided into
two categories: the Freezing Drizzle Environment (FDE) and the Freezing Rain Environment (FRE). The
spectrums of droplet distributions of each category is further subdivided into two distribution sub-
categories: MVD < 40 μm and MVD > 40 μm, where the 40 μm reference value is the Maximum Effective
(drop) Diameter (MED) of Appendix C icing conditions for Continuous Maximum stratiform clouds.

Enable the SLD option in the Model panel to gain access to the Appendix O functionalities. Three
SLD related options will be revealed; Break-up model, Splashing and bouncing, and Terminal ve-
locity.

For all SLD simulations, a Splashing and bouncing model should be enabled. The Post-processing
option is recommended.

For FRE conditions, the Break-up model should be set to Pilch & Erdman, and Terminal velocity
should be Enabled. FRE conditions include very large droplet sizes that are more sensitive to break-
up phenomena and gravity. When Terminal velocity is Enabled, the appropriate direction of the
Gravity vector must be defined in the Model panel. If not already set, FENSAP-ICE will prompt to
enable Terminal velocity when the FRE environment is selected.

FDE conditions do not include such large droplet sizes, they are not significantly affected by break-
up and gravity. Therefore, these settings do not need to be enabled. Splashing and bouncing alone
should be enough to characterize this environment.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 139
DROP3D - Droplet and Ice Crystal Impingement

Figure 5.4: Typical SLD Options, Freezing Drizzle Environment

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
140 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Figure 5.5: Typical SLD Options, Freezing Rain Environment

Select Enabled to set the Terminal Velocity to a non-zero gravity vector.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 141
DROP3D - Droplet and Ice Crystal Impingement

The two environments and their parameters are set in the Droplet reference conditions section of
the Conditions panel.

[Link]. Choosing the SLD Icing Condition

To access the Appendix O conditions, set Choose Appendix to Appendix O. A message will appear
asking you to select the Appendix O distribution. For now, select Appendix O (FAA AC 25-28).
This is explained further in Choosing the SLD Droplet Distribution (p. 148).

Click the Configure... button to open the Super-cooled Large Droplets Icing Conditions config-
uration window. The selected icing condition will be displayed in the active envelope as a red cross
mark.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
142 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 143
DROP3D - Droplet and Ice Crystal Impingement

Select the desired Environment by clicking either the Freezing Drizzle or Freezing Rain button,
and select the desired Distribution by clicking either the <40 microns or >40 microns button. If

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
144 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Terminal velocity and other required options are not already activated in the Model panel, DROP3D
will issue warnings and prompt for their activation when clicking either of these buttons.

Note:

The maximum liquid water content of the MVD > 40 μm distribution is smaller than for
the MVD <40 μm droplet distribution.

Tip:

The value of LWC can be edited in this panel and will override the value set in the Ref-
erence conditions.

Important:

It is not possible to override the Air static pressure and Air static temperature values
set in the Reference conditions section. This is done intentionally to avoid conflicts
with the reference conditions of the FENSAP solution. It is possible to edit the Altitude
and Air temperature values to visually explore the envelope in the window, but the
new values will not be saved if they override the reference conditions. Always make sure
that the values set in the Reference conditions sections of the FENSAP, DROP3D and
ICE3D configurations are identical.

If the chosen values are outside the range of validity of the selected environment and its distribution
sub-category, the value out of range will be displayed in red.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 145
DROP3D - Droplet and Ice Crystal Impingement

When the altitude exceeds 12,000 ft, temperature limits are activated and only the lighter part of
the envelope is accessible. Temperature values that exceed the limit will be shown in red.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
146 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

The original graphs from Appendix O can be consulted by clicking the question mark ( ) buttons
on the right of the configuration values.

Just as in Appendix C, the LWC can be corrected for either total time in the icing cloud or for cloud
extent. Click the LWC correction check box to activate this option.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 147
DROP3D - Droplet and Ice Crystal Impingement

Select either the total time or the cloud extent with the pull-down menu and modify the relevant
fields. The corrected value will be displayed as a blue cross on the graph.

[Link]. Choosing the SLD Droplet Distribution

When Choose Appendix is set to Appendix O, a warning message appears prompting you to select
a Droplet distribution.

Select Appendix O (FAA AC 25-28) to set the Droplet distribution to the 10 diameter built-in
distributions that were provided in Tables 1 and 2 of the FAA Advisory Circular AC 25-28 published
October 27th, 2014.

Click the View distribution button to display the droplet distribution, as shown in the following
figure.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
148 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Figure 5.6: Appendix O (FAA AC 25-28) Droplet Distribution Graph and Table

The title of the graph identifies the specific distribution that has been selected in the configuration
window. The values of the weights for each droplet diameter are displayed in a table on the left,
and the weight distribution (blue curve) and the cumulative weight distribution (red curve) are
shown as functions of droplet diameter in the graph on the right.

Notice that the menu options for Diameter distribution are disabled at the bottom of the window.
This is because, currently, there is only one diameter distribution provided for each environment
in the FAA AC 25-28.

It should be noted that the FAA Advisory Circular AC 25-28 states:

" Applications of drop size distributions require a bin tabulation of the proportion of mass (liquid water
content) to drop diameter. Mass proportions for the bins were selected to provide a reasonable resolution
of the upper range of the distributions. The shaded columns (a) and (b) in the tables contain values
typically used as input to ice accretion computer codes. For some simulation techniques, different
methods of segregating the bins may be appropriate. "

The document suggests that the use of different distributions of droplet sizes and weights may be
appropriate for some simulation techniques. Because of large jumps between simulated droplet
sizes, the 10 diameter FAA AC 25-28 distribution may not produce a smooth representation of
droplet impingement on wetted surfaces for many applications. In this instance, it may be useful
to select one of the alternative distributions described below.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 149
DROP3D - Droplet and Ice Crystal Impingement

Alternative 1:
Select Appendix O (Refined) to access the alternative diameter distributions available in DROP3D.
These distributions use a different diameter segregation method to provide a more refined definition
of the Appendix O SLD environments.

Click the View distribution button to display the droplet distribution, as shown in the following
figure.

Figure 5.7: Appendix O (Refined) Droplet Distribution Graph and Table (25 Diameters)

Again, the values of the weights for each droplet diameter are displayed in a table on the left, and
the weight distribution (blue curve) and the cumulative weight distribution (red curve) are shown
as functions of droplet diameter in the graph on the right. If a distribution with enrichment (via
ROM) has been selected, a legend is provided below the graph to indicate which diameters are
computed and which diameters are interpolated.

There are now four options for Diameter distribution available in the pull-down menu at the
bottom of the window:

1. 25 diameters

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
150 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

2. 10 diameters, enriched

3. 25 diameters, enriched

4. 97 diameters

These built-in distributions were constructed by using a 97 diameter representation to discretize

the cumulative weight distribution curves provided in Appendix O to CFR Title 14 Part 25.1420. The
computation of all 97 droplet diameters can become a resource intensive task, hence additional
options are offered that take advantage of enrichment via Reduced Order Modelling (ROM). In this
manner, you can select the one that best suits the available computational resources without paying
a heavy penalty in accuracy.

If the 25 diameters option is selected, the SLD environments are represented using a smaller set
of 25 points. The table to the left of the cumulative distribution curve shows the droplet diameters
and their corresponding weights.

If the 10 diameters, enriched option is selected, only 10 of the 97 diameters will be computed
and the remaining 87 diameters will be interpolated using ROM.

If the 25 diameters, enriched option is selected, 25 of the 97 diameters will be computed and the
remaining 72 diameters will be interpolated using ROM.

If the 97 diameters option is selected, the full 97 diameter distribution will be computed. This is
the most accurate but computationally expensive option.

Note:

The following curve shows the results of collection efficiency on a NACA23012 airfoil.
The Freezing Drizzle environment, MVD > 40μm was simulated using three distributions:

• Appendix O (Refined): 10 diameters, enriched

• Appendix O (Refined): 97 diameters

• Appendix O (FAA AC 25-28): 10 diameters.

Of the three simulated distributions, the Appendix O (Refined): 97 diameters provides

the smoothest representation of the droplet environment, thanks to the relatively small
changes between each simulated diameter, and it therefore produces a smooth collection
efficiency curve. In this case, the Appendix O (Refined): 10 diameters, enriched also
provides a smooth collection efficiency curve. The enrichment by Reduced Order Model-
ling (ROM) contributes significantly to the smoothness of the curve. However, the Ap-
pendix O (FAA AC 25-28): 10 diameters distribution produces a discontinuous collection
efficiency. The large change in diameters between droplets contributes to these discon-
tinuities. Therefore, in this case, it may be most appropriate to use the Appendix O
(Refined): 10 diameters, enriched distribution as it provides a good level of smoothness
while also offering a reduction in computational cost.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 151
DROP3D - Droplet and Ice Crystal Impingement

Figure 5.8: Comparison of Collection Efficiency for Different Simulated Distributions

Alternative 2:
Finally, the Custom distribution option can be selected to enable the definition of user-defined
custom droplet distributions. The droplet diameters specified in the Custom distribution must be
listed in decreasing order. However once you select the Custom distribution option, DROP3D will
immediately switch out of Appendix O, since DROP3D does not support custom distributions
within the Appendix O environment.

Note:

The droplet sizes and weights in the Appendix O (FAA AC 25-28) and Appendix O
(Refined) droplet distributions are different, because different discretization methods
were used to create them. Both distributions describe the same SLD environments. The
distributions are compared in the following figure. The black curve is the cumulative
weight distribution that represents the Freezing Rain Environment, MVD > 40 microns,
as outlined in the Appendix O regulations. The large red squares represent the droplet
sizes and weights tabulated in the FAA AC 25-28 document, accessible in DROP3D by
selecting Appendix O (FAA AC 25-28): 10 diameters. The large green triangles and
small green dots represent the simulated and enriched droplet sizes and weights access-
ible in DROP3D by selecting Appendix O: 10 diameters, enriched. Notice that both sets
of points all lie on the same curve, however their positions are different. The FENSAP-
ICE distributions are heavily weighted in the upper range of droplet diameters, where
splashing and bouncing phenomena are more dominant.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
152 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Figure 5.9: Cumulative Weight Distribution Represented Using Different Discretizations

Note:

Reduced Order Modeling dramatically reduces execution time, however you must ensure
that the technique is acceptable for your needs.

Splashing and bouncing effects tend to cause discontinuities in the individual collection
efficiency curves of the larger droplets, therefore a larger number of droplet sizes may
be required to produce smooth cumulative collection efficiency distributions.

5.3.6. Appendix D - Ice Crystals

Appendix D is the proposed FAA aircraft certification regulation concerning Ice Crystals (IC) conditions
associated with convective storms. In order to access the Appendix D configuration window, the
Particle type in the Model panel should be set to Crystals or Droplets + Crystals.

If only ice crystals are desired, select the Crystals option in the pull-down menu of the Particle
parameters section.

In the Ice crystals reference conditions section of the Conditions panel, set Choose Appendix to
Appendix D and click the Configure button to open the configuration window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 153
DROP3D - Droplet and Ice Crystal Impingement

The configuration window gives access to the Air temperature and Altitude settings, from which
the total water content is determined.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
154 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

The selected conditions will appear in the envelope of Appendix D as a red cross. Select either the
Liquid Water Content or the Ice Crystal Content to establish the ratio of the two particle types.

Important:

It is not possible to override the Air static pressure and Air static temperature values
set in the Reference conditions section, to avoid conflicts with the reference conditions
of the FENSAP solution. It is possible to change the Altitude and Air temperature values
in order to explore the envelope, however the values will not be saved. You should always
make sure that the Reference conditions sections of the FENSAP, DROP3D and ICE3D
configurations are identical.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 155
DROP3D - Droplet and Ice Crystal Impingement

Values outside the envelope of Appendix D will be shown in red.

If ice accretion calculations based on ice crystals are desired, a mixture of droplets and ice crystals
should be selected. The physical reason for this choice is that crystals need a thin film of water in
order to stick to a surface.

Choose the Droplets + Crystals option in the pull-down menu of the Particle parameters section.

In this case the reference conditions for both the droplets and the crystals must be set. Go to the
Conditions panel and set the desired values in the Droplet reference conditions. When droplets
plus crystals mixtures are used, the value of the Liquid Water Content is usually low, usually in the
range from 0.1 to 1 gm/m3.

In the Ice crystals reference conditions panel, select Appendix D from the pull-down menu. Click
Configure to display the configuration window.

Note:

The value of the ICC (Ice Crystal Content) is automatically set by FENSAP-ICE. The
graph displays TWC (Total Water Content) as a function of Altitude and Temperature.

Total Water Content is defined as:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
156 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

The Total Water Content value can be corrected for time in the icing cloud or extent of the icing
cloud by clicking the TWC correction check box. The TWC correction panel is similar to that of Ap-
pendix O.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 157
DROP3D - Droplet and Ice Crystal Impingement

Select either the total time or the cloud extent with the pull-down menu and modify the relevant
fields. The corrected value is displayed as a blue cross on the graph.

5.3.7. Droplet Initial Solution

The Eulerian particle flow calculation is an iterative process like air flow calculation and requires initial
conditions to be specified. There are several initial solution options to choose from.

Velocity Components
By default, the Liquid Water Content is initialized throughout the computational domain to its ref-
erence value.

If the option Velocity components is selected, the three components of the droplet velocity (Velocity
X, Velocity Y and Velocity Z) are imposed as an initial guess throughout the computational domain.

Note:

If the input grid file is in cylindrical coordinates, the velocity components should be given
as (m/s), (rad/s) and (m/s).

Velocity Angles
If Velocity angles is selected, the three components of the initial droplet velocity vectors are computed
from the two angles (See Velocity Angles (p. 70) and the norm of the reference velocity vector (See
Reference Conditions (p. 67)).

Note:

The angle of attack is the angle of the velocity vector in the X-Y plane. The yaw angle is
the angle of the velocity vector in the X-Z plane. Both angles are in degrees.

For difficult cases which have strong recirculation zones, the Liquid Water Content can
be set to zero throughout the domain, except at the inflow boundaries, by checking the
Dry initialization box.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
158 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Vapor Initialization
Vapor field can be initialized with either vapor concentration, or relative humidity, or wet-bulb tem-
perature. Relative humidity ranges from 0 to 100%. It is defined as the ratio of the partial vapor
pressure to the saturation vapor pressure. When relative humidity is set as the initialization method,
the local air temperature will be taken as reference on each grid node to calculate the corresponding
vapor pressure and concentration. With wet-bulb temperature setting, the vapor pressure in the domain
will be uniform and equal to 100% RH at that temperature, while its concentration will still depend
on local air temperature using the partial pressure and partial density relationship with the gas constant
for water vapor.

Figure 5.10: Initialization Using Vapor Concentration

Figure 5.11: Initialization Using Relative Humidity

Figure 5.12: Initialization Using Wet-Bulb Temperature

Dry Initialization
By default, DROP3D initializes the entire solution field using the reference Liquid Water Content or
Ice Crystal Content value. In internal flows this may not be ideal since some regions may not receive
any droplets and it may take a greater number of iterations to dissipate the non-zero water content
values in these locations. For external flows, droplets that initially become trapped in strong recircu-
lation zones may take a long time to clear out. In certain situations such issues can give rise to solution
instabilities. Dry initialization is recommended in general, especially if there are strong recirculation
zones in the airflow.

Input Profile
DROP3D can impose an inlet droplet velocity profile from a [Link] file. Select Input profile
in the Droplet initial solution menu.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 159
DROP3D - Droplet and Ice Crystal Impingement

If the Input profile type is set to TimeBC file, use to open the browse window and select the
appropriate [Link] file. [Link] files are files generated by FENSAP/DROP3D and ICE3D
to exchange node-based information among modules. See The [Link] file (p. 407) for more inform-
ation on the format of these files.

Input Rotational Profile

In turbomachinery each stage has its own grid, coupled to the preceding and following rows at their
interfaces through the pitch averaging procedure. The airflow solution process is based on a recursive
sweep through the stages with bi-directional data exchange from one stage to its neighbors at the
interfaces.

Select the Rotational DROP3D solution option in the Input profile type box.

The rotation speed is set in the Body forces section of the Model panel. Stationary stages have a
rotation speed of 0 rpm. Source BC refers to the index of the outflow boundary of the preceding
row, while Target BC refers to the boundary index of the inflow boundary of the following row. The
figure above shows the configuration for a non-rotating stage with inlet BC 1000 and outlet BC 3000.
The Reference LWC is the liquid water content of the first component in the series, required to cor-
rectly compute the water impact efficiency since as the droplets proceed through the rows some
water mass is lost in each row due to impingement on the blades, the hub and shroud.

Two methods are available for the boundary conditions: Mass flux is a mass-weighted pitch averaging,
while Averaging refers to simple pitch averaging. The averaging is computed using N points
equidistant from the rotational axis across the passage. Mass flux averaging is selected by default.

If ice crystals are enabled, the input solution file name for ice crystals is also required. The correspond-
ing reference Ice Crystal Content value must also be set in the panel.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
160 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Conditions

Dry Zone Initialization

In some regions, such as enclosures which are connected to the main flow but where the water
droplets are not expected to penetrate, for example the inner cavity of an engine nose cone, it may
be desirable to initialize and maintain dry conditions (zero LWC). To enable this option, in the Domains
panel, select the domain that is expected to remain dry and set its Initial conditions to Dry zone:

Note:

The grid file must contain more than one domain for this option to be accessible. See The
Domains Table (p. 399) for more information on domain IDs.

The Dry initialization condition is different than Dry zone, which does not allow the droplet solution
to change, maintaining zero water content at all times and excluding this zone from the calculation
of the average residuals.

5.3.8. Initial Velocity Display

Click the display icon to display the Initial velocity vector in the graphical window. Click the icon
again to remove the velocity vector from the graphical window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 161
DROP3D - Droplet and Ice Crystal Impingement

5.3.9. Restarting DROP3D

If Solution restart is selected, the droplets field is initialized with a previous droplet solution read
from a file.

If vapor model is enabled, a Solution restart file can be provided to initialize the vapor field.

Click the browse icon to open the file browser and select the solution file to be used for restarting
the calculation.

Note:

The restart file must have the same number of nodes as the current grid.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
162 of ANSYS, Inc. and its subsidiaries and affiliates.
 DROP3D Boundary Conditions

5.4. DROP3D Boundary Conditions

Particle transport equations are hyperbolic and they only need conditions to be defined at upstream
boundaries. Inflow nodes are assigned Dirichlet conditions for particle properties, while walls and exits
are free. Particles leave the computational domain through walls as water catch and exits. Similar to
losing total air pressure through screens, particle concentration is also reduced across these boundaries
as a function of the local blockage and water catch on the screens.

5.4.1. Inlets and Far Fields

The particle flow boundary conditions are specified only at inlets. The Liquid Water Content or Ice
Crystal Content, velocity components and temperature are needed when the Particle thermal
equation is enabled (See Particle Thermal Equation (p. 267)).

Melt fraction is available as a boundary condition for crystals when the crystal temperature is 273.15
+- 0.001 K. Crystal species max temperature is currently clipped to 273.15K and any higher value
entered as a boundary condition will automatically be clipped within the solver.

When the vapor model is enabled, the vapor amount at the inlet can be specified as vapor concen-
tration, relative humidity, or in terms of wet-bulb temperature.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 163
DROP3D - Droplet and Ice Crystal Impingement

Each boundary condition can either be constant in space or be a function of the grid coordinates. In
this case a formula can be built by clicking the f(x) function button to open the formula window. See
Boundary Conditions Varying in Space (p. 92) for an example of how to construct a boundary condition
using this feature.

The check marks beside the boundary condition fields serve to allow the solver to use the air flow
values or the values found in the particle restart solutions. This is useful when there is a restart file
involved and the inflow particle conditions are non-uniform.

Click the display icon to display the boundary velocity vector in the graphical window. Click again
to remove the velocity vector from the graphical window.

5.4.2. Vapor Transport – Wet Walls

For the wall boundary condition, vapor transport modeling provides an option that allows the walls
to stay at 100% relative humidity and enables evaporation at these walls. This option is generally not
needed in icing related simulations. This model injects vapor into the domain through diffusion from
a wall boundary and can be used to track water evaporation from fully wetted surfaces into the sur-
rounding air. Select Enabled to activate this wet wall condition.

5.4.3. LWC Reduction Across Screens

The reduction in liquid water content is simulated by considering the blockage created by the wire
mesh. Droplets collect on the wires, hence the liquid water content past the screen is reduced, com-
pared to the upstream flow. The drop in LWC is calculated by considering the ratio of total wire area
to the free area:

5.5. Droplets Solver Parameters

All the parameters that control the execution of the droplet module are set to default values. You may
change some of these parameters once you have gained a sufficient confidence level.

5.5.1. Steady-State Solution

To improve the performance of the iterative matrix solver, the terms associated with the temporal
operator of the droplets equations can be added to the Jacobian matrix (note that these terms do
not affect the residuals). The addition of these terms, proportional to 1/Δt, increases the diagonal
dominance of the Jacobian matrix and therefore improves the convergence of the iterative matrix
solver. The solution is then advanced in time until the time derivative terms become zero, or the flow
field reaches steady-state.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
164 of ANSYS, Inc. and its subsidiaries and affiliates.
 Droplets Solver Parameters

The choice of the local time step, for an element, is based on a stability analysis of the explicit-Euler
centered finite difference scheme, which provides a maximum theoretical . In DROP3D, the time
step is then selected as:

The droplets solution is advanced in time, with a that varies from one cell to another, until steady-
state is reached. At each time step, only one Newton iteration is performed to linearize the system.
The linear matrix system is solved using a GMRES approach.

Tip:

Recommended values for the CFL number range between 10 and 20. If convergence
problems are encountered, lower the CFL number.

Smaller droplets are affected by the airflow more than the larger ones and generally take
more iterations to converge. If the quality of the grid is good and the run is stable, the
CFL number can be increased to 100 or more to achieve convergence in a reasonable
number of iterations.

Maximum number of time steps is the maximum number of iterations of DROP3D. If the solution
has not converged sufficiently at the end of the iteration process, restart the droplets calculation from
the previous solution (See Restarting DROP3D (p. 162)) and perform additional iterations.

5.5.2. Artificial Viscosity

The Streamline upwind (SU) technique adds artificial viscosity exclusively in the direction of the
droplet velocity as an anisotropic artificial diffusivity. In tensor form the artificial viscosity coefficient
can be written as:

where

This coefficient is automatically computed by DROP3D and cannot be modified.

To address spurious oscillations that can occur in the cross-flow direction, the SU scheme is comple-
mented with a user-set crosswind diffusion amount, which acts exclusively in the cross-flow direction.
The default baseline magnitude is 10-5 and it scales with element size, where its power reduces as
elements get finer.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 165
DROP3D - Droplet and Ice Crystal Impingement

In the case of structured grids, the LWC discontinuity present in the shadow zone can result in node-
to-node oscillations in the cross-flow direction for certain droplet sizes. These can be suppressed by
dragging the cross-wind dissipation slider to Robustness,10-4. In general, the effect on the collection
efficiency will be negligible, however, case specific experimentation is recommended before adopting
a higher value.

5.5.3. Advanced Solver Settings

[Link]. Convergence Criteria

Two parameters control the DROP3D convergence stopping criteria: the overall residual of the
governing equations and the change in total beta (cumulative water catch) on all the wall surfaces.
Total beta is a derived quantity and therefore may require more iterations to fully converge. Change
in total beta usually does not exhibit a monotonous behavior, therefore the activation of this
stopping criterion is delayed until the average residual of the last 20 iterations is below the specified
criterion.

[Link]. Dissipation Scaling

The amount of streamline artificial dissipation can be increased or decreased by further adjusting
the scaling parameters. These are only available if Show advanced / beta solver options is checked
in Settings → Preferences → General tab. It is strongly recommended that these values are kept
as 1 for accurate particle impingement solutions. If the computations have difficulty converging,
the remedy should be looked elsewhere. It could be that the boundary conditions are not set
properly, the airflow has not fully converged, or the grid quality is inadequate overall or in certain
parts of the domain. Increasing cross-wind dissipation should be tried before resorting to increasing
overall dissipation scaling.

The maximum value for the dissipation scaling is limited to 2. Entering higher values will result in
a warning message logged in DROP3D.

5.6. Output
The solution of DROP3D can be printed to a file with a user-selectable name at specified intervals.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
166 of ANSYS, Inc. and its subsidiaries and affiliates.
 Particle Reinjection in External Flows

The solution can be saved only once at the end of the calculation (Final solution) or at fixed intervals
during the iterative solution process. When saving the solution every N iterations, the solution file is
either overwritten (Overwrite), or saved in numbered files (Do not overwrite). It is usually wise to save
the solution every 40-50 iterations when working on large projects so that the work is not completely
lost in case of computer malfunctions.

5.6.1. Solution Files with SLD

When running SLD conditions with Splashing and bouncing → By body force (See Splashing and
Bouncing by Body Force (p. 126)), an additional intermediate droplet file [Link] will be
saved for each diameter in the distribution when the change in total collection efficiency drops below
the level of the Activation trigger and the Delay number of iterations have elapsed, just before body
forces are computed. This file contains the droplet solution without body forces and can be used to
restart the calculation or to compare the surface impingement distribution with and without body
forces.

5.7. Particle Reinjection in External Flows

Crystals that impinge on cold surfaces of the aircraft will bounce and may collide with downstream
components, such as air data probes, or be ingested by the engine. Similarly, supercooled large droplets
(SLDs) can splash and bounce and partially or completely re-enter the flow stream as ejecta. To calculate
possible reimpingement due to such events, the Particle reinjection option can be enabled. This option
first executes a standard DROP3D run and the solution is saved as the primary solution. Next, reinjection
calculations track the particles (droplets or crystals) that rejoin the airflow from the primary impact
points. Particles may bounce multiple times before finally sticking to a wall or leaving the computational
domain. Final DROP3D solution file, droplet or crystal, contains a combination of the primary and all
reinjection solutions.

For reinjection calculations, wall boundaries where particles are re-emitted are temporarily converted
to inlets. The boundary conditions for velocity, concentration, and droplet size are determined using
crystals bouncing models for crystals and post-processing models for SLDs. Number of subdivisions
setting splits the collective reinjecting wall facets into separate inflow boundaries, to individually track
secondary particle flow for each. Splitting the secondary flow analysis helps prevent coalescence of
Eulerian particle tracks and increases the fidelity of the simulation. In case of SLDs, all wall boundaries

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 167
DROP3D - Droplet and Ice Crystal Impingement

will be included in reinjection analysis. For crystal reinjection, the user has to activate which walls to
reinject from. Only cold walls should be enabled for crystal reinjection where it is guaranteed that no
crystals can stick due to wall heating or possible water runback.

A stream of particles may bounce off a series of surfaces, requiring an iterative approach to compute
new impingement areas and calculate subsequent reinjection streams. Once all subdivisions are analyzed,
the next reinjection loop begins. The maximum reinjection loops is a user input. When total reinjecting
mass falls below 1% of primary water catch, the reinjection iterations will stop automatically.

The primary droplet and crystal solutions are saved in [Link] and [Link] files in the
simulation directory. In the reinjection phase of the calculations, the results from subdivisions are merged
into a composite file one by one after completion and saved to the disk with the standard names of
crystal and droplet. These composite files are the final output of the simulation which are meant to
be used with ICE3D or CHT3D for icing and IPS analyses. The execution can be stopped using the Stop
button on the GUI panel, and the composite file will contain the data from the latest completed subdi-
vision at the current reinjection iteration. At this time, restarting the simulation from this file to continue
the reinjection process is not possible, but will be added in later releases.

5.7.1. Crystal Reinjection in External Flows

Crystal sticking and collection on surfaces is a function of their melt fraction and the water film cov-
erage of the surface they are impinging on. In a standalone DROP3D calculation the surface film dis-
tribution is not available and it is not possible to properly decide if crystals can stick or not. In external
reinjection simulations, crystals are set to fully bounce on reinjection-enabled walls. Therefore, crystal
reinjection should be limited to wall boundaries that are not heated and have no possibility of having
runback water. By default, all walls are disabled for particle reinjection and the user enables select
walls to initiate the reinjection calculation. This is a safety measure not to bounce all crystals off all
surfaces where some might have the potential of sticking due to heating or water film coverage as
will be determined by ICE3D.

Cases where crystal reinjection may apply are, for example, crystals bouncing off the aircraft radome
and entering air data probes, or crystals bouncing off the unheated parts of the wing and enriching
the ICC ingested by aft-mounted engines.

Figure 5.13: Crystal Reinjection Inside a Channel. Primary Impingement Result (Left), Composite
Solution Combining Primary and Subdivision Calculations (Right).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
168 of ANSYS, Inc. and its subsidiaries and affiliates.
 The DROP3D Run Environment

5.7.2. SLD Reinjection

SLDs can splash and bounce off the aircraft and impinge further downstream where surfaces are
usually not protected for icing. The physics of the splashing and bouncing does not involve thermo-
dynamic effects and phase change and it is recommended to enable reinjection on all primary im-
pingement surfaces. Grouping wall boundaries of leading edges, nacelles, etc. can help reduce the
total number of subdivisions that will have to be solved during a reinjection iteration. The reinjection
boundary conditions for SLDs are determined using the SLD-by-post-processing models:

5.8. The DROP3D Run Environment

The job is ready to be submitted to the execution queue as soon as the configuration is completed.
Click the Run button at the bottom of the configuration window to switch to the run environment.

The configuration of the run environment is similar to that of the other solvers (See The Run Win-
dow (p. 45)), however some additional options are available to configure the execution of the runs in
sequence or in parallel if a droplet distribution has been specified. Go to the Sweep panel of the run
environment to access the additional options.

It is possible to restart the computation of each diameter of a distribution from the previous one by
selecting the Previous diameter option in the Restart mode pull-down menu under the Run settings

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 169
DROP3D - Droplet and Ice Crystal Impingement

section. This option may not necessarily result in faster convergence, since the trajectories of the droplets
are a function of their diameters. A diameter changes the trajectories, the extent of the shadow zones
and overall convergence.

If the number of CPUs per run is an integer fraction of the maximum number of CPUs, the jobs will
execute in parallel. For example, if the number of CPUs per run is set to 8 and the total is 16, 2 jobs
will run in parallel in the same queue until all diameters have been computed. The restart solution,
however, will be taken from a job that has already completed, not from a currently executing run. A
weighted average of the solutions for each diameter will then be automatically computed at the end
of the execution.

Check the Run in separately queued jobs box to run several droplet diameters in separate queues.
This option is offered to take advantage of multiple queues with small number of processors. The
solutions, however, will not be combined automatically at the end of the execution, the combine
utility must be executed manually.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
170 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 6: ICE3D - Ice Accretion and Water Runback
The following sections of this chapter are:
6.1. Governing Equations
6.2. Icing Model
6.3. Icing Conditions
6.4. Boundary Conditions
6.5. Screen
6.6. Solver
6.7. Output

This chapter describes the input parameters of ICE3D, the ice accretion and water runback module of
the FENSAP-ICE package. See Create a New Run (p. 19) on how to create a new ICE3D run. The run
name can be assigned in the New run name box at the bottom of the solver selection window, or re-
named after the run has been created.

6.1. Governing Equations

The next figure shows the heat and mass transfer phenomena modeled when solving for ice accretion
and runback. On each solid surface, the contamination caused the by impinging droplets is modeled
as thin liquid film. The film may run back, forced by the shear stresses created by the airflow, by a
centrifugal force, or by gravity. The height of the liquid film is to be determined at all grid points on
the solid surfaces. Based on the surface thermodynamic conditions, part of the film may freeze (ice ac-
cretion), evaporate or sublimate.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 171
ICE3D - Ice Accretion and Water Runback

The velocity of the water film is a function of the coordinates x=(x1,x2) on the surface and y (normal)
to the surface. The problem is simplified by introducing a linear profile for the film velocity (x,y),
normal to the wall, with zero velocity imposed at the wall:

where , the air shear stress, is the main driving forces for the film. This assumption is justified by
the thin film thickness, seldom greater than 10 μm in icing or anti-icing simulations. By averaging the
film velocity across the film thickness, a mean velocity can be derived as follows:

ICE3D solves a system of two partial differential equations on all solid surfaces. The first equation ex-
presses mass conservation:

where the three terms on the right hand side correspond, respectively, to the mass transfer by water
droplet impingement (source for the film), by evaporation and by ice accretion (sinks for the film).

The second partial differential equation expresses conservation of energy:

where the first three terms on the right hand side model the heat transfer generated by the impinging
supercooled water droplets, by evaporation and by ice accretion. The last three terms are the radiative,
convective and 1D conductive heat fluxes.

The coefficients are physical properties of the fluid and of the solid,
specified by you.

The reference conditions are airflow and droplets parameters specified by you.

The local wall shear stress and the convective heat flux should be supplied by the flow solver.

DROP3D provides local values of the collection efficiency β and droplets impact velocity .

The evaporative mass flux is recovered from the convective heat flux, using a parametric model.

is the anti-icing heat flux obtained from C3D for wet air calculations.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
172 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

Three unknowns remain to be computed: the film thickness , the equilibrium temperature at the
air/water film/ice/wall interface and the instantaneous mass accumulation of ice .

Compatibility relations are needed to close the system of equations. Based on physical observations,
one way to write them is as follows:

These inequalities ensure that the model predicts no liquid water when the equilibrium temperature
is below the freezing point (0˚C), and that no ice forms if there is film that is above 0˚C.

Note:

Ice can still form even if the local surface temperature is above freezing due to evaporative
cooling of ice/water mixture.

The governing equations are formulated for curvilinear two-dimensional surfaces embedded in three-
dimensional geometries. The boundaries of the three-dimensional mesh at the air-structure/ice shape
interface are denoted as the 3D surface mesh. From the surface mesh, a 3D dual surface mesh is auto-
matically obtained by connecting the mid-edges of the cells to cells' centroids. The discrete equations
are then solved with the finite volume method on this dual mesh.

6.2. Icing Model

This section allows the configuration of the input files and the various options pertaining to the selection
of the various icing models provided by ICE3D.

6.2.1. Grid and Air/Droplets Solution Files

The grid and air/droplets/crystals solution files should be selected before setting up the input para-
meters since some of these, for example boundary conditions, which are grid-dependent. Activate

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 173
ICE3D - Ice Accretion and Water Runback

the check box Vapor solution and assign its file if you would like to use DROP3D-calculated local
surface vapor pressure in your ICE3D computation.

The grid file should be assigned using the grid icon in the run window, however it can also be assigned
in this window. The grid file is then read to detect any changes to the boundary conditions.

Note:

To use vapor solution for icing computations, air solution must be obtained with adiabatic
walls and include EID.

6.2.2. Restart Conditions

ICE3D can be restarted from a previous [Link] displaced ice grid file and corresponding swimsol
solution file. Click in the Restart file box and use the browse window to assign the grid and solution
file.

Alternatively, right-click in the ICE3D configuration icon in the run window, select Options in the
menu and chose the Use restart solution option.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
174 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

[Link]. Glaze Ice

Select the option Glaze - Advanced in the Ice - Water model section to solve the three governing
equations and integrate the glaze ice accretion in time. In this case, both the shear stress and heat
flux from the air solution should be provided.

FENSAP computes heat fluxes in two different manners: Classical, which is based on temperature
gradients on the walls, or Gresho, which is based on Gresho’s Consistent Galerkin formulation. Select
either one of these two flux types in the Heat flux type box. Both Classical and Gresho fluxes are
2nd order accurate and should give very similar results. However, Gresho fluxes can exhibit some
oscillations if the surface grid is uneven or coarse. For accurate heat fluxes, the recommended
boundary layer grid spacing is: first element size 1e-6 m chords of an airfoil, with a growth ratio of
1.1.

[Link]. Rime Ice

In the special case of very low temperatures and low speeds, when the reference stagnation tem-
perature is well below freezing, the ice accretion problem can be simplified with the Rime ice option,
in which case all droplets are assumed to freeze on impact (no runback).

The energy equation is not solved and the wall temperature remains at the recovery temperature.
In this case, no files need to be assigned for the shear stresses and heat fluxes.

[Link]. Water Film

In the special case of stagnation temperatures much higher than freezing, where no droplets are
expected to freeze on impact (runback only), select the Water film option.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 175
ICE3D - Ice Accretion and Water Runback

This option is useful for solving surface water flow problems.

6.2.3. Extended Icing Data (EID) in ICE3D

In the previous versions of FENSAP-ICE, EID fields were found in a supplementary flow solution file
called [Link] which is discontinued since version R18.2. EID fields are now appended to the
existing soln air solution file to reduce file clutter and to streamline the setup process. However, to
maintain backward compatibility with flow and EID solutions computed with prior versions of FENSAP-
ICE, a legacy EID mode is made available. If possible, you should update the old flow solutions with
the latest version of FENSAP-ICE.

[Link]. EID Setup for Versions Starting with R18.2 and Forward
If the air solution file provided to ICE3D contains the EID fields, ICE3D automatically invokes the
EID functions. There is no additional settings in the ICE3D configuration regarding EID. This contrasts
with ICE3D versions prior to R18.2 where EID was found in [Link] files and a check box
had to be activated to instruct ICE3D to use EID.

[Link]. EID Backward Compatibility with Pre-R18.2 Flow Solutions

The legacy EID workflow still requires you to have an isothermal solution and a completed EID run
from an older FENSAP-ICE version to set-up an icing EID simulation.

1. Set up an ICE3D or ICE3D-TURBO run by clicking the new run icon:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
176 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

2. Drag and drop DROP3D/DROP3D-TURBO configuration icon to the ICE3D/ICE3D-TURBO config-

uration icon. Ensure that an isothermal airflow solution is being used as the airflow input solution.

3. To define a [Link] file that contains the EID fields, right-click the config icon and go
to Options → Use [Link] - legacy EID.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 177
ICE3D - Ice Accretion and Water Runback

A [Link] icon appears next to the config icon. Double-click the icon to define the relevant
[Link] file.

4. Double-click the config icon. In the Model panel, go to the Use Extended Icing Data option
and select Enabled to ensure that EID data is going to be used in the icing calculation.

6.2.4. Concavity Check

The Volume - Based growth model supports a concavity check algorithm to help prevent the ice
surface mesh from folding during growth. A minimum angle between the node normal and the adjacent
faces can be enforced. The artificial displacement added to a surface grid node by concavity fixing is
limited to maximum physical displacement of neighboring grid nodes. Pre-existing concave parts of
the mesh will not be artificially displaced if there is no icing taking place in the surrounding nodes.
This option should always be turned on (default).

6.2.5. Sand-Grain Roughness Output

When the Beading model is activated, a sand-grain roughness distribution is computed over the
contaminated surfaces to model the roughness of the frozen ice beads. The roughness distribution
is a function of location as well as ice accretion time. The roughness distribution greatly affects the
surface heat fluxes and shear stresses, and therefore has a considerable impact on the quality of the
final ice shape in multishot calculations. The surface sand-grain roughness distribution is automatically

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
178 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

written to the [Link] file when beading is enabled. The [Link] file will then
be read automatically by FENSAP at the beginning of the next shot.

Note:

When the Beading model is selected, the sand-grain roughness output is automatically
activated.

6.2.6. Impact of Beading

ICE3D assumes the presence of a continuous film of water when glaze conditions exist on the con-
taminated surface. Experimental evidence however indicates that when droplets impact on a surface
they tend to form beads that grow in time before running back and freezing as nearly-hemispherical
ice caps.

The Beading model can predict sand-grain roughness height on the surface caused by moving and
freezing beads. The local bead height changes not only in space but also in time, therefore beading
works best as a component of an unsteady or quasi-steady simulation, since it affects the heat fluxes
and therefore the growth rate of the accreting ice.

Furthermore, the Beading model removes any empiricism in the selection of surface sand-grain
roughness and therefore considerably enriches the level of physical modeling and simulation accuracy
obtainable with ICE3D.

To select this model, choose Activated in the Beading box. The Beading model is only available in
the Glaze - Advanced mode. The surface sand-grain roughness distribution file [Link],
used by FENSAP to simulate variable surface roughness, can be written by choosing Roughness
output: From beading in the Icing model menu shown in Sand-Grain Roughness Output (p. 178).

Note:

This option completely eliminates the guesswork of selecting the appropriate roughness
height and dramatically improves the accuracy of multishot calculations.

To take advantage of the roughness output from beading, multishot calculations are ne-
cessary in order to make use of this roughness distribution for the next shot.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 179
ICE3D - Ice Accretion and Water Runback

6.2.7. Crystal Bouncing Models

The ice crystal bouncing models determine the amount of crystals that contribute to the icing calcu-
lation. There are two options available.

[Link]. NTI Bouncing Model

The model can be accessed in the Model panel of ICE3D when a crystal solution is present. The
NTI bouncing model determines the amount of crystals that stick based on local surface conditions,
such as impact velocity, crystal size and film height. The model also includes an optional feature
to account for crystal erosion effects on ice accreting surfaces.

[Link]. NRC Bouncing Model

The NRC Model calculates the sticking fraction based on the liquid water content to total water
content (LWC/TWC) ratio hitting the surface. The model can be selected by choosing the NRC
Bouncing Model option in the Model panel of ICE3D.

Note:

The Crystal erosion is an option only available within the NTI bouncing model.

[Link]. Custom Bouncing Model

The Custom bouncing model is a feature developed to provide flexibility for you to define their
own sticking fraction within the crystal icing framework. The model requires you to create a User
Defined File (UDF) that calculates the sticking fraction at each nodal location on the surface
grid. The language syntax for FENSAP-ICE UDF’s can be found in UDF Syntax (p. 181). The model
can be selected by choosing Custom Sticking Model option from the Model panel of ICE3D.

[Link]. User Defined Functions

Selecting the Custom Sticking model allows you to construct a sticking fraction for crystals impacting
a surface. Once created, the UDF must be chosen in the User Defined Functions section in the
Model panel.

Note:

UDF template files can be found in the fensapice/data/udf directory of the FENSAP-
ICE installation directory.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
180 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

[Link]. Variables
Constants that are used in the UDF file can be defined by adding a checkmark next to the Variables
option. For example, ASPECT_RATIO, a variable that defines crystal geometric properties can be
added and assigned a static value as follows:

[Link]. UDF Syntax

A small program is prepared by you in a text file. The program runs on each node, with each iteration
of the simulation ICE3D.

Different physical variables (velocity vectors, crystal and droplet concentration, normal surface
vectors) are already available to you and can be used if desired. The language defining the UDF is
made of simple expressions close to the C language.

The basic rules are:

• A line beginning with # is a comment and will be ignored

• Each expression must be terminated with a semicolon (;)

• An arbitrary number of spaces and empty lines can be used

• All variables are floating point (double precision)

• Local variables can be declared, the declaration syntax requires a @, the structure is a statement:
@VARIABLE = VALUE;

• The program must end with a return 0

An expression is a combination of basic arithmetic operators

With the following additions

: Power

: Modulo, floating point

Logical operators are

The digital logic operation result is 0 (false) or 1 (true).

Priority between operators is similar to C language. Parentheses can be used freely and are preferable
to make the code less ambiguous.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 181
ICE3D - Ice Accretion and Water Runback

Math

sqrt () cos () sin () tan () acos () asin () atan () atan2 (,) exp
()

Trigonometric functions use radians.

Values

fabs () - absolute value

min(val1, val2) – minimum of value 1 and 2

max (val1, val2) – maximum of value 1 and 2

round ()

floor ()

ceil ()

sqrt ()

cos ()

sin ()

tan ()

acos ()

asin ()

atan ()

atan2 ()

exp ()

Utilities

print ( "Text") print (val)

File Access

fileData1D (value, "filename")

You can use this feature to interpolate within values contained in a file. The file contains two
columns. The call to fileData1D returns an interpolated value in the 2nd column, by providing
a value contained within the range of the 1st column.

This can be used to represent experimental data curve or function too complex to be easily defined
with an equation.

File format for fileData1D:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
182 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

npoints

variable value

variable value

variable value

variable value

Example 6.1: fileData1D File Format

0.5 291.75

0.6 293.4

0.73 295.9935

0.88 299.616

1.2 309.6

Given a value of 0.55, fileData1D(0.55,"[Link]") returns 292.595 based on linear interpol-

ation of values corresponding to 0.5(291.75) and 0.6(293.4)

[Link]. Error Handling

When starting ICE3D, the UDF will be read and syntax will be checked. If the syntax is invalid, ICE3D
will stop and a message like the following will be visible in the execution log.

Expression syntax error: invalid operands

ERROR: execution error

To identify a problem in writing the program, it is suggested to review the problematic lines to
isolate it.

To check the steps of the calculation, it is possible to display the calculated values in the UDF using
the print () function. Since the program is being executed on each node at each iteration (and
each CPU), it is better to debug using 1 CPU and a smaller mesh.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 183
ICE3D - Ice Accretion and Water Runback

Example 6.2: Calculation of Steps

@REI = DENS *VELMAG*DIAM / MU_A;

print ( "REI value:");

print (REI);

Would print for each evaluated node:

PRINT: "REI Value" (string)

PRINT: 57.4614 (float)

PRINT: "REI Value" (string)

PRINT: 57.2643 (float)

[Link]. UDF Template

This example is based on 2014 NRC sticking model:
# CUSTOM UDF TEMPLATE FOR COMPUTING STICKING FRACTION
# DIMENSIONAL VARIABLES THAT CAN BE USED
# CRYSTALS
# -------------
# ICC - LOCAL CRYSTAL CONTENT (kg/m3)
# LWC - LOCAL LIQUID WATER CONTENT (kg/m3)
# TWC - LOCAL TOTAL WATER CONTENT (kg/m3)
# XVEL - DIMENSIONAL CRYSTAL VELOCITY X
# YVEL - DIMENSIONAL CRYSTAL VELOCITY Y
# ZVEL - DIMENSIONAL CRYSTAL VELOCITY Z
# DIAM - ICED DIAMETER/SIZE
# NORMX - SURFACE NORMAL X
# NORMY - SURFACE NORMAL Y
# NORMZ - SURFACE NORMAL Z
# CONSTANTS
# ----------------
# VELINF - REFERENCE FREESTREAM VELOCITY
# INPUTS FOR NRC STICKING FRACTION
# ------------------------------------------
# NFACT - 2016 NRC COEFFICIENT
# KPOWER - EROSION FUNCTION COEFFICIENTS
# LPOWER - EROSION FUNCTION COEFFICIENTS
# CONSTA - EROSION FUNCTION COEFFICIENTS
# CONSTB - EROSION FUNCTION COEFFICIENTS
# NSTAG - STAGNATION STICKING EFFICIENCY(INTERPOLATED FROM FILE INPUT)
# REQUIRED OUTPUTS
# ----------------------------
# STFRACTION - STICKING FRACTION FOR CRYSTALS
@PI = 3.14159265359;
@RATIO = LWC/TWC;
#STAGNATION POINT STICKING EFFICIENCY
#-------------------------------------
@NSTAG = fileData1D(RATIO,"nrc_stick.txt");
#ANGLE BETWEEN SURFACE NORMAL AND IMPACT VELOCITY
#------------------------------------------------
@VNORM = (XVEL*NORMX + YVEL*NORMY + ZVEL*NORMZ);
@VELMAG = (XVEL^2 + YVEL^2 + ZVEL^2)^0.5;
if( VNORM < 0.0 ) {
VNORM = -VNORM;
};
@PSI = acos( VNORM/VELMAG );
#2014 NRC STICKING FRACTION COEFFICIENTS

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
184 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

#---------------------------------------
@KPOWER = 0.0;
@LPOWER = 1.5;
@SINFAC = 1.0;
@CONSTA = 1.0 - NSTAG;
@CONSTB = 0.578/VELINF^LPOWER;
# FLUX REDUCTION FACTOR
#-----------------------------------
if( TWC <= 0.004 ) {
@A_F = 0.0;
}
else if( TWC <= 0.012 ) {
@A_F = -0.1425 + 47.292*TWC - 1979.167*TWC^2;
}
else {
@A_F = 0.140;
};
#EROSION REDUCTION FACTOR DUE TO FLUX INTERFERENCE
#-------------------------------------------------------------------------------
@EROFACT = 1.0 - A_F*sin(PSI);
if(EROFACT < 0.86 ){
EROFACT = 0.86;
};
if(EROFACT > 1.0 ){
EROFACT = 1.0;
};
#EROSION FUNCTION
#----------------------------
@EROFUNC = SINFAC*( CONSTA*(VELINF*cos(PSI))^KPOWER + CONSTB*(VELINF*sin(PSI))^LPOWER );
#STICKING FRACTION
#---------------------------
STFRACTION = 1.0 - EROFACT*EROFUNC;
return 0

6.2.8. Body Forces

Two different types of body force can be applied during simulations.

[Link]. Effect of Gravity

The impact of gravity can be added to the water film velocity. To do so, select Gravity in the list
of body forces.

Enter the components of the gravity vector in the body force window. Select None to neglect the
impact of gravity (typical of most icing applications).

Click the display icon to display the gravity vector in the graphical window. Click again on the
icon to remove the gravity vector from the graphical window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 185
ICE3D - Ice Accretion and Water Runback

[Link]. Rotating Frame of Reference

For ice accretion in a rotating frame of reference, select the Rotation speed option in the Body
forces section. See Rotating Frame of Reference (p. 66) for more details.

The three components of the rotation speed Ω used for the airflow and droplet calculation should
then be entered in the appropriate boxes.

If at least one of the three components is non-zero, a reminder that the frame of reference has
been switched to Relative will appear at the bottom of the window.

Note:

If the ICE3D config file is initialized by dragging & dropping the DROP3D config file over
it, the rotational components will be initialized automatically.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
186 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

6.2.9. Ice Shedding on Rotating Components

[Link]. Introduction
Rotating components, such as engine spinners, fan blades, propeller blades and helicopter rotors
can undergo ice shedding where strong centrifugal forces on the ice can eventuallyreach a critical
point, overcoming adhesive forces between ice and the surface.

Ice can crack and detach from a surface according to different failure modes. The adhesive failure
mode involves the detachment of the entire ice layer from the surface, while the cohesive failure
mode begins with the formation of a crack, followed by the fracture and delamination of an isolated
ice piece within the ice layer. This section will focus on the modeling of ice shedding in a mixed
failure mode that accounts for both adhesive failure at the ice-metal interface as well as cohesive
failure within the ice volume subject to centrifugal loads.

[Link]. Ice Shedding Model in ICE3D

The ice shedding model is provided within ICE3D or ICE3D-TURBO. It is activated by enabling the
Delamination and Cracking option in the model panel of the run. ICE3D evaluates the shedding
of ice by automatically interfacing the ice accretion to an internal stress calculation in the ice volume.
The stress solver is triggered at the solution output write-out interval specified by the user.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 187
ICE3D - Ice Accretion and Water Runback

During the stress calculation, the crack propagation and determination of shed fragments, their CG
positions as radii, mass and ice remaining are determined. Centrifugal forces in the ice must overcome
aerodynamic, adhesive and cohesive stresses for the ice to shed. A flowchart of the entire process
within the ICE3D calculation has been shown in the figure above.

[Link]. Ice-Surface Interface

The adhesive strength of ice to the accreting surface depends on the type of surface defined in the
Ice-Surface interface options.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
188 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

Ice-Aluminum, Ice-Steel and Custom adhesive strengths can be defined. Ice-Aluminum and Ice-
Steel average values are based on available literature.

Ice aluminum 0.3 MPa

Ice steel 10 MPa

The interface model also includes a functional dependence with surface temperature, as adhesion
strength is known to vary with temperature. For example, the adhesive tensile strength of steel to
ice with respect to surface temperature is:

A Custom UDF adhesive strength can also be defined. A template file with thermally varying normal
and shear adhesion has been defined below:

In addition to the adhesive strength, the aerodynamic forces due to pressure and shear, as well as
body forces due to centrifugal forces are used in a force balance calculation to determine if ice
delaminates off the surface.

Note:

UDF template files can be found in the fensapice/data/udf directory of the FENSAP-
ICE installation directory.

# CUSTOM UDF TEMPLATE FOR COMPUTING STICKING FRACTION

# DIMENSIONAL VARIABLES THAT CAN BE USED
# SURFACE PARAMETER INPUTS FROM ICE3D
# -----------------------------------------------------------
# TEMP - LOCAL ICING SURFACE TEMPERATURE (Celsius)
# XCOORD - X COORDINATE (m)
# YCOORD - Y COORDINATE (m)
# ZCOORD - Z COORDINATE (m)
# RADIUS - RADIAL COORDINATE (m)
# THETA - THETA COORDINATE (degrees)
#
# REQUIRED OUTPUTS TO ICE3D
# -----------------------------------------
# FADHES_N - TENSILE ADHESIVE STRENGTH ( Pa )
# FADHES_T - SHEAR ADHESIVE STRENGTH ( Pa )
# ADHESIVE ICE-INTERFACE STRENGTH TEMPLATE
# -----------------------------------------------------------------
FADHES_N = 0.0;
FADHES_T = 0.0;
if( TEMP <= -10.5 )
{
FADHES_N = 1000*(-TEMP + 450.0);
FADHES_T = FADHES_N*0.181140;
}
else if( TEMP <= 0.0 )
{
FADHES_N = 1000*(-40.0*TEMP + 60.0);
FADHES_T = FADHES_N*(0.000070*TEMP^3 + 0.0006*TEMP^2 - 0.0147*TEMP + 0.0242);
};
return 0

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 189
ICE3D - Ice Accretion and Water Runback

[Link]. Crack Detection Criteria

The displacement of the ice structure can be described by the Cauchy-Navier equation:

where are the components of the displacement vector and is the resultant body force on the
ice due to centrifugal forces. The two parameters and are determined by Young’s modulus
and Poisson’s ratio .

The displacement on each node allows the calculation of 6 stress tensors in the element:

The stress tensors can then be used to evaluate the maximum principal stress in the element.
There are two options: Principal Stress or Fracture toughness to evaluate potential cracking in
the ice structure.

The Principal stress option uses the user defined cohesive tensile strength of ice to select elements
for cracking.

Fracture toughness is also provided as an option and is used to evaluate a criteria to compare the
calculated principal stress:

Where is the work of fracture, is the user defined fracture toughness and is the character-
istic length of the element. In general, fracture toughness is used for ductile materials.

Cracking occurs if the calculated maximum principal stress in an element exceeds the critical stress

Principal stress is the preferred method over fracture toughness for ice crack propagation simulation,
as ice is a brittle material that exhibits a low-strain rate.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
190 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Model

[Link]. Ice Material Properties

For the ice shedding model, ice is assumed to be an isotropic solid material with mechanical
properties within the linear elastic regime during in-flight icing encounters. The ice properties
shown below are based on average literature values and maybe changed if user data is available.

[Link]. Shedding Evaluation and Outputs

The out panel in ICE3D allows the user to control the frequency of the shedding analysis through
the Shedding every printouts option. The user can specify the shedding interval as a multiple of
the time between solution printouts. For example, if the Time between solution output of 1 second
and Shedding every 10 printouts is specified, then the shedding analysis is carried out every 10
seconds.

The user is encouraged to activate the Numbered output files option to see how the shedding
ice solution evolves with time. The following shedding files will be produced as outputs during the
calculation:

• [Link] - ice solution file post-shed

• [Link] - ice grid file post-shed

• max_ice_shed_piece.grd – largest ice volume that shed in the time period

• [Link] – No. of fragments that shed, mass of each fragment, COG radial distance from
centerline for each shedding instance

The View and View Ice buttons in the execution panel of the ice shedding run allow users to view
the shed solution files:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 191
ICE3D - Ice Accretion and Water Runback

6.3. Icing Conditions

To guarantee the correct simulation of ice accretion, the reference conditions must be identical to those
of the airflow and droplet solutions.

6.3.1. Reference Air and Droplets Conditions

These reference conditions are used to link the ICE3D calculation to its corresponding air and droplet
solution. Enter the reference characteristic length , freestream air velocity , freestream static air
temperature and air static pressure . The values must be identical to those used for the airflow
and droplet calculations.

The reference pressure can also be computed from the altitude. To do so, click Air static pressure
and select Altitude. ICE3D automatically computes the pressure based on the U.S. Standard Atmosphere
(1976).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
192 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Conditions

ICE3D also computes the reference air Reynolds and Mach numbers for verification purposes. These
two non-dimensional numbers should be identical to those computed for the air solution.

The reference conditions are also used to link the ICE3D calculation to its corresponding droplets
solution. Enter the reference Liquid Water Content LWC ( ) and diameter, .

Important:

The Air static temperature is used by ICE3D only to convert the heat fluxes from the airflow
solver into convective heat transfer coefficients. It is NOT the temperature at which the
icing simulation is performed. The icing simulation is conducted at the Icing air temper-
ature, which most of the time is the same as the Air static temperature. These two tem-
peratures, when used judiciously, permit the simulation of different icing conditions using
a single air solution.

[Link]. The Recovery Factor

The Recovery factor is used to introduce the effect of the energy losses due to friction when
computing the total temperature from the static temperature and the Mach number:

is set to unity by default, implying that the surface temperature is the stagnation temperature
computed from freestream conditions. A recovery factor less than unity implies that:

The heat fluxes from FENSAP are converted into convective heat transfer coefficients using the re-
covery reference temperature.

The convective heat transfer coefficient is multiplied by the recovery ice temperature in the energy
balance equation.

Good judgement should be used when setting a value of recovery factor less than unity. An empir-
ical formula to compute a value for the recovery factor on a flat plate is:

where is the laminar Prandtl number. This formula yields for

6.3.2. The Icing Parameters

This section provides more information regarding two crucial parameters: the Icing air temperature
and Ice density.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 193
ICE3D - Ice Accretion and Water Runback

[Link]. The Icing Air Temperature

The Icing air temperature is the static temperature at which ice accretion is computed. In general
cases, this is the temperature of the incoming droplets. In most cases it is the same as the Air
static temperature in the Reference Conditions section, but experienced users can set it to a
different value to study the effect of temperature on ice accretion without changing the airflow
solution. It is transformed automatically by the graphical interface to the recovery temperature at
which the icing calculation is performed. The recovery temperature depends on the recovery factor
(See The Recovery Factor (p. 193)).

Note:

For internal flows and turbomachinery icing simulations, icing air temperature variation
is not a recommended method to study different icing conditions. In such cases, even
the reference temperature setting may not reflect the inlet air static temperature. Internal
icing cases are best simulated using particle thermal equation, vapor transport, and
adiabatic-wall air flow solutions with EID enabled.

[Link]. Fluid Properties

Water and ice are the default media, and their thermodynamic characteristics are automatically
supplied to ICE3D. To select another fluid/solid media combination or to select different properties
for water and ice, select the Advanced option. This gives access to the fluid properties menu.

[Link]. Relative Humidity

The relative humidity is expressed as a percentage value. For clouds, this value should be set to
100%. Otherwise, enter the relative humidity of the icing tunnel, as determined during the experi-
ment. If a vapor solution is provided, this option is not required and will be greyed out. To facilitate
the use of a wet bulb temperature setting to figure out the relative humidity for the icing air tem-
perature, one can click on the Twb … button to the right of the Relative humidity % value box
and enter the wet bulb temperature in Kelvins:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
194 of ANSYS, Inc. and its subsidiaries and affiliates.
 Icing Conditions

This function calculates the saturation vapor pressures at specified wet bulb temperature and icing
air temperature, from the empirical formula found in D.M. Murphy and T. Koop, Review of the vapor
pressure of ice and supercooled water for atmospheric applications, 2005, Quarterly Journal of the
Royal Meteorological Society. The temperature range for which this function is valid is 123 – 332K.

[Link]. Radiation
The skin emissivity indicates whether radiation effects are taken into account by ICE3D (black body,
or 1.0). If not, enter a low emissivity (1.e-8 for example).

[Link]. Ice Density

Ice density can be set to:

• A constant value (the default value for ice is 917 kg/m3). This option should be used to compare
ICE3D results with other ice accretion results obtained with a fixed ice density.

• Based on the Macklin formula:

for 0.2 < RM < 170

where

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 195
ICE3D - Ice Accretion and Water Runback

is the droplet diameter in microns, is the droplet impact velocity, in m/s and is the
wall temperature from ICE3D, in degrees Celsius.

• Based on the Jones (glaze) formula:

(in g/cm3)

[Link]. Appendix C
See Appendix C (p. 135) for more information.

6.3.3. Advanced Settings

This section is required when running ICE3D in Conjugate Heat Transfer simulations (wet-air CHT3D)
for complex geometries such as piccolo tube applications for aircraft anti-icing and jet engine nose
cones, where the hot inner and cold outer airflow domains are connected but have distinct domain
indices. In these cases the outside reference air conditions are ill-suited for the ICE3D evaporation
model, which will also be required over the walls of the hot inner chamber.

To enable this option, click the Hot chamber reference evaporation conditions check box.

The Jet reference static temperature is the static temperature of the jet. The Jet effective static
temperature is normally also the jet static temperature, but it can be varied to study the effect of
different jet temperatures on the effectiveness of the IPS without recomputing the airflow solution.
Velocity is the jet velocity and Relative humidity is the relative humidity of the hot air jet.

6.4. Boundary Conditions

No specific boundary conditions are required for ICE3D, except for sink boundaries. Exits will automat-
ically apply a flow-through condition where the water is free to leave the domain and ice displacement
can take place if there is any icing on the corresponding exit nodes.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
196 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

6.4.1. Sink Boundaries

Although ICE3D can automatically remove the water film in regions where water pooling may occur,
such as trailing edges, wing tips, etc., in some cases it may be necessary to specify a sink boundary
condition manually.

To remove water locally, a sink can be associated to multiple wall boundary conditions (See FENSAP-
ICE File Formats (p. 393)). The sink is applied to all faces of that particular boundary.

6.4.2. Rotating Spinners

To account for rotation on rotating surfaces of revolution, such as propeller spinners and engine
center cones, a rotation boundary condition can be enabled on wall families. To use this boundary
condition, choose Enabled in the Rotation section of the selected wall family. Enter a magnitude for
the rotation rate and click apply. The axis of rotation is detected automatically and displayed in the
3D viewer panel. The direction of rotation follows the right-hand rule convention. To reverse the dir-
ection of rotation, simply add a minus (-) sign in front of the rotational velocity magnitude and click
Apply.

Note:

The flow solution for the spinner should also contain the surface rotation effects, using
the same rate and direction of rotation. If the ICE3D setup is done using the drag & drop
functionality from FENSAP and DROP3D configurations, the rotation settings in the FENSAP
run will automatically be carried over. If a different flow solver is used, then the correct
values for the rotation rate and direction should be imposed manually to match the flow
solution.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 197
ICE3D - Ice Accretion and Water Runback

6.4.3. Sliding Wall Boundaries

This option allows the additional characterization of walls on which ice accretion has been disabled
as sliding boundaries. Sliding boundaries are useful when ice accretion on one surface completely
dominates over the neighboring surfaces (the sliding boundaries). The resulting uneven ALE mesh
displacement could deform the grid to such an extent that elements become degenerate, making it
impossible to obtain a usable 3D displaced grid during multishot ice accretion (See Generate a 3D
Displaced Grid (p. 204)).

Important:

This option should be used only after careful examination of the surface collection efficiency,
to estimate whether displacement would lead to a degenerate grid, or if problems with
grid displacement have been encountered.

To use this option, click a wall boundary in the list of boundary surfaces and select the Disabled-
Sliding option in the Icing drop-down menu. ALE will then ensure that the grid nodes laying on this
wall will slide on their original surface rather than grow outward, preventing the grid from becoming
degenerate.

Figure 6.1: Nodes on the Engine Pylon

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
198 of ANSYS, Inc. and its subsidiaries and affiliates.
 Screen

Figure 6.2: Nodes on the Fuselage

6.5. Screen
FENSAP-ICE has the capability to model screens and their effect on the airflow and droplet fields by
using an internal surface 6000 BC. Wire spacing and wire diameter can be defined on the internal surface
to model the blockage formed by various screen characteristics. Furthermore, the effect of ice accretion
on screens can be simulated by calculating the increase in wire diameter based on collection efficiency
provided by the DROP3D solution. To enable screen icing, set the Type of the 6000 BC family to Screen.
Screen BCs should have a non-zero wire spacing defined so that porosity can be calculated. This spacing
should match the values set in the FENSAP and DROP3D steps to ensure consistent results. Configuring
ICE3D using a drag and drop from a DROP3D configuration will cause ICE3D to automatically inherit
the type and spacing for the screen boundaries.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 199
ICE3D - Ice Accretion and Water Runback

The screen icing model operates under the assumption that all droplets hitting the wire mesh of the
screen will freeze on contact (rime ice), therefore progressively obstructing the passages. The screen
may be subject to spatially variable rates of ice accretion, depending on local flow and droplet conditions.
The wire diameter field is calculated before the wall icing calculations take place and is saved within
the [Link] file with the timebc variable code 60. To visualize this, the original grid and the
[Link] file can be loaded within Viewmerical in TIMEBC mode.

In multishot simulations, FENSAP reads the [Link] file to take the new roughness and/or
screen wire diameter output by ICE3D. FENSAP and DROP3D take into account the new wire diameter
when calculating total pressure and LWC drop across the screen for the subsequent shots. Wire diameter
is then saved in the FENSAP soln file, which ICE3D uses as source data for the next shot.

Screen icing can also be enabled in unsteady icing when running in Combo mode, where, for each
physical air flow time step, ICE3D calculates the increase in wire diameter and provides it to FENSAP
and DROP3D for the next time step.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
200 of ANSYS, Inc. and its subsidiaries and affiliates.
 Screen

Figure 6.3: Helicopter Intake Screen

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 201
ICE3D - Ice Accretion and Water Runback

Figure 6.4: Wire Diameter on Iced Screen of a Helicopter Intake

6.6. Solver
The ICE3D module is based on an explicit time-marching scheme which requires the specification of
only two parameters.

6.6.1. Time Integration

Ice accretion is inherently an unsteady process, therefore the governing equations are integrated in
time. The process stops when the desired Total time of ice accretion (in seconds) is reached.

The time-marching procedure that governs the solution of the water film transport is subject to CFL
stability constraints. Smaller grid elements on the surface and faster film speeds will require smaller
time steps to avoid numerical instabilities. The Automatic time step option takes the guesswork out
of defining a stable time step by computing the optimal time step for each grid/film speed combin-
ation, resulting in considerable computational cost savings.

If desired, the time step can also be set manually to a specific value. In this case film fluxes will be
limited on nodes where CFL > 1 to maintain a stable run. This in turn will result in extra film being

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
202 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solver

retained on such nodes, affecting the accuracy of the solution. The difference may be significant and
you are advised to use the constant time stepping option with caution. Comparing the results of a
short duration run done with and without automatic time stepping is recommended before moving
forward with the constant time step option.

Note:

Automatic time step computes a stable and optimal uniform time step at each iteration,
which may be higher or lower than 0.001 second, depending on the problem. For example,
turbomachinery rotor blades typically have very thin leading edge elements and fast film
speeds due to the rotation. The stable time step in this case may be in the range of 1e-4
to 1e-7 second, depending on the amount of runback. Film flows on aircraft components
usually run with time steps of 0.01 to 0.1 second. Rime cases are not governed by film
flow, therefore they will remain at the default 0.001 second time step value unless the
Automatic time step option is disabled and a different time step is imposed.

Rime cases are not governed by film flow, therefore they are marched with the default
0.001 second time step value unless the Automatic time step option is disabled and a
different time step is imposed.

If the automatic time step goes below 1e-5 and icing calculations appear to take too long, a constant
time step of 1e-5 is likely to be a balanced compromise between the total run-time and solution ac-
curacy.

If the Rime option is selected as the icing model, the entire duration of icing will be done in a single
time step unless intermediate solution printout is requested.

6.6.2. Maximum Ice Thickness

The icing calculation can also be stopped when the ice accretion reaches a specified maximum ice
thickness.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 203
ICE3D - Ice Accretion and Water Runback

Select the Ice thickness option in the Stop conditions box and provide the Maximum ice thickness
value, in meters.

6.7. Output

The solution files of ICE3D can be saved in FENSAP format (See FENSAP-ICE File Formats (p. 393)). The
following files are created:

Table 6.1: ICE3D Solution Files

[Link] Surface temperature/film height convergence

information
[Link] 3D surface grid before ice accretion
[Link] 3D surface grid after ice accretion
[Link] CAD of the iced surface in ICEM CFD TETIN format
[Link] Reference/initial conditions and convergence
messages
swimsol ICE3D solution at each grid point on the wall
surfaces
[Link] Ice displacement information
[Link] Surface sand-grain roughness distribution
[Link] Reference/initial conditions and convergence
messages
[Link] CAD of the iced surface in SLD format

The solution files can be saved at intermediate time levels by setting the Time between solution
outputs. If the Numbered output files option is activated, the file numbering will follow the solution
output instances.

6.7.1. Generate a 3D Displaced Grid

ICE3D can output a 3D grid displaced by the accumulated ice on the solid boundaries. This grid can
then be used directly by the flow solver to compute performance degradation or to perform multishot
ice accretion without manual remeshing.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
204 of ANSYS, Inc. and its subsidiaries and affiliates.
 Output

To output the displaced grid file, saved in FENSAP format, select Yes in the Generate displaced grid
box. The displaced grid will appear inside the run folder, with the same name as the original 3D grid
and a .disp suffix appended to it, for example [Link].

Note:

For the volume grid displacement, ICE3D invokes FENSAP and its ALE (Arbitrary Lagrangian-
Eulerian) approach. The Default (Coupled) ALE solver mode yields a better quality mesh
near the surface compared to the Uncoupled solver mode. This is therefore the recommen-
ded grid displacement method.

If FENSAP cannot generate a displaced grid ( for example the displacement is too large or
the resulting grid has degenerate elements), load the [Link] file into ICEM CFD and
generate a new grid with the iced surface.

Tip:

For large or complex ice accumulation, the displaced grid may not be of good CFD quality.
To improve its quality, you are invited to use OptiGrid in mesh smoothing mode instead
of manual remeshing, in order to save time.

6.7.2. Compute IPS Load Requirements

ICE3D can also be used to compute the required heat flux distribution that prevents ice formation
on the walls of a geometrical model. When used in this mode, ICE3D conducts a mass and thermal
balance for two scenarios: a running wet scenario and a fully evaporative scenario. In the running
wet scenario, the required heat flux represents the minimum amount of heat flux required to maintain
a film of water at zero degrees Celsius (no ice) at each cell/element of the surface. In the fully evap-
orative scenario, the required heat flux represents the minimum amount of heat flux required to
evaporate all water droplets that impact each cell/element of the geometrical model.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 205
ICE3D - Ice Accretion and Water Runback

Figure 6.5: Running Wet Required Heat Flux Distribution over Generic Aircraft

Figure 6.6: Fully Evaporative Required Heat Flux Distribution over Generic

The required heat flux distribution provides an insight on the amount of heat/energy that an IPS (Ice
Protection System) should deliver in order to prevent ice formation over a geometrical model at a
specific in-flight icing condition.

To activate this special mode, select Compute IPS load conditions in the Options menu of the Out
panel and then press on Run to execute this simulation.

Note:

Currently, this feature only supports Appendix C type droplets. SLD or crystals are not yet
supported.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
206 of ANSYS, Inc. and its subsidiaries and affiliates.
 Output

Both running wet and fully evaporative results are stored inside a single swimsol file. Therefore,
they can be viewed with Viewmerical.

Thirteen fields are present in the swimsol file.

• Mass Caught (kg/s/m2): Mass flux of water droplets that impact on the surface of the model.

• RW Film Height (microns): Continuous water film height that satisfies running wet conditions.

• RW Evaporation MF (kg/s/m2): Mass flux of evaporation that satisfies running wet conditions.

• RW Required HF (W/m2): Required heat flux that satisfies running wet conditions

• RW Water Droplet HF (W/m2): Energy flux due to water droplets that satisfies running wet condi-
tions. This heat flux accounts for water droplet enthalpy and kinetic energy.

• RW Evaporation HF (W/m2): Heat flux of evaporation that satisfies running wet conditions.

• RW Radiation HF (W/m2): Radiation heat flux that satisfies running wet conditions

• RW Convection HF (W/m2): Convective heat flux that satisfies running wet conditions.

• FE Required HF (W/m2): Required heat flux that satisfies fully evaporative conditions.

• FE Water Droplet HF (W/m2): Energy flux due to water droplets that satisfies fully evaporative
conditions. This heat flux accounts for water droplet enthalpy and kinetic energy.

• FE Evaporation HF (W/m2): Heat flux of evaporation that satisfies fully evaporative conditions.

• FE Radiation HF (W/m2): Radiation heat flux that satisfies fully evaporative conditions.

• FE Convection HF (W/m2): Convective heat flux that satisfies fully evaporative conditions.

In addition, two heat/energy tables are printed inside the log file, [Link]. Each table reports the
thermal balance per wall family for fully evaporative and running wet conditions. Each heat/energy
source and sink satisfy the following equation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 207
ICE3D - Ice Accretion and Water Runback

Figure 6.7: Heat Tables of Fully Evaporative and Running Wet Conditions

In these tables, the first column coincides with the wall family number of the external grid. The other
columns correspond to heat/energy sources or sinks.

• Q_impinge: Energy due to water droplets enthalpy and kinetic energy change.

• Q_evap: Heat due to evaporation.

• Q_rad: Heat due to radiation.

• Q_conv: Heat due to convection.

• Q_required: Required heat to prevent ice formation.

• Q_req_ave: Average heat flux to prevent ice formation.

• Q_req_max: Maximum required heat flux to prevent ice formation.

• Area: Area of the wall family.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
208 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 7: C3D - Unsteady Heat Conduction
The following sections of this chapter are:
[Link] Physical Model
7.2. C3D Configuration
7.3. Settings
7.4. Properties
7.5. Materials
7.6. Boundary Conditions
7.7. Boundary Conditions Cycles
7.8. Numerical Parameters
7.9. Output

This chapter describes the input parameters of C3D, the heat conduction module of the FENSAP-ICE
package. The C3D module can solve heat conduction in domains consisting of several materials with
different properties.

7.1. The Physical Model

Heat conduction is an unsteady process during which heater pads are turned on and off sequentially
and heat flows through different solid materials. Heat conduction can be expressed as a partial differ-
ential equation with an added term to model phase changes:

where is the density of the solid, its specific heat, its conductivity and H is the enthalpy. The
unknown is the variation of the nodal temperature between iterations (equals 0 at convergence).

At each time step, starting from an initial temperature and enthalpy , the heat conduction equation
is solved iteratively until the new temperature

matches the temperature corresponding to the new enthalpy

A table that correlates the enthalpy with temperature T for each material must be provided by you.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 209
C3D - Unsteady Heat Conduction

7.2. C3D Configuration

The C3D run requires only the grid and configuration setup. Double-click the grid_material icon to
open the browse window and assign the grid in the same manner as in the other FENSAP-ICE modules.

The grid boundary conditions and materials will then be read. See FENSAP-ICE File Formats (p. 393) for
more information on how materials are identified in the grid. Double-click the config icon to open the
configuration window.

7.3. Settings
The initial settings for C3D affect the initial temperature and thermostat identifiers and positions, if they
are activated in the simulation.

7.3.1. Initial Conditions

Enter the initial temperature for the solid domain.

This temperature will be applied throughout the domain, for all the materials.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
210 of ANSYS, Inc. and its subsidiaries and affiliates.
 Settings

If a restart file is specified, the solution is initialized from the solution read from the file. This option
can be used to restart a computation or to continue a computation with different settings.

7.3.2. Electrothermal Model

The Electro-thermal model can be used to evaluate the resulting Joule-Thomson heating effects of
an electrical current carrying conductor. The electrical problem can be described by Maxwells continuity
equation that calculates the electric potential in a material:

The electrical problem is described by Maxwell’s continuity equation, which determines the electric
potential in a material:

where:

: Voltage potential [Volts]

: Temperature dependent electrical conductivity [S/m]

: Charge density [C/m3]

: Induced electro-motive force caused by a temperature gradient (Seebeck effect)

The heat produced electrical conduction can be described by the Joule-Thomson effect. The electric
potential gradient is used to calculate the heat generated per unit volume:

where:

: Peltier Coefficient

: Current Density Vector

The Peltier coefficient can be related to Seebeck coefficient, s, by temperature:

The equation can be then recast as:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 211
C3D - Unsteady Heat Conduction

The first term on the right corresponds to Joule heating and the second term includes both Peltier
effects at a junction between two different conductors, and Thomson effects, due to the thermal
gradient within a conductor.

Boundary conditions in terms of voltage can be specified at the terminals of an electrical conductor:

where and are the voltage potential defined at the two ends of the conducting material. Neu-
mann conditions for the current in the material are usually not specified but are computed from
the voltage potential through a conductor carrying a current:

where is the cross-sectional area of the conductor.

7.3.3. Thermostats
Double-click the Thermostats tab to define the names and positions of the thermostats. ASCII strings
can be used to define the thermostat names.

Use the Add button to create new lines. Use the Remove button to remove the last line in the group.

7.4. Properties
The density, conductivity and enthalpy properties should be defined for each material used in the
simulation. These properties can either be constant or functions of the temperature. In the latter case,
the number of temperature points should be defined, as well as the associated distribution.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
212 of ANSYS, Inc. and its subsidiaries and affiliates.
 Materials

The materials and their properties should all be defined in this section using:

Table 7.1: Defining Materials and Properties

New Add a new material.

Rename Change the name of a given material.
Duplicate Create a new material with the properties of the
previous one.
Delete Remove a material from the list.

Note:

The enthalpy is referenced at 0 °C.

Phase changes are introduced using temperature distributions. If the material is ice, which melts just
above the freezing point, the density, conductivity and enthalpy of water and ice should be given as
functions of temperature across both the solid and liquid states with substantial density, conductivity
and enthalpy jumps in a narrow range across the freezing point.

7.5. Materials
The solid object in which heat conduction occurs can be composed of many regions/layers of different
materials. Each region/layer is composed of a group of elements identified in the grid file (See FENSAP-

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 213
C3D - Unsteady Heat Conduction

ICE File Formats (p. 393)). All materials present in the grid file are listed sequentially in the Materials
window.

Click the material Name to highlight the selected material in the graphical window. For each material
ID number present in the grid file, assign a specific material and its properties as defined in Proper-
ties (p. 212). To do so, click any of the material reference name and assign the Material type in the
Material type box.

7.6. Boundary Conditions

All boundary surfaces present in the grid file are listed in the Boundary conditions panel. The boundary
conditions define the default state of walls or heaters. The heating elements should be set to zero heat
flux in this panel, indicating that they are inactive at all times, unless otherwise specified in the Cycles
panel.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
214 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

7.6.1. Walls

Two types of boundary definitions are available for wall boundaries, according to the type of problem
being solved: Thermal BC Definition and Electrical BC Definition.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 215
C3D - Unsteady Heat Conduction

[Link]. Thermal Boundary Conditions

Several types of conditions can be applied on the wall boundaries of the solid:

Table 7.2: Thermal Boundary Conditions

Nothing No specific boundary conditions are applied to

this boundary by C3D, but will be applied
automatically by other codes, such as CHT3D. In
standalone C3D operation, these boundaries will
receive an adiabatic boundary condition (q = 0)
instead.
Temperature A prescribed temperature is imposed on all nodes
of this boundary.
Flux A constant, prescribed heat flux is imposed. A
zero heat flux can be used for an adiabatic
boundary condition or a symmetry condition.
Mixed Indicates that a heat transfer coefficient h is
imposed on all surfaces of this boundary
condition family. The reference temperature must
also be specified in the Temperature box.

Boundary conditions for all surfaces other than heating pads must be assigned. When a wall surface
is selected, the BC definition box will appear.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
216 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

These boundary conditions can be set to:

Nothing: No specific boundary conditions are applied to this boundary condition index by C3D,
but will be applied automatically by other codes, such as CHT3D.

Temperature: The prescribed temperature is imposed at all nodes of this boundary.

Flux: The prescribed heat flux will be imposed on all surfaces of this boundary.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 217
C3D - Unsteady Heat Conduction

The heat flux is defined as:

where is the heat conduction coefficient and is the surface normal.

Mixed: The heat transfer coefficient (h) and the reference temperature will be imposed on all surfaces
of this boundary. In the case of a moving fluid, this heat transfer coefficient is the convective heat
transfer coefficient and the reference temperature is the recovery temperature.

This coefficient is defined as:

where is the reference temperature.

[Link]. Electrical Boundary Conditions

Several types of conditions can be applied on the wall boundaries of the conducting solid:

Table 7.3: Electrical Boundary Conditions

Nothing No specific boundary conditions are applied to

this boundary C3D.
Voltage Used to impose a prescribed voltage on all nodes
of this boundary.
Current density A constant, prescribed current is imposed. On the
external surface of a conductor, this should be
set to zero.
Internal surface Indicates a boundary that is embedded in the
mesh. It can be the interface of two different
materials, or internal to a material. In general
these do not impose a boundary condition but
are used to visualize and post-process the
solution at this location.

7.6.2. Thermostat
One thermostat can be assigned to each heating pad. Select Enabled to view more options.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
218 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions

The Thermostat can be selected from the list defined in Electrothermal Model (p. 211). The thermostat
will maintain the temperature at its location between the specified Minimum temperature and
Maximum temperature. To verify the location of the thermostat, click the on the icon to display
its position in the graphical window.

7.6.3. Heater Pads

C3D supports two heater pads models.

[Link]. Specified Heat Flux

A heat flux applied on a boundary surface. The surface must be identified by a boundary index
ranging from 6,000 to 6,999 (See FENSAP-ICE File Formats (p. 393)).

The heating pad can either be embedded inside the solid (internal surface) or located on the outer
surface. In the Boundary conditions panel the heating pad should initially be set to zero Heat
flux, indicating that is inactive by default. Its activation must be specified in the Cycle panel box.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 219
C3D - Unsteady Heat Conduction

In the Boundary conditions panel the heating pad should initially be set to zero heat flux, indicating
that is inactive by default. Its activation must be specified in the Cycle panel box. The value specified
for Heat flux in the Boundary conditions panel is a global value which will be applied as baseline
value for this heater pad, throughout the entire length of the simulation. If the heater pad flux
value is changed in the in the Cycles panel, the heater pad will use that new value for the length
of the state block.

Note:

Prior to R18.0, the heater pad values could have a single value, which was set-up in the
Boundary conditions panel. It is now suggested to set-up the heater pad in the Cycles
panel, and keep the global value to 0.

[Link]. Specified Power Density

Power density applies to a material acting as a volume heat source, as shown in white in the figure
below.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
220 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundary Conditions Cycles

This option requires the definition of the material properties for the heater pad (See Proper-
ties (p. 212)), the identification of the material as a Volume heat source (Materials (p. 213)), followed
by its Power density value. (See Boundary Conditions Cycles (p. 221)).

In this case heat conduction through the heating pad material can be simulated even when the
volume heating source is turned off.

7.7. Boundary Conditions Cycles

The unsteady solution process consists of one or more cycles, during which heating elements may be
turned on or off through changes of the boundary conditions.

To add or remove boundary condition cycles, click Add or Remove. All boundary condition cycles are
shown graphically and sequentially in the cycle bar at the top. To select one cycle, click the bar corres-
ponding to that cycle. The bar will then be highlighted in blue.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 221
C3D - Unsteady Heat Conduction

Each cycle starts at the end of the previous cycle. Set the cycle duration in the Duration box, in seconds.
The total time is then shown as the sum of all cycles.

For each cycle, set the heating element boundary conditions to be imposed. Heaters can be turned on
by clicking the On button and by imposing the corresponding heat flux. Specify the power density for
Volume heat sources (Mat). The other boundary conditions can be left as default or modified in this
menu.

7.7.1. Cycle
A Cycle defines the state of boundary conditions, heater pads or volumetric heat sources for a given
period of time. To add or remove cycles, click + or - button on the top left of the Cycle graph. Cycles
are identified with letters and can be selected in the Cycle drop box. Set the cycle duration, in seconds,
in the top right Duration box. Boundary conditions for walls, heater pads, and volumetric heat sources
can be added in or removed from each cycle by clicking the + or - button on the bottom right of the
Cycle graph. All boundary condition cycles are shown graphically.

To modify a defined boundary condition within the current cycle, click the green bar corresponding
to that object to enable editing. The bar will then be highlighted. The Start and Duration can be
toggled between seconds (s) and percentage (%). If the cycle is resized, boundary conditions set-up
in % will be rescaled to the new cycle length. The default duration type is in percentage (%) of the
cycle duration.

7.7.2. Functional Input

The heating pad Heat Flux can be set either to Constant or Function. In Constant mode, the heat
flux change is instantaneous. In Function mode, Power-on and Power-off transitions can be con-
figured. Various functions can be supplied:

Linear: The power increases from the default state to the defined power value in a linear fashion
from activation for a specified duration (in seconds or %).

Expression: The power changes according to the given expression. The expression uses the relative
time (T) variable, which is automatically set by FENSAP-ICE to 0 at the start of the power-on period

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
222 of ANSYS, Inc. and its subsidiaries and affiliates.
 Numerical Parameters

and 1 at the end. You must ensure that the expression f(T) returns 0 at the start and 1 at the end and
that 0 ≤ f(T) ≤ 1 over the interval 0 ≤ T ≤ 1.

7.7.3. Examples
Power-on functions for a 10-second activation period:

Linear: T

Power law: T^0.3

The syntax of the expression language is described in Expression Syntax (p. 411).

Note:

For Power-down, the expected values are reversed. The expression should return 1 at the
start of the power-off period and 0 at the end.

Power-down functions for a 5-second deactivation period:

Linear: 1-T

Power law: (1-T)^0.3

7.7.4. Sequence
A Sequence is a combination of one or multiple Cycles. Any sequence of cycles can be entered, with
the cycle name identifiers separated by a comma (such as A if there is a single cycle, or A,B or
A,B,A,C,C for more complex sequences). Each cycle starts at the end of the previous cycle. The
global repetition of sequences can be performed by providing the repetition number. Modify the
repetition number directly or click the up and down arrows to change it. The total time will be
automatically computed and then shown as the sum of all cycles.

7.8. Numerical Parameters

The solution of the heat conduction equation is an unsteady process therefore the time step and duration
must be specified.

The physical time step in seconds is specified in the Time step box. The solution process continues
until it reaches the final cycle time, the Total time.

Two time stepping schemes are provided in C3D: for example, Constant and Automatic modes. The
Constant mode employs a constant time step throughout the simulation whereas with the Automatic
option, the optimal time step is computed in each element from the rate of heat conduction and the
element size. With the Automatic option, the Maximum time step sets an upper bound on the auto-
matic time step to ensure that fast transients can still be captured with a reasonable temporal resolution.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 223
C3D - Unsteady Heat Conduction

7.9. Output
In Constant time step mode, the thermal solution ([Link]) and electrical solution ([Link])
of C3D are written in FENSAP format (See FENSAP-ICE File Formats (p. 393)) at set Iterations between
printouts intervals and at the end of the simulation. If the number of Iterations between printouts
is larger than the total number of time steps the solution will be printed only at the end of the simulation.

In Automatic time step mode, the thermal and electrical solutions are written at fixed time intervals
specified by Iterations between printouts. The time step may be reduced to meet the exact time
stamp. If the value of Iterations between printouts is zero the solutions will be written only at the
very end of the simulation.

7.9.1. Temperature Probes

The evolution of the unsteady solution can be monitored at specified locations in the grid (temperature
probes).

Add probes using the Add button, remove them using the Remove button. For each probe define
its X-, Y- and Z-coordinates.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
224 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 8: CHT3D - 3D Conjugate Heat Transfer
The following sections of this chapter are:
8.1. Best Practices
8.2. CHT3D Run Settings
8.3. Dry Air Regime
8.4. Wet Air Regime
8.5. CHT3D Input Parameters

The physics and thermodynamics of in-flight icing involve strong heat convection in fluids, heat con-
duction through solids, droplet impingement, surface water film flow, water evaporation, change of
phase and ice formation. Realistic simulations of these phenomena are too complex to treat within a
single computational domain. A computationally-efficient alternative consists in applying a divide-and-
conquer strategy by computing the solutions of the various domains separately and exchanging the
interface boundary conditions in an iterative manner. Convergence is achieved when the heat fluxes
and temperatures are equalized across the interfaces. This strategy also has the benefit of simplifying
the mesh generation process.

CHT3D is the module that solves Conjugate Heat Transfer (CHT) problems in either dry- or wet-air regimes
for anti-icing or de-icing simulations. CHT3D in anti-icing mode can handle up to two independent
airflow domains separated by one solid domain, usually a metallic material, however multi-layer synthetic
materials are also supported. For bleed-air applications, for example, the simulation involves cold ex-
ternal two-phase flow where wall-bound turbulence, transition, strong convection, evaporation and
phase-change dominate and a hot internal single-phase flow with strong turbulence and recirculation,
convection, and heat conduction through the thin metallic solid skin that separates the two fluid domains.
For electro-thermal unsteady de-icing problems, a single external two-phase flow domain is typically
required, but the solid is usually a multi-layered composite of synthetic materials, each with its own
material properties.

CHT3D fully supports non-matching grids, which can be constructed with any type of linear elements
and can take advantage of the most appropriate grid type in each domain. Several airflow solution
methods are supported, from the most complex full RANS with surface roughness, to the simplest
constant Heat Transfer Coefficient (HTC), where the flow solution is frozen and only the solid surface
temperature and heat fluxes are updated.

8.1. Best Practices

Before examining the details of the CHT3D module, a summary of the best practices to follow for this
kind of complex calculations is presented. Careful planning of grid construction and interface layout
and coverage is advised before proceeding to the setup of a CHT3D calculation. Due to weight, struc-
tural and heating power limitations, Ice Protection Systems (IPS) only protect selected surfaces of the
aircraft. It is tempting therefore to consider only the part of the structure associated with the IPS,
however this approach may be problematic if the IPS allows running-wet conditions or is operating at

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 225
CHT3D - 3D Conjugate Heat Transfer

off-design conditions. It is therefore a good practice to always consider a solid domain that includes
portions of the structure extending downstream of the IPS enclosure, so that the inevitable runback
effects and possible re-freeze of the liquid water film in the unprotected region can be adequately
captured.

From the geometrical point of view, it is also very important to ensure that pairs of surfaces that form
an interface are in contact with each other, are of very similar shape and spatial dimensions and that
the grids on either side of the interface, while not necessarily strictly matching, have similar densities.
For example, the jets emanating from piccolo tube orifices form hot spots on the protected surface,
and the associated flow phenomena exhibit very strong velocity and temperature gradients that should
be captured with sufficient spatial resolution. In addition, the solid and external airflow grids also need
to be refined in the region of the jet impingement location to prevent artificial diffusion of the heat
fluxes and temperature gradients that would occur due to sudden grid density changes from one domain
to the next. The CHT3D interface communication software is designed to support meshes that may not
be precisely in contact with one another, or overlap into one another, a situation that is encountered
naturally with non-matching grids, as long as the gap/overlap/penetration is smaller than the edges of
the element faces.

Note:

A good habit before generating grids for external/solid/internal domains that share CHT in-
terfaces is to:

• Separate the interface surface before generating any mesh;

• Make sure CADs of the external, solid, and internal domains share the same geometrical
surface at the CHT interfaces, including their position, boundaries, and geometrical shape.

CHT simulations of typical aircraft IPS involve cold high-speed flows at high Reynolds numbers on the
outer skin surfaces and sonic or supersonic regions in the hot-air inner chamber, therefore the flow and
thermal gradients on either side of the interface are very large and require low-Reynolds number turbu-
lence models that support laminar-to-turbulent flow transition, such as the SST intermittency model in
FENSAP, Fluent or CFX, and the associated very fine grids for accuracy. To ensure sufficient accuracy,
the thickness of the grid elements of the airflow domains in contact with the CHT interfaces should
permit operation with maximum Y+ values less than 1 and expand very gradually as distance from the
interface increase.

Note:

For most industry applications, external and internal grids are required to have the following
mesh requirements in order to improve the accuracy of CHT simulations. A first layer element
height of 1e-6 ~ 3e-6 m is suggested. Growth ratio will be within a range of 1.05 to 1.25.
These will ensure that there are sufficient mesh nodes within the boundary sub-layer and
with a reasonable growth to well capture the airflow boundary layer.

In piccolo tube applications, the hot-air jets impinge on relatively thin aluminum or titanium skins. It
might be tempting to construct a solid skin domain composed of a single layer of elements, however
in these applications the temperature gradients can be very large and some heat diffusion may occur
in the metal skin, therefore a multi-layer grid is preferable. Furthermore, due to the small thickness of
the metal skin, it may be more efficient to use structured grids that permit elongated elements. C3D,

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
226 of ANSYS, Inc. and its subsidiaries and affiliates.
 Best Practices

the Finite Element heat conduction solver, is relatively insensitive to element aspect ratio; 3 to 5 element
layers crossing the thin solid skin are recommended and should be sufficient for most applications.

Electro-thermal anti- and de-icing ice protection systems are typically built with multi-layer, multi-ma-
terial composite skin assemblies, divided into multiple heating strips. The simulation of these arrange-
ments usually involves a single (external) fluid domain. The same issues raised for piccolo tube applica-
tions, such as ensuring that the solid domain extends well past the protected region and that the surface
mesh coverage is of very similar density on both sides of the interface also apply to these simulations.

Note:

Heating strips can be defined as volume or surface heat sources. The heating strip must at
least have one element layer off from the solid exterior surfaces. Avoid defining any heating
strip at a CHT interface.

Initial solutions are required for the internal and external fluid domains, droplets and surface liquid
water film. These solutions should be set up with a specified wall temperature on the interface
boundary that is greater than the recovery temperature, so that initial non-zero wall heat fluxes can be
established to ensure good convergence. Ideally, a wall temperature value a few degrees higher than
the freestream total temperature should be imposed on the external interface surfaces, and a wall
temperature a few degrees lower than the internal total temperature of the jets should be imposed on
the internal interface surfaces.

The internal heated cavity airflow solution may be rather complex and may contain regions of high
turbulence, high velocity and temperature gradients, such as the hot jets and the saucer-shaped roll-
up vortices that they produce, and will feature several strong recirculation zones. Suitably fine grids are
therefore needed to ensure that these features are correctly captured.

OptiGrid (See OptiGrid - Mesh Adaptation (p. 343)) is the perfect tool to ensure that the grid can capture
all these features accurately. The external airflow grid and the solid grid should have the same surface
grid density, hence ideally when mesh adaptation is used the external and solid grids should be con-
structed after adapting the mesh of the heated cavity.

Note:

Before moving forward with a CHT3D simulation, make sure that the initial external and in-
ternal airflow reach steady state, and ensure that pressure, velocity, temperature, shear stress,
and heat-flux distributions no longer vary with iterations, specially over the protected region.

Additionally, to accelerate the convergence of CHT3D, an initial ICE3D solution should be computed on
the external domain to establish an initial water film coverage. Only the extent of the water film coverage
on the external surface is sought, and can usually be established with a simulation of 20-30 seconds,
depending on film speed. In steady-state anti-icing CHT3D computations, any ice shapes produced by
ICE3D are not representative of a real ice shape, since the ice mass and height are reset at the beginning
of each CHT iteration. In these cases, ICE3D only computes the thermodynamic conditions governing
the behavior the water on the skin surface. If a realistic ice shape for a specific duration is required, a

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 227
CHT3D - 3D Conjugate Heat Transfer

single-shot ICE3D simulation or a multishot sequence simulation (MULTI-FENSAP and MULTI-FLUENT

only) can be executed after the anti-icing CHT3D computation has converged.

Note:

In the case of a single ICE3D simulation, a drag-&-drop of the config icon of the ice_ext
component of the CHT3D run onto the config icon of the ICE3D run will automatically set
the in-flight icing solution and the steady-state conductive (anti-icing) heat flux solution of
the CHT3D run as inputs to the ICE3D run. This is supported when FENSAP, Fluent or CFX
are used as airflow solvers.

In the case of a multishot sequence simulation based on a CHT result, a drag-&-drop of the
config icon of the CHT3D run onto the config icon of the multishot run will automatically
take all reference conditions and thermal equilibrium solutions from each module of the
CHT3D run and set them as inputs to their respective modules of the multishot run.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
228 of ANSYS, Inc. and its subsidiaries and affiliates.
 Best Practices

In both cases, the conductive (anti-icing) heat flux obtained during the CHT3D calculation
is kept constant during the ice accretion process. A separate set of tutorials inside the FENSAP-
ICE Tutorial Guide portrays these setups. This feature is currently supported in MULTI-FENSAP
and MULTI-FLUENT but not in MULTI-CFX.

Conversely, if an unsteady de-icing simulation is conducted, the transient and final ice shape will be
determined directly in the CHT3D computation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 229
CHT3D - 3D Conjugate Heat Transfer

Since the setup of a CHT simulation requires careful consideration and planning, it is advisable to consult
FENSAP-ICE Tutorial Guide for examples of how to create the various domain grids, the coverage of
each interface, the boundary conditions, etc.

Important:

Plan ahead! Surface mesh density should be roughly the same on both sides of an interface.
A mesh size expansion ratio not exceeding 1.2 in the direction normal to the walls is recom-
mended.

8.2. CHT3D Run Settings

The window shown below will appear when a CHT3D run is created.

The Problem type menu offers a choice of Piccolo (2 fluids, 1 solid) or Electro-Thermal (1 fluid, 1
solid) anti-icing options.

The flow regime, Dry air, Wet air or Wet air & droplets should be selected next. In the Dry air regime,
CHT3D iteratively transfers the interface conditions (wall heat fluxes and temperature) among the fluids
and the solid domains. Other supported flow solvers, such as Fluent and CFX, can be selected with the
Flow solver pull-down menu.

Click the OK button to create the CHT3D run. The following figure shows the configuration of a typical
dry-air steady-state anti-icing simulation. Each row in the figure corresponds to a domain.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
230 of ANSYS, Inc. and its subsidiaries and affiliates.
 CHT3D Run Settings

In the Wet-air regime, intended for steady-state anti-icing calculations, CHT3D iteratively transfers the
interface conditions (wall heat flux and temperature) between the different fluids and the solid domain
interfaces, but also accounts for the water impingement and the surface water film energy balance on
the external surface of the metal skin.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 231
CHT3D - 3D Conjugate Heat Transfer

Note:

An extra row for the ICE3D run appears in this wet-air setup. ICE3D will compute the water
film flow on all wall surfaces as a balance of incoming water, evaporation/ sublimation,
convection and phase-change driven by heat flux exchanges between domains.

Important:

Only the thickness and extent of the water film on the surface is meaningful. Any ice shape
produced by ICE3D in this type of CHT3D computation is not representative of a real ice
shape, since the ice mass and ice thickness are reset at each CHT iteration.

Note:

There is no sub-run for the water droplet solution, since the incoming water flow rate remains
unchanged during the solution process. The DROP3D solution must be computed in advance
and used for the initial and CHT3D ICE3D runs.

The fluid_ext and fluid_int, as well as the ice_ext sub-runs, are configured as restarts. An
initial solution must be run for each fluid domain including its water film solution separately
before starting the CHT3D procedure. These solutions must be then supplied to the corres-
ponding CHT3D sub-run as a restart file. These initial solutions must be configured to generate
heat fluxes on all wall surfaces by specifying an interface temperature a few degrees higher
than the stagnation temperature on the outer interface surface and lower than the adiabatic
temperature on the inner interface surface. Imposing adiabatic conditions on the walls is
inadvisable, since it will considerably slow down the convergence of the CHT procedure.

The initial ICE3D run (30-40 sec only) is required to establish a film of water on the surface
to provide a meaningful starting point and accelerate the CHT3D convergence. More details
can be found in the FENSAP-ICE Tutorial Guide

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
232 of ANSYS, Inc. and its subsidiaries and affiliates.
 Dry Air Regime

Even though an initial wall temperature is imposed on all walls, the correct wall temperature
will be recovered even in dry regions outside the CHT interface (Full Energy Equation option).

In the Wet-air & droplets regime, CHT3D iteratively transfers the interface conditions (wall heat flux
and temperature) across the fluids and solid domain interfaces and accounts for the water impingement
and the surface water film energy balance on the external surface. It also transfers the temperatures of
the airflow domain to the droplet domain, solving an energy balance in the droplet domain which
contributes to the heating or cooling of droplets. In such a run, there will be a drop_ext input line,
containing the droplet configuration.

The configuration file in each row controls the behavior of the corresponding solver, while the main
configuration icon controls the behavior of the coupling algorithm. It is important to note that the ref-
erence conditions of the initial solutions must be exactly the same as those specified in the configuration
files of the sub-runs, otherwise the calculation will converge to erroneous values. The easiest way to
avoid mistakes is to drag & drop the configuration files of the initial solutions onto the configuration
files of the corresponding CHT3D sub-runs. This regime is supported by FENSAP, Fluent and CFX.

In the Dry-Air or Wet-air regimes, steady-state CHT3D computations can be performed for piccolo
tubes and electro-thermal systems in Anti-icing mode. In Wet-air electro-thermal simulations, the De-
icing mode is also available. This mode enables unsteady CHT3D computations through the solid, the
melting/accreting ice layer and the water film. At the moment, a wet-air de-icing simulation starts on
a surface which is free of ice. Therefore, the Initial solution is always set to From DRY and ice needs
to accrete during the CHT simulation before de-icing it.

8.3. Dry Air Regime

The following sections illustrate the settings required to run a dry-air simulation.
8.3.1. Input Parameters
8.3.2. Initial Flow Solutions

8.3.1. Input Parameters

The input parameters and grid files of all fluid and solid domains should be assigned before starting
the CHT3D calculation.

For the fluid domain,

• When FENSAP has been selected as the Flow solver in the CHT configuration window, the
graphical interface opens the FENSAP input parameter window. Consult FENSAP - Flow Solu-
tion (p. 53) of this manual for guidelines on how to set up the input parameters for the airflow
calculation.

• When Fluent or CFX has been selected as the Flow solver, the external and internal flow settings
can be adjusted by clicking the config icon of fluid_ext and fluid_int. The new input will

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 233
CHT3D - 3D Conjugate Heat Transfer

overwrite some of the original Fluent or CFX settings such as solver iterations and convergence
criteria. The execution settings include the path of the executable file, run parameters, and
additional commands if required. Guidelines to properly set Fluent and CFX simulations within
FENSAP-ICE are provided in Multishot with Fluent (p. 300) and Multishot with CFX (p. 309). It is
advisable to consult the FENSAP-ICE Tutorial Guide for examples on how to set-up these CHT
calculations using Fluent and CFX as flow solvers.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
234 of ANSYS, Inc. and its subsidiaries and affiliates.
 Dry Air Regime

For the solid domain, the graphical interface opens the C3D input parameter window. More information
on input parameters for the heat conduction calculation can be found in C3D - Unsteady Heat Con-
duction (p. 209).

Tip:

Since CHT3D is an iterative process, a limited number of iterations should be performed

on the fluid and solid domains at each CHT3D iteration. The maximum number of time
steps in FENSAP, Fluent and CFX should be set in the range 20 - 50 in order not to spend
an unnecessary amount of time in the CHT iteration.

To reduce computational time, both the flow solver and C3D should be configured to write
their solution files only at the end of their respective calculations.

In C3D, which is an unsteady solver, the Total time setting is what really controls the
convergence and stability of CHT3D. It acts as the global time step of the simulation. Larger
values may cause oscillating minimum/maximum solid temperatures between CHT3D iter-
ations since the conduction process in the solid can advance more rapidly than the other
solution modules (flow, icing). A low value, between 1 - 5 seconds, is recommended for
this setting. Similarly to any other time-marching solver, lower time step values will require
more iterations for global convergence.

8.3.2. Initial Flow Solutions

The CHT3D iterative process starts with initial airflow solutions computed for each fluid domain. To
assign these initial solutions, right-click the corresponding icons, select Define from the menu and
browse to assign the appropriate files. Alternately, the configuration files of the initial solutions can
be dragged & dropped onto the corresponding sub-run configuration files.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 235
CHT3D - 3D Conjugate Heat Transfer

8.4. Wet Air Regime

The wet-air regime requires a more complex setup than dry-air.

8.4.1. Input Parameters

The input parameters and grid files of all fluid and solid domains should be assigned before starting
the CHT3D calculation. Refer to FENSAP - Flow Solution (p. 53), Recommendations to Set up a Fluent
Calculation (p. 303), Recommendations to Set up a CFX Calculation (p. 312), DROP3D - Droplet and Ice
Crystal Impingement (p. 113), ICE3D - Ice Accretion and Water Runback (p. 171), C3D - Unsteady Heat
Conduction (p. 209) for the input parameters required for FENSAP, Fluent, CFX, DROP3D, ICE3D and
C3D, respectively.

In this flow regime, both water impingement (DROP3D) and water runback and evaporation (ICE3D)
on the external skin are considered. For all anti-icing and de-icing simulations, the water impingement
solution remains constant in time, therefore the ice growth should not be allowed to increase excess-
ively. For ICE3D, the mass and energy equations for the film of water are solved by considering the
convective (FENSAP, Fluent or CFX) and anti-icing (C3D) heat fluxes.

Tip:

Anti-icing simulations drive the inter-domain thermodynamic balance towards a steady-

state solution. In ICE3D, which is an unsteady solver, the time duration should be set to a
small value, for example 10 to 40 seconds, sufficient for the film to develop properly and
for the temperature to converge. The Icing model should be set to Glaze - Advanced.

The C3D Total time acts as the global time step for CHT3D iterations. Lower values improve
convergence and stability while larger values reduce the total number of CHT3D iterations
required for convergence. By default, a total time of 5 seconds is set. If minimum and
maximum solid temperatures show oscillations between CHT3D iterations, this value can
be reduced to 1 second, or even lower, depending on the problem.

8.4.2. Initial Flow and Droplet Solutions

Before the CHT3D iterative process can begin, initial airflow solutions must be computed on the cor-
responding internal and external flow grids. These initial solutions can then be used to start the
CHT3D procedure. Right-click each of the input file icons on the left of the configuration icon, select
Define from the menu and browse to assign the air solutions.

Tip:

Initial external flow solutions computed for de-icing simulations should include the surface
roughness generated during ice accretion. For anti-icing computations, clean surfaces can
be used since they are expected to remain free of ice. In this case you should activate the
transition model for the external airflow calculation.

Initial external flow solutions for anti-icing simulations should be computed with uncon-
taminated surfaces (no roughness), since they are expected to remain free of ice. In this

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
236 of ANSYS, Inc. and its subsidiaries and affiliates.
 CHT3D Input Parameters

case it is also strongly recommended to activate the transition model, since flow transition
has a very noticeable impact on the accuracy of the simulation.

The CHT3D iterative process for the wet-air regime starts with an initial droplet solution, pre-computed
on the external fluid domain. To assign this initial droplet solution to the ICE3D domain, right-click
the corresponding icon, select Define and browse to assign the appropriate droplet solution file.

Tip:

To quickly set up a CHT run, drag and drop the configuration icon of each initial run onto
the configuration icon of the corresponding domain in the CHT run. FENSAP-ICE will
automatically copy the parameters and will assign the solution files of the initial run to
the input files of the CHT run. Remember to adjust the ICE3D and C3D total simulation
time and the number of iterations in flow solver.

8.5. CHT3D Input Parameters

In this section you will set up various conjugate heat transfer options using CHT3D.

8.5.1. Anti-Icing Parameters

The number of CHT3D iterations, for example, the number of loops through all the domains to ex-
change information can be set in the Run parameters section. The solutions of all the domains can
be saved every few iterations if desired.

When FENSAP is the flow solver, the Flow solver mode box under Solver options offers the choice
of four solution modes: Solve energy only (default), Solve energy only - Conservative, Solve full
Navier-Stokes or Useheat transfer coef. In the case of Fluent and CFX, the Flow solver mode box
only offers these options: Solve full Navier-Stokes and Use heat transfer coef..

In the Solve energy only mode, the continuity and momentum equations of the fluid in each domain
are frozen, only the energy equation is solved. The Solve full Navier-Stokes mode allows a full viscous
solution in each fluid domain, however this mode can be computationally expensive. The Solve energy
only - Conservative option solves the conservative energy equation which is recommended if the
free stream Mach number is in the transonic range. Finally, the option Use heat transfer coef. sim-
plifies the problem by modeling the heat exchange with the fluid domains using the convective heat

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 237
CHT3D - 3D Conjugate Heat Transfer

transfer coefficient and a reference temperature. While the reference temperatures are taken from
the parameters of each fluid run, the heat transfer coefficient is automatically computed using the
initial solution temperature and heat flux distribution.

When the external flow solver mode is set to Solve full Navier-Stokes, the Ice roughness height
option can be enabled. This option improves the ice shapes computed by CHT3D by imposing
roughness where ice forms. The shear stress and heat flux of the ice patches will change accordingly,
while uncontaminated regions will remain smooth. Two roughness options are available:

The Specified height option uses a constant value of sand grain roughness for the iced surfaces in
the anti-icing simulation. From ICE3D option inherits the ice roughness calculated by ICE3D using
one of its roughness models (beading, NASA roughness, Shin & Bond, etc.)

Note:

Fluent and CFX will automatically apply this roughness using the High roughness (Icing)
model. The Roughness Constant is always set to 0.5. It will also enable the Blended Near
Wall treatment of CFX.

If the initial Fluent solution was computed using serial or parallel solver execution, the same parallel-
ization setting should be used in the subsequent CHT execution. Fluent might reorder the nodes of
the grid when switching between serial and parallel execution, making the reordered grid unsuitable
for FENSAP-ICE restarts. You should always use the parallel version of Fluent, to avoid mismatched
files. In the case of CFX, only parallel runs are supported. Therefore, two or more cores should be
specified.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
238 of ANSYS, Inc. and its subsidiaries and affiliates.
 CHT3D Input Parameters

8.5.2. De-Icing Parameters

Values for the time-step and convergence loops are set in the Parameters panel of the CHT de-icing
configuration.

Similar to the standalone C3D module, two time stepping schemes are provided in de-icing CHT:
Constant and Automatic modes. The Constant mode employs a constant time step throughout the
simulation, while with the Automatic option, the time step is determined by the rate of heat conduc-
tion and the element size. The Maximum time step sets the maximum upper limit of the auto-com-
puted time step.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 239
CHT3D - 3D Conjugate Heat Transfer

The Unsteady time step parameter sets the global time step of the CHT loop. The Unsteady total
time is the total time of the CHT simulation.

Within each CHT time step, the water film, ice and solid domains will be solved sequentially and re-
peatedly until thermodynamic balance is reached at the interfaces. The number of times each domain
is solved is controlled with Iter. per time step parameter.

Note:

Select a number of Iter. per time step large enough to converge the solid minimum and
maximum temperature at each time step. The solid temperature convergence graphs are
displayed at runtime in the Graph tab of the run window.

At each time step, the solution of each domain advances for a total duration corresponding to the
Unsteady time step. While the solid and phase-change solvers can march with the same time step
as the CHT loop, the water film solution requires much smaller time steps for stability. Hence, each
CHT Unsteady time step is divided into a given number of smaller intervals to compute the water
film solution. The number of time steps of the film domain is defined with the Icing sub-iterations
parameter. For example, using an Unsteady time step of 0.1 s and 1000 Icing sub-iterations, the
film solution will be computed at each CHT time step using 1000 inner time steps of 1E-04 s, while
the conduction and phase change through the solid and ice layer domains will advance using a single
time step of 0.1 s.

8.5.3. Domain Interfaces

The Conjugate Heat Transfer procedure requires the application of a specific solver in each domain,
hence the domain interfaces must be configured in order to apply the appropriate interface conditions.

Go to the Interfaces panel to configure the interfaces between the fluid and solid domains.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
240 of ANSYS, Inc. and its subsidiaries and affiliates.
 CHT3D Input Parameters

Each interface is defined in terms of a pair of wall boundary condition indices that connect a fluid
domain to one side of the solid domain. Select the boundary condition indices of the fluid and the
solid domain that correspond to the common interface.

Multiple interfaces are supported. To add an interface, click the button and pair the wall families
that form the interface. To delete an interface, click the button.

Click the Display buttons to visually verify the correctness of the coupling of each pair of wall families
in the graphical window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 241
CHT3D - 3D Conjugate Heat Transfer

Note:

Only wall boundary condition indices are shown by the graphical interface.

CHT3D takes care of the information exchange through the interfaces automatically, even
if the two surfaces don’t match point-by point.

8.5.4. Reference Temperatures

To obtain accurate CHT solutions, especially in the wet air regime, it is imperative that the CHT3D
reference temperatures be set correctly. CHT3D uses two reference temperatures to compute convective
heat transfer coefficients from the heat fluxes, the External surface recovery temperature and the
Internal adiabatic stagnation temperature. The two temperatures are detected automatically by
FENSAP-ICE when FENSAP is the main flow solver, hence these parameters are not editable.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
242 of ANSYS, Inc. and its subsidiaries and affiliates.
 CHT3D Input Parameters

Other flow solvers, such as Fluent or CFX, may not provide this critical data automatically, therefore
when the flow solver is other than FENSAP, the Specify temperatures check box is activated auto-
matically and the correct reference temperature values must be initialized manually. Refer to The
Recovery Factor (p. 193) for more details on how to compute the External surface recovery temper-
ature.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 243
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
244 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 9: FENSAP-ICE-TURBO
The following sections of this chapter are:
9.1. Multi-Component Simulations
9.2. Airflow Through a Turbomachine
9.3. Multiphase Droplet and Ice Crystal Simulations
9.4. Ice Accretion in Turbomachines
9.5. Computing Re-Injected Particles
9.6. Output Files
9.7. Specification of Mixed-Type Boundary Conditions
9.8. Completing a Run

Turbofan engine malfunctions characterized by flameout or rollback events have been previously reported
by flight safety agencies. Recent studies have indicated that ice buildup can occur in a low pressure
compressor in mixed phase environments, containing little or no droplets, but a large concentration of
ice crystals.

Ice crystals penetrate the compressor core, where temperatures are substantially higher than the external
ambient conditions. Ice crystals warm up and start to melt and stick to the surfaces and can eventually
cause some ice build-up. The collection of ice can cause compressor vibrations, blockage of airflow
leading to compressor surge. The aerodynamic forces acting on the ice can cause it to shed and damage
components downstream. If shed ice reaches the combustor, it can cause an engine flameout.

Engine manufacturers must ensure that jet engines remain ice-free under all operating conditions. While
the physics related to icing in jet engines are very complex, more sophisticated models are being de-
veloped to enhance the accuracy and predictability of icing simulations within turbomachines.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 245
FENSAP-ICE-TURBO

FENSAP-TURBO is a module that is specifically conceived to simulate in-flight icing effects in jet engines.

9.1. Multi-Component Simulations

FENSAP-ICE solves steady-state airflow, water droplet/ice crystal impingement and the corresponding
ice accretion on multiple stationary and rotating components.

Each component in a single simulation is solved independently and linked to adjacent components
through interfaces. The mixing-plane algorithm is used to transfer boundary conditions between inter-
faces. Since all grids are separate, non-matching grids and blade rows with unequal pitch are supported.
Usually the grids used in turbo simulations are rotationally periodic, however it is possible for a periodic
grid to interface with a non-periodic grid as long as the interface on the non-periodic side is axisymmetric.
The non-periodic grid orientation does not need to align with the periodic components, as the mixing
plane boundary condition transfer is designed to work with local cylindrical coordinates at each interface.
This allows an aircraft with nacelle that is not exactly aligned with any of the Cartesian axes to be con-
nected to an engine aligned in any direction.

This section describes the general features in FENSAP-ICE required to set up an airflow, droplet/ice
crystal impingement or ice accretion in a turbomachine.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
246 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multi-Component Simulations

Figure 9.1: Turbo Simulation Setup Featuring Rotationally Periodic Internal Components with a
Full 3D External Grid That Contains a Wing-Body-Nacelle-Pylon Configuration

9.1.1. Adding a Turbo Run

A series of individual components (rows) is required to set up a multi-row simulation. A new run is
created either through the File → New run menu or by clicking the new run icon in an existing project
window:

Three simulation types are available to you:

FENSAP-TURBO - airflow simulations

DROP3D-TURBO - droplet and ice crystal impingement

ICE3D-TURBO - ice accretion simulations

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 247
FENSAP-ICE-TURBO

Once a simulation type and suitable run name are chosen, a window will appear to identify the
number of components:

A global config icon, identified by a blue gear, contains the configuration settings for this run:

When several runs appear in the project, the readability of the project window can be improved by
clicking the + or - buttons on the left of each individual run to collapse or expand each run:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
248 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multi-Component Simulations

9.1.2. The Turbo Panel

The Turbo panel is available in every FENSAP-ICE-TURBO run window, and can be accessed by double-
clicking the config icon. The Turbo panel allows you to configure grids and their interfaces and set
up rotation speeds for each component.

The Advanced section allows you to define interface algorithms and the frequency of transfer between
boundaries.

[Link]. Grid File Assignment

The grid file is assigned in the Components section of the Turbo panel using the Browse buttons
(blue folder icons) on the right side of each Row.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 249
FENSAP-ICE-TURBO

The grids do not necessarily have to be arranged sequentially; staggered arrangements are also
supported. The following figures show examples of supported configurations.

Figure 9.2: Components in a Sequential Arrangement

Figure 9.3: Components in a Staggered Arrangement

To assign the grid directly in the project window, right-click the grid icon and select the appropriate
grid file with the Define option from the pull-down menu.

Important:

If the assigned grid is replaced by a different one, it is imperative to review the Bound-
aries panel to ensure that the boundary values are still valid.

[Link]. Specifying Component Rotation

A rotational speed for any component is defined by adding a check mark next to the Rotating
check box at the right of the row number and imposing the appropriate rotation speed, in revolutions
per minute (rpm).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
250 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multi-Component Simulations

A negative or positive sign in the rotation speed indicates the direction of rotation relative to the
axis of rotation.

[Link]. Reviewing Periodicity

To verify the periodicity of components and display periodic repetitions of the grid, specify the
Rotation axis, either X, Y, or Z, using the drop-down menu located at the bottom of the Components
panel.

Click the Display check box and define the number of repetitions. Multiple instances of the periodic
components will be displayed.

[Link]. Component Interfaces

An interface is created by pairing the adjoining boundaries in neighboring rows.

Interfaces are automatically generated the first time the configuration panel is opened under the
assumption that the rows are all arranged in sequential order (purely axial geometry). The automatic
assignment should be reviewed and edited, if necessary, before proceeding to the input parameters.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 251
FENSAP-ICE-TURBO

To add or remove an interface, use the + or - buttons. Each component is identified by its row
number. Typically, the exit of one component should be coupled with the inlet of its downstream
component. As soon as surfaces from neighboring components are coupled to form an interface,
they are marked as disabled in the Boundaries panel, since no user-defined boundary condition
can be applied on these surfaces.

The interface Pressure relax. is used when pressure boundary conditions are updated at an exit.
The relaxation factor is set to a default value of unity but could be reduced should convergence
instabilities arise.

[Link]. Advanced Settings

The settings indicated in this section apply to airflow simulations in a FENSAP-TURBO run.

The Update solution every (iterations) parameter defines the frequency with which the interfaces
boundary conditions are updated. This parameter is set to a default value of unity but can be in-
creased if the convergence of the system is slow.

Two Interface algorithm methods are available for the application of boundary conditions at the
interfaces:

Table 9.1: Interface Algorithm Methods

Fast It is the simplest and quickest method but may

be unstable when the mesh is very fine at the
interface.
Stable Provides a smooth variation of the interface
conditions at each update. It is more robust but
may reduce the convergence rate compared to
the Fast option. This is the default setting.

The Initial steady-solution sets the number of iterations to be completed in each component
before the first update of the interfaces is allowed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
252 of ANSYS, Inc. and its subsidiaries and affiliates.
 Airflow Through a Turbomachine

9.1.3. Turbo Part

In order to properly post-process turbo (airflow, particle and ice) solutions inside CFD-Post Turbo, it
is recommended to assign a Turbo part (Hub, Shroud, Blade, Inlet, Outlet, Periodic1, Periodic2,
Other) at each boundary surface of the computational domain.

• Inlet and Outlet turbo parts are automatically detected by the graphical user interface of FENSAP-
ICE at execution time.

• Hub, Shroud, Blade, Periodic1, and Periodic2 must be manually selected.

• Other is used to define boundary surfaces that cannot be represented by another Turbo part. In
this manner, Other surfaces are ignored by CFD-Post Turbo and should be manually selected in
the graphical user interface of FENSAP-ICE.

For more details regarding post-processing of (airflow or particle) solutions using CFD-Post Turbo,
consult FENSAP-ICE Turbo (p. 491).

9.2. Airflow Through a Turbomachine

A FENSAP-TURBO run simulates airflow in a set of turbomachinery components.

9.2.1. Physical Model for Static and Rotating Components

The Model panel in the configuration settings of a FENSAP-TURBO run contains the physical models
that are going to be used to run a turbomachinery simulation. The Air option in the Physical Model
box is set by default.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 253
FENSAP-ICE-TURBO

The Continuity and Momentum Equations (p. 54) are used to solve all static components.

For rotating components, these equations are converted to the relative frame of reference to account
for the rotational speed:

where the subscript refers to the relative frame. The external force vector in the momentum
equations consist of the Coriolis force, , and centrifugal force, :

where Ω is the rotational velocity of the component and r is the distance from the axis of rotation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
254 of ANSYS, Inc. and its subsidiaries and affiliates.
 Airflow Through a Turbomachine

The energy equation for rotating components is:

where and are the relative internal energy and total enthalpy:

Here is the relative velocity in the rotating frame, and is the tangential velocity of the rotating
frame, . The Full PDE energy equation is the only option available in FENSAP-TURBO when
solving airflow.

The default turbulence model for airflow simulations in FENSAP-TURBO is Spalart-Allmaras. More details
and options for other turbulence models are available in Turbulent Flows (p. 56).

9.2.2. Airflow Setup in FENSAP-TURBO

In this section you will set up airflow options using FENSAP-TURBO.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 255
FENSAP-ICE-TURBO

[Link]. Reference Conditions

The Reference conditions in a turbomachine are typically the conditions experienced at the inlet
of the first row or freestream, outside the nacelle. The reference conditions in FENSAP-TURBO also
establish the reference icing conditions of the first stage. The Conditions panel in the configuration
settings is used to establish reference conditions for the airflow simulation.

The Characteristic length is typically the span-wise length of a fan or compressor blade or the
annular length of a compressor cross-section.

The Air velocity could be either the axial velocity at the inlet of the first row, or the maximum
tangential velocity at the tip of the fan blade, a function of the fan speed ω and the tip radius rtip

Air static temperature and Air static pressure are governed by the engine inlet operating condi-
tions. The static pressure and temperature are also used to initialize the computational domain in
each component.

At high rotation speeds, or when many stages are present in a single simulation, there is a risk of
transient flow reversal at the exits of each stage due to the adverse pressure gradient. To reduce
the risk of flow reversal and its impact on convergence, the reference static pressure may be also
set to its highest value, static pressure at the exit of the final stage.

[Link]. Initial Conditions and Restarting a Calculation

Initial conditions setup the initial velocity components for all rows. You may specify Velocity
components, Velocity angles or a Solution restart.

Velocity components specify velocities in X, Y and Z directions.

Velocity angles break up the Reference velocity into X, Y and Z components.

The Solution restart option is used to specify a previous solution file as an initial condition for the
present simulation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
256 of ANSYS, Inc. and its subsidiaries and affiliates.
 Airflow Through a Turbomachine

Click the Browse buttons on the right to open the file browser and select the solution file that
corresponds to each component.

9.2.3. Boundary Conditions

The list of general boundary conditions is described in Boundary Conditions (p. 73). The additional
conditions required for turbomachinery flows are explained in this section.

FENSAP-TURBO lists all boundaries present in each sub-component in the Boundaries panel.
Boundary condition options for boundaries that are interfaced are grayed out since the boundary
conditions are transferred internally.

When many components are present, navigating between components can be challenging. Double-
clicking the row maximizes or minimizes the boundaries listed for the row.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 257
FENSAP-ICE-TURBO

[Link]. Engine Inlet

The engine inlet boundary condition can be used for engine intakes to specify Total pressure,
Total temperature, and a Mass flow rate. Alternatively if Mach number is known, this value can
be set instead of the mass flow rate. It is a 1D-Riemann characteristics based boundary condition

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
258 of ANSYS, Inc. and its subsidiaries and affiliates.
 Airflow Through a Turbomachine

that allows a limited variation of the specified total conditions based on flow phenomena that occurs
downstream.

This flexibility in allowing small variations of the flow variables makes the boundary condition robust
for handling complex flows. It can be used in internal flow applications, such as hot air anti-icing
air supply inlets.

[Link]. Counter-Rotating Walls

Rotating components may contain some wall boundaries that remain static. For example, a fan
section, such as the one below, has a rotating blade with a static shroud.

Since FENSAP-TURBO solves rotating components in the relative frame of reference, a counter ro-
tating velocity, equal and opposite to the blades rotational speed must be applied to the shroud

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 259
FENSAP-ICE-TURBO

wall, and all other components that are static. This condition is applied by selecting the Counter-
rotating option from the pull-down menu in the Rotation section.

The boundary label turns yellow to identify the wall as a counter-rotating wall boundary. The
Counter-rotating option may only be applied to axisymmetric surfaces.

[Link]. Radial Equilibrium at the Exit Boundary

A fluid element subject to forces in the radial direction due to the tangential (whirl) component of
velocity, experiences a pressure gradient in the radial direction. The pressure gradient is a
function of the radius , and density .

On outflow boundaries, a radial variation of the static pressure can be imposed by setting the Ra-
dial Equilibrium equation option to Enabled. For details on how to configure radial equilibrium
settings on a subsonic outlet, please refer to Subsonic (p. 82).

9.2.4. Extended Icing Data for Turbomachinery Applications

EID is a required step before running any icing calculation in turbomachinery components. It is im-
portant to note that the EID run requires an adiabatic wall airflow solution. Refer to Extended Icing
Data (EID) (p. 107) for more details.

9.2.5. Importing a CFX Flow Calculation

A turbo solution from CFX can be easily converted to FENSAP-ICE format and set up automatically.
Ensure that the following are available in a CFX file before initiating an import:

1. All reference conditions must be constant values, and not based on expressions. Constant per
row rotation values are mandatory. The per row rotation speed must be constant for the solution
to be properly converted to the absolute frame of reference. All FENSAP-ICE solutions are read
and written in the absolute frame.

2. CFX solutions with adiabatic walls will need EID calculation by FENSAP before they can be used
for icing simulations.

Note:

Conditions defined as expressions will be set up with a default value which can be fine-
tuned in the import panel in FENSAP-ICE.

In CFX, laminar viscosity and conductivity of air should be set using the icing conditions
of your problem. This can be done by adjusting the air material properties within CFX.
Otherwise, these parameters will remain at standard atmosphere and will not accurate
results.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
260 of ANSYS, Inc. and its subsidiaries and affiliates.
 Airflow Through a Turbomachine

[Link]. Auto-Configure a Run from a CFX File

1. Start a new project directory or navigate into an existing one.

2. Start a new FENSAP-TURBO/DROP3D-TURBO run.

3. Specify the number of rows corresponding to the number of components/zones in the CFX
solution file.

4. Right-click the first grid icon of the turbo configuration and select the Define option. Choose
the .res or .def file, and click Next. The following panel will appear:

Table 9.2: The Choices Are:

Single grid Will import all the zones in a single grid.

Multiple grids Each zone will be imported as a separate grid
& solution file.
Single zone Used to import a single zone from a CFX file.

Note:

For turbomachinery runs, the Multiple grids option must be selected. The wall
boundaries are automatically identified by FENSAP-ICE and should not need any user
intervention.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 261
FENSAP-ICE-TURBO

5. Click Next to import the solution fields. The flow datafields are automatically assigned based
on availability in the .res file.

6. Click Next to assign the reference conditions. Any reference condition that cannot be found in
the .res file must be configured manually.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
262 of ANSYS, Inc. and its subsidiaries and affiliates.
 Airflow Through a Turbomachine

7. Click Next to finish the grid/solution import process.

Note:

If you choose a CFX file that has already been converted, the following message will
appear.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 263
FENSAP-ICE-TURBO

If the same .res file is used to start an EID or DROP3D-TURBO calculation, then select
the Keep option. The run will get auto-configured to set up information required to start
a turbo calculation. The Edit option allows you to modify boundary condition definitions,
reference information imported into an EID/DROP3D-TURBO run. The New import option
lets you convert a new grid by overwriting the existing file in the project.

The following options are also available through the command line using the cfx2fensap com-
mand:

Table 9.3: Commands

cfx2fensap [Link] OUTPUT

Converts automatically a CFX file, and writes [Link] [Link].

cfx2fensap [Link] OUTPUT -hflux -shear

Writes [Link] and [Link].

cfx2fensap [Link] OUTPUT -zone=1

Extracts the 1st zone only.

cfx2fensap [Link] OUTPUT -split

Splits all sub-zones and writes to [Link], [Link],

etc.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
264 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multiphase Droplet and Ice Crystal Simulations

cfx2fensap [Link] OUTPUT -d

Diagnostic mode, will list the content of the file including the amount and name of the zones
(volumes/rows).

9.3. Multiphase Droplet and Ice Crystal Simulations

The configuration parameters for DROP3D calculations have been described in DROP3D - Droplet and
Ice Crystal Impingement (p. 113). The following sections describe the additional features exclusive to
the computation of droplet and/or ice crystal impingement in turbomachinery components.

Droplet and ice crystal calculations of turbomachinery components are simulated by choosing a DROP3D-
TURBO run in the New run dialog box. Each row is run sequentially in DROP3D-TURBO to utilize max-
imum CPU usage per row. Interactions between interfaces are done through files containing pitch aver-
aged information.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 265
FENSAP-ICE-TURBO

9.3.1. Assigning an Airflow Solution

The airflow solution sets up the inertial drag experienced by droplets and ice crystals and allows for
an accurate computation of particle impact zones. Air solutions are assigned in the Air Solution
section of the Model panel:

Click the button to open the file browser and select the airflow solution file that corresponds to
each component in the list.

Tip:

The airflow solutions of each component can also be assigned automatically in the project
window by dragging & dropping the config icon of the FENSAP-TURBO run onto a DROP3D-
TURBO config icon. The drag and drop operation also automatically copies the common
airflow reference and input parameters for the particle impingement calculation.

9.3.2. The DROP3D-TURBO Physical Model

The Particle parameters section of the Model panel contains several models that impact the icing
solution on a turbomachinery component:

Table 9.4: DROP3D-TURBO Physical Model

Particle type Droplets or Crystals or Droplets+Crystals

Particle thermal equation Enabled or Disabled
Mass reinjection (Turbo only) Disabled, Simple Reinjection, Complete Reinjec-
tion

Vapor can also be Enabled within a turbomachinery component. This provides a more realistic icing
environment.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
266 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multiphase Droplet and Ice Crystal Simulations

[Link]. The Particle Equations

It is possible to run either droplets, crystals, vapor or all particle types in a simulation. For static
components, the Eulerian two-phase model described in The Physical Model (p. 113) is used to solve
for crystal or droplet impingement while the Vapor model is used to predict the transport of water
vapor. For rotating components, the Eulerian equations are modified to include the rotational body
forces:

where the variables and refer to the particle concentration (LWC or ICC) and the particle ve-
locity, respectively, and where and refer to the vapor concentration and the air velocity,
respectively. The force term on the right-hand side of the momentum equations, representing
the centrifugal and Coriolis forces acting on the particles, is activated for rotating frames:

[Link]. Particle Thermal Equation

Supercooled droplets or crystals entering a turbomachine warm up progressively, but not at the
same rate as the airflow. In this manner, the temperature difference between the particle and the
surrounding airflow increases as particles travel through the compressor.

The particle thermal equation is:

The source term accounts for the transfer of energy between the droplets and/or ice crystals and
the airflow. The term can be sub-divided to include terms such as convection with airflow, absorption
or emission due to radiant energy, and addition or losses due to mass coupling effects that cause
evaporation, condensation, freezing or melting:

represents the total internal energy of the particle, such that:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 267
FENSAP-ICE-TURBO

is the particle concentration and is the specific internal energy of the particle:

is the isobaric specific heat capacity (measured in J/(kg K)) of either the droplets or the ice
crystals.

For ice crystals, the temperature is obtained directly from the specific internal energy of ice crystals:

Where = 334,000 J/kg/k is the latent heat of fusion to melt ice crystals.

To activate the particle thermal equation, go to the Particle parameters section of the Model
panel of DROP3D-TURBO and select the Enabled option in the Particle thermal equation pull-
down menu.

The activation of the particle thermal equation adds additional fields in the solution file: particle
temperature and particle specific energy, diameter and melting fraction (in the case of crystals).

The calculated melting fraction is important in determining the possibility of crystals sticking to
either a dry or rime surface. The specific energy variable is used by ICE3D-TURBO in glaze ice simu-
lations to identify the local particle enthalpy at the point of contact on the surface.

It is normal for the melting fraction to contain high values in the ice crystal shadow zones, where
this quantity loses its meaning. For a more sensible view, melting fraction and ice crystal concen-
tration are combined in Viewmerical to display the liquid phase and the solid phase of the particles.

Note:

To allow mass and energy transfer between droplets/crystals and vapor, select Enabled
beside the Particle thermal equation.

9.3.3. Particle Reference Conditions

The Reference conditions section in the Conditions Panel sets the initial conditions for a particle
impingement calculation. If the config icon of the FENSAP-TURBO run has been dragged & dropped
onto the DROP3D-TURBO config icon, the airflow conditions have already been copied into the Ref-
erence conditions section automatically. Only the Droplets reference conditions need to be set.

The reference conditions for the DROP3D-TURBO run are explained in Particle Conditions (p. 131).

9.3.4. Particle Initial Solution

Several options are available to initialize the solution domain on all components.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
268 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multiphase Droplet and Ice Crystal Simulations

[Link]. Initial Velocity Components

You can specify Velocity components in X, Y and Z directions.

[Link]. Specifying Velocity Angles

Velocity angles break up the reference velocity into X, Y and Z components.

[Link]. Vapor Initialization

Vapor field can be initialized with vapor concentration, relative humidity or wet bulb temperature.
Relative humidity ranges from 0 to 100%. It is defined as the ratio of the partial vapor pressure to
the saturation vapor pressure.

Figure 9.4: Initialization Using Vapor Concentration

Figure 9.5: Initialization Using Relative Humidity

Figure 9.6: Initialization Using Wet-Bulb Temperature

[Link]. Restarting from a Previous Solution

The particles solution can be restarted from a previous set of solutions by choosing the option
Solution restart in the Particle initial solution menu. Click the browse buttons to open the
file browser and select the particle solution file that corresponds to each component.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 269
FENSAP-ICE-TURBO

[Link]. User Defined Input Profile

A user defined timebc file can be generated to define LWC/ICC, velocities and temperature for
droplets and ice crystals entering the inlet of the first row. When the Input profile option is specified,
the values in the user defined data file take priority over those specified in the Boundaries of
FENSAP-ICE.

[Link]. Restart + Input Profile

This option is useful when previous solutions are available and a similar set of solutions are desired
with a new inlet condition. The inlet condition of the first row is provided by a user defined
timebc file. When the Restart + profile option is specified, the values in the user defined data
file take priority over those specified in the Boundaries panel of FENSAP-ICE.

Converged solutions from a different run are used to define the initial conditions for each component.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
270 of ANSYS, Inc. and its subsidiaries and affiliates.
 Ice Accretion in Turbomachines

[Link]. Dry Initialization

The Dry initialization option applies zero LWC/ICC/Vapor concentration to the entire domain except
the inlet boundaries and can be set by putting a checkmark in the box next it. Dry initialization
should always be enabled when simulating turbomachinery components to improve the rate of
convergence of DROP3D-TURBO solutions.

9.4. Ice Accretion in Turbomachines

The configuration parameters for ICE3D calculations have been described in ICE3D - Ice Accretion and
Water Runback (p. 171).

Icing calculations through set of turbomachinery components are simulated by choosing an ICE3D-
TURBO run in the New run dialog box. Each row is run sequentially to utilize maximum CPU usage per
row.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 271
FENSAP-ICE-TURBO

9.4.1. ICE3D-TURBO Physical Models

The necessary precursors before running icing calculations are:

• An airflow solution with specified isothermal wall boundaries

• EID data

• Droplet and/or Ice crystal solutions

A drag and drop of the configuration settings from a DROP3D-TURBO run to an ICE3D-TURBO run
sets up initial parameters (such as linking solution files, copying reference conditions, assigning icing
temperature).

The following sections outline the additional features exclusive to ICE3D-TURBO for the computation
of ice accretion in turbomachinery components.

[Link]. Icing on Rotating Components

Centrifugal and Coriolis source terms are included in the governing equations for ice accretion in
rotating components. The body forces are automatically activated by ensuring that component
rotation is enabled and that the rotation speed is set to a non-zero value in the Turbo panel.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
272 of ANSYS, Inc. and its subsidiaries and affiliates.
 Ice Accretion in Turbomachines

Drag & drop the config icon of the DROP3D-TURBO run onto the config icon of ICE3D-TURBO to
import the reference settings automatically.

If other flow solvers are used, then you need to review the input settings to ensure that rotating
components are set up correctly.

[Link]. Effect of Ice Crystals

The drag and drop of a Crystal and Droplet run from DROP3D-TURBO will set up ICE3D-TURBO to
run a simulation containing droplets and ice crystals. More options are available in the Ice crystals
menu of the Model panel.

To evaluate the impact of ice crystals on an icing calculation, you can choose to run a simulation
with exclusively droplets (Disabled), or exclusively with crystals (Crystals only) where the impact
of droplets will not be considered.

9.4.2. Boundary Conditions

The wall boundary labels in the Boundaries panel are color coded to identify the boundary condition
that has been applied.

[Link]. Enabled and Disabled Walls

All walls are Enabled for icing by default. An enabled wall boundary label appears grey in the
Boundary panel list and in the display window.

If the wall is Disabled, the color changes to dark grey. Disabled walls are omitted from the icing
calculation.

[Link]. Counter-Rotating Walls

Some walls in rotating components, such as the shroud, remain stationary in the absolute frame
of reference. Since rotating components are solved in the relative frame of reference, for each sta-

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 273
FENSAP-ICE-TURBO

tionary surface activate the Counter-rotating option in the Rotation section of the Boundaries
panel:

Counter-rotating walls are displayed in the boundaries list in yellow.

Counter-rotating walls experience a time-varying history, since the rotating components cause
periodic variations in the flow field and particle impingement as they move. The instantaneous
variation of these variables is circumferentially averaged to account for their time variation. Properties
received from FENSAP-TURBO and DROP3D-TURBO are pitch-averaged on the static counter-rotating
walls before starting an icing calculation.

Figure 9.7: Convective Heat Flux on the Turbofan Splitter Section Belonging to the Rotor
Stage Showing the Wake of the Rotor

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
274 of ANSYS, Inc. and its subsidiaries and affiliates.
 Ice Accretion in Turbomachines

Figure 9.8: Corresponding Pitch-Averaged Heat-Flux in ICE3D

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 275
FENSAP-ICE-TURBO

Figure 9.9: Collection Efficiency on the Turbofan Splitter Section Belonging to the Rotor Stage
Showing the Wake of the Rotor

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
276 of ANSYS, Inc. and its subsidiaries and affiliates.
 Ice Accretion in Turbomachines

Figure 9.10: Pitch-Averaged Collection Efficiency in ICE3D

[Link]. Sliding Wall Boundaries

Strong differences in the ice growth rate between neighboring surfaces may cause some wall
boundaries to become highly distorted, displace into each other, or move past the physical
boundaries of an adjoining surface.

Walls where ice accretion is much less dominant than their neighbors can be defined as sliding
boundaries, where ice growth is neglected to permit the adjoining surface grid to move only in a
tangential direction. For more information refer to Boundary Conditions (p. 73).

There are two sliding wall boundary condition options available to the user:

Enabled Sliding
This option allows the wall boundary to take part in the film flow and ice mass calculations, but it
will be omitted when carrying out grid displacement. The wall boundary will act as a sliding surface
for adjoining surfaces to slide on. The Enabled-Sliding option is identified in the boundary list and
appears in the display window as a light orange color.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 277
FENSAP-ICE-TURBO

The Enabled-Sliding option is useful in turbomachinery applications when defining a hub and
shroud boundary. This will allow the transfer of film between rotor-stator domains whilst allowing
ice growth on the blade to slide on hub and shroud interfaces.

Figure 9.11: Rotor Blade with the Hub Defined as a Sliding Surface

Figure 9.12: Blade Leading Edge Ice Displacement Along the Sliding Surface

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
278 of ANSYS, Inc. and its subsidiaries and affiliates.
 Ice Accretion in Turbomachines

Figure 9.13: Displaced Mesh (Red) on the Hub After 3D Mesh Movement

Disabled-Sliding
This option removes the wall boundary from both film flow and ice displacement calculations. The
boundary will only be used to allow adjoining surfaces to slide along its contour. The Disabled-
Sliding option is identified in the boundary list and appears in the display window as a dark orange
color.

The following example shows how a Disabled-Sliding boundary could be used. The geometry is
a fuselage-wing-pylon configuration. In this example, the icing on the wing is of interest. The fuselage
and pylon are defined as sliding boundaries.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 279
FENSAP-ICE-TURBO

[Link]. Water Pooling and Sinks

A pooling node is identified as a node where the film becomes stationary and accumulates indef-
initely. Pooling nodes are detected automatically by ICE3D-TURBO and the film on these nodes is
clipped to a maximum value determined by local aerodynamic conditions.

Sink nodes in ICE3D-TURBO include all nodes on a boundary that are identified by the Sink option
plus any node that touches the exit boundary. In a sink boundary, all nodes remain free of any film
and ice growth.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
280 of ANSYS, Inc. and its subsidiaries and affiliates.
 Computing Re-Injected Particles

9.5. Computing Re-Injected Particles

The primary particle flow computations do not account for the fact that some particles, such as ice
crystals and large droplets, can bounce off a surface and re-enter the flow. Crystals bounce off engine
components such as the shroud, nose-cone, splitter and the blades. The amount of bouncing crystals
can be significant and this is the mechanism that enables them to travel deep inside the compressor
core.

Likewise, water film can spray from rotating components such as the spinner, hub and blades and re-
join the flow. The particle reinjection options have been included to allow the modeling of these phe-
nomena.

The activation of Particle reinjection enables ICE3D-TURBO options for each component within the
DROP3D-TURBO configuration panels. A review of the ICE3D-TURBO options listed in Ice Accretion in
Turbomachines (p. 271) is highly recommended before configuring the re-injection models.

9.5.1. Simplified Reinjection

This option is available in the Particle reinjection menu of the Model panel of the DROP3D-TURBO
configuration.

The Simplified option determines the concentration of ejected particles and transfers it to the exit
plane of a component without the calculation of particle trajectories. Icing parameters must be set
when this option is activated. Only icing-activated wall boundaries will re-inject particles into the
flow.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 281
FENSAP-ICE-TURBO

9.5.2. Complete Reinjection

This feature is computationally expensive but provides a more accurate representation of the crystal
and film reinjection dynamics in a component. The option is available in the Particle reinjection list
of the Model panel of a DROP3D-TURBO run. Like the Simple reinjection option, icing parameters
need to be set up when this option is activated.

The Complete model uses the reinjected particle concentrations, velocities and temperatures generated
from an automated ICE3D-TURBO run to write a boundary condition file to treat wall boundaries as
inlets.

When the particle detachment zones are determined in ICE3D-TURBO, a second DROP3D-TURBO run
on the same component establishes the secondary particle trajectories from the wall to the exit. The
re-injecting wall boundaries are divided into several sub-sections. The Number of subdivisions
controls number of subsections that are divided in the axial direction. The default number of split
sections is set to 21. More subdivisions would increase the accuracy of the solution but can be com-
putationally expensive. The Spacing defines the type of spacing between subsections. Currently, only
a uniform spacing is available.

Note:

If you are trying to simulate reinjection due to bouncing crystals, ensure that either the
NTI Bouncing Model or NRC Bouncing Model is enabled. If you are trying to simulate
film shedding due to centrifugal force on moving components, the Beading model must
be activated to ensure that the critical bead height for detachment can be established.

9.6. Output Files

The solution for each component is saved in FENSAP format in the absolute frame of reference (See
FENSAP-ICE File Formats (p. 393) for format details). FENSAP-ICE writes the following output files for
each row XX in a given run. A list of files with its descriptions is provided below.

Table 9.5: Output Files

Files Filename Description

Common Files [Link] Log file giving a description of
the solver run history.
[Link] Contains solver convergence
data.
[Link]
[Link] Contains matrix solver
convergence data.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
282 of ANSYS, Inc. and its subsidiaries and affiliates.
 Specification of Mixed-Type Boundary Conditions

Files Filename Description

FENSAP-TURBO [Link] Solution file with flow variables
for each grid-point.
[Link] File containing heat fluxes on all
wall element faces (if the Energy
equation option is activated).
[Link] File containing forces acting on
all wall element faces (if the drag
direction is set).
DROP3D-TURBO [Link] Solution file containing droplet
variables for each grid-point.
[Link] Solution file containing ice crystal
solution variables for each
grid-point.
[Link] Solution file containing vapor
solution variables for each
grid-point.
[Link] File containing pitch averaged
information for droplets and ice
crystals for all interfaced exits.
ICE3D-TURBO [Link] Original surface grid file.
[Link] Displaced iced surface grid file.
[Link] Solution file containing ice
solution variables for each grid
point on the wall boundaries.
[Link] If 3D grid displacement is
enabled, a 3D displaced grid is
saved.
pitchdata_ice.rowXX File containing pitch averaged
data for droplets and ice crystals
with additional LWC/ICC
accounting for film reinjection
and/or ice crystal bouncing.

9.7. Specification of Mixed-Type Boundary Conditions

Boundary conditions for airflow, droplet and ice crystals can be specified using:

1. Input file: specified [Link] boundary file that is defined in the Conditions panel →
Boundary conditions file → Specify file ([Link]) section.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 283
FENSAP-ICE-TURBO

2. Note:

Specification of a filename overwrites any other boundary inputs from the boundary
conditions panel.

3. Boundaries panel:

Each variable on the boundary can be given either as:

• Specified value: specified value in the bounding box

• Functional input: functional dependence of the variable with X,Y and Z coordinates

• 1D radial file input: you generate a file that contains a radial distribution with the following format:
Number of points
Radial position Value
- -
E.g. data file for static temperature
5
0.000 285.0
0.143 265.6
0.150 330.6
0.424 340.2
0.500 500.0

The data file must be placed in the working project directory just outside the active run. In the
Boundaries panel, you can then select the 1D data file using the fileData1D (R,filename) input
command. The radial points are used to generate an interpolated [Link] file for the specified
boundary nodes.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
284 of ANSYS, Inc. and its subsidiaries and affiliates.
 Specification of Mixed-Type Boundary Conditions

Figure 9.14: Inlet Profile for Liquid Water Content Using the fileData1D Option

In DROP3D-TURBO, you can deactivate the application of boundary conditions for certain variables by
deactivating the check box next to the variable name. In this case, DROP3D-TURBO will inherit airflow
values for the unchecked variables on this boundary.

For example, in the panel below, the deactivation of Temperature, Velocity X, Y and Z implies that
the droplets will inherit the airflow temperature and velocity components at the inlet boundary.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 285
FENSAP-ICE-TURBO

Figure 9.15: Boundaries Panel in DROP3D-TURBO, with Checkboxes to Activate or Deactivate the
Imposition of User-Specified Boundary Conditions

9.8. Completing a Run

When the configuration of the FENSAP-ICE simulation is completed, click the Run button at the bottom
of the panel to go to the run environment. The run environment manages the configuration of the
parallel execution, the assignment to the queuing system and the monitoring of the key convergence
indicators.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
286 of ANSYS, Inc. and its subsidiaries and affiliates.
 Completing a Run

The Number of CPUS allocates the maximum number of processors available for the calculation. In an
airflow calculation, a sub-set of the total number of processors is assigned for each row.

If the sum of the processors used for each row does not correspond to the total number of processors,
FENSAP-ICE will prompt you to allow the automatic allocation of the processors, based on the number
of grid nodes present in each component.

To start the run, click the Run button. The view will automatically switch to the Execution panel. To
monitor the convergence in each row, click the Graphs panel. The convergence graphs of each row
can be selected by clicking the Row pull-down menu at the top of the panel.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 287
FENSAP-ICE-TURBO

Each row of the geometry has a full complement of convergence indicators to help monitor all aspects
of the calculation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
288 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 10: Automated Sequences and Multishot
Icing Calculations
The following sections of this chapter are:
10.1. Multishot Run Creation and Basic Configuration
10.2. Multishot Icing Sequences
10.3. Optigrid Feedback Loop

Some of the commonly performed operations in icing calculations and mesh adaptation are repetitive
and, if performed individually, would require a considerable amount of attention and labor, while also
increasing the risk of inadvertent mistakes creeping into the parameter configurations.

Automated sequences of multiple FENSAP/DROP3D/ICE3D runs, multiple runs with different parameters
and automated feedback loops condense the configuration of the parameters and the execution into
a single, simple and efficient setup:

Figure 10.1: Single Run

Figure 10.2: Multiple Runs

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 289
Automated Sequences and Multishot Icing Calculations

Figure 10.3: Multishot Ice Accretion

10.1. Multishot Run Creation and Basic Configuration

Automated sequences can be easily created and configured, and look very similar to the CHT3D runs
created in CHT3D - 3D Conjugate Heat Transfer (p. 225).

10.1.1. Creating the Run

A multishot run is created by selecting the Sequence run type in the New run dialog window, as
shown in The Run Manager (p. 19), followed by clicking the Configure button:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
290 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Run Creation and Basic Configuration

A new window will appear showing a listing of the available sequence types. Select the desired type
and provide a label in the New run name box:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 291
Automated Sequences and Multishot Icing Calculations

The available multishot types are:

Table 10.1: Multishot Types

MULTI-FENSAP A multishot sequence executing FENSAP, DROP3D

and ICE3D in order to simulate the total icing time
subdivided into shorter portions (shots), while
updating the grid between shots to account for
the ice growth.
MULTI-FLUENT Similar to MULTI-FENSAP, but using Fluent
for the flow solution instead of FENSAP.
MULTI-CFX Similar to MULTI-FENSAP, but using CFX for
the flow solution instead of FENSAP.
ADAPT-FENSAP Execution of FENSAP and OptiGrid in a closed loop.
ADAPT-FENSAP-DROP3D Execution of FENSAP+DROP3D and OptiGrid in a
closed loop to adapt the grid using both air and
droplet flow solution variables.
ADAPT-DROP3D Execution of DROP3D and OptiGrid in a closed
loop.
ADAPT-DROP3D-CRYSTAL Execution of DROP3D and OptiGrid, with the
Particle type set to Crystal

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
292 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Run Creation and Basic Configuration

Once FENSAP is configured, you can drag-and-drop the FENSAP config icon onto the DROP3D con-
figuration icon and similarly, from DROP3D onto ICE3D. This operation will copy the shared parameters.
Remaining non-shared parameters will need to be edited after dragging-and-dropping.

10.1.2. Defining the Input Grid

In a multishot sequence, all the solvers must share the same initial grid; therefore the first step in the
configuration is the selection of the initial grid. The initial grid can be defined in many ways: drag-
and-drop a grid file onto the grid icon from an existing run in the same project; double-click the grid
icon to open the file browser; right-click the icon and select Define in the menu; open the main
configuration file and select the grid file with the file browser.

Once the grid file has been defined, all the configuration icons will turn blue.

10.1.3. Configuring the Solvers

The solver modules can be configured from scratch, or by dragging-and-dropping from other runs
in the same project.

• Double-click a config icon to configure its corresponding run;

• Drag-and-drop the config icon of the source run onto the corresponding icon of the target solver;

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 293
Automated Sequences and Multishot Icing Calculations

• Copy (Ctrl+C) and paste (Ctrl+V) the configuration icon from another run.

Note:

The grid of the source configuration run does not need to be the same as the grid in the
main config file; however for a perfect copy of the settings, the boundary condition list
must be identical. If this is not the case, review the boundary conditions to ensure their
correctness.

The input and output files of the run will not be changed by this operation.

Once FENSAP is configured, you can drag-and-drop the FENSAP config icon onto the DROP3D con-
figuration and similarly, from DROP3D onto ICE3D. This operation will copy the shared parameters.
Other, non-shared, parameters will need to be edited.

In multishot configurations, there is no need to specify any setting for the input and output file names;
the file names are automatically defined by FENSAP-ICE. For example, in DROP3D:

FENSAP-ICE is warning that an input airflow solution file is required but does not exist; the solution
file will be created at runtime by FENSAP and managed automatically. This warning can be ignored,
it is not necessary to specify this file name or to modify the automatic configuration.

10.1.4. Setting up the Initial Solution

Multishot can be launched with no initial solutions, but in order to speed-up the first cycle, it is possible
to specify restart solutions for each solver in the loop. This restart solution will be used for the first
cycle of the multishot iteration.

Right-click the config icon of each solver and enable the restart solution for the selected solver:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
294 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Run Creation and Basic Configuration

Alternatively, the restart can be set up in the Initial solution configuration panel:

10.1.5. Multishot Primary Configuration

Double-clicking the main config icon opens the configuration window:

[Link]. Multishot Iterations

The default setup of the multishot run is a single iteration. Each iteration is a full sequence of
solvers (FENSAP-DROP3D-ICE3D, for example).

It is possible to add more iterations and define specific values for some of the configuration para-
meters at each iteration with the Add iteration and Add variable buttons:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 295
Automated Sequences and Multishot Icing Calculations

The Add iteration button will copy the Total time set it in ICE3D as the iteration duration. To
simplify the process, set the time value to the desired shot length in ICE3D prior to adding new it-
erations.

[Link]. Variable Values

Double-clicking one of the iterations in the list opens a window that allows the assignment of
specific values:

[Link]. Variables
The Add variable button will permit the definition of additional variables for each iteration.

Additional variables will appear in new columns.

[Link]. Restart Types

The default setting is to restart from the previous iteration.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
296 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Run Creation and Basic Configuration

10.1.6. Execution
Launch the execution using the Run button in the configuration dialog, or the Run menu in the
project window.

Once launched, the execution window will present a log and a convergence graph for each of the
solver iterations:

10.1.7. Post-Processing
The View button allows the selection of a specific output file and iteration to display. Depending on
the type of multi-shot sequence, the files available for viewing are the new grids, air/droplet/icing
solutions, etc. The results can be viewed using Viewmerical or CFD-Post, based on the selection made
in the Preferences menu of the project main window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 297
Automated Sequences and Multishot Icing Calculations

10.2. Multishot Icing Sequences

As ice accretes on aircraft surfaces, the geometry of the surfaces exposed to the incoming air and droplet
flow changes, leading to changes of surface heat fluxes, collection efficiency, shear stresses, etc. In case
of internal flows, ice can increase the blockage of passages between blades and other internal walls.
To capture the effects of surface geometry change due to icing, the computational grid and the air and
droplet solutions need to be updated frequently. The multishot icing approach splits the ice accretion
duration into shorter sequential steady-state shots, modeling the unsteady ice accretion in a quasi-
steady manner. The durations of the shots are user-defined. After each shot, the grid is updated either
by morphing or by remeshing to conform to the new ice shape, also providing surface roughness in-
formation if the ICE3D beading model is enabled. The airflow solution is computed again using the
previous shot’s solution as a restart. Similarly, the droplet and/or ice crystal solutions are updated and
a new ICE3D solution follows. Multishot icing options are provided separately for FENSAP, Fluent, and
CFX airflow solvers.

10.2.1. Multishot with FENSAP

In a MULTI-FENSAP sequence, the computational grid is updated after the surface is displaced with
ice at each shot. One of the mesh update methods available is to displace the node coordinates
without changing the topology of the original grid. The other option is to remesh the surface and
the volume to help maintain a proper surface grid resolution and quality and provide a better mesh
for the next shot. In both cases, FENSAP, DROP3D, and ICE3D are executed in sequence followed by
a grid displacement/remeshing step before moving onto the next shot. The following table lists the
steps done at each shot.

Table 10.2: Solvers

FENSAP Will use the new displaced grid and its own air
solution on the previous grid as a restart.
DROP3D Will use the displaced grid, the new air solution
from FENSAP and its own droplet solution on the
previous grid as a restart.
ICE3D Will use the displaced grid, the new solutions
from FENSAP and DROP3D. ICE3D itself will
restart from the previous ice shape and
surface icing solution automatically (film
height, bead height, surface temperature,
etc.), no manual setup option is necessary.
Grid Displacement The grid will be morphed or remeshed based on
the type of grid displacement selected. Several
options are available: ALE displacement for mesh
displacement with constant topology, Remeshing
- Optigrid to remesh only the iced parts with
OptiGrid (called internally by FENSAP) and
Remeshing - Fluent Meshing to automatically

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
298 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

remesh the entire grid using meshing journal files

for Fluent.

Tip:

For guess-free, accurate computations of ice shapes, select the Beading model in the
ICE3D config file (See Impact of Beading (p. 179)) to automatically transfer the spatially-
and temporally-evolving roughness data to the airflow module at the end of each shot.
The initial roughness height can be specified as a small constant value (k s≈0.5 mm), or
from one of the various sandgrain roughness correlations provided by the FENSAP module.
This initial value will be automatically overwritten after the end of the first shot.

The multishot procedure can also be started from a clean surface by specifying a sand-grain roughness
height of zero, however a number of additional shots of short duration should be added to properly
start the procedure.

[Link]. MULTI-FENSAP
The configuration of a multishot icing simulation uses FENSAP, DROP3D, and ICE3D configurations
as building blocks, where each module is configured separately with the possibility of dragging
and dropping the reference settings from one solver to the next. The shot duration is set in the
main multishot configuration panel, but to facilitate the shot entries the total icing time in the
ICE3D configuration can be set to the shot length intended. In this manner adding multishot itera-
tions, or shots, will copy this time as the iteration (shot) length.

The mesh update options are found in the Out panel of the ICE3D configuration.

Using ALE Displacement to update the mesh by morphing significantly faster than remeshing
since the topology and number of nodes remain constant and no solution interpolation between
grids is necessary. However, not updating the grid topology has several limitations. Since the
number of nodes remains constant, this method tends to coarsen the surface grid as ice accretes.
Due to fixed mesh topology between shots, this method is not very effective in capturing complex
glaze ice shapes. Due to these limitations, this approach often requires manual remeshing after a
certain amount of automatic shots to maintain appropriate mesh and solution quality. However,
this method is still able to capture rime ice shapes well since the ice shape usually conforms to the
original shape of the aircraft surface.

When Remeshing - Optigrid option is selected, the iced surfaces and a small cavity extracted
around them are remeshed. The cavity size is proportional to the local thickness of the ice. During
remeshing, FENSAP calls the OptiGrid grid adaptation and smoothing tool in the background after
morphing the mesh. OptiGrid runs in grid smoothing mode with predefined settings to resurface
the iced parts of the mesh, with the aim to maintain local grid density while refining high-curvature
zones. The remeshing operations are done in parallel. The limitations of this remeshing method
are listed below:

• Only 3D unstructured (prism+tetra) grids are supported.

• Prism layers in the entire grid must have equal number of layers.

• Pyramids are not allowed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 299
Automated Sequences and Multishot Icing Calculations

• The total height of the prism layer cannot be high (i.e. suggested maximum total prism
layer < ½ leading edge radius for wings).

• Non-conformal interfaces that cut through iced surfaces cannot be handled.

• Geometry topological changes cannot be handled (hole closure due to blockage, ice bridging
over control surfaces, gaps, etc.)

• End wall + blade icing in internal flow simulations cannot be handled due to iced surface
mesh folding at intersections.

• Will require manual remeshing in case the simulation fails due to remeshing errors.

For best practices in mesh generation, the grid provided in the remeshing workshop can be used
as reference. The total prism height per chord length, number of layers, initial cell height per chord
length, and surface mesh distribution of that grid can be used as recommended settings.

The Remeshing – Fluent Meshing option is the most sophisticated remeshing method available
where all the limitations listed above for OptiGrid remeshing are lifted and wall boundary bridging,
gap closing, and other geometry topology changes are supported. This option calls Fluent with a
prescribed meshing journal file that is generic enough to deal with a wide range of mesh configur-
ations. The remeshing step first executes a shell script that includes running Fluent and carrying
out restart solution interpolations once the new grid is ready. To learn more about remeshing with
Fluent Meshing, please visit section Automatic Remeshing Using Fluent Meshing (p. 323).

10.2.2. Multishot with Fluent

The MULTI-FLUENT sequence is defined around an initial Fluent case file (.cas(.h5)).

[Link]. Input Grid Configuration

Double-click the input grid and select the initial Fluent .cas(.h5) file; the file should be in the
same directory as the .dat(.h5) file with the initial solution.

This operation will open the FLUENT-to-FENSAP Grid converter; this will convert the grid to the
FENSAP format, for use with DROP3D and ICE3D.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
300 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

If the default choices for the boundary condition types are not suitable, select the correct FENSAP
boundary condition type for each of the Fluent zones. In the next panel, the numerical parameters
can be kept to their default values. When done, click Next.

In the next panel, the Reference parameters can be kept to their default values, which are the
Reference Conditions of Fluent, or modified. It is suggested to keep these default values if you
followed the recommendations in Recommendations to Set up a Fluent Calculation (p. 303) regarding
the setup of the Reference Conditions in Fluent.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 301
Automated Sequences and Multishot Icing Calculations

The last panel will convert the grid to FENSAP format, the View button helps to double-check the
grid conversion and boundary condition types, using the internal 3D viewer.

[Link]. Fluent Configuration

All Fluent input parameters must be set up in the case (.cas(.h5)) file; FENSAP-ICE does not
permit the modification of the Fluent input parameters.

The config icon for the Fluent run will enable the selection of some Fluent-specific run parameters:

Table 10.3: Fluent Configuration Window

Number of iterations Fluent will execute for the specified number of

iterations.
Solve energy-only The journal file will contain a command to disable
the flow and turbulence computation, however
the FLUENT Turbulence type (if any) must be
specified in the text box.
Under-relaxation factor If specified, the Under-relaxation factor will be
applied to the temperature computation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
302 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

FLUENT executable Assuming that the default Fluent executable

cannot be found in your $PATH environment
variable, it allows the selection of the full path to
the Fluent executable.
Parameters The command line arguments used to launch
Fluent. To use the double-precision solver, use
the 3ddp flag instead of 3d flag. Do not remove
the –g –I $JOURNAL options. In the Windows
operating system, the command line should also
contain the –wait flag.
Additional journal-file commands For experienced Fluent users. Click the ? button
for more information.

[Link]. Recommendations to Set up a Fluent Calculation

This section provides recommendations for obtaining a steady-state airflow solution Fluent that is
suitable for icing simulations with FENSAP-ICE. It outlines models, settings and inputs that will
produce results as consistent as possible to those obtained with the FENSAP airflow solver that has
been used in numerous validation cases for icing simulation predictions.

Inside your Fluent run:

• Select General from the side menu and ensure the Solver is set to Type: Pressure-Based, Velo-
city-Formulation: Absolute and Time: Steady.

• Select Models from the side menu.

– Ensure that Energy is turned On.

– Under Viscous, change the Model to k-omega (2eqn) and then to SST under k-omega
Model. To produce viscous effects as consistent as possible to those in the FENSAP airflow
solver:

→ Enable Viscous-Heating and Production Limiter in the Options section.

→ Change the Energy Prandtl Number and Wall Prandtl Number to 0.9 and the Production
Limiter Clip Factor to 10 in the Model Constants section.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 303
Automated Sequences and Multishot Icing Calculations

• Select Materials from the side panel and, under Fluid, select air. By default, FENSAP models air
as an ideal gas. Therefore,

– Set the Density to ideal-gas.

– Set the Cp (Specific Heat) (j/kg-k) to 1004.688 J/kg/K. This value is equal to 7/2 R. In FENSAP,
the gas constant R is 287.05376 J/kg/K.

– Set the Thermal Conductivity to constant. To compute its value, refer to The Energy Equa-
tion (p. 55) and replace T in the equation by the static ambient air temperature.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
304 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

– Set the Viscosity to constant. To compute its value, refer to The Continuity and Momentum
Equations (p. 54) and replace T in the equation by the static ambient air temperature.

Note:

If beading is disabled in ICE3D, the initial Fluent roughness settings will be preserved
throughout the shots.

→ If the initial Fluent solution was computed using a serial or parallel solver execu-
tion, the same parallelization setting should be used in the subsequent multishot
execution. Fluent might reorder the nodes of the grid, when switching between
serial and parallel execution, making the reordered grid unsuitable for FENSAP-
ICE restarts. You should always use the parallel version of Fluent, to avoid mis-
matches.

• Under Boundary Conditions

– On the inlets of the computational domain that represent ambient conditions:

→ Set the Turbulence Intensity to 0.08% (based on Effective Inflow Conditions for Turbulence
Models in Aerodynamic Calculations paper by Philippe R. Spalart and Christopher L. Rumsey.
"Effective Inflow Conditions for Turbulence Models in Aerodynamic Calculations", AIAA Journal,
Vol. 45, No. 10 (2007), pp. 2544-2553.)

→ Set the Turbulent Viscosity Ratio to 1e-05 (consistent with FENSAP’s default Eddy/Lam-
inar viscosity ratio).

– On the walls that are prone to icing:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 305
Automated Sequences and Multishot Icing Calculations

→ In the Momentum panel, set the Shear Condition to No Slip and the Wall Roughness to
High Roughness (Icing). Specify a Roughness Height equal to 0.5 mm in the Sand-Grain
Roughness sub-panel to start your icing simulations. This height is automatically updated
at every shot if beading is selected in ICE3D. For more information regarding the High
Roughness (Icing) roughness model, consult Additional Roughness Models for Icing Simu-
lations within the Fluent User's Guide.

→ In the Thermal panel, set the Thermal Conditions to Temperature. Specify a Temperature
equal to the Adiabatic stagnation temperature + 10 K. See Reference Conditions (p. 67)
to compute this parameter.

• Under Reference Conditions, use the ambient airflow properties to set the Reference Values.
This provides consistency with the workflow of FENSAP-ICE and facilitates subsequent setup of
DROP3D, ICE3D and CHT3D calculations since these Reference Values must be used as Reference
parameters during the Fluent to FENSAP format conversion (See Fluent Configuration (p. 302))
and as Reference Conditions in the Conditions panel of DROP3D or an ICE3D simulations.

• Under Solution Methods, you should set the Pressure-Velocity Coupling scheme to Coupled
and to select at least a Second Order or Second Order Upwind scheme for the Spatial Discret-
ization of the governing equations.

• Monitor your solutions, especially surface static pressures, shear stresses and convective heat
fluxes. It is important to obtain smooth continuous solutions of these fields as they play a major
role during ice accretion.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
306 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

[Link]. DROP3D and ICE3D Configuration

DROP3D can accept the converted Fluent airflow solution as input; however the correct reference
conditions and other physical quantities must be provided to DROP3D and ICE3D, and must be
identical to those specified for the Fluent solution. FENSAP-ICE does not automate this process;
these values must be defined manually and you must ensure their correctness.

If you followed the recommendations in Recommendations to Set up a Fluent Calculation (p. 303),
the correct reference air conditions in DROP3D and ICE3D should have been automatically populated
in these simulations.

[Link]. Multishot Configuration

The multishot configuration is similar to that for FENSAP-DROP3D-ICE3D. However, the Fluent run
can be set up for a different number of iterations for each step:

Use Add variable and select the FLUENT - FLUENT-iterations variable.

[Link]. Execution
When Fluent is executed, the log will be available in the run panel of FENSAP-ICE:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 307
Automated Sequences and Multishot Icing Calculations

The Fluent output file will be named [Link], and then the file will be renamed to an iteration-
specific file name and converted to FENSAP format.

The following files will be created at each multishot iteration:

• [Link]

• [Link]

• [Link].00000X

[Link]. Post-Processing
The .cas(.h5) file for each iteration can be post-processed using the Fluent graphical-user inter-
face or CFD-Post. The airflow solution, converted to FENSAP format, as well as the other DROP3D,
ICE3D output files can be visualized using the View with Viewmerical button.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
308 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

10.2.3. Multishot with CFX

The MULTI-CFX sequence is defined around an initial CFX .res file.

[Link]. Input Grid Configuration

Double-click the input grid and select the initial CFX .res file.

This operation will open the CFX-to-FENSAP Grid converter, which will convert the grid to FENSAP
format for use with DROP3D and ICE3D.

If the default choices for the boundary condition types are not suitable, select the correct FENSAP
boundary condition type for each of the CFX zones. In the next panel, the Datafields parameters
can be kept to their default values. Click Next.

Note:

If you are performing a MULTI-CFX simulation using automatic remeshing with Fluent
Meshing, there are additional requirements for the boundary and domain names that
should be used in the CFX setup. Refer to the note related to CFX in Automatic
Remeshing Using Fluent Meshing (p. 323).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 309
Automated Sequences and Multishot Icing Calculations

In the next panel, the Reference parameters can be kept to their default values or modified. It is
suggested to keep these default values if you followed the Recommendations to Set up a CFX
Calculation (p. 312).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
310 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

The last panel will convert the grid to FENSAP format, the View button allows you to double-check
the grid conversion and boundary condition types, using the internal 3D viewer.

[Link]. CFX Configuration

All CFX input parameters should have already been set up in the .res file; FENSAP-ICE does not
permit the modification of the CFX input parameters.

Note:

Only execution parameters can be modified.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 311
Automated Sequences and Multishot Icing Calculations

CFX Execut- This allows the selection of the full path to the CFX executable, when the default
able CFX executable cannot be found in your $PATH environment variable.
Parameters This section describes the command line arguments used to launch CFX in
batch mode, -batch flag. The flag -par-local indicates that the CFX simulation
will use the local host parallel CPUs or processors. The $NCPU indicates the
number of processors employed. The value of NCPU is taken from the number
of CPUs specified in Execution Settings of your multishot configuration.

EXTRA_CFX_ARGS (Optional): If an environment variable has been defined,

the $EXTRA_CFX_ARGS will be replaced by its value.

For more details on the CFX command line, refer to Command-Line Options
and Keywords for cfx5solve in the CFX-Solver Manager User's Guide.
CCL Settings For experienced CFX users.

[Link]. Recommendations to Set up a CFX Calculation

This section provides recommendations for obtaining a steady-state CFX airflow solution that is
suitable for icing simulations with FENSAP-ICE. It outlines models, settings and inputs that will
produce results as consistent as possible to those obtained with FENSAP, the airflow solver of
FENSAP-ICE that has been widely used in numerous icing validation cases.

Inside your CFX run:

• In the top menu bar, go to Edit and select Options.... In CFX-Pre → General → Beta Options
→ Physics Beta Features, check mark Enable Beta Features.

• For every CFD Domain located on the side menu bar under Simulation → Flow Analysis, right-
click the domain name and select Edit to modify the following sub-menus:

– Inside Basic Settings:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
312 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

→ Select Air Ideal Gas as the Material of your Fluid Domain. By default, FENSAP models air
as an ideal gas.

→ Use the ambient static pressure of your simulation as Reference Pressure.

– Inside Fluid Models:

→ Select Total Energy and activate Incl. Viscous Work Term under Heat Transfer.

→ Select Shear Stress Transport and checkmark Blended Near Wall Treatment (Beta) under
Turbulence.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 313
Automated Sequences and Multishot Icing Calculations

• If the bounding region of your CFD Domain is an Inlet that represents ambient conditions:

– In the Boundary Details panel, set Turbulence → Option to Intensity and Eddy Viscosity
Ratio.

→ Set Fractional Intensity to 0.0008 (based on Effective Inflow Conditions for Turbulence
Models in Aerodynamic Calculations paper by Philippe R. Spalart and Christopher L. Rumsey.
"Effective Inflow Conditions for Turbulence Models in Aerodynamic Calculations", AIAA Journal,
Vol. 45, No. 10 (2007), pp. 2544-2553.).

→ Set the Eddy Viscosity Ratio to 1e-05 (consistent with FENSAP’s default Eddy/Laminar
viscosity ratio).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
314 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

• If the bounding region of your CFD Domain is a Wall that is prone to icing:

– In the Boundary Details panel, set the Mass And Momentum to No Slip Wall.

– Set the Wall Roughness to High Roughness (Icing) and specify a Sand Grain Roughness
height equal to 0.5 mm to start your icing simulation. This height is automatically updated
at every shot if beading is selected in ICE3D. Otherwise, it is preserved. For more information
regarding the High Roughness (Icing) roughness model, consult Wall Roughness.

– Set the Heat Transfer to Temperature and specify a Fixed Temperature equal to the Adia-
batic stagnation temperature + 10 K. See Reference Conditions (p. 67) to compute this
parameter.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 315
Automated Sequences and Multishot Icing Calculations

• On the side menu bar panel, you should use the following solver settings located in Simulation
→ Flow Analysis → Solver → and double-clicking Solver Control.

– Inside Basic Settings:

→ Set the Advection Scheme and Turbulence Numerics to High Resolution.

→ Keep the default settings of the Fluid Timescale Control. The default settings should be
Auto Timescale for the Timescale Control, Conservative for the Length Scale Option and
a Timescale Factor of 1.0.

→ Under Convergence Criteria, set its Residual Type to RMS and its Residual Target to 1e-
20 to promote convergence.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
316 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

– Inside Equations Class Settings:

→ If oscillations of shear stress and heat flux are observed on the Walls of the Domain and if
the cause of these oscillations is not linked to the geometry or the mesh refinement of the
CFD simulation, you should change the Convergence Control of the turbulence and energy
equations to Local Timescale Factor and to use a factor of 1 or a factor below 5.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 317
Automated Sequences and Multishot Icing Calculations

• On the side menu bar panel, double-click the default Air Ideal Gas properties located under
Simulation → Materials.

– Inside Basic Settings:

→ Set air as a Pure Substance with Material Group equal to Calorically Perfect Ideal Gas.

– Inside Material Properties:

→ Select General Material under Option.

→ Specify the following Thermodynamic Properties:

• In the Specific Heat Capacity sub-menu, specify the Specific Heat Capacity to 1004.688
J/kg/K and the Specific Heat Type to Constant Pressure. The value of the specific heat
capacity at constant pressure is equal to 7/2 R. In FENSAP, the gas constant R is 287.05376
J/kg/K.

• In the Transport Properties sub-menu, use The Continuity and Momentum Equa-
tions (p. 54) to compute the Dynamic Viscosity and The Energy Equation (p. 55) to
compute the Thermal Conductivity. In both equations, replace T by the static ambient
air temperature.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
318 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

• On the top menu bar, select Execution Control, and select Double Precision in the Run
Definition panel.

• CFX does not have a menu to define reference airflow conditions. Therefore, during the CFX to
FENSAP format conversion, inlet airflow boundary conditions and/or solution are automatically
selected by the graphical user interface of FENSAP-ICE as reference conditions. However, to set
the reference pressure condition, specify its value inside the Reference Pressure field located
in the Domain panel of CFX. In general, the airflow reference conditions should correspond to
the ambient airflow properties of the CFD simulation. If this is not the case, new reference con-
ditions can be defined during the CFX to FENSAP file conversion. See Input Grid Configura-
tion (p. 309).

• Monitor your solutions, especially surface static pressures, shear stresses and convective heat
fluxes. It is important to obtain smooth, continuous solutions of these fields as they play a major

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 319
Automated Sequences and Multishot Icing Calculations

role during ice accretion. See the Solver Control recommendations located at Recommendations
to Set up a CFX Calculation (p. 312).

Note:

If you are performing a MULTI-CFX simulation using automatic remeshing with Fluent
Meshing, there are additional requirements for the boundary and domain names that
should be used in the CFX setup. Refer to the note related to CFX in Automatic
Remeshing Using Fluent Meshing (p. 323).

[Link]. DROP3D and ICE3D Configuration

DROP3D can accept the converted CFX airflow solution as input; however, correct reference condi-
tions and other physical quantities of air must be provided to DROP3D and ICE3D. The default airflow
parameters suggested by DROP3D and ICE3D are not the most appropriate for your icing simulation.
If you followed the recommendations in Recommendations to Set up a CFX Calculation (p. 312), the
correct reference air conditions in DROP3D and ICE3D should have been automatically populated
otherwise, you should use the ambient airflow conditions to manually define the reference conditions
and other physical quantities of air inside DROP3D and ICE3D.

[Link]. Multishot Configuration

The multishot configuration is similar to that for FENSAP-DROP3D-ICE3D, however, the CFX settings
cannot be modified at each shot through this configuration panel. Therefore, the original CFX settings
are preserved during the entire multishot calculation.

[Link]. Execution
When CFX is executed, the log will be available in the run panel of FENSAP-ICE:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
320 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

CFX output files will be named using an iteration-specific suffix that considers the shot number.
These files will then be converted to FENSAP format.

The following files will be created at each shot:

• [Link] is the CFX airflow solution file in CFX format.

• [Link] is the CFX displaced mesh solution file in CFX format.

• [Link].00000X is the CFX airflow solution file in FENSAP format.

• [Link].00000X is the CFX displaced mesh solution file in FENSAP format.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 321
Automated Sequences and Multishot Icing Calculations

[Link]. Post-Processing
All .res files in the graphical user interface of FENSAP-ICE can be post-processed using CFD-Post
by right-clicking the CFX solution and by selecting View with and then CFD-Post. The airflow
solution, converted to FENSAP format, as well as the other DROP3D and ICE3D output files can be
visualized using Viewmerical.

10.2.4. Multishot with Custom Remeshing

It is possible to provide a custom prepared remeshing script for all the above described multishot
icing simulations if desired. With a custom remeshing script, a user can sequence a grid generation
procedure to be executed in batch with their preferred meshing tool, using the ice surface STL grid
files as CAD inputs over the original surfaces.

Such a script should be designed to perform the following steps:

• Copy the last STL file (i.e. [Link]) generated by ICE3D to a common temporary
name (i.e. [Link]).

• Execute a meshing software that loads the base grid, the [Link] file, and replaces the walls with
those from the STL file, and fully or partially remeshes the grid.

• Convert the grid to FENSAP format.

• Interpolate air and droplet solutions from the previous grid to the new grid to serve as restart
solutions.

• Interpolate the surface roughness file from the previous grid to the new grid.

• Perform cleanup and error checking operations along the way to stop the execution if an error
occurs.

The Custom remeshing option can be activated in the Out panel of the ICE3D configuration of a
multishot simulation. When Custom remeshing mode is used, the grid displacement step of the
multishot simulation will be replaced with the line provided in the Remesh command, as shown in
the figure below.

The first item in the Remesh command above specifies the bash script file used to control the custom
remeshing procedure. This must be provided by the user and placed inside the run directory. Following

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
322 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

this, there are a number of shell variables that will be used inside the script. These shell variables are
available in the Custom remeshing mode to allow the user to access the grid files necessary to perform
the remeshing procedure. These variables will automatically contain the correct shot number associated
with the previous or next shot of the multishot simulation. Inside the user’s custom remeshing script,
the shot number can also be extracted from these names using standard bash script commands. The
following variables are available to the user:

• $grid_input: contains the name of the initial grid used in the multishot ice accretion simulation
(ex: [Link])

• $grid_previous: contains the file name of the grid used in the previous shot of icing (ex:
[Link].000002)

• $grid_output: contains the file name of the grid that will be used in the next shot of icing (ex:
[Link].000003)

• $grid_map / $grid_ice: contains the file names of the map and ice grids used by ICE3D in the
previous shot of ice accretion (ex: [Link].000002, [Link].000002)

• $grid_stl / $grid_tin: contains the file names of the stl and ICEM format CAD files produced by
the previous shot of ice accretion (ex: [Link], [Link])

• $grid_bc: contains the file names of the boundary condition files used in the previous shot of ice
accretion (ex: [Link].00002)

The last portion of the Remesh command shown above directs all screen outputs from this scripted
procedure to be written into the .[Link] file, which contains all screen outputs from the
entire multishot remeshing simulation.

[Link]. Automatic Remeshing Using Fluent Meshing

Fluent Meshing is a powerful meshing tool with the possibility of automation and scripting of
complex meshing operations. It is able to mesh ice surfaces with challenging topologies.

Example Fluent remeshing scripts to replace the grid displacement steps of MULTI-FENSAP and
MULTI-FLUENT and MULTI-CFX simulations are provided in the data/templates/remeshing
directory of the FENSAP-ICE installation folder. Depending on the simulation type and operating
system, the appropriate files are automatically copied to the run directory. These script files are
named custom_remeshing.sh, and are tagged for use with FENSAP, Fluent and CFX airflow
solvers as well as with Windows and Linux operating systems. In these example scripts, Fluent
Meshing is called with a journal file to perform the remeshing procedure. The journal file, named
[Link], controls the remeshing steps using a very generalized and automated meshing
technique. Additionally, the journal file calls a [Link] file, which contains required
case specific meshing parameters, such as minimum and maximum element sizes. Finally, a
[Link] file is included to support future developments related to Fluent remeshing
workflows. These example journal and sizing files are also located in the data/templates/remesh-
ing directory.

In order to use this example custom remeshing procedure using Fluent Meshing, choose Remeshing
– Fluent Meshing in the grid displacement menu, and switch the Template to Default. For MULTI-
FENSAP and MULTI-FLUENT, the Template should be set to Default. For MULTI-CFX, the Template
should be set to CFX.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 323
Automated Sequences and Multishot Icing Calculations

The prism layer growth operation can be executed in parallel if number of remeshing CPUs is set
larger than 1.

The table of mesh settings displayed in this window are the contents of the [Link]
scheme file that Fluent meshing will use to grab the user defined minimum/maximum edge length
specifications, number of prism layers, etc. The explanation of these parameters are provided below:

• globmin, globmax: minimum and maximum global element size.

• proxmin: minimum element size used in the proximity surface mesh controls.

• curvmin, curvmax: minimum and maximum element size used in the curvature surface meshing
controls.

• nprisms: number of prism layers to generate on all wall boundaries, used in the prism meshing
controls.

• firstCellAR: the aspect ratio of the first prism layer, used in the prism meshing controls.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
324 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

• mpx, mpy, mpz: X-, Y- and Z- coordinate of a point located in the area where you would like to
create the volume mesh.

• periodicAngle: the periodic angle used in rotationally periodic meshes.

• periodicCenterX,Y,Z: the periodic center point used in rotationally periodic meshes.

• periodicZones: The rotational periodic zones in FENSAP-ICE are 5000-type BCs. For Fluent
Meshing to treat these as periodic, the remeshing journal file queries the BC names in the variable.
By default, this list contains zone5* which should be kept as is. For MULTI-CFX, they should be
renamed as zone5000* or zone5001*.

Note:

To enable rotational periodicity, [Link] file in the simulation directory

needs to be edited to uncomment the relevant section.

• periodicTranslationVx,Vy,Vz: For translational periodic cases, these provide the periodicity

vector from one side to the other.

• periodicTranslationZones: Similar to rotational periodicity, this variable contains the list of BC

families that will be used as translational periodic in Fluent Meshing. The list by default contains
zone5* which means all 5000-type BCs and should be left as is for most applications. For MULTI-
CFX, they should be renamed as zone5000* or zone5001*. The zone name and number used
should be the one from which the translational periodic vector starts. For example, if the periodic
pair points from zone5001 to zone5000 with vector (0,-1,0), the zone5001 must be used, vice
versa.

Note:

To enable translational periodicity, [Link] file needs to be modified by

uncommenting the relevant section.

Based on user needs and their experience with Fluent Meshing, the journal file can be enhanced
and customized to include more specialized sizing functions, refinement zones bodies of influence,
hard-set mesh sizing for certain boundaries, etc. In its most basic form, the provided journal file
should be able to handle long duration glaze icing cases for external icing simulations on wings,
nacelles, multi-element airfoils, complete aircraft configurations, etc., provided that the user properly
determines the meshing sizes that will prevent the collapse of sharp features like trailing edges.

Note:

• Walls should be separated into different zones at corners or joints. Doing so will ensure,
sharp edges of the geometrical model will be preserved after wrapping. For example,
if the tip cap of a wing is placed in the same boundary family as the rest of the wing,
the corners will be smoothed during the wrapping operation, which should be avoided.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 325
Automated Sequences and Multishot Icing Calculations

• Grid file format conversions are carried out using fluent2fensap and
fensap2fluent command line tools. The -zonebc option should be used during
conversions to maintain FENSAP boundary condition family IDs by converting them
to zone#### format in the *.cas(.h5) file and back to 4 digit #### format in the
FENSAP grid file. Otherwise, the FENSAP boundary IDs may get reshuffled, resulting
in incorrect settings for the next shot.

• When using Fluent as the airflow solver with this custom remeshing script, in your
initial .cas(.h5) file, you must first edit your boundary names to the zone####
format. Make sure to use FENSAP boundary conditions numbering format (ex:
zone1000s for inlets, zone2000s for walls, zone3000s for exits, zone4000s for symmetry
and zone5000s for periodic boundaries).

• When using CFX as the airflow solver with this custom remeshing script, you must
modify your initial .res file in CFX-Pre.

1. First, make sure that only one 3D region/domain exists in your .res file. The current
MULTI-CFX supports only one domain for external icing simulations.

– If you would like to use the geometry from a multi-domain mesh, it is recom-
mended to go back to the tool used to generate the mesh and create a new
mesh with a single domain represented by a continuous fluid domain.

2. Change the Principal 3D Regions names to internal.

3. Make sure that all BCs under Principle 2D Regions are Assembly BC type; the
Composite BC type of CFX is not supported. In case there are Composite BC types
in your .res file, you may need to re-define their BC type in your meshing process
or to go to CFX-Pre → Fluent (save as cas) → CFX-Pre to change the BC type
from composite to assembly.

4. Set the Principle 2D Regions names and Boundary names to the zone####
format. Make sure to use FENSAP’s boundary conditions numbering format (ex:
zone1000s for inlets, zone2000s for walls, zone3000s for exits, zone4000s for sym-

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
326 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

metry). Each Boundary name must be linked only to its corresponding Principle
2D Region with the same name. For example, if you have a wall boundary with
Boundary name zone2000, in its Basic Settings → Location, the Principle 2D
Region, also called zone2000, must be selected.

5. MULTI-CFX supports only one pair of periodic BCs in a 3D external region/domain.

Periodic BCs must be named as zone5000 and zone5001. When your .res file
has Interfaces with periodic BCs, you must change your periodic interface’s name
to Periodic, and re-name the two corresponding BCs as zone5000 and zone5001
under Principle 2D Region. Then, make sure that the two Periodic Sides of Inter-
faces Periodic are referring them, respectively.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 327
Automated Sequences and Multishot Icing Calculations

• The custom remeshing scripts are set to use the AWP_ROOT211 environment variable
to launch ANSYS tools. This variable is automatically set by the ANSYS installer as the
default ANSYS directory. However, if this is incorrect, you may correct this variable in
your environment before launching FENSAP-ICE, or in your custom_remeshing.sh
script (for example: export AWP_ROOT211=/path/to/ansys_inc/v211/).

The Fluent Meshing scripts will carry out the following operations:

• Convert the script inputs ($grid_input, $grid_next…) to simple variables to be used throughout
the script.

• Extract the previous and next shot numbers (ex: 000002, 000003) from these variables.

• Clean up and remove any files that exist from previous simulations.

• Create a [Link] file containing all boundaries from the initial mesh that will be used during
the remeshing operation.

• Copy the most recent iced geometry STL file to a general [Link] name for use during the
remeshing operation.

• Call Fluent Meshing with the [Link] journal file to perform the remeshing operation,
creating a new mesh ([Link] and [Link]).

• Convert the [Link] file to FENSAP format, using the -zonebc option to preserve the
boundary names.

• Interpolate the FENSAP and DROP3D and roughness solutions onto the new grid.

The example [Link] journal file performs the following steps within Fluent Meshing:

• Read the original grid converted to Fluent format, called [Link], as a boundary mesh
omitting volume cells.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
328 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

• Remove the wall boundary zones – they will be replaced by zones coming from the [Link]
file.

• Triangulate quad elements on any boundary zones, like symmetry planes.

• Import the [Link] file from the current shot.

• Specify curvature and proximity based sizing functions.

• Extract boundary zone outer edges - (do not extract features based on angles as this might also
extract unwanted ice surface sharp edges).

• Create a material point to initiate surface wrapping projections.

• Wrap the entire domain using the computed sizing function

– This is the surface remeshing step.

– Wrapping feature is well automated and smooths the surface while wrapping over features
smaller than the local sizing function.

– Local sizing function controls the level of smoothing and defeaturing that will take place
during wrapping.

– The outcome of wrapping is always a high quality, low skewness surface mesh.

• Specify prism layer settings.

• Auto mesh the volume, creating prism layers and filling the rest with tetras.

• Write the new mesh file and exit.

Using Custom Fluent Meshing Journal Files

Based on user needs and their experience with Fluent Meshing, the journal file can be enhanced
and customized to include more specialized sizing functions, refinement zones bodies of influence,
hard-set mesh sizing for certain boundaries, etc. There are currently two recommended ways to
manage adding these enhancements to the remeshing journal files.

The first option it select the Template -> Default option, which will copy the default remesh-
[Link] files to the current run directory. Next, a user can open the [Link] file and
add any modifications required to the Fluent remeshing script. This option may be preferred if the
user would like to make quick adjustments to the default template for use in the run of interest.
However, in this case the UI Template option will still be listed as Default, so care should be taken
when setting up new runs in the same project to ensure the proper file is used in each run. For
example, if a user drag and drop’s the configuration from a run containing a modified default
[Link] template, the modified [Link] file will be copied to the new run’s
directory. To reload the default template, select (…) → Reload Template to the right of the Template
option box.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 329
Automated Sequences and Multishot Icing Calculations

A second option is to setup a custom remeshing script and load it into the run. First, create a
remeshing_templates folder inside the simulation project directory. Next, place the following
files into your remeshing_templates folder:

• [Link]: this file is required so that the template can be automatically recognized
by the UI. For now, it can simply be an empty text file. (In the future, this file will allow for
further Fluent meshing workflow developments).

• [Link]: this file should contain the complete Fluent Meshing journal commands
to perform the remeshing operation within Fluent Meshing.

• [Link]: this file should contain the mesh size information

requested by the user. It will be loaded into the table accessible inside the UI, and accessed
by the journal file above during the remeshing process.

Note:

The customname portion of the filenames above can be whatever the user desires,
it is simply a requirement that the same string is used.

Once the files above are placed in the remeshing_templates folder, they will then be accessible
inside the Template selection box. Choosing the custom template will copy the files into the current
run. If the custom template is at first not available, close and then re-open the ice config to have
the user interface auto-check for new remeshing templates.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
330 of ANSYS, Inc. and its subsidiaries and affiliates.
 Multishot Icing Sequences

Figure 10.4: 45-Minute Glaze Icing on a Full Aircraft with Slats and Flaps Deployed, 9 Shots

Figure 10.5: 22-Minute Glaze Ice on a Swept Wing, 22 Shots

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 331
Automated Sequences and Multishot Icing Calculations

Figure 10.6: 22-Minute Icing on a Swept Wing, Mid-Span Surface Mesh, Pressure Side (Top)
and Suction Side (Bottom)

10.3. Optigrid Feedback Loop

In a sequence with OptiGrid, the mesh adaptation will run on the current step grid and solution (airflow,
droplet, combined), and write an adapted grid.

Note:

ADAPT-FENSAP-DROP3D will enable the combined solution output, DROP3D will write a
droplet with air solution file, which contains both droplet and air solution. This file will be
used as input by OptiGrid, enabling the adaptation to use fields from both airflow and droplet
solver in multi-scalar adaptation. The interpolated solution produced by OptiGrid also contains
all datafields, and will be used in the subsequent FENSAP and DROP3D restarts.

FENSAP airflow fields: PRES, XVEL, YVEL, ZVEL, TEMP, VIST, etc. (See The FENSAP Solution File – Binary
Format (p. 400)).

DROP3D solution fields: DRUU, DRVV, DRWW (Droplet velocity), DRVF (LWC), BETA (Collection efficiency).

ICE3D output files can be visualized using Viewmerical.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
332 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 11: FENSAP-ICE-Unsteady
The following sections of this chapter are:
[Link]-Phase Flows: Coupling Flow and Droplets
[Link]-Phase Flows: Coupling Flow, Droplets and Ice
11.3. Rime Ice Accretion on Screens
11.4. Rigid Motion

This chapter describes the multiphase model of FENSAP-ICE-Unsteady that couples the flow, droplets
and/or ice equations into a single multiphase code. The coupled flow and droplets equations are solved
time-accurate, with ice accretion displacing the mesh and changing the surface conditions as time ad-
vances.. The mesh displacement due to icing is incorporated into the Arbitrary Lagrangian Eulerian
method which transforms the governing equations on moving and morphing grids. On top of mesh
morphing due to iced surface displacement, rigid motion can be prescribed to the entire grid to calculate
flows over moving bodies that undergo icing, (i.e. pitching and plunging airfoils).

You are invited to read FENSAP - Flow Solution (p. 53) and ICE3D - Ice Accretion and Water Run-
back (p. 171) for a description of all input parameters of, respectively, FENSAP, DROP3D and ICE3D. This
chapter only highlights input parameters directly related to multiphase flows and that differ from the
other solvers.

11.1. Two-Phase Flows: Coupling Flow and Droplets

The conservation of mass and momentum can be defined from the one fluid formulation for multiphase
flow:

where the subscript refers to gas and to droplet particles. The right-hand side ( ) terms include
the effects of air on droplets and of droplets on air.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 333
FENSAP-ICE-Unsteady

In this equation, the time derivative terms account for mesh displacement using the Arbitrary Lagrangian
Eulerian (ALE) formulation.

During in-flight icing conditions, the droplets volume fraction (ag) is of the order of 10-6. Therefore the
air volume fraction (ap) can be considered constant and equal to one and the air-droplets flow is viewed
as a dilute gas particle system, where only the effects of air on droplets are accounted for. The resulting
equations for air:

and droplets:

correspond in essence to the governing equations of the icing codes FENSAP, for air, and DROP3D, for
droplets impingement. The main difference in this work is that the one-way-coupled equations are
solved together in time.

11.1.1. The Physical Model

Select Air + Droplets under Physical model to solve for the coupled flow and droplets equations as
a multiphase flow.

In the case of unsteady calculations, the Energy equation option should be set to Full PDE mode.
Transition to turbulence or sand-grain roughness can be imposed as well.

11.1.2. Steady-State Multiphase Flows

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
334 of ANSYS, Inc. and its subsidiaries and affiliates.
 Two-Phase Flows: Coupling Flow and Droplets

To improve the performance of the iterative matrix solver, the terms associated with the temporal
operator of the equations can be added to the Jacobian matrix (these terms do not affect the residuals).

The addition of these terms, proportional to , increases the diagonal dominance of the Jacobian
matrix and improves the convergence of the iterative solver. The solution is then advanced in time
until the time derivative terms become zero, or the flow field reaches steady-state.

The choice of the local time step, for an element, is based on the stability analysis of the explicit-Euler
centered finite difference scheme, which provides a maximum theoretical . The time step is then
selected as:

The solution is advanced in time, with a that varies from one cell to another, until steady-state is
reached. Only one Newton iteration is performed to linearize the system at each time step. The linear
matrix system is solved using a GMRES approach.

To select this option, click Steady. Enter the CFL number for air (from 50 to 1,000, default 100) and
for droplets (between 1 and 50, default 2), and the maximum number of time steps. The calculation
ends if either the maximum number of time steps or the convergence residual level criteria have
been reached.

Tip:

Reduce the CFL number if convergence problems are encountered.

11.1.3. Unsteady Multiphase Flows

Two time stepping schemes are available for unsteady time-accurate simulations.

[Link]. Constant Time Step

Select Unsteady - Constant time step to solve for an unsteady flow using a constant time step.
Set the time step and the total solution time, both in seconds. The solution is advanced in time
using a second-order Gear scheme. The non-linear governing equations are linearized by performing,
at each time step, a given number of Newton linearization loops (default 5). The solver then moves

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 335
FENSAP-ICE-Unsteady

to the next time step if either the number of Newton iteration per time step is reached or, the
convergence residual level criteria is satisfied. The calculation stops at the end of the total time.

Note:

The convergence of the GMRES solver is closely linked to the time step, since the time
derivative term affects the diagonal dominance of the linear matrix system. Reduce the
time step if the GMRES solver is not converging more than two orders of magnitude.

[Link]. Dual-Time Stepping

Select Unsteady - Dual time stepping to solve for an unsteady flow using a dual time approach.
Set the physical time step and the total solution time, both in seconds. The solution advances in
physical time using a second-order Gear scheme. At each physical time step, the non-linear governing
equations are converged in pseudo-time using a local time stepping technique with a constant
CFL number. Make sure to perform enough pseudo-time iterations (default 4) to ensure solver
convergence. The calculation stops at the end of the total physical time. It is important to use the
same CFL number for airflow and droplet calculations so that they advance in similar fashion during
each physical time step. For example, if the DROP3D CFL number is lower than the CFL number
of the air flow, the droplet solution may not converge sufficiently and calculation can be comprom-
ised.

11.1.4. Output Files

Even if the flow and droplets solutions are coupled, their solutions will be saved in two separate files.
Enter the name of the airflow solution file in the Air box, and the droplets solution file in the Droplets
box. Select Overwrite to save solutions every N iterations in the same files. Select Do not overwrite
to save solutions every X iterations in different numbered files.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
336 of ANSYS, Inc. and its subsidiaries and affiliates.
 Three-Phase Flows: Coupling Flow, Droplets and Ice

11.2. Three-Phase Flows: Coupling Flow, Droplets and Ice

For icing calculations, the unsteady air-droplets model introduced in Two-Phase Flows: Coupling Flow
and Droplets (p. 333) is complemented by the Messinger model to compute accretion speed and to dis-
place the surface grid in time.

The resulting system of coupled equations can be solved for inviscid (Euler equation) or viscous
(Navier-Stokes) flows. For rime ice accretion, inviscid flow with constant total enthalpy is sufficient to
guarantee accurate results. For glaze ice, however, the viscous equations should be complemented by
the one-equation Spalart-Allmaras turbulence model to predict accurate shear stresses and by the full
energy equation to compute heat fluxes on the walls.

11.2.1. Rime Ice

In the Model panel select Rime to activate rime ice growth in the Icing model section.

At very low temperatures, droplets impinging on the surface freeze on impact and therefore contribute
directly to ice formation. This assumption represents a simple mass balance between droplets impinge-
ment and ice accretion:

where is the rate of ice accretion in kg/m2s. The surface displacement vector is computed
from the accretion speed (always normal to the iced surface):

as

where is the ice density and is the physical time step. The accretion speed is imposed as
boundary conditions to the diphasic and mesh deformation models.

The ice density can be set either to Constant (default 917 kg/m3) or computed using Macklin formula:

for 0.2 < RM < 170, where

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 337
FENSAP-ICE-Unsteady

11.2.2. Glaze Ice

Select Glaze - Advanced to activate glaze icing.

This model couples the flow and droplets equations in time with the glaze icing model of FENSAP-
ICE, described in ICE3D - Ice Accretion and Water Runback (p. 171), which solves for local water film
height (h), temperature (T) and accretion rate of ice ( ). As for the rime icing model (See Rime
Ice (p. 337)), the accretion speed is obtained directly from the ice accretion rate and used as input to
displace the iced surface in time in the ALE formulation.

The ice density can be set either to Constant (default 917 kg/m3) or computed using the Macklin
formula.

The heat fluxes are computed by FENSAP at each physical time step. They are then directly affected
by ice growth in time and the resulting changes in boundary layer characteristics. Choose between
Gresho heat flux type (default) and the Classical (k·dT/dn) form. Water and ice are the default media,
and their thermodynamic characteristics are automatically supplied to FENSAP-ICE-Unsteady.

The Relative humidity is expressed from 0 (0%) to 1 (100%, or default). For clouds, this value should
be set to 1 (or 100%). Otherwise, enter the relative humidity of the icing tunnel, as determined during
the experiment.

11.2.3. Output Files

Since icing is an unsteady phenomenon, the different solutions should be saved at fixed intervals in
time, and in separate files numbered by the iteration number. These include:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
338 of ANSYS, Inc. and its subsidiaries and affiliates.
 Rime Ice Accretion on Screens

1. The flow solution file

2. The droplets solution file

3. The displaced grid in function of the ice shape

4. The CAD of the iced geometry saved in ICEM CFD TETIN format

5. The CAD of the iced geometry saved in .stl format

11.2.4. View Ice Accretion in Time

The evolution of the iced surface in time can be visualized in the graphical window during convergence

of the unsteady solver. For this, click to display both the initial grid (all solid surfaces) and iced
surface on top of each other.

11.3. Rime Ice Accretion on Screens

This model combines the screen model and pressure drop correlations of FENSAP with FENSAP-ICE
Unsteady for droplets impingement and ice accretion. You should refer to FENSAP - Flow Solution (p. 53)
for guidelines on how to set up the screen geometry and input parameters. In the boundary condition
menu, select Enabled under Icing to activate this model.

Note:

In order to enable screen icing, the solver should already be set to Unsteady. Only then
screen icing will be configurable.

The initial wire diameter grows as the screen collects ice, increasing blockage and pressure and reducing
LWC. The screens may be of any orientation and shape. The screen icing model uses the droplet flow
direction and the screen surface normal orientation to compute a local collection efficiency at every
point on the screen, and determines the ice accretion and wire diameter growth rates. The collection

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 339
FENSAP-ICE-Unsteady

efficiency of the screen and the wire diameter distributions are available in droplet and soln files
from DROP3D and FENSAP.

The screen model (See Screen Models (p. 88)) is not designed to work with 100% blocked screens and
can give rise to convergence problems if this happens. You are advised to monitor the unsteady screen
icing run and stop it before the wire diameter becomes excessive, or, discard the solutions after which
the blockage factor has become excessive. Saving numbered solution files is therefore highly recom-
mended with screen icing simulations.

Figure 11.1: Collection Efficency on the Intake Screen of a Helicopter Engine

Figure 11.2: Wire Diameter on the Intake Screen of a Helicopter Engine

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
340 of ANSYS, Inc. and its subsidiaries and affiliates.
 Rigid Motion

11.3.1. Mass Loss in the Droplet Continuity Equation

This screen icing model is complemented by introducing an extra term that represents the mass of
droplets impinging on the iced screen on the right-hand side of the droplet continuity equation. The
term represents the amount of water going through the screen and, therefore, the water collection
pattern downstream of the screen. The continuity equation of the droplets can be written in the weak
integral form (using integration by part) as:

where is the Liquid Water Content and is the droplets velocity vector. A surface integral, evalu-
ated only on the screen itself, is added to this governing equation to subtract the water captured by
the screen (a droplet sink):

The constant indicates the ratio of mass caught by the screen to the total mass of incoming
droplets.

11.4. Rigid Motion

The Rigid Motion option can be activated to efficiently simulate unsteady flow on bodies undergoing
cyclic motion, like oscillating airfoils that undergo pitching and plunging motions. Instead of morphing
the grid to account for the motion of the solid, the entire grid moves with the prescribed motion. This
is a cost-effective approach as it does not solve for mesh deformation during unsteady calculations.
The option is found in the Out panel in the ALE mode menu:

The provided rigid motion option has two modes that can be superimposed, translation and rotation
about an axis. The translation mode is expressed in terms of grid velocity (m/s) and the rotation mode
is expressed in terms of the actual rotation angle relative to the original grid orientation. Both modes
use the sine trigonometric function, and with the help of the phase lag entry, sine can be converted

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 341
FENSAP-ICE-Unsteady

to cosine using a phase lag of 0.25 periods. In the rotation section, the axis of rotation and the pivot
point must be provided along with the amplitude and the frequency of the motion.

Note:

The far-field boundary should be set as Riemann when applying rigid motion. This will allow
the far-field boundary nodes to seamlessly switch between inflow/outflow states during the
motion.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
342 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 12: OptiGrid - Mesh Adaptation
The following sections of this chapter are:
[Link] Background
12.2. Input Files
12.3. Boundaries
12.4. Adaptation Strategy
12.5. Mesh Constraints
12.6. Performing Mesh Adaptation
[Link]

12.1. Theoretical Background

Below are examples of OptiGrid's theoretical background.

12.1.1. Error Estimation in 1D

In order to adapt a grid to minimize the error throughout the computational domain, OptiGrid first
needs to estimate the difference or error, e(x), between the exact solution g(x) and the numerical
solution gh(x) of a given flow problem on a grid of size of O(h):

Of course, for most problems, except those with an exact solution, the error can only be estimated,
as g(x) is generally unknown.

The global error e(x) has various sources:

1. Error resulting from the discretization of a continuum over a finite grid.

2. Grid-related errors, such as inappropriate grid distribution and misaligned grids.

3. Geometric approximations of solid boundaries.

4. Addition of stability and convergence enhancers, such as artificial viscosity, damping, smoothing
and upwinding.

5. Incomplete convergence of the flow solver should it slow down or stall.

6. Computer round-off error.

A grid adapted by OptiGrid will minimize error sources 1 to 3, as new grid points will be placed or
displaced, automatically, where needed to accurately capture the flow characteristics. For error sources

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 343
OptiGrid - Mesh Adaptation

4 and 5, experience indicates that the flow solver usually requires less and less artificial viscosity as
the grid gets optimized and, in addition, that convergence of the flow solver is improved. Round-off
error is intrinsic to numerical calculations and is unaffected by OptiGrid.

OptiGrid is based on minimizing the difference between the PDE and its discretized form. Using a
1D Taylor expansion of both the exact (PDE) and numerical solutions (discretized), the truncation
error can be estimated within an element, in 1D, to be:

where h is the element size and x is a local coordinate within the element (0,h). The error estimate
over one element is computed as the maximum of e(x):

This indicates that the error is a direct function of the second derivative of the solution and not, as
is used by many other mesh adaptation tools, a function of the gradients (first derivatives). This es-
timator is therefore a truer representation of the problem error.

12.1.2. Error Estimation in 3D

The truncation error, derived for the 1D case, can be extended to 3D by considering the coordinates
of each edge of the mesh, or

where is the edge length and is the tangential direction of that edge. The second derivatives of
the numerical solution are computed along the direction of an edge from

where

This error estimate is edge-based and the derived error estimate can therefore be computed for any
element type (hexahedral, tetrahedral, prismatic, or pyramidal).

Furthermore, information about the error direction can be derived from the eigenvectors R of the
Hessian matrix H, allowing anisotropic adaptation. In a shock, for example, cells will automatically be
stretched by OptiGrid along the discontinuity direction, therefore requiring fewer grid points to ac-
curately capture the shock than if isotropic adaptation was performed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
344 of ANSYS, Inc. and its subsidiaries and affiliates.
 Theoretical Background

12.1.3. Adaptation Strategies in 3D

Several adaptation strategies are implemented in OptiGrid. These are categorized as follows:

• Moving Nodes:

Equidistribute the error throughout the domain by moving the position of the grid points.

• Refinement:

Reduce the error throughout the domain by adding new grid points where the error is higher than
a target error threshold.

• Coarsening:

Equidistribute the error throughout the domain by removing grid points where the error is lower
than the target error threshold.

• Edge Swapping:

Reconnect edges to optimize their orientation and to better align the grid to unidirectional flow
features.

The best strategy is a combination of all four operations to minimize and make the error uniform
everywhere, while maintaining an acceptable number of grid points (memory requirement). Node
movement is the only continuous operation and it may be viewed as the driving force of mesh adapt-
ation. Refinement, coarsening, and edge swapping are binary (yes/no) operations that complement
the action of node movement and should be viewed as a way to accelerate convergence to an optimum
grid.

The next figure shows a typical distribution of the error density on the edges, normalized by the target
error. The threshold levels for coarsening, swapping and refinement are set at (1-σc), (1+σs) and (1+σr),
respectively.

Figure 12.1: Distribution of the Normalized Error Density

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 345
OptiGrid - Mesh Adaptation

[Link]. Node Movement

In the node movement strategy, all edges connected to a given node xj are viewed as a network
of springs, with stiffness constants proportional to the edge-based error, or

where is the n node connected to node . The ideal position of node is then computed from
a nonlinear energy minimization problem:

where

This equation is nonlinear and therefore, its solution is based on the iterative algorithm

which starts from an initial guess and converges gradually to the location of equilibrium .
The input parameter ω is a relaxation factor.

Note:

The movement of one grid point modifies all the surrounding elements. For this reason,
the node movement strategy should be repeated several times throughout the domain.

[Link]. Refinement and Coarsening

The mesh is refined if the error estimate on a given edge exceeds the target error by more than
σr. In this case, a new node is introduced in the middle of the edge, and the connectivity of the
nodes is updated accordingly. On boundary curves and surfaces, the new or collapsed node is
projected back onto the CAD description of the boundary of the computational domain. Conversely,
the mesh is coarsened if the error estimate on a given edge is below the coarsening threshold (1-
σc). In that case, the edge is simply deleted and its two end points are collapsed, or merged, into
a single point.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
346 of ANSYS, Inc. and its subsidiaries and affiliates.
 Theoretical Background

[Link]. Edge Swapping

The edge swapping algorithm implemented in OptiGrid swaps the edges that connect a set of
nodes. The optimal configuration is selected such that the error along the edges is minimized. A
minimum aspect ratio in the Euclidean space must also be respected. Swapping is applicable to
tetrahedral elements and to columns of prismatic elements. It is not supported for hexas and pyr-
amids.

The role of swapping is to accelerate the alignment of edges with one-directional flow features
such as shocks and boundary layers.

Tip:

Swapping an edge modifies the surrounding elements. For that reason, the edge swapping
strategy should be repeated several times throughout the domain.

12.1.4. Adaptation Sequence

OptiGrid adapts the grid in the following sequence:

1. Node movement is performed on boundaries to smooth out the grid on surfaces. This may be
repeated several times, based on the user input.

2. Edge refinement and swapping on boundaries are performed according to a user-specified curvature
criterion so as to better represent regions of high curvature.

3. Node movement is performed in the entire computational domain, including boundaries.

4. Edge refinement and coarsening are performed simultaneously in the entire domain, including
boundaries.

5. Edge swapping is performed in the entire computational domain, including boundaries, in order
to optimize the shape of elements. This is repeated several times based on the user input.

6. Node movement is performed in the entire computational domain, including boundaries, in order
to smooth the adapted mesh (repeated several times based on the user input).

Note:

Sequence 1 to 6 is referred to as one main iteration. Many main iterations can be performed
by OptiGrid, based on the user’s input. If the initial grid is well suited to the flow, the mesh
adaptation may require no more than 3 main iterations. If the initial grid is uniform or very
coarse, the mesh adaptation may require up to 15 main iterations.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 347
OptiGrid - Mesh Adaptation

12.2. Input Files

12.2.1. Initial and Adapted Grids

Solution interpolation permits to choose if an interpolated solution file is written along the adapted
grid. Not writing the solution file permits to save disk space.

• Disabled: No output solution file.

• Enabled: (Default) Interpolated solution file is written.

• Subset of fields - for restarts: A minimum amount of datafields are written to the output file. This
is useful to reduce the output file size, while retaining the capability to use the file as a restart.

Note:

Available for Fluent only (V, P, T, TKE, SDE fields are only written when this option is selec-
ted).

The grid file format can be set to:

Grid Description
Format
FENSAP FENSAP-ICE file format described in FENSAP-ICE File Formats (p. 393).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
348 of ANSYS, Inc. and its subsidiaries and affiliates.
 Input Files

Select the input mesh file with the browse button. Enter the name and complete path of the adapted
grid (the output of OptiGrid).

12.2.2. Initial Flow Solution

Select the input flow solution file with the browse button. The flow solution type can be set to:

• No solution: This option should be selected when only mesh smoothing is performed by OptiGrid.
No solution files are required in this case.

• FENSAP: FENSAP-ICE file format described in FENSAP-ICE File Formats (p. 393).

• FLUENT: In this case, the .dat(.h5) file should be loaded.

Note:

The base filename for both .cas(.h5) (grid) and .dat(.h5) (solution) files must
be the same directory.

GENERIC: FENSAP-ICE simplified format for mesh adaptation, described in FENSAP-ICE File
Formats (p. 393)

Important:

The solution file format should be the same as the mesh file format.

12.2.3. Assign Flow Variables for Error Estimation

In this section you will set up and assign flow variables for error estimation within OptiGrid.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 349
OptiGrid - Mesh Adaptation

[Link]. Scalar Variables

Variable sets the flow variable that is used to compute the error estimate:

• Single scalar allows selecting one variable from the input solution file, all listed under Datafield.
The list of variables can be modified in the Advanced menu.

• Multiple scalars option allows you to select more than one variable from the solution file. For
this option, OptiGrid combines the contribution of all selected variables in error approximation.
The list of variables in the solution file is provided as a list of check boxes.

The Mach number is computed by OptiGrid from the input flow solution as:

where is the gas constant set to 1.4.

The Magnitude of velocity is computed by OptiGrid from the input flow solution as:

The Magnitude of vorticity is computed by OptiGrid from the input flow solution as:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
350 of ANSYS, Inc. and its subsidiaries and affiliates.
 Input Files

If Expression is selected, OptiGrid constructs the scalar to be used for error estimate based on the
expression supplied by you.

The expression can be a single field or a function of any of the flow variables present in the input
solution file. Each of them should be referred to using its corresponding solver label in the solution
file. The equation should be built using the provided variables, functions and operators:

Finally, select Mesh smoothing for grid smoothing only (no input solution provided).

[Link]. Edit Variable Labels

Click the Advanced toolbar to specify the label of each input flow variable.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 351
OptiGrid - Mesh Adaptation

Specify opens a new window:

to create links between labels of the flow variables in the input solution file and OptiGrid’s standard
names, in order to ensure full compatibility between the flow solver and OptiGrid.

Note:

If the flow is incompressible and the density field is not stored in the solution file, a nu-
meric value can be entered. In this way, the Mach number and Y+ will be properly
defined.

[Link]. Guidelines
The flow variable used to compute the error should be chosen so as to best capture the desired,
determining or dominant flow characteristics. The following guidelines help in selecting the appro-
priate flow variable:

For a subsonic Euler flow (without shocks), almost any sensible variable should work.

For a transonic or supersonic Euler flow (with shocks), the pressure is a good adaptation variable
since it experiences a jump across each shock. The Mach number and density may also be used
advantageously, because they can detect both shocks and contact discontinuities.

For subsonic Navier-Stokes solutions (without shocks), the Mach number can be used as the adapt-
ation variable to capture the boundary layer, since the velocity gradient is strong normal to a wall.
Using pressure as the adaptation variable is not recommended, since the pressure gradient is very
weak across a boundary layer. However, to adapt for both the Mach number and the pressure, you
must either use the Multiple scalars adaptation or define an expression of these variables.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
352 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundaries

For transonic Navier-Stokes solutions (with shocks), no ideal choice for the adaptation variable is
obvious, as the Mach number is often not sensitive enough to capture shocks properly, giving too
much emphasis to boundary layers. In this case it is suggested to use a combination of the Mach
number and pressure using the Multiple scalars option or by defining a custom expression of
these variables.

For the solutions with multiple separation zones, it is suggested to choose the Multiple scalars
adaptation and then select all velocity components in order to capture separation lines accurately.

12.2.4. Geometry (CAD)

Enter the name and location of the geometry filename to be created by OptiGrid. You can also load
a previously saved CAD file using the browse icon.

Click Generate to automatically create a suitable CAD for the input mesh. This operation may take a
few moments depending on the size of the grid.

For more advanced CAD operations, click View/Edit. Detailed guidelines on how to use the CAD re-
construction tool are presented in OptiGrid - CAD Reconstruction (p. 377).

12.3. Boundaries
In this section you will view and edit boundary layers, adjust Global Y+ settings and use advanced options
within OptiGrid.

12.3.1. View and Edit the Boundary Surfaces

Checkmark to select each labeled surface present in the grid file. The selected boundaries are shown
in the graphical window.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 353
OptiGrid - Mesh Adaptation

12.3.2. Y+ Adaptation
Global Y+ settings determines the constraints within which OptiGrid must operate when adapting
layers of prismatic or hexahedral elements based on Y+ values. Use Enabled to activate Y+ adaptation.

Note:

If the grid has prismatic layers: After the CAD construction step, OptiGrid will set up auto-
matically a Constant height setting onto the detected boundaries, along with the number
of layers defined in the grid.

If no Y+ adaptation is activated, all elements, including any prismatic elements, will be

adapted in the same way, based on the solution error. In this case, the thickness and shape
of the prism layer will not remain constant from the initial grid to the adapted grid. For
this reason, it is suggested that Y+ surfaces be selected for turbulent flows.

[Link]. Number of Layers

Select the Number of prism/hexa layers. For hexahedra grids, only elements within the prescribed
number of layers close on the selected walls will be affected by Y+ corrections. The other elements
will be adapted based on the error estimate.

Prisms are generally used in hybrid grids (with tetrahedral elements) to improve grid quality and
orthogonality near walls. In this case, enter the total number of prisms normal to the wall, or
within the prism layer.

[Link]. Y+ Label

This option is available only for Specified Height option in the Y+ prism/hexa section (See Con-
straints on Hexahedral/Prismatic Elements (p. 354)).

The Y+ variable should be read from the input flow solution. Select YPLS for Y+ datafield.

[Link]. Constraints on Hexahedral/Prismatic Elements

Different options are offered for hexahedral and prismatic (hybrid) grids:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
354 of ANSYS, Inc. and its subsidiaries and affiliates.
 Boundaries

Constant height maintains the height of the layers at its original value.

Specified height allows controlling the height of the layers directly by setting limits on the Y value
(normal distance from the wall) of the nodes in the selected layers. For this, select a Lower Y bound
and an Upper Y bound. These parameters indicate the Y value (not the Y+ value) of the first node
from the wall and of the last node in the layers. OptiGrid scales the height of the layers so that the
outer nodes satisfy these bounds and the node distribution within the layers satisfies the
equidistribution principle of the error.

Specified height from Y+ allows controlling the height of the layers indirectly by setting limits on
the Y+ value of the nodes. Select a Lower Y+ bound and an Upper Y bound. These parameters
indicate the Y+ value of the first node and the Y value of the last node from the wall. OptiGrid
scales the height of the layers so that the outer nodes satisfy the bounds and the node distribution
within the layers satisfies the equidistribution principle of the error.

The height of the first layer is reduced to the Max height of first layer if it exceeds its limit. The
clipping is intended to occur in regions of very small Y+ (leading edge stagnation point, reversed
flow separation point) in order to prevent large cells from being created. In such a case, the target
lower Y+ bound may not be respected.

Note:

For centroid-based finite volume solvers, the Y+ values may be averaged at the centroid
of the first cell on the wall. Care must be taken to differentiate the Y+ displayed by the
CFD solver’s post-processor and the Y+ defined at nodes by OptiGrid.

[Link]. Transition

Transition detection is used to detect zones where very small Y+ occur (leading edge stagnation
point, reversed flow separation point) in order to use the solution error as the criterion for adaptation
in these regions instead of Y+. This prevents large cells from being created in these critical flow
regions. This option should be used only with layers of prisms or hexahedra when logarithmic wall
functions are used by the turbulence model. In the current version, this treatment is available only
when there is more than one layer of prisms or hexahedra.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 355
OptiGrid - Mesh Adaptation

[Link]. Constraints on Tetrahedral Elements

Y+ adaptation can be applied to unstructured tetrahedral meshes. Specified height or Specified

height from Y+ may be specified if the height is to be controlled in terms of, respectively, Y or Y+.
For the chosen method, the lower and upper limits of the boundary layer must be entered (Wall
thickness Y or Y+, Total thickness Y or Y+) as well as a Growth ratio inside the boundary layer.
No correction can be used to switch off Y+ adaptation in tetrahedral cells above layers of prisms
if it is not desired to extend the Y+ adaptation beyond the prisms.

The possibility to adapt the tetrahedral cells above the prisms is most useful when only one layer
of prisms is used. Specified height can be used effectively with mesh smoothing to generate more
cells in the boundary layer on no-slip walls.

12.3.3. Advanced Options

More options can be specified for each boundary by clicking the Advanced options toolbar.

[Link]. Dead Zones

Dead zone indicates that nodes on this boundary will not be adapted by OptiGrid.

Situations may occur where you wish to freeze the nodes in certain portions of the mesh. To accom-
plish this, you can divide the volume into several families while generating the mesh, and then
define selected volume families as dead zones of adaptation.

Note:

If a volume is defined as a dead zone of adaptation, you must be careful to avoid defining
a column of prisms that spans both a dead zone and an active zone; in such a case, un-
predictable behavior may occur.

[Link]. No-Slip Wall

This option ensures that a zero velocity is imposed on all selected boundaries. This feature is useful
when reading solutions from finite volume codes (for example Fluent), for which the solution must
be reconstructed from cell to node data. This feature ensures that a zero velocity on walls will be
enforced on the specified no-slip wall families. By default, no correction to the solution is performed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
356 of ANSYS, Inc. and its subsidiaries and affiliates.
 Adaptation Strategy

This option can be used to set the velocity to zero on walls with an Euler flow solution if a viscous
solution is to be computed on the adapted grid afterwards.

[Link]. Floating Periodicity

This option keeps node periodicity during mesh adaptation. All nodes on one periodic surface will
be adapted the same way as nodes on the opposite periodic surface.

Note:

All periodic surfaces should be assigned during CAD construction, requiring manual
CAD edition (See OptiGrid - CAD Reconstruction (p. 377)).

12.4. Adaptation Strategy

12.4.1. Mesh Operations

OptiGrid gives the choice of adapting the grid using:

• Full mesh optimization including adding/removing nodes, edge swapping and node movement.
This strategy is strongly recommended as the combination of all adaptive strategies allows
equidistributing the error throughout the computational domain more effectively.

• Full - no swapping combines only adding/removing nodes with node movement.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 357
OptiGrid - Mesh Adaptation

• Node movement only should only be used with hexahedral grids where nodes cannot be added
nor deleted.

12.4.2. Number of Adaptation Iterations

Number of adaptation iterations sets the number of cycle performed by OptiGrid, starting from the
initial grid and flow solution, to the adapted mesh and the flow solution interpolated onto that new
grid.

Note:

If the initial grid is well suited to the flow, the mesh adaptation may not require more than
3 main iterations. On the other hand, if the initial grid is uniform or very coarse, the mesh
adaptation process may require up to 15 main iterations.

• Node movement pre-iterations sets the maximum number of node movement loops in stages 1
and 3 of the adaptation sequence.

• Node movement post-iterations sets the maximum number of node movement loops at stage 6
of the adaptation sequence.

• Edge swapping iterations sets the maximum number of edge swapping loops at stage 5 of the
adaptation sequence.

Adapt on curvature is enabled by default, and controls the activation of curvature-only refinement
& swapping operations. With this option enabled, OptiGrid might refine edges on surfaces where the
maximum coarsening on curvature setting suggests it, even if the adaptation metric does not imply
refinement at this location.

If this option is disabled, OptiGrid will still constrain all operations to be compliant to the curvature
defined by the CAD. This option can be useful to avoid curvature-only refinement on a curved surface
(such as a far-field) with a low error solution.

Adaptation on curvature was always enabled in previous versions of OptiGrid.

12.4.3. Error Control

OptiGrid gives you several options for setting the error density:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
358 of ANSYS, Inc. and its subsidiaries and affiliates.
 Adaptation Strategy

• In Automatic mode, OptiGrid auto-selects the error density based on the current number of elements
in the initial grid. This option is useful to obtain a first estimate of the error density.

• In Custom mode, OptiGrid equidistributes the error to match the specified Error density. Click
to display the error density.

The graph (left) presents the error computed on the initial grid as a function of the percentage of
the total number of edges. A good initial guess for the target error density can be obtained by
viewing the cumulative error distribution (right) and selecting the error that corresponds to the 70th
percentile of the distribution.

With Target # elements, OptiGrid auto-selects and adjusts the error density so as to obtain a specified
target number of elements set under Target/Elements. Note that it is acceptable, within OptiGrid,
to momentarily exceed the specified target number of elements.

With Target # nodes, OptiGrid auto-selects and adjusts the error density so as to obtain a specified
target number of nodes set under Target/Nodes.

Note:

It is acceptable, within OptiGrid, to momentarily exceed the specified target number of

nodes.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 359
OptiGrid - Mesh Adaptation

For options target # elements and target # nodes, the number of main iterations should
be set to approximately 10, in order to allow a good estimation of the error density and
reach the desired target number of elements or nodes.

Tip:

When performing mesh smoothing, set the error density to 1 to preserve mesh density of
the original mesh (with the Custom option). Reduce this value to refine or increase it to
coarsen.

Maximum in the Nodes group sets the maximum allowable number of nodes. No matter which
method of error control is selected, if this limit is reached during the adaptation, OptiGrid will stop
refining the mesh until more nodes are eliminated through the coarsening process.

Maximum in the Elements group sets the maximum allowable number of elements. No matter which
method of error control is selected, if this limit is reached, OptiGrid will stop refining the mesh and
swapping edges until more elements are freed through the coarsening process.

Important:

If either of the Maxima is reached during the adaptation process, it is very likely that some
patches of the grid have not been adapted and therefore the final grid is not optimal. In
this case it is wise to increase the Maxima to a safe level and adapt the grid again.

You can compute and view the error carpet (obtained from the input solution) by clicking the button
View error carpet. If the carpet is computed already, a message box will appear asking if you want
to display the existing error carpet plot or recompute it.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
360 of ANSYS, Inc. and its subsidiaries and affiliates.
 Adaptation Strategy

The error carpet is also computed automatically before and after adaptation. It is then available
through the View button of the run panel, or from the error_before.soln/error_after.soln icons of

the project panel.

The computation and writing of the error carpet can be switched off (See Error Computation (p. 361))

12.4.4. Advanced Options

In this section you will use OptiGrid's more advanced settings to compute the error carpet.

[Link]. Node Movement Algorithm

Available only in Advanced solver options mode:

• Convergence criterion is the convergence level of the iterative scheme used to solve for node
movement. Use a value of 0.001 by default.

• The Relaxation factor is the constant in the node movement equation, and should be set to 1
for most applications. It can be reduced to a smaller value if convergence of the iterative process
is difficult to achieve. For the adaptation of a hexahedral grid, a value of 0.2 is suggested. Under-
relaxation is also recommended when performing Y+ adaptation.

[Link]. Error Computation

Convolution is used to filter the solution and remove the noise. This operation is achieved by
solving a Laplacian equation, which is equivalent to a convolution process with a Gaussian. Convo-
lution iterations is the number of time steps. A value of one is sufficient to remove reasonable
numerical oscillations unless the solution is extremely noisy. Adapting on a noisy solution can affect
the quality of the adaptation.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 361
OptiGrid - Mesh Adaptation

When selecting the check box Write error carpet before/after files, the error carpet is computed
before and after the adaptation, and saved respectively in error_before.soln and error_after.soln.
Icons for these files will be added to the list of output files.

The quality of the adapted grid is determined by the quality of the solution. When the original grid
is quite coarse, the solution is poor around shocks and across boundary layers. To enhance the
shocks and the boundary layers before adapting, a shock-filter pre-processing (deconvolution) is
used. Deconvolution iterations is the number of time steps of the model; higher is the value of
the parameter, the better discontinuities are enhanced. To avoid an excessive enhancement, which
is time-consuming, a value between 30 and 50 is suggested for the number of deconvolution iter-
ations.

In some cases it is possible that the deconvolution process engenders some noise in the solution.
To remove it, use again the convolution process (with the number of Post-deconvolution iterations
set to 1).

Boundary layer merge count for metric: Very thin boundary layers might have an adverse effect
in the error computation. Setting the number of layers of the boundary layers for this setting will
ignore the boundary layer internal solution values, and compute the error on the column top-to-
bottom super-element.

12.5. Mesh Constraints

12.5.1. Minimum and Maximum Edge Lengths

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
362 of ANSYS, Inc. and its subsidiaries and affiliates.
 Mesh Constraints

OptiGrid guarantees a mesh in which no newly created edges are smaller than the user-specified
Minimum edge length. If there are edges smaller than this value, OptiGrid may or may not succeed
in eliminating them completely.

Note:

The edge length must be defined in the same units as in the original mesh file. Moreover,
the prism/hexa layers height will not be affected by the minimum edge length if Y+ adapt-
ation is enabled with Constant Height option.

OptiGrid also guarantees a mesh in which no newly created edges are larger than the user-specified
Maximum edge length. The edge length must be defined in the same units as in the original mesh
file.

To help define both lengths, the actual minimum and maximum edge lengths of the initial grid are
shown by the graphical interface. To use the actual edge length, click the left arrow.

12.5.2. Quality of Tetrahedral Elements

OptiGrid guarantees a mesh in which no newly created tetras have an aspect ratio smaller than the
user-specified Aspect ratio. However, if some tetras in the original mesh violate the aspect ratio
constraint, OptiGrid may or may not be able to cure these elements.

In 2D, the aspect ratio is the ratio of the radius of the circle inscribed within the triangular element,
compared to the radius of the smallest circle containing the element. In 3D, these circles are replaced
by spheres.

To attain the most anisotropic mesh, you should use an aspect ratio value up to 10-2, depending on
the ability of the flow solver to accept stretched meshes. For finite volume codes, such as Fluent, the
aspect ratio should not be smaller than 0.1 if computing a viscous solution.

12.5.3. Quality of Prism Elements

OptiGrid guarantees a mesh in which no prisms have an aspect ratio smaller than Aspect ratio. Prisms
which violate this constraint in the original mesh may not all be repaired.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 363
OptiGrid - Mesh Adaptation

The prism aspect ratio is defined as a function of the aspect ratio of its two triangular faces and the
minimum/maximum ratio of the determinant of the Jacobian.

Important:

Limiting the prism aspect ratio too severely (for example, setting a minimum prism aspect
ratio that is too high) will adversely affect Y+ adaptation.

Warpage is the cosine of the angle between the normal vectors of the two triangles obtained by
cutting any quadrangular face of the prism in half. The warpage ranges from 0 to 1. A value of 1
yields straight prisms, while a value of 0 will result in skewed prisms. If the flow solver accepts highly
skewed cells, a value of 0.1 is preferred, so that OptiGrid may perform to its full potential.

Tip:

For Y+ adaptation, set the minimum warpage to 0.1 to give OptiGrid full freedom to adjust
the prism layers. At convergence, the axial edges of the prisms will be normal to the wall,
giving a warpage near 1.0.

12.5.4. Quality of Hexahedral Elements

OptiGrid uses the determinant of the Jacobian to calculate the hexahedral determinant. Determinant
ranges from 0 to 1, a value of 1 giving a perfect quality and a value of 0 giving a totally skewed
hexahedral.

Warpage is the cosine of the angle (scaled from 0 to 1) between the normal vectors of the two trian-
gular facets that form each face of a hexahedral element. A value of 1 yields hexas with perfectly flat
faces, while a value of 0 will result in hexas with creased faces. If the flow solver accepts skewed cells,
a value of 0.5 is preferred, so that OptiGrid may perform to its full potential.

12.5.5. Other Mesh Constraints

Max. coarsening on curvature is used to control the fineness of the mesh on curved surfaces so as
to preserve the integrity of the CAD geometry. It prevents over-coarsening of the mesh on high-
curvature surfaces and causes refinement if the deviation from curved surfaces in the original mesh
is too large.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
364 of ANSYS, Inc. and its subsidiaries and affiliates.
 Mesh Constraints

The level of coarsening on curvature for a boundary edge is defined as the ratio of the distance
between the mid-point of the edge and the nearest surface, divided by the length of the edge (See
figure below). The coarsening should be set to a few percentage points, more or less.

• The Mesh degree of anisotropy is an overall aspect ratio for the mesh. It should be larger than
the values of the quality metrics for the individual cell types.

• The Minimum face angle is the minimum angle, in degrees, between two edges of a given quad-
rangular face (for hexahedral, prism and pyramid elements).

• The Maximum dihedral angle is the maximum angle, in degrees, between two adjacent faces of
an element.

• The Maximum number of elements at node sets the maximum number of elements that may be
connected at a node.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 365
OptiGrid - Mesh Adaptation

12.6. Performing Mesh Adaptation

Click Run to start the adaptation. Refer to The FENSAP-ICE Solver Manager (p. 39) for guidelines on
how to use both the Execution and Graphs windows.

12.6.1. Post-Processing the Adapted Grid

OptiGrid shows at conclusion of mesh adaptation the initial and adapted grids in the graphical window.
You can change the boundaries displayed by OptiGrid under the Boundaries menu.

Click the side-by-side icon to display the initial grid on the left and the adapted grid on the right.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
366 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Mesh Adaptation

Click the up-and-down icon to display the initial grid in the upper section of the window, and
the adapted grid in the lower section.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 367
OptiGrid - Mesh Adaptation

Finally, click the last icon to overlay the initial and adapted grids.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
368 of ANSYS, Inc. and its subsidiaries and affiliates.
 Performing Mesh Adaptation

12.6.2. Viewmerical Display

If Viewmerical is your default post-processing tool defined in the preferences, use the View button
in the run panel. Viewmerical will permit to display the grid boundaries and also cutting planes onto
the volume. Refer to Post-Processing (p. 439).

Viewmerical can display all grid types supported by OptiGrid.

12.6.3. Solver-Adaptation Coupling

OptiGrid is closely linked to the flow solver. Generally, several loops between the flow solver and
OptiGrid should be performed in order to obtain a final adapted grid with an accurate flow solution.
The process can be summarized as follows:

Given a mesh Mn at loop n, compute the solution Sn on this mesh with the flow solver;

OptiGrid estimates the error of Sn over all edges of Mn;

OptiGrid produces a new mesh Mn+1 using edge refinement, coarsening, swapping and node move-
ment, and interpolates the solution Sn+1/2 from Sn on Mn+1;

A solution Sn+1 on Mn+1 is then computed by the flow solver, starting with the interpolated solution
Sn+1/2 provided by OptiGrid as an initial guess;

The loop is repeated until convergence is achieved.

Note:

The ability of the flow solver to accept increasingly stretched grids determines how close
one gets to an optimum grid. Most well-written unstructured flow solvers are capable of
accepting grids that are increasingly, but gradually, stretched.

12.6.4. Tips for a Successful Adaptation

The following tips are designed to help you run OptiGrid in the most effective way possible.

Make sure your CAD data is properly and completely defined.

The most common source of problems when using OptiGrid is poorly defined CAD data. OptiGrid is
quite sensitive to messy CAD data and problems will often become apparent only after OptiGrid has
been used to adapt the mesh. If these problems appear, it will be necessary to go back to the CAD
geometry and repair the troublesome areas of the geometry. For example, make sure curves are well-
defined at the junction of non-tangential surfaces.

It is better to start with a dense mesh rather than with a mesh that is too coarse.

It is a good idea to start with an initial mesh that has a higher density rather than a lower one, for
several reasons. To start with, the geometry may not be properly represented by an initial mesh that
is too coarse, especially if it is complex or has highly curved surfaces. Since the CAD is reconstructed
from the initial mesh, it is important to have a high-resolution mesh on rounded surfaces for quality

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 369
OptiGrid - Mesh Adaptation

adaptation. OptiGrid is also more likely to have trouble refining the mesh on high curvature areas if
the mesh is too coarse. It is much easier to coarsen on curved surfaces than to refine. Also, if the initial
mesh is too coarse, the solution is less likely to capture the important characteristics of the flow and
the adaptation may make the mesh worse rather than better.

Run OptiGrid in the smoothing mode (without a solution) before starting the solution, to ensure that
there are no elements with a very small aspect ratio.

Examine the flow solution before starting the adaptation.

Make sure the solution is sufficiently converged before starting the adaptation to ensure that the
dominant flow characteristics are captured.

Use the target number of elements or target number of nodes option.

The easiest way to run OptiGrid is to select the target # elements or target # nodes. With these
options, you can set the final size of the adapted mesh and OptiGrid will approximate the target error
density so as to match that size. The main iterations should be between 5 and 15.

Set the mesh constraints based on the current mesh. Verify the minimum and maximum edge lengths.

Gradually increase the total number of nodes/elements, do not abruptly increase the mesh size.

Do not expect to adapt in one solver-adaptation cycle (3 or more cycles are generally required).

12.7. Troubleshooting
This section presents a list of common problems that may be encountered when using OptiGrid. Each
problem description is followed by one or more possible actions which may help to overcome the
problem.

Problem: OptiGrid did not complete the adaptation.

• In order to figure out what happened, first look at the error log file. If the process ended abnormally,
there should be a message in this file indicating what the problem is.

The following are examples of the most commonly encountered error messages:

Error: variable name, *variable* was not found in the solution file.

• In this message, *variable* can be any of the solver labels that were selected under the variable for
adaptation. The message indicates that the solver label from the solution file was entered incorrectly.
To see a list of the solver labels for the variables in the solution file, use the edit variable labels or
refresh the list.

Error: can't open result interface.

• OptiGrid was not able to read the input solution file. Check the solution file format and filename.

Error: OptiGrid found more than 100 layers of prisms in the domain. Stop.

• The maximum number of layers of prisms is 100. Either generate a new mesh with fewer layers or
contact FENSAP-ICE support for a customized version of OptiGrid.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
370 of ANSYS, Inc. and its subsidiaries and affiliates.
 Troubleshooting

Error: Periodic nodes were detected in the mesh, but periodicity is not
defined in the geometry file.

• OptiGrid detected periodicity in the mesh but not in the geometry file. Periodicity must be properly
defined to allow OptiGrid to project these nodes correctly. Update the mesh or the geometry.

Error: The Y+ correction parameters for certain groups of adjoining sur-

face families are incompatible. Curves and bars must be created at the
junction between the following groups of families: WING_TOP WING_BOTTOM.
Adaptation cannot proceed. Stop.

• The parameters for Y+ adaptation must be consistent across surfaces that touch one another. Correct
the configuration file to specify valid parameters.

Error: OptiGrid execution aborted unexpectedly. Check the [Link] file.

• This is a general error message. Detailed information to be found in [Link] (or er-
[Link] in MPI mode where xxx is the processor ID).

Error: Movement 2: edge is too long 453.

Refine 12: new edge is too small 286.

Collapse 23: failed conformity check on elements 102539.

Swap 26: no best swap found 45873.

• At the end of the adaptation, OptiGrid reports the number of rejected operations by occurrences.
There are messages for node movement, refinement, coarsening, and swapping. A brief message
describes each operation, followed by the number of times this operation was rejected. Some rejections
occur naturally. However, a high count on some operations (for example edge is too long or edge is
too small) can reveal mesh constraints that are too severe.

Problem: OptiGrid did not adapt everywhere in a regular fashion.

• Action 1:

OptiGrid adapted in some regions, but not in others. Verify if the maximum # nodes or elements was
reached during the course of the adaptation. This information can be found on the control window.
If either maximum is reached, refinement and swapping is halted until elements and nodes are freed
through coarsening. This prevents OptiGrid from adapting evenly throughout the domain. To avoid
this problem, increase the maximum # nodes and elements parameters accordingly.

• Action 2:

The adaptation may be incomplete. It is possible that OptiGrid has not converged, in which case the
main iterations must be increased. Also, try increasing the number of node movement pre- and post-
iterations, and maximum edge swapping iterations. To get an idea of how well the adaptation process
has converged, look at the control window under edge convergence. If the percentage of edges op-
erated on steadily decreases from iteration to iteration until it is around 1%, this is a good indication
that the adaptation process has converged properly. However, more iterations of node movement
may still be required.

• Action 3:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 371
OptiGrid - Mesh Adaptation

It is difficult to adapt in columns of prisms. Thin layers of prisms are sensitive to the aspect ratio and
warpage. It is also difficult to rapidly increase the height of prisms. Under-relaxation on node movement
is suggested.

• Action 4:

The presence of pyramid transition elements between tetras and hexas or prisms will limit the adapt-
ation operations in the neighboring tetras. Pyramids should be avoided.

Problem: The adapted mesh is too coarse.

• Action 1:

The target error density is too high. If the adaptation was done using the user-specified option, then
the target error density must be lowered. If the adaptation was done using the target # elements
or nodes, then you must increase the target # elements or nodes accordingly. Remember to increase
the maximum number of elements and the nodes to a value which is at least 20% greater than the
target number, otherwise the adaptation process will not be properly completed. As a general rule,
for tetrahedral elements, the number of elements is 5 to 6 times greater than the number of nodes.

• Action 2:

The minimum edge length may be too large, causing too much coarsening.

Problem: The adapted mesh is too dense.

• Action 1:

The target error density is too low. If the adaptation was done using the user-specified option then
the target error density must be increased. If the adaptation was done using the target # elements
or nodes, then you must decrease the target # elements or nodes accordingly. You may also increase
the minimum edge length to prevent the creation of very small elements.

• Action 2:

The maximum edge length may be too small, causing excessive refinement in the far-field.

Problem: There are asperities on rounded surfaces.

• Surface asperities are defined as edges carving through a rounded surface, leading to sharp angles
between adjacent faces and causing a kink in the surface (See figure below).

• Action 1:

The original mesh is too coarse near rounded surfaces. Refine the mesh in those regions and restart
the adaptation.

• Action 2:

The parameter for maximum coarsening on curvature is too small. Although a small value is preferable
in order to better represent the curvature of the surface, you may have to start from a higher value
(for example 0.10) and gradually decrease it over several adaptation cycles. When there are faces that
are too coarse to properly represent curved surfaces, it is advised that you refine the worst edges
first and then proceed to refine slightly better edges, rather than refining all these edges at once.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
372 of ANSYS, Inc. and its subsidiaries and affiliates.
 Troubleshooting

This can be accomplished by first running OptiGrid with a high value for the maximum coarsening
on curvature, and then progressively lowering the value from cycle to cycle.

Problem: There are clusters (patches) of elements on surfaces.

• There may be fluctuations in the solution which lead to a high error estimation and high refinement
in certain regions. Check that the solution is smooth and not patchy and that there are no hot spots.
If there are such fluctuations, the solution must be rerun or continued until it is more fully converged.
It is also possible to apply data filtering on the adaptation variable using the OptiGrid filter (See Error
Computation (p. 361)).

Problem: The height of prisms is not uniform or the prisms are not ortho-
gonal to the surface.

• Action 1:

The minimum edge length may be too large, causing OptiGrid to fail to achieve the desired Y+. Lower
this value.

• Action 2:

The aspect ratio and warpage of prisms may be too restrictive. Lower these values.

• Action 3:

Node movement may be incomplete. Try to increase the number of node movement iterations or
decrease the relaxation factor for displacement.

• Action 4:

If the bad prisms are near the trailing edge of a wing, there is not much that can be done since the
normal vector to the surface cannot be evaluated accurately at a sharp corner. In such a case, make
sure that the initial mesh is suitable for the solver in that region.

• Action 5:

There can be pyramids between layers of prisms and tetrahedral elements, preventing proper adapt-
ation. In this case, it would have been preferable to eliminate the pyramids during the mesh generation
phase.

Problem: Hexahedral elements look pinched on the surface.

• The next figure shows an example of pinched elements in a hexahedral mesh.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 373
OptiGrid - Mesh Adaptation

• Action:

There are surface nodes which are not moving, making the grid look pinched near these nodes. Node
movement is more delicate for hexas. Try decreasing the relaxation factor for displacement and the
minimum face angle parameters. Decreasing the minimum face angle will not necessarily lead to
skewed elements, but it will allow node movement to succeed if at some transitory state the face
angle is below this threshold. Similarly, the values for the minimum hexahedral determinant and the
minimum hexahedral warpage can be lowered to allow more freedom in the movement of nodes,
but this may lead to slightly more distorted cells. Adjusting the error density can also affect the out-
come of node movement for hexas (and other element types as well).

Problem: There is little difference between the initial hexahedral mesh

and the adapted mesh.

• Action:

Node movement depends on the target error density and choosing a target error density that is too
high may prevent movement of the nodes if the error of the initial mesh is already smaller than the
specified target. In most cases, using the automatic error estimator should work. If not, you should
plot the error distribution using view error and select a suitable value.

Problem: The Minimum/Maximum edge length settings are not respected.

• Action:

The length of any edge should remain between these bounds. OptiGrid will never create edges that
violate these constraints. If these limits are not respected in the original mesh, OptiGrid may not be
able to fix these edges, but it will not make them worse. If this is a major concern, try running more
main iterations and the problem should go away on its own.

Problem: The Minimum aspect ratio is not respected.

• Action:

If the original mesh contains elements whose aspect ratio is below the specified minimum aspect
ratio, OptiGrid may or may not be able to eliminate them. As for the edge length constraint, the aspect
ratio constraint is strictly enforced in OptiGrid, meaning that no new element violating this constraint
will be introduced.

Problem: The solver does not converge when an attempt is made to restart
the solution on the adapted mesh.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
374 of ANSYS, Inc. and its subsidiaries and affiliates.
 Troubleshooting

• Action 1:

OptiGrid writes out the solution fields interpolated on the new adapted mesh. It is strongly recom-
mended that the solver be restarted using this interpolated solution.

• Action 2:

The mesh may have areas where patches of excessively small elements were created next to very
large elements. This kind of element cluster can prevent a solver from converging properly or give
unrealistic solutions. It is necessary to locally repair these patches of small elements - they are likely
due to problems with the CAD data.

• Action 3:

The solver may have difficulty converging because the adapted mesh is too anisotropic. This is more
likely to be the case with finite volume codes. Increase the minimum tetra aspect ratio and the min-
imum prism aspect ratio, if applicable. A value of 0.25 for the mesh degree of anisotropy is a safe
first guess.

• Action 4:

The wrong adaptation variable might have been used. For example, adapting a grid for a viscous
flow based on pressure will coarsen the mesh in the boundary layer, making the new grid unsuitable
to viscous flow calculations, therefore leading to poor convergence of the flow solver. Simply restart
the adaptation using an appropriate flow variable.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 375
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
376 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 13: OptiGrid - CAD Reconstruction
The following sections of this chapter are:
13.1. GUI-Assisted CAD Reconstruction
[Link] CAD Reconstruction Process
13.3. Advanced CAD Edition

OptiGrid requires CAD information to perform various geometric operations including projections onto
surfaces, normal computations, etc. CAD information permits the adaptation process to be more accurate
as it contains the geometry of the problem, described using parametric objects like splines, planes and
lines.

The next figure presents the CAD of a simple circle. The coarse mesh generated from this CAD shows
line segments that make the original circle look like an octagonal object, which is far from the original
circle geometry. By performing mesh adaptation, however, more grid points can be added on the circle
boundary and its discretization in space is therefore finer, getting closer and closer to the original circle
geometry. The addition of extra grid points is only possible if the CAD of the circle is known a-priori.
Adding grid points based only on the original coarse mesh would have kept the octagonal shape of
the geometry.

Figure 13.1: CAD of a Circle

Figure 13.2: Coarse Mesh

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 377
OptiGrid - CAD Reconstruction

Figure 13.3: Refined Mesh Using CAD Information

CAD reconstruction is the process by which CAD information is deduced from a raw mesh with no, or
few, geometrical information. It offers many advantages among which the use of any grid, generated
initially with an unknown or unsupported CAD format, with OptiGrid. Naturally, the accuracy of the re-
constructed CAD is a function of the density and the location of the grid points on all surfaces of the
original grid. For example, it is therefore important to use a sufficiently fine grid for capturing zones of
high curvature.

Automatic CAD reconstruction can be performed in OptiGrid using Generate. Manual CAD edition can
be performed using View/Edit.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
378 of ANSYS, Inc. and its subsidiaries and affiliates.
 The CAD Reconstruction Process

13.1. GUI-Assisted CAD Reconstruction

OptiGrid automatically detects CAD features from the grid file and displays the grid and its different
edges. Edges are lines separating two or more CAD surfaces, which are automatically detected from:

1. BAR elements and boundary condition patches;

2. The topology: sharp corners, geometric features.

OptiGrid offers different options to automatically detect, add and filter edges from a mesh topology.
In many cases, the default parameters are sufficient to generate an accurate CAD.

If the mesh provides no, or only partial edge definitions, the accuracy of the automatic edge detection
becomes limited. It may generate a good CAD for simple meshes, but may not be accurate for meshes
with irregular curvatures. In this case, manual edition of the edges may be required.

13.2. The CAD Reconstruction Process

In this section, you will reconstruct a CAD surface, view the reconstructed CAD and save your geometry
file.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 379
OptiGrid - CAD Reconstruction

13.2.1. Input/Output Geometry Files

OptiGrid reconstructs the CAD surfaces from an input grid, and writes three files required for mesh
adaptation:

• [Link] → geometry (CAD).

• [Link] → zones.

• [Link] → grid-to-CAD conversion.

These 3 files are saved in the same directory as the input grid. The first two may be moved to other
locations, if needed, however the grid-to-CAD conversion file must stay in the same directory as the
grid.

When performing mesh adaptation, OptiGrid writes the following two files:

• gridFilename_adapted → the adapted grid.

• gridFilename_adapted.info → the adapted grid-to-CAD conversion file.

This new grid-to-CAD conversion file enables the adapted grid to be used with the original CAD. The
CAD generation step can therefore be performed only once, before the first adaptation sequence.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
380 of ANSYS, Inc. and its subsidiaries and affiliates.
 The CAD Reconstruction Process

13.2.2. Initial Edge Detection

When starting CAD reconstruction, the first step consists in reading the input grid. The basic features
of the CAD are then detected: external surfaces, internal boundaries between volume elements,
automatic edges, and other geometric features.

For large-size grids and slow computers, this operation may take some time as it is the most demanding
part of the process, in both RAM usage and CPU time.

13.2.3. Edge Edition

The edition mode shows the grid in wire frame and edges with bold colored lines.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 381
OptiGrid - CAD Reconstruction

Mesh edges are colored lines or splines separating surfaces in the CAD. They are groups of concaten-
ated mesh segments. These edges should separate the CAD surfaces at natural borderlines, geometric
features or boundary conditions zones borders.

Auto-detection uses a specific threshold to detect edges. The tolerance modifies these thresholds.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
382 of ANSYS, Inc. and its subsidiaries and affiliates.
 The CAD Reconstruction Process

13.2.4. View the Reconstructed CAD

Each mesh surface is converted to a CAD surface and its curvature is deduced from the mesh topology.
CAD surfaces are made of parametric surfaces and splines. The CAD can be displayed by selecting
View mode → CAD.

The CAD is displayed in blue, with its edges in lighter blue. By default, the CAD is drawn using the
same resolution as the grid (1 triangle per grid face). The CAD is however a high-order representation
of a grid topology. The resolution of the display can be improved by increasing the graphical detail
settings, as in the example shown below. An increased resolution requires, however, more RAM for
large grids and, therefore, reduces the graphical rendering speed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 383
OptiGrid - CAD Reconstruction

13.2.5. CAD Attributes

A group of surfaces can be flagged as a family for mesh adaptation, for example, to impose Y+ con-
straints. Families cannot overlap and are displayed in red.

Families are listed under the attributes tab. When editing a grid in FENSAP or Fluent formats, families
are automatically created to fit the boundary condition zones.

New families can be created using Add. Use short and simple identifier names for groups and families,
with alphanumerical and underscore characters only. Other operations (Erase, Rename and Merge)
are also available.

Transfer to selection mode and right-mouse click the 3D window to add or remove surfaces to
or from the selected family. All surfaces removed from one family are added to the default SURFACES
family. The SURFACES family contains all surfaces not owned by any other family.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
384 of ANSYS, Inc. and its subsidiaries and affiliates.
 Advanced CAD Edition

13.2.6. Periodicity

Some grid formats (for example FENSAP, Fluent) already define the periodicity between different
boundary patches. This information is saved in the geometry file, and used by OptiGrid for mesh ad-
aptation.

If the grid file does not provide such information, it may be added to the geometry file within OptiGrid.
For this, select two families between which periodicity should be imposed (edit and click two surfaces).
Configure sets the detection thresholds and validates the periodicity between the two surface groups.
If the periodicity is invalid, a warning message is issued when saving the CAD and, consequently, the
periodicity will not be saved in the geometry file.

13.2.7. Save the Geometry File

The geometry can be saved at any time during the edition process, using File → Save CAD.

13.3. Advanced CAD Edition

In this section you will modify edge detection settings, set up filtering and add groups of edges.

13.3.1. Edge Tolerance

Consider the example shown below of one element junction with different angles on both sides.
Here, one angle is detected with the default tolerance (edge in blue), while the other is not. In such
case, it is necessary to change the default tolerance.

The auto-detection procedure uses default tolerances which are optimal for most grids. The tolerances
button gives access to the detection thresholds dialog box where values can be better tuned for a
specific grid.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 385
OptiGrid - CAD Reconstruction

Detect edges enables edge detection. If disabled, only the edges provided in the initial grid are used
to reconstruct the geometry.

Max face angle adds edges whenever the angle between two surfaces is greater than the specified
value. A lower value detects more edges, but may create undesired edges especially when the grid
is too coarse to represent the geometry.

Max curve angle adds prescribed points onto curves if the angle is less than the input value. The
edge is then split in two and a prescribed node is introduced at the breaking point.

If Keep edited edges is selected, the selected tolerances will not erase edges added manually using
the edition tools.

Unselect Detect edges and Keep edited edges to apply a full reset, and only consider edges provided
by the input grid.

The Refresh CAD icon performs the edge detection operation and refreshes the display.

Reset sets the detection thresholds to their default values.

13.3.2. Edge Filtering

The Unconnected edge filter option enables a filter to remove automatically most of CAD detection
artifacts. These artifacts are small isolated edges not related to the geometry.

Unconnected curves is an orphan curve created during the detection process, which is not connected
to any other curves at its end points. The curve is erased if its length is less or equal to the specified
value.

Connected curves. Same as standalone curve, but the curve is connected to another curve at only
one of its ends. The curve is erased if its length is less or equal to the specified value.

The edge filter is applied on detected edges only and will not remove user-created curves.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
386 of ANSYS, Inc. and its subsidiaries and affiliates.
 Advanced CAD Edition

Example 13.1: Standalone Curves

Figure 13.4: Initial Mesh Edges

Figure 13.5: After Filtering Edges of Length <= 3

Figure 13.6: After Filtering Edges of Length <= 10

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 387
OptiGrid - CAD Reconstruction

Example 13.2: Connected Curves

Figure 13.7: Initial Mesh Edges

Figure 13.8: After Filtering

13.3.3. Edge Edition – Edge by Edge

The activation of this tool allows adding and removing edges manually by a right-mouse clicking the
edge in the 3D window. Added edges are shown in white, while removed edges are in black:

Example 13.3: Example of Edge Addition (Added Edges in White)

Example 13.4: Example of Edge Suppression (Deleted Edge in Black)

Use Refresh CAD to commit the current modification and refresh the edge colors.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
388 of ANSYS, Inc. and its subsidiaries and affiliates.
 Advanced CAD Edition

Tip:

Undo and redo any edition operations with Edit → Undo/Redo or Ctrl+Z/Ctrl+Shift+Z.
However, mandatory edges obtained from the grid (boundary condition patches, BAR
elements, etc.) will not be removed by this operation.

13.3.4. Add a Group of Edges

This tool allows adding a group of interconnected edges by clicking only one edge of this group. The
edges are then connected one by one, if the connected edge is nearly parallel to the current one.

Transfer to selection mode:

and right-mouse click in the 3D window to add edges.

For example, the edges of this cube could be added manually, instead of using the auto-detection
tool.

Figure 13.9: Initial Mesh, with No Edges. The X Mark Is the Edge Selected with Define Curves

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 389
OptiGrid - CAD Reconstruction

Figure 13.10: The Group of Edges Detected Is Shown in Red. Parallel Edges Connected to the
Initial Edge Were Selected Automatically

Figure 13.11: The Tolerance Control Allows Connecting Edges That Are Not Parallel, as Shown
Below

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
390 of ANSYS, Inc. and its subsidiaries and affiliates.
 Advanced CAD Edition

13.3.5. Prescribed Points

Prescribed points are separations between edges. Edges can be split in two by adding a prescribed
point at a given position, or joined together by removing the prescribed point.

While the edit curve breaks tool is active, existing prescribed points are shown with red dots. Transfer
to selection mode and right-mouse click a node position to add and remove this point. New
prescribed points are shown in white, while removed ones are in black.

13.3.6. Delete an Edge

When this tool is active, right-mouse click an edge to delete it. However some mandatory curves
cannot be deleted.

13.3.7. Refresh the Geometry

The Refresh CAD icon saves the current edition and clears
the undo history. The graphical display is refreshed, displaying the edges defined on the CAD in bright
colors.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 391
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
392 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 14: FENSAP-ICE File Formats
The following sections of this chapter are:
[Link] Grid File - ASCII Format
[Link] Grid File – Binary Format
[Link] FENSAP Solution File – Binary Format
[Link] Actuator Disk File
[Link] Probe Coordinate File ([Link])
[Link] Probe Output File ([Link])
[Link] [Link] file
[Link] Sand-Grain Roughness Distribution File ([Link])

Most of the FENSAP-ICE solvers are based on the Finite Element Method. In FEM, the element, not the
node, is the basic building block of the grid and the table of connectivity of the nodes to the elements
is its most important feature. FEM supports a great variety of element types. Fortunately, the simplest
linear elements are ideal for fluid dynamics applications. The table below shows the characteristics of
the four types of linear elements supported by FENSAP-ICE.

Table 14.1: Elements

Element Face Node Node layout

geometry number Ordering
4-node 1 2-3-4
tetrahedron 2 1-4-3
ielgeom = 2 3 1-2-4
4 1-3-2

5-node 1 1-4-3-2
pyramid 2 1-2-5
ielgeom = 5 3 2-3-5
4 3-4-5
5 4-1-5

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 393
FENSAP-ICE File Formats

Element Face Node Node layout

geometry number Ordering
6-node 1 2-3-6-5
prism 2 3-1-4-6
ielgeom = 3 3 1-2-5-4
4 1-3-2
5 4-5-6

8-node brick 1 1-4-3-2

2 1-5-8-4
ielgeom = 1
3 4-8-7-3
4 2-3-7-6
5 1-2-6-5
6 5-6-7-8

14.1. The Grid File - ASCII Format

All FENSAP-ICE modules require a grid file. Each grid file is subdivided into five main parts, described
in detail in the following sections. An example of the contents and ASCII format of a grid file is shown
below.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
394 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Grid File - ASCII Format

14.1.1. The Grid Header

On the first line, nnode (32-bit integer) is the total number of nodes, nelemb (32-bit integer) is the
number of boundary faces, and cosys (32-bit integer) is a flag for the coordinate system (1 for
Cartesian, 9 for Cylindrical).

Note:

FENSAP-ICE supports the cylindrical coordinate system. To enable this feature, the parameter
cosys should be set to 9.

On the second line, neltype (32-bit integer) is the number of different element types in the grid.
In the following neltype lines, one per element type, ielgeom (32-bit integer) is a flag for the
element type (See Table 14.1: Elements (p. 393)) and nelem (32-bit integer) is the total number of
elements of that type. Several groups of element types may appear in one grid, for example a hybrid
grid would have groups of tetrahedra and prism elements.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 395
FENSAP-ICE File Formats

The parameters on the next line contain the characteristic length charlen (64-bit double precision)
of the flow and the reference area arearef (64-bit double precision).

Note:

The parameters charlen and arearef are no longer used in FENSAP-ICE, but remain
in the grid file for backward compatibility of the format.

Finally, the last line of the grid header contains a brief ASCII text description of the grid, grid_label
(character*80).

14.1.2. The Coordinate Table

The next nnode lines contain the coordinates xj,i, j=1,2,3, i=1,... or (r,θ,z) of the nodes
(64-bit double precision), and a boundary identification index bci, i=1,... (32-bit integer). There
are three possible values for the boundary identification index:

• If the node is an internal node not touching any surface, its boundary identification index must
have a value of 0.

• If the node belongs to a boundary surface, it has the same value as the surface index. This is purely
to facilitate mesh inspection, FENSAP-ICE will ignore this index if its value is greater than zero.

• If the node is periodic to another node, its index must have the negative value of the number of
the other node.

Note:

In the latter case, only one node of the periodic pair will have a negative index, the
other node will either be on a symmetry plane, or in the case of rotational or translational
periodicity not perpendicular to a symmetry plane, it will be an internal node with index
0.

For example, the following two lines corresponding to nodes 8641 and 8642 were extracted from the
coordinate table of a periodic grid.

-.11419295100912E+00 0.57121910165400E-01 -.76200000000000E-01 4300

-.11419295100912E+00 0.57121910165400E-01 0.76200000000000E-01 -8641

Node 8641 is on a symmetry plane normal to the z-axis and hence has an index 4300 (See
Table 14.2: Boundary Condition Indices (p. 398)). Node 8642 is periodic to 8641, has the same x- and
y-coordinates but lies on the other parallel plane perpendicular to the z-axis. Its boundary index is
negative and shows that it is periodic to node 8641.

Tip:

Two-dimensional geometries can be simulated using a quasi-2D grid with single element
in the direction normal to the plane of the flow (xi = constant). One of the two parallel

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
396 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Grid File - ASCII Format

planes (xi = constant) is defined as a symmetry plane (index 4i00, i=1, 2 or 3), while nodes
on the other plane (xi+∆xi) are periodic to the corresponding node on the symmetry plane.
The periodicity is specified using the node boundary identification index. Therefore, one
can obtain a 2D flow/droplet/ice solution much more efficiently from a periodic quasi-2D
grid without solving a full 3D problem. The quasi-2D grid can be either hexa, prism (trian-
gular faces on the parallel planes) or a hybrid between the two.

Important:

There are some serious disadvantages with hybrid tetra-prism grids (triangular faces on
the wall surface) applied to the solution of quasi-2D problems when the two parallel planes
are symmetry planes. The first one is that if the two parallel planes are widely spaced to
permit fairly large elements in the far-field, the grid size becomes incredibly large, much
larger than the equivalent hexa grid or hexa-prism grid mentioned in the previous sugges-
tion, due to the inevitably fine mesh on the surface. The second main disadvantage is
much more subtle, but has severe effects on the accuracy and stability of the solution: in
order to preserve symmetry and the 2D nature of the solution there must be at least three
layers of elements sandwiched between the parallel symmetry planes, even at the far-field,
otherwise it is impossible to ensure symmetry. In other words, if the grid is not symmetric,
the solution will also not be symmetric and possibly unstable.

14.1.3. The Connectivity Table

Following the nodal coordinates, the next nelem=sum(nelem(i), i=1,neltype(i)) lines
contain the table of global connectivity (32-bit integers) for the elements. Each line contains the
global node numbers nj,i, j=1,...,e, i=1,... of the element’s nodes; the number of
columns corresponds to the number of nodes e for that element type (ielgeom(i)). It is very
important that the global node numbers of each element be listed in the order presented in
Table 14.1: Elements (p. 393), otherwise the Jacobian of the element transformation will become neg-
ative or the element may appear to be degenerate. Different elements have different numbers of
nodes, hence the number of columns (ne) in the table may vary from four (tetra) to eight (8-node
bricks).

The following line was extracted from the table of connectivity of a grid. It has 8 columns and it belongs
to an 8-node brick element. The nodes are listed in the local order 1-2-3-4-5-6-7-8 shown in
Table 14.1: Elements (p. 393).

158579 158739 158740 158580 158581 158741 158742 158582

If the nodes were listed in the wrong order, say 1-3-2-4-5-6-7-8

158579 158740 158739 158580 158581 158741 158742 158582

the coordinates of node 2 and 3 would become inverted, the element would be degenerate and
FENSAP-ICE would issue a fatal error message.

For C3D (heat conduction) only, an additional index mati, i=1,... (32-bit integer) must be added
at the end of each element connectivity line. This is the material number, which links each element
with a specific material whose properties are defined by the C3D interface.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 397
FENSAP-ICE File Formats

14.1.4. The Boundary Face Table

The next nelemb lines list the boundary faces ordered by increasing element number. The three
columns of this table represent the face’s boundary identification index fbi, i=1,... (32-bit in-
teger), the local face number fi, i=1,... (32-bit integer), shown in Table 14.1: Elements (p. 393),
and the number of the element iei, i=1,... (32-bit integer) to which the face belongs.

Note:

Some elements may have more than one face on the boundary.

The table must be ordered by increasing element number.

Boundary conditions in FENSAP-ICE are of two types: Dirichlet (node values) or contour integrals.
Boundary condition application is always performed by scanning the list of boundary faces, and
looping over the nodes if Dirichlet conditions must be applied. A four-digit index is used to identify
boundary faces, allowing up to 1,000 different inlets, walls, exits, heater pads, etc. The recognized
boundary index types are listed in the table below.

When using boundary faces to specify boundary conditions, there is never any doubt as to which
condition has to be applied to which variable, even when nodes may belong to two or three faces
of different types.

Table 14.2: Boundary Condition Indices

Boundary Index Surface Type

0 Interior Node (Not on a boundary)
1,000 to 1,999 Inlet or Far-field Face
2,000 to 2,999 Wall Face
3,000 to 3,999 Exit Face
4,000 General Symmetry Plane
4,100 Symmetry Plane Perpendicular to the X-Axis
4,200 Symmetry Plane Perpendicular to the Y-Axis
4,300 Symmetry Plane Perpendicular to the Z-Axis
5,000 Periodic Boundary*
6,000 to 6,999 Face on an Actuator Disk, a Screen or a Heater Pad
7,000 to 7,999 Surface to Be Stitched for Rotor/Fuselage
Interaction or Non-Conformal Interfaces in Case of
No Stitching

*For display purposes only, will be ignored by the solvers.

Note:

Translational periodicity (not normal to a symmetry plane) in Cartesian coordinates is de-

tected automatically by FENSAP-ICE.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
398 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Grid File – Binary Format

The rotational periodicity in Cartesian coordinates is detected automatically by FENSAP-

ICE. No periodicity angle is required.

The rotational periodicity in the q-direction in cylindrical coordinates is detected automat-

ically by FENSAP-ICE.

Non-conformal interfaces need to exist in pairs as odd and even numbers, for example
7001 and 7002, 7003 and 7004, 7011 and 7012, etc. Their boundaries should be matching
as close as possible, although, this is not a hard limit.

When a node belongs to more than one face, certain rules apply. For example, at the interface between
two surfaces of different types, the priority of the boundary conditions is assigned according to the
guidelines set forth in Table 14.3: Boundary Condition Priorities (p. 399).

Table 14.3: Boundary Condition Priorities

First Index (mi) Second Index (mj) Prioritized Index

1 2 2
1 3 1
1 4 1
2 3 2
2 4 2
3 4 3

Therefore, nodes at the interface between a 1000-family and 2000-family of boundary indices would
give higher priority to the 2000-family of boundary conditions, meaning that conditions imposed on
a wall would receive higher priority than those of an inlet.

In the case where the two surfaces are of the same type but have different numbers, the one with
the higher number dominates. So at the nodes of an interface between a 2000 and 2001 face the
conditions of the 2001 face dominate.

14.1.5. The Domains Table

Finally, the last table contains the domain indices mi, i=1,... (32-bit integer) which link each
element to a given domain index for applications such as Rotor/Fuselage, that require stitching of
the stationary and moving meshes, or engine center cones where the internal and external flow do-
mains require different initial conditions. Elements that belong to the stationary grid should always
be identified with material number 0.

Note:

If only one material is present, the materials table may be omitted.

14.2. The Grid File – Binary Format

An example of the grid file (binary format) is shown below:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 399
FENSAP-ICE File Formats

14.3. The FENSAP Solution File – Binary Format

The FENSAP binary flow solution file is written with the following structure:

On the first line,

• nnode (32-bit integer) Number of nodes (must be identical

to nnode in the grid file);
• nfields (32-bit integer) Number of variable fields (6 for
Euler, and up to 17 for Navier-Stokes);
• goveqns (32-bit integer) Flag for the governing equations (1
for Euler, 8 for Navier-Stokes);
• kturb (32-bit integer) Flag for the turbulence model (0 for
a laminar flow, 1 for the Spalart-Allmaras
one-equation turbulence model, 3 or 4 for
kay-epsilon, 5 or 6 for kay-omega);
• lvltime (32-bit integer) Indicates the number of time levels
stored in the file.

The fields are identified by 34-character labels. The first 4 characters of the label are the flow variable
key names in FIELDVIEW and the following 30 characters describe the field. The first six labels are always:

DENS - Density (kg/m3 )

PRES - Pressure (N/m2 )
XVELV1 - Velocity (m/s)
YVELV2 - Velocity (m/s)
ZVELV3 - Velocity (m/s)
TEMP - Static temperature (K)

If the flow solution is viscous (goveqns=8) and the turbulence model is Spalart-Allmaras (kturb=1),
the next six labels are:

KAY - Nutilde (m/s)2

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
400 of ANSYS, Inc. and its subsidiaries and affiliates.
 The FENSAP Solution File – Binary Format

WLDS - Wall distance (m)

VISL - Laminar viscosity (kg/m s)
VIST - Turbulent viscosity (kg/m s)
YPLS - y-plus
UPLS - u-plus

Note:

When variable surface sand-grain roughness is imposed, the wall distance in the solution file
is replaced with the sand-grain roughness height, whose label is WLDSroughness height
(m). The roughness height will have non-zero values away from the walls.

If the flow solution is viscous (goveqns=8) and the turbulence model is k-epsilon (kturb=3 or
kturb=4), the next six labels are:

KAY - Kay (m/s)2

EPSI - Epsilon (m/s2 )
VISL - Laminar viscosity (kg/m s)
VIST - Turbulent viscosity (kg/m s)
YPLS - y-plus
UPLS - u-plus

If the flow solution is viscous (goveqns=8) and the turbulence model is k-omega (kturb=5 or
kturb=6), the next six labels are:

KAY - Kay (m/s)2

OMEG - Omega (1/s)
VISL - Laminar viscosity (kg/m s)
VIST - Turbulent viscosity (kg/m s)
YPLS - y-plus
UPLS - u-plus

If the Navier-Stokes equations have been used to obtain the solution, the solution is complemented by
the three components of the shear stress vector, expressed in Pascal (N/m2):

XSFOSF1 - Shear stress (Pa); Shear

YSFOSF2 - Shear stress (Pa)
ZSFOSF3 - Shear stress (Pa)

If the full energy equation has also been used, the flow solution is complemented by the Classical and
Gresho heat fluxes, both expressed in W/m2:

CLAS - Classical heat flux (W/m2 )

GRES - Gresho heat flux (W/m2 )

Note:

Heat fluxes are zero everywhere except on wall surfaces.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 401
FENSAP-ICE File Formats

The values contained in the vector dble_cnst (64-bit double precision) of length num_cnst (=24 in
this version of FENSAP-ICE) are reference values used to obtain the solution. Some of them are important
for FENSAP, DROP3D and ICE3D:
rgas, gamma, tinf, pinf, machinf, velx, vely, velz, velinf, hinf, xkeinf, rhoinf, p0inf, zmuinf, reinf, prinfnd, en

• rgas Gas constant

• gamma Specific heat ratio

• tinf Reference static temperature

• pinf Reference static pressure

• machinf Freestream Mach number

• velx X-component of the freestream velocity

(non-dimensional)
• vely Y-component of the freestream velocity
(non-dimensional)
• velz Z-component of the freestream velocity
(non-dimensional)
• velinf Magnitude of the freestream velocity

• hinf Freestream static enthalpy

• xkeinf Freestream dynamic pressure (rV2)

• rhoinf Reference density

• p0inf Reference total pressure

• zmuinf Reference dynamic viscosity

• reinf Reynolds number

• prinfnd Freestream reference pressure (non-dimensional)

• entrinf Freestream reference entropy

• length Effective characteristic length

• omgx X-component of the rotational velocity

• omgy Y-component of the rotational velocity

• omgz Z-component of the rotational velocity

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
402 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Actuator Disk File

• zero Unused (0.0d0)

• zero Unused (0.0d0)

• zero Unused (0.0d0)

Next, the time (64-bit double precision) and time steps dt (64-bit double precision) are written. For a
steady flow (lvltime=1), this line becomes 0.0d0.

Finally, each variable field (64-bit double precision) is written following the same order as the labels. If
the solution was steady-state (lvltime=1) only one time level will be found. For unsteady solutions (lvl-
time=2 or lvltime=3) two or three time levels of the pressure, velocity components and temperature
will be written to the file.

Note:

All flow variables are saved in dimensional form, except y_plus and u_plus when the solution
has been obtained with the Spalart-Allmaras turbulence model. If the input grid is in cylindrical
coordinates, the flow solution is also saved in this reference system.

14.4. The Actuator Disk File

The actuator disk input file is an ASCII file. Comment lines must begin with the pound symbol (#). A
single file may control one or more disks. In the latter case, the data of each disk is listed sequentially.

Example 14.1: Disk Data File, for Two Counter-Rotating Disks Located at (0,±1,0)

This is an example of the disk data file, for two counter-rotating disks located at (0,±1,0):

# Actuator disk input file for FENSAP

# –––––––––––––––––––––––––––
#
# FORMAT:
# Number of disks
#
# For each disk:
# –––––––––––
# Disk index number (6x, x=0-9)
# Coordinates of the origin of the disk
# Position of the 12 o'clock mark
# Components of the thrust line (downwash direction)
# Components of the angular velocity vector (Magnitude   rpm)
# (right-hand rule)
#
# Number of angular locations, Number of radial locations
# Angular position (deg)
# Radial distribution (r, Load, DelTtot, omega)
#
2
6001
0.000000d+00 0.100000d+01 0.000000d+00
0.000000d+01 0.100000d+01 0.450000d+00
0.100000d+01 0.000000d+00 0.000000d+00
–.120000d+04 0.000000d+00 0.000000d+00
3 7
0.00000000E+00

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 403
FENSAP-ICE File Formats

0.00000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03

0.13503750E+00 0.32606623E+03 0.35200000E+00 0.12256671E+03
0.23631563E+00 0.72623842E+03 0.78400000E+00 0.12256671E+03
0.32071406E+00 0.91960866E+03 0.99275000E+00 0.12256671E+03
0.35447344E+00 0.90548221E+03 0.97750000E+00 0.12256671E+03
0.39385938E+00 0.69474339E+03 0.75000000E+00 0.12256671E+03
0.45000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.12000000E+03
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.13503750E+00 0.32606623E+03 0.35200000E+00 0.12256671E+03
0.23631563E+00 0.72623842E+03 0.78400000E+00 0.12256671E+03
0.32071406E+00 0.91960866E+03 0.99275000E+00 0.12256671E+03
0.35447344E+00 0.90548221E+03 0.97750000E+00 0.12256671E+03
0.39385938E+00 0.69474339E+03 0.75000000E+00 0.12256671E+03
0.45000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.24000000E+03
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.13503750E+00 0.32606623E+03 0.35200000E+00 0.12256671E+03
0.23631563E+00 0.72623842E+03 0.78400000E+00 0.12256671E+03
0.32071406E+00 0.91960866E+03 0.99275000E+00 0.12256671E+03
0.35447344E+00 0.90548221E+03 0.97750000E+00 0.12256671E+03
0.39385938E+00 0.69474339E+03 0.75000000E+00 0.12256671E+03
0.45000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
6002
0.000000d+00 –.100000d+01 0.000000d+00
0.000000d+01 –.100000d+01 0.450000d+00
0.100000d+01 0.000000d+00 0.000000d+00
0.120000d+04 0.000000d+00 0.000000d+00
3 7
0.00000000E+00
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.13503750E+00 0.32606623E+03 0.35200000E+00 0.12256671E+03
0.23631563E+00 0.72623842E+03 0.78400000E+00 0.12256671E+03
0.32071406E+00 0.91960866E+03 0.99275000E+00 0.12256671E+03
0.35447344E+00 0.90548221E+03 0.97750000E+00 0.12256671E+03
0.39385938E+00 0.69474339E+03 0.75000000E+00 0.12256671E+03
0.45000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.12000000E+03
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.13503750E+00 0.32606623E+03 0.35200000E+00 0.12256671E+03
0.23631563E+00 0.72623842E+03 0.78400000E+00 0.12256671E+03
0.32071406E+00 0.91960866E+03 0.99275000E+00 0.12256671E+03
0.35447344E+00 0.90548221E+03 0.97750000E+00 0.12256671E+03
0.39385938E+00 0.69474339E+03 0.75000000E+00 0.12256671E+03
0.45000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.24000000E+03
0.00000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03
0.13503750E+00 0.32606623E+03 0.35200000E+00 0.12256671E+03
0.23631563E+00 0.72623842E+03 0.78400000E+00 0.12256671E+03
0.32071406E+00 0.91960866E+03 0.99275000E+00 0.12256671E+03
0.35447344E+00 0.90548221E+03 0.97750000E+00 0.12256671E+03
0.39385938E+00 0.69474339E+03 0.75000000E+00 0.12256671E+03
0.45000000E+00 0.00000000E+00 0.00000000E+00 0.12256671E+03

The first line indicates how many disks will be specified.

The second line specifies the surface index of the first disk. Valid numbers are 6,000 to 6,999. The old
two-digit index format, 60 to 69, is still supported for backward compatibility.

The third line specifies the coordinates of the center of the disk.

The fourth line specifies the position of the 12 o'clock mark on the rim of the disk, which is the reference
point for the angles of the radial distributions that define the properties of the disk.

The fifth line contains the direction cosines of the thrust line (non-dimensional).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
404 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Probe Coordinate File ([Link])

The sixth line specifies the direction cosines of the rotational velocity: their vector sum is the rotational
velocity in rpm. In the example, a rotational velocity of 1,200 rpm is specified.

The seventh line indicates how many radial distributions (NR) are used to specify the properties of the
disk, and how many data points are located on each line.

The next group of lines is repeated NR times, you must indicate the radial position of the line as an
angle from the 12 o'clock mark (θ in the direction of rotation; the orientation follows the right-hand
rule with respect to the direction of the thrust line), followed by the radial position (m), disk loading
(Pa), total temperature (K) jump across the disk and swirl velocity (rad/sec) at that radial location, for
each of the Np points on the line.

Note:

Swirl velocity is not necessarily equal to the velocity of rotation of the component.

The disk loading is the local force per unit area, and has the units of pressure, while the total temperature
jump has the units of temperature.

Note:

The rotational velocity vector follows the right-hand rule. Note that the swirl velocity is
not imposed as a Dirichlet boundary condition.

You must not specify the 360° radial line since it is identical to the 0° line.

You must ensure that the disk loading, integrated over the surface of the actuator disk,
produces the desired thrust. Similarly, the total enthalpy jump ( ) integrated over
the disk surface must yield the work done.

14.5. The Probe Coordinate File ([Link])

This file contains the user-defined coordinates of the probe points, at which variable values can be
sampled. The format is:

nmbr_probes
x1 x2 x3
x1 x2 x3
x1 x2 x3
.. .. ..
.. .. ..
.. .. ..

where:

• nmbr_probes (32-bit integer) is the number of probes

• xi, i=1,2,3 (64-bit double precision) are the Cartesian components of the coordinates of each
probe.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 405
FENSAP-ICE File Formats

14.6. The Probe Output File ([Link])

This file contains the values of the variables sampled at the probe locations for the specified number
of iterations. The data contained in the file can be post-processed to yield the time evolution of specific
variables at predefined locations (See The Probe Coordinate File ([Link]) (p. 405)) in the mesh. The
format of the file is:

num_probes
num_iter
Probe number
Iteration
Time
label1
label2
label3
......
......
......
probe1 iter1 time1 val1 val2 val3 ....
probe2 iter1 time1 val1 val2 val3 ....
probe3 iter1 time1 val1 val2 val3 ....
...... ..... ..... .... .... .... ....
...... ..... ..... .... .... .... ....
...... ..... ..... .... .... .... ....
probe1 iter2 time2 val1 val2 val3 ....
probe2 iter2 time2 val1 val2 val3 ....
probe3 iter2 time2 val1 val2 val3 ....
...... ..... ..... .... .... .... ....
...... ..... ..... .... .... .... ....
...... ..... ..... .... .... .... ....

where:

• num_probes (32-bit integer) Number of probes

• num_iter (32-bit integer) Number of iterations for which probe values have been
recorded
• Probe number An ASCII label

• Iteration An ASCII label

• Time An ASCII label

• labelj, j=1,2, … The label of each of the variables sampled at the probe points

• probei, The probe number (See The Probe Coordinate File ([Link]) (p. 405))
i=1,num_probes

• iterk, k=1, (32-bit integer) The iteration number

num_iter

• timek, k=1, (64-bit double precision) The time level

num_iter

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
406 of ANSYS, Inc. and its subsidiaries and affiliates.
 The [Link] file

• valj, j=1,... (64-bit double precision) The value of the variable corresponding to
label j at the probe point

Note:

Groups of num_probes lines are sequentially listed for num_iter iterations.

14.7. The [Link] file

This file is used to impose nodal values of specific variables at predefined time levels. Although it is
intended for unsteady computations, it can also be used in steady computations. The format is as follows:

ntsteps 1 1
time_level nmbr_bc_conds nmbr_bc_conds
nodeid var_nbr value [domain]
nodeid var_nbr value [domain]
nodeid var_nbr value [domain]
...... ....... ..... ......
...... ....... ..... ......
...... ....... ..... ......
time_level nmbr_bc_conds nmbr_bc_conds
nodeid var_nbr value [domain]
nodeid var_nbr value [domain]
nodeid var_nbr value [domain]
...... ....... ..... ......
...... ....... ..... ......
...... ....... ..... ......
time_level nmbr_bc_conds nmbr_bc_conds
nodeid var_nbr value [domain]
nodeid var_nbr value [domain]
nodeid var_nbr value [domain]
...... ....... ..... ......
...... ....... ..... ......
...... ....... ..... ......

where:

• ntsteps Number of time levels (32-bit integer)

• time_level Current time level (64-bit double-precision)

• nm- Number of boundary conditions to impose at each time level (32-bit integer)
br_bc_conds

• nodeid Node number (32-bit integer)

• var_nbr Number of the variable to impose, see Table 14.4: List of Variable Numbers in
[Link] (p. 408) (32-bit integer)
• value Value of the variable to impose (64-bit double-precision)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 407
FENSAP-ICE File Formats

• domain Number of the grid domain, grid stitching mode only (32-bit integer). It can be
omitted if only one domain is present

Note:

The table should be ordered by increasing node number for computational efficiency. When
multiple variables are imposed at a node, they should appear sequentially.

The list of assignable variables is shown in the table below

Table 14.4: List of Variable Numbers in [Link]

var_nbr Variable
1 pressure (Pa)
2 x-velocity (air) (m/s)
3 y-velocity (air) (m/s)
4 z-velocity (air) (m/s)
5 temperature (K)
6 heat flux (W/m2)
7 LWC (kg/m3)
8 x-velocity (drop) (m/s)
9 y-velocity (drop) (m/s)
10 z-velocity (drop) (m/s)
11 drop diameter (m)r
12 nu-tilde (m2/s)/kay (m2/s2)
13 epsilon (m2/s3)/omega (s-1)
14 total pressure (Pa)
15 total temperature (K)
16 flow angle α (deg)
17 flow angle β (deg)
18 ice crystal content (kg/m3)
19 x-velocity (crystal) (m/s)
20 y-velocity (crystal) (m/s)
21 z-velocity (crystal) (m/s)

14.8. The Sand-Grain Roughness Distribution File ([Link])

This file provides the mechanism to impose equivalent sand-grain roughness values on surface nodes,
similar to the [Link] file of The [Link] file (p. 407), and is used only if the Variable roughness
mode is enabled. The format is as follows:

1 1 1
1 nmbr_bc_conds nmbr_bc_conds
nodeid 20 value [domain_nmbr]

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
408 of ANSYS, Inc. and its subsidiaries and affiliates.
 The Sand-Grain Roughness Distribution File ([Link])

nodeid 20 value [domain_nmbr]

nodeid 20 value [domain_nmbr]
...... .. ..... ...........
...... .. ..... ...........
...... .. ..... ...........

where:

• nm- Number of boundary conditions to impose at the current time level (32-bit integer)
br_bc_conds

• nodeid Node number (32-bit integer)

• 20 ID number of the roughness variable (32-bit integer)

• value Equivalent sand-grain roughness height (m) (64-bit double-precision)

• domain Number of the grid domain, grid stitching mode only (32-bit integer). It can be
omitted if only a single domain is present.

Note:

For information on the CFD-Post View Setup File for FENSAP-ICE, see View Set-up File.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 409
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
410 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 15: Tools Reference
The following sections of this chapter are:
15.1. Environment Setup
15.2. Expression Syntax
15.3. Grid Operations
15.4. Solution File Operations
[Link] Operations

Command-line tools are provided in the .../bin/ directory of the FENSAP-ICE installation directory,
whose complete paths are contained in the environment variable $NTI_PATH.

15.1. Environment Setup

Properly configuring your environment PATH will allow you to have all FENSAP-ICE command line tools
available to you from that location.

15.1.1. Command-Line Tools

Linux:

Add the $NTI_PATH to your shell environment $PATH variable, in your shell startup script.

export PATH = "$PATH":/path/to/nti/bin/

Windows:

Launch a terminal from FENSAP-ICE (View → Open Terminal) will initiate a DOS prompt with the
environment PATH already set. All FENSAP-ICE command line tools will be available from there.

15.2. Expression Syntax

The following sections of this chapter are:
15.2.1. Operators
15.2.2. Functions

FENSAP-ICE, solnEdit, convertgrid and other ANSYS tools share the same syntax for expression
evaluation.

An expression is a string defining an algebraic equation to compute a value. Typically, this equation is
evaluated at a node or for a specific {X,Y,Z} coordinate.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 411
Tools Reference

Example 15.1: Basic Examples

"123" or "100+23" corresponds to the constant value 123.

"X>100" corresponds to 1 if X is greater than 100.

15.2.1. Operators
Arithmetic:

• is the modulo operator (division remainder). is

• is for exponent. is

Logical:

• is "and", is "or".

• The result of an operation is either 0 or 1.

• ! is used to reverse a logical value (any nonzero value will be permuted to 0, 0 permuted to 1).

15.2.2. Functions
Table 15.1: Functions

sqrt(), cos(), sin(), tan(), acos(), Mathematical Functions

asin(), atan(), atan2(,), exp()
min(val1,val2), max(val1,val2) Value Operations - Returns the
minimum/maximum of two values
round(), floor(), ceil() Rounding Functions
fabs() Absolute Value

Table 15.2: Range Operations

inRange(value,min,max) Returns 1 if the value within [min,max].

inRangeExcl(value,min,max) Returns 1 if the value outside [min,max].
valueRange(val,min,max,valIN,valOUT) Returns valIN if the value is within [min,max],
returns valOUT otherwise.
valueRangeExcl(val,min,max,valIN,valOUT) Same as valueRange, but when the value is
outside [min,max].
ifValue(condition,valueTrue,valueFalse) Returns valueTrue if the condition is true
(nonzero), otherwise returns valueFalse.

Table 15.3: File Data

fileData1D(value,"filename") Reads the filename from the current directory

(must be a 1D dataset of N points). The data

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
412 of ANSYS, Inc. and its subsidiaries and affiliates.
 Grid Operations

will be interpolated linearly. Values out of

range are clamped to the minimum/maximum
data point.
npoints fileData1D File Format

variable value

variable value

variable value

...

Example 15.2: Linearly Interpolated Data

0.5 291.75

0.6 293.4

0.73 295.9935

0.88 299.616

1.2 309.6

15.3. Grid Operations

The following sections of this chapter are:
15.3.1. Convertgrid
15.3.2. fluent2fensap
15.3.3. fensap2fluent
15.3.4. cfx2fensap
15.3.5. Conversion from FENSAP to CFX

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 413
Tools Reference

15.3.1. Convertgrid
convertgrid is a tool that enables many editing operations on a FENSAP format grid.

[Link]. Description
Operations:

• File format conversion (ASCII, binary, C3D solid)

• General grid statistics

• Grid order optimization

• Scaling, rotation, translation

• Node periodicity correction

• Boundary condition operations: renumbering, detection of missing facets

• Volume operations: splitting

• Cell operations

[Link]. Command Line Reference

Note:

For a complete and fully up-to-date command reference, use convertgrid -h.

Table 15.4: Convertgrid

convertgrid [SOURCEGRID] [DESTINATIONGRID] Format of the convertgrid command.

[OPTIONS]

Table 15.5: Options

-d Diagnostic mode - Does not write output file

but lists the solution content (reference
values, solution datafields, zones and
boundary conditions).

Table 15.6: Output File Formats

-ascii Writes text format grid (default=binary, for

speed). File output format is binary, unless
-ascii is specified.
-c3d Writes a C3D format grid (solid domains).
-cart Writes a grid in Cartesian coordinates.
-cyl Writes a grid in cylindrical coordinates.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
414 of ANSYS, Inc. and its subsidiaries and affiliates.
 Grid Operations

-solid Writes a solid domain grid.

Table 15.7: Input File Format

-readc3d Reads a C3D format grid.

-rotx Specifies the X axis of rotation, if any.
Required for some features.
-roty Specifies the Y axis of rotation, if any.
Required for some features.
-rotz Specifies the Z axis of rotation, if any.
Required for some features.

Table 15.8: Stats

-d Printout grid stats and end (size, boundary

conditions, cell types).
-dd Outputs extra read info.

Table 15.9: Grid Scaling/Operations

-factor=VALUE Scale the nodes coordinates by VALUE factor.

-factor=X,Y,Z Scales the X,Y,Z coordinates by VALUE factor.
-translate=X,Y,Z Scales the grid by the specified vector.
-translatePost Translates after all other operations (on all
materials).
-rotate[X,Y,Z]=angle Rotates the grid along X,Y,Z axis, by the
specified angle (degrees).

Table 15.10: Optimization

-optimize Reorders the node numbering with the RCM

algorithm.
-optimize2 Reorders the node numbering with the
Octree algorithm.

Table 15.11: Boundary Condition Operations

-renameBC=OLD,NEW Renumbers the specified boundary condition

to NEW.
-renameBC=OLD,NEW,EQUATION Same as -renameBC but only where
EQUATION is true.
-detectBC=BC Detects missing boundary facets on the grid
and assigns them the identifier boundary
condition.
-fixBC Detects and remove duplicate facets.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 415
Tools Reference

-filterInternalBCs Removes boundary condition surrounded by

two volume elements, except actuator disks
or heater pads.

Table 15.12: Volume Operations

-splitVolumes Writes OUTPUT.X grids, one for each

volume.
-splitMaterials As -splitVolumes, but using material IDs as
volumes.
-splitSoln=FILENAME In -splitVolumes mode, can split a solu-
tion file.
-splitHFlux=FILENAME In -splitVolumes mode, can split a
[Link] file.
-splitShear=FILENAME In -splitVolumes mode, can split a sur-
[Link] file.
-splitJoin=V1,V2 Volume 2 will be merged to Volume 1.
-splitSkip=V Discards the volume V when working on
multiple domains.
-mergeBC=BC1,BC2 Merges nodes of node-matching surfaces.

Table 15.13: Material Operations

-renameMat=OLD,NEW Renumbers the specified material ID to NEW.

-renameMat=OLD,NEW,EQUATION Same as -renameMat but where EQUATION
is true.

Table 15.14: Periodicity Operations

-periodic[=tolerance] Sets periodic flags on 4100, 4200, 4300s

boundary condition, must be node-matching;
also permits to double-check the accuracy
of a grid periodicity.
-notperiodic Removes periodicity in the output grid.
-periodicZone=4*** For -periodic, specifies the symmetry
boundary condition number that is periodic.
-periodicPlanes=tolerance Optionally used with -periodic, to refine the
tolerance of a point on a plane.
-periodicTranslation=X,Y,Z Specifies the translation vector.
-periodicClipPlane=[X|Y|Z],low,hi Clips the periodic nodes on the given planes.
Used with -periodic.
-periodicRotational=X/Y/Z,ANGLE Specifies the axis of rotation and angle in
DEG.
-periodicFix For already periodic grids, will increase the
periodic plane accuracy
(periodicTranslation/Rotational argument
required).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
416 of ANSYS, Inc. and its subsidiaries and affiliates.
 Grid Operations

-clearPeriod=BC,BC,... Removes periodicity on specified boundary

condition list.
-prBC=BC1,BC2 Used with -periodicRotational/Translation,
specifies boundary condition pairs to match.
Boundary conditions are erased.

[Link]. Examples
Table 15.15: Example Commands

convertgrid grid_bin grid_asc -ascii Convert a grid to ASCII Format.

convertgrid grid_asc grid_opt -optimize2 Convert a grid to binary format, and reorder
the node numbering for better performance.
Nodal solutions, heat fluxes and so on are
not useable with the reordered file as the
node and facet order of the output file is
different.
convertgrid grid_in grid_m -factor=0.0254 Scale a grid from inches to meters.
convertgrid grid_in grid_out Renumber a boundary condition identifier.
-renameBC=2002,2000 -renameBC=2003,2000 (All facets of boundary condition 2002 and
2003 renamed to 2000).
convertgrid grid_in grid_out Renumber a boundary condition identifier
-renameBC=2000,2001,"Y>0" from a geometrical condition. (All facets of
boundary condition 2000 for which the
centroid is over Y = 0 coordinate will be
renumbered as 2001).
convertgrid grid_multi grid_part -splitVolumes Split a multi-volume grid into separate grids,
grid_part.1 and grid_part.2 would
be written.
convertgrid grid_multi grid_part -splitVolumes Split a multi-volume grid and solution files
-splitSoln=grid_multi.soln into separate grid/solution files. (In addition
-splitHFlux=grid_multi.hflux to grid_part.X,
-splitShear=grid_multi.surface grid_part.[Link]/hflux/surface
will be written).

Table 15.16: Example Commands Continued

To add rotational periodicity onto a grid lacking periodicity information:

• Grid provided with a single BC=4000 for both rotational periodic sides, the boundary condition
is first split in two boundary conditions, the renamed boundary condition is based on the
rotational coordinate THETA (grid is specified as rotating along the X axis, with the -rotx
argument).

convertgrid grid_orig grid_bcsplit The two boundary conditions are now

-renameBC=4000,4001,"THETA>0" -rotx useable for periodicity node detection, which
is a known 45 degrees rotation along the X
axis.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 417
Tools Reference

convertgrid grid_bcsplit grid_periodic FENSAP requires a rotational periodic grid

-periodicRotational=X,45 -prBC=4000,4001 (or non-axis-aligned translational periodic
grid) to have periodic nodes, but no
boundary condition facets (or a boundary
condition 5000).
convertgrid grid_orig grid_bcsplit Renames the two temporary symmetry plane
-renameBC=4000,5000 -renameBC=4001,5001 boundary conditions 4000 and 4001 to their
final identifier 5000 and 5001 (periodic
boundary conditions).

15.3.2. fluent2fensap
The ANSYS Fluent case and solution file (.cas(.h5) and .dat(.h5)) can easily be converted to
a FENSAP grid and airflow solution format.

[Link]. Description
This operation is usually done within FENSAP-ICE by selecting a .cas(.h5) file as the grid input
file. The import panels will provide the means to fine-tune the boundary conditions, reference
conditions and solution field association.

The fluent2fensap process is fully automated and normally does not require adjustments.

Reference values are extracted from the Fluent configuration and written in the solution file header.
The values in the solution file header are required only for:

• Viewmerical Postprocessing:

The calculation of the pressure coefficient requires PINF, TINF, VELINF. The calculation of the
airflow Mach number requires RGAS, GAMMA. The calculation of the relative velocity components
require RPMX, RPMY, RPMZ.

• CHT3D Anti-Icing:

Requires RGAS, GAMMA, VELINF.

Note:

If the reference velocity value selected by fluent2fensap is not correct, it

must be reset with the proper value, otherwise CHT3D will not be able to compute
the correct surface temperature and heat fluxes.

[Link]. Command Line Reference

fluent2fensap [Link] OUTPUT [parameters] Reads from the Fluent case file [Link]
(and optionally [Link], if in the same

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
418 of ANSYS, Inc. and its subsidiaries and affiliates.
 Grid Operations

location), and write to the OUPUT prefix

([Link], [Link], etc.).

Table 15.17: Options

-d Diagnostic mode. Does not write the output

file but list its content (reference values,
solution datafields, zones and boundary
conditions).

Table 15.18: Icing Options

-roughness=FILE If Fluent was configured with a roughness

profile, typically obtained from ICE3D
beading model in a previous FENSAP-ICE
computation, it is required to apply the same
roughness value in the airflow solution file
converted from Fluent format. This argument
permits to specify a [Link] file,
with the roughness distribution. The
roughness values will be inserted in the
output airflow solution file written by flu
ent2fensap. The roughness information
will be used by ICE3D, if the beading model
is enabled.

A [Link] file related to the node

number and ordering in the grid. If the
Fluent grid has been remeshed, or reordered,
the [Link] of the previous shot
cannot be used as-is, and will need to be
re-interpolated on the new grid: Use then
the rough2rough tool.

Table 15.19: Output Files

-nosoln Will not read a .dat(.h5) file nor write a

soln file.
-ascii Output FENSAP grid written in ASCII (default
is binary).
-solid Write a solid grid (for use with C3D).
-imat Write a multi-material grid (for use with
FENSAP/DROP3D and multiple domains). This

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 419
Tools Reference

is automatic if the Fluent grids have more

than one cell section.

Table 15.20: Multi-Zone Options

-materials=ZONE,ZONE,ZONE Optional. Provide a specific order for the

material IDs.

Table 15.21: Solution Options

-rotVX=RPM Convert a relative-frame solution to absolute.

-rotVY=RPM Convert a relative-frame solution to absolute.
-rotVZ=RPM Convert a relative-frame solution to absolute.
-rotabs Indicate the solution is absolute frame. Use
–rotVX/-rotVY/-rotVZ to specify the rotation
speed which will be stored in the solution
header (used for post-processing).

Table 15.22: Boundary Conditions

wall-6:2001 wall-7:2002 "inlet with Fluent boundary conditions are matched to

spaces":1001 non-useful-internal-wall:0 suitable FENSAP boundary condition types
and identifiers. The automatic behavior can
be overloaded by using the ZoneName:BC
syntax. Use quotes for zone names with
multiple words separated by spaces. If the
boundary condition identifier 0 is chosen,
the facet zone will not be written. Refer to
the Boundary Conditions (p. 73) for details
on boundary condition identifiers.

[Link]. Reference Values

The reference values automatically detected from Fluent configurations can be replaced on the
command line by using the VAR=VALUE syntax.

Table 15.23: The Following Values are Important

VELINF Reference velocity (m/s)

TINF Reference static temperature (K)
PINF Reference static pressure (Pa)

Table 15.24: The Following Values are Optional

LENINF Reference length (m)

VELX, VELY, VELZ Components of the reference velocity (m/s)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
420 of ANSYS, Inc. and its subsidiaries and affiliates.
 Grid Operations

RPMX, RPMY, RPMZ Rotation speed (rpm)

Table 15.25: Variables with a Default Value

RGAS 287.05 GAMMA 1.4 (kJ/kg K, gas constant for air)

Table 15.26: Variables Continued

MACHINF, HINF, XKEINF, RHOINF, P0INF, Variables computed automatically from the
ZMUINF, REINF, PRINFND, ENTRINF other variables above.

[Link]. Examples
Table 15.27: fluent2fensap Commands

fluent2fensap cht_ext.cas cht_ext Writes chg_ext.grid (and

cht_ext.soln, cht_ext.hflux,
cht_ext.surface, if there is a
check_ext.dat in the same directory).
fluent2fensap cht_ext.cas cht_ext TINF=265.3 Same as above, however the reference
temperature read from the file is adjusted
to 265.3 K.
fluent2fensap cht_solid.cas cht_solid Writes the output file in a format compatible
wall-6:6100 -solid with C3D. The wall-6 surface is converted to
a heater boundary condition (range
6000-6999).

15.3.3. fensap2fluent
This tool permits to convert a FENSAP grid into the Fluent grid format. The file will contain only the
grid and boundary condition types, no solver settings are written.

[Link]. Description

Important:

Some grids with periodicity will be converted to a Fluent file with invalid shadow zone
surfaces, and Fluent might fail to read them. In such a case, the suggested approach is:

• Convert the grid using the –noperiod option or prepare an input grid with convertgrid
INPUT OUTPUT -notperiodic.

• Rotational periodicity: Operations required in Fluent after the conversion.

– For each cell zone: Set-up the rotation axis.

– For each facet periodic zone: Set up the periodicity type as rotational.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 421
Tools Reference

• Translational periodicity : No operation required.

Note:

A Check Mesh operation in Fluent can confirm the grid periodicity is correctly set up.

[Link]. Command Line Reference

Table 15.28: General Commands

fensap2fluent grid soln -out=OUT [options] Read the FENSAP format grid and airflow
solution soln, and writes to [Link] and
[Link].
fensap2fluent grid -nosoln -out=OUT [options] Grid-only conversion. Reads the file grid,
and writes to [Link].

Table 15.29: Input File Options

-solid Reads a C3D solid grid file format.

-read=[Link] Reads a reference case file, some options
(solver settings, zone numberings) will be
copied in the new output .cas(.h5) file.
This might result in an incomplete Fluent
configuration.
-modifyNodes=[Link] Reads a reference case file and writes it as
output, with the only modification being the
XYZ coordinates of the nodes, read from the
input FENSAP grid. This is used to displace
the nodes after ICE3D ALE grid displacement.
-h5 Writes a .cas.h5 file.

Table 15.30: Output File Options

-ascii Fluent file will be written in ASCII.

-noperiod Disable periodicity writing.

15.3.4. cfx2fensap
cfx2fensap is a tool introduced in FENSAP-ICE 2015R1.0 to enable automatic conversion from CFX
.res format to FENSAP grid and airflow solution formats. General usage is similar to fluent2fensap.

[Link]. Description
This operation is usually done within FENSAP-ICE, by selecting the .res file as the grid input file
for a run. The import panels will allow fine-tuning of the boundary conditions, reference conditions

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
422 of ANSYS, Inc. and its subsidiaries and affiliates.
 Grid Operations

and solution field associations. In FENSAP-TURBO simulations, multi-row grids can be separated
and automatically configured in FENSAP-ICE.

Note:

CFX must be installed on the machine where cfx2fensap is launched, and the
cfx5cmds tool is accessible, either via a global execution path, or the command line
below.

-cfxPath=/path/

Used to indicate the path of the bin/ subdirectory of the current installation of
CFX.

Alternatively, if a CCL appears alongside the input .res file, CFX is not required to reside on the
execution machine. ([Link] alongside [Link]) The CCL can be generated in the following
way.

• From CFX-Pre:

File → Export → CCL → select all objects.

• cfx5cmds - read -definition [Link] -text [Link]

Generates a CCL from a command line.

[Link]. Command Line Reference

cfx2fensap [Link] OUTPUT [options]

Reads from the CFX solution file [Link], and writes to the OUTPUT prefix ([Link],
[Link], etc.).

Table 15.31: Output Options

-zone=N Extract a subzone of the grid (1-N), only, for

example, a turbofan stage, or a single
material.
-split Write all subzones of the grid to different
[Link] files. Used for turbo-fan
grid, separated in multiple rows.
-hflux -shear Write hflux and shear stress facet-based files.
-solid Write a solid grid (for use with C3D).
-notperiodic Write a grid without considering its
periodicity (translational or rotational).
-roughness=FILE Specify a [Link] file from a
previous ICE3D execution on this grid. The
roughness data will be appended to the
converted airflow solution in FENSAP format.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 423
Tools Reference

This is done automatically at each shot

(except the first) of a Multishot-CFX
simulation.

[Link]. Boundary and Reference Conditions

Boundary Conditions:

CFX boundary conditions are matched to suitable FENSAP boundary condition type and identifiers.
The automatic behavior can be overloaded by using the ZoneName:BC syntax. Use quotes for
zone names with multiple words separated by spaces.

If the boundary condition identifier 0 is chosen, the facet zone will not be written. Refer to
Boundary Conditions (p. 73) for details on FENSAP boundary condition identifiers.

Table 15.32: Boundary Condition Identifier

Wall1:2001 Wall2:2002 "inlet with spaces":1001 Boundary Condition Identifier at 0.

non-useful-internal-wall:0

Reference Conditions
The detection is done automatically from the CFX settings and flow solution, but should be reviewed
in the output log.

• The reference velocity and reference temperature are the average quantities of the airflow velocity
and static temperature distributions at the inlet of your CFD solution. For multi-domain solution
files:

– in -zone-N mode, the reference values are computed at the inlets of the selected domain,

– while in default or -split mode, the reference conditions are computed at the global inlets of
the multi-domain.

• The reference pressure is taken from the Reference Pressure field located in the Domain panel
of CFX as long as its value is non-zero. If the Reference Pressure in CFX is set to zero, the reference
pressure used during conversion is set to 101,325 Pa.

CHT3D/CFX requires proper reference condition values in the FENSAP solution file.

Refer to fluent2fensap (p. 418).

15.3.5. Conversion from FENSAP to CFX

The automatic conversion of a FENSAP grid file to CFX format is not natively supported. Instead, the
FENSAP file is to be converted to a Fluent file using fensap2fluent and then the new Fluent mesh
is read by CFX-Pre.

An existing CFX-Pre configuration can be updated from a new, compatible, mesh if the original mesh
is overwritten and the File → Reload Mesh Files option is chosen.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
424 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solution File Operations

15.4. Solution File Operations

The following sections of this chapter are:
15.4.1. solnEdit
15.4.2. soln2soln

15.4.1. solnEdit
solnEdit is a tool that enables operations on a solution file.

[Link]. Description
Operations range from:

• Imposition of a constant value on a datafield, or a part of a datafield.

• Imposition of an analytic value on a datafield.

• Modification of solution header information.

• Conversion of solution files from non-SI unit systems.

• Combination of datafields for postprocessing operations.

Note:

Advanced edition of an INPUT solution file is not a supported feature of FENSAP-ICE. A

modified solution file might affect the solver convergence and the physical accuracy of
your computations. This command should only be used for postprocessing or data ana-
lysis purposes.

[Link]. Command Line Reference

Note:

solnEdit -h

For a complete, and fully up-to-date command reference description, use the
built-in command line help with the above script.

Table 15.33: solnEdit

solnEdit GRID INPUT OUTPUT [options] The solution file INPUT and its related grid
are read, and the file OUTPUT is written.
-l Printout the content of the solution file, the
OUTPUT argument can be omitted.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 425
Tools Reference

-c3d Input grid is a C3D solid grid.

Table 15.34: Options

FIELDNAME=EXPRESSION The content of the named field will be

replaced by the expression value. Expressions
are Maple-like. Use enclosing quotes around
EXPRESSION if spaces are used in the
expression.

For example "XVEL=Z^2"

Available variables are: the 4-letter solution

field names, X, Y, Z, NN (node ID), MAT
(material ID).
FIELDNAME:#=EXPRESSION For unsteady fields, # permits to select the
time level to change.
"PRES:2=sqrt(X*X+Y*Y)*1000 + 101325" Specify a boundary condition where the
FIELDNAME@BC=EXPRESSION values are applied. When no boundary
condition is specified, the value is applied
to the whole datafield, internally too.
Multiple boundary conditions and a
no-boundary condition expression can be
specified simultaneously.
FIELDNAME=@FILENAME@FIELD The entire content of FIELDNAME will be
replaced by the content from the source
solution file. The source solution must be
from a grid with the same number of nodes,
however the file format and available fields
may differ.
-convertToMetricFrom=[ft/s,in/s,mph,m] This converts the solution for velocity,
[,[psi,psf,Pa,kPa,lbm/ins2], [R,F,C,K], pressure, temperature, density using the
[kg/m3,lb/in3,lb/ft3]] specified units.

[Link]. Examples
Example 15.3: Print the Content of a Solution File

solnEdit grid soln -l

Prints the content of a solution file. The output record below shows the list of available
fields, as 4-letter groups.

...reading grid

...done

Grid BCs : 1000 2000 3400 4100

== File information:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
426 of ANSYS, Inc. and its subsidiaries and affiliates.
 Solution File Operations

nodes: 4854 fields: 6 lvltime: 1

Available fields : DENS ( Density (kg/m^3) )

Available fields : PRES ( Pressure (N/m^2) )

Available fields : XVEL ( V1-velocity (m/s); Velocity )

Available fields : YVEL ( V2-velocity (m/s) )

Available fields : ZVEL ( V3-velocity (m/s) )

Available fields : TEMP ( Static temperature (K) )

Header variable #1 : 287.054

Header variable #2 : 1.4

Header variable #3 : 288

...

Example 15.4: Modify the Content of a Datafield

solnEdit grid soln soln_out TEMP=288 Assigns a constant value.

Example 15.5: Modify the Content of a Datafield on a Specific Boundary Condition

solnEdit grid soln soln_out TEMP@2000=288 Assigns a constant value on wall 2000.

Example 15.6: Set up Material-Specific Values (Two Possible Syntaxes)

solnEdit grid soln soln_out Syntax 1

"TEMP=ifValue(MAT==1,288,270)"
solnEdit grid soln soln_out Syntax 2
"TEMP=(MAT==1)*288+(MAT==0)*270"

See Expression Syntax (p. 411) for more details regarding the available expression operators.

15.4.2. soln2soln
The soln2soln command interpolates a solution file from one grid to another. The grids can be
node-matching or non-node-matching.

[Link]. Description
If the grids are exactly node-matching, no interpolation will be required, the solution will simply
be copied from one grid to the other. This is useful if a solution must be copied onto a grid that
has been reordered. Use the -nodes option for this specific mode.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 427
Tools Reference

If the grids are not node-matching, each target node will be interpolated in 3D in the source grid
cells. If the node lies outside of the original grid volume, the value at the closest surface projection
is used. This feature must be used with caution.

Note:

Wall nodes have a special treatment. For some datafields (temperature, pressure, velocity,
heat flux, forces, beta), their value will be projected to the closest wall of the target grid.
Use the -raw option to disable this behavior.

If the source grid is curvilinear two-dimensional (such as ICE3D output grid files), it is suggested to
use the -flat option.

[Link]. Command Line Reference

soln2soln GRID1 SOLN1 GRID2 SOLN_OUT [options]

This command interpolates solution1 values from grid1 to grid 2 and writes SOLN_OUT.soln.

Note:

For FENSAP/DROP3D solution files, it interpolates wall-based hflux/shear/beta on surfaces

only.

Table 15.35: Options

-raw Disable any automatic behavior (wall only,

slip/noslip).
-flat Use with [Link]/[Link] source
(GRID1) files.
-nodes Use with reordered grids or grids same nodes
coordinates, no interpolation is done,
interpolation is a closest-node search.
-walls Interpolate all points from the nearest WALL
boundary condition of the input grid.
-perbc Values are computed on boundaries only
and closest-surface/point search is done on
the matching boundary condition in the
other grid. The two grids must share same
boundary condition identifiers.

Table 15.36: Optimizations

-outbc Values computed on the target boundaries

only (internal nodes = 0).
-threads=N Execute the interpolation using multiple CPU
cores.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
428 of ANSYS, Inc. and its subsidiaries and affiliates.
 TimeBC Operations

[Link]. Examples
Table 15.37: Interpolating Solutions

soln2soln grid_orig soln grid_reordered Interpolate solution of a reordered grid

soln_ordered -nodes (different node ordering).
soln2soln grid1 soln grid2 soln.2 -threads=4 Interpolate solution between two different
grids of same general geometry
(Interpolation using multi-cores is much
faster).

Table 15.38: Interpolating swimsol Files and 3D Airflow Wall Values

soln2soln [Link] swimsol grid_3d Interpolate a swimsol file onto the 3D

swimsol.3d -flat airflow grid.
soln2soln grid_3d soln [Link] [Link] Interpolate 3D airflow wall values onto a 2D
-walls flat grid.

15.5. TimeBC Operations

The following sections of this chapter are:
[Link] Files
15.5.2. interpTimeBC
15.5.3. genTimeBC
15.5.4. interpTurboDropTimeBC (TURBO)
15.5.5. mergebcs
15.5.6. generateRoughnessDat

15.5.1. TimeBC Files

TimeBC files ([Link] and [Link]) are used to specify nodal boundary condition
values to FENSAP and DROP3D.

The timebc file is used for inlet, wall and/or exit boundary conditions, and is created by fensapice
GUI from the values input in the boundary conditions panel. A custom file can be created using these
command line tools.

FENSAP
Custom timebc files can be set, overriding some settings of the boundary conditions panel, this feature
is for expert users and can be enabled by enabling the advanced options in FENSAP-ICE (Settings →
Preferences → Show advanced / beta solver options (available at next restart)). The Initial con-
ditions panel will then be accessible in the Conditions panel of FENSAP.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 429
Tools Reference

DROP3D
Custom timebc file can be set in the Droplet initial solution panel, by choosing Input Profile →
TimeBC file.

The TimeBC files can be viewed with the Viewmerical post-processor by using either the TimeBC file
input solution type, in the data-loader panel, or by launching it from the command line with the
viewmerical TIMEBC grid [Link] command.

15.5.2. interpTimeBC
interpTimeBC interpolates the nodal values of a grid/solution onto the nodes of a grid, writing
these values to a timebc file.

[Link]. Description
A typical case for this command is when running a simulation using a solution from a different flow
solver (Fluent, CFX and so on) in which the inlet velocity is not uniform. The source and destination
grids are then the same and the boundary condition inlet values are extracted to a TimeBC file.

[Link]. Command Line Reference

Table 15.39: interpTimeBC Command

interpTimeBC GRID1 SOLN1 GRID2 BCLIST Will interpolate, in grid1+solution1 values

FIELD [FIELD FIELD...] [options] for each node of the specified boundary
conditions in grid 2. FIELD is the 4-letter field
name of FENSAP/DROP3D. Such as DENS or
DRUU, BCLIST can be a single boundary
condition, or a comma-separated list of
boundary conditions (BC,BC,BC). If BCLIST is
-1, all the INLET+WALL+OUTLET will be
interpolated.

The input and output grids can be the same,

will be faster and interpolation-free.

Table 15.40: Options for DROP3D (Droplets)

-drop3d Converts XVEL,YVEL,ZVEL fields (if specified)

to a DROP3D input [Link].
-lwc=VALUE Adds a LWC (liquid water content) entry to
the timebc, with the specified value.

Table 15.41: Options for DROP3D (Crystals) (TURBO Specific)

-icc=VALUE Adds a ICC (ice crystal content) entry to the

timebc file, with the specified VALUE.
-dtemp=VALUE Adds a constant droplet temperature.
-ctemp=VALUE Adds a constant crystal temperature.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
430 of ANSYS, Inc. and its subsidiaries and affiliates.
 TimeBC Operations

-crystals Converts XVEL,YVEL,ZVEL fields (if specified)

to a DROP3D CRYSTAL input [Link]
file.
-out=FILENAME Specifies the output filename (default is
[Link]).

Note:

-drop3d and -crystals can be combined, leading to a droplet+crystal [Link]

file.

[Link]. Examples
Example 15.7: Extraction of Droplet Inlet Conditions from an Air Solution File

interpTimeBC grid.row01 soln.row01 grid.row01 1001 XVEL YVEL ZVEL -drop3d -lwc=0.001

The example above is:

• reading the airflow input solution from the source grid.

• writing a drop3d timebc file, for the same grid.

• extracting the X/Y/Z velocity components from the airflow for the droplet solution.

• setting a constant value of 0.001 for the droplet LWC.

Example 15.8: Droplet & Crystal Timebc Input File (TURBO Only)

interpTimeBC grid.row01 soln.row01 grid.row01 1001 XVEL YVEL ZVEL -drop3d -lwc=0.001 -crystals
-icc=0.009 -dtemp=270 -ctemp=270

Sets up a droplet and crystal timebc input file.

15.5.3. genTimeBC
genTimeBC generates a timeBC or a sandgrain roughness file from scratch.

[Link]. Description

Note:

This feature is for advanced users.

[Link]. Command Line Reference

Change GRIDFILE text to: genTimeBC GRIDFILE "BC,Variable,Expression" [...]
[-c3d -fensap -drop3d -rough -ale]

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 431
Tools Reference

genTimeBC is a tool enabling to create a timebc (boundary profile) input file. On a specified
GRIDFILE it can define boundary conditions for one or multiple boundary conditions. The value of
each boundary condition to write in the file, is defined by a tuple BC,Variable,Expression.
The command line can state multiple tuples. By default, the type of the boundary profile is -fensap,
the tool can be switched to alternate modes using the other options.

Table 15.42: genTimeBC Command

genTimeBC GRIDFILE "BC,Variable,Expression" • GRIDFILE = Grid for which the time-

[...] [-c3d -fensap -drop3d -rough -ale] [Link] is generated

• Tuple = BC,Variable,Expression

• BC = BC to define

• Variable = Target variable to define on the

boundary condition

Solver mode dependent:

• fensap = P,U,V,W,T,TURB1,TURB2

• drop3d =
LWC,U,V,W,DIAM,CRYST_LWC,CRYST_U/V/W

• c3d = TEMP,HEAT

• ale = DISPX,DISPY,DISPZ

• other = VAR_# the specified number will

be used on the timebc entries

• C3D only = For facet-based boundary

profile, prefix a F to the tuple : "F**,***,***"

• Expression = An algebric expression

computing the value of the BC at each
nodal location of the boundary condition
(See Expression Syntax (p. 411)). The
expression can use X,Y,Z as input variable.

Table 15.43: The Expression Can Make Use of the Following Variables

XYZ Coordinate of the evaluated node.

XMIN XMAX YMIN YMAX ZMIN ZMAX Minimum/maximum boundaries of the set
of nodes belonging to the boundary
condition.
T For time based equations (use
-timeStart/Step/End also).
Time-based file (default is time = 0, no time step)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
432 of ANSYS, Inc. and its subsidiaries and affiliates.
 TimeBC Operations

-timeStart=VALUE

Time value used for the first step.

-timeStep=VALUE

Time step used (require -timeEnd).

-timeEnd=VALUE

Final Time.

Table 15.44: The Variable Parameter Is Ignored for Roughness

-drop3dConfig=[Link] Reads the DROP3D configuration and write

a suitable [Link] file.
-bcExtra=BC,Variable,Extra For advanced format timebc, last line value
specification.
-out=[Link] Sets the custom output file name.

15.5.4. interpTurboDropTimeBC (TURBO)

interpTurboDropTimeBC

Performs manual row-by-row pitch-averaging interpolation for sequential DROP3D runs.

[Link]. Description

Note:

This is a TURBO feature only.

This tool permits to do row-per-row pitch averaging of solution data, to create a [Link] file
to use in the next row. The tool will extract conditions from droplet or crystal solutions.

In addition to the pitch-averaged value, the tool permits value injection by modifying the value
with an expression. Expressions can read a datafile to construct a 1D inlet-profile dataset.

[Link]. Command Line Reference

Table 15.45: Reading a DROPLET Solution

interpTurboDropTimeBC GRID1 SOLN1 This tool will read a DROPLET solution for
bcGRID1 GRID2 bcGRID2 [-nmix NMIX] [-LWCref GRID1 and will interpolate onto GRID2 a
VALUE] [-mflux] [-out FILE] [Link] file, for use as input to
[-varChange=FIELD,EXPR]

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 433
Tools Reference

DROP3D. Values are interpolated from BC1

of grid1 to BC2 of grid2.

Table 15.46: Mandatory Parameters

-nmix Number of sample points to use for the

integration (suggested value: 50).

Table 15.47: Optional Parameters

-rot X DEPRECATED, If the GRID1 solution is in a

rotating frame of reference and the GRID2
computation is not, specify the rotation in
RPM. (from 2012 onwards, all solutions are
in absolute frame of reference).
-rotout X Specify the GRID2 rotation speed. The
[Link] written will be added that
rotation speed.
-rotx/-roty/-rotz Specify the rotation axis (default Z).
-mflux Integrate the velocity by poderating using
the mass-flux info.
-autoLWC if -LWCref is not needed, this mode will:
compute the mean LWC from the input
outlet, and write it to the [Link] of
the current dir; read the LWC from the input
solution's directory [Link], and use
it for the clipping.
-LWCref / -ICCref The reference LWC value default is 0.001
gm/m^3. Values below LWCREF*1.25e-6 will
be clipped to zero.
-crystal Writes a crystal timebc file instead. LWC
options will apply to ICC for a hybrid
droplet+crystal timebc file, use mergebcs
tool.
-out FILENAME Specify an output file (default is time-
[Link]).
-varChange=FIELD,EXPR Permits to modify the interpolated datafield,
either by fully replacing the value, or mixing
it with other values in the equation. EXPR is
an algebraic equation which can be
constructed with the X,Y,Z,R,THETA variables
and the current variable name. For Linux O/S:
put the full -varChange in single quotes
to ensure proper shell parsing. Variables are:
LWC,U,V,W[,TEMP,DIAM]. The TEMP and

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
434 of ANSYS, Inc. and its subsidiaries and affiliates.
 TimeBC Operations

DIAM fields are accessible only if the input

solution has them.

Table 15.48: Examples

-varChange=LWC,0.333 Forces the LWC to a constant value.

'-varChange=LWC,"(R>0.5)*LWC+(R<=0.5)*0.001' Forces the LWC to 0.001 if the R coordinate
is less than 0.5.
'-varChange=TEMP,fileData1D(R,"[Link]")'
Loads the text file [Link] as
a 1D linear lookup table. It will change the
value of the variable TEMP, for which a new
value will be computed as a function of R.

[Link]. Examples
Table 15.49: Interpolation of Droplet Values with Temperature Modification

interpTurboDropTimeBC grid.row01 The [Link] file here used will

droplet.row01 0 grid.row02 0 -nmix 50 -LWCref be interpolated as a function of R. The
0.001 -mflux -out [Link] -rotx general format of such a file is:
-varChange=TEMP,
fileData1D(R,"[Link]")' number_of_points

r valuer value

...

If the value of R falls between two entries, a linear interpolation is computed. See Expression Syn-
tax (p. 411) for reference on the possible input syntaxes for the varChange second argument.

Table 15.50: Interpolation of Both Drop and Crystals

interpTurboDropTimeBC grid.row01 Interpolate droplets and store in the output

droplet.row01 0 grid.row02 0 -nmix 50 -LWCref file [Link].
0.001 -mflux -out [Link] -rotx
interpTurboDropTimeBC grid.row01 Interpolate crystals and store in the output
crystal.row01 0 grid.row02 0 -nmix 50 -ICCref file [Link].
0.009 -mflux -out [Link] -rotx
mergebcs [Link] [Link] Combine the two timebc files in a single
[Link] [Link].

15.5.5. mergebcs
mergebcs merges two timebc files defined on the same grid. The two files must not have any conflicts
(different BC-Variable-Node entries). Typically mergebcs is used to combine separate droplet and
crystal timebc files into a single one.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 435
Tools Reference

It can also be used to merge the output of a TimeBC interpolation (interpTimeBC and a field-
specific evaluation with equations or 1D profiles generated using genTimeBC).

Table 15.51: Usage

mergebcs TIMEBC_FILE_1 TIMEBC_FILE_2 Merges the output of a TimeBC interpolation

TIMEBC_OUT (interpTimeBC and field-specific evaluation
with equations or 1D profiles generated using
genTimeBC).

15.5.6. generateRoughnessDat
generateRoughnessDat creates a surface sandgrain roughness input file with values computed
from a specified solution file.

[Link]. Description
The sandgrain roughness file is defined with reference to the airflow (3D) grid, but if quantities
from an ICE3D (surface) solution are to be used, the solution must be transmogrified onto the 3D
grid. Use soln2soln in -flat mode to do this (See Examples (p. 437)).

[Link]. Command Line Reference

Table 15.52: Creating a [Link] File

generateRoughnessDat GRID [options] Creates a [Link] file using the

specified options. Each successive option
may overwrite node values of the previous
options.

Table 15.53: Options

-bc:ID=VALUE Applies a value to all boundaries with

ID=VALUE.
-range:XMIN,YMIN,ZMIN,XMAX,YMAX, Range will apply to any wall.

ZMAX=VALUE
-solnVar:SOLNFILE:FIELD:>FIELDVALUE:AX,YMAX,From the soln file solution file, read the
datafield FIELD. For each node for which the
ZMAX=VALUE value is greater than FIELDVALUE, the
[Link] file will contain the value
ROUGHVALUE. The < operator is also
available.
-node:ID=VALUE Assign the specified VALUE to the node
number ID.
-out:FILENAME Specify an optional different output file
name.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
436 of ANSYS, Inc. and its subsidiaries and affiliates.
 TimeBC Operations

[Link]. Examples
Table 15.54: Set up Roughness Values from Ice Thickness in Solution

soln2soln [Link] swimsol grid swimsol_3d For each node where the ice thickness is
-flat generateRoughnessDat grid greater than 0.0001, a roughness of 0.003
-solnVar:swimsol_3d:WWIT:>0.0001:0.003 (m) is set in the output file.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 437
 Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
438 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 16: Post-Processing
The following sections of this chapter are:
16.1. Post-processing
16.2. Viewmerical
16.3. CFD-Post Macros

16.1. Post-processing
The default FENSAP-ICE post-processing tool is Viewmerical, the native post-processor of FENSAP-ICE.
However, it is also possible to visualize your FENSAP-ICE solutions using other post-processors such as
CFD-Post, Fieldview, Fluent, EnSight and Tecplot.

To change the default post-processing tool, go to Settings → Preferences → Postprocessing to open

the configuration window.

Write CFD-Post launch files: When selected, a [Link] file is set up in the run directory at the
start of each solver run. This file is a CFD-Post setup file and can be used to load the data of this run
directory, directly from CFD-Post. For more information regarding this setup file, consult View Set-up
File in the CFD-Post User's Guide.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 439
Post-Processing

Alternatively, when CFD-Post is selected as the default post-processor, the View action will launch CFD-
Post with the selected file.

Note:

CFD-Post can read FENSAP grid and solution files and the .fsp view set- up file, see FENSAP-
ICE Files within the CFD-Post User's Guide. Older versions cannot be used to load these files.

When a different option is selected, the pull-down menu will change to the new default setting; for
example, after selecting Viewmerical as the default post-processor, the pull-down menu will show View
with VIEWMERICAL.

A tool to convert the FENSAP-ICE grid and solution files into the TECPLOT ASCII file format is also
available. The converter nti2tecplot can be found in the FENSAP-ICE installation directory.

Note:

• The FENSAP-ICE grid file should be named grid.

• The FENSAP solution file should be named soln.

• The DROP3D solution file should be named droplet.

• The ICE3D solution file should be named swimsol.

• The ICE3D initial and displaced grid files should be named, respectively, [Link] and
[Link].

In this chapter, the native post-processor Viewmerical is described as well as the icing related macros
for CFD-Post that facilitate the visualization and creation of icing related images and videos.

16.2. Viewmerical
In this section you will learn the different capabilities of FENSAP-ICE's native post-processor.

16.2.1. Introduction to Viewmerical

Viewmerical is a simple data post-processor that enables the visualization of FENSAP-ICE grids and
solution files. It can be launched from FENSAP-ICE to view most file formats, and can be used in
command-line or batch mode. The major features are:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
440 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Features Action
Grid Display • Boundaries

• Cutting planes, crinkle cuts

• Multiple grids display (split screen, overlay)

Scalar Solution Display • Colormap

• Iso-values, iso-surfaces

• Vector fields

• Unsteady/animated solutions

ICE3D Specific Display • Ice cover

• Ice solution

• Glaze/rime/film zones

• Unsteady/animated icing

• Ice CAD surface extraction

FENSAP-ICE Specific File Formats (Grids) Grids:

• FENSAP

• C3D (with materials)

• OptiGrid GENERIC input/output format

FENSAP-ICE Specific File Formats (Solutions) • FENSAP (soln)

• DROP3D (droplet)

• ICE3D (swimsol)

• C3D ([Link])

• Heat flux ([Link])

• Shear stress ([Link])

• Time-BC ([Link])

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 441
Post-Processing

Features Action
• Roughness ([Link])

Table 16.1: Other File Formats

Type Format
Grids • Fluent

• STL

Solutions • Fluent

[Link]. Launch from the FENSAP-ICE Project Manager

The button in the toolbar permits to launch Viewmerical:

If a grid or solution icon is selected, Viewmerical will be launched to open that file automatically.

[Link]. Setup in FENSAP-ICE as Primary Post-Processor

In the solver execution panel, the View button will launch the default post-processor.

The default post-processor of FENSAP-ICE can be selected in the Preferences panel:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
442 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Once configured, the main visualization option in the menus will be Viewmerical. Using the option
View with VIEWMERICAL on a solution file will load the selected grid and solution from FENSAP
automatically:

[Link]. Launch from FENSAP-ICE - Secondary Post-Processor

At any time, any alternate post-processor (including Viewmerical) can be launched to view input/out-
put datasets.

[Link].1. From the Run View

Right-click an input/output icon and select View with...:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 443
Post-Processing

[Link].2. From the Execution Panel

Holding the Ctrl key will switch the view button from View to View with..., which will enable
you to select the post-processing viewer to use:

[Link]. Launch from the Command Line/Start Menu

Viewmerical can be launched standalone; it does not require a FENSAP-ICE main window or project
and can be used on any compatible input file.

Note:

A valid FENSAP-ICE license is required to Viewmerical. It can only be used on machines

where your license server can be reached. Each license seat of FENSAP-ICE provides a
seat for one opened instance of Viewmerical.

16.2.2. 3D Display
The following sections of this chapter are:
[Link]. Mouse Controls
[Link].Toolbar
[Link]. Axis Display
[Link]. Interactive Menu
[Link]. Keyboard Shortcuts

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
444 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

[Link]. Mouse Controls

Table 16.2: Mouse Control Examples

Button Action +Shift +Control +Alt* Double-click

Left Rotation Zoom Zoom Box Pick Center
Right Zoom/Roll Menu
Center Pan Center
Scroll wheel Zoom

Tip:

Alt button operation might not work in all windowing environments. In such cases, use
the toolbar pick icon.

Table 16.3: Controls

Control Action
Rotation Moving the mouse with the left button
pressed will rotate the camera around the
object.
Zoom Moving the mouse up/down permits to zoom
interactively. The scroll-wheel button of the
mouse also zooms.
Zoom Box With the zoom box selected, moving the
mouse left-to-right will permit to draw a
zoom rectangle.

Figure 16.1: Zoom in

If the rectangle is drawn right-to-left, the

resulting operation will zoom-out.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 445
Post-Processing

Control Action
Figure 16.2: Zoom out

Zoom/Roll In this mode, up-down movements will zoom

in-out interactively.

Left-right movements will roll around the

view axis.
Pan Holding the center button (usually the
scroll-wheel) and moving the mouse will pan
the view. This will move the center of
rotation.
Center Double-clicking a 3D position to center the
display on that point. The center of rotation
is moved to the chosen point.
MENU See Interactive Menu (p. 449).
Pick Puts you in data query mode (use with the
Query panel).

[Link]. Toolbar
At the top of the 3D display, a toolbar permits to switch between the main view modes which are
normally accessible via mouse + keyboard combinations. See Interactive Menu (p. 449) for the
equivalent keyboard/mouse bindings, and the operation description.

Table 16.4: Toolbar

Action Icon
Toolbar

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
446 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Action Icon
Rotation

Zoom Box

Pick

Screenshot

MENU

See Interactive Menu (p. 449).

Note:

Keyboard-mouse combinations described in Mouse Controls (p. 445) will not work if Zoom
Box or Pick are enabled. All keyboard-mouse combinations will work correctly if the
Rotation mode is selected.

[Link]. Axis Display

Clicking in the axis window will trigger a view change.

Table 16.5: Axis Display

Action Result
Click the X/Y/Z arrows Orients the display along that axis.
Click the gray cube Orients the display in the default 45 degree
isometric view.
Shift + X/Y/Z/gray cube Orients the display in the reverse direction
(If X-axis would show the front along +X,

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 447
Post-Processing

Action Result
Shift-click-X-axis would show the back along
-X).
Anywhere else Keeps the same camera direction; resets the
zoom and the center of rotation to view all
items. Will use the current Fit to view (vis-
ible) or Reset view (domain) settings.

Right-clicking the axis window provides additional view options:

Table 16.6: Additional View Options

Action Result
Fit to view (visible)/Reset view (domain) Resets the zoom and center of rotation in
order to view all items.

• Fit to view (visible):

– Only visible items are considered.

• Reset view (domain):

– All items, even invisible, are considered

for the bounding box.

– Using the Backspace key, or clicking in

the axis window, will use the current
Fit/Reset setting.

Front, Back, Right, Left, etc. Reset the view to this direction.
Camera Switch between Orthogonal and Perspect-
ive.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
448 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Action Result
View symmetry Permits to duplicate or repeat symmetric or
rotationally periodic datasets.

[Link]. Interactive Menu

A Ctrl left-click in the 3D display, or the usage of the Menu button shows the interactive menu:

Table 16.7: Interactive Menu

Menu Item Result

Hide (click on surface) • The clicked-on surface is hidden.

• In Ctrl + right-click, the hide operation is

immediate.

• When using the toolbar menu, the surface

to hide must be clicked on afterwards.

Undo Hide Undo the previous Hide operation.

Show all/Hide all Show/hide all surfaces of all objects.
Hide all except one (click on surface) All surfaces of all objects are hidden, except
the one that was clicked upon.
Refresh Reloads the scalar solution data (if any) from
disk.
Command window Open the 3dview command console
window.
Save state Create a view state file (.views by
default) and a command file (.3DCMD by
default). If used as command file argument,
the command file permits to restart
Viewmerical in the saved state. Not all modes
and settings are saved.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 449
Post-Processing

Menu Item Result

Save screenshot Saves a .PNG screenshot to disk. The toolbar
and the axis display will not be saved in the
image file.
Save/Restore position Viewmerical permits to save the current
camera position, and reuse it in later
execution. In addition, multiple camera
positions can be saved and chosen from.

• default view: If the view is saved as

default, Viewmerical will
automatically load that view when
launched in the same directory.

• These views are saved in a

.views.3dview file in the current
directory, the default and saved views
can be reset by erasing that file.

[Link]. Keyboard Shortcuts

Table 16.8: Keyboard Shortcuts

Key Action
Backspace Reset/Fit to view
H+click surface Hide a surface
Ctrl+H Undo the last Hide operation
B Toggle between boundaries display modes:

All, no-SYMM, WALLs only, None

U Undo a view change (rotation/zoom/etc.)
Shift+U Redo a view change removed with U
P (hold down) Pick mode, click an item to select
Ctrl+T Show/Hide the toolbar
Space Show/Hide the right panel (full screen mode)
F5 Refresh - Reload solution from disk
1,2,3,4,5,6,7,8.9.0 Switch between pre-set views (+X, -X, +Y, -Y, etc.)
S Switch between shading modes
X,Y,Z,R,T Cutting plane mode, if available
I Iso-values mode, if available

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
450 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Key Action
Up/Down/Left/Right+Shift+Ctrl Tweak values for the current mode. (Selection of
the current datafield, cutting plane position,
number of iso-values contours, etc.)

Left/Right will iterate through numbered

datasets, if the step settings are visible in the
Data panel
Shift+~ Shows the Viewmerical command line window
(See Command Line Usage (p. 490)).

16.2.3. Data Management

The following sections of this chapter are:
[Link]. Open Files Dialog
[Link]. Adding/Removing Datasets
[Link]. Dataset Visibility
[Link]. Current Selection
[Link]. Multiple Selection
[Link]. Lock Selection

[Link]. Open Files Dialog

When Viewmerical is launched standalone, or when additional data is to be loaded, this file selection
dialog appears:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 451
Post-Processing

The loaded data can be either grid only or grid and solution.

Table 16.9: Grid File Formats Notes

Format Notes
FENSAP-ICE grid Grids of the FENSAP/DROP3D/ICE3D file
format. Also applies for [Link] and
[Link].
C3D solid grid Grids with material IDs, specific to C3D and
CHT3D/solid runs.

Boundaries Only
Loads only the grid boundaries, not the 3D cells. This will be faster and use less memory. In this
mode, it is not possible to display cutting planes or 3D iso surfaces.

Table 16.10: Solution File Notes

Solution File Description

FENSAP-ICE solution • The nodal solution output of
FENSAP/DROP3D/ICE3D/C3D. (soln,
droplet, swimsol, [Link], etc.).

– swimsol is bound to [Link] and

[Link], not the original 3D grid.

– [Link] grid must be loaded in

C3D grid format.

Heat flux [Link] file output of FENSAP contains

facet based data.
Shear stress [Link] file output of FENSAP
contains facet based data.
TimeBC [Link] or [Link] contains
node based boundary condition values.
ICE3D full solution ([Link] + swimsol) • Will load [Link], [Link] and
swimsol outputs of ICE3D.

– This mode enables ICE cover display

and CAD extraction.

– Specify [Link] as the grid file, and

the swimsol as the solution file. This
will load the [Link] with the same
suffix (if any) than the swimsol file.
swimsol.000100 requires the
availability of [Link].000100.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
452 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Solution File Description

C3D TimeBC [Link] file output of C3D contains
facet based data.

Note:

The solution must match the selected input grid.

[Link]. Adding/Removing Datasets

The Objects panel permits to manage the loaded datasets:

Opens the Open files dialog, to load an additional Grid/Solution.

Removes the currently selected object.

Selects all the datasets for modification. (See Lock Selection (p. 454)).

[Link]. Dataset Visibility

The check box at the left of an object in the object list permits to modify the global visibility of
that object.

Regions of a dataset (typically, boundary conditions), can be shown/hidden using the same check
box.

[Link]. Current Selection

Some operations are available or not depending on what the current selection is in the object list.

Object (grid) selected:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 453
Post-Processing

Surface (boundary condition) selected:

The current selected boundary condition (if any) is shown using a white contour and white wireframe:

[Link]. Multiple Selection

In addition to the current selection, multiple selection can be used to perform operations on multiple
items in the object list:

Holding down Shift enables adjacent selections from the current item to and including the item
clicked.

Holding down Ctrl enables items to be selected and deselected discretely.

The last item clicked becomes the current selection and, similar to the current selection, is highlighted
with a white contour and white wireframe only if it is a boundary condition.

In a single operation, selected items can be modified in the following ways:

• Toggling visibility by clicking the item check box.

• Changing the shading, color of the wireframe or grid and the opacity in the object dialog.

• Enabling and positioning a cutting plane for selected datasets and datasets of selected boundaries.

Modifications on multiple selections that include datasets may affect all boundary conditions of
the selected dataset.

[Link]. Lock Selection

The lock selection is used to select all datasets in addition the current item and/or multiple selection
items. Operations in a locked selection work similarly to a basic multiple section. This selection can
be enabled by clicking the Lock button in the Object Browser (See Adding/Removing Data-
sets (p. 453)). Locked selection permits similar operations to the shared mode and also enables all

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
454 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

data set to the be selected and modified in one operation particularly useful for synchronizing data-
field operations or expanding the scope of such operations to include all datasets. The Shared
button is in the LUT range dialog (See Shared Range (p. 472)).

This feature is particularly useful when the loaded grids have no associated solution and the LUT
range dialog is hidden.

16.2.4. Object Panel

The following sections of this chapter are:
[Link]. Shading Mode
[Link]. Object Color
[Link]. Repetition (Mirror/Periodicity)
[Link]. Split Screen

The panel is restricted to color settings should a single surface (boundary condition) be selected in
the object list panel:

[Link]. Shading Mode

The shading mode is selected at the top of the object panel:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 455
Post-Processing

Figure 16.3: Wireframe

Figure 16.4: Colored

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
456 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Figure 16.5: Colored+Wireframe

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 457
Post-Processing

Figure 16.6: Shaded

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
458 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Figure 16.7: Shaded+Wireframe

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 459
Post-Processing

Figure 16.8: Smooth Shaded

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
460 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Figure 16.9: Metallic

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 461
Post-Processing

Figure 16.10: Metallic+Smooth

[Link]. Object Color

Wire (wireframe lines) and Cell (facets) color can be changed. Click the colored box to access the
color picker.

Opacity permits to change the transparency of both wireframe and facets.

Object (grid) selected: The new wire/cell color is applied to all sub-objects.

Surface (boundary condition) selected: The color is applied only to the specified boundary condition.

Note:

These settings are useful only for grid types, not colored scalar solutions.

[Link]. Repetition (Mirror/Periodicity)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
462 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

The Repeat options permits to duplicate symmetric data.

Figure 16.11: No Repetition (Z-Symmetric Grid)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 463
Post-Processing

Figure 16.12: Z-Axis Repetition Enabled

[Link]. Split Screen

This permits to split the 3D window in two, showing datasets either top/bottom or left/right. The
camera position between the two halves is locked, the display are always exactly at the same pos-
ition.

The split-screen selection applies to the currently selected object, in the Objects list.

Different objects can have different split-screen settings:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
464 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Figure 16.13: Grid Adaptation, Before Adaptation/After Adaptation

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 465
Post-Processing

Figure 16.14: CHT Solution – Static Temperature. External Wall/Internal Wall

To load multiple datasets from FENSAP-ICE:

• If Viewmerical is already opened with a dataset.

• In FENSAP-ICE, load the second dataset using another View with VIEWMERICAL command. A
prompt will then ask you to Append or open a New window. Select Append:

• In Viewmerical, select one of the objects in the data list, and choose a Split screen option.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
466 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

16.2.5. Cutting Plane Panel

The following sections of this chapter are:

This panel is only available for 3D data. Grids loaded in Boundaries only mode, or 2D data (heat flux,
shear stress, timebc) do not offer the cutting plane option.

X/Y/Z-coordinate will select the cutting plane.

Grids providing cylindrical coordinates can also be cut in R or T (Theta).

The slider permits to interactively move the plane between the min and max values.

The minimum and maximum values can be edited, to select a custom range. Entering an empty value
(then hitting Enter) will revert to the default range value.

The icon provides additional display options:

Table 16.11: Display Options

Menu Description
Shaded + Wireframe, Shaded, Wireframe These settings are independent of the
individual object/surface settings.
Set color/Set wireframe color Changes the colors of the cutting plane
elements.
Auto-hide non-wall When the cutting plane mode is enabled, all
surfaces of the grid are hidden. (Enabled by
default). If Auto-hide boundaries are enabled,

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 467
Post-Processing

Menu Description
individual boundary conditions can be shown
afterwards using their visibility check box.

Use visible surf. for range By default, the cutting plane range is the full
3D domain of the object (minimum coordinate
to maximum coordinate). The range can be
restricted to the minimum/maximum of the
visible items. For example, if this option is
enabled and only the walls are currently
visible, the minimum/maximum of the cutting
plane zone will be the minimum/maximum
of the wall area.
Crinkle Instead of displaying the planar intersection
of each 3D cell with the cutting plane, the
whole cell is displayed. The display is then
much cleaner, and the internal 3D topology
of the grid easier to visualize.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
468 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Menu Description

Crinkle - Colored The crinkle is shaded by element type. Blue

= hexa, Green = Prism, Red = Pyramid, White
= Tetra.
Clipping Hide the + or - side of the mesh, in relation
to the cutting [Link] - only will hide
the cutting plane, while the clipping is
enabled.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 469
Post-Processing

Menu Description

Animation steps Displays the animation controls of the cutting

plane. Cycling through the domain is
controlled by the play/pause button. The step
accuracy of the movement and the direction
are configurable.

16.2.6. Scalar Solution Visualization

The following sections of this chapter are:
[Link]. Files Panel
[Link]. IsoValues Panel
[Link]. Vector Data Panel
[Link]. Displacement Panel

[Link]. Files Panel

Table 16.12: Files Panel

Menu Item Action

Grid The currently selected dataset. Refer to the
Objects panel to add/remove datasets.
Data If a solution file is loaded, this permits to
switch the currently loaded data-field
otherwise the data field combo-box is
disabled.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
470 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

The dataset and data-field are also visible in the combo-boxes at right side the status bar. These
combo-boxes can also be used to switch the dataset and data-field:

The button allows you to define an expression for custom fields using existing fields in the
dataset.

The icon offers the option to reload the data from the disk.

This will reload and display the current dataset, field and step (See below for Unsteady or Numbered
Solutions (p. 471)).

[Link].1. Unsteady or Numbered Solutions

If the loaded solution file is in the format of name.###### (six-digit numbered file) or
name.######## (eight-digit numbered file), the Step number, without preceding zeroes, is
shown in the panel as well as slider and an Play/Pause button. The slider permits to sweep
through the steps, loading/displaying the new solution for each step. The play/pause button
triggers a sweep animation for the steps in a continuous loop. If there were initially none included,
step animations for the selected datasets are added to the animation item list when an animation
is triggered.

Color Range Panel

The scalar field loaded is displayed using the settings of this panel. The minimum/maximum
values can be edited by modifying the numerical values, or by moving with the mouse the min-
imum/maximum boundary in the colored box.

Entering an empty value for the minimum/maximum (with the Enter key), will reset the value to
the minimum/maximum value of the dataset (as displayed below).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 471
Post-Processing

Invert

Inverts the direction of the spectrum.

Real-Time Update

Permits to display immediately any change made to the minimum/maximum of the color table.

[Link].2. Color Range

Modes other than Spectrum will use a textured color-mapping table and will permit to have
smoother display, but might not be compatible with all 3D display drivers.

Using a color range will give more gradient detail, visible mostly when a facet contains values
near the min and the max of the data range.

Spectrum (Linear Interpolation Shading)

Other colormaps, can show the full gradient of the data:

[Link].3. Shared Range

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
472 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

The check box Shared is useful only if multiple solutions of the same type are loaded. Using this
option will:

• Select the same datafield in all loaded solutions.

• Apply any datafield operations to the other loaded solutions.

• The global minimum/maximum of all datafields is used for the colormap minimum/maximum.

Example 16.1: Multiple Solutions

• Solution1 = 260 to 320 K.

• Solution2 = 274 to 406 K.

• Shared range = 260 to 406 K.

[Link].4. Global Range

If disabled, the Global setting will use the minimum/maximum only from the visible surfaces.

Default - Global range:

Local data range - With Global check box unchecked and a subset of the surfaces visible:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 473
Post-Processing

[Link].5. Advanced Options

Hide Values out of Range

When a facet has no node within the data range, it will not be drawn (completely invisible).

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
474 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Point Cloud for out of Range

If a node is not in the data range, it is marked with a white point. This option is useful to identify
mesh regions where the data is over/under a given threshold.

Important:

This option will show a point for each node of the grid, not only surface nodes, this
might be many of points to display, if the range is not carefully chosen.

Show Legend

Toggles the display of the legend panel, in the 3D view, for this dataset.

Top/Bottom

Selects the position of the legend panel in the 3D view.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 475
Post-Processing

[Link]. IsoValues Panel

Enabled - Surfaces
This option will display contour lines on the surfaces.

Enabled - Volumes
This option will display 3D Iso-Surfaces.

The position of the surface can be adjusted using the color range minimum/maximum values.

Advanced settings are available by clicking the icon:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
476 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

The options are the same than for the cutting plane (See Cutting Plane Panel (p. 467)).

[Link]. Vector Data Panel

This panel is available only if the loaded solution contains recognized X/Y/Z vector datafields.

Menu Item Action

Enabled - Surfaces Displays a vector for every visible surface
node.
Enabled - Volumes Displays a vector for a fraction of the volumic
nodes.
Volumetric data Controls the percentage of volumic nodes
to display.
Enabled - Both Display a vector for every visible surface
node, and for the specified fraction of
volumic nodes.

[Link].1. Vector Scaling

The default vector scale is 1. Meaning that a vector of magnitude 1 will be displayed as size 1 in
the scale of the grid. Usually, the vector scale must be changed to be suitable for display, enter
a scaling value or use +/- to change it:

Relative and Normalized Scaling

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 477
Post-Processing

The scaling mode will either display vector with length relative to their magnitude (Relative
scaling) or all of the same length (Normalized scaling):

Figure 16.15: Relative Scaling

Figure 16.16: Normalized Scaling

[Link].2. Coordinate Clamping

This menu entry permits to switch between XYZ, XY, YZ, XZ, X, Y, Z clamping modes. In these
modes, only the enumerated coordinate will be used for display.

[Link]. Displacement Panel

Some data files contains mesh displacement information (such as ALE timebc used for grid displace-
ment). This panel is visible if the Displacement magnitude option is selected. The scaling permits
you to deform the grid from the displacement vector. The default range is 0-10 with 0 being the
default value:

[Link].1. Real-Time Update

Enabling the Real-time update option allows the modifications to be applied immediately to
the dataset while moving the slider:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
478 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

[Link].2. Advanced Settings

Enabling the advanced setting expose controls to modify the minimum and maximum of the
range for the displacement factor multiplier:

16.2.7. View Options

The following sections of this chapter are:
[Link]. Window Panel
[Link]. Anaglyph 3D Display

[Link]. Window Panel

Table 16.13: Window Panel

Menu Item Result

Background Permits to change the background color.
Size Choose the behavior or resolution for the 3D
display viewport or the window size of
3DView. Window-Free allows the window
and viewport be resized freely and is the
default option. With a fixed viewport size the
window is resizable. With a fixed window
size the viewport is resized to fit. Custom
sizes can be set using the Width and Height
settings for either the viewport of the
window.
Toolbar/Axis Control the visibility of the elements on the
screen.
Legend Selects the mode of display of the dataset
legend.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 479
Post-Processing

Menu Item Result

Title Permits to select a title written at the top of
the display, useful for screenshots.

[Link]. Anaglyph 3D Display

This mode can be enabled in the Advanced panel (double-click the panel header).

It will render the data for use with red/cyan or red/blue filter 3D glasses:

The Angle and Depth settings can be fine-tuned using the sliders.

Grayscale or black & white data is well suited for this type of display.

16.2.8. Query Mode

The following sections of this chapter are:
[Link]. 2D Plot
[Link]. Selection Panel
[Link]. Computation/Integration

[Link]. 2D Plot
The currently loaded scalar data-field is used for 2D plots:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
480 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

The 2D plot data is computed onto the mesh intersections with a cutting plane.

Table 16.14: Target

Walls
Walls - Visible
Inlets
Inlets - Visible
Outlets
Outlets - Visible
All items
Visible items

The Target specifies the surfaces onto which the cutting plane will be applied.

To work only on a single wall, on a multi-wall dataset:

1. Hide all other boundary conditions from the display.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 481
Post-Processing

2. Select Visible items or the - Visible option of the appropriate target type.

Table 16.15: 2D Window Panel Modes

Modes Description
Data The data-field is evaluated for each
intersection point, this value is shown in the
Y-axis of the 2D Plot. In Geometry mode,
only the grid geometry is used, this is useful
to display a iced surface cutting plane
maintaining the aspect ratio for the
geometry to be plotted.
Cutting plane: X/Y/Z Specifies the plane and its position. The
plane position and alignment is displayed in
the 3D window. (The plane is infinite, the
displayed grid depends of the visible items
bounding box).

In the plot area:

• Left-click will select a point for value query.

• Shift drag left button will draw a zoom area, and zoom in.

– Dragging the mouse horizontally/vertically will do a horizontal/vertical zoom.

• Shift + left-click will zoom-out.

X/Y/Z/Distance: Selects the coordinate to use for the plot horizontal scale. Distance is the distance
from the previous point.

Print: Send the plot to the default printer.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
482 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

: Permits to accumulate multiple plots in the same display. For example ice cuts at different
cutting plane positions, or different icing time. All the plots must be sharing the same dataset mode
(For example, you cannot mix a temperature plot with a heat flux plot).

Up/Down: Permits the 2D plot panel to be resized vertically. Horizontal resize is done with the view
port and tab splitter grip which affects all the panels.

Figure 16.17: 2D Plot Menu

Save one file: Save all the date from plot to one plain text file.

Save multiple files: Save data from plot in one plain text file per curve.

Curve Settings: This opens a dialog to edit the width, color and style of visible curves.

[Link]. Selection Panel

Clicking the 3D data when in picking mode (Alt + click or P +click) will select the closest node
to the XYZ point clicked upon.

The currently selected node is shown as a white dot:

The node ID is shown in the Node field (node identifiers start at 1).

The node coordinate is in X/Y/Z fields.

The node scalar value, for the currently selected datafield is shown in Value.

If the scalar value is a velocity magnitude, the individual X/Y/Z components are also displayed.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 483
Post-Processing

Figure 16.18: Node Selection Tool

[Link]. Computation/Integration
To expand the panel, double-click the Compute header.

Figure 16.19: Compute Panel Window

[Link].1. Surface Integration

In the Target menu, select the boundary condition to work on and click the Compute button.

• Area: Area of the surface boundary condition.

• Integral: Integrated value of the current dataset, on the boundary condition.

• Average, Min, Max: Statistics of the current dataset, on the boundary condition.

[Link].2. Mass Flow Integration

In the Target menu, select the boundary condition to work on and click the Compute button.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
484 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

This mode is only valid for airflow, and will use the Density and Velocity components of the
solution.

• Area: Area of the surface boundary condition.

• Avg Normal X/Y/Z: Integrated average value of the surface normal.

• Integral: Integrated mass flow value.

[Link].3. Volume Integration

• Volume: Volume of the mesh.

• Integ. Scalar: Integrated value of the loaded scalar solution, through the whole volume.

16.2.9. ICE3D Solutions

The following sections of this chapter are:
[Link].The ICE3D Panel
[Link]. CAD Output

Viewmerical has a special mode optimized to display ICE3D output files. These output files are:

Table 16.16: ICE3D Output Files

Output Description
Files
[Link] Grid walls on icing surfaces.
[Link] Iced surface (displaced grid of [Link], with the ice thickness).
swim- Nodal solution, applicable to [Link]/[Link].
sol

The View ICE menu/button, from FENSAP-ICE permits to launch Viewmerical in this mode, loading
the 3 files automatically. From the Open files dialog, select the FENSAP-ICE grid = [Link] and
ICE3D full solution ([Link] + swimsol) = swimsol.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 485
Post-Processing

[Link]. The ICE3D Panel

Ice Cover
Displays the ice in white, over a metallic base mesh. The ice is only displayed where the threshold
is respected. For example if the ice thickness is more than the specified value. This is used to clip
the display of near-zero values. Multiple threshold variables are available.

The default threshold is Ice Growth which is accounting for all the growth since the start of the
computation(s). Ice thickness and Instant Ice Growth are based on data relative to the last ICE3D
simulation.

Table 16.17: Display Mode

Mode Displays
Ice cover - shaded As ice cover, but with some shading on the
ice shape.
Ice cover (only) Only displays the ice cover, the shading
options and color settings of the current
object apply to the ice cover.
Ice solution - Overlay swimsol scalar data is applied to the ice
shape grid (shown with the threshold).
Ice solution swimsol scalar data mapped on the
[Link] shape grid.
Surface solution swimsol scalar data mapped on the
[Link].
Glaze/Rime/Film Displays in colors the zones of
Glaze/Rime/Film.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
486 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Mode Displays

CAD output CAD Output (p. 487)

[Link]. CAD Output

The CAD Output mode permits to select an iced zone - using the same threshold used for the ice
cover display - and save the ice shape to a .stl or point cloud file.

Such files can then be used with CAD or 3D printing software to reconstruct the ICE shape.

From the ice cover:

The surface for the CAD would be:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 487
Post-Processing

Select the most appropriate threshold, to avoid CAD artifacts.

The surface can be saved to a CAD-friendly file using the options from the gray cube menu.

[Link].1. CAD Surface Cleanup

If the CAD surface contains islands (small surfaces disconnected to the main iced surface), such
as:

Or holes in the iced surface:

Use the Cleanup options to correct these artifacts.

[Link].2. Boundary Edge Smoothing

To remove sharp edges in the CAD boundary, such as:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
488 of ANSYS, Inc. and its subsidiaries and affiliates.
 Viewmerical

Use the Edge smoothing function:

Additional triangles will be added, to smooth the external edges of the CAD (not present in the
original grid, but reusing original node coordinates).

Angle:

More degrees will lead to more smoothing.

Iterations:

Number of times this process is repeated.

[Link].3. Output

Use the icon to access the output commands:

The CAD surface can be exported to a .stl file, readable by most CAD software, or to a point
list file.

STL output will write two files: [Link] and FILE_surf.stl, [Link] is the displaced
ice surface, FILE_surf.stl is the base wing surface:

Labels:

For .stl files, from this setting each triangle patch will be saved in a different zone named for
each boundary condition (or by Patch/Boundary Conditions+Patches).

Snap edges to [Link]:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 489
Post-Processing

In the case of a 3D ice shape (not a 2D periodic/symmetric grid) if the two files are joined together,
they can be assembled in a gap-free 3D shape suitable for 3D printing. For a perfectly gap-free
shape, Snap edges to [Link] is required, as it will use the coordinates of the wing surface for
each of the boundary edges of the iced surface.

16.2.10. Command Line Usage

The files to open with Viewmerical can be specified on the command line.

Typical usages:

• nti_3dview GRID3D gridfilename

Loads one grid.

• nti_3dview GRID3D grid1 EOL GRID3D grid2

Loads two grids, EOL is required to separate two commands.

• nti_3dview SOLN3D gridfilename solutionfile

Loads one grid & solution dataset.

• nti_3dview SOLN3D gridfilename solutionfile:TEMP

Loads one grid & solution dataset, and loads the TEMP datafield (4-letter field identifier of
FENSAP-style solution files).

• nti_3dview ICE3D

Loads [Link], swimsol and [Link] from the current directory.

Additional command syntax are listed in the -h all command-line help output, however any
command not listed in this user manual may not yet be fully supported.

16.3. CFD-Post Macros

The following sections of this chapter are:
16.3.1. Introduction to CFD-Post Macros
16.3.2. FENSAP-ICE Turbo
16.3.3. Ice Cover – 3D-View
16.3.4. Ice Cover – 2D-Plot
16.3.5. Ice Cover – Turbo 3D-View

16.3.1. Introduction to CFD-Post Macros

The purpose of these macros is to facilitate post-processing of FENSAP/DROP3D TURBO and ICE3D
results in CFD-Post. To enable these macros, first change the default post-processing tool of the
graphical user interface of FENSAP-ICE to CFD-Post. To do this, go to Settings → Preferences →

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
490 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Postprocessing and enable CFD-Post under Default postprocessing software and Write CFD-Post
launch files under General settings.

All FENSAP/DROP3D/ICE3D TURBO and ICE3D macros are located inside the Calculators panel of CFD-
Post. The following FENSAP/DROP3D/ICE3D TURBO and ICE3D macros are provided.

• FENSAP-ICE Turbo

• Ice Cover – 3D-View

• Ice Cover – 2D-Plot

• Ice Cover – Turbo 3D-View

16.3.2. FENSAP-ICE Turbo

The FENSAP-ICE Turbo macro allows users to automatically access post-processing features of the
Turbo workspace of CFD-Post, such as viewing solution fields and generating 2D plots using single
and multiple turbomachinery stages as shown in the figures below, in order to post-process airflow,
droplets, crystals and vapor solutions computed by FENSAP/DROP3D TURBO on a FENSAP-ICE grid.

Note:

For ICE3D TURBO solutions use the Ice Cover – Turbo-3D-View macro.

Figure 16.20: Post-Processed Particle Solution of DROP3D TURBO Inside CFD-Post Turbo

Without this macro, you will have to manually define the properties of each stage. Refer to Turbo
Initialization for more details regarding initialization of CFD-Post Turbo.

[Link]. Requirements
FENSAP-ICE Turbo macro has the following requirements:

• Before loading an airflow or particle solution into CFD-Post,

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 491
Post-Processing

– Make sure that your FENSAP grid does not contain a repeated BC Index (ID). If this is the case,
assign a different boundary condition number to all repeated boundary conditions and reload
this grid in FENSAP-ICE. Refer to Grid Operations (p. 413) in order to properly modify a boundary
condition index of a FENSAP grid.

– Each boundary surface of each stage must be properly defined inside FENSAP-ICE. Use the
following boundary types: Hub, Shroud, Blade, Inlet, Outlet, Periodic1, Periodic2, and Other
to define these surfaces. Consult Turbo Part (p. 253) to define these boundary surfaces using
FENSAP-ICE.

– If a boundary type is missing or not properly defined inside a domain, the FENSAP-ICE Turbo
macro will not be executed and manual initialization of the Turbo components must be done
inside CFD-Post. To initialize Turbo components in CFD-Post, consult Turbo Initialization and
Region Information.

• The macro only supports rows that are defined using the principle axes of rotation (X, Y and Z).

[Link]. Usage
To enable this macro, first launch CFD-Post with the turbomachinery airflow or particle solution by
clicking on the View with CFD-Post button inside your FENSAP or DROP3D TURBO run.

• From FENSAP TURBO:

The graphical user interface prompts amessage that asks you to bring the solution of a single
stage or all stages (airsol-all rows) into CFD-Post. Select all stages in order to fully benefit from
the FENSAP-ICE Turbo macro capabilities. Once inside CFD-Post, a Domain Selector window will
appear asking you to select which stage(s) you would like to analyze. You can hold Ctrl to select
more than one stage.

• From DROP3D TURBO:

The graphical user interface prompts twomessages. The first asks you to determine a particle
type (droplet, crystal, or vapor) that you would like to post-process. The second allows you to
bring the solution of a single stage or all stages (droplet/crystal/vapor-all rows) into CFD-Post.
Select all stages in order to fully benefit from the FENSAP-ICE Turbo macro capabilities. Once

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
492 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

inside CFD-Post, a Domain Selector will appear asking you to select which stage(s) you would
like to analyze. You can Ctrl to select more than one stage.

Note:

If you select a single stage from the graphical user interface, you will have to manually
define the properties of the stage.

Once the airflow/particle solutions of the selected rows have been correctly loaded into CFD-Post,
go to the Macro Calculator of CFD-Post. Select FENSAP-ICE Turbo from the Macro dropdown list
and execute it. The FENSAP-ICE Turbo macro will then properly define the turbo components in-
cluding their names, properties and axis of rotation and will auto-configure the Turbo workspace
of CFD-Post. This will give you access to the built-in turbo variables of CFD-Post.

Note:

The native mass-flow functions (such as massFlow, massFlowAve, massFlowAveAbs,

and massFlowInt) of CFD-Post are only supported when post-processing FENSAP TURBO
solutions. They are not supported with DROP3D TURBO solutions.

Refer to Turbo Workspace for more details regarding the Turbo workspace of CFD-Post as well as
the type of post-processing it enables.

For more details on how to properly use this macro, consult CFD-Post Setup for FENSAP-ICE turbo
solution within the FENSAP-ICE Tutorial Guide.

16.3.3. Ice Cover – 3D-View

The Ice Cover – 3D-View macro post-processes ICE3D output files and displays them within CFD-
Post’s 3D Viewer allowing you to view computed ice shapes/solutions, save figures, and generate
animations.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 493
Post-Processing

[Link]. Usage
To enable this macro, first launch CFD-Post with the ice solution dataset by clicking on the View
Ice button inside your ICE3D run. The following ICE3D domains will appear inside CFD-Post.

• map grid: The surface grid at each shot.

• map swimsol: The surface grid and its corresponding ICE3D swimsol solution at each shot.

• ice swimsol: The ice grid and its ICE3D swimsol solution at each shot.

Then, select Ice Cover – 3D-View from the Macro Calculator located in the Calculators tab of
CFD-Post.

[Link]. Features
1. Easy visualization of 2D/3D single-shot and multi-shot ICE3D results.

2. Automatic and user defined boundary selection modes.

3. Ice cover display modes used in Viewmerical.

4. Ice threshold variables that define the extent of ice shape.

5. Surface transparencies.

6. Display of ICE3D datafields over iced surfaces or original wall surfaces.

7. Contour plots & legend of the selected datafields.

8. Display the surface mesh of the ice shape or the original walls.

9. Create and save figures by specifying its type, format, size and quality.

10. Create and save multi-shot animations by specifying its format, size and quality.

[Link]. Input Parameters

The following lists the input parameters shown in the user interface panel of the Ice Cover – 3D-
View macro:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
494 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.21: Ice Cover – 3D-View UI in CFD-Post

1. Multi-shot # Selects the shot number to visualize. Leave

this as 1 for single shots.
2. View Mode Select All BCs or User Defined BCs to view
all or a certain group of BCs (surfaces).
(Defined BCs) Ice When User Defined BCs is selected, a set of
Ice with its respective Map BCs can be
(Defined BCs) Map specified. Define those sets by selecting the
appropriate BCs under (Defined BCs) Ice and
(Defined BCs) Map. A pre-defined Surface
Group of boundary conditions is also
supported. For more details on Surface Group
Commands, refer to Surface Group Command
in the CFD-Post User's Guide.
3. Display Mode Displays the following Viewmerical view
modes: Ice Cover, Ice Cover – shaded,
Ice Cover – No Orig, Ice Cover (only),
Ice Cover (only) – shaded, Ice Solution
– Overlay, Ice Solution, and Surface
Solution. The figures below show these
views on a 3rd shot ice shape.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 495
Post-Processing

Figure 16.22: Ice Cover

Figure 16.23: Ice Cover - Shaded

Figure 16.24: Ice Cover - No Orig

Figure 16.25: Ice Cover (only)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
496 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.26: Ice Cover (only) –

shaded

Figure 16.27: Ice Solution –

Overlay

Figure 16.28: Ice Solution

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 497
Post-Processing

Figure 16.29: Surface Solution

Isoclip Variable Threshold variables (Isoclip Variable) and

values (Isoclip Value) are used to limit
Isoclip Value the extent of the ice shape surface. The
next figures show some examples.

Figure 16.30: Isoclip Variable (Ice

Growth), Isoclip Value (0.01 kg/m2)

Figure 16.31: Isoclip Variable (Ice

Growth), Isoclip Value (2 kg/m2)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
498 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.32: Isoclip Variable (Ice

Growth), Isoclip Value (15 kg/m2)

Transparency Transparency controls the level of

transparency of the ice shape surface or
original surface. The range of available
value is from 0 (no transparency) to 1 (full
transparency).

Figure 16.33: Transparency: 0

Figure 16.34: Transparency: 0.5

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 499
Post-Processing

Figure 16.35: Transparency: 1

4. Display Variable Displays the ice solution datafield over the

iced surfaces or map surfaces specified in
Display Mode. Only the following Display
Modes are supported: Ice Solution – Overlay,
Ice Solution, or Surface Solution.

Figure 16.36: Display Variable

(Instant. Ice Growth)

Figure 16.37: Display Variable (Ice

Thickness)

Lines of Contour: Displays contour lines over ice/map

On or Off surfaces (On) or not (Off) of the Display
Variable selected.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
500 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.38: Lines of Contour

(Off)

Figure 16.39: Lines of Contour

(On)

Number of Contour Specifies the number of contour lines if

Lines of Contour has been activated.

Figure 16.40: Number of Contour:

8

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 501
Post-Processing

Figure 16.41: Number of Contour:

32

Range Defines the legend range of the Display

Variable. New max./min. values are required
-(Usr. Specif.) Max. when selecting User Specified. Otherwise,
Global considers the max./min. of the field.
-(Usr. Specif.) Min.
5. Display Mesh Displays the ice and map surface meshes.

Figure 16.42: Display Mesh (Off)

Figure 16.43: Display Mesh (On)

6. Save Figure Saves the image. Its properties are defined

within its secondary options. If No is selected,
all secondary options are ignored.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
502 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

By Defines how to save the image using the

current window. The options available are
Screen Shot or Size.
-(Size) Width When saving the image in Size mode, Width
and Height in pixels are required; Screen
-(Size) Height Shot does not require these options.
Format Defines the image format: PNG, JPEG, BMP.
Filename Assigns image name. If CFD-Post was opened
through ICE3D, the image will be saved inside
the ICE3D run folder. If not, the figure will be
saved in Windows’ default system folder. In
both cases, a message will open advising you
of the save location.
7. (Multishot) Movie Creates a multishot animation by taking into
account all the user interface settings of points
1 through 5 of the above list. The script will
generate an animation from the assigned shot
number specified in 1. Multi-shot # to the
last shot loaded in CFD-Post.
Frame Rate Varies the Frame Rate (between shots) to
adjust movie speed.
Save Saves the movie into a file. All secondary
options will be ignored if No is selected. It is
therefore possible to create an animation
without saving it into a file.
-Size Animations can be saved in different sizes and
quality. The Size choices are: Large (720x576)
-Quality pixel, Medium (640x480) pixel, Low
(320x240) pixel and Use Screen Size. The
Use Screen Size corresponds to the current
window size of the 3D Viewer in CFD-Post.
Quality options are Highest, Medium, and
Low.
-Format Animations can be saved in the following
most common formats, WMV or MPEG4.
-Filename Specifies animation name. If CFD-Post was
opened through ICE3D, the movie will be
saved in the ICE3D run folder. If not, the
animation will be saved in Windows’ default
system folder. In both cases, a message will
appear advising you of the location.

16.3.4. Ice Cover – 2D-Plot

This Ice Cover – 2D-Plot macro creates 2D plots using CFD-Post’s ChartViewer. You can easily gen-
erate curves of the computed ice shapes and solutions, export data points of all plotted curves and
save 2D plots into figures.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 503
Post-Processing

[Link]. Usage
To enable this macro, first launch CFD-Post with the ice solution dataset by clicking on the View
Ice button inside your ICE3D run. The following ICE3D domains will appear inside CFD-Post.

• map grid: The surface grid at each shot.

• map swimsol: The surface grid and its corresponding ICE3D swimsol solution at each shot.

• ice swimsol: The ice grid and its ICE3D swimsol solution at each shot.

Then, select Ice Cover – 2D-Plot from the Macro Calculator located in the Calculators tab of CFD-
Post.

[Link]. Features
1. Easy generation of 2D-Plots around 3D single-shot and multi-shot ICE3D results.

2. Automatic and user defined boundary selection modes.

3. Visualization of multiple shot results in the same 2D-Plot to ease comparison.

4. Generation of ice shape 2D-Plots.

5. Generation of scalar 2D-Plots using iced, Solution (on Ice Surfaces), and pre-iced surfaces,
Solution (on Map Surfaces).

6. Definition of 2D-Plots using cutting planes. Four modes are supported: (X, Y, Z) Plane (3 modes),
and Point and Normal.

7. Location of the 2D-Plot cutting plane over the 3D geometry in 3D Viewer.

8. Customization of 2D-Plot Title and X/Y-Axis range.

9. Exporting 2D-Plot data points into a file.

10. Saving 2D-Plots as figures.

[Link]. Input Parameters

The following lists the input parameters shown in the user interface panel of the Ice Cover – 2D-
Plot macro.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
504 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.44: Ice Cover – 3D-View UI in CFD-Post

1. Multi-shot # Selects the shot number to visualize. Leave

this as 1 for single shots.
2. View Mode Select All BCs or User Defined BCs to view
all or a certain group of BCs (surfaces).
(Defined BCs) Ice When User Defined BCs is selected, a set of
Ice with its respective Map BCs can be
(Defined BCs) Map specified. Define those sets by selecting the
appropriate BCs under (Defined BCs) Ice and
(Defined BCs) Map. A pre-defined Surface
Group of boundary conditions is also
supported. For more details on Surface Group
Commands, refer to Surface Group Command
in the CFD-Post User's Guide.
3. Plot’s Title Allows you to change plot title. The default
title is ICE SHAPE PLOT.
4. 2D-Plot (with) Plot geometry/solution curves in Single
Shot (using the assigned shot number in
1. Multi-shot #), Multi-Shots (from the

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 505
Post-Processing

assigned shot number in 1. Multi-shot

# to the last shot loaded in CFD-Post), or
Selected Shots (a series of assigned shot
numbers defined by you.)

Figure 16.45: 2D-Plot with Single

Shot (Shot No.3)

Figure 16.46: 2D-Plot with

Multishots (Shot No.4 -> 8)

Figure 16.47: 2D-Plot with

Selected Shots (Shot No. 2, 5, 6,
and 8)

(Selected) Shots Defines a series of assigned shot numbers

used when Selected Shots mode is selected
in 2D-Plot (with). Its input format must be in
the form of 1, 2, 3, 7, 9, …, 25.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
506 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Mode Plot curves of Geometry (ice shapes),

Solution (on Ice Surfaces), or Solution
(on Map Surfaces).

Figure 16.48: Mode: Geometry

Figure 16.49: Mode: Solution (on

Ice Surfaces)

Figure 16.50: Mode: Solution (on

Map Surfaces)

Cutting Plane By All curves are generated using cutting planes.

The cutting plane can be created using one
of the four following modes: Z Plane (at a
point), Y Plane (at a point), X Plane (at a
point) and Point and Normal. An intersecting
curve between the cutting plane and ice/map
surfaces will automatically be displayed in
CFD-Post’s 3D Viewer in all modes.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 507
Post-Processing

-X/Y/Z Plane Point A point used to locate an X Plane or Y

Plane or Z Plane.

Figure 16.51: Cutting X Plane at

Point 0.5, (0.5, 0, 0)

Figure 16.52: Cutting Y Plane at

Point 0, (0, 0, 0)

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
508 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.53: Cutting Z Plane at

Point 0.5, (0, 0, 0.5)

-(Pt. & Nml.)Pnt.X A point that defines the location of an

arbitrary linear plane. This option is associated
-(Pt. & Nml.)Pnt.Y with the Point and Normal mode.

-(Pt. & Nml.)Pnt.Z

-(Pt. & Nml.)Nml.X A normal vector that defines the
orientation of an arbitrary linear plane.
-(Pt. & Nml.)Nml.Y This option is associated with the Point
and Normal mode. This vector can be a
-(Pt. & Nml.)Nml.Z unitary vector or of arbitrary size.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 509
Post-Processing

Figure 16.54: Cutting Plane: Point

(0.291, 0.017, 0.512) and Normal
(0.5, 0, 0.866)

X-Axis Selects a variable to be assigned as the X-

Axis of the 2D-Plot. Only X/Y/Z geometrical
variables are supported.
-(x)Range Defines the range of the X-Axis of the 2D-Plot.
If Global, this range is automatically defined
by using the real geometrical max./min. values
of the selected variable (X/Y/Z). You can
specify different max. and min. values if the
range is set to User Specified.
([Link].x) Max If (x)Range is User Specified, the plotted
range of the X-Axis will consider the specified
-([Link].x) Min max/min values, ([Link].x) Max and
([Link].x) Min.
Y-Axis Selects a variable for the Y-Axis of the 2D-Plot.
X/Y/Z geometrical variables as well as all
ICE3D variables are supported.
-(y)Range Defines the range of the Y-Axis of the 2D-Plot.
If Global, this range is automatically defined
by using the real max./min. values of the
selected variable. You can specify different
max. and min. values if the range is set to
User Specified.
-([Link].y) Max If the (y)Range is User Specified, the plotted
range of the Y-Axis will take the specified
([Link].y) Min max/min values, ([Link].y) Max and
([Link].y) Min.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
510 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

5. Export (to csv) Export all plotted curves to a CSV format file.
The default value for export is No.
Filename (csv) Specifies the CSV file name. If CFD-Post was
opened through ICE3D, the file will be saved
inside the ICE3D run folder. If not, the file will
be saved in Windows’ default system folder.
In both cases, a message will open advising
you of the save location.
6. Save Figure Saves the plot as a figure with its secondary
options. All secondary options will be ignored
if No is selected.
Width When saving an image, Width and Height in
pixels are required.
Height
Format Specifies image format: PNG or BMP.
Filename Specifies image name. If CFD-Post was opened
through ICE3D, the figure will be saved inside
the ICE3D run folder. If not, the figure will be
saved in Windows’ default system folder. In
both cases, a message will open advising you
of the save location.

16.3.5. Ice Cover – Turbo 3D-View

The Ice Cover – Turbo 3D-View macro post-processes ICE3D-TURBO output files and displays them
within CFD-Post’s 3D Viewer allowing you to view computed ice shapes/solutions of turbo applications
and save figures. It has similar features to the ICE Cover – 3D-View macro described in the previous
section but extends them to cover turbo icing applications.

Note:

The Ice Cover – Turbo 3D-View macro currently supports single shot multiple-stage turbo
icing solutions. To post-process multishot solutions in CFD-Post, please use the Ice Cover
– 3D-View macro.

[Link]. Usage
To enable this macro, first launch CFD-Post with the turbo ice solution dataset by clicking on the
View Ice button inside your ICE3D-TURBO run. All rows will be loaded into CFD-Post and the fol-
lowing ICE3D domains will appear inside CFD-Post.

• map [Link]: The surface grid of each row.

• [Link]:The surface grid and its corresponding ICE3D swimsol solution of each row.

• ice [Link]: The ice grid and its ICE3D swimsol solution of each row.

The index of each domain follows the row numbering defined in ICE3D-TURBO. For example, the
following three domains with index 03 correspond to the Turbo row 03.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 511
Post-Processing

Then, select Ice Cover – Turbo 3D-View from the Macro Calculator located in the Calculators
tab of CFD-Post.

[Link]. Features
1. Easy visualization of 3D single-shot ICE3D-TURBO results.

2. Display results of all rows, single rows, or multiple selected rows.

3. Display single copy or full circle copies of rows selected for post-processing.

4. Different view mode of displaying all turbo BCs or combination of turbo type BCs

5. Ice cover display modes used in Viewmerical.

6. Ice threshold variables that define the extent of ice shape.

7. Surface transparencies.

8. Display of ICE3D datafields over iced surfaces or original wall surfaces.

9. Contour plots & legend of the selected datafields.

10. Display the surface mesh of the ice shape or the original walls.

11. Create and save figures by specifying its type, format, size and quality.

[Link]. Input Parameters

The following lists the input parameters shown in the user interface panel of the Ice Cover – Turbo
3D-View macro:

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
512 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.55: Ice Cover – Turbo 3D-View User Interface in CFD-Post

Settings from 1.b. Turbo Rows to 2. View Mode are inputs for the turbo rows. Details are explained
in the table below. Settings from 3. Display Mode to 6. Save Figure are inputs to display and save
the ice solutions, which are identical to the features of the Ice Cover – Turbo 3D-View macro.
Please see Input Parameters (p. 494) for more information regarding these settings.

1. a. Multi-shot # Selects the shot number to

visualize. Leave this as 1. If you
put a value number different
than 1, a warning message will
appear since the Ice Cover –
Turbo 3D-View macro only
supports single shot solutions.
1. b. Turbo Rows Select All Rows or Selected
Rows to view all rows or a
certain group of rows of your
turbo solution.
(Selected) Rows Defines a series of assigned row
numbers used when Selected
Rows mode is selected in Turbo
Rows. It can be single or
multiple rows. Selected rows
can be entered in random order
and row numbers must be
separated by a comma. The
following shows an example of
the input format: 6, 2, 1,
3, 7, 10, …,5.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 513
Post-Processing

1. c. Turbo Graphic Select to display Single Copy

or Full Circle copies of turbo
rows.
2. View Mode Select All BCs - On to view all
BCs (surfaces) of the turbo rows.
Select All BCs - Off and then
specify the turbo types
Shrouds, Blades, and Hubs to
display.
Shrouds When All BCs – Off is
selected, these three turbo
Blades types will be considered as
a combination of BCs
Hubs (surfaces) to display. Select
On next to the turbo types
to display. For example, if
you select the following
combination of turbo
types:

• Shrouds set to Off;

• Blades set to On;

• Hubs set to On;

CFD-Post will display the

blades and the hubs of the
turbo rows selected.

[Link]. Extended Usage

In some turbo applications, ice accumulates across multiple succeeding turbo stages. In this case,
the inspection and analysis of the icing solution might be difficult to conduct, especially when all
turbo rows are displayed in full cycle mode and some rows hide the view of subsequent rows. For
instance, in the following figure, the fan and bypass block the view of the IGV.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
514 of ANSYS, Inc. and its subsidiaries and affiliates.
 CFD-Post Macros

Figure 16.56: View of Multiple Stages in Full Cycle Mode

In the above case, some copies of the fan blade must be hidden to properly visualize the icing
results over the IGV, rotor, and stator inside the compressor. To hide some copies,

• First, select the rows to display and then set Turbo Graphic to Full Circle as shown below.

• Execute the macro to display all selected rows in Full Cycle mode. The macro automatically
computes the number of copies for each row and creates an Instance Transform object for each
row. The index of the Instance Transform object follows the turbo row numbering.

• Go to the Outline tab. Under the tree User Locations and Plots, double-click onto the row’s
Instance Transform object to edit it.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 515
Post-Processing

• When the panel of Instance Transform is open, the number of copies is defined in Number of
Graphical Instances. Un-check Full Circle and then set a new number next to Number of
Graphical Instances. This number should be less than the default value. Click Apply.

• Repeat this modification for each row. The following figure shows that with a reduced number
of copies of the fan and bypass, it is possible to better visualize ice accretion over the IGV, stator,
etc.

Figure 16.57: Improved View of Multiple Stages in Full Cycle Mode

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
516 of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 17: References
The following sections of this chapter are:
17.1. Journal Publications in Mesh Adaptation
17.2. Conference Publications in Mesh Adaptation
17.3. Von Karman Lecture Series in Mesh Adaptation
17.4. Chapters in Books in In-Flight Icing
17.5. Refereed Journal Publications in In-Flight Icing
17.6. Conference Publications in In-Flight Icing
17.7. Referenced within this manual

17.1. Journal Publications in Mesh Adaptation

L. Remaki and W.G. Habashi, 3D Mesh Adaptation on Multiple Discontinuities and Boundary Layers, In Press
SIAM Journal, MS#042987-1, June 2003.

D. Ait-Ali-Yahia, G. Baruzzi, W.G. Habashi, M. Fortin, J Dompierre and M-G. Vallet, Anisotropic Mesh Ad-
aptation: Towards User-Independent, Mesh-Independent and Solver-Independent CFD Solutions: Part
II: Structured Grids, International Journal for Numerical Methods in Fluids, Vol. 39, pp. 657-674, June
2002.

J. Dompierre, M-G. Vallet, Y. Bourgault, M. Fortin and W.G. Habashi, Anisotropic Mesh Adaptation: Towards
User-Independent, Mesh-Independent and Solver-Independent CFD Solutions: Part III: Unstructured
Meshes, International Journal for Numerical Methods in Fluids, Vol. 39, pp. 675-702, June 2002.

W.G. Habashi, J. Dompierre, Y. Bourgault, D. Ait-Ali-Yahia, M. Fortin and M-G. Vallet, Anisotropic Mesh
Adaptation: Towards User-Independent, Mesh-Independent and Solver-Independent CFD Solutions: Part
I: General Principles, International Journal for Numerical Methods in Fluids, Vol. 32, No. 6, pp. 725-744,
March 2000.

A. Tam, D. Ait-Ali-Yahia, M.P. Robichaud, M. Moore, V. Kozel and W.G. Habashi, Three-dimensional Mesh
Optimization: Tight Coupling of Mesh Generation and Solver, with CAD Integrity, Computer Methods in
Applied Mechanics and Engineering, Vol. 189, No. 4, pp. 1205-1230, September 2000.

M. Sleiman, A. Tam, M.P. Robichaud, M.F. Peeters and W.G. Habashi, Turbomachinery Multistage Simulation
by a Finite Element Adaptive Approach, ASME Journal of Fluids Engineering, Vol. 121, No. 2, pp. 450-459,
June 1999.

W.G. Habashi, J. Dompierre, Y. Bourgault, M. Fortin and M.-G. Vallet, Certifiable Computational Fluid Dy-
namics Through Mesh Optimization, Invited Paper in Special Issue on Credible Computational Fluid Dy-
namics Simulation, AIAA Journal, Vol. 36, No. 5, pp. 703-711, 1998.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 517
References

D. Ait-Ali-Yahia and W.G. Habashi, A Finite Element Adaptive Method for Hypersonic Thermo-Chemical Non-
equilibrium Flows, AIAA Journal, Vol. 35, No. 8, pp. 1294-1302, 1997.

D. Ait-Ali-Yahia, M.-G. Vallet, A. Tam, W.G. Habashi and M. Fortin, A Directionally-Adaptive Methodology
Using an Edge-Based Error Estimate on Quadrilateral Grids, International Journal for Numerical Methods
in Fluids, Vol. 23, pp. 673-690, 1996.

17.2. Conference Publications in Mesh Adaptation

L. Remaki, S. Nadarajah, W.G. Habashi, M.C. Bogstad, C. Kho and F. Mokhtarian, Mesh Adaptation Impact
on Lift and Drag Coefficients, CASI 11th Aerodynamics Symposium, Toronto, April 2005.

L. Remakiand W.G. Habashi,Towardan Optimal Initial Grid for CFD, 43rd AIAA Aerospace Sciences Meeting,
Reno, January 2005.

W.G. Habashi, Keynote Address, Mesh Adaptation, from Qualitative to Quantitative CFD, Pacing CFD,
Stanford University, November 2004.

F. Suerich-Gulick, C.Y. Lepage and W.G. Habashi,Automatic Mesh Adaptation: Towards User-Independent
CFD, Keynote Lecture, The 4th International Conference on Engineering Computational Technology,
Lisbon, Portugal, September 2004.

F. Suerich-Gulick, C.Y. Lepage and W.G. Habashi, Anisotropic 3-D Mesh Adaptation for Turbulent Flows,
AIAA Paper 2004-2533, 34th AIAA Fluid Dynamics Conference, Portland, July 2004.

C.Y. Lepage, A. St-Cyr and W.G. Habashi, Parallel Unstructured Mesh Adaptation on Distributed Memory
Systems, AIAA Paper 2004-2532, 34th AIAA Fluid Dynamics Conference, Portland, July 2004.

Lepage, C.L., Remaki, L. and Habashi, W.G., Advances in CFD Mesh Optimization, Invited paper, Proceedings
Grand Review of the State-of-the-Art in the Numerical Simulation of Fluid Flow, I Mech E, London, U.K.,
December 2002, to appear in IMechE Journal, 2003.

W.G. Habashi, C.Y. Lepage, G.S. Baruzzi and I. Akel, OptiMesh: Anisotropic Mesh Adaptation with CAD In-
tegrity for Verifiably Accurate CFD Solutions Over Complete Aircraft, NATO Applied Vehicle Technology
Panel Symposium, Paris, April 2002.

L. Remaki, H. Beaugendre and W.G. Habashi, An Anisotropic Isovalue-oriented Artificial Viscosity Method
for CFD, Proceedings CFD Society of Canada Meeting, June 2002, Windsor, ON, pp. 222-227.

C.Y. Lepage, L. Remaki and W.G. Habashi, Anisotropic 3-D Mesh Adaptation on Unstructured Hybrid Meshes,
AIAA Paper 2002-7318, 40th AIAA Aerospace Sciences Meeting, Reno, January 2002.

G.S. Baruzzi, C. Lepage, I. Akel and W.G. Habashi, MOM3D: CAD-based Mesh Adaptation for CFD Solutions
over Complete Aircraft, 8th Aerodynamics Symposium, CASI, Toronto, April 2001

Tam, D. Ait-Ali-Yahia, M.P. Robichaud, M. Peeters, V. Kozel and W.G. Habashi: Three-dimensional Aniso-
tropic Adaptation for Viscous External and Turbomachinery Flows, AIAA Paper 2000-2248, AIAA Fluids
2000, Denver, June 2000

W.G. Habashi, V. Kozel, A. Tam, D. Ait-Ali-Yahia, M.P. Robichaud and M. Moore, Anisotropic Mesh Adapt-
ation for 3-D Flows on Unstructured Grids, Proceedings ICEM CFD Users’ Conference’99, Berkeley, USA,
May 1999.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
518 of ANSYS, Inc. and its subsidiaries and affiliates.
 Conference Publications in Mesh Adaptation

V. Kozel, W.G. Habashi, A. Tam, M.P. Robichaud, M. Bogstad, A. Wulf and M. Hohmeyer, Mesh Optimization:
Tight Coupling of Mesh Generation and Solver, with CAD Integrity, Proceedings of the Fourth European
Computational Fluid Dynamics Conference (ECCOMAS), Athens, September 1998, pp. 114-118, Volume
1, part 1.

Tam, M.P. Robichaud, P. Tremblay, W.G. Habashi, M. Hohmeyer, G. Guèvremont, M.F. Peeters and D. Ait-
Ali-Yahia, A 3-D Adaptive Finite Element Method for Aerodynamic Flows, Proceedings CFD98, Quebec City,
June 1998, pp. II-63-II-68.

W.G. Habashi and A. Wulf, 3D Mesh Adaptation, with CAD Integrity, Invited Paper, Proceedings of the
World User Association in Applied CFD Conference, Freiburg, Germany, June 1998, pp. 22.1-22.6.

Tam, M.P. Robichaud, P. Tremblay, W.G. Habashi, M. Hohmeyer, G. Guèvremont, M.F. Peeters and P.
Germain, A 3D Adaptive Anisotropic Method for External and Internal Flows, AIAA Paper 98-0771, 36th
AIAA Aerospace Sciences Meeting, Reno, January 1998.

F. Taghaddosi, W.G. Habashi, G. Guèvremont and D. Ait-Ali-Yahia, An Adaptive Least-Squares Method for
the Compressible Euler Equations, AIAA Paper 97-2097, 13th AIAA Computational Fluid Dynamics Confer-
ence, Snowmass, June 1997.

W.G. Habashi, Anisotropic Mesh Optimization: Toward Mesh-User, and Solver-Independent CFD, Invited
Lecture, Proceedings of the CFD’97 Conference of the Canadian Society for CFD, Victoria, British Columbia,
May 1997, pp. 5.3-5.6.

J. Dompierre, M.-G. Vallet, M. Fortin and W.G. Habashi, Anisotropic Mesh Adaptation: Towards a Solver
and User Independent CFD, AIAA Paper 97-0861, 35th AIAA Aerospace Sciences Meeting, Reno, January
1997.

W.G. Habashi, M. Fortin, J. Dompierre, M-G. Vallet and Y. Bourgault, A Mesh Optimizer for CFD, 6th ASME
International Congress on Fluid Dynamics & Propulsion, Cairo, December 1996, pp. 1-8.

M. Fortin, M.-G. Vallet, J. Dompierre, Y. Bourgault and W.G. Habashi, Anisotropic Mesh Adaptation: Theory,
Validation and Applications, Proceedings of the Third European Computational Fluid Dynamics Conference
(ECCOMAS), Paris, John Wiley, September 1996, pp. 174-180.

W.G. Habashi and M. Fortin, Anisotropic Mesh Adaptation: A Step towards a Grid-independent and User-
independent CFD, Invited Keynote Address at ICASE-NASA Langley Research Center Workshop on Barriers
and Challenges in CFD, Hampton, VA, August 1996, Kluger Academic, pp. 99-117.

D. Ait-Ali-Yahia and W.G. Habashi, A Directionally-Adaptive Finite Element Method for High-Speed Flows,
AIAA Paper 96-2553, 32nd AIAA/ASME/SAE/ASEE Joint Propulsion Conference, Lake Buena Vista, July
1996.

Tam, W.G. Habashi, D. Ait-Ali-Yahia, M.P. Robichaud and M. Fortin, A 3-D Adaptive Finite Element Method
for Turbomachinery, AIAA Paper 96-2659, 32nd AIAA/ASME/SAE/ASEE Joint Propulsion Conference, Lake
Buena Vista, July 1996.

M-G. Vallet, Y. Bourgault, J. Dompierre, M. Fortin and W.G. Habashi, A Directional Error Estimator for CFD,
Proceedings of the ASME Fluids Engineering Division Summer Meeting, FED-Vol. 238, Volume 3, pp.
209-215, San Diego, July 1996.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 519
References

M. Sleiman, A. Tam, M.P. Robichaud, M.F. Peeters, W.G. Habashi and M. Fortin, Turbomachinery Multistage
Simulation by a Finite Element Adaptive Approach, ASME Paper 96-GT-418, 41st ASME Gas Turbine and
Aeroengine Congress, Birmingham, U.K., June 1996.

D. Ait-Ali-Yahia and W.G. Habashi, A Directionally-Adaptive Finite Element Method for Hypersonic Thermo-
Chemical Non-equilibrium Flows, 15th International Conference on Numerical Methods in Fluid Dynamics,
Monterey, Springer-Verlag, June 1996, pp. 261-267.

W.G. Habashi and M. Fortin, Anisotropic Mesh Adaptation: Towards a Mesh-independent, User-Independent
and Solver-Independent CFD, Invited Workshop Address, World User Association in Applied CFD Conference,
Freiburg, Germany, May 1996, pp. 13.1-13.4.

17.3. Von Karman Lecture Series in Mesh Adaptation

Computational Fluid Dynamics

The Von Karman Institute for Fluid Dynamics, Belgium

Montreal, August 1996, Co-Director of the course with H. Deconinck (VKI)

Brussels, March 1997

17.4. Chapters in Books in In-Flight Icing

Inno’va-tion: Essays by Leading Canadian Researchers

J. Downey and L. Claxton (Eds.), Key Porter Books, Toronto, 2002.

Chapter Title: Putting Supercomputers on Ice, Chapter 5, pp. 78-85.

Computational Analysis of Convection Heat Transfer

G. Comini and B. Sundén (Eds.), Wessex Institute of Technology Press, 2000.

Chapter Title: Thermal Analysis of Wing Anti-Icing Devices, Chapter 10, pp. 409-432.

17.5. Refereed Journal Publications in In-Flight Icing

P. Tran, G. Baruzzi, I. Akel, W.G. Habashi and J.C. Narramore, FENSAP-ICE Applications to Complete Rotorcraft
Configurations, Journal of Aerospace, SAE Transactions, September 2004.

H. Beaugendre, F. Morency and W.G. Habashi, Roughness Implementation: Model Calibration and Influence
on Ice Shapes, AIAA Journal of Aircraft, Vol. 40, No. 6, November/December 2003.

H. Beaugendre, F. Morency and W.G. Habashi, ICE3D, FENSAP-ICE’s 3D In-Flight Ice Accretion Module, AIAA
Journal of Aircraft, Vol. 40, No 3, May-June 2003.

G. Croce, H. Beaugendre and W.G. Habashi, Numerical Analysis of Heat Transfer in Mist Flow, using FENSAP-
ICE, Journal of Numerical Heat Transfer, Part A, Vol. 42 No. 1, pp. 1-14, 2002.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
520 of ANSYS, Inc. and its subsidiaries and affiliates.
 Conference Publications in In-Flight Icing

Y. Bourgault, H. Beaugendre and W.G. Habashi, Development of a Shallow Water Icing Model in FENSAP-
ICE, AIAA Journal of Aircraft, Vol. 37, pp. 640-646, 2000.

Y. Bourgault, Z. Boutanios and W.G. Habashi, 3D Eulerian Droplets Impingement Using FENSAP-ICE, Part I:
Model, Algorithms and Validation, AIAA Journal of Aircraft, Vol. 37, pp. 95-103, 2000.

Y. Bourgault, W.G. Habashi, J. Dompierre and G.S. Baruzzi, A Finite Element Method Study of Eulerian
Droplets Impingement Models, International Journal for Numerical Methods in Fluids, Vol. 29, No. 4, pp.
429-449, May 1999.

W.G. Habashi, Putting Computers on Ice, ICAO Journal, Vol. 50, No. 7, pp. 14-17, October 1995.

17.6. Conference Publications in In-Flight Icing

C.N. Aliaga, W.G. Habashi, M.S. Aubé, G.S. Baruzzi, A Third-generation In-flight Icing Code: FENSAP-ICE-
Unsteady, SAE Aircraft & Engine Icing International Conference, Seville, Spain, September 2007.

M.S. Aubé, G.S. Baruzzi, W.G. Habashi and C.N. Aliaga, Application of FENSAP-ICE-Unsteady to Helicopter
Icing, SAE Aircraft & Engine Icing International Conference, Seville, Spain, September 2007.

G.S. Baruzzi, P. Lagacé, W.G. Habashi and M.S. Aubé, FENSAP-ICE: A Computational Approach to Shed-Ice
Trajectory Simulation, SAE Aircraft & Engine Icing International Conference, Seville, Spain, September
2007.

K. Togami, M. Tsujita, M.S. Aubé and W.G. Habashi, Validation Results of FENSAP-ICE, SAE Aircraft & Engine
Icing International Conference, Seville, Spain, September 2007.

H. Wang, P. Tran, W.G. Habashi, Y. Chen, M. Zhang and L. Feng, Anti-Icing Simulation in Wet Air of a Piccolo
System using FENSAP-ICE, SAE Aircraft & Engine Icing International Conference, Seville, Spain, September
2007.

F. Morency, H.Z. Wang, W.G. Habashi, S. Nadarajah, A. Pueyo and F. Kafyeke, Thermal Validation of FENSAP-
ICE Anti-Icing Procedure, CASI 11th Aerodynamics Symposium, Toronto, April 2005.

L. Remaki, S. Nadarajah, W.G. Habashi, M.C. Bogstad, C. Kho and F. Mokhtarian, Mesh Adaptation Impact
on Lift and Drag Coefficients, CASI 11th Aerodynamics Symposium, Toronto, April 2005.

W.G. Habashi, Keynote Address, In-flight Icing, Pacing CFD, Pacing CFD, Stanford University, November
2004.

W.G. Habashi, M. Aubé, G. Baruzzi, F. Morency, P. Tran, J.C. Narramore, P. Petersen and M. Liggett, FENSAP-
ICE: Full-3D In-Flight Icing Simulation System for Aircraft, Rotorcraft and UAVs, ICAS, Yokohama, Japan,
August 2004.

W.G. Habashi et al, Keynote Speech, Rôle de la CFD dans la simulation du givrage en vol, Keynote Address,
CFT’04: Colloque Franco-Tunisien sur les Méthodes Numériques Appliquées aux Écoulements et aux
Transferts, pp. 15-22, 23-24 April 2004, Monastir, Tunisia.

P. Tran, G. Baruzzi, F. Tremblay, W.G. Habashi P. Petersen, M. Liggett, J. Vos, FENSAP-ICE Applications to
Unmanned Aerial Vehicles (UAV), AIAA Paper 2004-0402, 42ndAIAA Aerospace Sciences Meeting, Reno,
January 2004.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 521
References

W.G. Habashi, H. Beaugendre, F. Morency, Development of a Second Generation In-Flight Icing Simulation
Code, FEDSM2003-45816, Keynote Lecture, Proceedings of FEDSM’03 4TH ASME-JSME Joint Fluids Engin-
eering Conference, Honolulu, Hawaii, USA, July 6–11, 2003.

W.G. Habashi, H. Beaugendre, F. Morency, Development of a Second Generation In-Flight Icing Simulation
Code, FEDSM2003-45816, Keynote Lecture, Proceedings of FEDSM’03 4TH ASME-JSME Joint Fluids Engin-
eering Conference, Honolulu, Hawaii, USA, July 6–11, 2003.

P. Tran, G. Baruzzi, I. Akel, W.G. Habashi and J.C. Narramore, FENSAP-ICE Applications to Complete Rotorcraft
Configurations, Paper 03FAAID-49, FAA In-flight Icing / Ground De-icing International Conference & Ex-
hibition, Washington, June 2003.

H. Beaugendre, F. Morency and W.G. Habashi, FENSAP-ICE: A Second Generation 3D CFD In-flight Icing
Simulation System, Paper 03FAAID-50, FAA In-flight Icing / Ground De-icing International Conference &
Exhibition, Washington, June 2003.

J.C. Narramore P. Tran, G. Baruzzi, W.G. Habashi, I. Akel, and S. Balage, ICE Accretion Computations for
Full Tiltrotor Configurations, American Helicopter Society 59th Annual Forum, Phoenix, Arizona May 6 –
8, 2003.

G. Croce, W.G. Habashi and H. Beaugendre, Conjugate Heat Transfer Computations of Flows with Droplet
Impingement, TED-J03-125, 6thASME-JSME Thermal Engineering Joint Conference, Hawaii, March 2003.

F. Morency, H. Beaugendre and W.G. Habashi, FENSAP-ICE: Effect of Pressure Gradient on 3D Eulerian
Droplet Impingement, AIAA Paper 2003- 1222, 41st AIAA Aerospace Sciences Meeting, Reno, January
2003.

H. Beaugendre, F. Morency and W.G. Habashi, FENSAP-ICE: Roughness Effects on Ice Accretion Prediction,
AIAA Paper 2003- 1223, 41st AIAA Aerospace Sciences Meeting, Reno, January 2003.

G. Baruzzi, P. Tran, W.G. Habashi and J.C. Narramore, Actuator Disk Implementation in FENSAP-ICE, a 3D
Navier-Stokes In-Flight Simulation System, AIAA Paper 2003- 0619, 41st AIAA Aerospace Sciences Meeting,
Reno, January 2003.

J.C. Narramore, G. Baruzzi, P. Tran and W.G. Habashi, FENSAP-ICE: Progress Towards a Rotorcraft Full-3D
In-Flight Icing Simulation System, 41st AIAA Aerospace Sciences Meeting, Reno, January 2003.

P. Tran, S. Balage, G. Croce, F. Lafond and W.G. Habashi, FENSAP-ICE: A Multi-disciplinary, Multi-component,
Integrated Design Tool, and its Application to Ice Protection Systems, ASME International Design Engineering
Conference, Montreal, September 2002.

W.G. Habashi, P. Tran, G.S. Baruzzi, M. Aubé and P. Benquet, Design of Ice Protection Systems and Icing
Certification through the FENSAP-ICE System, NATO Applied Vehicle Technology Panel Symposium, Paris,
April 2002.

F. Morency, H. Beaugendre and W.G. Habashi, Effect of Pressure Gradient on Droplet Impingement and Ice
Shape Calculations, Proceedings CFD Society of Canada Meeting, June 2002, Windsor, ON, pp. 299-304.

P. Tran, S. Balage, G. Baruzzi, I. Akel, W.G. Habashi and J. Narramore, Reducing Icing Certification Flight
Tests through Second Generation 3-D CFD-based Technologies, Abstract (58-06), 58th AHS International
FORUM, June 11-13, 2002, Montreal, Canada.

G.S. Baruzzi, P. Tran and W.G. Habashi and J. C. Narramore, A New Actuator Disk FEM Model For Propellers,
58th AHS International FORUM, June 11-13, 2002, Montreal, Canada.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
522 of ANSYS, Inc. and its subsidiaries and affiliates.
 Conference Publications in In-Flight Icing

H. Beaugendre, F. Morency and W.G. Habashi, ICE3D, FENSAP-ICE’s 3D In-Flight Ice Accretion Module, AIAA
Paper 2002-7134, 40th AIAA Aerospace Sciences Meeting, Reno, January 2002.

G. Croce, H. Beaugendre and W.G. Habashi, CHT3D, FENSAP-ICE Conjugate Heat Transfer Computations
with Droplet Impingement and Runback Effects, AIAA Paper 2002-7212, 40th AIAA Aerospace Sciences
Meeting, Reno, January 2002.

P. Tran, P. Benquet, G.S. Baruzzi and W.G. Habashi, Design of Ice Protection Systems and Icing Certification
Through Cost-effective Use of CFD, AIAA Paper 2002-0382, 40th AIAA Aerospace Sciences Meeting, Reno,
January 2002.

F. Morency, H. Beaugendre, G.S. Baruzzi and W.G. Habashi, FENSAP-ICE: A Comprehensive 3D Simulation
Tool for In-flight Icing, AIAA Paper 2001-2566, 15th AIAA Computational Fluid Dynamics Conference,
Anaheim, CA, June 2001.

G. Croce, H. Beaugendre and W.G. Habashi, FENSAP-ICE: Numerical Simulation of Heat Transfer in Mist
Flows, ICHMT Computational Heat Transfer 2001, Palm Cove, Australia, May 2001, pp. 1283-1290.

F. Morency, H. Beaugendre and W. Habashi, FENSAP-ICE: A Navier-Stokes Eulerian Droplet Impingement

Approach for High-lift Devices, 8th Aerodynamics Symposium, CASI, Toronto, April 2001.

H. Beaugendre, F. Morency and W. Habashi, ICE3D, FENSAP-ICE's 3D In-flight Ice Accretion Module, 8th
Aerodynamics Symposium, CASI, Toronto, April 2001.

Y. Bourgault, W.G. Habashi and E. Beaugendre, Development of a Shallow-Water Icing Model in FENSAP-
ICE, AIAA Paper 99-0246, 37th AIAA Aerospace Sciences Meeting, Reno, January 1999.

W.G. Habashi, Y. Bourgault, G.S. Baruzzi, Z. Boutanios, G. Croce and G.A. Wagner, FENSAP-ICE: An Integrated
CFD Approach to the In-Flight Icing Problem, Invited paper at Special Technological Session on Icing and
De-Icing, Proceedings Fourth European Computational Fluid Dynamics Conference (ECCOMAS), Athens,
September 1998, pp. 512-517, Volume 2.

Y. Bourgault, E. Beaugendre, W.G. Habashi, C.Y. Lepage and G. Croce, FENSAP-ICE: A New Equilibrium
Model for Ice Accretion, including Film Runback and Conjugate Heat Transfer, Proceedings of the Fourth
European Computational Fluid Dynamics Conference (ECCOMAS), Athens, September 1998, pp. 723-728,
Volume 1, part 2.

W.G. Habashi, Putting Computer on Ice: A CFD Integrated Approach to the In-Flight Icing Problem, Keynote
Lecture, 13th Canadian Symposium on Fluid Dynamics (CSFD-98) 19th Annual Meeting of the Canadian
Applied and Industrial Mathematics Society (CAIMS-98), Simon Fraser University, Vancouver, May 1998,
pp. 58-59.

Z. Boutanios, Y. Bourgault, W.G. Habashi, G.A. Isaac and S.G. Cober, 3D Droplets Impingement Analysis
Around an Aircraft's Nose and Cockpit Using FENSAP-ICE, AIAA Paper 98-0200, 36th AIAA Aerospace Sciences
Meeting, Reno, January 1998.

G. Croce, W.G. Habashi, G. Guèvremont and F. Tezok, 3D Thermal Analysis of an Anti-Icing Device Using
FENSAP-ICE, AIAA Paper 98-0193, 36th AIAA Aerospace Sciences Meeting, Reno, January 1998.

W.G. Habashi, Y. Bourgault, J. Dompierre, G. Baruzzi and D. Cronin, A Modern CFD Look at In-Flight Icing
Phenomena, Proceedings of the 16th Canadian Congress of Applied Mechanics, Quebec City, June 1997,
pp. 309-310.

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 523
References

W.G. Habashi and Y. Bourgault, Une approche moderne pour la simulation numérique des problèmes du
givrage en vol, Canada-France Aerospace Workshop, Concordia University, Montreal, May 1997.

J. Dompierre, D. Cronin, Y. Bourgault, G. Baruzzi and W.G. Habashi, Numerical Simulation of Performance
Degradation due to Small-scale Roughness, 6th Canadian Aeronautics and Space Institute Aerodynamics
Symposium, Toronto, April 1997.

W.G. Habashi, Y. Bourgault, J. Dompierre, G. Baruzzi and D. Cronin, Putting Computers on Ice: A CFD In-
tegrated Approach to the In-Flight Icing Problem, 6th Canadian Aeronautics and Space Institute Aerody-
namics Symposium, Toronto, April 1997.

Y. Bourgault, W.G. Habashi, J. Dompierre, G.S. Baruzzi and G. Chevalier, An Eulerian Approach to Supercooled
Droplets Impingement Calculation, AIAA Paper 97-0176, 35th AIAA Aerospace Sciences Meeting, Reno,
January 1997.

Y. Bourgault, W.G. Habashi, J. Dompierre, G. Baruzzi, G. Chevalier and W. DiBartolomeo, An Eulerian

Computational Approach to Ice Droplets Impingement, Proceedings of the Third European Computational
Fluid Dynamics Conference (ECCOMAS), Paris, John Wiley, September 1996, pp. 827-833.

Y. Bourgault, W.G. Habashi, J. Dompierre and G. Chevalier, An Eulerian Approach to Ice Droplets Impinge-
ment, 15th International Conference on Numerical Methods in Fluid Dynamics, Monterey, Springer-
Verlag, June 1996, pp. 274-279.

W. Di Bartolomeo, P.L. Kotiuga and W.G. Habashi, Certification Test Design Using CFD, Proceedings of the
American Helicopter Society International Icing Symposium '95, pp. 43-51, Montreal, September 1995.

17.7. Referenced within this manual

Wilcox, D. C., "Formulation of the k-ω Turbulence Model Revisited," AIAA Journal, Vol. 46, No. 11, 2008,
pp. 2823-2838.

Menter, F. R., Kuntz, M., and Langtry, R., "Ten Years of Industrial Experience with the SST Turbulence
Model," Turbulence, Heat and Mass Transfer 4, ed: K. Hanjalic, Y. Nagano, and M. Tummers, Begell House,
Inc., 2003, pp. 625-632.

SST roughness: Aupoix, B., "Roughness Corrections for the k-ω Shear Stress Transport Model: Status and
Proposals, " Journal of Fluids Engineering, Vol. 137, No. 2, 021202.

K-omega roughness: Knopp, T., Eisfeld, B., and Calvo, J.B., "A New Extension for k-ω Turbulence Models
to Account for Wall Roughness, " International Journal of Heat and Fluid Flow, Vol. 30, No. 1, 2009, pp.
54-65.

Shin and T.H. Bond, ‘Experimental and Computational Ice Shapes and Resulting Drag Increase for a
NACA 0012 Airfoil’, NASA Technical Memorandum 105743, 1992.

E. Brundrett, Prediction of Pressure Drop for incompressible Flow Through Screens, J. Fluid Eng., June
1993.

Idelchik, I.E., Handbook of Hydraulic Resistance, Second Edition, p. 402.

Clift, R., Grace, J.R., and Weber, M. E., Bubbles, Drops, and Particles, Academic Press, New York, 1978

G. K. Batchelor, An introduction to fluid dynamics, Cambridge University Press, Cambridge, 1967, p. 233

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
524 of ANSYS, Inc. and its subsidiaries and affiliates.
 Referenced within this manual

Clift, R., Grace, J.R., and Weber, M. E., Bubbles, Drops, and Particles, Academic Press, New York, 1978, p.
112

R. L. Pitter, H. R. Pruppacher and A. E. Hamielec, A Numerical Study of Viscous Flow Past a Thin Oblate
Spheroid at Low and Intermediate Reynolds Numbers, Journal of the Atmospheric Sciences, Vol. 30,
January 1973, pp. 125-134

Jayaweera, K. O. L. F. and Cottis, R. E., Fall velocities of plate-like and columnar ice crystals, The Quarterly
Journal of the Royal Meteorological Society, Vol. 95, No. 406, 1969, p. 703-709.

List, R. and Schemenauer, R. S., Free Fall Behaviour of Planar Snow Crystals, Conical Graupel and Small
Hail, Journal of Atmospheric Sciences, Vol. 28, 1971, p. 110-115.

Pitter, R. L., Pruppacher, H. R. and Hamielec, A. E., A Numerical Study of Viscous Flow Past a Thin Oblate
Spheroid at Low and Intermediate Reynolds Numbers, Journal of Atmospheric Sciences, Vol. 30, 1973, p.
125-134

Happel, J. and Brenner, H., Low-Reynolds Number Hydrodynamics, Prentice Hall, 1965, p. 553.

Pilch M. & Erdman C.A., Use of Break-up Time Data and Velocity History Data to Predict the Maximum
Size of Stable Fragments for Acceleration-induced Break-up of a Liquid Drop, Int. J. Multiphase Flow,
Vol. 13, No. 6, 1987.

Potapczuk, M., Wright, W. (2006), SLD simulation capabilities with LEWICE, CFD Methods for SLD Simulation
Workshop, Scottsdale, AZ.

Schmel, R. (2002). Advanced Modeling of Droplet Deformation and Break-up for CFD Analysis of Mixture
Preparation, ILASS-Europe 2002, Zaragoza, 9-11 September 2002.

Hsiang, L.-P., Faeth, G.M. (1995), Drop Deformation and Break-up due to Shock Wave and Steady Disturb-
ances, Int. J. Multiphase Flow, Vol. 21, No. 4, 545-560.

Trujillo, M. F., Mathews, W. S., Lee, C. F., Peters, J. E. (2000), Modeling and experiment of impingement and
atomization of a liquid spray on a wall, International journal of engine research, 1(1), 87-105.

Mundo, C., Tropea, C. & Sommerfeld, M. (1997), Numerical and experimental investigation of spray char-
acteristics in the vicinity of a rigid wall, Experimental thermal and fluid science, 15, 228-237.

Khan, A. R. & Richardson, J. F. (1987), The resistance to motion of a solid sphere in a fluid, Chemical engin-
eering communication, 62, 135-150.

Department of Transportation, Federal Aviation Administration NPRM: “Airplane and Engine Icing Certi-
fication Requirementsin Supercooled Large Drop, Mixed Phase, and Ice Crystal Icing Conditions,” June
29, 2010, US Government Federal Register, Vol. 75, No. 124, pages 37311-37339.

Department of Transportation, Federal Aviation Administration NPRM: “Airplane and Engine Icing Certi-
fication Requirementsin Supercooled Large Drop, Mixed Phase, and Ice Crystal Icing Conditions,” June
29, 2010, US Government Federal Register, Vol. 75, No. 124, pages 37311-37339.

Currie, T., et al. (2014). Experimental Studies of Mixed Phase Sticking Efficiency for Ice Accretion in Jet
Engines. Atmospheric and Space Environments Conference. Atlanta, GA, AIAA. 2014-3049.

J.G. Mason, J.W. Strapp, P. Chow, The Ice Particle Threat to Engines in Flight, AIAA 2006-206, AIAA Reno,
2006

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
of ANSYS, Inc. and its subsidiaries and affiliates. 525
References

X. Veillard, Implementation of a Quasi-Steady Mixing plane method in FENSAP-ICE, Master of Sciences

Thesis, Imperial College London, September 2008

Federal Aviation Administration (2014). Advisory Circular AC 25-28, “Compliance of Transport Category
Airplanes with Certification Requirements for Flight in Icing Conditions”

Supercooled large drop icing conditions. 14 CFR 25.1420. 2017

Mundo, C., Sommerfeld, M. and Tropea, C. 1995 Droplet-wall collisions: experimental studies of the de-
formation and breakup process. Int. J. Multiphase Flow, Vol. 21, No. 2, pp. 151-173

Honsek R, ‘Development of a three dimensional eulerian model of droplet-wall interaction mechanisms’,

McGill University Thesis, 2005

Trujillo, Lee, ‘Modeling and Experiment of Impingement and atomization of a liquid spray on a wall’,
Journal of Engine Research, Vol .01 Issue 1 p87-105, 2000

Wright W.B., ‘Refinement of the LEWICE SLD model’, AIAA 2006-464, 2006

William B. Wright. . Semi-Empirical Modeling of SLD Physics 2004; (AIAA–2004–0412): .

Release 2021 R1 - © ANSYS, Inc. All rights reserved. - Contains proprietary and confidential information
526 of ANSYS, Inc. and its subsidiaries and affiliates.