_userManual_AUTOGRID5_87

N U M E R I C A L M E C H A N I C S A P P L I C A T I O N S

User ManualAutoGrid5™ v8

Automated Grid Generator for Turbomachinery

- March 2010 -

N U M E R I C A L M E C H A N I C S A P P L I C A T I O N S

User ManualAutoGrid5™ v8

Documentation v8d

NUMECA International

5, Avenue Franklin Roosevelt

1050 Brussels

Belgium

Tel: +32 2 647.83.11

Fax: +32 2 647.93.98

Web: http://www.numeca.com

Contents

AutoGrid5™ iii

CHAPTER 1: Getting Started 1-1

1-1 Overview 1-1

1-2 Introduction 1-1What is AutoGrid5™ 1-1Features 1-1Structured vs. Unstructured 1-2Approach 1-2Project Management 1-3

Mesh files 1-3Template files 1-3

1-3 How To Use This Manual 1-4Outline 1-4Conventions 1-4

1-4 First Time Use 1-5Basic Installation 1-5Expert Graphics Options 1-5

Graphics Driver 1-5Background & Foreground Colors 1-6

1-5 How to Start AutoGrid5™ Interface 1-6

1-6 Required Licenses 1-7Standard AutoGrid5™ License 1-7Additional Licenses 1-7

CHAPTER 2: Graphical User Interface 2-1

2-1 Overview 2-1

2-2 Project Selection 2-2Create New Template/Project 2-2Open Existing Template/Project 2-3

2-3 Main Menu Bar 2-4File Menu 2-4

Open Project 2-4New Project 2-4Save Project / Save Project As 2-5Save Template / Save Template As 2-5Save Grid -> Save Grid As 2-6Save Grid -> Save Grid As Fine 7.4 2-6Save Grid -> Save Grid As Fine 8.6 2-6Save Grid -> Merge Project Grid 2-6Save Grid -> Save Fluid Domain(s) 2-6Project List -> Transfer File List 2-6Project List -> Open File List 2-6Scripts -> Edit 2-6Scripts -> Save All 2-7Scripts -> Execute 2-7Scripts -> Re-execute Last 2-7Print -> As PostScript 2-7

iv AutoGrid5™

Contents

Print -> As Bitmap PostScript 2-7Print -> As PNG 2-7Export -> IGES 2-8Export -> Geometry Selection 2-8Export -> Geometry Control Points 2-8Export -> Block Coor 2-8Export -> Face Coor 2-8Export -> Patch Coor 2-9Export -> Plot3D 2-9Import -> IGG Project 2-9

Prefix 2-10Importation operations 2-10

Import -> IGG Data 2-10Import -> External Grid 2-11Import -> Face Grid 2-11Import -> Topology 2-12Import -> CATIA V5 2-12Import -> Parasolid 2-12Import -> IGES 2-13Import -> PLOT3D 2-14Import -> CGNS 2-15Import -> GridPro 2-16Preferences 2-16

Saving Page 2-16Graphics Page 2-17Layout Page 2-18

Quit 2-18Geometry Menu 2-18View Menu 2-19

Patch Viewer 2-19Sweep Surfaces 2-20Coarse Grid 2-21Repetition 2-22Face Displacement 2-22View Depth 2-22Toggle 3D Solid View 2-23View/Hide 3D Solid Mesh 2-23View 3D Solid Block 2-24Toggle Throughflow Mesh 2-24Toggle Tool Bar / Symbolic View / Configuration/IGG Panel 2-24

Grid Menu 2-25Periodicity 2-25Boundary Conditions 2-26

Patch Browser 2-26Filters 2-27Patch Type Specification 2-27Patch Definition & Editing 2-28Automatic Connectivity Search 2-28Manual Connectivity Settings 2-30

Contents

AutoGrid5™ v

Full Non Matching Connections 2-31Rotor/Stator Connections 2-33

Grid Quality 2-34Quality Criterion Definitions (Block Page) 2-36Quality Criterion Definitions (Boundaries Page) 2-38Quality Criterion Definitions (FNMB Page) 2-39

Grid Quality Report 2-41Grid Quality Report (HTML) 2-41Negative Cells 2-43Compute All Fnmbs 2-44Create Face / Create Block 2-44

2-4 Toolbar 2-44User Mode 2-45Project Management Icons 2-45Mesh Generation Buttons 2-45View & Mesh Quality Management Icons 2-46Mesh Control Icons 2-46Contextual Icons 2-47

Row Management Icons 2-47Blade Management Icons 2-47Shroud & Hub Gap Management Icons 2-48

2-5 Quick Access Pad 2-48Rows Definition Subpad 2-50

Project Management Buttons 2-50Configuration Tree 2-50Contextual Popup Menu of Tree Items 2-51

Geometry Definition Subpad 2-52Mesh Control Subpad 2-53

Grid Level Page 2-53Row Mesh Control Page 2-54Active B2B Layer Page 2-54

View Subpad 2-55Geometry Groups Page 2-55Block Groups Page 2-57Grid Configuration Page 2-58

Main Project Management 2-59Duplicate Main Project 2-59Merge Main Project 2-60SubProject Management 2-60Rename SubProject 2-60Duplicate SubProject 2-61Save SubProject 2-61Load SubProject 2-61Merge SubProject 2-62Delete SubProject 2-62Domain Management 2-62Domain Properties 2-63Rename Domain 2-63

vi AutoGrid5™

Contents

Group Domain 2-63Delete Domain 2-64Domain Interface Management 2-64Domain Boundary Properties 2-65Rename Domain Boundary 2-65Group Domain Boundaries 2-65Ungroup Domain Boundaries 2-66Connect Domain Boundaries 2-66Interface Viewer 2-68Export Surfaces 2-68

Grid Page 2-68

2-6 Control Area 2-69Message Area 2-70Keyboard Input Area 2-70Mouse Coordinates 2-70Information Area 2-70Grid Parameters Area 2-70Generation Status Area 2-71Viewing Buttons 2-72

X, Y & Z Projection Buttons 2-72Coordinate Axis 2-72Scrolling 2-723D Viewing Button 2-73Rotate Around X, Y or Z axis 2-73Zoom In/Out 2-73Region Zoom 2-73Fit Button 2-74Original Button 2-74Cutting Plane 2-74

2-7 Graphics Area & Views 2-74Symbolic View 2-75Meridional View 2-75Blade to Blade View 2-763D View 2-76View & User Interaction 2-77

2-8 File Chooser 2-77

CHAPTER 3: Meshing Fundamentals 3-1

3-1 Overview 3-1

3-2 Mesh Domain Definition 3-2Hub & Shroud Definition 3-2Blade Definition 3-3Inlet & Outlet Limits 3-3Technological Effects 3-3

Meridional Technological Effects 3-33D Technological Effects 3-3

Cooling & Conjugate Heat Transfer 3-3

Contents

AutoGrid5™ vii

3-3 Geometry Definition 3-4The ".geomTurbo" File Format 3-4

Channel Format 3-4Basic Curves 3-5Channel Curves 3-6

Row(s) Definition Format. 3-6Row Type 3-7Row Periodicity 3-7Blade Definition 3-7

External CAD Format 3-9

3-4 Mesh Generation Steps 3-10Project Initialization 3-10Project Setup 3-11

Row Properties 3-12Periodicity 3-12Number of Geometry Periodicity 3-12Row Information 3-12Hub/Shroud/Shroud Gap Non-Axisymmetric 3-12Tandem Row 3-13Full Mesh Generation 3-13Low Memory Use 3-13Number of Repetition 3-13

Hub/Shroud Gap (Expert Mode) 3-13Cell Width 3-13Mesh Control 3-13

Flow Paths Control 3-14Blade to Blade Control 3-14

Conformal Mapping 3-15Blade to Blade Mesh Initialization 3-15

Default (O4H) Blade to Blade Topology 3-15Grid Points Clustering 3-17Initial Mesh 3-17

Blade to Blade Mesh Optimization 3-18Blade to Blade View Control 3-18

Display Update 3-18Active Layer 3-18

3D Mesh Generation 3-20Project Persistency 3-20

Create New Project 3-21Overwrite Existing Project 3-21Project Library 3-21Project Info 3-21Project Files 3-21

Mesh files 3-21Template files 3-22

Open Project File 3-22Select Project File 3-22Project File Library 3-23

viii AutoGrid5™

Contents

Project Information Area 3-23

3-5 Meshing Similar Geometry & Batch Mode 3-23

CHAPTER 4: Wizard Mode 4-1

4-1 Overview 4-1

4-2 Wizard Mode GUI 4-2Main Menu Bar 4-2Toolbar 4-3

User Mode 4-3Project Management Icons 4-3Mesh Generation Buttons 4-4View & Mesh Quality Management Icons 4-4View Management Icons 4-5Copy/Paste Row Topology Icons 4-5

Quick Access Pad 4-5Rows Definition Subpad 4-7Geometry Definition Subpad 4-7Mesh Control Subpad 4-7View Subpad 4-8

4-3 Row Wizard 4-8Geometry Check 4-9Machine Characteristics Definition 4-9Gap/Fillet Definition 4-10Flow Path Definition 4-10Blade-to-Blade Mesh Definition 4-11Initialization End 4-13MultiStage Management 4-13Automatic Blade-to-Blade Settings 4-14

Global Settings 4-14Upstream & Downstream H blocks Definition 4-14Blade-to-Blade Topology 4-15High Staggered Topology 4-15Blade-to-Blade Grid Points 4-15Throat Control 4-16Sharp & Rounded Treatment 4-16B2B Mesh Parameters 4-16Optimization Parameters 4-16

Machine Dedicated Settings 4-17Wind Turbine Settings 4-17Axial Turbine Settings 4-20Francis Turbine Settings 4-20Kaplan Turbine Settings 4-21Inducer Settings 4-21Axial Compressor Settings 4-22Centrifugal Impeller Settings 4-22Radial Diffuser Settings 4-22Return Channel Settings 4-23

Contents

AutoGrid5™ ix

Counter Rotative Fan Settings 4-23SHF Pump Settings 4-23Axial Fan Settings 4-24

CHAPTER 5: Geometry Definition 5-1

5-1 Overview 5-1

5-2 Import ".geomTurbo" File 5-1

5-3 Import CAD 5-2Menu Bar 5-3

File Menu 5-3Open... 5-3Open IGES 5-4Export... 5-5Close 5-6Exit 5-6

Geometry Menu 5-6Edit Menu 5-6

Geometry Axis... 5-6View Menu 5-6

View Solid 5-6Select Menu 5-7

Surfaces 5-7Curves 5-7Surface List ... 5-8Curve List ... 5-8Invert Selection 5-9Hide Selection 5-9

Viewing Buttons 5-9Quick Access Pad 5-9Graphics Area Interaction 5-10

Overview 5-10"Link to..." Description 5-10

Link to Hub 5-11Link to Shroud 5-11Link Non Axi to Hub 5-11Link Non Axi to Shroud 5-11Link Non Axi to Shroud Gap 5-11Link to Nozzle 5-11Link to Fin Up/Down 5-11Import Meridional 5-12Link to 3D Effect 5-12Link to Blade 5-12Link to Pressure/Suction Side 5-12Link to Leading Edge 5-12Link to Trailing Edge 5-12Link to Hub Gap 5-12Link to Shroud Gap 5-12

x AutoGrid5™

Contents

Link to Inlet 5-13Link to Outlet 5-13Link to Outlet Up 5-13

5-4 Hub/Shroud Edition 5-13Edit Hub/Shroud 5-13Non-Axisymmetric Hub/Shroud 5-14

From ".geomTurbo" File 5-15From Import CAD 5-16Mesh Generation Control 5-16

5-5 Blade Edition 5-18Blade Expansion 5-18

Force Blunt at Leading Edge 5-18Force Blunt at Trailing Edge 5-18Stick Leading/Trailing Edge 5-18Apply a Rotation 5-18Sewing Tolerance 5-19Expansion at Hub 5-19

Unchanged 5-19Expand 5-19Treat blend 5-20Treat blend with offset 5-20

Expansion at Shroud 5-20Unchanged 5-20Expand 5-20Treat blend 5-20Treat blend with offset 5-21

Blade Fillet 5-21Leading/Trailing Edge Wizard 5-23

Control Layers Definition 5-23Control Layer Limits 5-24Control Layer Clustering 5-24Global Layer Control 5-24Expert Layer Control 5-25

Leading/Trailing Edge Location Definition 5-25Active Layer 5-26Edge Location Control. 5-26Edge Expansion Control 5-27View B2B & Solid Body 5-27

Sheet on Blade 5-28Non-Axisymmetric Shroud Gap 5-30

From ".geomTurbo" File 5-31From Import CAD 5-31Mesh Generation Control 5-32

5-6 Cascade Configuration 5-33

5-7 Blade Geometry Check 5-34Check Geometry 5-34

Blade Definition Check 5-34Streamwise Orientation Check 5-35

Contents

AutoGrid5™ xi

Loop Detection - Distance Check 5-35 Loop Detection - Angle Check 5-35

Adapt Geometry 5-36Data Reduction 5-36 Blade Sections Interpolation Loops 5-36Blade Rotation 5-37

5-8 Blade Geometry Export 5-37

CHAPTER 6: Meridional Control 6-1

6-1 Overview 6-1

6-2 Geometry Control 6-1Basic Curves 6-1

Creation 6-1Discretization 6-2Deletion 6-2Check Geometry 6-2

Hub - Shroud - Nozzle 6-3Rotor/Stator 6-4

Properties 6-5Control Points Editing 6-6

Meridional Control Lines 6-6Creation 6-7Deletion 6-7Edition 6-7Properties 6-7Specific Cases: Bypass, Fin & Bulb 6-9

Channel Control 6-11Meridional Curve Checks 6-11

6-3 Mesh Control 6-12Flow Paths Control 6-13Flow Paths Manual Editing 6-14Hub/Shroud Gaps Control 6-16Blade Fillet 6-16Bulb Control 6-17Bypass Control 6-18Fin Control 6-20Copy - Merge Distributions 6-20

Conditions of Use 6-21Representation 6-21

Mesh Quality Checks 6-22

CHAPTER 7: Blade to Blade Control 7-1

7-1 Overview 7-1

7-2 Blade to Blade Topology Management 7-3Overview 7-3Topology Selection 7-3

xii AutoGrid5™

Contents

Copy/Paste Topology 7-6

7-3 Default Topology (O4H Topology) 7-7Default Topology Control 7-7

Control Number of Grid Points 7-7Control Periodic Boundary Condition Type 7-9Control Skin Mesh Clustering around the Blade 7-9

Grid Point Number Control 7-10Leading Edge & Trailing Edge Clustering Control 7-10Move Leading Edge & Trailing Edge Location 7-11Control Boundary Layer in the Skin Mesh. 7-12

Control Hub/Shroud Gap Mesh 7-13Blend/Sharp/Rounded Treatment at Leading/Trailing Edge 7-14Grid Points in Throat 7-15Wake Control 7-17Inlet & Outlet Boundary Control 7-18Relax Inlet & Outlet Clustering 7-18Blunt at Leading/Trailing Edge 7-20

Topology for High Staggered Blades 7-21Overview 7-21High Staggered Blade Topology Optimization 7-22Grid Points - Periodic Boundary - Gap Control 7-23

Tandem Row 7-24Main Blade/Splitter Configuration 7-25Multi-Rows Configuration 7-26

Control Lines & Blade to Blade Mesh. 7-27Upstream & Downstream Control Lines. 7-28Control Line on Blade 7-29Cell Width around Control Line 7-29Mesh Quality Improvement with Control Line 7-29

Intersection Control Options 7-30

7-4 HOH Topology 7-32Overview 7-32HOH Blade to Blade Mesh Control 7-32

Upstream & Downstream Extension Control 7-33Number of Points Control 7-34Blade Clustering Control 7-35

Butterfly Mesh Topology for Hub/Shroud Gap 7-36Hub to Shroud Mesh Control 7-37Intersection Control Options 7-37

7-5 H&I Topology 7-38Overview 7-38H&I Topology Control 7-39

Control Number of Grid Points 7-43Control Skin Mesh Clustering around the Blade 7-43Control Hub/Shroud Gap Mesh 7-44Blend/Sharp/Rounded Treatment at Leading/Trailing Edge 7-44Inlet & Outlet Boundary Control 7-44Control Clustering at Projection Points 7-44

Contents

AutoGrid5™ xiii

Topology for High Staggered Blades 7-45Intersection Control Options 7-46

7-6 User Defined Topology 7-47Geometry Control 7-48Mesh Control 7-49

Control Layer Page 7-51Create - Connect Pages 7-51

View Control 7-54

7-7 Blade to Blade Optimization 7-55Introduction 7-55Optimization Control 7-55

Optimization Steps 7-56Skewness Control 7-56Orthogonality Control 7-57

Wake Control Level 7-58Multigrid Acceleration 7-59Non-Matching Control 7-59Periodic Boundary Optimization 7-59Multisplitter Control 7-60Skin Mesh Control 7-60Advice to Users 7-60Theoretical Aspect 7-60

CHAPTER 8: 3D Generation 8-1

8-1 Overview 8-1

8-2 Application Field 8-2

8-3 3D Mesh - Interpolation 8-23D Blocks Naming 8-3

Row Mesh 8-3Default Topology - H&I Topology - HOH Topology 8-3User Defined Topology 8-4

Mesh in Bulb 8-4Mesh around Nozzle (Bypass) 8-4Mesh in Meridional Technological Effect 8-4Mesh in 3D Technological Effect 8-4

3D Boundary Condition Patches 8-4Generation 8-4Patch Naming 8-4

Block Order 8-5Generate Full Mesh 8-5Number of Mesh Points. 8-5

8-4 Mesh Quality 8-6

8-5 Template & Mesh Files 8-6Mesh Files 8-7Template Files 8-7

8-6 B2B Cut 8-7Edit B2B Cut 8-8

xiv AutoGrid5™

Contents

Delete B2B Cut 8-9Create B2B Cut 8-9

CHAPTER 9: Meridional Technological Effect 9-1

9-1 Overview 9-1

9-2 Configuration Management 9-2

9-3 Geometry Definition 9-2The ".geomTurbo" File 9-3CAD Import 9-3User Defined 9-3

9-4 Definition of Meridional Mesh 9-4Start Edition Mode 9-4Edition Mode 9-5

Geometry Control 9-5Topology Control 9-6

Create & Modify New Block 9-7Delete Existing Blocks 9-8Insert New Control Vertices 9-8Grid Points Clustering 9-8Grid Point Number Control 9-8

Automatic Default Topology 9-9Optimization Steps 9-10Radial Expansion 9-10Automatic Detection Tools 9-10

9-5 Connection with Main Blade Channel 9-12Connection Types 9-12Multiple Connections 9-13

9-6 3D Generation 9-14

CHAPTER 10:3D Technological Effect 10-1

10-1 Overview 10-1

10-2 Configuration Management 10-1

10-3 Geometry Definition 10-2External Data File 10-2CAD Import 10-2

10-4 Edition Mode 10-3

10-5 Topology Management 10-43D effect library 10-4Copy/Paste Feature 10-5

10-6 3D Generation & Persistency 10-6

CHAPTER 11:Cooling & Conjugate Heat Transfer Modules 11-1

11-1 Overview 11-1

11-2 Conjugate Heat Transfer 11-1

Contents

AutoGrid5™ xv

Mesh of Blade Solid Body 11-1Solid Body Configuration 11-3

Solid Body Configuration (Default) 11-3Solid Body + Spanwise Holes Configuration 11-3Solid Body + Cooling Channel Configuration 11-4Solid Body + Basin Configuration 11-4Solid Body + Basin + Cooling Channel Configuration 11-4Solid Body + Cooling Channel Configuration 11-5Solid Body + Penny Configuration 11-5Solid Body + Squiller Tip Configuration 11-5

Internal Offset Shape Control 11-6Parametric Mode 11-6External ".geomTurbo" File 11-7External CAD Data File 11-7

Leading/Trailing Edge Wizard 11-8Basin / Tip Wall / Basin Bottom Wall Definition 11-8Mesh Generation Control 11-8

Blade to Blade Control 11-9Internal Cooling Wall Streamwise Distribution. 11-9Number of Points in O-Mesh (Solid Blade Area) 11-10Special Configuration: Inserted Cooling Tube 11-103D Control 11-12

Mesh of End Wall Solid Body 11-12Geometry Definition 11-13Topology Definition 11-133D Mesh Generation 11-14

11-3 Cooling - Blade Holes 11-14Blade Holes Methodology 11-14Blade Holes Properties 11-16

Geometry Control 11-17Holes Number Control 11-17Holes Shape Control 11-17Holes Location Control 11-18Parametric Mode 11-18XYZ Mode (Px,Py,Pz) 11-18RTHZ Mode (Pr,Pth,Pz) 11-18Holes Axis Control 11-19Parametric Mode 11-19XYZ Mode (Vx,Vy,Vz) 11-19RTHZ Mode (Pr,Pth,Pz) 11-19Holes Dimension Control 11-19Circular Shape 11-19Rectangular & Oval Shapes 11-19Trailing Edge Groove Shape 11-204-Sided Shape 11-20Holes Orientation Control 11-20External Holes Definition File 11-20Data File for Circular Shape Holes Line 11-20

xvi AutoGrid5™

Contents

Data File for Rectangular Shape Holes Line 11-21Data File for Oval Shape Holes Line 11-21Data File for Trailing Edge Groove Holes Line 11-21Data File for Trailing Edge Circular Holes File 11-22Data File for 4-Sided Shape Holes Line 11-22

Mesh Control 11-23Grid Points Distribution 11-23Optimization Control 11-24Wake Control 11-25Mesh Shape Control 11-25

Global Control 11-25Blade Holes Mesh Generation 11-26Blade Holes Project Management 11-27

11-4 Cooling - Basin Holes/Separator 11-27Basin Holes/Separator Methodology 11-28Basin Holes Properties 11-29

Geometry Control 11-30Parametric Mode 11-30XYZ Mode 11-30External Holes Definition File 11-31

Mesh Control 11-32Basin Separator Properties 11-33Basin Holes/Separator Mesh Generation 11-34

11-5 Cooling - End Wall Holes 11-34 End Wall Holes Methodology 11-35End Wall Holes Properties 11-35·End Wall Holes Mesh Generation 11-36

11-6 Cooling - Pin Fins 11-37Pin Fins Properties 11-38

Pin Fins Box Definition 11-38From IGG™ Edit Mode 11-38From External Block File 11-38

Pin Fins Lines Definition 11-38Pin Fins Mesh Generation 11-40

11-7 Cooling - Ribs 11-41Ribs Properties 11-41

Ribs Box Definition 11-41From IGG™ Edit Mode 11-42From 3D View 11-42

Ribs Geometry Control 11-42Ribs Mesh Control 11-44

Ribs Mesh Generation 11-45

CHAPTER 12:Python Script 12-1

12-1 Overview 12-1

12-2 Running a Script File 12-1

12-3 Commands Description 12-2

Contents

AutoGrid5™ xvii

Configuration Commands 12-2Geometry Import Commands 12-4Viewing Commands 12-5NIConfigurationEntities Class Commands 12-6RowWizard Class Commands 12-6WindTurbine Class Commands 12-7B2B Cut Class Commands 12-8Row Class Commands 12-8

Topology Management 12-9Row Boundaries Access 12-9Row Technological Effects 3D Access 12-9Row Blades Properties 12-9Row Properties 12-9Row Hub/Shroud Non-Axisymmetric 12-11Row Shroud Gap Non-Axisymmetric 12-11Row Hub/Shroud Solid Mesh 12-11Flow Paths Control 12-12Optimization 12-12

Blade Class Commands 12-13Blade Expansion & Rotation Parameters 12-14Blunt & Sharp Blade Parameters 12-14Default Topology Parameters 12-15

Topology Control 12-15Grid Points Control 12-15Mesh Control 12-16Intersection Control 12-17

HOH Topology Parameters 12-17Topology Control 12-17Grid Points Control 12-18Leading Edge Grid Points Distribution Control 12-19Trailing Edge Grid Points Distribution Control 12-19Mesh Control 12-20

H&I Topology Parameters 12-20Topology Control 12-20Grid Points Control 12-20Mesh Control 12-21

Cooling - Conjugate Heat Transfer Parameters 12-21Blade Cooling Holes Control 12-21Cooling Channel & Basin Control 12-21Basin Holes & Separator Control 12-22Pin Fins & Ribs Control 12-22

Gap Class Commands 12-23Fillet Class Commands 12-23WizardLETE Class Commands 12-24Blade Sheet Class Commands 12-25RSInterface Class Commands 12-26BasicCurve Class Commands 12-27StagnationPoint Class Commands 12-27TechnologicalEffectZR Class Commands 12-27

xviii AutoGrid5™

Contents

TechnologicalEffect3D Class Commands 12-28Cooling Channel Class Commands 12-28Hole Class Commands 12-28

Hole Location Control 12-29Parametric Mode (all hole type excepted grooves) 12-29XYZ Mode 12-29RTHZ Mode 12-29

Hole Axis Control 12-30Parametric Mode (all hole type excepted grooves) 12-30XYZ Mode (all hole type excepted grooves) 12-30RTHZ Mode (all hole type excepted grooves) 12-30

Hole Dimension Control 12-30Circular Shape 12-30Rectangular/Oval Shape 12-30Grooves (Parametric Mode) 12-30Quadrilateral Shape (4-Sided) 12-31

Hole Orientation Control 12-31HolesLine Class Commands 12-31

External File Control 12-31Hole Line Geometry Control 12-32

Holes Number 12-32Hole Shape 12-32Hole Location 12-32Hole Axis 12-33Hole Dimension 12-34Hole Orientation 12-35

Hole Line Mesh Control 12-35Grid Points Number 12-35Optimization 12-35Wake Control 12-36Holes Line Mesh Shape Control 12-36

Global Mesh Control 12-36Basin Class Commands 12-36

Global Parameters 12-36Hole Parameters 12-36

Basin Hole 12-37Separator 12-37Penny 12-37

PinFinsChannel Class Commands 12-37PinFinsLine Class Commands 12-38

External File Control 12-38Pin Fins Line Geometry Control 12-38

Pin Fins Number 12-38Pin Fin Shape 12-38Pin Fin Location 12-39Pin Fin Axis Control 12-39Pin Fin Dimension Control 12-40Pin Fin Orientation Control 12-40

Pin Fin Mesh Control 12-41

Contents

AutoGrid5™ xix

Grid Points Number 12-41Optimization 12-41Wake Control 12-41Holes Line Mesh Shape Control 12-41

Global Mesh Control 12-42PinFin Class Commands 12-42

Pin Fin Location 12-42Parametric Mode 12-42XYZ Mode 12-42UV Mode 12-42

Pin Fin Axis Control 12-43Parametric Mode 12-43XYZ Mode 12-43

Pin Fin Dimension Control 12-43Circular Shape 12-43Rectangular/Oval Shape 12-43Quadrilateral Shape (4-Sided) 12-43

Pin Fin Orientation Control 12-44EndWall Class Commands 12-44

End Wall Generation Control 12-44End Wall Parameters Control 12-44

EndWallHole Class Commands 12-44Hole Location Control 12-45

XYZ Mode 12-45MTheta Mode 12-45

Hole Axis Control 12-45Parametric Mode 12-45XYZ Mode 12-45

Hole Dimension Control 12-45Circular Shape 12-45Rectangular/Oval Shape 12-46Quadrilateral Shape (4-Sided) 12-46

Hole Dimension Control 12-46EndWallHolesLine Class Commands 12-46

External File Control 12-46Hole Line Geometry Control 12-47

Holes Number 12-47Hole Shape 12-47Hole Location 12-47Hole Axis 12-48Hole Dimension 12-48Hole Orientation 12-49

Hole Line Mesh Control 12-49Grid Points Number 12-49Optimization 12-49Wake Control 12-50Holes Line Mesh Shape Control 12-50

Global Mesh Control 12-50

xx AutoGrid5™

Contents

AutoGrid5™ 1-1

CHAPTER 1: Getting Started

1-1 OverviewWelcome to the AutoGrid5™ User’s Guide, a presentation of NUMECA’s fully automatic grid gen-erator for turbomachines. This chapter presents the basic concepts of AutoGrid5™ and shows howto get started with the program by describing:

• what is AutoGrid5™,• how to use this guide,

• how to start AutoGrid5™.

1-2 Introduction

1-2.1 What is AutoGrid5™

AutoGrid5™ is an automatic meshing system for turbomachinery configurations developed to easepre-processing for numerical computations on such configurations. Pre-processing consists ofdefining the geometrical description of the to-be-studied model and the discretization (mesh gener-ation) of the to-be-studied domain. The number of computational nodes needed increases rapidlywith the detail in the model. For 3D geometries, this easily reaches from 100,000 to 1,000,000nodes and even higher. This vast number of nodes, along with the description of the complexgeometries, necessitates the use of a powerful mesh generator that allows providing a computa-tional mesh with sufficient quality in an automatic way. AutoGrid5™ enables to deal with complexgeometries resulting in a structured mesh of high quality.

1-2.2 Features

The advanced tools of AutoGrid5™ enable to create mesh for a large range of gas turbines, fans andcompressors:

• turbofan, turboprop, turboshaft,

Getting Started Introduction

1-2 AutoGrid5™

• turbojet and after burning turbojet,

• axial or centrifugal,

• single or multistage,

• including or not bulbs on the hub,

• with one or multiple splitter blades (centrifugal),

• with hub or shroud clearances,

• with bypass,

• with seal leakages,

• with meridional or 3D technological effects.

1-2.3 Structured vs. Unstructured

Depending on the geometry complexity, the user should define the requested mesh type: structuredor unstructured. Structured meshes are to be preferred for reasons of accuracy in cases of alignedflow even if their generation can sometimes be difficult and cumbersome. Unstructured meshes canbe easily generated independently of the geometrical complexity and owing to their nature gener-ally tend to generate less points than in the structured case. For turbomachinery design, because of arequest of high accuracy, it is recommended to use AutoGrid5™ which enables to provide adaptedstructured meshes.

Users requiring an unstructured mesh may consider the use of the NUMECA automatic hexahedralmesh generation software Hexpress™.

1-2.4 Approach

To obtain fully automatic or semi-automatic grids with an optimal quality control, AutoGrid5™takes advantage of the characteristics of turbomachinery configurations by creating blade to bladegrids onto surfaces of revolution. The generation based on a conformal mapping between the 3DCartesian space (XYZ coordinates) and the cylindrical surfaces of the 2D blade to blade space (dm/r-θ plane) follows 4 main steps:

1. Definition of the geometry:

— The blade surface description.

— The curves for the definition of the hub and shroud surfaces of revolution.

— The additional data needed to handle special features such as splitters, meridional or 3Dtechnological effects.

2. Generation of meridional flow paths. These flow paths define the meridional trace of the sur-faces of revolution on which the 3D mesh will be built.

3. Generation and control of 2D meshes on spanwise surfaces. This 2D generation enables the userto control the mesh topology, the grid clustering and the mesh orthogonality along the solidwalls.

4. Generation of the final 3D mesh. This generation combines the meridional flow paths and the2D blade to blade meshes to create the mesh on surfaces of revolution. The use of the conformalmapping between the 3D Cartesian space and the 2D blade to blade space ensures conservationof quality in terms of orthogonality and clustering for each axisymmetric surface mesh.

The settings used to create a mesh are controlled interactively through dialog boxes. At the end ofthe grid generation process, all the parameters can be saved in a template file (".trb"). Meshes forsimilar geometries can be created automatically using this file.

Introduction Getting Started

AutoGrid5™ 1-3

1-2.5 Project Management

To manage complete mesh generation, AutoGrid5™ integrates the concept of project. AnAutoGrid5™ project involves template files and mesh files:

a) Mesh files

The mesh files contains the multiblock mesh topology, geometry, grid points, patch grouping andthe boundary condition types:

• new_prefix.bcs: boundary conditions files

• new_prefix.cgns: grid points files (CGNS format)

• new_prefix.geom and new_prefix.xmt_txt (.X_T): geometry files

• new_prefix.igg: topology file

• new_prefix.qualityReport: mesh quality report file

• new_prefix.config: mesh configuration file used for the grouping in FINE™ GUI and for thesubProject (more details in FINE™ User Manual)

These files can be loaded into the structured multiblock grid generation system IGG™ and by theCFD integrated environment FINE™/Turbo.

� The mesh quality file is saved at the end of the grid generation. If the new project has notyet been saved before launching the 3D generation, no grid quality report file will besaved because the system is not able to determine automatically the file location.

b) Template files

The template files contain the parameters and the geometry needed to reproduced the mesh withAutoGrid5™:

• new_prefix.geomTurbo and new_prefix.geomTurbo.xmt_txt (.geomTurbo.X_T): the geometryfiles (geomTurbo format)

• new_prefix.trb: the template file containing the grid generation parameters.

• new_prefix.info: the information file

• new_prefix_b2b.png: a picture of the blade to blade view

• new_prefix_merid.png: a picture of the meridional view

FIGURE 1.2.5-1 Example of file management for an AutoGrid5™ project

Getting Started How To Use This Manual

1-4 AutoGrid5™

1-3 How To Use This Manual

1-3.1 Outline

This manual consists of four distinct parts:

• Chapters 1and 2: Introduction and description of the interface,

• Chapter 3: Mesh fundamentals,

• Chapter 4: Mesh generation wizard,

• Chapters 5 to 8: Mesh generation and parameters,

• Chapters 9 and 10: Meridional and 3D technological effects.

• Chapter 11: Cooling & Conjugate Heat Transfer Modules.

• Chapter 12: Script within AutoGrid5™.

At first time use of AutoGrid5™ it is recommended to read this first chapter carefully and certainlysection 1-4 to section 1-6. Chapters 2, 3 and 4 give a general overview of the AutoGrid5™ interfaceand the way to manage a project. For every mesh generation, the input parameters can be defined asdescribed in the Chapters 5 to 8. Chapters 9 and 10 give an overview of how to add technologicaleffects in the Meridional or in the 3D view. Chapter 11 is describing how to define cooling holes,basin, cooling channel with pin fins/ribs and to mesh the solid body (blade and end walls). Chapter12 is presenting python commands available within AutoGrid5™.

1-3.2 Conventions

Some conventions are used to ease information access throughout this guide:

• Commands to type in are in italic.

• Keys to press are in italic and surrounded by <> (e.g.: press <Ctrl>).

• Names of menu or sub-menu items are in bold.

• Names of buttons that appear in dialog boxes are in italic.

• Numbered sentences are steps to follow to complete a task. Sentences that follow a step and arepreceded with a dot (•) are substeps; they describe in detail how to accomplish the step.

� The hand indicates an important note.

� The pair of scissors indicates a keyboard shortcut.

A light bulb in the margin indicates a section with a description of expert parameters.

First Time Use Getting Started

AutoGrid5™ 1-5

1-4 First Time Use

1-4.1 Basic Installation

When using AutoGrid5™ for first time it is necessary that AutoGrid5™ is properly installedaccording to the installation note. The installation note provided with the installation softwareshould be read carefully and the following points are specifically important:

• Hardware and operating system requirements should be verified to see whether the chosenmachine is supported.

• Installation of AutoGrid5™ according to the described procedure in a directory chosen by theuser and referenced in the installation note as ‘NUMECA_INSTALLATION_DIRECTORY’.

• A license should be requested that allows for the use of AutoGrid5™ and the desired compo-nent and modules (see section 1-6 for all available licenses). The license should be installedaccording to the described procedure in the installation note.

• Each user willing to use AutoGrid5™ or any other NUMECA software must perform a userconfiguration as described in the installation note.

When these points are checked the software can be started as described in the installation note orsection 1-5 of this users guide.

1-4.2 Expert Graphics Options

a) Graphics Driver

The graphics area of AutoGrid5™ interface uses by default an OPENGL driver that takes advan-tage of the available graphics card. When the activation of OPENGL is causing problems,AutoGrid5™ uses an X11 driver (on UNIX) or MSW driver (for Windows) instead.

It is possible to explicitly change the driver used by FINE™ in the following ways:

On UNIX:

in csh, tcsh or bash shell:setenv NI_DRIVER X11

in korn shell:NI_DRIVER=X11export NI_DRIVER

The selection will take effect at the next session.

On Windows:

• Log in as Administrator.

• Launch regedit from the Start/Run menu.

• Go to the HKEY_LOCAL_MACHINE/SOFTWARE/NUMECA International/Fine# or autog-rid# register.

• Modify the DRIVER entry to either OPENGL or MSW.


Getting Started How to Start AutoGrid5™ Interface

1-6 AutoGrid5™

b) Background & Foreground Colors

The background color of the graphics area can be changed by setting the environment variableNI_IGG_REVERSEVIDEO on UNIX/LINUX platforms or IGG_REVERSEVIDEO on Windowsplatforms. Set the variable to ’ON’ to have a black background (white axis) and set it to ’OFF’ tohave a white background (black axis). The variable can be manually specified through the follow-ing commands:

On UNIX:

in csh, tcsh or bash shell:

setenv NI_IGG_REVERSEVIDEO ON

in korn shell:

NI_IGG_REVERSEVIDEO=ONexport NI_IGG_REVERSEVIDEO


On Windows:

• Log in as Administrator.

• Launch System Properties from the Start/Settings/Control Panel/System menu.

• Go in the Environment Variables.

• Modify or add the IGG_REVERSEVIDEO entry to either ON or OFF.


Furthermore, the background and foreground colors of the graphics area can be adapted throughFile/Preferences menu available within IGG™ in the Colors page.

1-5 How to Start AutoGrid5™ InterfaceIn order to run AutoGrid5™, the following command should be executed:

On UNIX and LINUX platforms type: igg -niversion # -autogrid5 <Enter>

On Windows platforms:

1. click on the IGG icon in Start/Programs/NUMECA software/Fine# or in Start/Programs/NUMECA software/autogrid#. Then AutoGrid5™ is accessible through the menu Modules/AutoGrid5.

2. alternatively AutoGrid™ can be launched from a dos shell by typing:

<NUMECA_INSTALLATION_DIRECTORY>\Fine#\bin\igg.exe <Enter> or

<NUMECA_INSTALLATION_DIRECTORY>\autogrid#\bin\igg.exe <Enter>

where NUMECA_INSTALLATION_DIRECTORY is the directory indicated in section 1-4.1. ThenAutoGrid5™ is accessible through the menu Modules/AutoGrid5.

Required Licenses Getting Started

AutoGrid5™ 1-7

1-6 Required Licenses

1-6.1 Standard AutoGrid5™ License

The standard license for AutoGrid5™ allows for the use of all basic features of AutoGrid5™including:

• CAD importation and geometry management (except CATIA v5),

• single row and multistage management,

• skin, HOH and H&I blade-to-blade topology management,

• wind turbine mesh wizard,

• introduction of blade to blade cut,

• no meridional technological effect,

• no 3D technological effect,

• no solid mesh, cooling channel, holes, pin fins and ribs.

1-6.2 Additional Licenses

Within AutoGrid5™ the following features are available that require a separate license:

• CATIA v5 importation,

• introduction of bypass configuration,

• introduction of meridional technological effect,

• user-defined blade-to-blade topology management,

• introduction of 3D technological effect,

• introduction of solid mesh, cooling channel, holes, pin fins and ribs.

Next to AutoGrid5™ other products are available that require a separate license:

• FINE™/Turbo (structured mesh generator - solver - visualization software),

• FINE™/Design 3D (3D inverse design),

• Hexpress™ (unstructured mesh generator),

• FINE™/Hexa (unstructured mesh generator - solver - visualization software),

• FINE™/Marine (unstructured mesh generator - solver - visualization software).

Getting Started Required Licenses

1-8 AutoGrid5™

AutoGrid5™ 2-1

CHAPTER 2: Graphical User Interface

2-1 OverviewWhen launching AutoGrid5™ as described in Chapter 1 the interface appears in its default layoutas shown in Figure 2.1.0-1. An overview of the complete layout of the AutoGrid5™ Expert Modeinterface (see Chapter 4 for AutoGrid5™ Wizard Mode interface) is shown on the next page inFigure 2.1.0-2. In the next sections the items in this interface are described in more detail.

FIGURE 2.1.0-1 AutoGrid5™ Expert Mode Interface.

Together with the AutoGrid5™ interface, a Open Turbo Project Wizard window is opened, whichallows to open an existing project. See section 2-2.2 for description of this window.

Graphical User Interface Project Selection

2-2 AutoGrid5™

A File Chooser window is available for browsing through the file system and to select a file. Moredetail on the File Chooser window is given in section 2-8.

FIGURE 2.1.0-2 AutoGrid5™ Graphical User Interface (Expert Mode)

2-2 Project SelectionTogether with the AutoGrid5™ interface, a Open Turbo Project Wizard window is opened, whichallows to open an existing template with or without the corresponding mesh. See section 2-2.2 fordescription of this window. After use of this window it is closed. To create or open a template or aproject is also possible using the File menu.

2-2.1 Create New Template/Project

To create a new template or project when launching the AutoGrid5™ interface:

1. close the Open Turbo Project Wizard window.

Information area

Grid parameters area

Generation Status

KeyBoard Input AreaMessage area

Quick Access Pad

Graphics area

Menu bar

Toolbar

(section 2-3)

(section 2-4)

(section 2-5)

(section 2-7)

Control area(section 2-6)

Mouse coordinates

Viewing Buttons

Project Selection Graphical User Interface

AutoGrid5™ 2-3

2. select File/New Project or click on the New Project icon ( ). A new window will appear,

which allows to confirm. Click yes to confirm.

3. A project initialization window appears to assign a geometry to the new project. There are fivepossibilities:

• to start a new project presenting a bypass (if license key) from scratch.

• to start a new project presenting a bypass and a fin on fan (if license key) from scratch.

• to start a new project presenting no bypass and no fin on fan from scratch.

• to start a new project presenting a cascade configuration from scratch.

• to initialize a new project from an existing ".geomTurbo" file. Then a File Chooser window isavailable for browsing through the file system and to select a file. When clicking on OK(Open) the geometry is loaded in AutoGrid5™.

2-2.2 Open Existing Template/Project

If the Open Turbo Project Wizard window is closed, select File/Open Project. A new window willappear, which allows to confirm. Click yes to confirm.

To open an existing project the following possibilities are available in the Open Turbo Project Wiz-ard window:

• Click on the icon Select a Project File. A File Chooser will appear that allows to browse to thelocation of the existing template. Automatically the filter in the File Chooser is set to displayonly the files with extension ".trb", the default extension for a template file. If the option LoadMesh is active, the corresponding mesh will also be loaded.

• Select a Project in the List by left clicking on it, this list contains all projects available in thelocal AutoGrid5™ library. To view all information on the selected template, click on Info>>.To remove the selected template from the list, click on Hide. To open the selected templateclick on Open Template or double-click on the selected template. To open the selected project(the template with the corresponding mesh) click on Open Project.

Graphical User Interface Main Menu Bar

2-4 AutoGrid5™

2-3 Main Menu BarThe menu bar contains a part of available options of AutoGrid5™. Menu items can be activatedusing click and drag or click and release modes.

2-3.1 File Menu

2-3.1.1 Open Project

The menu item File/Open Project allows to open an existing AutoGrid5™ project. When click-ing on File/Open Project a new window will appear, which allows to confirm. Click yes to con-firm and to open the Open Turbo Project Wizard window presented in section 2-2.2.

2-3.1.2 New Project

The menu item File/New Project allows to create a new AutoGrid5™ project. When clicking onFile/New Project a new window will appear, which allows to confirm. Click yes to confirm anto open the project initialization window presented in section 2-2.1.

Main Menu Bar Graphical User Interface

AutoGrid5™ 2-5

2-3.1.3 Save Project / Save Project As

The File/Save Project or File/Save Project As menu item stores the project file (template andmesh) on disk. When clicking on File/Save Project As a new window will appear, which allows to:

• Save the project (template and grid) under a new name when clicking on the icon Select a newProject File Name.

• Save the project (template and grid) under an existing name selected in the list when clickingon the icon Overwrite the Selected Project.

• Add information to the project in the Enter Project Info area.

2-3.1.4 Save Template / Save Template As

The File/Save Template or File/Save Template As menu item stores the template files (template".trb" and geometry ".geomTurbo") on disk. When clicking on File/Save Template As a new win-dow will appear, which allows to:

• Save the template under a new name when clicking on the icon Select a new Template FileName.

• Save the template under an existing name selected in the list when clicking on the icon Over-write the Selected Template.

• Add information to the project in the Enter Template Info area.


2-6 AutoGrid5™

2-3.1.5 Save Grid -> Save Grid As

The File/Save Grid/Save Grid As menu item stores the grid files on disk to enable to launch acomputation within FINE™/Turbo 8.7.

2-3.1.7 Save Grid -> Save Grid As Fine 7.4

The File/Save Grid/Save Grid As Fine 7.4 allows to save the grids generated in the current ver-sion of AutoGrid5™ in a format compatible with IGG™ 5.7 (FINE™/Turbo 7.4).

2-3.1.7 Save Grid -> Save Grid As Fine 8.6

The File/Save Grid/Save Grid As Fine 8.6 allows to save the grids generated in the current ver-sion of AutoGrid5™ in a format compatible with IGG™ 8.6.

2-3.1.8 Save Grid -> Merge Project Grid

The File/Save Grid/Merge Project Grid menu item allows when dealing with multistage machinealready generated to adapt the ".cgns" file when regenerating one or more rows of the machinebased on a new geometry but still meshed with the same topology.

Steps

1. Generate full mesh of the multistage machine,

2. Save project,

3. Change geometry of one or more rows,

4. Regenerate mesh of rows presenting new geometry but keep same topology,

5. Merge project grid

2-3.1.9 Save Grid -> Save Fluid Domain(s)

In addition to the save subproject feature (more details in section 2-5.4.3 and in FINE™ User Man-ual), the menu Save Fluid Domain(s) creates and saves a subproject named SubProject Fluid con-taining only the fluid blocks of the project.

2-3.1.10 Project List -> Transfer File List

The File/Project List/Transfer File List menu item enables to store a library of project files con-tained in the project list when selecting File/Open Project.

2-3.1.11 Project List -> Open File List

The File/Project List/Open File List menu item enables to load a library of project files accessibleafterwards through the Project Selection and Template Selection windows

2-3.1.12 Scripts -> Edit

File/Scripts/Edit... opens a dialog box displaying some of the commands performed by the userwhen defining the geometry using Import CAD window, when performing a technological effect,...The user can easily edit this script (add, remove and modify commands). More details on the avail-able commands are presented in the Chapter 12.

Transfer File List


AutoGrid5™ 2-7

The dialog box contains two pull-down menus. File menu allows to open a script in a separate dia-log box and to save the script in a file. Run menu allows to run the script shown in the windowunder the current session ("Rerun on top").

2-3.1.13 Scripts -> Save All

File/Scripts/Save All... is used to save the dynamic recording of all commands performed by theuser since the beginning of its session.

2-3.1.14 Scripts -> Execute

File/Script/Execute... is used to run a python script file containing IGG™ commands.

A file chooser is opened to select a file with a ".py" extension. Upon selection of a valid file, thescript is executed in the current session and the result is visualized in the graphical window.Depending on the content of the script, operations will be added to the current project or a newproject will be automatically opened before operations are performed (The previous project isclosed).

If the script being run contains a syntactical error it will be aborted and a message will appear in theshell.

2-3.1.15 Scripts -> Re-execute Last

File/Script/Re-execute Last can be used to rerun the last script that was run using the Scripts/Exe-cute... command. This option is most useful when writing own scripts manually to rapidly test it onthe fly.

2-3.1.16 Print -> As PostScript

File/Print/As PostScript is used to dump the graphics area in a true PostScript file. This optionuses true Postscript statements to save the graphics content and can produce compact files when allgraphics entities in AutoGrid5™ consist of lines (i.e. visualization of the grid in wireframe). Whendisplaying surfaces in solid model, the quality of the saving reduces considerably while the size ofthe file can become very large.

2-3.1.17 Print -> As Bitmap PostScript

File/Print/As Bitmap PostScript is used to dump the graphics area in a bitmap PostScript file. Inthis mode each pixel of the graphics area is saved in the file. The size of the file can be very large.Bitmap saving may be more advantageous than true postscript when solid surfaces in hidden linemode appear in the graphics area.

2-3.1.18 Print -> As PNG

File/Print/As PNG is used to dump the graphics area in a PNG file.


2-8 AutoGrid5™

2-3.1.19 Export -> IGES

File/Export/IGES... menu is used to export geometry entities in the standard IGES format.

The entire geometry repository can be saved or only the selected curves and surfaces. The lengthunit must also be specified through the following dialog box:

2-3.1.20 Export -> Geometry Selection

File/Export/Geometry Selection... is used to save the selected geometry curves and surfaces intoan ASCII file.

Only the curves and surfaces selected respectively by the Geometry/Select/Curves and by theGeometry/Select/Surfaces options are saved.

� When selected geometry is containing Parasolid™ and/or CATIA V5 entities, a Para-solid™ file will also be saved in addition of ".dat" file.

2-3.1.21 Export -> Geometry Control Points

File/Export/Geometry Control Points... is used to save the control points of the selected geome-try curves into an ASCII file. It does not save the complete information about the curve (type, para-metrization,...). The files created in this way are not intended to be directly read by AutoGrid5™.Their main use is to print out the coordinates of the control points of the curves.

� This option is only available for curves, not for surfaces.

2-3.1.22 Export -> Block Coor

File/Export/Block Coor... is used to save the coordinates of an active block range in ASCII format,according to the level of coarseness selected for the grid (set by using View/Coarse Grid menuitem). A warning is given if the grid has not been created yet. The standard block grid file format isused and is detailed in IGG™ User Manual - Chapter 11.

The block range to save must be determined by two points, specified by their IJK coordinates in thekeyboard input area (indices start at 1):

Enter imin jmin kmin (q)Enter imax jmax kmax (q)

By default, values for the full block range are displayed.

2-3.1.23 Export -> Face Coor

File/Export/Face Coor... is used to save the coordinates of the active face in ASCII format, accord-ing to the level of coarseness selected for the grid (set by using the View/Coarse Grid menu item).The standard surface grid file format is used and is detailed in the IGG™ User Manual - Chapter 11.


AutoGrid5™ 2-9

2-3.1.24 Export -> Patch Coor

File/Export/Patch Coor... is used to save the coordinates of the active face patches in ASCII for-mat, according to the level of coarseness selected for the grid (set by using the View/Coarse Gridmenu item).

The standard face grid file format is used and is detailed in the IGG™ User Manual - Chapter 11.One file is created for each patch of the active face and is named automatically by appending thepatch number to the specified file name. The files are written with a ".dat" extension.

2-3.1.25 Export -> Plot3D

File/Export/PLOT3D... is used to save the coordinates of all grid blocks in a PLOT3D format file.The saved file will have a ".g" extension and its format is described in the IGG™ User Manual -Chapter 11.

The following dialog box is opened to select a file with a ".g" extension and the corresponding fileformat.

FIGURE 2.3.1-1 Output file and file format selection

The following file types can be selected in the File type entry:

• ASCII

• Binary single

• Binary double

• Unformatted single

• Unformatted double

Binary stands for C binary files whereas Unformatted stands for Fortran binary files. Single anddouble describe the precision of reals.

Then two radio buttons are provided to select the binary order desired in the output file: little or bigendian. This information must be specified only for binary files (the buttons are deactivated whenASCII type is selected).

The desired file can be selected by entering its full path name into the Plot3D File entry or through

a file chooser opened by pressing the icon ( ) next to the file entry.

2-3.1.26 Import -> IGG Project

File/Import/IGG Project... is used to merge an existing IGG™ project stored on disk with the cur-rently opened project. It allows several people working on large projects to perform the meshing inseparate sessions and to merge their work at a later stage.


2-10 AutoGrid5™

a) Prefix

To easily recognize blocks and groups of an imported project from those in the current project, aprefix can be specified during importation. For this purpose, a dialog box is provided:

Upon proper prefix specification, all the names of patches, blocks, geometry groups and blockgroups will be automatically prepended with the prefix. For example, if a block being imported isnamed "Inlet"and a prefix "stage1" is specified, the name of the block within the current sessionwill be "stage1#Inlet". Due to limitations in the CGNS format, the length of the prefix should belimited to 5 characters. Moreover it cannot begin with a number.

If no prefix is specified blocks and groups names will not be modified. Exception to this rule holdshowever when an imported block has the same name as a block in the current project. In that casean underscore will be automatically appended to the name.

Pressing on the Cancel button will cancel the importation of the selected project in AutoGrid5™.

b) Importation operations

During project importation the following operations are performed:

• All the curves and surfaces from the imported project are added to the current project. When aname clashing occurs with existing curves or surfaces, AutoGrid5™ automatically renames theimported entities. The prefix currently does not apply to curves and surfaces.

• All the blocks of the imported project are appended to the existing blocks. The index of theimported blocks is adapted automatically to follow the last block of the current project. Thename of the patches and blocks follow the rule described here above.

• The geometry and block groups are imported in the current project. The names of the groupsfollow the rule described here above.

2-3.1.27 Import -> IGG Data

File/Import/IGG Data... is used to read external curves and surfaces stored in an ASCII IGG™format. The file formats are specific to IGG™ (Curve & Surface data files) and are described inIGG™ User Manual - Chapter 11.

When using the option, a file chooser is opened to select files with ".dat" or ".dst" extensions. Uponacceptance, the entities are automatically stored in the geometry repository and displayed in thegraphical area.

� A fitting of the view may be needed to see all the entities properly.

Since AutoGrid5™ uses the name of curves and surfaces to access them, no duplicate is allowed.During importation of a geometry file, AutoGrid5™ checks for name duplication. When an entitybeing loaded has the same name as an existing entity in the current session, a dialog box is openedwith different possibilities:


AutoGrid5™ 2-11

FIGURE 2.3.1-2 Importation options dialog box.

Replace:

When using this mode, AutoGrid5™ replaces the existing curve or surface by the one beingimported. At the end of importation, AutoGrid5™ remaps all the vertices and edges lying on thereplaced entities so that the topology of the grid fits onto the new geometry.

This mode should be used when using the current project as a template. See the chapter related totemplates for additional information.

Don’t Load:

When using this mode, the entity having the same name will NOT be imported in the session.

Auto Rename:

When using this mode, AutoGrid5™ imports the entity and automatically modifies its name so thatit becomes unique in the current session. If no replacement is desired (as described above), thisoption should be used.

2-3.1.28 Import -> External Grid

File/Import/External Grid... is used to import inside the current AutoGrid5™ project a block gridgenerated either by IGG™/AutoGrid5™ (using File/Export/Block Coor... menu item) or byanother grid generator. A file chooser is opened to select a file with a ".dat" extension. Several fileformats are available:

• Block data file

• Surface data file (2D or 3D wireframe)

• Multiple surface data file (2D or 3D wireframe)

See the IGG™ User Manual - Chapter 11 for a detailed description of the formats. Upon selectionof a valid file, a new block (or several for multiple data files) is created and put at the end of the listof blocks. For "Surface data file", which represent surfacic meshes, only face 1 of the block is cre-ated. For 2D meshes, the z coordinate is set automatically to 0 for all the points. AutoGrid5™ auto-matically creates the block topology (edges) by using the boundary grid points of the block.

2-3.1.29 Import -> Face Grid

File/Import/Face Grid... is used to import and copy a 2D or 3D grid surface to the active face or toa BC patch on this face. A file chooser is opened to select a file, which must have a ".dat" extensionand have the Surface data file format (see the IGG™ User Manual - Chapter 11 for more informa-tion about this format). The type of surface and the edge creation mode are indicated from the key-


2-12 AutoGrid5™

board input area. If the edges of selected surface are on the boundaries and the edge creation flagis on, the segments of that edge are created as polylines.

When the active face contains several patches, the imported grid can be copied on the entire face oron one of its patches. In this case, the following prompt(s) appear:

Surface (=0) or Patch (=1) ? (q)>> 1Patch number (1...3) ? (q) (if previous answer is 1)>> 2

Then the following prompt will appear to specify if edges must be reconstructed by using the faceboundary grid points:

Create boundary segments (y/n) ?>> y

2-3.1.30 Import -> Topology

The option File/Import/Topology... allows to re-use an existing IGG™/AutoGrid5™ project on asimilar geometry by importing all the topology and grid information from the related ".igg" file.The complete current project is deleted before importing. During the import operation, the follow-ing happens:

• all the geometry entities are discarded from the imported project.

• the geometry groups are loaded, emptied from any curve or surface.

• the grid information like number of blocks, connection between blocks, clustering,... iskept.

• the blocks topology (vertices and edges) is kept, as well as their position and shape.

• the face generation recording, including the projection on geometry groups is kept.

Then, to use the imported topology on a similar geometry, do the following:

• Import the new geometry with the File/Import/IGG Data... or IGES... options.

• Redefine the geometry groups by selecting the proper surfaces and by adding them to theexisting groups (right button press on a geometry group pops up a menu for adding orremoving the current geometry selection).

• Remap all the vertices manually onto the new geometry. New vertices may be added if thetopology of the new geometry has changed.

Regenerate the faces with the Regenerate Face option. It is to be noted that face projected onto ageometry group will be successfully re-projected if the groups have been redefined as described inthe previous operation.

2-3.1.31 Import -> CATIA V5

The option File/Import/CATIA V5... reads external geometry files in CATIA format. SeveralCATIA files can be opened when defining the geometry before the domain creation.

� CATIA importation is optional and subject to an additional license file allowing the userto import CATIA V5 file within AutoGrid5™.

2-3.1.32 Import -> Parasolid

The option File/Import/Parasolid... reads external geometry files in Parasolid™ format ".x_t".Several Parasolid™ files (Parasolid™ and CATIA v5) can be opened when defining the geometrybefore the domain creation.


AutoGrid5™ 2-13

� Importation is not available on 64 bits platforms except LINUX x86_64. Please refer tothe installation note for more information about the 64 bits supported platforms.

� The supported Parasolid™ version is 19.

2-3.1.33 Import -> IGES

File/Import/IGES... menu is used to import CAD data stored in the standard IGES format. Whennames are defined for entities the IGES file, AutoGrid5™ uses them for the new entities created inthe repository. When these names are already used by existing entities, a dialog box is opened toresolve the conflict. See the menu option File/Import/IGG Data... for details about the dialog box.

FIGURE 2.3.1-3 IGES file browser

This option provides a powerful browser to scan the content of an IGES file and selectively importIGES entities recognized by AutoGrid5™. In the case of composite curves and surfaces, thebrowser allows to view each component defining the entity and to select them individually.

Filters, reserved to expert users, allows to filter the data viewed by the browser. Each filter corre-sponds to a criterion defining if entities with the corresponding attribute set accordingly will be dis-played in the browser/imported.

It might be useful to uncheck the Blank Filter/Blanked item in order to import only the entitiesmeant to be visible and get a clear view of the intended geometry. The same holds for the EntityUse Filter with only the geometry item checked.

For the Subordinate Filter items, it might be useful to also have the both item checked if top-levelentities cannot be translated, preventing the importation of their depending entities.


2-14 AutoGrid5™

The Filters default settings have the following items checked: all Blank Filter items, all EntityUse Filter items but the definition item, the Subordinate Filter independent and logical items,all Hierarchy Filter items.

See the IGES reference manual for a complete understanding of all filter values. The list of availa-ble IGES entities that can be imported in AutoGrid5™ are presented in the table below.

2-3.1.34 Import -> PLOT3D

File/Import/PLOT3D... is used to import inside the current AutoGrid5™ project block(s) gener-ated either by IGG™/AutoGrid5™ (using File/Export/PLOT3D... menu item) or by another gridgenerator. The imported file must have a ".g" extension and have the PLOT3D file format, asdescribed in IGG™ User Manual - Chapter 11.

The following dialog box is opened to select a file with a ".g" extension and the corresponding fileformat.

Entity Type Nr Entity Type

100 Circular Arc

102 Composite Curve

104 Conic Arc

106 Copious Data (only curves and not points inAutoGrid5™)

110 Line

112 Parametric Spline Curve

114 Parametric Spline Surface

116 Point

120 Surface of Revolution

122 Tabulated Cylinder

126 Rational B-spline Curve

128 Rational B-Spline Surface

130 Offset Curve (only uniform offset inAutoGrid5™)

140 Offset Surface

142 Curve On Parametric Surface

144 Trimmed Parametric Surface

158 Sphere

196 Spherical surface


AutoGrid5™ 2-15

FIGURE 2.3.1-4 Input file and file format selection

The following file types can be selected in the File type entry:

• ASCII

• Binary single

• Binary double

• Unformatted single

• Unformatted double

Binary stands for C binary files whereas Unformatted stands for Fortran binary files. Single anddouble describe the precision of reals.

Then three buttons are provided to select the remaining file specifications. These ones must bespecified only for binary files (the buttons are deactivated when ASCII type is selected). The twofirst radio buttons allow to select the binary order in the file: little or big ending. The last buttonspecifies if the file is single or multi-block.

The desired file can be selected by entering its full path name into the Plot3D File entry or through

a file chooser opened by pressing the icon ( ) next to the file entry.

Upon selection of a valid file, the blocks of the imported file are created and put at the end of thecurrent list of blocks. AutoGrid5™ automatically creates the block topology by using the blockcoordinates.

2-3.1.35 Import -> CGNS

File/Import/CGNS... is used to import CGNS grid files inside the current AutoGrid5™ project.CGNS is a widely used standard for the exchange of CFD data. In particular it is very well suited toexchange meshes and boundary conditions between heterogeneous systems. Block coordinates andboundary conditions are read from the ".cgns" file. Only connections of type CON can be read andperformed automatically by AutoGrid5™.

It is to be noticed that a CGNS file is automatically created during the saving of a project, using theFile/Save options. This file can be reread by AutoGrid5™ using this option or exchanged withother CGNS compliant systems.

The imported file must have a ".cgns" extension and must be a valid CGNS format, as described inIGG™ User Manual - Chapter 11.

A file chooser is opened to select a file with a ".cgns" extension. Upon selection of a valid file, theblocks of the imported file are created and put at the end of the current list of blocks. AutoGrid5™automatically creates the block topology by using the block coordinates.


2-16 AutoGrid5™

2-3.1.36 Import -> GridPro

File/Import/GridPro... is used to import inside the current AutoGrid5™ project block(s) createdby the GridPro grid generator.

A file chooser is opened to select a GridPro file. Upon selection of a valid file, the blocks of theimported file are created and put at the end of the current list of blocks. A message indicating whatblock is read appears in the AutoGrid5™ message area. AutoGrid5™ automatically creates theblock topology by using the block coordinates. Blocks connection information is read by IGG™and patch decomposition is automatically performed. Periodicity information is not read from thefile and must be specified manually within AutoGrid5™, when required, using the Grid/Periodic-ity... and Grid/Boundary Conditions... menu items.

2-3.1.37 Preferences

The File/Preferences opens a dialog box to control the default settings of AutoGrid5™.

This dialog box contains three pages. All the parameters are validated by pressing the Apply button,which applies the option and automatically saves them in the file ~/.numeca/igg.preferences. Whenstarting AutoGrid5™, this file is read automatically and the preferences are restored directly. If thisfile cannot be found, the system is initialized with default settings.

a) Saving Page

Backup when saving is used to make a backup of the geometry and topology files at saving.

AutoGrid5™ backups the project using a ".bak" extension (<projectname>.igg.bak).

Ask quality check when saving option is used to make automatically some tests on the grid eachtime a project is saved. It includes:

• A calculation of the number of multigrid levels available in the I, J and K directions for thewhole grid.

• A calculation of the negative cells in single and double precision.


AutoGrid5™ 2-17

• A rough idea of the grid quality (extremum values) in terms of orthogonality, aspect ratioand expansion ratio.

The results are displayed in a dialog box appearing automatically just after the saving.

Save CGNS patch info option is used to save automatically boundary conditions information asconnection type, full non matching connection definition,... in the ".cgns" file. The Keep Row(s)Name option is used to control the way the row names and blade names are saved in the cgns file:

• "ROW(<i>)" and "BLADE(<i>)" where i is the row and blade number when Keep Row(s)Name is not active.

• row and blade names imposed in AutoGrid5™ (Quick Access Pad/Rows Definition)when Keep Row(s) Name is active.

Keep Left Handed Orientation After Saving option (when deactivated) is used to keep left-handed blocks when saving in order to decrease the time needed for saving or loading intermediatemeshes including multiple blocks (e.g. blade with cooling holes and channel with ribs and pin fins).

b) Graphics Page

The Graphics Driver flag is used to select the driver X11.

The Visibility flag is used to control the rendering of graphic objects during dynamic viewing oper-ations. With full visibility, all graphic objects are displayed during viewing operations, which mayslow down the system response. When partial visibility is selected, only grid boundaries are dis-played during viewing operations.

Turn On Additional Lights option allows to enhance the lightening for shaded representations.

Edges width frame allows to control the width of the block edges displayed in the graphics area.The width of the active block edges can be controlled by Highlight width and the width of otherblock edges by Normal width.

Grid Line Width allows to control the width of the grid lines displayed in the graphics area.


2-18 AutoGrid5™

Geometry Curve Width allows to control the width of the geometry curves displayed in the graphicsarea.

Meridional channel shading option allows to have the channel in the meridional view representedwith shading.

B2B Full Mesh Visibility option allows to see the mesh moving in the blade to blade view whenapplying the modified blade to blade mesh parameters. This option is interesting for demo purposesbut it is not recommended to keep it active when generating the 3D mesh.

B2B Full Quality Visibility option allows to see the mesh skewness (orthogonality) field moving inthe blade to blade view when applying the modified blade to blade mesh parameters. This option isinteresting for demo purposes but it is not recommended to keep it active when generating the 3Dmesh.

Automatic 3D Mesh Viewing option allows to see the 3D solid mesh (section 2-3.3.8) when loadinga project or after generating the mesh.

c) Layout Page

This page allows to control some aspects of the AutoGrid5TM graphical interface.

Quick Access Pad is used to toggle the Quick Access Pad.

Control Area toggles the visibility of the control area at the bottom of AutoGrid5™ main window. Itallows to use a larger part of the screen for better graphics rendering, but cannot be used during theinteractive generation of a mesh, since it hides the keyboard input area and the viewing buttons.

Balloon Help is used to activate or deactivate the on-line balloon help available in AutoGrid5TM.When activated, help balloons are displayed when the cursor is located on some buttons or icons.

Progress Status is used to toggle the progress status window when performing the mesh generation.

Optimization Convergence History toggles the convergence history window when performing themesh generation.

2-3.1.38 Quit

File/Quit is used to end the interactive session. A dialog box is inserted to confirm the end of the ses-sion. Please notice that the current work is NOT automatically saved when exiting AutoGrid5™.

2-3.2 Geometry Menu

All menus are described in detail in the dedicated IGG™ User Manual - Chapter 9. This menu is onlyavailable when selecting the 3D view or when adding a 3D technological effects (AutoGrid5™ UserManual - Chapter 10).


AutoGrid5™ 2-19

2-3.3 View Menu

The View menu options provide a set of display options to visualize the grid boundaries, surface and blockgrids, repetition, hidden lines and rendered surfaces. The viewing parameters and projection can also be mod-ified interactively.

2-3.3.1 Patch Viewer

View/Patch Viewer... is used to visualize selected patches in wireframe or solid mode to produce full ren-dered pictures of the grid. The dialog box provides control over the colour and transparency effects for eachpatch.

Patch Browser:

The patch browser (see figure below) lists all the patches in the grid, according to the current Block, Face,Patch or Type filters. In this browser, one or more patches can be selected with the left mouse button.

It is possible to select several patches at once in the following way:

• While holding the <Ctrl> key down, select the desired patches in the browser.

• While holding the <Shift> key down, select two patches delimiting a range of patches.

• While pressing the left mouse button, drag the mouse and release the left button to select a range ofpatches.

FIGURE 2.3.3-1 Patch Viewer dialog box

Filters:

The different filters allow to display specific patches of a grid in the browser while hiding the others. TheBlock, Face and Patch filters work together and allow to display patches by indices. For example:

Block Filter: ’*’

Face filter: ’1 2’

Patch filter: ’*’

Patch browser, allowingto select the current patch(es)

Wireframe visualization control

Solid visualizationcontrol

Show the selected

Hide wireframe forselected patches

Show the selected patchesas solid

Hide solid forselected patches

Visibility control duringtransparency setting

patches as wireframe


2-20 AutoGrid5™

shows in the browser all the patches of faces 1 and 2 of all the blocks. ’*’ means ALL. The Face fil-ter allows also to select a boundary face by choosing imin, imax, jmin, jmax, kmin or kmax. Theseitems can be shown and selected by left-clicking on the Face filter arrow.

The Type filter is very useful to list all the patches of a given type (according to the other filters). Inparticular it allows to easily identify the periodic and connected patches (PER, PERNM, CON,NMB) and the patches that have not any type yet (UND).

Patch visualization:

To assign a color to one or several patches:

1. Select the patches in the patch browser,

2. Select one color from the predefined colors or from customized colours (Ed. button),

3. Press the Show Grid (wireframe representation) or the Show Solid (solid representation)button.

To hide the patches representation, proceed in the same way by pressing the Hide Grid or the HideSolid button.

It is possible to make some patches semi-transparent by specifying a transparency factor on theselected patches. The transparency factor can vary from 0 (no transparency) to 1 (highly transpar-ent). By default, the transparency factor is only applied when pressing the Show Solid button. Thisdefault may be overwritten by activating the Full Visibility toggle button. In this case, the transpar-ency effect will be recomputed each time the transparency slider is moved.

Since the rendering of transparent patches is computationally intensive and may take up to severalminutes, it is not advised to use the Full Visibility flag on large grids.

2-3.3.2 Sweep Surfaces

View/Sweep Surfaces... is used to scroll the constant grid index surfaces within 3D grid blocks. Ifthe active block is not generated or has been modified since the last generation (by moving a vertex,for example), the following message will appear:

FIGURE 2.3.3-2 Message indicating that the block may be regenerated

� It asks for block regeneration. If the block is not generated and that the no button ispressed, the dialog box of the next figure will appear but without being able to do some-thing except pressing the Close button. If the block has been modified since the last gen-eration (a block is not automatically regenerated after modifications of its topology) andthat the no button is pressed, the mesh that will be interactively displayed (see below)may look quite strange.

Mesh sweeping is done through the following dialog box:

FIGURE 2.3.3-3 Sweep Surfaces dialog box.


AutoGrid5™ 2-21

The Block box allows to choose the active block in which the surface grids will be scrolled. Next tothis box, the active block name and the amount of grid points in each direction (according to thecoarse grid levels selected) are displayed.

� It is to be noticed that setting the Block to 0 allows to scroll the grid surface on allblocks.

The I, J and K scrollers allow to interactively sweep the surface grid along the three directions.While scrolling, surface grids are displayed for each constant index direction.

2-3.3.3 Coarse Grid

View/Coarse Grid is used to view in the meridional, blade to blade and 3D views the selectedcoarse grid level in the active view. When selecting the menu, a dialog box allows to impose theCoarse Grid Level to plot.

FIGURE 2.3.3-4 Coarse level viewer

In the meridional and blade to blade views, the option is available when respectively the flow pathsand the blade to blade mesh are generated.

In the 3D view, the coarse grid levels can be plotted on the active block or grid. To select the scope(active block or grid), set the viewing scope (see the Quick Access Pad/View/Grid page descrip-tion) to Block or Grid mode. The active coarse grid levels are taken into consideration while:

• displaying the block faces and boundary conditions patches on all active views,

• saving the block or face coordinates,

• scrolling the block surface grids or cells.

These graphical representations are automatically updated after each change to the coarse grid lev-els.

The finest grid level is identified as 1. The smallest number of grid points for coarse levels is 2. Thecoarsest level is computed and updated in each index direction separately. The keyboard inputarea is used to enter the desired levels within available ranges.


2-22 AutoGrid5™

2-3.3.4 Repetition

View/Repetition... opens the following dialog box to control the repetition of the blocks on theactive view (in 3D and blade-to-blade views only):

FIGURE 2.3.3-5 View Repetition dialog box

For each block, the number of repetition desired can be set in the Nb Repet entry. The repetition ofall blocks can be displayed or hidden respectively by pressing the Show or Hide button.

To perform a repetition, AutoGrid5TM takes the information about the periodicity of each block(angle, rotation axis,...) in the Grid/Periodicity dialog box. By default, the repetition is not dis-played.

2-3.3.5 Face Displacement

View/Face Displacement menu allows to adapt the view if interferences are appearing between thegrid lines and the shading.

When the block face grids are visualized, in both wireframe and solid modes (shading), visual inter-ference may be produced between the grid lines and the shading. For this reason, AutoGrid5™slightly shifts the grid lines towards the user to get a correct picture.

This shift is controlled by the Face displacement. This parameter represents the amount by whichthe grid is shifted along the view plane normal vector (normal to the screen), and is used to correctthe display when combining wireframe and solid representations.

The following window is shown to enter the face displacement (higher or equal to 1).

Apply and Close to respectively apply the new parameter and close the window.

2-3.3.6 View Depth

View/View Depth menu allows to control the view depth. This depth is used for all interactivegeometry editing operations with the mouse.

When using the option, the new depth for the active view is imposed by entering the coordinates ofthe reference point:

New reference pt coordinates (q)>> 0 0 0


AutoGrid5™ 2-23

All subsequent inputs with the mouse will be at z = 0. To quit this option, enter <q> and press<Enter>.

2-3.3.7 Toggle 3D Solid View

View/toggle 3D Solid View is used as a toggle to show shaded view of the complete hub and singleblade on each of the rows of the turbomachine in the 3D view.

The number of blades in the graphics area can be repeated for each row individually using theNumber Of Graphics Repetition parameter available in the Row Properties dialog box. Activatethe Default option to see a complete view of all the blades of the selected row.

FIGURE 2.3.3-6 3D solid view with graphics repetition

2-3.3.8 View/Hide 3D Solid Mesh

View/view 3D Solid Mesh and View/hide 3D Solid Mesh are used to respectively show or hide inthe 3D view the mesh on hub and blades (shading and mesh on hub/blades). Furthermore, the View/Patch Viewer... menu can be used to adapt or to clean the visualized solid mesh.


2-24 AutoGrid5™

2-3.3.9 View 3D Solid Block

View/view 3D Solid Block is used to show in the 3D view the mesh on the solid blocks (shading andmesh).This option is not a toggle, the View/Patch Viewer... menu has to be used to adapt or to clean the visu-alized solid mesh.

2-3.3.10 Toggle Throughflow Mesh

View/toggle throughflow mesh is used as a toggle to show the throughflow mesh in the meridional view. Thismesh is used for the initial turbomachinery solution available in FINE™ GUI (EURANUS).

2-3.3.11 Toggle Tool Bar / Symbolic View / Configuration/IGG Panel

View/Toggle Tool Bar is used as a toggle to show or hide the toolbar presented in section 2-4.

View/Toggle Symbolic View is used as a toggle to show or hide the symbolic view presented in section 2-7.1.

View/Toggle Configuration Panel is used as a toggle to show or hide the quick access pad presented in sec-tion 2-5.

View/Toggle IGG Panel is used as a toggle to show or hide the quick access pad of IGG™ available whenactivating the 3D view or performing a 3D technological effect as presented in section 10-4 and in IGG™ UserManual.

Blade including basin – cooling holes

cooling holes

basin


AutoGrid5™ 2-25

2-3.4 Grid Menu

The Grid menu includes the connectivity and boundary conditions definitions, as well as the gridquality tools.

2-3.4.1 Periodicity

Grid/Periodicity... menu is used to check or to define the periodicity for each block of the grid togenerate and it is defined automatically depending of the number of blades in the row in the follow-ing dialog box.

FIGURE 2.3.4-1 Periodicity dialog box

In this box, the following things can be specified:

Block number: The periodicity can be defined block by block or for the whole grid. To define theperiodicity for the whole grid, the block number should be set to ’0’. All subsequent "Apply" willaffect ALL the blocks of the grid, overwriting previous settings.

Periodicity type: Three types of periodicity can be specified:

— Rotation: A rotation periodicity rotates a block around a given axis by a specified angle. Therotation axis is specified by a rotation axis direction (axis) and an anchor point (origin). Theangle is indirectly specified by indicating the number of periodicities for the block, e.g. acompressor with 4 blades should have a number of periodicities of 4, and the number ofmeshed passages is directly specified.

— Translation: A translation periodicity, e.g. a cascade in turbomachinery, is obtained by spec-ifying a translation vector, in direction and magnitude. For example, a translation vector of(0,0,2) will repeat a block along the Z axis by 2 absolute units.

— Mirror: A mirror periodicity mirrors a block with respect to a symmetry plane and is speci-fied by the origin and normal of the mirror plane.

To choose among these types, simply left-click on it.

The dialog box contains also three buttons at the bottom:

Index of the block affected by "Apply" (0 applies the settings to all the blocks)

Clears the parameters

Applies the current settingsto the specified block

Periodicity parameters,function of the periodicity type

Periodicity type

Close the box


2-26 AutoGrid5™

• Apply: it applies the current settings to the specified block(s).

• Clear: it resets the periodicity parameters to default values for the specified block(s).

• Close: it closes the dialog box.

2-3.4.2 Boundary Conditions

Grid/Boundary Conditions... menu item allows to check or to serve three different purposes per-formed automatically within AutoGrid5™:

1. To divide the faces of the grid into patches, for grid generation purposes.

2. To specify the boundary conditions on these patches, as input to a flow solver.

3. To establish connection between the patches.

When invoking the menu item, a dialog box is opened:

FIGURE 2.3.4-2 Boundary Conditions dialog box

a) Patch Browser

The patch browser (see Figure 2.3.4-2) lists all the patches in the grid, according to the current"Block", "Face", "Patch", "Type", "MG.Level" or "Name" filters. In this browser, a patch can beselected with the left mouse button. This patch is automatically visualized in the graphics areaaccording to the visualization options in the dialog box:

• Show Grid will display the grid of the patch.

• Show Solid will display the patch as a solid face.

It is possible to select several patches at once in the following ways:

1. While holding the <Ctrl> key down, select the desired patches in the browser.


AutoGrid5™ 2-27

2. While holding the <Shift> key down, select two patches delimitating a range of patches.

3. While pressing the left mouse button, drag the mouse and release the left button to select arange of patches.

The last patch selected is always the ’current patch’ for manual connections and patch editing.

b) Filters

The different filters allow to display specific patches in the browser while hiding the others. The"Block", "Face" and "Patch" filters are cumulative and allow to display patches by indices. Forexample:

Block Filter: ’*’ (’*’ means ALL)

Face filter: ’1 2’

Patch filter: ’*’

shows in the browser all the patches of faces 1 and 2 of all the blocks. The "Face" filter allows alsoto select a boundary face by choosing imin, imax, jmin, jmax, kmin or kmax. These items can beshown and selected by left-clicking on the "Face" filter arrow.

The "Type" filter is very useful to list all the patches of a given type (according to the other filters).In particular it allows to easily identify the connected patches (CON, NMB, PER, PERNM) and thepatches that have not any type yet (UND).

The "MG.Level" filter can be used to see the list of patches for a given multigrid level.

The "Name" filter allows to display patches by name. Enter or choose an expression. All the patchesof which the name contains this expression will be listed.

c) Patch Type Specification

An option menu allows the setting of the boundary condition type for the selected patch(es). Thepossible boundary condition types are the following:

• UND : undefined type.

• INL : inlet.

• OUT : outlet.

• EXT : external. Used to impose farfield conditions.

• SOL : solid. Used for walls.

• SNG : singular. Used for patch degenerated into a line.

• MIR : mirror. Used to impose a symmetry plane.

• ROT : rotating. Used for rotor-stator interaction.

• CON : matching connection.

• NMB : non matching connection.

• PER : periodic matching connection.

• PERNM : periodic non matching connection.

The following types can be set manually: INL, OUT, EXT, SOL, SNG, ROT, MIR. To set such atype, left-press on the Set Patch Type button of the dialog box; a list with all the types that can be setmanually appears. Move the cursor to the desired type and release the left button to set it to theselected patch(es).

If a patch is involved in a full non matching connection, a "*" will appear next to the patch type.


2-28 AutoGrid5™

d) Patch Definition & Editing

The patch definition mode is enabled by pressing the Edit Patch >> button. The dialog box is thenenlarged to show a symbolic definition of the current face, as shown in the following figure.

FIGURE 2.3.4-3 Patch editing

In this example the active face has three patches with a topology indicated in the figure. The currentpatch is represented in yellow.

The current patch can be changed by clicking with the left mouse button within the rectangle corre-sponding to the desired patch. The current patch is automatically updated in the browser and in thegraphics area.

An information area is used to display information about the current patch (limits, indices and rela-tive orientation of the connected patch if existing, and patch type). See Manual Connectivity Set-tings section for information about the relative orientation.

The patch definition mode is disabled by pressing the "<<" button (see Figure 2.3.4-3).

e) Automatic Connectivity Search

Automatic connectivity search allows to perform connections between patches (matching and nonmatching, periodic or not).

For periodic connections, the block periodicity must be set previously by using the Grid/Periodic-ity... menu item.

Matching connections are obtained between two patches with same number of grid points along thetwo directions, and when all their points are matching at a specified tolerance. Non matching con-nections are obtained when some patches points are not matching at the specified tolerance, orwhen the number of grid points is not the same in one or both directions.

Current patch

Current patch info

Symbolic face representation

patch limits

Clicking on the border allowsto change the patch limits

Clicking the right mouse buttonpulls down a menu for deleting or dividing the patch:

Edit Patch area

Close Edit Patch area


AutoGrid5™ 2-29

A periodic connection between two patches (PER or PERNM) is equivalent to a simple connection,after application of the periodicity of the block to one of the patch.

The following checks are performed by AutoGrid™ when trying to connect two patches:

• Four patch corners must be matching at the given tolerance ("patch corner" means thepatch grid point at the corner of the patch).

• Four patch boundaries must be matching at the given tolerance ("patch boundaries" meanscurves passing through the patch grid points defining the patch limits).

• Patch points must lie on a same common surface. For this, some points of the first patch areprojected on the surfacic cells of the second patch. An intersection must be found and thedistance between the point and its projection must be lower than an internally calculatedvalue based on the given tolerance and the patch dimension.

• All the patch points must be matching at the given tolerance. Obviously, when number ofgrid points is different in one or both directions, this test is never satisfied.

The three first tests are performed for both matching and non matching connections and determineif a connection is possible between the two considered patches. The last test determines if the con-nection is matching or non-matching. The relative orientation of the two patches is automaticallyfound after the three first tests and is assigned to the connection.

Three interactors are provided with the automatic connectivity search: one field to input the abso-lute tolerance used to compare point coordinates, another one to delete all connections currently set(CON, NMB, PER, PERNM types) and one to start the search.

FIGURE 2.3.4-4 Automatic connectivity search interactors

To make a new automatic connectivity search on all the patches, left-click on the Delete All buttonto delete all connections currently set. To delete only some connections, select the correspondingpatches and set the patch type to UND by using the related button.

Before starting the automatic search, the tolerance must be adjusted. It is specified in absolute unitsin the Tol input field. For example, if the mesh coordinates range from 0 to 1, a possible value is 1e-5, whereas if the mesh coordinates range from 0 to 10000, a value of 1e-3 is more appropriate. Thedefault value that is set at the dialog box opening is 1e-5.

� It is highly recommended to avoid setting a tolerance close to the patch size, other-wise connection can be wrongly found. For example, having two square patches of size 1and distant of 2, a tolerance of 3 will connect them whereas they should remain discon-nected.

The search can be started by clicking on the Search button. At the end of the operation, the numberof simple connections found as well as the number of periodic connections are displayed in theinformation area. The "Type" filter is automatically set to CON and the corresponding patches arelisted in the Patch browser.

� It is advised to do this search operation after all the blocks have been properly definedand are ready to be used by the solver.


2-30 AutoGrid5™

f) Manual Connectivity Settings

When automatic connectivity search fails, the manual connectivity option can be activated bypressing the Manual... button. Within this option, the relative orientation of the two selected patchesmust be entered manually and checks are performed according to the connection type selected todetect if the connection is possible or not.

This option opens a dialog box shown below:

FIGURE 2.3.4-5 Manual Connectivity dialog box

Firstly, specify the indices of the patch that will be connected to the current patch and the connec-tion type. Patch indices are defined as follows: Block, Face and Patch index. Enter them with thekeyboard and validate them by pressing <Enter>.

Secondly, the correct relative orientation of the two patches must be chosen. To define this, a refer-ence patch is needed, which is always in this case the current patch selected in the "Patch browser".In general, with a couple of patches, by taking either the first or the second one as reference, the rel-ative orientation will be different.

In fact, for each patch, two axis can be defined, which are equal in direction and orientation to thoseof the block to which it belongs. So, there are three possibilities: I, J or K. To connect two patches,their relative orientation must be determined by specifying the correspondence between their axis.It is done by assigning an expression (such as "Ilow", "Khigh") for each axis. (expression = dir 1 forfirst axis and expression = dir 2 for second one). Dir 1 and dir 2 are determined as follows:

1. Take the first axis of the reference patch.

2. Search the axis of the connected patch which has the same direction, that is to say X (where Xis I, J or K).

3. If the two axis have the same orientation, dir 1 = "Xhigh", else dir 1 = "Xlow".

4. Do the same with the second axis of the reference patch to determine dir 2.

The first axis of the reference patch has to be chosen as follows:

— axis (I, J) -> I

— axis (J, K) -> J

— axis (I, K) -> I

Example:

Connection type

Relative orientationof the patches

Connected patch


AutoGrid5™ 2-31

Reference patch: Patch 1 - Patch 1 first axis: I - Dir 1: Klow - Dir 2: Ihigh

Indeed, it can be seen that Patch 1 axis I increasing corresponds to Patch 2 axis K decreasing, whilePatch 1 axis J increasing corresponds to Patch 2 axis I increasing. The correct relative orientationspecification should consequently be: "Klow", "Ihigh".

After pressing "Apply", AutoGrid5™ checks whether the connection is possible or not. A warningappears if the connection cannot be set.

g) Full Non Matching Connections

This type of connection allows to connect several patches of several blocks with non matchingboundaries. The definition of such connection consists of the following:

• A connection name.

• A list of “left” patches defining one side of the connection.

• A list of “right” patches defining the other side of the connection.

The patches in one list are not restricted to belong to the same face or same block.

� It is to be noticed that full non matching connections are always defined on top of exist-ing patches and that these ones must have a valid basic type (no undefined type (UND)),even if the patch is entirely contained in the connection region. In the case a patch has anundefined type (UND) and is used in the definition of the FNMB (full non matchingboundary), AutoGrid™ automatically sets its type to solid (SOL). This is required by thesolver to run properly. However, the type is not reset to UND when deleting a FNMBconnection, even if the SOL type has been set automatically by AutoGrid™.

Following rules must be respected when performing FNMB connections:

1. A patch can be contained in only one list (either the left patches list or the right one) andone type of FNMB connection (fluid-solid or solid-solid). Patch contained in two FNMBconnections

2. For periodic FNMB connections, all the patches defining the connection must have thesame periodicity information.

FIGURE 2.3.4-6 Full Non Matching Connections dialog box

To define and edit full non matching connections:

Press the Full Non Matching/Define... button of the Patch Selector dialog box (Grid/BoundaryConditions... menu). It opens the dialog box shown on Figure 2.3.4-6.


2-32 AutoGrid5™

This dialog box contains two patch browsers to define the left and right patches lists. The use of the patchbrowsers and filters is the same as for the Patch Selector dialog box. A list containing the connectionsalready defined is displayed on the right of the dialog box.

To define a FNMB connection:

• Select the patches defining the “left” side. These patches are highlighted in yellow in the graphicsarea.

• Select the patches defining the "right" side. These patches are highlighted in blue.

• Enter a name for the connection.

• Select the Periodic button to define a periodic FNMB connection.

• Select the Repetition number to allow periodic FNMB connection that is not covering the samearea (option compatible with EURANUS starting from FINE™/Turbo 7.1-1). The number of rep-etition has to be set in order to fully cover one side (yellow patch(es) - "left" side list of patch(es))with the other side (blue patch(es) - "right" side list of patch(es)) and its repetition.

• Press on the Create/update button to define the FNMB connection.

• This connection will appear in the connection list.

Once a connection is created, patches can be added and/or removed from it. Simply update patches listsby clicking on them and press the Create/update button.

To compute a FNMB connection:

Once a connection is defined, it is possible to visualize the triangulation of the common region by press-ing the Compute & Show button. This triangulation is not directly used in AutoGrid™ but only serves tovisualize the triangulation that will be used by the solver and to verify that the connection is correctly per-formed. Calling this item is optional in AutoGrid™. This calculation can be performed on the desired gridlevel by selecting it freely in the Grid level computed entry (this parameter is global and not saved inconnections). Moreover several parameters can be controlled by pressing the Options button. It opens anadditional frame:

FIGURE 2.3.4-7 FNMB computing parameters

NOT CORRECT CORRECT


AutoGrid5™ 2-33

The process of the computation involves that one side of the connection is triangulated whereas theother side is projected on it. Default values should normally be used. If the computation fails,parameters can be tuned. These parameters are local to each connection and saved into it, thereforeto be taken into account they must be set before creating the connection or the button Create/updatemust be pressed once a parameter is modified.

ADT algorithm: to use the new projection algorithm based on the use of the Alternating DigitalTrees (ADT). The main advantage of this method is a decrease of the time required by the pro-jection stage.Reverse triangulated side: to reverse the triangulated side which is by default the one contain-ing the greater number of points.Maximum projection distance: when the projection distance of a point is greater than thisvalue, it is rejected.Minimum projection distance: when all the points of a patch (contained in the projected sideof the connection) have a projection distance greater than this value, the patch projection isrejected.Normals smoothing steps: before projection, some smoothing steps are done on the projectionnormals.Edge attraction: after the triangulation process, while projecting the vertices on both the sidesof the FNMB, sometimes the projections end close to some boundary of the triangles, whichimpacts negatively on the robustness of the treatment. The edge attraction tolerance removesthis impact and forces the projected point to belong to the triangle boundaries whenever neces-sary.

To view and/or delete an existing FNMB connection:

• Left-click on the desired connection in the connection list to select it.

• The patches participating in the definition of the connection will be automatically high-lighted in the dialog box as well as in the graphics area. A "*" is also displayed next to thepatch type to indicate that the patch is involved in a FNMB connection. If the computationof the triangulation was performed for this connection, it will also be shown on the screen.

• To list only the patches involved in the desired connection, middle-click on it in the connec-tion list.

• Press the Delete button to delete the selected FNMB connection (the type of the corre-sponding patches is unchanged).

h) Rotor/Stator Connections

This type of connection allows to connect several patches of several blocks with rotor/stator bound-aries. The definition of such connection consists of the following:

• A connection name.

• A list of “left” patches defining one side of the connection.

• A list of “right” patches defining the other side of the connection.

The patches in one list are not restricted to belong to the same face or same block.

� It is to be noticed that such connections are only required to have the information in".cgns" file.


2-34 AutoGrid5™

2-3.4.3 Grid Quality

This item gives access to a tool for performing an analysis of the flow paths quality (if meridionalview active), of the grid quality of the blade-to-blade mesh (if blade-to-blade view active) and onthe final 3D mesh generated (if 3D view active). The following dialog box will appear:

FIGURE 2.3.4-10 Mesh Quality dialog box

This dialog box contains two or three pages, one dedicated to analyse the grid quality on wholeblock cells, and the second to the grid quality at the block boundaries (boundary faces), includingmatching connections with adjacent blocks. The items for both pages are similar and described hereafter. The quality criteria are just slightly different. The last page (FNMB) only available for the 3Dmesh allows to control the mesh quality along the full non matching connections.

The Row list or Block entry allows to choose the row or block in which the quality will be ana-lyzed. It is selected by respectively its name or its number. Each change must be validated by press-ing <Enter> to recompute the quality checking.

• In meridional and blade-to-blade views, if all rows selected (left-click and <Shift>), the meshquality is analyzed on all rows.

Blade-to-Blade View

3D View

MeridionalView


AutoGrid5™ 2-35

• In 3D view, if 0 is entered, the mesh quality is analyzed on all the blocks of the grid. Next to thisentry, the selected block name and the grid points number in each direction are displayed. Bydefault, when opening this dialog box, the active block is selected. If the selected block is not gener-ated or has been modified since the last generation (by moving a vertex, for example), the followingmessage will appear:


� It asks for block regeneration. If the no button is pressed, the quality analysis is not per-formed.

The next entry Butterfly block is a special item dedicated to butterfly topologies allowing to choose thebutterfly block in which the quality will be checked. When the block selected in the first entry is a par-ent block, the second entry is activated, displaying the number of the butterfly block which is analyzed.The range goes from 0 to 6. The number 0 represents the inner block and is therefore always present.The other numbers between 1 and 6 represent the parent face number and thus the associated bufferblocks. If there is no associated buffer, the corresponding number does not appear.

The Quality Criterion frame is used to choose the criterion type which will be used to analyze theblock cells quality. The criterion is chosen through the Type pull-down menu. According to the crite-rion, a preferential direction can be chosen through the second pull-down menu Direction (only forBlock page in 3D view). It is used when the criterion gives different results along different directions(for example 2D criterions applied on surfacic cells). When it is not the case, this menu is deactivated.The following possibilities are available: All, I, J or K. ’All’ is equivalent to the three directions I, J, K.Moreover, a range can be selected for each criterion; each range modification must be validated bypressing <Enter>.

The Visualization control frame is used to select the representation mode of the cells. Cells can be dis-played with markers and/or with a shaded representation (Cells button). Markers are useful to detectcells that cannot be seen with the shaded representation only. Moreover, cells shading can be deacti-vated to greatly improve the speed of representation. In the shaded representation, cells are shaded witha different color according to their quality value. The link between colors and values is established by acolormap which is displayed in the graphics area after the tool selection. The range of the colormap isautomatically updated according to the criterion range. The cells can be displayed as surfaces (in merid-ional, blade-to-blade and 3D views) or volumes (in 3D view) by switching on the corresponding button.

Blade-to-Blade View

3D View


2-36 AutoGrid5™

The Display frame is used to show in the AutoGrid5™ graphics area the cells falling inside thequality criterion range. The Display all cells (All cells) button shows all the bad quality cells of theselected block(s). The Sweep cells scrollers, only available in 3D view, allow to sweep the selectedblock to display cells by constant I,J,K face.

The Show chart button is used to toggle a histogram displaying the result of the quality checking.Left-clicking on a bar displays the corresponding cells in the AutoGrid™ graphics area.

FIGURE 2.3.4-12 Quality analysis histogram

The entry Number of intervals is used to select the number of bars of the histogram. The defaultvalue is 5 and the maximum number is 10. Each new number must be validated by pressing<Enter>.

The More info button is used to toggle a window giving more information about the quality check-ing: minimum and maximum values with their location (and possibly the block number in whichthey are detected if the check is performed on all the blocks in the 3D view).

a) Quality Criterion Definitions (Block Page)

These criteria are dedicated to evaluate the grid quality on whole cells of a block.

• Criterion class

Two classes can be defined according to the type of element on which criterion is applied:

• 2D criterions: application on surfacic cells (quadrilateral cells)

• 3D criterions: application on volumic cells (hexahedral cells)

Obviously, the number of cells falling in the criterion range is always greater for a 2D criterion thanfor the equivalent 3D one because an hexahedral cell contains six quadrilateral cells. This meansthat, for a 2D criterion, the number of cells falling in the range can easily be greater than the blocknumber of points.

On the other hand, as 2D criteria are applied on surfacic cells, they are all direction dependent.

• Criteria definitionFollowing criteria are available:

• Overlap,

• Orthogonality,


AutoGrid5™ 2-37

• Angular Deviation,

• Aspect Ratio,

• Expansion Ratio,

• Cell Width.

Each one is described here below.

Overlap

2D criterion available in meridional view. Range: 0 - 1. Overlap allows to detect overlapping cells(flow paths) in the meridional view when the value is set to 1.

Orthogonality

2D criterion available in blade-to-blade and in 3D views. Range: 0 - 90 degrees. Orthogonality is ameasure of the minimum angle between edges of the element. If angle between two edges is greaterthan 90 degrees, the value taken into account is (180 - real angle).

Angular deviation

3D criterion available in 3D view. Range: 0 - 180 degrees. Angular deviation is a measure of theangular variation between two adjacent cells in I, J and K directions.

FIGURE 2.3.4-13 Angular deviation definition

Aspect ratio

2D criterion available in blade-to-blade and 3D views. Range: 1 - 50,000. If the calculated value isoutside the range, the value is reset to 50,000.3

FIGURE 2.3.4-14 Aspect Ratio definition

a1

a3

a4

b1

b3

b4

b2

xI

a1 a2 a3 a+ + 4+

4-----------------------------------------=

yIb1 b2 b3 b+ + 4+

4-----------------------------------------=

Angular deviation along I-direction xI yI,( )∠=

Cell 1

Cell 2

a2

a b

c

d

xa b+

2------------= y

c d+2

------------=

Aspect Ratiomax x y,( )min x y,( )------------------------=


2-38 AutoGrid5™

Expansion ratio

3D criterion available in meridional, blade-to-blade and 3D views. Range: 1 - 100. Expansion Ratiois a measure of the size variation between two adjacent cells. It is direction dependent. If the calcu-lated value is outside the range, the value is reset to 100. Obviously, this criterion is nonsense ifthere is only one cell in the selected direction.

FIGURE 2.3.4-15 Expansion Ratio definition

Cell width

3D criterion available in 3D view. Range: 0 - 1,000,000. Cell width is the height of the cell meas-ured along I, J and K directions. If the calculated value is outside the range, the value is reset to1,000,000.

b) Quality Criterion Definitions (Boundaries Page)

These criteria are dedicated to evaluate the grid quality at the boundaries of a block (boundaryfaces), including matching connections with adjacent blocks (only CON and PER boundary facesare considered).

Following criteria are available:

• Orthogonality (available in blade-to-blade and 3D views),

• Angular Deviation (available in blade-to-blade and 3D views),

• Expansion Ratio (available in meridional, blade-to-blade and 3D views),

• Cell Width (available in 3D view).

Each one is described here below.

Orthogonality

Range: 0 - 90 degrees. Orthogonality is a measure of the cell angle relatively to the block boundary(face). If angle is greater than 90 degrees, the value taken into account is (180 - real angle).

a2

a1

a3

a4

b1

b3

b4 b2

xa1 a2 a3 a+ +

4+

4-----------------------------------------=

yb1 b2 b3 b+ +

4+

4-----------------------------------------=Expansion Ratio (K)

max x y,( )min x y,( )------------------------=

K


AutoGrid5™ 2-39

FIGURE 2.3.4-16 Orthogonality definition

Angular deviation

Range: 0 - 90 degrees. Angular deviation is a measure of the angular variation between two adja-cent cells, the first one being in the current block and the adjacent one in the matching connectedblock. Obviously, this criterion is nonsense if there is no matching connected block.

FIGURE 2.3.4-17 Angular deviation definition

Expansion ratio

Range: 1 - 100. Expansion Ratio is a measure of the size variation between two adjacent cells, thefirst one being in the current block and the adjacent one in the matching connected block. Obvi-ously, this criterion is nonsense if there is no matching connected block. The definition is the sameas for the Block page (see before).

Cell width

Range: 0 - 1,000. Cell width is the height of the cell measured normally to the block boundary(face). If the calculated value is outside the range, the value is reset to 1,000.

c) Quality Criterion Definitions (FNMB Page)

These criteria are dedicated to evaluate the grid quality across fully non-matching boundary(FNMB) connections.

� FNMB connection must be computed with the fine mesh level before checking the qual-ity.

Following criteria are available:

• Expansion ratio

• Cell Width Ratio

a1

a3

a4

xa1 a2 a3 a+ + 4+

4-----------------------------------------=

Orthogonality x N,( )∠=

a2

N

Block boundary face

a1

a3

a4

b1

b3

b4

b2

xa1 a2 a3 a+ + 4+

4-----------------------------------------=

yb1 b2 b3 b+ + 4+

4-----------------------------------------=

Angular deviation x y,( )∠=

Current block

Connected block

a2


2-40 AutoGrid5™

• Inner Gap

• Relative Inner Gap

Each definition is described here below.

Expansion Ratio

Range: 1 - 100. This computes the expansion ratio perpendicularly and through the FNMB for eachcell involved in the FNMB connection. This criterion is symmetric, which means the result is thesame on the left and right parts of the FNMB.

Cell Width Ratio

Range: 1 - 1000. This computes the difference of cell size between each side of the FNMB. It isavailable for each cell involved in the FNMB connection. It identifies how many cells are con-nected to the cell considered. The criterion takes into account the "wall fraction", which means oneleft cell is connected to only a part of a right cell. Then the ratio will be balanced according to thesize of the connected part. This criterion is not symmetric, which means the result is not the sameon the left and right parts of the FNMB.

Example: One cell (A) on the left, four cells (B, C, D and E) on the right covering exactly the leftcell. The result will be 4 for cell A (because this cell is connected to 4 right cells) and 0.25 for eachright cell, B, C, D or E (because each one is connected to only 0.25 part of the left cell).

Inner Gap

Range: 1 - 1e6. This computes the gap between the left and right side of the FNMB (absolute dis-tance). It is available for each cell involved in the FNMB connection. This criterion is symmetric.

Relative Inner Gap

Range: 1 - 1000. It is exactly the same as the previous criterion except that the result is balancedwith the cell size perpendicular to the FNMB. It enables the user to have a better idea on how theorder of magnitude of the gap is compared to the cell size around FNMB. The cell size taken intoaccount can be either the one of the left or the right side (depending on which side has been donethe FNMB projection) but it does not matter as if the cell size is too different on both sides, theexpansion ratio criterion will be bad.


AutoGrid5™ 2-41

2-3.4.4 Grid Quality Report

A mesh quality report can be displayed with the top menu item Grid/Grid Quality Report. It includes thecharacteristics of the mesh in terms of minimum and maximum of the expansion ratio, the expansion ratioand the angular deviation along spanwise direction (J), the aspect ratio and the cells skewness. These dataare available for the entire mesh or by configurations entity (row, technological effect, bulb).

FIGURE 2.3.4-18 3D grid generation and quality check

Negative cells are detected and indicated on top of the histogram as well as the blocks where there arelocated at the bottom of the histogram. The number of multigrid levels of each entity (row and technologicaleffects) is listed in the Mg. Level column.

If the spanwise angular deviation exceeds 40 degrees, a warning appears at the bottom of the window thatindicates the blocks where the maximum value has been reached.

2-3.4.5 Grid Quality Report (HTML)

The Grid/Grid Quality Report (HTML) menu (not available on Windows) allows to automatically write amesh quality report. When selecting the menu, a window enables to select the images that will be insertedinto the report and provides disk usage necessary for the report and images.


2-42 AutoGrid5™

projectname_main.html

Quality Report

3D Mesh of Whole Machine

projectname_rowname.html

Quality Data

Blade-to-Blade Images

3D Mesh Images

left-click


AutoGrid5™ 2-43

2-3.4.6 Negative Cells

Grid/Negative cells... is used to compute, store the indices and show the cells with a negative vol-ume. The following dialog box is provided to select calculation preferences:

FIGURE 2.3.4-19 Preferences dialog box for Negative cells calculation

Four preferences can be controlled:

• Scope: determines whether the calculation will proceed on the active block or on all blocks.

• Coord Sys: specifies whether calculation should proceed using a left-handed local referenceframe for each cell or a right-handed one.

• Precision: specifies whether to perform calculation in single or double precision.This preference is the most important to control. Indeed, AutoGrid5™ always works in doubleprecision. However some solvers may work in single precision. Consequently, checking nega-tive cells in double precision in AutoGrid5™, with no negative cells as a result, may give nega-tive cells in the solver !

• Coarse Levels: specifies on which multigrid level the calculation should proceed. The All but-ton allows to perform the calculation on all the available uniform multigrid levels at once, "uni-form" meaning that the levels are equal in the three directions I, J and K, for example "0 0 0", "11 1" and "2 2 2". The "Custom" button allows to select a specific multigrid level, like "1 2 2".

The Apply button performs the negative volumes calculation. If the active block is not generated orhas been modified since the last generation (by moving a vertex, for example), the following mes-sage will appear:


The View neg cells button allows to visualize cells with negative volume. The computation of thenegative volumes is performed automatically as a first step. Cells with negative volumes are dis-played in a shaded representation and with markers, which are useful to detect cells that cannot beseen only with the shaded representation.

� Beware that the visualization of negative cells can be memory consuming when a largenumber of cells must be displayed. It is then advised to first check the number of nega-tive cells by pressing the Apply button.

Graphical User Interface Toolbar

2-44 AutoGrid5™

If no cell with negative volume is detected, the message "No negative cells" appears. On the con-trary, if there are cells with negative volumes after the complete search, a message like the follow-ing will appear:

FIGURE 2.3.4-21 Grid contains cells with negative volume

It shows the number of each block containing negative cells and the corresponding number of neg-ative cells.

For butterfly topologies, the calculation is performed on all the butterfly blocks of the correspond-ing parent block. The number of negative cells of each butterfly block is added and displayed in theprevious dialog box by referencing the parent block.

2-3.4.7 Compute All Fnmbs

Grid/Compute All Fnmbs is used to ease the calculation of the full non matching connections bycomputing all full non matching connections defined in the menu Grid/Boundary Conditions atonce on all available grid levels. A window appear when full non matchings are failing on specificgrid level(s).

2-3.4.8 Create Face / Create Block

Grid/Create Face... and Grid/Create Block... are used to respectively create and adapt the meshon a face or in the block. The available features are fully described in the Chapter 9 of the IGG™User Manual.

2-4 ToolbarThe toolbar contains icons and buttons providing fast input/output options (See in the related chap-ters the complete description of the icon functions). These are divided into 6 sections.

FIGURE 2.4.0-1 Top toolbar

Project Management Icons Mesh Generation Buttons

View & Mesh Quality Icons Mesh Control Icons Contextual Icons

User Mode

Toolbar Graphical User Interface

AutoGrid5™ 2-45

2-4.1 User Mode

By clicking on the arrow at the right the user may select the user mode.

The Wizard Mode will give access to a mesh wizard presented in Chapter 4. For most projects theavailable parameters in the Wizard Mode are sufficient. When selecting Expert Mode, the userwill have access to all parameters presented in Chapters 5 to 11. These parameters may be useful insome more complex projects.

2-4.2 Project Management Icons

These icons are related to the most often used options of project management.

2-4.3 Mesh Generation Buttons

These buttons are used to start the mesh generation with different scope of application.

TABLE 1. Project Management icons

Icon Description

Opens an existing project previously created by AutoGrid5™.

See the File/Open Project menu item description on section 2-3.1.1.

Closes the current project and opens a new empty one.

See the File/New Project menu item description on section 2-3.1.2.

Saves the current work in the files of the current project.

See the File/Save Project menu item description on section 2-3.1.3.

TABLE 2. Mesh Generation buttons

Buttons Description

Reset all topology and the grid points number according to the grid level chosen by the user AutoGrid5™.

Generate the flow paths of the selected rows

See the Generate Flow Paths button description on Chapter 6.

Generate the flow paths and the blade to blade mesh of the selected rows.

See the Generate B2B button description on Chapter 7.

Generate the flow paths, the blade to blade mesh and the 3d mesh of the selected rows.

See the Generate 3D button description on Chapter 8.

Graphical User Interface Toolbar

2-46 AutoGrid5™

2-4.4 View & Mesh Quality Management Icons

These icons are related to view management and the mesh quality analysis.

2-4.5 Mesh Control Icons

These icons open dialog boxes use to change the mesh parameters.

TABLE 3. View & Mesh Quality Management icons

Icon Description

Open the Mesh Quality dialog box of AutoGrid5™.

See the Grid/Grid Quality menu item description on section 2-3.4.3.

Open the Grid Quality Check dialog box of AutoGrid5™.

See the Grid/Grid Quality Report menu item description on section 2-3.4.4.

Open the Negative Cells dialog box of AutoGrid5™.

See the Grid/Negative Cells menu item description on section 2-3.4.6.

Open the Patch Selector dialog box of AutoGrid5™.

See the Grid/Boundary Conditions menu item description on section 2-3.4.2.

Select the grid level used by AutoGrid5™ to visualize the mesh.

See the View/Coarse Grid menu item description on section 2-3.3.3.

Open the Sweep Surface dialog box of AutoGrid5™.See the View/Sweep Surface menu item description on section 2-3.3.2.

Act as a toggle and perform a repetition in the blade-to-blade or 3D views based on the settings imposed by the user in the View Repetition dialog box of AutoGrid5™.See the View/Repetition menu item description on section 2-3.3.4.

Visualize or hide the solid model of the machine in the 3D view.

See the View/toggle 3D Solid View menu item description on section 2-3.3.7.

Set the active view in full display mode.

Reset the display mode to multiview.

TABLE 4. Mesh Control icons

Icon Description

Select all the rows of the current project.

Create new control lines in the meridional view.

Open the Row: Flow Path Control dialog box.

Open the dialog box dedicated to the blade to blade topology control.

Toolbar Graphical User Interface

AutoGrid5™ 2-47

2-4.6 Contextual Icons

During an AutoGrid5™ session, the contextual icons are updated according to the active entity (rows,blades, hub/shroud gap, fin, control lines). These icons are used to manage these entities.

2-4.6.1 Row Management Icons

2-4.6.2 Blade Management Icons

Open the Optimization Properties dialog box.

Open the Inlet Bulb Mesh Topology dialog box. Displayed only if AutoGrid5™detects a bulb at inlet (hub reaches R=0).

Open the Outlet Bulb Mesh Topology dialog box. Displayed only if AutoGrid5™detects a bulb at outlet (hub reaches R=0).

Open the Nozzle Mesh Topology dialog box. Displayed only in case of machinewith by-pass

TABLE 5. Row Management icons

Icon Description

Remove the selected row(s) from the project database.

Copy the selected row topology into a buffer.

Replace the selected row(s) topology by the topology stored into the current buffer.

Open the Row Properties dialog box.

Open a file chooser used to select a ".geomTurbo" file which contains the (new) geometry of the row.

Add a new blade to the selected row (s) (splitter blade or tandem blade).

Define a hub gap for the blade(s) of the selected row(s).

Define a shroud gap for the blade(s) of the selected row(s).

TABLE 6. Blade Management icons

Icon Description

Remove the selected blade(s) from the project database.

TABLE 4. Mesh Control icons

Icon Description

Graphical User Interface Quick Access Pad

2-48 AutoGrid5™

2-4.6.3 Shroud & Hub Gap Management Icons

2-5 Quick Access PadThe Quick Access Pad is located in the left part of the GUI. It contains icons and more evolvedoptions providing a fast access to the more used functions of AutoGrid5™. Some of these functionsare only accessible through the Quick Access Pad whereas others are also accessible through themenu bar, so that their description will be referenced to these menus.

The pad is divided into four subpads, each of which can be toggled by a simple mouse left-click:

• Rows Definition subpad

• Geometry Definition subpad

• Mesh Control subpad

• View subpad

All the commands and options accessible with these subpads are described in detail in this section.

Icon Description

Copy the selected blade to blade topology into a buffer.

Replace the selected blade to blade topology by the topology stored into the currentbuffer.

Open a file chooser used to select a ".geomTurbo" file which contains the (new) blade geometry.

Open the Blade Expansion dialog box.

Define a hub gap for the selected blade(s).

Define a shroud gap for the selected blade(s).

TABLE 7. Shroud & Hub Gap Management icons

Icon Description

Remove the selected gap(s) from the project database.

Copy the selected gap(s) topology into a buffer.

Replace the selected gap(s) topology by the topology stored into the currentbuffer.

Open a Gap Properties dialog box.

Quick Access Pad Graphical User Interface

AutoGrid5™ 2-49

The four subpads are composed of pages containing buttons, icons, input areas. The icons performspecific function related to the subpad and the page. Each page can also be toggled by a simplemouse left-click.

FIGURE 2.5.0-1 Quick Access Pad

Rows Definition subpad

to control the machine configuration

Mesh Control subpad

View subpad

Geometry Definition subpad

to define the geometry of hub, shroud,

to control the mesh in meridional and

to control the mesh representation

Grid Parameters area

nozzle and blades

blade-to-blade views


2-50 AutoGrid5™

2-5.1 Rows Definition Subpad

The rows definition subpad is used to control the machine configuration through project manage-ment buttons and a tree. All the turbomachinery entities, rows or technological effects (seal leak-age, cooling holes,...) composing a project are symbolically displayed into the tree.

FIGURE 2.5.1-1 Row definition subpad

a) Project Management Buttons

These buttons are used to select or add entities into the tree.

b) Configuration Tree

The configuration tree is used to navigate through the project configuration, to select and modifythe configuration entities.

TABLE 8. Project Management buttons

Icon Description

Select all the entities of the tree: rows, meridional effects (bleed, seal leakage,...) and 3d effects (cooling holes,...).

Select all the rows of the project.

Add a meridional effect (seal leakage, bleed,...) into the tree ofthe project.

Add a 3d effect (cooling holes,...) into the tree of the project.

Add a row at the outlet of the machine. When the project has a configuration with bypass, the row is added before the nozzle.

Available only if the project has a configuration with bypass. Add a row (arm) on the nozzle.

Available only if the project has a configuration with bypass. Add a row near the outlet of the by-pass.

Available only if the project has a configuration with bypass. Add a row near the outlet of the compressor.

Add a B2B Cut into the tree of the project.


AutoGrid5™ 2-51

FIGURE 2.5.1-2 Configuration Tree

The turbomachinery entities defining a project are:

• The rows containing the blade(s), the upstream and downstream boundaries (inlet & outlet).

• The meridional effects defining seal leakage, bleed... Their domain is axisymmetric and definein the meridional plane (ZR).

• The 3D effects defining cooling holes,... Their domain is define in the XYZ space. These enti-ties are considered as sub-entities of the rows.

• The solid mesh of end walls and/or the blade.

• The basin, cooling channel with pin fins and/or ribs in the blade.

• The cooling holes in the end walls and/or the blade.

The selection of the entities and navigation through the tree is performed using left-click. Multipleselection is allowed. It can be performed by keeping the <Shift> or <Ctrl> button pressed during theselection process.

c) Contextual Popup Menu of Tree Items

The entities of the tree can be managed with the features available through their related quickaccess popup menu. After selection, right-click displays these menus. For quick access, theyappears above the mouse location and allows the user to add, remove or modify the properties of allselected entity.

FIGURE 2.5.1-3 Contextual popup menus

Rows entities

3D Effect

Meridional Effects

Rows menu

Meridional effect menu

3D effect menu

Domain limit menu

Blade menu Default menu


2-52 AutoGrid5™

2-5.2 Geometry Definition Subpad

The geometry definition subpad contains button and interaction area used to define or modify thegeometry of the configuration entities.

FIGURE 2.5.2-1 Geometry definition subpad

The geometry defining the channel and the blades as well as the technological effects can be speci-fied from external CAD files and/or from ".geomTurbo" file (native geometry format).

The Units page allows to change the "units" of the imported geometry in order to impose a scalingfactor and a corresponding tolerance that will ensure correct treatment during the grid generationwhen computing for example the intersection. If not necessary, it is recommended to keep thedefault settings (Scale Factor set to 1)

TABLE 9. Geometry Management buttons

Icon Description

Start the editing tool used to define the axisymmetric lower limit defining the blade channel from the basic meridional curves defined in the geometry file.

Start the editing tool used to define the axisymmetric upperlimit defining the blade channel from the basic meridionalcurves defined in the geometry file.

Start the editing tool used to define the meridional trace of thenozzle. Available only if the project has a configuration withbypass.

Open a dialog box to control the number of control points defin-ing the channel curves used to define the inlet, outlet, rotor-sta-tor and control lines.

Open a dialog box to control the completeness of the geometry as well as validity of the end walls, before starting the mesh generation. It also repairs the curves wherever it is required.

Select and load a geometry file to define or replace the geom-etry of the entities found in the file.

Start the import geometry manager to load external CAD file and define the geometry of the configuration entities. More details in chapter 4.


AutoGrid5™ 2-53

2-5.3 Mesh Control Subpad

The mesh control subpad is divided into three pages containing buttons and interaction areas usedto control the mesh of the active row(s). Left click to open or close the desired page.

FIGURE 2.5.3-1 Mesh control subpad

In this subpad, the number of points used to mesh the selected entities (rows and technologicaleffects) is displayed and continuously updated following the modifications of the mesh generationparameters.

a) Grid Level Page

The buttons and the input area of the grid level page are used to set up a default mesh.Four grid lev-els are available to define the number of points used to mesh the selected row(s). The button ResetDefault Topology (re)set a new default mesh topology according to the geometry configuration andthe chosen grid level. The button Start Row Wizard allows to access the mesh wizard mode in orderto mesh the selected row in few steps by defining few parameters (more details in Chapter 4).

FIGURE 2.5.3-2 Grid level control

The option Streamwise Weights allows to increase the number of points in the streamwise direc-tion respectively at the inlet, on the blade and the outlet (for more details, refer to section 7-2.2).


2-54 AutoGrid5™

b) Row Mesh Control Page

The buttons and input areas of the row mesh control page are used to control all the grid generationparameters of the selected row(s).

FIGURE 2.5.3-3 Row mesh control

Quick access is given for the main parameters defining the flow path number and the cell width andthe spacing between the layer of control (blade to blade layer on which the mesh is optimized andused to interpolate the other layers.

Additional buttons give access to several dialog boxes used to control all the expert grid generationparameters.

c) Active B2B Layer Page

FIGURE 2.5.3-4 Active layer control

The input area of the active B2B layer page, is used to change the flow path on which the mesh iscomputed and displayed in the blade to blade view.

TABLE 10. Mesh Control buttons

Icon Description

Open the flow path control dialog box.

Open the dialog box dedicated to the blade to blade topologycontrol.

Open the optimization properties dialog box.

Create new control lines in the meridional view.


AutoGrid5™ 2-55

2-5.4 View Subpad

When the blade-to-blade view active, the View subpad contains five buttons allowing viewingoperations on the blade to blade grid. The selected rows define the scope of the buttons.

When the 3D view active, the View subpad provides commands and tools that allow viewing oper-ations on the geometry and the grid. In particular, the three first pages provide options permittingthe creation and the visualization of geometry and block groups. The four pages of this subpad aredescribed in the following sections.

2-5.4.1 Geometry Groups Page

Geometry groups are powerful means of classifying geometrical entities by grouping them underthe same name. This tool proves to be essential as soon as the input geometry gets a little compli-cated. Using groups, the user can easily perform selective visualization of parts of interest and focuson the current region being meshed.

The geometry group page allows the creation, the deletion and the visualization of geometrygroups, which can contain curves and/or surfaces. Different groups can contain the same curve(s) orsurface(s).

FIGURE 2.5.4-1 Geometry Groups page

TABLE 11. View buttons

Icon Description

Toggle the vertices of the blade to blade blocks of the selected row(s).

Toggle the fixed points of the blade to blade blocks of the selected row(s).

Toggle the grid points of the blade to blade blocks of the selected row(s).

Toggle the edge of the blade to blade blocks of the selected row(s).

Toggle the face grid of the blade to blade blocks of the selected row(s).

Check button allowing selectivevisualization of items.

Group browser List of curves andsurfaces in the group


2-56 AutoGrid5™

All the existing geometry groups are listed by name in the browser of the page. Each group name ispreceded by two buttons. Left-clicking on the first one toggles the list of curves and surfaces of thecorresponding group in the Quick Access Pad. Left-clicking on the second one toggles the displayof curves and surfaces of the group in the graphics area.

Each item in a group is also preceded with a check button that allows to individually show or hidethe item.

The page contains four buttons at the bottom:

• Create Group. Before pressing this button, curves and surfaces that will be put in the newgroup must be selected (see the Geometry/Select menu in IGG™ User Manual). The followingdialog box will be opened:

Simply enter the new group name and press the Create button to create the new group.

• Delete Group. It opens the following dialog box:

All existing geometry groups are listed in the box. Simply select a group by left-clicking on itsname and press the Delete button to delete it (this will not delete the related geometrical enti-ties).

• Show All. This button shows all the geometry in the graphics area: curves, surfaces and Carte-sian points.

• Hide All. This button hides all the geometry in the graphics area: curves, surfaces and Cartesianpoints.

Two pop-up menus are also accessible by right-clicking on a group name or on a geometry entity inthe page browser:

The first menu contains three items:

• Add Selection. This adds the currently selected curves and surfaces to the group.

• Remove Selection. This removes the currently selected curves and surfaces of the group. Ifsome selected curves or surfaces are not in the group, the removal of these entities will have noeffect on the group.

• Delete. This deletes the geometry group.


AutoGrid5™ 2-57

The second menu allows to remove of the group the geometry entity from which the menu isopened.

2-5.4.2 Block Groups Page

This page allows the creation, deletion and the visualization of block groups. Different groups cancontain the same block(s).

FIGURE 2.5.4-2 Block Groups page

All the existing block groups are listed by name in the browser of the page. Each group name is pre-ceded by two buttons. Left-clicking on the first one toggles the list of blocks of the correspondinggroup in the Quick Access Pad. Left-clicking on the second one toggles the display of blocks of thegroup in the graphics area.

Each item in a group is also preceded with a check button that allows to individually show or hidethe item.

The page contains four buttons at the bottom:

• Create Group. The following dialog box will open:

Simply enter the new group name and press the Create button to select the group blocks. Thefollowing prompt will appear:<1> Select a Block, <2> Add to Group, <3> Quit, <Keyboard Area>: Block Indices

Left-click on a block to select it. The block will be highlighted. Then, middle-click to add theblock to the group. This block will remain highlighted until leaving this tool. Add in the samemanner as many blocks as desired. Blocks can also be added to the group by entering their number in the keyboard input area. Inthis case, the blocks are directly added to the group without being highlighted and without anyvalidation. The numbers must be separated by spaces. A range of blocks can also be added byentering two numbers separated by a ’-’. For example, enter ’1 5 10-15 3’ to add the blocks 1, 3,5 and the range 10->15. The numbers do not have to be ordered and the same number can beentered more than one time. If a syntax error is made, a warning message will appear.

Press <q> or the right mouse button to complete the group creation.

• Delete Group. It opens the following dialog box:

Group browser List of blocks in the group

Check button allowing selectivevisualization of items.


2-58 AutoGrid5™

All existing block groups are listed in the box. Simply select a group by left-clicking on itsname and press the Delete button to delete it (this will not delete the related blocks).

• Show All. This button shows all the blocks in the graphics area.

• Hide All. This button hides all the blocks in the graphics area.

Two pop-up menus are also accessible by right-clicking on a group name or on a block in the pagebrowser:

The first menu contains three items:

• Add Selection. This adds the active block to the group.

• Remove Selection. This removes the active block of the group. If it is not in the group, thisoperation will have no effect on the group.

• Delete. This deletes the block group.

The second menu allows to remove of the group the block from which the menu is opened.

2-5.4.3 Grid Configuration Page

When creating a mesh with AutoGrid5™, the multiblock data structure can becomes very complex.A new database, named Grid Configuration, is created by AutoGrid5™ at the end of the mesh gen-eration, saved together with the project into a file ".config". When loading the mesh in IGG™,AutoGrid5™ or in FINE™ GUI, the grid configuration is also loaded.

The grid configuration describes the mesh structure of the project as a set of fluid and solid domainsinterconnected together through domain interfaces. Each domain contains a set of subdomains anda set of interfaces. Each domain interface contains a type of boundary condition, a type of freeboundary condition and the possible connected domain reference. The domain encapsulates the listof structured blocks defining the domain. The domain interface encapsulated the list of structuredpatches defining the interface.

This new data structure is very useful. It can be used to reduce the time needed to analyse the meshof a project, to set up the boundary conditions into FINE™ GUI and to easily visualize the mesh.

AutoGrid5™ computes automatically the grid configuration of the meshed turbomachine after each3D generation as well as after loading or saving a project. This configuration is composed by a treeof domains similar to the configuration tree used to set the template configuration. The Main


AutoGrid5™ 2-59

Project of an AutoGrid5™ configuration contains a single subdomain named "AG5 <projectname>" where project name is the name of the template. The AutoGrid5™ domain contains the listof subdomain related to each row and each technological effect 3D.

When navigating through the configuration, the boundary edges of the selected domain and the gridof the selected interface are automatically displayed and updated in the XYZ view. This behaviourcan be switched off using the buttons Highlight Domain and Highlight Boundaries on the bottomof the Grid Configuration page.

Selecting one or several item of the configuration and using right-click gives access to all the man-agement options through contextual menus dedicated to each type of configuration item.

a) Main Project Management

a.1) Duplicate Main Project

The menu option Duplicate is used to create an new instance of the Main Project into the configu-ration. This new instance is called a SubProject and is a perfect copy of the main project configura-tion.

Right-Click


2-60 AutoGrid5™

a.2) Merge Main Project

The option Merge can be used to merge together subprojects with the main project. A new instanceof the Main Project is created and if mesh and template files exist on disk for the selected sub-project, new mesh and template files are created for the new merged subproject resulting of the con-catenation of the main project mesh and template files with the subproject mesh and template files.

b) SubProject Management

Subprojects are useful when part of the main configuration must be analysed separately. In additionAutoGrid5™ allows also to redefine geometry in a subproject through template manipulation andremeshing partially the machine. Each subproject can have its own mesh and template inside whichthe user can modify locally some part of the geometry (i.e. a blade definition). Once the computa-tion is fruitful on the subproject a merge process allow the user to concatenate the main project withthe selected subproject to analyse the complete configuration with the new geometry defined in thesubproject.

b.1) Rename SubProject

This option can be used to rename the subproject. A entry prompts the user to enter a new name.Blank and special characters are allowed excepted tabulation. The system warns the user if thename is already used.

Right-Click


AutoGrid5™ 2-61

When a new subproject name is accepted, the subproject files and directory are also renamed.Therefore it is strongly recommended to save also the main project (File/Save Project menu) afterrenaming process to keep consistency between the main project configuration stored on disk andthe name of the subproject files.

b.2) Duplicate SubProject

The menu option Duplicate is used to create an new instance of the SubProject into the configura-tion.

b.3) Save SubProject

The menu item Save is used to save the mesh and the template of the selected subproject. Bydefault, when a subproject is created from the main project, the mesh and the template files are notduplicated. Once the subproject edition done, the option Save creates a new directory <main-project-file-name>_<subproject-name>. The partial mesh and template related to the subproject areautomatically created and stored in this directory.

All the structured patches boundary condition type of the mesh belonging to a domain interfaceconnected to a subdomain removed in the subproject are switched to the free boundary conditiondefine in the interface properties. In the below example, the patch type of the RS Connection Withrow 1 are switched to Inlet when saving the subproject mesh.

When saving the subproject, AutoGrid5™ asks if the main project mesh and template must remainthe active one. If not, the created subproject file or template are automatically loaded replacing themain project.

b.4) Load SubProject

The menu Load can be used to load the mesh (and the template) of a subproject if the file exists ondisk. If not a warning prompts the user to first save the subproject.


2-62 AutoGrid5™

b.5) Merge SubProject

The menu Merge can be used to merge together subprojects and/or with the main project. The fig-ure illustrates the process to merge together the subproject 1 & subproject 2 into a subproject 3.

This operation can takes some time because of the following steps needed to keep consistency:

• An new subproject is created in the configuration as the result of the merging process betweenthe selected subproject,

• The main project is saved (needed to keep consistency),

• The main project is duplicated and saved into the new subproject directory,

• The mesh and template of the selected subproject are loaded to replace partially the data into theduplicated main project,

• The domains which does not appear in the new subproject are removed from the mesh and thetemplate,

• The final subproject is saved on disk.

At the end of the merging process the subproject 3 remains loaded. To retrieve the original interfacestatus, the user must load again the main project (File/ Open Project).

b.6) Delete SubProject

The menu Delete can be used to delete the mesh (and the template) of a subproject if the file existson disk.

c) Domain Management

Each domain edges are automatically highlighted in red in the XYZ view when selected (click-left)in the configuration.


AutoGrid5™ 2-63

Each row domain contains a list of subdomains which depends of the option chosen by the user during theturbomachinery configuration setup. In the example, each row contains only a subdomain correspondingto the Main Blade definition. For each domain, a folder named Domain Boundaries contains the interfaceof the domain. Right-clicking on a domain gives access to the domain menu.

� Each subdomain contains a list of IGG™ blocks. When dealing with butterfly topology createdin IGG™ or as 3D technological effect in AutoGrid5™, the button Update assumes that all theblocks are now included in the grid configuration except the parent blocks. This is a suitablebehaviour for the usage of the grid configuration in the FINE™ GUI.

c.1) Domain Properties

The menu Properties opens the dialog box use to control the type and the rotation speed of the domain.

Each modification will affect all the blocks linked to the domain. The type Fluid-Solid means that thedomain contains subdomains of different type.

In the example, the Main Blade subdomain contains the core flow domain around the blade (fluid), theshroud gap domain (Fluid) and the solid body of the blade (Solid). Therefore the type of the domain MainBlade is set to the hybrid type Fluid-Solid.

c.2) Rename Domain

The menu Rename can be used to rename a domain.

c.3) Group Domain

The menu Group can be used to group the domain together. The resulting domain contains a list of sub-domains equal to the selected list. This menu is available only in the grid configuration within IGG™.

Right-Click


2-64 AutoGrid5™

c.4) Delete Domain

The menu Delete can be used to remove the selected domain from the related main project and/orfrom the related subprojects.

d) Domain Interface Management

Each domain of the main project or a subproject contains domain interfaces defining the physicalboundaries of the configuration and the connections between the domains. These interfaces arestored in the Domain Boundaries folder of the domain. If the button Highlight Boundaries ischecked, the selected domain interfaces are automatically displayed using grid and color shadingrepresentations as presented in the below figure.

In addition, the main project and the subprojects include also a Domain Boundaries folder contain-ing the full list of the project domain interfaces. For more visibility, the list has been divided intoseveral subfolder according to the boundary condition type of each interface: inlet, outlet, solid,external, rotor-stator, connection(Fluid->Fluid), connection(Solid->Solid), connection(Fluid->Solid), connection(Solid->Fluid).

Each subfolder contains a list of interfaces and/or subfolders. The interfaces are given by their fullcomposite name. The composite name is composed by the name of the tree entity and all its parentsseparated by a character "/". The subfolders (i.e. row 1 Connection(Fluid->Fluid)) contain a list ofinterfaces. These subfolders represent interfaces groups and are defined for quick access. These


AutoGrid5™ 2-65

groups are defined automatically by AutoGrid5™ or manually using the features dedicated to thedomain boundary management. These features are available through the right-click menu of thedomain boundaries.

d.1) Domain Boundary Properties

The menu Properties opens a dialog box dedicated to the management of the interfaces properties.

In the dialog box, the rotation speed, the name, the type of the boundary in the main project(Boundary Condition Type) and in the subproject (Free Boundary Condition Type) are availa-ble.

In a subproject, some domains can be removed by the user. When saving the grid of a subproject, allthe boundary condition type of the domain boundaries connected to the removed domains are set tothe free boundary condition type.

In addition, when the interface selected is a rotor-stator, the side (upstream or downstream) of theinterface can be setup (Rotor/Stator Side).

d.2) Rename Domain Boundary

The menu Rename can be used to rename a domain boundary.

d.3) Group Domain Boundaries

The menu Group can be used to group together domain boundaries of the same type within IGG™.As the groups are stored in the main project or the subproject boundaries, the menu item groupappears only when at least two boundaries of the same type of a subproject or the main project areselected.

By default the name of the group is composed by the "type name" + "group id" (i.e. Solid 1). A newsubfolder is automatically displayed in the tree and contains all the selected boundaries.


2-66 AutoGrid5™

d.4) Ungroup Domain Boundaries

The menu Ungroup is used to ungroup existing group or domain boundaries within IGG™.Ungroup a group of domain boundaries results in removing the initial group.

Ungroup an existing domain boundary split it into a list of new domain boundaries. The number ofnew boundaries is equal to the number of grid patches defined in the selected domain boundaries.The name of the new domain boundaries is equal to B <block-id> F <face-id> P <patch-id>.

d.5) Connect Domain Boundaries

Three types of interfaces between domains of a grid configuration are available:

• Interface with no connection with other domain (i.e: hub,shroud,…),


AutoGrid5™ 2-67

• Interface connected with another domain: connection (Connect), full non matching connection (Con-nect As FNMB) and rotor/stator connection (Connect As Rotor/Stator),

• Internal domain full non matching connections.

If the mesh (including patch connection and full non matching definition) is completed, the connectedboundaries between domains are automatically defined by AutoGrid5™ or by IGG™ when using the but-ton Update of the grid configuration page.

In some circumstances, the complete mesh of a project results of a concatenation of submeshes created inseparate session of IGG™ and/or AutoGrid5™. During this mesh concatenation within IGG™, the gridconfiguration is also concatenate. The menu Connect, Connect As FNMB and Connect As Rotor/Statorare used to establish the connection between the different concatenated configuration.

The below example illustrates the concatenation between two meshes created in separate IGG™ sessionconnected through one domain boundary:

1. Two meshes are created separately and stored into the mesh files "mesh1-fluid.igg" and "mesh2-fluid.igg". Both meshes have an inlet and an outlet. The inlet of mesh2 is equal to the outlet of mesh 1.Both meshes have similar grid configuration.

2. A new IGG™ project is initialized and is composed by both meshes imported into this new project.

mesh1-fluid.igg mesh2-fluid.igg


2-68 AutoGrid5™

3. The Outlet 1 and Inlet 2 are selected than connected together using the menu Connect.

The same above steps can be repeated to connect with a full non matching connection. In this case,a new full non matching connection is created automatically using the mesh patches of the selectedboundaries. Finally, a rotor/stator connection between two imported domains can also be estab-lished in such way.

d.6) Interface Viewer

The menu Interface Viewer opens a dialog box dedicated to the domain interface visualization. Itallows to select the display of the grid and/or a solid representation of the selected interfaces.

d.7) Export Surfaces

The menu Export Surfaces is used to export a IGG™ data file format of the surfaces created asnew wireframe of each patches defining the interface. The file name is defined automatically usingas prefix the name of the configuration file (".config" file) and the name the interface.

2-5.4.4 Grid Page

This page provides visualization commands on the grid. It consists of two rows: a row of buttonsand a row of icons.

The first row of buttons is used to determine the viewing scope, that is the grid scope on which theviewing commands provided by the icons of the second row will apply. There are five modes deter-mining the scope, each one being represented by a button: Segment, Edge, Face, Block, Grid (allblocks). Only one mode is active at a time and the current mode is highlighted. Simply left-click ona button to select the desired mode.

Control Area Graphical User Interface

AutoGrid5™ 2-69

• In Segment mode, a viewing operation applies to the active segment only.

• In Edge mode, a viewing operation applies to the active edge only.

• In Face mode, a viewing operation applies to the active face only.

• In Block mode, a viewing operation applies to the active block only.

• In Grid mode, a viewing operation applies to all the blocks of the grid.The icons of the second row and their related commands are listed in the following table:

� When the Grid configuration page is opened, the viewing button related to the gridtopology acts on the selected configuration item. The user is now able to draw the gridedges row by row.

2-6 Control AreaThe control area is composed of seven major areas:

• Message area

• Keyboard input area

• Mouse coordinates

• Information area

• Grid parameters area

• Generation Status area

• Viewing buttons

Each one is described in the following sections.

TABLE 12. View buttons

Icon Description

Toggles vertices

Toggles fixed points

Toggles segment grid points

Toggles edges

Toggles face grid

Toggles shading

Graphical User Interface Control Area

2-70 AutoGrid5™

2-6.1 Message Area

This area has several display functions:

— Display of warning messages notifying the user

— Display of request messages asking the user for inputs from Keyboard input area orGraphics area

— Display of general information messages (current function options,...)

2-6.2 Keyboard Input Area

To mesh 3D technological effects, AutoGrid5™ gives access to the structured multiblock grid gen-eration module IGG™. Some of the options in IGG™ require numerical inputs from the user. Forexample, rotating a curve around a given line requires to specify the direction of the line, its originand the rotation angle.

The keyboard input area is provided to allow such inputs. When an option requires numericalinputs, a message is indicated in the Message area. Without leaving the graphics area, the user canthen type the required data. The keystrokes are automatically echoed in the keyboard input area andthe user has the possibility to modify the inputs. The input is acknowledged after pressing <Enter>.

Entering scalar values: a scalar value is specified by a floating number followed by <Enter>.Valid values are 5 1.32323 -0.1234 1.4E-5.

Entering vectors: a vector is specified by typing its three components separated by a blank and fol-lowed by <Enter>.

The Keyboard input area can also be used to select the active block, face, edge or segment. Sim-ply enter the related indices separated by blanks and press <Enter> to make the correspondingentity active. This obviously causes the update of the Grid parameters area.

2-6.3 Mouse Coordinates

This area displays the mouse cursor coordinates in the Graphics area. If the cursor is out of it, itindicates the last cursor position in it.

2-6.4 Information Area

This area gives general informations (about edges, curves,...). For example, when moving a vertexand attracting it to a curve, the name of that curve is displayed in this area.

2-6.5 Grid Parameters Area

Active block, face, edge and segment indices

Number of blocks, faces, edges and segmentsfor the active topology


AutoGrid5™ 2-71

This area shows very useful informations about the grid:

• Active Block, Face, Edge and Segment indices

• Number of grid blocks, active block faces, active face edges, active edge segments

• Block:

— Number of active block points

— Number of grid points

— Name of the block

— Number of points in each block direction

• Face: constant direction and the corresponding index

• Edge: constant direction according to the active face and the corresponding index

• Segment: number of points on the segment

• The maximum multigrid level available in the I, J and K direction

If the name of the active block is "invalid", it means that any block has been created yet or all theblocks have been deleted.

2-6.6 Generation Status Area

During grid generation process, the status of each steps is displayed in this area. In addition twopop-up windows are also displayed to control the iteration process of the optimization steps and theprogress status of all the other generation steps. These two windows are optional and can be deacti-vated by toggle the button Show this next time.

FIGURE 2.6.6-1 Progress status & Optimization status windows

Graphical User Interface Control Area

2-72 AutoGrid5™

2-6.7 Viewing Buttons

The Viewing buttons are used to perform viewing manipulations on the active view, such as scroll-ing, zooming and rotating. The manipulations use the left, middle and right buttons of the mouse indifferent ways. The sub-sections below describe the function associated with each mouse button foreach viewing button.

� For systems that only accept a mouse with two buttons, the middle mouse button can beemulated for viewing options by holding the <Ctrl> key with the left mouse button.

� During viewing operations, AutoGrid™ automatically removes from the active view all‘heavy’ graphics representations such as solid model or color shading. This is done tokeep a reasonable speed during rotation, translation or zoom operations. The completepicture is restored after a viewing operation is finished. A ‘full visibility’ can be explic-itly requested during viewing operations by calling the Autogrid Preferences dialog boxand setting the visibility flag to Full in the Graphics page.

� Viewing manipulations can be done while another action is already undertaken (forexample, a vertex displacement). That action is temporarily stopped until the viewingoperation is finished; then, the action can be performed just like before the viewing. Thisis useful when operations have to be executed in very distant areas of the model.

2-6.7.1 X, Y & Z Projection Buttons

These buttons allow to view the graphics objects on X, Y or Z projection plane.

• Left : press this mouse button to project the view on an X, Y or Z constant plane. If the samebutton is pressed more than one time, the horizontal axis sense changes at each press.

2-6.7.2 Coordinate Axis

The coordinate axis button acts as a toggle to display different types of coordinate axis on the activeview using the following mouse buttons:

• Left : press to turn on/off the display of symbolic coordinate axis at the lower right corner ofthe view.

• Middle : press to turn on/off the display of scaled coordinate axis for the active view. The axissurrounds all objects in the view and may not be visible when the view is zoomed in.

• Right : press to turn on/off the display of IJK axis at the origin of the active block (in BlockViewing Scope) or of all the blocks (in Grid Viewing Scope). (For more information about theviewing scope, see the View/Grid page of the Quick Access Pad).

2-6.7.3 Scrolling

This button is used to translate the contents of active view within the plane of graphics window inthe direction specified by the user. Following functions can be performed with the mouse buttons:

• Left: press and drag the left mouse button to indicate the translation direction. The translation isproportional to the mouse displacement. Release the button when finished. The translation magnitude is automatically calculated by measuring the distance between theinitial clicked point and the current position of the cursor.

• Middle : press and drag the middle mouse button to indicate the translation direction. The trans-lation is continuous in the indicated direction. Release the button when finished. The translation speed is automatically calculated by measuring the distance between the initialclicked point and the current position of the cursor.


AutoGrid5™ 2-73

2-6.7.4 3D Viewing Button

This button allows to perform viewing operations directly in the graphics area. Allowed operationsare 3D rotation, scrolling and zooming.

After having selected the option, move the mouse to the active view, then:

• Press and drag the left mouse button to perform a 3D rotation

• Press and drag the middle mouse button to perform a translation

• Press and drag the middle mouse button, while holding the <Shift> key, to perform a zoom

• To select the centre of rotation, hold the <Shift> key and press the left mouse button on a geom-etry curve, a vertex or a surface (even if this one is visualized with a wireframe model). Thecentre of rotation is always located in the center of the screen. So, when changing it, the modelis moved according to its new value.

� This 3D viewing tool is also accessible with the <F1> key.

2-6.7.5 Rotate Around X, Y or Z axis

The rotation buttons are used to rotate graphical objects on the active view around the X, Y or Zaxis. The rotations are always performed around the centre of the active view. Following functionscan be performed with the mouse buttons:

• Left : press and drag the left mouse button to the left or to the right. A clockwise or counter-clockwise rotation will be performed, proportional to the mouse displacement. Release the but-ton when finished.

• Middle : press and drag the middle mouse button to the left or to the right. A continuous rota-tion will be performed, clockwise or counterclockwise. Release the button when finished.

2-6.7.6 Zoom In/Out

This button is used for zooming operations on the active view. Zooming is always performedaround the centre of the view. Following functions can be performed with the mouse buttons:

• Left : press and drag the left mouse button to the left or to the right. A zoom in - zoom out willbe performed, proportional to the mouse displacement. Release the button when finished.

• Middle : press and drag the middle mouse button to the left or to the right. A continuous zoomin - zoom out will be performed. Release the button when finished.

2-6.7.7 Region Zoom

This button allows to specify a rectangular area of the active view that will be fitted to the viewdimensions. After having selected the button,

• Move the mouse to the active view

• Press and drag the left mouse button to select the rectangular region

• Release the button to perform the zoom operationThese operations can be repeated several times to perform more zooming.

• Press <q> or the right mouse button to quit the option.

� This tool is also accessible with the <F2> key.

Graphical User Interface Graphics Area & Views

2-74 AutoGrid5™

2-6.7.8 Fit Button

The fit button is used to fit the content of the view to the view limits without changing the currentorientation of the camera (which can be interpreted as the user’s eyes).

2-6.7.9 Original Button

The original button is used to fit the content of the view and to give a default orientation to the cam-era.

2-6.7.10 Cutting Plane

This option displays a movable plane that cuts the geometry and the blocks of the mesh. The planeis symbolically represented by four boundaries and its normal, and is by default semi-transparent.After having selected the button,

• Press and drag the left mouse button to rotate the plane

• Press and drag the middle mouse button to translate the plane

• Press <x>, <y> or <z> to align the plane normal along the X, Y or Z axis

• Press <n> to revert the plane normal

• Press <t> to toggle the transparency of the plane (to make it semi-transparent or fully transpar-ent). It is highly advised to deactivate the plane transparency when using X11 driver to increasethe execution speed.

2-7 Graphics Area & ViewsThe graphics area is the region of the screen dedicated to the display of all graphical objects createdby the system. These graphical objects may be distributed in different windows called ’views’ inthe AutoGrid5™ terminology.

FIGURE 2.7.0-1 Graphics area

Graphics Area & Views Graphical User Interface

AutoGrid5™ 2-75

Four views are displayed simultaneously in the graphics area:

• The symbolic view.

• The meridional view.

• The blade to blade view.

• The 3D View

Although four views can be visible at a time, only one can be active. This view is identified by a red bor-der and is called the ’active view’. The active view can be changed with the left mouse button. Right-clickinto a view gives access to contextual menu which always contains the two items dedicated to the viewmanagement

Selecting the Full View item display the active view on the entire graphics area. To return to the multiviewenvironment, right click on the item MultiView.

Full View can also be accessed by double left-clicking in the view. MultiView mode can be retrieved bypressing <Esc>.

2-7.1 Symbolic View

The symbolic view displays a theoretical scheme of the turbomachinery row(s). Each entities (rows,blades, shroud & hub gaps) can be select using left click.

FIGURE 2.7.1-1 Symbolic view

2-7.2 Meridional View

The meridional view displays the entities of the machine projected in (z,r) coordinates. This view ismainly used to create and control the flow paths in each row.

FIGURE 2.7.2-1 Meridional view

View management items

Graphical User Interface Graphics Area & Views

2-76 AutoGrid5™

2-7.3 Blade to Blade View

The blade to blade view displays one blade to blade layer of the mesh in (dm/r,theta) coordinates.The m coordinates is the curvilinear arc length along the active layer (flow path). The angles (cellskewness) and the distances (expansion ratio and boundary cell width) are kept by the conformalmapping (x,y,z->dm/r,theta).

The blade to blade view is mainly used to control blade to blade generation of the mesh.

FIGURE 2.7.3-1 Blade to blade view

2-7.4 3D View

The 3D view is used to display the solid body of the geometry and the 3D generated mesh, to checkthe mesh quality.

FIGURE 2.7.4-1 3D view of solid body

File Chooser Graphical User Interface

AutoGrid5™ 2-77

2-7.5 View & User Interaction

The graphical object displayed in the symbolic, meridional and blade to blade view are related toentities of the configuration tree (row, blade, domain limit, shroud & hub gap). Object under themouse are automatically highlighted in yellow indicating that their selection can be operated byleft-click. Right-click displays contextual menus related to the underlying object. To unselect allobjects, left-click on a empty location.

2-8 File ChooserFor file management (opening and saving of files) AutoGrid5™ uses the standard file chooser win-dow. The layout of the file chooser depends on the used operating system but a typical layout isshown in Figure 2.8.0-1. The directories and files list allows to browsing through the availabledirectory structure to the project directory.

In the case a file needs to be opened an existing file should be selected in the list of available files.In the case a new file needs to be created the user can type a new file name with the appropriateextension.

In the Files of type bar the default file type is set by default to list only the files of the required type.

FIGURE 2.8.0-1 Typical layout of a file chooser

Graphical User Interface File Chooser

2-78 AutoGrid5™

AutoGrid5™ 3-1

CHAPTER 3: Meshing Fundamentals

3-1 OverviewAutoGrid5™ has been developed to ensure a quick management of the grid generation process ofturbomachinery configurations. The software is able to take into account the most used componentsof a turbomachinery. These components are divided into five types:

• the blade rows

• the meridional technological effects (seal leakage, bleed,...)

• the 3d technological effects (volute, cooling holes,...)

• the solid mesh

• the cooling holes, cooling channel and basin

The software provides a highly interactive user interface and a mesh wizard (Chapter 4) allowing aneasy setup of the mesh generation process for complex geometries. Based on a template approach, itensures reusability of the interactive work on similar geometries through the full batch mode capa-bility.

The application field of AutoGrid5™ covers all the turbomachinery types:

• axial and centrifugal machine

• multistage machine

• turbine, compressor

• multi-splitters

• tandem rows

• return channel

• inducer

• airplane engine compressor stages with fan and by-pass

Meshing Fundamentals Mesh Domain Definition

3-2 AutoGrid5™

3-2 Mesh Domain DefinitionA turbomachinery configuration domain is defined by the space located between the hub, theshroud and the blades of the machine. Additional domains can be added to the configuration tomesh technological effects (bleed, seal leakage, cooling holes)

FIGURE 3.2.0-1 Turbomachinery domain

3-2.1 Hub & Shroud Definition

The hub & shroud are defined by their meridional trace (ZR coordinates). They define the spanwiseboundaries of the domain. The 3D blade to blade domain is meshed on surface of revolution located

Hub definition

Shroud definition

Blade definition

Technological Effect

Blade channel

Inlet Outlet

x

yz

Mesh Domain Definition Meshing Fundamentals

AutoGrid5™ 3-3

between the hub and the shroud definition. The geometry of the hub and the shroud are definedusing curves in (x,y,z), (r,theta,z) or (r,z).

3-2.2 Blade Definition

The blades are defined (x,y,z coordinates) by several surfaces and two curves defining their leadingand trailing edge locations. During the mesh generation the blades surfaces are intersected by sur-faces of revolutions defined from the hub to the shroud.

3-2.3 Inlet & Outlet Limits

The inlet and outlet limits of the domain are by default automatically defined by AutoGrid5™ usingtwo straight lines joining the limits of the hub and shroud definitions. The shape and the location ofthe inlet and outlet boundaries can be interactively modified in the meridional view. In case ofmultistage configuration (multiple rows), the location of the rotor/stator mixing plane is also auto-matically defined by AutoGrid5™. Their default location are set at the average streamwise locationbetween the upstream trailing edge and the downstream leading edge. Furthermore, the shape andthe location of the rotor/stator can be interactively modified in the meridional view.

3-2.4 Technological Effects

The technological effects are divided in two types: the meridional and the 3d effects. They defineadditional domains stuck to the main channel domain.

3-2.4.1 Meridional Technological Effects

The seal leakages, the cavities and the bleed belong to the meridional effect types. The meridionaleffect is axisymmetric and its geometry is defined by meridional curves (z,r coordinates). Thedomain of a meridional effect must always be connected to one or more blade row(s).

The mesh of these configuration entities are generated in 3 steps:

• manual blocking in the meridional space

• automatic settings of the number of grid points and the clustering in the meridional space

• 3D mesh generation obtained by the combination of the meridional blocking and the mesh at theconnection(s) with the blade row(s).

More details are presented in Chapter 9 and in dedicated tutorial.

3-2.4.2 3D Technological Effects

The draft tube, pipe diffuser, volute belong to the 3D technological effects. These effects aredefined by 3D surfaces or 3D curves (x,y,z coordinates). Their meshes are created manually usingthe structured multiblock grid generation system IGG™. The steps used to create the mesh (moredetails in IGG™ user manual and in dedicated tutorial) are automatically saved and can be replayedon similar geometry.

3-2.5 Cooling & Conjugate Heat Transfer

AutoGrid5™ allows the mesh generation of the blade and the end wall solid bodies (Conjugate HeatTransfer module). Furthermore, the cooling module allows the mesh generation of basin, basinholes, blade holes, end wall holes, cooling channel with or without pin fins and ribs. More detailsare presented in Chapter 10.

Meshing Fundamentals Geometry Definition

3-4 AutoGrid5™

3-3 Geometry DefinitionThe geometry curves and surfaces defining the turbomachinery domain can be entered using twodifferent ways:

• ".geomTurbo" native files (NUMECA turbomachinery geometry file format)

• external CAD files (Parasolid™, CATIA v5, IGES format, ".geomTurbo" native, ".dat" files)

3-3.1 The ".geomTurbo" File Format

The ".geomTurbo" file format is structured in three main blocks: the header, the channel and therow(s) definitions. Following is a example of a ".geomTurbo" file format structure for a turboma-chinery with three blade rows respectively named impeller, diffuser and return channel.

GEOMETRY TURBOVERSION 5.3bypass nocascade noNI_BEGIN CHANNEL...NI_END CHANNEL NI_BEGIN nirow NAME impeller ...NI_END nirowNI_BEGIN nirow NAME diffuser...NI_END nirowNI_BEGIN nirow NAME return channel...NI_END nirowNI_END GEOMTURBO

NI_BEGIN GEOMETRY

NI_END GEOMETRY

� The bypass parameter must be set to yes in case of a project configuration with bypass(airplane engine,...)

� The cascade parameter must be set to yes in case of a cascade configuration.

3-3.1.1 Channel Format

The channel format contains the definition of the turbomachinery meridional contour (hub, shroud,seal leakage, bleed,...). It is defined by two types of curves:

• The basic curves defined by a set of points.

• The channel curves defined as a composite of basic curves.

NI_BEGIN CHANNEL NI_BEGIN basic_curve

basic curves definition

header

channel definition

row(s) definition

all geometry defined using import CAD window

Geometry Definition Meshing Fundamentals

AutoGrid5™ 3-5

NAME curve_1 ... NI_END basic_curve NI_BEGIN basic_curve NAME curve_2 ... NI_END basic_curve NI_BEGIN channel_curve hub NAME hub... NI_END channel_curve hub NI_BEGIN channel_curve shroud NAME shroud ... NI_END channel_curve shroud NI_END CHANNEL

� The number of basic curves is unlimited.

� The ".geomTurbo" file must contain two channel curves named respectively hub andshroud.

a) Basic Curves

The basic curve format is used to defined a curve and project it in the meridional space (z,r). Thecurve is defined by a name, an interpolation method (c-spline or polyline), the coordinate type, thenumber of control points and the points coordinates:

NI_BEGIN basic_curve NAME curve_1 DISCRETISATION 10 DATA_REDUCTION 0 NI_BEGIN zrcurve ZR 28 -0.0425 0.256692 -0.0312928 0.25656... NI_END zrcurve NI_END basic_curve

The coordinate types are identified by the following keyword: ZR, XYZ, RTHZ, ZRTH, THRZ,RZTH,... where X,Y and Z are the 3 Cartesian coordinates and R,TH and Z are the 3 cylindrical coor-dinates.

� By default a c-spline interpolation between the control points is applied. The keywordpolyline can be added beside the coordinate type (ZR) to switch off the c-spline interpo-lation. In this case, the basic curve is defined by straight lines joining the control points.

� The DISCRETISATION number is the number of points defined between each controlpoints of the c-spline.

� The DATA_REDUCTION when set to 1 allows to perform a data reduction of the basiccurve based on DATA_REDUCTION_ANGLE and DATA_REDUCTION_DISTANCE.

curve name

interpolation type - coordinate type

number of control points

points coordinates

channel curves definition


3-6 AutoGrid5™

b) Channel Curves

The channel curves are used to define the hub, the shroud and possibly the nozzle in case of bypassconfiguration. A channel curve is a composite of defined basic curves. It is defined by a name andvertices. Each vertex belong to a basic curves and is defined by its parametric location (normalizedarc length).

NI_BEGIN channel_curve hub NAME hub VERTEX CURVE_P curve_1 0 VERTEX CURVE_P curve_1 1 NI_END channel_curve hub NI_BEGIN channel_curve shroud NAME shroud VERTEX CURVE_P curve_2 0 VERTEX CURVE_P curve_2 1 VERTEX CURVE_P curve_3 1 NI_END channel_curve shroud

� The nozzle curve is defined starting from the lower radius side from the outlet to the"inlet" (reverse hub direction) and then on the upper radius side from the "inlet" to theoutlet (shroud direction).

FIGURE 3.3.1-1 Nozzle curve orientation

3-3.1.2 Row(s) Definition Format.

The row format contains the geometry definition of a complete row. It is defined by a row name, arow type, a periodicity and the definition of the main blade and possibly the splitter(s):

NI_BEGIN nirow NAME impeller TYPE normalPERIODICITY 36NI_BEGIN 3d effectNAME 3d techno effect 1NI_END 3d effectNI_BEGIN NINonAxiSurfaces hub NAMEnon axisymmetric hub REPETITION0NI_END NINonAxiSurfaces hubNI_BEGIN NINonAxiSurfaces shroud NAMEnon axisymmetric shroud REPETITION0NI_END NINonAxiSurfaces shroud

row namerow typerow periodicity

hub keyword

shroud keyword

vertex definition

vertex definition

hub/shroud non axisymmetric definition

3d technological effect definition


AutoGrid5™ 3-7

NI_BEGIN NINonAxiSurfaces tip_gap NAMEnon axisymmetric tip gap REPETITION0NI_END NINonAxiSurfaces tip_gapNI_BEGIN NIBlade NAME main Blade...NI_END NIBladeNI_BEGIN NIBlade NAME splitter 1...NI_END NIBlade...NI_END nirow

a) Row Type

The row type is used to specify the row location in case of bypass configuration. Four types, identi-fied by the keyword NORMAL, ON_NOZZLE, IN_BYPASS and DOWN_BYPASS, are respectivelyused to locate the row before the nozzle (inlet fan), on the nozzle (arm), in the bypass and in thecompressor.

b) Row Periodicity

The periodicity defines the number of main blades in the row.

c) Blade Definition

The blade(s) and possibly the splitter(s) are defined by a name and two surfaces defining the pres-sure and the suction side. The surfaces are identified by the keywords pressure and suction:

NI_BEGIN NIBlade NAME main BladeNI_BEGIN nibladegeometryTYPE GEOMTURBOGEOMETRY_MODIFIED0GEOMETRY TURBO VERSION 5blade_expansion_factor_hub0.01blade_expansion_factor_shroud0.01intersection_npts 10intersection_control 1data_reduction 0data_reduction_spacing_tolerance 1e-006data_reduction_angle_tolerance 90control_points_distribution 0 9 77 9 50 0.00622408226922942 0.119480980447523 units 1number_of_blades 36

suction...pressure...NI_END nibladegeometryNI_END NIBlade

blade name

blade definition: pressure & suction keywords

main blade definition

splitter definition

tip gap non axisymmetric definition

blade unitsnumber of blades


3-8 AutoGrid5™

The units allows to change the "units" of the imported geometry in order to impose a scaling factorand a corresponding tolerance that will ensure correct treatment during the grid generation whencomputing for example the intersection. If not necessary, it is recommended to keep the default set-tings (Scale Factor set to 1).

The number_of_blades is the number of blades in the row and this must be an integer. This parame-ter comes from the old AutoGrid4™ geomTurbo format. The PERIODICITY (AutoGrid5™ geom-Turbo format) specifies also the number of blades and this can be different from an integerespecially for cascade configuration (section 5-6). For such configuration, only the PERIODICITYis used and correspond to the pitch distance between two consecutive blades.

The pressure side and the suction side are defined by a set of cross sections of the blade at severalspanwise location. Each section is defined by a set of points:

suctionSECTIONAL13# section 1XYZ1000.17669 -0.0208609 0.0003514710.176691 -0.0208788 0.000370063...# section 2XYZ1000.17669 -0.0208609 0.0003514710.176691 -0.0208788 0.000370063...

The coordinate types of each sections are identified by the following keyword: ZR, XYZ, RTHZ,ZRTH, THRZ, RZTH,... where X,Y and Z are the 3 Cartesian coordinates and R,TH and Z are the 3cylindrical coordinates.

� In AutoGrid5™ the rows and blades can be named by the user. These names are appear-ing in the ".geomTurbo" file and are used in the ".trb" file. In case the user wants to use atemplate for different ".geomTurbo" files, the row and blade names should be the same.

Besides format description, as discussed in the above part, the following options can be consideredin order to close the blade geometry using a Cspline curve technique. The options are howeverrestricted to situations when either the leading or trailing edge are left undefined. To do so, the fol-lowing can be added in the sections pressure or suction.

• [ blend_inlet [nb_pt expan_ratio]]: providing the leading edge of the blade is not defined, theuser can add the key word blend_inlet to define automatically a rounded leading edge using a c-spline curve that connects the pressure and suction sides of the blade. The parameters nb_pt andexpan_ratio respectively represent the number of points selected to define the blend curve andthe relative expansion size of the curve edge relative to the distance between the suction andpressure sides of the leading edge. Example: suction blend_inlet 10 1.2

• [blend_outlet [nb_pt expan_ratio]]: providing the trailing edge of the blade is not defined, theuser can add the key word blend_outlet to define automatically a rounded trailing edge using ac-spline curve that connects the pressure and suction sides of the blade. The parameters nb_ptand expan_ratio respectively represent the number of points selected to define the blend curveand the relative expansion size of the curve edge relative to the distance between the suction andpressure sides of the trailing edge. Example: suction blend_outlet 12 1.1

• [blend_inlet_outlet [nb_pt expan_ratio] [nb_pt expan_ratio]]: providing both the leading andtrailing edge of the blade are not defined, blend_inlet and blend_outlet optional key words canbe concatenated into a single blend_inlet_outet key word. blend_inlet_outlet enables to define

points coordinates

coordinate typenumber of control points

definition of section 2

suction keyword

points coordinates

coordinate typenumber of control points

number of sections

definition of section 1 - close to hub


AutoGrid5™ 3-9

automatically the edges using a c-spline curve that connects the pressure and suction sides of theblade. See blend_inlet and blend_outlet for the definition of parameters nb_pt andexpan_ratio. Example: suction blend_inlet_outlet 10 1.2 12 1.1

When the surfaces defining the blade are physically ruled and that the blade is defined through a setof sections within the ".geomTurbo" file, user must take care to select the same number of points todefine each section. In addition, when using the keyword uniform_parametrization, the ith pointof the first section will be connected to ith point of the second section.

Example:

Section_1 XYZ uniform_parametrization 36 0.5 0.3 0.1...Section_2 XYZ uniform_parametrization 36 0.55 0.35 0.11...

3-3.2 External CAD Format

AutoGrid5™ is able to import the geometry defining the domain from various external CAD format(IGES, CATIA v5, Parasolid™). The files containing the surfaces and the curves defining theblades and the meridional contour of the turbomachinery are loaded and displayed. Easy selectionof the geometrical entities can be operated interactively and linked to the project configurationthrough contextual menu (see Chapter 5 for more details). The blade channel must be defined by aset of curves (i.e. axisymmetric boundary of a surface of revolution). The blade(s) of each row aredefined by a set of surfaces and two curves defining the leading and the trailing edges. As long asthese curves are not defined, AutoGrid5™ is not able to create the inlet, outlet and mixing planeboundary of the domain.

� Parasolid™ and CATIA v5 import is not available on specific platforms. Please refer tothe installation note for more details.

Meshing Fundamentals Mesh Generation Steps

3-10 AutoGrid5™

3-4 Mesh Generation StepsThe mesh generation of a turbomachinery configuration is divided into 6 main steps:

FIGURE 3.4.0-1 Mesh generation steps

Additional steps can be defined to mesh technological effects.

3-4.1 Project Initialization

AutoGrid5™ provides two different ways to initialize a new project according to the type of the geome-try definition (".geomTurbo" or external CAD file). The dialog box Create a new Project (availablethrough the menu item File/New Project) lets the choice between a manual initialization from externalCAD file and an automatic initialization from a ".geomTurbo" file.

FIGURE 3.4.1-1 Project initialization dialog box

Project set up

Flow path control

Blade to blade mesh control

3D mesh generation

Project persistency

Project Initialization

Optional

Expert Mode Wizard Mode

Mesh Generation Steps Meshing Fundamentals

AutoGrid5™ 3-11

As mentioned in the previous chapter, the ".geomTurbo" file contains data used to set up automatically thenumber of rows and to link the geometry contained in the files.

3-4.2 Project Setup

The project setup can be divided in 3 main steps:

The geometry & configuration definition step is only needed if the project is initialized from external CADfile. In this case, the configuration of the machine must be set through the subpad Rows Definition of theQuick Access Pad and the link with the geometry must be done manually through the Import CAD windowbefore starting the grid generation.

The global parameters settings involves the definition of the periodicity for each row (contextual menu Row/Properties in Expert Mode or in the Blade row type dialog box in Wizard Mode), the shroud and hub gapdefinition (contextual menu Row/Define Shroud Gap & Row/Define Hub Gap in Expert Mode or in theGap and Blending Control dialog box in Wizard Mode) and the first cell width at the solid wall definition(parameter Mesh Control/Row Mesh Control/Cell Width in the Quick Access Pad in Expert Mode or inthe Layer Control dialog box in Wizard Mode).

Global parameters settings

Default topology definition

Geometry & Configuration definition

Expert Mode Wizard Mode

Wizard Mode


3-12 AutoGrid5™

3-4.2.1 Row Properties

The row contextual menu item Properties in Expert Mode opens the dialog box Row Properties.The options and parameters available into this dialog box controls the mesh generation of the rows.

a) Periodicity

The parameter Periodicity defines the number of main blade passage into the row. It defines thepitch angle of the blade to blade domain pitch = 2PI/periodicity.

b) Number of Geometry Periodicity

Usually the geometry is specified for one main blade passage: main blade and possibly the splittersurfaces. If the geometry is specified for 2 blade passages, the parameter Number Of GeometryPeriodicity must be set to 2. This option is useful for dissymmetric blading.

c) Row Information

The parameters Row Type, Row Orientation, Multi-splitters and Rotation Speed are informa-tion not used by the grid generation process. However the Rotation Speed will be used in FINE™GUI.

d) Hub/Shroud/Shroud Gap Non-Axisymmetric

These options allow to control the hub, shroud and shroud gap when non-axisymmetric. All theseoptions are explained in details in section 5-4.2 and section 5-5.5.


AutoGrid5™ 3-13

e) Tandem Row

The parameters Tandem Row must be set to Yes or to With Next/With Previous in case of tandemrow. This is taken into account during the blade to blade grid generation process to improve thequality of the initial mesh (before optimization). The blade to blade process is explained in detailsin section 7-3.3.

f) Full Mesh Generation

By default, the mesh is generated for 1 main blade passage. The parameter Generate Full Meshcan be switched on to generate all the blade passages. The mesh is obtained by repetition of the firstblade passage.

g) Low Memory Use

To reduce the memory usage, the parameters Low Memory Use can be switch on to swap on disksome data (i.e. the computation of the intersections) performed during the grid generation process.It is recommended to switch on this option when meshing multiple channels of blades defined usingimport CAD window.

h) Number of Repetition

By default, when selecting the menu View/toggle 3D Solid View (section 2-3.3.7), a single blade ofeach row will appear in the 3D view.

The number of blades in the graphics area can be repeated for each row individually using theNumber Of Graphics Repetition parameter available in the Row Properties dialog box. Activatethe Default option to see a complete view of all the blades of the selected row.

3-4.2.2 Hub/Shroud Gap (Expert Mode)

The row contextual menu item Define Hub/Shroud Gap in Expert Mode opens the dialog boxallowing to control the geometry and the meshing parameters of the gap as presented in section 6-3.3.

3-4.2.3 Cell Width

The Cell Width imposed in the subpad Mesh Control in Expert Mode will allow to impose thecell width at the hub, shroud, shroud and hub gap, and the cell width at the wall in the blade to blademesh. Afterwards, the cell width can be controlled in the meridional and in the blade to blade views(refer to chapters 5 and 6).

3-4.2.4 Mesh Control

The default topology is set up automatically using the button (Re)set Default Topology of the topmenu bar in Expert Mode. It defines the topology and the grid points distribution in the mesh. Dur-ing this process, AutoGrid5™ searches an optimized topology according to some geometrical crite-rion and the grid level selected through the Mesh Control/Grid Level page of the Quick AccessPad:


3-14 AutoGrid5™

� The button (Re)set Default Topology applies to the active row(s).

� The total number of points resulting from the automatic default topology settings depends ofthe geometry, the number of splitter, the shroud and/or hub gap definition (Coarse ≅ 150,000points, Medium ≅ 300,000 points and Fine ≅ 1,000,000 points per blade).

3-4.3 Flow Paths Control

The 3D row meshes generated with AutoGrid5™ are obtained by stacking blade to blade meshes on sur-faces of revolution generated from meridional curves called flow paths. Each row of the project has itsown set of flow paths. In Expert Mode, the default number of flow paths is equal respectively to 33, 57,97 (if the blade is without hub/shroud gap) according to the grid level chosen during the topology initial-ization (coarse, medium or fine mesh). This number can be modified through the Mesh Control/RowMesh Control/Flow Paths Number parameter. In Wizard Mode, the number of flow paths is controlledin the Control Layer dialog box.

FIGURE 3.4.3-1 Flow path definition

If the default flow path definition generated by AutoGrid5™ is not suitable for the project configurationor for the CFD computation, the features of the dialog box Row: Flow Paths Control can be used toobtain a complete control of the flow path definition. This dialog box is available through the menu itemMesh Control/Row Mesh Control/Flow Path Control in Expert Mode.

3-4.4 Blade to Blade Control

The 3D row meshes generated with AutoGrid5™ are obtained by stacking blade to blade meshes createdin the (dm/r,theta) space. Each blade to blade mesh is related to a flow path. The "m" coordinate is equalto the curvilinear coordinate along this flow path. A blade to blade mesh is generated in four steps:

Conformal Mapping

B2B Mesh Initialization

B2B Topology Optimization

Blade(s) & Layer Intersection


AutoGrid5™ 3-15

The button (Re)set Default Topology (Expert Mode) and the button Preview B2B in the B2B Con-trol dialog box (Wizard Mode) perform automatically these steps. Afterwards, the user is able tomodify manually the default settings proposed by AutoGrid5™ in Expert Mode.

3-4.4.1 Conformal Mapping

The flow paths defined in the meridional space are used to create surfaces of revolution named lay-ers. These surfaces are intersected by the blade(s) definition to obtain 3d sections projected into the(dm/r,theta) space. The projection, named conformal mapping, ensures reciprocity of the angles anddistances.

FIGURE 3.4.4-1 Blade cross section

3-4.4.2 Blade to Blade Mesh Initialization

The blade to blade mesh initialization is divided in 3 steps:

• Definition of a default topology around the cross sections projected in the (dm/r,theta) space.

• Initialization of the grid point clustering.

• Initialization of the mesh by transfinite interpolation.

a) Default (O4H) Blade to Blade Topology

The default B2B topology computed by AutoGrid5™ is composed by 5 Blocks:

FIGURE 3.4.4-2 Default mesh topology

Blades cross sections

Layer

Blade

Upper block

Lower block

Outlet blockSkin block

Inlet block

(dm/r,theta) cross section


3-16 AutoGrid5™

The inlet, outlet, upper and lower blocks use a H-topology. The skin block around the blade uses aO-topology.

The (Re)set Default Topology settings algorithm can change the upper and/or the lower blockstopologies from H to C-topology if one of the following criteria is reached:

• The inlet solid angle of the blade becomes higher than 45 degrees and the distance between theinlet and the stagnation points (in the (dm/r,theta) space) becomes smaller than the pitch angledivided by 4.

• The outlet solid angle of the blade becomes higher than 45 degrees and the distance between theoutlet and the trailing edge (in the (dm/r,theta) space) becomes smaller than the pitch angledivided by 4.

This mesh topology adaptation is called high staggered blade topology optimization:

FIGURE 3.4.4-3 Mesh topology for high staggered blade

Beside the default (O4H) topology (5 blocks), AutoGrid5™ allows the use of HOH and H&I topol-ogy, and gives access to a manual blocking mode named User Defined Topology mode. In thismode, the user creates its own blocking and control manually the grid points clustering (moredetails in Chapter 7).

� The topology can be modified through the dialog box Define B2B Topology For ActiveBlade. This dialog box is available through the menu item Mesh Control/Row MeshControl/B2B Mesh Topology Control in Expert Mode.

H block

C block


AutoGrid5™ 3-17

b) Grid Points Clustering

The feature (Re)set Default Topology computes the most appropriated grid points clustering on eachblock edge of the default topology (and possibly the HOH or H&I topology) according to the cho-sen grid level.

� The grid point number can be modified through the dialog box Define B2B Topology ForActive Blade. This dialog box is available through the menu item Mesh Control/RowMesh Control/B2B Mesh Topology Control in Expert Mode.

c) Initial Mesh

The initial mesh is computed using transfinite interpolation techniques inside all the blocks of thedefault topology except in the skin block inside which a hyperbolic mesh is generated.

FIGURE 3.4.4-4 Initial mesh for a normal blade

� The parameters used to control the initial mesh can be modified through the dialog boxDefine B2B Topology For Active Blade. This dialog box is available through the menuitem Mesh Control/Row Mesh Control/B2B Mesh Topology Control in ExpertMode.


3-18 AutoGrid5™

3-4.4.3 Blade to Blade Mesh Optimization

The optimization system is based on a multiblock elliptic smoother with source terms. All theblocks of the initial mesh (all edges included except the solid wall) are optimized to reduce the cellskewness and the cells expansion ratio

FIGURE 3.4.4-5 High staggered mesh optimization

� The parameters used to control the optimization can be modified through the dialog boxOptimization Properties. This dialog box is available through the menu item Mesh Con-trol/Row Mesh Control/Optimization Control in Expert Mode.

3-4.4.4 Blade to Blade View Control

The blade to blade view is used to display and control the quality of the blade to blade mesh of therows. The blade to blade mesh quality can also be controlled using the menu Grid/Grid Quality...

or the corresponding icon ( )

a) Display Update

After each modification of the blade to blade topology, the grid points number, the initial mesh orthe optimization parameters, the blade to blade view of the active row(s) can be updated using thetop menu bar button Generate B2B in Expert Mode or the button Preview B2B in the B2B Controldialog box in Wizard Mode.

b) Active Layer

The blade to blade view of the row is related to an active layer. By default, the active layer is thehub of the machine. The interaction area Mesh Control/Active B2B Layer is used to change theactive layer on which the blade to blade mesh is computed and displayed.


AutoGrid5™ 3-19

FIGURE 3.4.4-6 Active layer set to 100% (shroud) of the span

In multistage configuration, the user controls row by row the blade to blade display. A particularattention must be focused on the undesirable behaviour obtained when different blade to blade rowmeshes are displayed for different active layers: as the blade to blade view abscissa is the arc lengthon the active layer, the blade to blade mesh of different rows could overlap if they are displayed ondifferent layers. To avoid this and retrieve a correct display, all the rows must be selected and thetop menu bar button Generate B2B in Expert Mode or the button Update B2B View in the MeshControl/Active B2B Layer area in Wizard Mode, applied after selecting the new active layer.

� In case of a blade to blade user-defined topology (see section 7-6), when defining anactive layer which is not a control layer, internal faces are inserted in blocks to computethe mesh and then they are removed. Therefore this layer is not available for grid qualitycontrol.

Active Layer


3-20 AutoGrid5™

3-4.5 3D Mesh Generation

The 3D mesh generation of the active blade rows is performed through the top menu bar buttonGenerate 3D. The 3D mesh is automatically computed by AutoGrid5™ and displayed in the 3Dview. A mesh quality report can be computed and displayed with the top menu item Grid/Grid

Quality Report ( ).

FIGURE 3.4.5-1 3D grid generation & quality check

3-4.6 Project Persistency

The project persistency is performed using the menu items of the File menu. The name and thelocation of the project files are entered through the dialog box Save Project available through thetop menu item File/Save Project.


AutoGrid5™ 3-21

FIGURE 3.4.6-1 Save Project dialog box

3-4.6.1 Create New Project

The button Select a new Project File Name opens a file chooser used to specify the location and theprefix use to save the new project files. The new prefix is automatically added in the project library.

3-4.6.2 Overwrite Existing Project

The button Overwrite the Selected Project overwrites all the project files of the project selected inthe project library.

3-4.6.3 Project Library

The project library is the list of all projects saved previously. It is ordered using alphabetical orderand a quick search can be performed using the Search interaction area.

3-4.6.4 Project Info

The interaction area Enter Project Info is used to specify or modify text information about the savedproject. When scanning the library, the interaction area is automatically updated with the text of theselected project.

3-4.6.5 Project Files

Two types of files are saved by AutoGrid5™: the mesh and the template files.

a) Mesh files

The mesh files contain the multiblock mesh topology, geometry, grid points, patch grouping and theboundary condition types:

New project

Overwrite the project selected in the project library

Project library

Project Info


3-22 AutoGrid5™

• new_prefix.bcs: boundary conditions files

• new_prefix.cgns: grid points files (CGNS format)

• new_prefix.geom and new_prefix.xmt_txt (.X_T): geometry files

• new_prefix.igg: topology file

• new_prefix.qualityReport: mesh quality report file

• new_prefix.config: mesh configuration file used for the grouping in FINE™ GUI and for thesubProject (more details in FINE™ User Manual)



b) Template files

The template files contain the parameters and the geometry needed to reproduced the mesh withAutoGrid5™:

• new_prefix.geomTurbo and new_prefix.geomTurbo.xmt_txt (.geomTurbo.X_T): the geometryfiles (geomTurbo format)

• new_prefix.info: the information file

• new_prefix.trb: the template file containing the grid generation parameters.

• new_prefix_b2b.png: a picture of the blade to blade view

• new_prefix_merid.png: a picture of the meridional view

� In some cases, the Parasolid™ file (".X_T" (Windows) or ".xmt_txt" (UNIX)) is alsoneeded in AutoGrid5™ to replay the template (using ".geomTurbo.X_T") or to load theproject (using ".X_T"):

• If the Import CAD window is used with Parasolid™ or CATIAV5 entities. For IGES andIGG™ native files the Parasolid™ file is not needed as these are stored in the ".geom-Turbo" file.

• If AutoGrid5™ creates additional surfaces/curves in the available options, these are storedin Parasolid™ file as well. For example, if the Import CAD window is used to define thegeometry, the expansion is treated in Parasolid™ and the resulting surfaces are Parasolid™entities, even if the initial geometry was IGES or native IGG™.

3-4.6.6 Open Project File

Open an existing project is performed using the menu item Open Project of the top menu File. Thegeometry, the parameters and the existing mesh are loaded during this process. The project isopened by selecting its template file (".trb" extension). The template file of the project can beselected through a file chooser or through the project library of the Open Turbo Project Wizard.

The Open Project Turbo Wizard is divided into three areas presented on Figure 3.4.6-2.

a) Select Project File

This button opens a file chooser used to select a template file (".trb" extension).

Meshing Similar Geometry & Batch Mode Meshing Fundamentals

AutoGrid5™ 3-23

b) Project File Library

All the previously generated projects can be selected in the list and opened using the button Open.The last opened project becomes the active project of the list.

c) Project Information Area

The button Info>> opens the information area containing two pictures of the selected project, theuserdefined and global information of the project. This information are automatically updated whenscanning the projects of the list.

FIGURE 3.4.6-2 Open turbo project wizard

3-5 Meshing Similar Geometry & Batch ModeWhen a particular turbomachinery configuration has been meshed within AutoGrid5™, the originaltemplate files of the project can be used to mesh automatically similar geometries.

� In AutoGrid5™ when using an existing template for different geometry, it is not suffi-cient to rename the template as the ".geomTurbo" file (as in AutoGrid4™). It is manda-tory to use a ".geomTurbo" file presenting the same row and blade names as the onesused in the template (e.g. when using a new ".geomTurbo", only the geometrical entities

(A)

(B)

(C)

Meshing Fundamentals Meshing Similar Geometry & Batch Mode

3-24 AutoGrid5™

with the same naming as the ones used in the template file will be replaced).

The original template file and ".geomTurbo" file are first duplicated using the menu item File/SaveTemplate As. The geometry in the duplicated ".geomTurbo" file is then replaced by the user by asimilar geometry. Finally, AutoGrid5™ is launched in batch mode using command lines argumentsspecifying the template ".trb" file, the geometry ".geomTurbo" file and the target location of themesh files:

igg -niversion <version> -autogrid5 -batch -trb <template file> -geomTurbo <geomTurbo file> -mesh <mesh file> -print on UNIX/Linux,

igg.exe -autogrid5 -batch -trb <template file> -geomTurbo <geomTurbo file> -mesh <mesh file> -print on Windows.

where <version>, <template file>, <geomTurbo file> and <mesh file> are respectively the versionnumber and the full path names of the template file (".trb" extension), the geometry file (".geom-Turbo" extension) and the mesh file (".igg" extension).

For example:

igg -niversion 87_2 -autogrid5 -batch -trb /usr/user1/template/template1.trb -geomTurbo /usr/user1/geometry/geometry1.geomTurbo -mesh /usr/user1/mesh/mesh1.igg on UNIX/Linux,

igg.exe -autogrid5 -batch -trb c:/usr/user1/template/template1.trb -geomTurbo c:/usr/user1/geome-try/geometry1.geomTurbo -mesh c:/usr/user1/mesh/mesh1.igg on Windows.

� The location of the grid quality report file can also be specified using the command line:-qualityReport <quality report file full path name>.

� The option -real_batch can also be specified to allow to generate the mesh in batch modewithout the need of a display: igg -niversion 87_2 -real_batch -autogrid5 -trb ...

� When the original geometry has been specified through external CAD geometry files, thesimilar geometry CAD files can also be specified using the command lines: -dat <geom-etry file 1> -dat <geometry file 2> ...

FIGURE 3.5.0-1 Batch Generation

Create Original Template

Duplicate Template

Replace Geometry

Generate New Mesh using Batch Mode

AutoGrid5™ 4-1

CHAPTER 4: Wizard Mode

4-1 OverviewThe Wizard Mode is a simplified mode allowing to create meshes for a large range of turbomachineryconfigurations without technological effects and/or cooling effects such as:

• wind turbine

• axial, Francis, Kaplan turbine

• inducer

• axial compressor

• centrifugal impeller

• centrifugal diffuser

• return channel

• counter rotative fan

• SHF pump

• axial fan

The Wizard Mode has been designed to reduce drastically the number of options available in the inter-face in order to simplify the user life when meshing blade rows without technological effects and/or cool-ing effects. This mode is available in Expert Mode when selecting Wizard Mode in the top right toolbarby clicking on the arrow at the right of the user mode combo box.

In addition to the simplified interface, a row wizard offers an easy way to set up the mesh generationparameters according to the type of the machine. The row wizard is available using the button Row MeshSet Up of the top menu bar in Wizard Mode or using the button Start Row Wizard through the Mesh Con-trol/Grid Level page of the Quick Access Pad in Expert Mode.

Wizard Mode Wizard Mode GUI

4-2 AutoGrid5™

4-2 Wizard Mode GUIThe Wizard Mode has been designed to reduce drastically the number of options available in theinterface in order to simplify the user life when meshing blade rows without technological effectsand/or cooling effects.

In Expert Mode, this mode is available when selecting Wizard Mode in the top right toolbar byclicking on the arrow at the right of the user mode combo box.

FIGURE 4.2.0-1 AutoGrid5™ Wizard Mode Interface.

Together with the AutoGrid5™ interface, a Open Turbo Project Wizard window is opened, whichallows to open an existing project. See section 2-2.2 for description of this window.

4-2.1 Main Menu Bar

The menu bar contains a part of available options of AutoGrid5™. Menu items can be activatedusing click and drag or click and release modes. More details on each menu is available in section2-3.

• File menu: Open/New/Save and Save Project As, Save and Save Template As

• View menu: Patch Viewer, Sweep surfaces, Coarse Grid, Repetition, Face Displacement, Viewand Hide 3D Solid Mesh

User Mode

Toolbar(section 4-2.2)

Menu bar (section 4-2.1)

Quick Access Pad(section 4-5)

Graphics area(section 4-7)

Control area(section 4-6)

Wizard Mode GUI Wizard Mode

AutoGrid5™ 4-3

• Grid menu: Boundary Conditions, Grid Quality, Grid Quality Report and Negative Cells

• Module menu: IGG, AutoGrid4 and AutoGrid5 switch menu items

4-2.2 Toolbar

The toolbar contains icons and buttons providing fast input/output options. These are divided into 6 sec-tions:

• the user mode combo box: Wizard Mode/Expert Mode

• the project management icons

• the mesh generation buttons

• the view and mesh quality icons

• the view management icons

• the copy/paste row topology icons

FIGURE 4.2.2-1 Top toolbar

4-2.2.1 User Mode

By clicking on the arrow at the right the user may select the user mode.

4-2.2.2 Project Management Icons

These icons are related to the most often used options of project management.


Icon Description

Opens an existing project previously created by AutoGrid5™.

See the File/Open Project menu item description on section 2-3.1.1.

Project Management Icons Mesh Generation Buttons

View & Mesh Quality Icons

User Mode

View Management Icons Copy/Paste Row Topology Icons


4-4 AutoGrid5™

4-2.2.3 Mesh Generation Buttons

These buttons are used to start the mesh wizard or the 3D mesh generation.

4-2.2.4 View & Mesh Quality Management Icons

These icons are related to view management and the mesh quality analysis.

Closes the current project and opens a new empty one.

See the File/New Project menu item description on section 2-3.1.2.

Saves the current work in the files of the current project.

See the File/Save Project menu item description on section 2-3.1.3.

TABLE 14. Mesh Generation buttons

Buttons Description

Start the row wizard process for the selected row.

Generate the flow paths, the blade to blade mesh and the 3d mesh of the selected rows.

See the Generate 3D button description on Chapter 8.


Icon Description

Open the Mesh Quality dialog box of AutoGrid5™.

See the Grid/Grid Quality menu item description on section 2-3.4.3.

Open the Grid Quality Check dialog box of AutoGrid5™.

See the Grid/Grid Quality Report menu item description on section 2-3.4.4.

Open the Negative Cells dialog box of AutoGrid5™.

See the Grid/Negative Cells menu item description on section 2-3.4.6.

Open the Patch Selector dialog box of AutoGrid5™.

See the Grid/Boundary Conditions menu item description on section 2-3.4.2.

Select the grid level used by AutoGrid5™ to visualize the mesh.

See the View/Coarse Grid menu item description on section 2-3.3.3.

Open the Sweep Surface dialog box of AutoGrid5™.See the View/Sweep Surface menu item description on section 2-3.3.2.

Act as a toggle and perform a repetition in the blade-to-blade or 3D views based on the settings imposed by the user in the View Repetition dialog box of AutoGrid5™.See the View/Repetition menu item description on section 2-3.3.4.


Icon Description


AutoGrid5™ 4-5

4-2.2.5 View Management Icons

These icons allow to set any view in full display mode or to reset the display mode to multiview.

4-2.2.6 Copy/Paste Row Topology Icons

The copy/paste topology icons allow the user to apply same wizard options from one row to others.It is especially dedicated for multistage machine with several rows of same type (i.e. axial compres-sor or axial turbine).

4-2.3 Quick Access Pad

The Quick Access Pad is located in the left part of the GUI. It contains icons and more evolvedoptions providing a fast access to the more used functions of AutoGrid5™. Some of these functionsare only accessible through the Quick Access Pad whereas others are also accessible through themenu bar, so that their description will be referenced to these menus.

The pad is divided into four subpads, each of which can be toggled by a simple mouse left-click:

• Rows Definition subpad

Visualize or hide the solid model of the machine in the 3D view.

See the View/toggle 3D Solid View menu item description on section 2-3.3.7.

Set the active view in full display mode.


TABLE 16. View Management icons

Icon Description

Set meridional view in full display mode.

Set blade-to-blade view in full display mode.

Set 3D view in full display mode.


TABLE 17. Copy/Paste Row Topology icons

Icon Description

Copy the selected row wizard options into a buffer.

Replace the selected row(s) wizard options by the wizard optionsstored into the current buffer.


Icon Description


4-6 AutoGrid5™

• Geometry Definition subpad

• Mesh Control subpad

• View subpad

All the commands and options accessible with these subpads are described in detail in this section.

The four subpads are composed of pages containing buttons, icons, input areas. The icons performspecific function related to the subpad and the page. Each page can also be toggled by a simplemouse left-click.

FIGURE 4.2.3-1 Quick Access Pad

Rows Definition subpad

to control the machine configuration

Mesh Control subpad

View subpad

Geometry Definition subpad

to define the geometry of hub, shroud,

to update the mesh in blade-to-blade view

to control the mesh representation

Grid Parameters area

nozzle and blades


AutoGrid5™ 4-7

4-2.3.1 Rows Definition Subpad

The rows definition subpad is used to control the machine configuration through project manage-ment buttons and a tree. In the rows definition tree subpad, the user can access following options:

• Select all the rows

• Define new rows

• Define or remove new blade(s) through the row contextual menu (right-click)

• Define and control the blade geometry through the blade contextual menu (right-click)

FIGURE 4.2.3-2 Contextual popup menus

4-2.3.2 Geometry Definition Subpad

The geometry definition subpad gives access to:

• The project initialization through the selection of a native AutoGrid5™ geomTurbo file (section3-3.1).

• The geometry initialization through external CAD files (section 5-3). The import CAD windowhas been simplified to give access only to blade and end wall geometry definition.

• The units definition (section 2-5.2).

4-2.3.3 Mesh Control Subpad

The mesh control subpad displays the number of mesh points of the selected row(s) and allows tochoose the layer (Active Layer (% span)) on which the user wants to display the blade-to-blademesh by pressing the button Update B2B View.

Blade menuRow menu

Wizard Mode Row Wizard

4-8 AutoGrid5™

4-2.3.4 View Subpad

The view control subpad is used to control the display of mesh entities in the blade-to-blade viewand in the 3D view. When clicking in the 3D view or pressing the viewing icon View 3D, the view-ing buttons are associated to the mesh field of application buttons and the Geometry Definitionand Mesh Control subpads are closed.

4-3 Row WizardAfter defining the geometry, a row wizard provides an easy way to set up the mesh propertiesthrough a wizard. The wizard is launched using the button Row Mesh Set Up in Wizard Mode orStart Row Wizard in Expert Mode:

The wizard is composed be a set of dialog boxes. Each dialog box is related to the set up of a set ofmesh generation parameters. They contains buttons Cancel, OK, <<Back, Skip>>, Next>> or Fin-ish to control the set up process.

• The Cancel button suppresses all the parameters already set by the wizard.

• The OK button is used to quit the wizard and keep the parameters already set.

• The <<Back button is used to return to the previous dialog box.

• The Skip>> button is used to skip the settings of the dialog box.

• The Next>> button is used to go the next dialog box.

• The Finish button is used to quit the wizard and launch the 3D mesh generation.

The wizard is divided in 6 steps:

• The geometry check (optional)

• The machine characteristics definition

• The gap and fillet definition

• The flow path definition

• The blade-to-blade mesh definition

• The end of the initialization

Expert Mode

Wizard Mode

Row Wizard Wizard Mode

AutoGrid5™ 4-9

4-3.1 Geometry Check

When launching the wizard, AutoGrid5™ warns the user that mesh generation parameters will be modi-fied by the wizard and prompts the user to continue. This reset will keep the modifications performed bythe user in the Wizard Mode but will reset to the default value the parameters modified in Expert Mode.Then AutoGrid5™ proposes to check the geometry.

If a geometry check is asked (Yes button), a dialog box displays the geometry status. If the geometry isOK, a button Next prompts the user to continue the wizard.

� Only one row must be selected before launching the wizard. If no row or multiple rows areselected, AutoGrid5™ warns the user and quits the wizard.

4-3.2 Machine Characteristics Definition

After the geometry check, the Blade row type dialog box is opened.

Geometry Check OK Geometry Check not OK


4-10 AutoGrid5™

At this stage, the machine type is specified: Wind Turbine, Axial Turbine, Francis Turbine, KaplanTurbine, Inducer, Axial Compressor, Centrifugal Impeller, Centrifugal Diffuser, Return Channel,Counter Rotative Fan, SHF pump and Axial Fan. By default no blade type is selected.

The user must also define the row periodicity, the rotation status (rotor or stator) and the rotationspeed.

According to the machine type, AutoGrid5™ will choose and adapt the most appropriated meshgeneration parameters available in AutoGrid5™ expert mode.

4-3.3 Gap/Fillet Definition

The next step of the wizard is used to define the gaps and the blade fillets if needed.

In case of inducer, axial compressor, axial turbine or Kaplan turbine with rotor mode active, the firsttime the wizard is executed, AutoGrid5™ automatically defines a tip gap into the mesh configura-tion. If hub and/or tip gap or hub and/or tip fillet already exists in the project configuration, the usercan keep unmodified their definition by pressing the button Skip>>.

At this stage, the meridional view display the gap or fillet definition. The user can control the gap orfillet width at leading and trailing edge. By default, the widths are set equal to the blade heightdivided by 20. When selecting the hub gap or tip gap option, the respective hub fillet or tip filletoption is automatically frozen and reversibly.

� When pressing the button Next>>, a message warns the user if the fillet does cut thelimit of the domain.

4-3.4 Flow Path Definition

The fourth stage of the wizard controls the cell width at the wall and the number of flow paths. Thespanwise expansion ratio is continuously updated after each user's change. The flow paths are auto-matically displayed and updated into the meridional view.

Hub Fillet

Tip Gap


AutoGrid5™ 4-11

By default, the number of flow paths is set to 57. If tip and/or hub gap/fillet are defined previouslyin the Gap and Blending Control dialog box, the number of flow paths is increased by 16 or 32 (73or 89 flow paths).

When increasing or decreasing the number of flow paths, the number of flow paths in the gaps andfillets is automatically updated as well as the percentage of constant cells:

• the flow paths in the gap or fillet will be 25 for N>=129, 21 for N>=97, 17 for N>=65, 13 forN>=33 and 9 for N<33 (N is the number of flow paths).

• the percentage of constant cells will be 80 for N’>=157, 70 for N’>=129, 60 for N’>=97, 50 forN’>=81, 40 for N’>=65, 30 for N’>=33, 0 for N’<33 (N’ is the number of mid flow paths corre-sponding to N - gap/fillet flow paths).

4-3.5 Blade-to-Blade Mesh Definition

The last stage of the wizard is used to set up all the blade-to-blade parameters for the mesh genera-tion. All the expert parameters are set automatically according to the type of machine and the blade-to-blade geometry configuration.

When selecting the button Preview B2B, the blade-to-blade mesh is displayed in the blade-to-bladeview. The Minimum Skewness Angle and the Maximum Expansion Ratio are displayed in thedialog box. The option Full Visibility allows to see the mesh moving in the blade to blade viewwhen applying the modified blade to blade mesh parameters.


4-12 AutoGrid5™

The Grid Level of the mesh can be increased or decreased with the buttons << and >>.AutoGrid5™ automatically changes the number of grid points in all the area of the mesh. An esti-mation of the total number of grid points is continuously updated and displayed after each userchanges.

In addition, the option Skewness and Expansion Ratio can be used to display the quality colorcontour.

If the machine type is not an inducer, a Kaplan turbine or a shf pump and the high staggered bladeoptimization is high at inlet, low at outlet or low at inlet and high at outlet, a full matching mesh canbe imposed between the channel and the gap when a hub or tip gap is defined with the option FullMatching Mesh.


AutoGrid5™ 4-13

� A non-matching connection could be created in the gap if the throat control is activatedautomatically during the setup of the expert parameters. If Full Matching Mesh isactive, the throat control will not be activated.

4-3.6 Initialization End

When previewing the mesh (Preview B2B button in B2B Control dialog box or Update B2B View inMesh Control subpad) or finishing the initialization (Finish button in B2B Control dialog box),AutoGrid5™ imposes automatically cell width around the inlet and outlet limit of the row to ensurestreamwise continuity through the rotor stator line. The minimum value between two successiveblades is chosen.

When clicking on the button Finish, AutoGrid5™ proposes to start the 3D mesh generation of theselected row by clicking on yes.

Selecting no stops the 3D mesh generation process and allows the user to view the blade-to-blademesh on another active layer (Mesh Control subpad) or to switch in Expert Mode to verify andcontrol the mesh parameters set by AutoGrid5™ mesh wizard. When the parameters are welldefined, clicking on Generate 3D button in the toolbar will start the 3D mesh generation process.

4-3.7 MultiStage Management

The row wizard is useful for a quick setup of the mesh for all the rotors and stators of a multistageturbomachine:

• the row wizard is applied on the first rotor and on the first stator

• the first rotor is selected and the button Copy Row Topology pressed


4-14 AutoGrid5™

• all the other rotors are selected and the button Paste Row Topology pressed to apply the samewizard parameters to the other rotors.

• the first stator is selected and the button Copy Row Topology pressed

• all the other stators are selected and the button Paste Row Topology pressed to apply the samewizard parameters to the other stators.

4-3.8 Automatic Blade-to-Blade Settings

When clicking on the Preview B2B button in the dialog box B2B Control (section 4-3.5),AutoGrid5™ modifies expert parameters according to the machine type and the geometry configu-ration. All the parameters of the Define B2B Topology for Active Blade and Optimization Propertiesdialog boxes (Chapter 7) available in Expert Mode are updated during this operation.

4-3.8.1 Global Settings

a) Upstream & Downstream H blocks Definition

AutoGrid5™ automatically is adding and unfixing upstream and downstream control lines follow-ing the blade leading and trailing meridional shapes. These lines are created for all the machinetypes and are useful to activate the high staggered blade topology optimization.

The number of points in the streamwise direction before the upstream control line (N1) and after thedownstream control line (N3) is computed automatically based on the length and the number ofpoints (N2) in the streamwise direction between the control lines.

N1 = 0.5*N2*L1/L2

N3 = 0.5*N2*L3/L2

1

3

2 4


AutoGrid5™ 4-15

b) Blade-to-Blade Topology

The default matching O4H topology is used by the wizard. When the row geometry contains splitterblades or if the machine type is a centrifugal impeller, the H&I topology is automatically activated.

In case of a rotor, a tip gap is defined by default in the Gap and Blending Control dialog box.

c) High Staggered Topology

According to the blade solid angle (section 7-3.2) computed on the hub (βhub) and shroud (βshroud)

layer, the high staggered topology optimization is automatically activated.

The topology is highly staggered if:

• βhub>35° and βshroud>35°

• βhub>60° and βshroud>-20°

• βshroud>60° and βhub>-20°

• βshroud>50° and βhub>-10°

• βshroud>45° and βhub>=-1°

• βhub>45° and βshroud>=-1°

d) Blade-to-Blade Grid Points

For grid level 0, the default number of points on the blade is set to 81. When decreasing or increas-ing the grid level the number of points on the blade is set to ensure 3 multigrid levels. The numberof points in the blade-to-blade mesh is controlled by the number of flow paths (N):

• The number of points in the skin block: 9 if N<49, 17 if N<97, 25 if N<129 and 33 if N>=129.

• The number of points at leading edge and trailing edge: 9 if N<57, 17 if N<89, 25 if N<105 and33 if N>=105.

• The number of points in the gap boundary layer: 9 if N<49, 17 if N<97 and 25 if N>=97.

• The number of points in inlet and outlet blocks along streamwise direction: 9 if N<65, 17 ifN<105, 25 if N<129 and 33 if N>=129.

• The number of points in up and down blocks along azimuthal direction:9 if N<49, 17 if N<97,25 if N<129 and 33 if N>=129.

� In addition when high staggered mode is active, the number of points is computed in up

L3L2L1


4-16 AutoGrid5™

& down blocks to obtain a high quality mesh. The method also ensures at least 3 multi-grid levels.

• The number of points along the blunt leading or trailing edge is automatically updated to reducethe expansion ratio to 1.6 for grid level <=2, 1.4 for grid level <=4 and 1.2 for grid level >4.

For H&I topology, the number of points is automatically computed according the grid level andAutoGrid5™ imposes variation of the streamwise weight to recompute grid points distribution.

e) Throat Control

The throat control is automatically activated when:

• the machine type is a Kaplan turbine, inducer, shf pump or Francis turbine,

• the high staggered mode is high and low or low and high and the throat angle is < 60° at hub,shroud and midspan.

f) Sharp & Rounded Treatment

The sharp treatment is automatically activated for blade edge angle higher than 25°.

The rounded treatment is automatically activated for blunt blade of Kaplan and Francis turbines.

g) B2B Mesh Parameters

• The free outlet and inlet angle are activated.

• The minimum expansion ratio is computed automatically.

• The leading and trailing edge clustering is set to the cell width at wall for blunt blade.

• The interpolation level is set to 2%.

h) Optimization Parameters

• The number of smoothing steps is set to 200.

• The number of smoothing steps in the gap is set to 100.

• The skewness control is set to off.

• The skewness control in the gap is set to off.

• The multigrid acceleration is set to on.

Throat Angle


AutoGrid5™ 4-17

• The orthogonality level is set to 0.5.

• The orthogonality level in the gap is set to 0.5.

• The multisplitter control flag is set to off.

• The number of boundary smoothing steps is set to 0.

4-3.8.2 Machine Dedicated Settings

According to the type of machine, the defaults settings described above can be changed.

a) Wind Turbine Settings

The wizard of the wind turbine is composed by 6 steps controlling the main parameters of the meshgeneration of the wind turbine:

• Geometry check (optional)

• Dedicated pseudo shroud and upstream and downstream limit definition,

• Dedicated blade flow paths definition,

• Dedicated far field limit and far field flow path definition,

• Blade-to-blade mesh accuracy definition,

• 3D mesh generation.

Control Upstream and DownStream limits

When the wizard is launched, the Shroud Control dialog box allows to control the pseudo shroudlocation and the upstream/downstream limits.

AutoGrid5™ creates automatically a horizontal pseudo shroud located at a radius (R) defined by:

R=(Rtip x Blade Tip R Value) - (1e-5 x BladeHeight)

The normalized parameters Far Field Zmin Value and Far Field Zmax Value are used to locatedthe inlet and outlet of the domain using the blade location (Zref) and the blade height (BladeHeight)as normalisation value:


4-18 AutoGrid5™

Lupstream = abs(BladeHeight x Far Field Zmin Value) Zinlet = Zref-Lupstream

Ldownstream = abs(BladeHeight x Far Field Zmax Value) Zoutlet = Zref+Ldownstream

Control Flow Paths Definition

The Layers Control dialog box of the wizard is used to control the flow paths number and the flowpaths distribution on the blade by defining the cell width at hub and shroud and the percentage ofconstant cells.

The Spanwise Expansion Ratio is displayed in the dialog box.

� If the blade height is respectively upper or lower than 1000, the cell width at wall is auto-matically set to 1e-2 or 1e-5.

Control Far Field Domain

The third dialog box is used to control the domain up to the blade (far field).

The far field limit is controlled by the parameters Far Field R Value normalized with the bladeheight:

LdownstreamLupstream

INLET OUTLET

ZrefRtipBladeHeight


AutoGrid5™ 4-19

H = Far Field R Value x BladeHeight

In addition, the number and the distribution of the layers in the far field can be modified.

Automatically, at the end of the wizard procedure, a ZR effect named <Row name> far field is cre-ated to control the grid generation process of the domain up to the blade.

The following dedicated settings are changed automatically:

• The new topology (Wind Turbine (WT) High Staggered) is activated automatically if the bladesolid angle at mid span is upper than 45°.

• A rounded treatment is applied at the blunt trailing edge (Wind Turbine and Wind Turbine (WT)High Staggered topologies).

• The optimization steps is set to 5000.

• The multigrid acceleration is set to off.

• The free inlet and outlet angle are set to off and mesh is frozen (if the blade solid angle < 45°).

• The straight boundary initialization is set to on.

• The interpolation level is set to 10%.

• The butterfly bulb topology is applied when the configuration is presenting a bulb.

H

Wind Turbine (WT) High Staggered


4-20 AutoGrid5™

b) Axial Turbine Settings

In case of a rotor, a tip gap is defined by default.

c) Francis Turbine Settings

• A rounded treatment is applied at the blunt trailing edge.

• The throat control is active.

• The H bulb topology is applied when the configuration is presenting a bulb.


AutoGrid5™ 4-21

d) Kaplan Turbine Settings



• The H bulb topology is applied when the configuration is presenting a bulb.

• In case of a rotor, a tip gap is defined by default.

e) Inducer Settings

• A tip gap is defined by default.

• When defining the geometry using a geomTurbo native format, leading and trailing edge fittingis active (section 5-5.1.3)


• The default number of points at grid level 0 is set to 129 on the blade.

• The free inlet and outlet angle are set to off and mesh is frozen.

• The mesh relaxation at inlet/outlet is active.




4-22 AutoGrid5™

f) Axial Compressor Settings

In case of a rotor, a tip gap is defined by default.

g) Centrifugal Impeller Settings

If the machine type is a centrifugal impeller, the H&I topology is automatically activated.

h) Radial Diffuser Settings

No dedicated settings applied.


AutoGrid5™ 4-23

i) Return Channel Settings

No dedicated settings applied.

j) Counter Rotative Fan Settings

• The number of points along azimuthal direction is multiply by 2.

• Dedicated far field limit and far field flow path definition control (more details in Wind TurbineSettings).

k) SHF Pump Settings



4-24 AutoGrid5™

• The default number of points at grid level 0 is set to 129 on the blade.

• The free inlet and outlet angle are set to off and mesh is frozen.



l) Axial Fan Settings

• The new topology (Wind Turbine (WT) High Staggered) is used automatically if the blade solidangle at mid span is upper than 45°.



• The free inlet and outlet angle are set to off and mesh is frozen (if the blade solid angle < 45°).



AutoGrid5™ 5-1

CHAPTER 5: Geometry Definition

5-1 OverviewIn addition to define the geometry using a ".geomTurbo" file, the geometry definition can be per-formed interactively through the Import CAD window. Geometry data can be imported from severalCAD file formats, interactively selected and linked to configuration entities in an AutoGrid5™project.

The user can build a test case starting from scratch and using CAD data in an interactive way. Theblade geometry is defined by selecting one or more surfaces while the definition of other configura-tion features such as the leading edge, the trailing edge, the hub, the shroud, is performed by select-ing one or more curves and attaching that curve selection to the required feature.

5-2 Import ".geomTurbo" FileWithin AutoGrid5™, the ".geomTurbo" file format (more details in Chapter 3) can be imported indifferent ways:

• when creating a new project (File/New Project ( )), a Create a new Project window appears

that allows to initialize a new project from an existing ".geomTurbo" file. Then a File Chooserwindow is available for browsing through the file system and to select a file. When clicking onOK (Open) the geometry is loaded in AutoGrid5™.

Geometry Definition Import CAD

5-2 AutoGrid5™

• in the Quick Access Pad Geometry Definition subpad, the Import Geometry File menuallows to select and load geometry file (IGES, IGG™ geometry, Parasolid™ coupled with ".dat",".geomturbo’, CATIAV5 files) to define or replace the geometry of the entities found in the file.

• in the Quick Access Pad Rows Definition subpad, the popup menu on rows allows to load a

".geomTurbo" file to define or replace the geometry of the selected entities found in the file. After row(s)selection, right-click displays this menu. Define Geometry item replaces only the geometry ofthe row (blades, shroud/hub gap, cooling wall, ...) selected. To import a new hub or shroud, theImport CAD window must be used.

� In AutoGrid5™ when using an existing template for different geometry, it is not suffi-cient to rename the template as the ".geomTurbo" file (as in AutoGrid4™). It is manda-tory to use a ".geomTurbo" file presenting the same row and blade names as the onesused in the template (e.g. when using a new ".geomTurbo", only the geometrical entitieswith the same naming as the ones used in the template file will be replaced).

� AutoGrid4™ ".geomTurbo" file can be loaded within AutoGrid5™. When AutoGrid4™geometry file loaded, a warning will appear before loading.

5-3 Import CADThe Import CAD window is started by clicking on Import and Link CAD in the Quick Access PadGeometry Definition subpad.

Import CAD Geometry Definition

AutoGrid5™ 5-3

FIGURE 5.3.0-1 Import CAD window

5-3.1 Menu Bar

The menu bar gives access to several options which can be useful during the setup of a project.

• The pull-down menu File used to import and/or export geometry data in several CAD formats.

• The pull-down menu Geometry used to perform some geometry editing operations such as cre-ation of geometric entities

• The pull-down menu Edit used to specify the rotation axis of the configuration being defined.

• The pull-down menu View used to perform interactive viewing operations.

• The pull-down menu Select used to perform interactive selection operations.

5-3.1.1 File Menu

a) Open...

File/Open... is used to import geometry data from a file. A file chooser is opened to select a CADfile with one of the following extensions:

• ’.igs’, ’.IGS’, ’.iges’, ’.IGES’ : IGES files.

• ’.dat’, ’.geom’, ’.dst’ : IGG™ geometry files.

• ’.X_T’, ’.xmt_txt’ : Parasolid™ files.

Quick Access Pad

Menu Bar

Viewing Buttons


5-4 AutoGrid5™

• ’.geomturbo’, ’.geomTurbo’ : AutoGrid™ geometry files.

• ’.CATpart’ : CATIAV5 files (license key required).

FIGURE 5.3.1-1 Data Files selection window

� When importing a CATIAV5 file, only the surfaces are imported. If a curve is not part ofa surface, it is not imported.

b) Open IGES

File/Open IGES is used to import CAD data stored in the standard IGES format. When names aredefined for entities in the IGES file, AutoGrid5™ uses them for the new entities created in therepository.

FIGURE 4.3.1-1 IGES file browser


AutoGrid5™ 5-5

This option provides a powerful browser to scan the content of an IGES file and selectively importIGES entities recognized by AutoGrid5™. In the case of composite curves and surfaces, thebrowser allows to view each component defining the entity and to select them individually.

Filters, reserved to expert users, allows to filter the data viewed by the browser. Each filter corre-sponds to a criterion defining if entities with the corresponding attribute set accordingly will be dis-played in the browser/imported.

It might be useful to uncheck the Blank Filter/Blanked item in order to import only the entitiesmeant to be visible and get a clear view of the intended geometry. The same holds for the EntityUse Filter with only the geometry item checked.

For the Subordinate Filter items, it might be useful to also have the both item checked if top-levelentities cannot be translated, preventing the importation of their depending entities.

The Filters default settings have the following items checked: all Blank Filter items, all EntityUse Filter items but the definition item, the Subordinate Filter independent and logical items,all Hierarchy Filter items.

See the IGES reference manual for a complete understanding of all filter values. The list of availa-ble IGES entities that can be imported in AutoGrid5™ are presented in the table below.

c) Export...

File/Export... is used to save all geometry curves and surfaces into an ASCII file with extension".dat", using the IGG™ geometry file format, combined with a Parasolid™ ".xmt_txt" file.

Entity Type Nr Entity Type

100 Circular Arc

102 Composite Curve

104 Conic Arc

106 Copious Data (only curves and not points in IGG™)

110 Line

112 Parametric Spline Curve

114 Parametric Spline Surface

116 Point

120 Surface of Revolution

122 Tabulated Cylinder

126 Rational B-spline Curve

128 Rational B-Spline Surface

130 Offset Curve (only uniform offset in IGG™)

140 Offset Surface

142 Curve On Parametric Surface

144 Trimmed Parametric Surface

158 Sphere

196 Spherical surface


5-6 AutoGrid5™

d) Close

File/Close closes the current Import CAD session and opens a new one. All curves and surfaces areremoved without been saved from the geometry repository.

e) Exit

File/Exit is used to close the Import CAD window.

� The geometry entities imported in the Import CAD window session are not deleted bythis action. When reopening the Import CAD window, it shows still all entities.

5-3.1.2 Geometry Menu

The Geometry menu provides simple and efficient tools to create, edit and delete points, curves andsurfaces. Without having the complexity of CAD systems, it allows to create wire or surface modelsfrom scratch or to complement imported geometries. The menu allows to:

• create and edit basic and advanced curves and surfaces,

• visualize and probe the geometry entities,

• perform advanced geometry operations such as surface-surface intersection, offsetting...including attraction features to points, curves and surfaces.

� The Geometry menu is inherited from the IGG™ technology. Please refer to the IGG™User Manual.

5-3.1.3 Edit Menu

a) Geometry Axis...

Edit/Geometry Axis... is used to specify the rotation axis of the rotating parts of the configurationunder definition by the user. By default, the z-axis is assumed to be this rotation axis. The rotationaxis is defined by the position of the origin of the axis (X,Y,Z coordinates) and a direction vector(dx,dy,dz components). The modification is validated when pressing Apply.

5-3.1.4 View Menu

a) View Solid

View/View Solid is used to toggle the display of the solid triangulated representation for theselected surfaces. If a surface does not have any triangulated representation yet, one will be createdwith default settings.


AutoGrid5™ 5-7

� A triangulated representation with custom settings can be generated using Geometry/View/Prepare View.

5-3.1.5 Select Menu

a) Surfaces

Select/Surfaces allows the user to select or unselect one or more visible surfaces with the mouse.When selected, the boundary curves of the selected surfaces appear highlighted in yellow (default)else they appear in blue.

Surface selection is possible by simple positioning of the mouse over the surface. When several sur-faces are stacked on top of each other, AutoGrid5™ provides a way to sweep through the surfacesbefore selecting the desired one. The following prompt appears when selecting this option:

Subsequent operations are done with the mouse in the graphics area:

• Move the mouse to a surface to select (unselect). The surface is ready for selection (unse-lection) when it becomes highlighted in blue.

• Left-click to select (or unselect) the surface. The surface changes its highlight to reflect itsnew selection status.

• It is possible to select several surfaces at once by defining a selection rectangle. This rectan-gle can be specified by pressing the left mouse button without releasing it and dragging themouse. Releasing the left button will select all the surfaces totally included in this rectangle.

• When several surfaces are stacked on top of each other, in the direction of the user’s eyes,AutoGrid5™ takes by default the closest surface to the user. The user can sweep throughthe surfaces by middle-clicking the mouse, until the desired surface is highlighted. Left-click then allows to select the highlighted surface.

• Pressing the right button or <q> terminates the selection process.

� It is possible to select or unselect all surfaces at once by pressing <a> in the graphicsarea. The first time <a> is pressed all the surfaces are unselected. The next time, <a> actsas a toggle.

b) Curves

Select/Curves allows the user to select or unselect one or more visible curves with the mouse.When selected, the curves appear highlighted in yellow (default) else they appear in blue. The fol-lowing prompt appears when selecting this option:

Subsequent operations are done with the mouse in the graphics area:

— Moving the mouse over a non-selected curve highlights it,

— Pressing the left mouse button selects it,

— Pressing one more time unselects it,

— Pressing the left mouse button without releasing it and dragging the mouse draw a rectangle.Releasing the left button selects all the curves having a part in this rectangle,

— Pressing the right button or <q> terminates the selection process.

� It is possible to select or unselect all curves at once by pressing <a> in the graphics area.The first time <a> is pressed all the curves are unselected. The next time, <a> acts as a


5-8 AutoGrid5™

toggle.

c) Surface List ...

A surface chooser, showing all the surfaces in the geometry repository, is opened to select the surfaces. Theselected surfaces are highlighted. To make one or more surfaces selected, choose them with the left mousebutton in the chooser, then press Apply. The boundary curves of the surfaces are automatically highlightedin yellow in the graphics area.

The <Ctrl> key is used in combination with the left mouse button to select several surfaces in the chooser.

The <Shift> key is used in combination with the left mouse button to select a range of surfaces in thechooser. A range of surfaces can also be selected by pressing the left button, dragging the mouse and releas-ing the left button.

A filter, using regular expression search, is provided to select or unselect surfaces by their name.

d) Curve List ...

A curve chooser, showing all the curves in the geometry repository, is opened to select the curves. Theselected curves are highlighted. To make one or more curves part of the selection, select them with the leftmouse button in the chooser, then press Apply. The curves automatically appear highlighted in yellow in thegraphics area.


AutoGrid5™ 5-9

The <Ctrl> key is used in combination with the left mouse button to select several curves in thechooser.

The <Shift> key is used in combination with the left mouse button to select a range of curves in thechooser. A range of curves can also be selected by pressing the left button, dragging the mouse andreleasing the left button.

A filter, using regular expression search, is provided to select or unselect curves by their name.

e) Invert Selection

Select/Invert Selection toggles the selection status for each curve and surface in the geometry repos-itory. The geometry selection representation, which is highlighted in yellow in the graphics area, isautomatically updated

f) Hide Selection

Select/Hide Selection hides the selected curves and surfaces, i.e. the selected curves and surfaces areno longer visible in the graphics area.

� Curves and surfaces visibility can be controlled further by using Geometry/View/Curves... and Geometry/View/Surfaces...

5-3.2 Viewing Buttons

The viewing buttons allow the user to perform viewing manipulations on the geometry data. They areall inherited from the IGG™ technology.

From left to right, the viewing buttons are the following:

• X, Y, and X projection buttons.

• Coordinate axis

• Scrolling

• 3D viewing button

• Rotate around X, Y or Z axis

• Zoom in/out

• Region zoom

• Fit button

• Original button

• Cutting plane

� For further details, please refer to section 2-6.7.

5-3.3 Quick Access Pad

The Quick Access Pad is located on the left of the Import CAD window. It contains one subpadGeometry including the Geometry Groups page allowing the creation, the deletion and the visuali-zation of geometry groups, which can contain curves and/or surfaces.


5-10 AutoGrid5™

� When importing CATIA V5 data, a geometry group is automatically created for eachsolid model contained within the file. The name of the group is the name of the corre-sponding solid model.

� For further details, please refer to the Chapter 7 in IGG™ User Manual.

5-3.4 Graphics Area Interaction

5-3.4.1 Overview

The Import CAD window allows the user to define the geometry for a configuration by importingexternal geometry files. The curves and surfaces in the geometry repository can be interactivelyselected by the user. Once selected, geometry entities can be linked to a configuration entity such asthe hub, the shroud, the blade,...

The Check Surfaces option allows to automatic check the geometry when linking the blade sur-faces, blade leading/trailing edges. The status of the checks is displayed into a Blade GeometryCheck dialog box.

When the blade is defined by multiple surfaces, a single body will be created using a tolerance tofill the potential holes between the surfaces defining the blade. When clicking on the Check button,AutoGrid5™ checks if the body can be created within the specified tolerance. If not, the toleranceis automatically adapted and the user can manually increase the tolerance in case of failure.

5-3.4.2 "Link to..." Description

In the graphics area of the Import CAD window, the capabilities of linking geometry curves andsurfaces to configuration entities, whether in meridional representation or in 3D-space, are accessedby pressing the right mouse button after selecting the curves and surfaces (highlighted in yellow) inthe graphics area.


AutoGrid5™ 5-11

a) Link to Hub

Link to Hub is used to link a curve selection to the hub of the configuration The meridional repre-sentation of the hub is updated to display the new hub geometry.

b) Link to Shroud

Link to Shroud is used to link a curve selection to the shroud of the configuration. The meridionalrepresentation of the shroud is updated to display the new shroud geometry.

c) Link Non Axi to Hub

Link Non Axi to Hub is used to link a surface selection to the hub of the configuration in case of anon-axisymmetric hub.

d) Link Non Axi to Shroud

Link Non Axi to Shroud is used to link a surface selection to the shroud of the configuration incase of a non-axisymmetric shroud.

e) Link Non Axi to Shroud Gap

Link Non Axi to Shroud Gap is used to link a surface selection to the tip gap of the configurationin case of a non-axisymmetric shroud gap.

f) Link to Nozzle

Link to Nozzle is used to link a curve selection to the nozzle of the configuration. The meridionalrepresentation of the nozzle is updated to display the new nozzle geometry. This item only appearsin case of bypass configuration

g) Link to Fin Up/Down

Link to Fin Up/Link to Fin Down is used to link a curve selection respectively to the upper/lowercurve of the first row fin. This item only appears in case of bypass configuration and if the first row(fan) contains a fin.

define non axisymmetric hub/shroud

define nozzle in by-pass configurationdefine axisymmetric fin on fan in by-pass

define both outlets in by-pass configuration

configuration

and shroud gap


5-12 AutoGrid5™

h) Import Meridional

Import Meridional is used to import the geometry selection in the meridional representation.

Geometry selection may contain surfaces but those will not be taken into account by the importprocess. Only the curves in the geometry selection will effectively be imported and displayed in themeridional representation.

i) Link to 3D Effect

Import 3D is used to import the geometry selection and link it to the selected 3D effects.

j) Link to Blade

Link to Blade is used to link a surface selection to the active blade. That surfaces set will thus com-pose the blade surface geometry. When needed, the user may be requested to specify the blade towhich the geometry surfaces have to be linked. The meridional representation of the blade isupdated in order to display the new blade representation.

k) Link to Pressure/Suction Side

Link to Pressure Side/Link to Suction Side is used to link a selection of surfaces respectively tothe pressure/suction side of the active blade. The blade is assumed blunt at both edges and is notcompatible with Link to Blade. In particular, this link overrides the link to the blade geometry.

l) Link to Leading Edge

Link to Leading Edge is used to link a curve selection to the leading edge of the active blade.When needed, the user may be requested to specify the blade to which the geometry curves have tobe linked. The meridional representation is updated in order to display the new leading edge geom-etry.

� For a blunt leading edge, only one leading edge curve of the two blade sides should beselected.

m) Link to Trailing Edge

Link to Trailing Edge is used to link a curve selection to the trailing edge of the active blade.When needed, the user may be requested to specify the blade to which the geometry curves have tobe linked. The meridional representation is updated in order to display the new trailing edge geom-etry.

� For a blunt trailing edge, only one trailing edge curve of the two blade sides should beselected.

n) Link to Hub Gap

Link to Hub Gap is used to link a curve selection to the hub gap geometry for the active blade.When needed, the user may be requested to specify the blade to which the geometry curves have tobe linked to the hub gap definition. The meridional representation is updated in order to display thehub gap geometry.

o) Link to Shroud Gap

Link to Shroud Gap is used to link a curve selection to the shroud gap geometry for the activeblade. When needed, the user may be requested to specify the blade to which the geometry curveshave to be linked to the shroud gap definition. The meridional representation is updated in order todisplay the shroud gap geometry.

Hub/Shroud Edition Geometry Definition

AutoGrid5™ 5-13

p) Link to Inlet

Link to Inlet is used to link a curve selection to the inlet geometry of the active row.

q) Link to Outlet

Link to Outlet is used to link a curve selection to the outlet geometry of the active row.

r) Link to Outlet Up

Link to Outlet Up is used to link a curve selection to the second outlet (upper outlet) geometry of the activerow. Therefore the active row should be the row just before or on the nozzle. This item only appears in caseof bypass configuration.

� All link operations replace the previous link, if any. If the entity is composed of multiple curves orsurfaces, a multiple selection is therefore required (using <Shift> - left-click) before the link oper-ation is applied. For instance, the two sides surfaces of a blade must be selected before invokingthe link command.

5-4 Hub/Shroud EditionThe hub & shroud are defined by their meridional trace (ZR coordinates). They define the spanwise bounda-ries of the domain. The geometry of the hub and the shroud are defined using curves in (x,y,z), (r,theta,z) or(r,z) coming from a ".geomTurbo" file (NUMECA turbomachinery geometry file format) or from externalCAD files (Parasolid™, CATIA v5, IGES format).

5-4.1 Edit Hub/Shroud

Furthermore, in the Quick Access Pad Geometry Definition subpad, the Edit Hub/Edit Shroud (Edit Noz-zle in by-pass configuration) menus allow to edit and adapt the shape of the hub and shroud (nozzle) in the meridi-onal view.

When selecting Edit Hub or Edit Shroud, the control of the hub or shroud is done through the editing of anedge and its vertices.

Geometry Definition Hub/Shroud Edition

5-14 AutoGrid5™

Vertices can be:

• added. Use the <i> shortcut,

• deleted. Right-click on an intermediate vertex to popup the corresponding menu,

• moved. Left-click on a vertex to select it, move it and left-click again to fix it.

FIGURE 5.4.1-1 Move/Add vertex

Once the edge is correctly positioned, right-click to quit the editing tool. All the channel is recom-puted according to the modification as shown in the following figure where the hub is representedby a green dashed line (representation mode when the hub is not completely mapping on basiccurves).

FIGURE 5.4.1-2 New hub definition

5-4.2 Non-Axisymmetric Hub/Shroud

The end walls of a usual turbomachinery configuration are defined by axisymmetric surfaces. Thegeometry of these end walls are defined by the hub and shroud curves in meridional coordinates.When the real end walls are non axisymmetric surfaces, the mesh is obtained in two steps:

• generate an axisymmetric mesh,

• axisymmetric mesh adaptation to the specified non-axisymmetric end walls.

Please refer to dedicated tutorial for more details.

Right-click

Leading Edge

Trailing Edge


AutoGrid5™ 5-15

FIGURE 5.4.2-1 Non-axisymmetric end walls

In addition to the axisymmetric hub and shroud curves defining the meridional domain, 3D surfaces defin-ing the non-axisymmetric end walls must be defined. These can be directly specified in the ".geomTurbo"file or imported through the Import CAD window of AutoGrid5™.

5-4.2.1 From ".geomTurbo" File

The non-axisymmetric surfaces are stored in external IGG™ data file and specified into the ".geomTurbo"file using the following format:

NI_BEGIN NINonAxiSurfaces hub NAME non axisymmetric hub REPETITION 3 EXTERNAL nonaxihub.datNI_END NINonAxiSurfaces hubNI_BEGIN NINonAxiSurfaces shroud NAME non axisymmetric shroud REPETITION 0EXTERNAL nonaxihub.datNI_END NINonAxiSurfaces shroud

non axisymmetric hub definition

non axisymmetric shroud definition

Geometry Definition Hub/Shroud Edition

5-16 AutoGrid5™

Any type of surface created and stored by IGG™ can be used to defined the non-axisymmetric endwalls.

5-4.2.2 From Import CAD

The non-axisymmetric surfaces can be imported from external CAD files. The contextual menu ofthe import window allows the user to link imported surfaces to the hub and/or shroud definition.

FIGURE 5.4.2-2 Import CAD contextual menu for non-axisymmetric end walls

5-4.2.3 Mesh Generation Control

The non-axisymmetric end walls generation is controlled into the Row Properties dialog box.

FIGURE 5.4.2-3 Row properties dialog box

The options Non-Axisymmetric Hub & Shroud are used to enable or disabled the mesh adapta-tion on the specified non axisymmetric surfaces.

If the non axisymmetric surfaces do not intersect the axisymmetric mesh, the 3D mesh needs to beprojected on the end walls. This can be done in two ways:

• Projection Along Grid Line. The mesh is projected on the end walls based on the spanwisegrid line direction. This method allows to avoid non matching connections that may appearwhen using the Projection Along the Face Normal.


AutoGrid5™ 5-17

• Projection Along the Face Normal (active by default). The mesh is projected on the end walls,based on the normal direction of the hub or shroud face. This method leads to a better meshquality.

The option Repair Non-projected Points allows to correct non-well projected points (i.e. when themesh points on boundaries are close to hub or shroud surface limits).

The options Display Non-Axisymmetric Hub & Shroud are used to display the surfaces in the 3Dview.

To obtain a correct behaviour, the surfaces must cover all the hub or shroud blade to blade domainof the axisymmetric mesh. If the specified surfaces do not cover the entire domain as shown in thenext figure, the Geometry Repetition options allow the user to repeat the entered surfaces by rota-tion until the new surfaces cover the domain.

FIGURE 5.4.2-4 Surfaces repetition ensure full domain covering.

At the end of the 3D blade row generation, the mesh adaptation is performed automatically. Theaxisymmetric mesh is adapted by hub to shroud grid points redistribution along the curve obtain byintersecting the surfaces with the hub to shroud grid lines.

Hub blade to blade domain is not cover by the surface definition

Surface repetition ensure the blade to blade domain covering

Geometry Definition Blade Edition

5-18 AutoGrid5™

5-5 Blade Edition

5-5.1 Blade Expansion

The Blade Expansion dialog box is accessed by right-clicking on the selected blade in the maingraphics area and by selecting Expand Geometry from the list of commands. An alternate methodconsists in right-clicking over the Main Blade (splitter) in the Rows Definition subpad of theQuick Access Pad, then in selecting Expand Geometry from the list of commands.

FIGURE 5.5.1-1 Blade Expansion dialog box

5-5.1.1 Force Blunt at Leading Edge

Force blunt at leading edge is used to specify whether or not the blade geometry has to be consid-ered as blunt in the region of the leading edge.

5-5.1.2 Force Blunt at Trailing Edge

Force blunt at trailing edge is used to specify whether or not the blade geometry has to be consid-ered as blunt in the region of the trailing edge.

5-5.1.3 Stick Leading/Trailing Edge

Stick leading & trailing edge is used to fit leading and trailing edge of pressure and suction sidesalong the spanwise direction when the leading and/or trailing edge are very curved (i.e. inducer,twisted blade,...) and the blade is defined by few sections in ".geomTurbo". In such cases, a discon-tinuous shape in the blade-to-blade view may result when reconstructing the section. This option isby default deactivated.

5-5.1.4 Apply a Rotation

Apply a rotation is used to rotate the blade around a user-defined axis, but is only available fornative ".geomTurbo" blades. The axis and anchor point fields expect three floating point coordi-nates while the angle value is given in degrees.

Blade Edition Geometry Definition

AutoGrid5™ 5-19

� This item is not available if the blade has been linked by mean of the CAD import tool.

5-5.1.5 Sewing Tolerance

Sewing tolerance is used to define a tolerance value during CAD import, in order to sew the surfaces thatdefine the blade. The default tolerance value is set as 1e-006. Too small value may leave many unwantedholes/gaps, while too large value can end up making some faces disappear, and can also lead to unwantedgaps.

5-5.1.6 Expansion at Hub

An optional expansion can be applied when the blade geometry has to be extended towards the hub surfaceof revolution. Four options are available.

a) Unchanged

This choice is the default and leaves the original blade surfaces unchanged or restores the original surfaceswhen another option was previously activated.

b) Expand

An expansion can be specified by the user when the blade geometry has to be extended towards the hubsurface of revolution in order to make it intersects the hub definition.

• In case of native "geomTurbo" format, the input value is treated as an expansion factor.

• In case of geometry definition through CAD import, two input boxes appear: Cut offset and Extensionoffset. These inputs allow respectively to define the absolute hub offset to cut the blade and the abso-lute blade extension over the hub.

FIGURE 5.5.1-2 Definition of blade offset from hub with schematic sketch

Axis(dx,dy,dz)

Anchor Point(x,y,z)

Angle(θ in degree)

HUB

SHROUD

BLADE

cut offset

extension offset


5-20 AutoGrid5™

c) Treat blend

When the blade geometry and the hub surface of revolution connect tangentially by mean of ablend, a special treatment needs to be applied in order to ensure proper intersection computationbetween the blade and the hub.

The method used to handle such cases can be summarized as follows:

• Creation of a virtual hub created by an offset of the hub surface of revolution according to userspecified parameter(s).

• Intersection of the blade and the virtual hub.

• Extension of the blade geometry towards the hub surface of revolution starting from these inter-section curves. The extension is performed tangentially to the blade geometry and ensures thatthe new blade geometry and the hub do intersect.

• The blade geometry is replaced by this new definition and any dependent configuration entity isupdated, e.g. the leading and trailing edges are modified to remain consistent with the new bladegeometry definition.

With this input method, the cutting offset is built from the curvature radius of the blend and theminimum angle at which the blade should intersect the hub.

d) Treat blend with offset

This treatment consists in the same steps as treat blend, but the cutting offset is input directly as adistance.

5-5.1.7 Expansion at Shroud

An optional expansion can be applied when the blade geometry has to be extended towards theshroud surface of revolution. Four options are available.

a) Unchanged

This choice is the default and leaves the original blade surfaces unchanged or restores the originalsurfaces when another option was previously activated.

b) Expand

An expansion can be specified by the user when the blade geometry has to be extended towards theshroud surface of revolution in order to make it intersects the shroud definition.

• In case of native "geomTurbo" format, the input value is treated as an expansion factor.

• In case of geometry definition through CAD import, two input boxes appear: Cut offset andExtension offset. These inputs allow respectively to define the absolute shroud offset to cut theblade and the absolute blade extension over the shroud.

c) Treat blend

When the blade geometry and the shroud surface of revolution connect tangentially by mean of ablend, a special treatment needs to be applied in order to ensure proper intersection computationbetween the blade and the shroud.

The method used to handle such cases can be summarized as follows:

• Creation of a virtual shroud created by an offset of the shroud surface of revolution according touser specified parameter(s).


AutoGrid5™ 5-21

• Intersection of the blade and the virtual shroud.

• Extension of the blade geometry towards the shroud surface of revolution starting from theseintersection curves. The extension is performed tangentially to the blade geometry and ensuresthat the new blade geometry and the shroud do intersect.

• The blade geometry is replaced by this new definition and any dependent configuration entity isupdated, e.g. the leading and trailing edges are modified to remain consistent with the new bladegeometry definition.

With this input method, the cutting offset is built from the curvature radius of the blend and theminimum angle at which the blade should intersect the shroud.

d) Treat blend with offset

This treatment consists in the same steps as treat blend, but the cutting offset is input directly as adistance.

5-5.2 Blade Fillet

The blade geometry can be connected to the hub or shroud surface of revolution by means of a fil-let. The Fillet Properties dialog box is accessed by right-clicking on the selected blade or row in themain graphics area and by selecting Define Hub Fillet or Define Shroud Fillet from the list ofcommands. An alternate method consists in right-clicking over the row or the Main Blade (split-ter) in the Rows Definition subpad of the Quick Access Pad, then in selecting Define Hub Fillet orDefine Shroud Fillet from the list of commands.

FIGURE 5.5.2-1 Fillet Properties dialog box

The method used to add a fillet to the blade can be summarized as follows:

• Creation of a virtual hub or shroud created by respectively an offset (radius at leading/trailingedge) of the hub or shroud surface of revolution according to user specified parameter(s) or anexternal curve by activating the Defined Shape option and selecting a simple ".dat" file throughthe button Select Geometry File. The Show/Hide buttons allow to preview the user definedcurve used for the fillet before generating the flow paths.

• Intersection of the blade and the virtual hub or shroud.


5-22 AutoGrid5™

• Extension of the blade geometry up to the hub or shroud surface of revolution starting fromthese intersection curves and respecting the radius imposed at leading/trailing edge.

• When the minimum angle is reached locally, the blade geometry is extended tangentially to theblade geometry defined at this location and ensures that the new blade geometry and the hub orshroud do intersect.

• Control of the fillet clustering by giving the cell width and the number of constant cells (Per-centage of Mid-flow Cells). By default the fillet clustering is computed using a hyperbolic tan-gent spanwise distribution.

• The blade geometry is replaced by this new definition and any dependent configuration entitydepending on it is updated, e.g. the leading and trailing edges are modified to remain consistentwith the new blade geometry definition.

FIGURE 5.5.2-2 Fillet parameters: radius & angle

When the fillet has been added, popup menu is available in the Rows Definition subpad of theQuick Access Pad when right-clicking on Hub Fillet or Shroud Fillet items allowing to modify thesettings of the fillet or to delete the fillet.

FIGURE 5.5.2-3 Fillet popup menu

Minimum Angle

BLADE

HUB


AutoGrid5™ 5-23

5-5.3 Leading/Trailing Edge Wizard

The leading and trailing edge curves can be defined by the user by adding a wizard to the blade through theblade menu Add Wizard LE TE. This menu will add an item Wizard LE TE in the blade configurationtree.

The wizard is started when selecting the menu Start after right-clicking on the new item.The wizard iscomposed be a set of dialog boxes. Each dialog box is related to the setup of a set of parameters and con-tain buttons Cancel, OK, <<Back, Next>> or Finish to control the set up process:

• The Cancel button suppresses all the parameters already set by the wizard.

• The OK button is used to quit the wizard and keep the parameters already set.

• The <<Back button is used to return to the previous dialog box

• The Next>> button is used to go the next dialog box.

• The Finish button (only in last dialog box) is used to quit the wizard and launch the 3D generation.

5-5.3.1 Control Layers Definition

When starting the wizard, the dialog box controlling the layers is opened and the default layers are dis-played in the meridional view.


5-24 AutoGrid5™

a) Control Layer Limits

The default layer limit can be controlled through the parameters Upstream control layer limit andDownstream control layer limit. Their values are given in relative arc length location on the hub.

� A visual control should be performed in the meridional view to ensure that the layercover the domain of the blade definition.

b) Control Layer Clustering

The clustering at hub and shroud (Hub clustering/Shroud clustering) is controlled by giving aratio of the cell width corresponding to a uniform distribution of the layer.

AutoGrid5™ uses a geometrical progression to define the layer from hub to shroud. In addition, theuser can control the percentage of cell of constant width (% of Constant Cells), the number of lay-ers and the number of control points used to defined each layer.

c) Global Layer Control

When the blade has a very high staggered angle close to 90°, the technology that uses dm/r mini-mum and maximum value is no more suitable. The options Very low leading edge angle and Veryhigh leading edge angle allow the user to switch to a more suitable technology (using theta mini-mum and maximum).

When the blade does not cut the hub and/or the shroud, the user can specify that the first and the lastcontrol layer must not be taken into account to compute the leading and the trailing edge by deacti-vating respectively the options Use First Control Layer and Use Last Control Layer.

Uniform Clustering Hub/Shroud Clustering set to 0.5


AutoGrid5™ 5-25

d) Expert Layer Control

The tolerance used to create the chord at leading or/and trailing edge can be decreased especially in case ofblade with a large width at leading and/or trailing edge.

The number of iterations steps and the number of points used to create the chord can also be controlled.

The Debug mode option allows the user to show the chord computed at each iteration and the intersectionpoints used to compute the leading and the trailing edges. This can be useful to identify the area where theoscillations appear in the chord in case of circular leading or trailing edge.

5-5.3.2 Leading/Trailing Edge Location Definition

When the button Next>> is pressed in the Leading Edge & Trailing Edge: Control Layer dialog box, defaultleading edge and trailing edge locations are computed and displayed in the XYZ view and the dialog boxLeading Edge & Trailing Edge: Edges Control is opened.


5-26 AutoGrid5™

a) Active Layer

By default, all the layers are activated (displayed in yellow). The Active layer (0:all) parameters can be usedto select the layer on which the values of the following parameters will be applied. When the value is notequal to 0, the active layer is automatically displayed in yellow and the others ones in blue.

b) Edge Location Control.

By default, AutoGrid5™ computes a location for the leading and trailing edge in 8 steps:

1. Generation of the control layer in the meridional plane,

2. Intersection between the control layer and the blade definition,

3. Projection of the intersection in the blade-to-blade plane (dm/r,theta),

4. Generation of the chord using as limit the dm/r minimum and maximum value by default,

5. Limit the chord using the blade width as reference cut distance,

6. Extend the chord to obtain a first location of the leading and trailing edge,

7. Repeat steps 4 to 6 to refine the location of the leading and trailing edge.

8. Finally, cspline curves (joining all the leading edge and trailing edge points defined from the projection inthe XYZ space of the points defined in the B2B space) are created and expanded using first order prolonga-tion.

The parameters Leading Edge Location and Trailing Edge Location allow the user to modify the defaultlocation by giving a deviation of its parametrical position on the blade intersection. The parameters can varyfrom 0 to 1.

1

2

3

456


AutoGrid5™ 5-27

c) Edge Expansion Control

The parameters Hub Expansion and Shroud Expansion control the expansion of the leading edgeand trailing edge curves in percentage of the spanwise height.

d) View B2B & Solid Body

The option View B2B switch the visualization from the 3D view in a blade-to-blade view.

The option View Solid Body allows to visualize the solid body of the blade in the 3D view.

The button Finish is used to replace the current definition of the leading and trailing edge curves bythe one created by the wizard. The options Update Leading Edge and Update Trailing Edge areused to choose if the leading, trailing or both edges must be replaced.

� The wizard is not available for blunt leading and trailing edge.


5-28 AutoGrid5™

5-5.4 Sheet on Blade

A sheet can be added on the blade by right-clicking on the selected blade in the main graphics area andby selecting Define Sheet from the list of commands. An alternate method consists in right-clickingover the Main Blade (splitter) in the Rows Definition subpad of the Quick Access Pad, then in select-ing Define Sheet from the list of commands.

� The sheet on blade is not compatible with sharp treatment, control lines on blade, throat con-trol and conjugate heat transfer/cooling options.

In the meridional plane, AutoGrid5™ imposes flow paths at the upper and lower sheet limit, while inthe blade-to-blade view, AutoGrid5™ imposes grid point clustering at the upstream and downstreamlimits. The blade sheet is defined by 5 geometry characteristics: i

• the upper and lower limits,

• the upstream and downstream limits,

• the sheet width.


AutoGrid5™ 5-29

In the Sheet Lower/Upper Zone dialog boxes available by right-clicking over the Lower/Upper Zone inthe Rows Definition subpad and selecting Properties, the upper and lower limit control is performedusing a way similar to the tip gap. For both, the user can control the width and clustering in the spanwisedirection through a dialog box identical to the dialog box used to control the gap or the fillet.

� The lower/upper zone are identical for all the blades of the same row.

In the Blade Sheet Properties dialog box available by right-clicking over the Sheet in the Rows Definitionsubpad and selecting Properties, the upstream, downstream limits and the sheet width can be controlled.

Lower Side, Upper Side, Both Side. A sheet can be added on the lower, the upper or on both sides of theblade.

Distance From Leading/Trailing Edge. The sheet upstream and downstream limits are defined by givinga distance from the leading and the trailing edge along the blade chord.

Streamwise Npts Near Leading/Trailing Edge. The streamwise number of points can be controlledbefore and after the sheet definition (N1,N2). The number of points on the sheet is equal to the number ofpoints on the blade lower side and/or on the blade upper side - (N1+N2-2).

Upper Zone

Lower Zone


5-30 AutoGrid5™

Width. The sheet width can be controlled. The skin block width is equal to the sheet width (w) multiply by 2.Mid-clustering is imposed to capture the boundary layer of the sheet. The optimization of the skin block isswitched off.

5-5.5 Non-Axisymmetric Shroud Gap

In AutoGrid5™, meshing a multisplitter configuration with different tip gap heights is possible at the condi-tion that tip gap meridional profiles do not intersect and that there is enough space between each of them to beable to insert mesh layers (flow paths).

In order to overcome this limitation, a technique similar to hub and shroud non-axisymmetric treatment (sec-tion 5-4.2) is available for non-axisymmetric tip gap. When the real tip gap is defined by non-axisymmetricsurfaces, the mesh is obtained in two steps:

• generate a mesh with an axisymmetric tip gap,

• axisymmetric mesh adaptation to the specified non-axisymmetric tip gap.

� The axisymmetric gap curve should be lower than the non-axisymmetric surfaces in order that thegap mesh intersects these surfaces. Otherwise gap spanwise grid lines should be extended to inter-sect these surfaces and it will lead to a non matching connection with the channel mesh.

Sheet

N1

Sheet

w

Skin Block

2 x w


AutoGrid5™ 5-31

FIGURE 5.5.5-1 Non-axisymmetric shroud gap

In addition to the axisymmetric curve defining the shroud gap, 3D surfaces defining the non-axisymmet-ric shroud gap must be defined. These can be directly specified in the ".geomTurbo" file or importedthrough the Import CAD window of AutoGrid5™.

� To obtain a correct behaviour, the non-axisymmetric surface(s) defining the shroud gap:

+ should cover all the domain (blades + channel parts),

+ should cross all the blades including the non-axisymmetric shroud gap,

5-5.5.1 From ".geomTurbo" File

The non-axisymmetric surfaces are stored in external IGG™ data file and specified into the ".geom-Turbo" file using the following format:

NI_BEGIN NINonAxiSurfaces tip_gap NAME non axisymmetric tip gap REPETITION 3 EXTERNAL nonaxitipgap.datNI_END NINonAxiSurfaces tip_gap

Any type of surface created and stored by IGG™ can be used to defined the non-axisymmetric shroudgap.

5-5.5.2 From Import CAD

The non-axisymmetric surfaces can be imported from external CAD files. The contextual menu of theimport window allows the user to link imported surfaces to the shroud gap definition.


5-32 AutoGrid5™

FIGURE 5.5.5-2 Import CAD contextual menu for non-axisymmetric shroud gap


The non-axisymmetric shroud gap generation is controlled into the Row Properties dialog box.

FIGURE 5.5.5-3 Row properties dialog box

The option Non-Axisymmetric Shroud Gap is used to enable or disabled the mesh adaptation onthe specified non axisymmetric surfaces.

The option Repair Non-projected Points allows to correct non-well projected points (i.e. when themesh points on boundaries are close to hub or shroud surface limits).

The option Display Non-Axisymmetric Shroud Gap is used to display the surfaces in the 3Dview.

To obtain a correct behaviour, the surfaces must cover all the domain (blades + channel parts) of theaxisymmetric mesh. If the specified surfaces do not cover the entire domain, the Geometry Repeti-tion option allows the user to repeat the surfaces by rotation until the new surfaces cover thedomain.

At the end of the 3D blade row generation, the mesh adaptation is performed automatically. Theaxisymmetric mesh is adapted by hub to shroud grid points redistribution along the curve obtain byintersecting the surfaces with the hub to shroud grid lines.

Cascade Configuration Geometry Definition

AutoGrid5™ 5-33

5-6 Cascade ConfigurationBy default, AutoGrid5™ is generating a mesh in an axisymmetric configuration turbomachine.When creating a new project (File/New Project), a cascade configuration can be generated afteractivating the Cascade option.

This type of configuration is defined by a translation periodicity instead of a rotation periodicity.

The geometry can be defined through Import CAD window in the same way as for an axisymmetricconfiguration after defining the geometry reference axis and origin (Edit/Geometry Axis...).

By default, the stream and span directions are respectively the Z- and X-directions.

In addition, the cascade configuration geometry can be defined using a ".geomTurbo" file, wherethe channel and blades are defined similarly as for an axisymmetric configuration after setting thecascade parameter to yes on the top of the file.

When the geometry is defined, in the Row/Properties contextual menu, a rational value for thepitch distance between two successive blades (Periodicity) can be defined instead of the number ofblades imposed for an axisymmetric configuration.

FIGURE 5.6.0-1 Cascade Configuration - Periodicity

d = 57

Geometry Definition Blade Geometry Check

5-34 AutoGrid5™

The mesh controls and generation are similar to the method used for an axisymmetric configuration.

FIGURE 5.6.0-2 Cascade Configuration - 3D Mesh

5-7 Blade Geometry Check

5-7.1 Check Geometry

Once the properties of the blade geometry are defined, the user can check the correctness of the defini-tions of the blade geometry using the Blade Geometry Check dialog box. This dialog box is availablefrom the Check Geometry option in the contextual menu, and appears by right-clicking on the MainBlade or Splitter in the Rows Definition subpad of the Quick Access Pad. When the dialog box isopened, the blade sections and orientations are automatically displayed in the 3D view.

The progress status displays a report about the blade definition status when the Check button is selected.During the geometry check of a blade, AutoGrid™ performs the following operations:

• check blade definition.

• check orientation of the blade section curves.

• loop detection into the blade section curves.

• loop detection between the blade sections.

5-7.1.1 Blade Definition Check

Using this checking criterion, blade surface definition is checked. Check Geometry (Import CAD)

In addition, when the blade is defined by multiple surfaces using Import CAD window, a single body willbe created using a tolerance to fill the potential holes between the surfaces defining the blade. Whenclicking on the Check button, AutoGrid5™ checks if the body can be created within the specified toler-ance. If not, the tolerance is automatically adapted and the user can manually increase the tolerance incase of failure.

Blade Geometry Check Geometry Definition

AutoGrid5™ 5-35

5-7.1.2 Streamwise Orientation Check

The blade sections must be streamwise oriented. If the hub and shroud are defined, AutoGrid™warns the user if the blade section is not correctly oriented.

� This checking is available for ".geomTurbo" native format only.

5-7.1.3 Loop Detection - Distance Check

The distance check in loop detection process warns the user if the Control Points Distance Crite-ria is reached. The default value of the distance between 2 consecutive blade sections control pointsis 1e-006.


5-7.1.4 Loop Detection - Angle Check

The angle check in loop detection process warns the user if the Control Points Angle Criteria isreached. The default value of the angle between 3 consecutive blade sections control points is 90.0.


Geometry Definition Blade Geometry Check

5-36 AutoGrid5™

5-7.2 Adapt Geometry

Once the blade geometry is checked, the blade definition can be adapted by performing the follow-ing actions:

• data reduction, so as to remove potential loops,

• blade rotation around the Z axis,

• re-orientation of the blade sections,

• data reduction using the distribution of control points.

5-7.2.1 Data Reduction

A data reduction of the blade sections curve is performed if the Data Reduction option is selected.The points detected in the loop search process are removed from the blade section definition.

� This process is available for ".geomTurbo" native format only.

5-7.2.2 Blade Sections Interpolation Loops

A second check is done on intermediate blade section curve to see if the interpolation of the sec-tions does not contain loops.

If the loops are detected in the intermediate curve section, then the loop locations are displayed inthe 3D view. A warning indicates that interpolation is wrong and contains loops. Problem of inter-polation often arises due to the way the sections are defined and in particular the control points dis-tributions on the sections. It is strongly advised to define the control points as smooth as possible. Ifthis process does not work, the Blade Geometry Check dialog box can be used to redistribute thecontrol points on each section by activating the option Control Points Redistribution. When theoption is checked, the blade sections are automatically recomputed based on a user-defined controlpoint distribution. The parameters controlling the distribution are the following:

1. Control Points Number on the Leading Edge.

2. Control Points Number on the Middle.

3. Control Points Number on the Trailing Edge.

4. Number Of Constant Cells on the Middle.

5. Control Points Spacing at Leading Edge.

6. Control Points Spacing at Trailing Edge.

FIGURE 5.7.2-1 Control points redistribution settings

A geometric progression is used to assume minimum expansion ratio between the control points tominimize the risk of loops after sections interpolation. In 99% of the test cases, after selecting theCheck button and discovering interpolation loop for one time, the default values provided byAutoGrid5™ gives appropriated results.

Blade Geometry Export Geometry Definition

AutoGrid5™ 5-37

This option can also be really useful in case of very accurate data entered for each section by theuser. This can be a reason of the slowness of the intersection process. To improve, Control PointsRedistribution option can be tried.

� This process is available for ".geomTurbo" native format only.

5-7.2.3 Blade Rotation

A blade section rotation is applied around the Z-axis using the angle specified in the OriginalBlade Data Rotation Angle input data field.

� This option is available for ".geomTurbo" native format only.

5-8 Blade Geometry ExportThe Export Geometry is a very useful feature to export blade geometry definition in ".geom-Turbo" format. The created file contains the blade defined by two surfaces (pressure and suctionside). Each surface is defined by a set of cross sections (set of control points). This file can be alsoused as a pre-processor of the blade fitting process of AutoBlade™ in case of blades defined byexternal CAD data files.

The user can access the Export Geometry option from the contextual menu, available by rightclicking on Main Blade or Splitter in Rows Definition subpad of the Quick Access Pad. It opensthe Export Blade Geometry dialog box.

FIGURE 5.8.0-1 Export Blade Geometry dialog box

The dialog box consists of the following features,

• Selection of Use Flow Path Definition check box allows to compute one blade section on eachflow path defined in the meridional view.

Geometry Definition Blade Geometry Export

5-38 AutoGrid5™

• Selection of Export Original Data check box allows to export the original data available in the".geomTurbo" file.

� This option is available only if the original blade geometry data exists in a "geomTurbo"format.

• Set the Number Of Sections to define the number of blade sections to be computed in theexported ".geomTurbo" file.

• Set the Number Of Points Near Leading Edge to define the number of control points at theleading edge.

� This option is not taken into account for blunt or sharp leading edge.

• Set the Number Of Points On Blade Sides to define the number of control points on pressureand suction sides of the blade.

• Set the Number Of Points Near Trailing Edge to define the number of control points at thetrailing edge.

� This option is not taken into account for blunt or sharp trailing edge.

• The clustering law between the leading edge area and the trailing edge area is defined by:

• The Number of Cst Cells. This number has to be less than the number of control points onthe blade sides defined in the Number Of Points On Blade Sides data input field.

• The Clustering At Leading Edge, defined as the normalized length of the leading edgearea.

• The Clustering At Trailing Edge, defined as the normalized length of the trailing edgearea.

• Selection of Export End Wall Definition check box allows to save the end wall definitions,such as, hub and shroud flow paths polyline definition.

The Preview button is used to display in the 3D view the computed sections of the blade geometryto be exported.

The Export button allows to export the computed sections in a ".geomTurbo" file. The file is savedin the parent directory where the project or template is saved. The name of the file is computedautomatically using the name of the template, the name of the row, the name of the blade and theparameters use to define the sections. This assumes that a unique name is used for any kind ofexport process.

� If there is any blank space in the parent directory path, AutoGrid5™ does not allow toexport the ".geomTurbo" file and displays an error message.

AutoGrid5™ 6-1

CHAPTER 6: Meridional Control

6-1 OverviewThe meridional space allows first to control the geometry of a machine and the related parameters:

• Basic curves: these are general 2D meridional curves.

• Channel curves: hub, shroud, nozzle. They are based on basic curves, i.e. lying on them.

• Rotor/stator curves. They define the row domain in the streamwise direction.

• Meridional control lines. Optional control lines geometrically similar to rotor/stator. They canhave a role in all meshes (meridional, blade to blade and 3D).

The meridional space allows also to control the flow paths used to create the 3D revolution surfacesfor the final mesh.

6-2 Geometry Control

6-2.1 Basic Curves

Basic curves are 2D meridional curves which can be used to define channel curves (hub, shroud ornozzle) and meridional technological effects. They are defined as general NURBS curves and thendiscretized to be used as polylines.

a) Creation

Basic curves can be created through the ".geomTurbo" file (more details in Chapter 3) or throughthe import CAD facility (more details in Chapter 5).

Meridional Control Geometry Control

6-2 AutoGrid5™

b) Discretization

Basic curves can be discretized through the right-click popup menu. The following dialog box willappear:

Enter the number of discretization points desired between each basic curve control points. Severalbasic curves can be selected to change the discretization in one time. All channel curves using themodified basic curve will be updated and all rotor/stators and control lines recomputed if necessary.

c) Deletion

Basic curves can be deleted through the right-click popup menu when basic curve highlighted inmeridional view.

d) Check Geometry

Basic curves can be checked through a Channel Geometry Check dialog box. This meridionalgeometry checking process helps to check the completeness of the geometry as well as the validityof the end walls, before starting the mesh generation. It is also useful as it could repair the curveswherever it is required.

Geometry Control Meridional Control

AutoGrid5™ 6-3

6-2.2 Hub - Shroud - Nozzle

Once defined, all these channel curves can be controlled interactively to change their shape and/or orienta-tion. The control is accessible from the Edit Hub - Edit Shroud - Edit Nozzle menus of the Quick AccessPad Geometry Definition subpad or directly by right-clicking on a basic curve.

The control is done through the editing of an edge and its vertices.

FIGURE 6.2.2-1 Shroud editing

Vertices can be:

• added. Use the <i> shortcut,

• deleted. Right-click on an intermediate vertex to popup the corresponding menu,

• moved. Left-click on a vertex to select it, move it and left-click again to fix it.

FIGURE 6.2.2-2 Vertices options

<i>

Left-click Right-click


6-4 AutoGrid5™

Once the edge is correctly positioned, right-click to quit the editing tool. All the channel is recom-puted according to the modification as shown in the following figure:

FIGURE 6.2.2-3 Channel regenerated

� When hub/shroud/nozzle are not completely mapping the basic curves, there are repre-sented by a green dashed line (see Figure 5.4.1-2).

6-2.3 Rotor/Stator

Rotor/stators define the limits of a row, either the interface between two rows or the inlet or outletof a row. They are created automatically when initializing the configuration (defining the rows) andcan be controlled once the geometry is defined. They are displayed in blue in the meridional view.

A rotor/stator is defined by a set of control points which are allowed to move on a "support curve".There are two means to control a rotor/stator: directly through the control points or through the ded-icated dialog box.

FIGURE 6.2.3-1 Rotor/stator control points

Left-click

Right-click


AutoGrid5™ 6-5

To display the control points, simply left-click on a rotor/stator (Figure 6.2.3-1) and then left-clickto move them. To open the dialog box (Figure 6.2.3-2), right-click on it and select Properties in thepopup menu.

FIGURE 6.2.3-2 Rotor/stator properties dialog box

6-2.3.1 Properties

The dialog box is divided in two main parts, allowing to control the shape of the rotor/stator andother properties.

The Reference frame allows to specify the frame on which the position of the rotor/stator depends.For consistency reasons, when switching to absolute frame, the rotor/stator shape is switched tocurvilinear.

• Absolute. The rotor/stator control points are relative to the channel (i.e. the hub and shroud).

• Relative. The rotor/stator control points are relative to the rotor/stator neighbouring rows (i.e.the trailing edge of the previous row and the leading edge of the following row).

The shape frame contains four buttons. Each modification in the shape frame updates automaticallythe rotor/stator and its control points in the graphical area.

• Linear. Impose a linear shape. Additionally the rotor/stator can be located at a R or Z constantposition by activating the corresponding button and entering the desired value.

• Curvilinear. Just for information, does not change the current shape, it indicates that a controlpoint was moved manually.

• Defined Shape. This button is activated if the rotor/stator was defined by an external curve. Anexternal curve can be imposed by selecting a simple ".dat" file through the button Select Geom-etry File. When imposed by a file, the location of the rotor/stator will be defined in a totallyabsolute position. It also means that if the hub or shroud changes, it should still intersect the userdefined rotor/stator.

• Default. Optimized shape computed, i.e. a straight line between hub and shroud when the rotor/stator is the machine inlet or outlet, otherwise a curve located at midway between two rows.

The second part of the dialog box specifies several properties; only the first one Cell width is use-ful for a rotor/stator, it imposes the cell size in the blade to blade mesh at the rotor/stator location. Adefault optimized value is always computed, symbolised by "0.0" in the dialog box.


6-6 AutoGrid5™

6-2.3.2 Control Points Editing

Each control point of a rotor/stator can be moved on a "support curve" automatically created, which shape isfixed and cannot be changed (this "support curve" is not displayed). The number of control points is fixedand cannot be changed neither.

To move a control point:

1. Move the mouse to the desired control point. It will be highlighted when close enough. Then left-click.

2. Subsequent mouse movement will move the control point. The rotor/stator is automaticallyupdated. The control point can be moved from the upstream row trailing edge to the downstreamrow leading edge. If there is no upstream or no downstream row, the limit is a straight line goingfrom the hub extremity to the shroud extremity.

3. Left-click again to fix the control point position.

A specific (R,Z) position can also be imposed for a control point:

1. Move the mouse to the desired control point. It will be highlighted when close enough. Then right-click.

2. The following dialog box will be opened. Enter the desired (R,Z) values. The control point and therotor/stator will be updated.

FIGURE 6.2.3-3 Control point (R,Z) control

3. Once the dialog box is opened, another control point can be selected to change its (R,Z) coordi-nates. Simply left-click on it, its current coordinates will be updated in the dialog box.

4. Close the dialog box.

6-2.4 Meridional Control Lines

Control lines can be added in meridional space to control the meridional mesh (spanwise flow paths distri-bution), to change the topology of the 3D mesh (additional H block created upstream or downstream thecontrol line) or to impose a z constant line in the meridional space (i.e. to capture corner). They are dis-played in blue in meridional view.

FIGURE 6.2.4-1 Meridional control line example

Corner to capture

Right-click


AutoGrid5™ 6-7

� Using this feature, the seal leakage defined at the trailing edge of a blunt centrifugalimpeller can now be connected using matching connection (see Chapter 9).

6-2.4.1 Creation

A tool is dedicated to the creation of meridional control lines ( or ).

Once activated, move the mouse on a channel curve (hub, shroud or nozzle) in the meridional view.When close enough, a point is displayed on the channel curve. Left-click to create a meridional con-trol line at this position. This operation can be repeated until the tool is quit by right-clicking.

6-2.4.2 Deletion

Right-click on a meridional control line to popup the Delete menu item.

6-2.4.3 Edition

Meridional control lines are very similar to rotor/stators. They are also defined by a set of controlpoints which are allowed to move on a "support curve". Therefore they can be edited in the samemanner as for rotor/stators: directly through the control points by left-clicking on it or through thededicated dialog box (Figure 6.2.4-2) by right-clicking on it and select Properties in the popupmenu.

6-2.4.4 Properties

The properties of a meridional control line can be controlled through the dedicated dialog box, thesame as for rotor/stators:

FIGURE 6.2.4-2 Control lines properties dialog box


6-8 AutoGrid5™

• The dialog box is divided in two main parts. For Reference frame, when it is set to Relative, thecontrol points are relative to a row and their reference depends on the position of the control line.Either the control points are relative to the row inlet and its blade leading edge, either to the lead-ing and trailing edge, or to the blade trailing edge and the row outlet. When it is set to Absolute,the control points are relative to the channel (i.e. the hub and shroud).

The second part of the dialog box allows to control the properties of the meridional control line:

• Cell width imposes the cell size in the blade to blade mesh at the control line location. A defaultoptimized value is always computed, symbolised by a zero in the dialog box.

• Streamwise Index is used when the control line is located on a blade and specifies the index ofthe mesh line corresponding to the control line location in the blade to blade view.

• Streamwise Npts is used when the control line is not located on a blade and specifies the numberof streamwise points in the H block upstream or downstream the control line in the blade to bladeview if, respectively, the control line is upstream or downstream from the blade.

• B2B control specifies if the meridional control line should also be a blade to blade control line.

FIGURE 6.2.4-3 Control lines upstream and downstream from the blade

FIGURE 6.2.4-4 Control line located on blade

Streamwise Npts

Streamwise Npts

Control lines

H blockdownstream

H blockupstream

Cell width imposedaround control line

Control line on blade,shape z constant

Streamwise Index


AutoGrid5™ 6-9

• Fixed Geometry specifies if the blade to blade control line should be a z constant line or can berelaxed and have the shape obtained by the optimizer (blade to blade control line is considered as a zcst line instead of a normal connection).

FIGURE 6.2.4-5 Control line blade to blade geometry

6-2.4.5 Specific Cases: Bypass, Fin & Bulb

Meridional control lines are created automatically in three specific cases to capture discontinuity gener-ated by a bypass engine, a fin and/or bulbs. In these three cases, the specific meridional control lines can-not be deleted and some control points cannot be moved.

A bulb is a specific region of a machine where the hub has a zero radius. A machine can have a bulb at itsinlet and/or its outlet.

Bulbs are automatically detected, the condition being that the hub has a zero radius at one point (not aline). The domain is automatically extended from this point at zero radius to the shroud axial positionextremity. One or two meridional control lines are automatically created, the first one representing themachine inlet (outlet), the second one to capture either the zero radius point for sharp topology (H-topol-ogy) or the limit between the radial and the axial domain for radial topology. The hub extension allows tomove the meridional control lines before the bulb. The rotor/stator (inlet) of the row following the bulb ispositioned after the control line capturing the zero radius point or the limit between the radial and axialdomain, and should not be moved before it (the opposite if the bulb is at the outlet of the machine). Thezone between the entry control line and the rotor/stator is the bulb region and its meshing is controlledthrough a specific dialog box dedicated to the bulb.

FIGURE 6.2.4-6 Bypass case

H blockdownstream

H blockupstream Fixed geometry,

shape z constant

Geometry not fixed,shape optimized,not z constant

Control linesautomaticallycreated. Cannot bedeleted

Control points onnozzle cannot bemoved


6-10 AutoGrid5™

FIGURE 6.2.4-7 Bulb case

If a control line is added between the fan and the nozzle, the user can unfix the geometry. Neverthe-less undefined or non-matching instead of matching connections can be detected at the connectionbetween the downstream blocks. In case of problems (non-matching or undefined patches) the addi-tional control line must be fixed again.

� Furthermore, in case of a geometry defined in "millimeter", the tolerance used to definethe connection in the Patch Selector dialog box (Grid/Boundary Conditions menu) canbe increased to obtain matching connections.

� In bypass configuration, it is mandatory to have an inlet fan upstream of the nozzle.

Control line automatically created

This control line cannot be deletedThe control point at zero radius cannot be moved.

Hub automatically extended

Machineinlet

Row rotor/stator (bulb outlet)

Sharp Topology

Radial Topology


Machineinlet

Row rotor/stator (bulb outlet)Control lines automatically created


Machineinlet

Row rotor/stator (bulb outlet) Control lines automatically created

Rounded Topology


AutoGrid5™ 6-11

FIGURE 6.2.4-8 Fin case

� When a fin is defined, the two control lines defining the leading and the trailing edge of the fin,must be defined with a unique cell width.

6-2.5 Channel Control

AutoGrid5™ automatically creates support channel curves to define the location of the control linesincluding inlet, outlet and rotor-stator. The number of points of the support curves is automatically com-puted by AutoGrid5™. If necessary, when the default control lines are not well defined on hub and shroud,the number of points can be adapted by the user.

6-2.6 Meridional Curve Checks

During loading or importing of ".trb" or ".geomTurbo" files, AutoGrid5™ automatically checks the hub,shroud or nozzle curves. It also checks the curves, which are imported from the Import CAD window. If itdetects any discontinuity in the curve of more than 80°, a warning message appears.

A Channel Geometry Check dialog box is also accessible from the Check Meridional Curves button in theGeometry Definition subpad of the Quick Access Pad or directly by right-clicking on the curves andselecting the Check Geometry menu. This meridional geometry checking process helps to check thecompleteness of the geometry as well as the validity of the end walls, before starting the mesh generation.It is also useful as it could repair the curves wherever it is required.

Control lines automatically created.Cannot be deleted

Control points on fin cannot be moved

Meridional Control Mesh Control

6-12 AutoGrid5™

FIGURE 6.2.6-1 Channel geometry check

Selection of the Check All Meridional Curves check box allows to check all the meridional curvesat once, otherwise the selected meridional curve can be checked one by one. The Check buttonapplication computes the Minimal Distance and the Maximum Angular Deviation between twocurve control points either for all the curves or for the selected curve. While computing for all themeridional curves, the name of the curve also appears on which the minimum distance and maxi-mum angular deviation exist as shown in Figure 6.2.6-1.

Also the potential failures due to coincident points and/or discontinuity on channel curves using theData Reduction option can be treated. This option removes the coincident points or discontinuitybased on the Control Points Distance Criteria and Control Points Angle Criteria provided bythe user.

� The data reduction process is reversible, as the original curve retrieves once the DataReduction check box is deselected.

� Meridional curve checking process cannot detect the discontinuity between two curvesdefined in the meridional plane.

6-3 Mesh ControlAfter defining the setup of the project (section 3-4.2), AutoGrid5™ will define for each selectedrow the number and the distribution of the flow paths automatically when using the button (Re)setDefault Topology of the top menu bar.

Afterwards, the flow paths are mainly controlled row by row and some interactions are availablebetween rows.

Mesh Control Meridional Control

AutoGrid5™ 6-13

The number of flow paths for a row is controlled separately through the Quick Access Pad in theMesh Control subpad. Other row parameters for flow paths control are controlled through the dia-log box by left-clicking on Flow Path Control in Mesh Control subpad.

6-3.1 Flow Paths Control

The dialog box is divided in two main parts, a first part controlling flow paths spanwise distributionand a second expert part allowing to tune some parameters, useful in some specific cases. Allparameters are applied for the selected rows.

• Cell width at Hub controls the cell size imposed at the hub.

• Cell width at Shroud controls the cell size imposed at the shroud.

• Percentage of Mid-flow Cells controls the number of cells of constant size in the main part ofthe channel (excluding gaps).

• View Flow Path allows to visualize the grid used to generate the flow paths. Deactivate the but-ton to display the grid.

• Flow Paths Control Points Number controls the streamwise number of points of the grid usedto generate the flow paths. Can be increased if the machine is very long. This number of pointswill also be the number of control points of the flow paths.

• Number Of Intermediate Points controls the number of discretization points between eachcontrol point of the flow paths.

• Smoothing Steps controls the number of iterations for flow paths smoothing.

• Hub & Shroud Distribution Smoothing controls the number of iterations for points distribu-tion smoothing.

• Hub Control Points Distribution controls the distribution of flow path control points on thehub. The distribution can be uniform or concentrated around curvature.


6-14 AutoGrid5™

• Shroud Control Points Distribution controls the distribution of flow path control points on theshroud. It can be the same distribution as on the hub, a distribution obtained from an orthogonalprojection of the hub points on the shroud, or a distribution obtained from the minimal distancewith hub points (hub closest points on the shroud).

FIGURE 6.3.1-1 Flow paths dialog box

The dialog box contains four buttons at the bottom:

• Generate allows to generate the flow paths of the selected rows.

• Clear Manual Operations cleans all manual operations performed through the manual editmode for the selected rows (does not include copy/merge distributions).

• Manual Edit starts the flow paths manual editing tool. It is activated for all the rows. Refer tonext section for more details.

• Close closes the dialog box.

6-3.2 Flow Paths Manual Editing

Manual editing allows to control directly the block faces which are used to construct flow paths.Edges can be moved, segments can be created or modified and grid points distribution on segmentscan be controlled. As block faces need to be created for editing, flow paths of the row to be control-led should be generated before activating the tool.

The manual editing tool is started by pressing the button Manual Edit of the Row:Flow Paths Con-trol dialog box (Figure 6.3.1-1). It is stopped by right-clicking in the meridional view or by closingthe dialog box. Once activated, all edges, vertices and fixed points of the rows for which flow pathsare generated appear.

Following operations are available:

• face selection. Left-click on face edges to select the face,

• vertex displacement on rotor/stators and meridional control lines. Left-click on a vertex to selectit, move it, left-click again to fix its new position.


AutoGrid5™ 6-15

FIGURE 6.3.2-1 Vertex displacement on vertical edge

• fixed point insertion. Right-click on a vertical edge to popup the Divide edge menu item. It will launch thefixed point insertion tool.

• fixed point deletion. Right-click on a fixed point to popup the Delete menu item.

• fixed point displacement on vertical edges. Left-click on a fixed point to select it, move it, left-click againto fix its new position.

FIGURE 6.3.2-2 Fixed point insertion on vertical edge

• fixed point index change. Right-click on a fixed point to popup the Change index menu item.

• control of the segment distribution on vertical edges. Right-click on an vertical edge to popup the Distri-bution menu item. It will open the Clustering dialog box.

FIGURE 6.3.2-3 Manual editing activated

Vertexdisplacement

Fixed pointinsertion

Right-clickRight-click


6-16 AutoGrid5™

After each operation, faces mesh are regenerated basically (i.e. without smoothing) to display directly thechanges on flow paths shape. To regenerate completely the faces (including smoothing), regenerate theflow paths of the row.

Some vertices and fixed points cannot be moved, they are displayed in blue to indicate it.

All manual edit operations can be deleted for a row by pressing the button Clear Manual Operations inthe Row:Flow Paths Control dialog box (Figure 6.3.1-1). Then flow paths generation becomes the defaultone again.

6-3.3 Hub/Shroud Gaps Control

Gaps are controlled through their dedicated dialog box. It allows to control the geometry and the meshingparameters of the gap.

FIGURE 6.3.3-1 Gap dialog box

• Topology. It allows to control the topology in the gap. By default HO topology is selected corre-sponding to a butterfly topology in the gap. When meshing an inducer presenting a sharp leading andtrailing edge, the H (Sng. Line) will be selected.

• Defined Shape. This button is activated if the gap curve was defined by an external curve. An exter-nal curve can be imposed by selecting a simple ".dat" file through the button Select Geometry File.

• Width At Leading Edge - Width At Trailing Edge. It allows to specify the size of the gap at theleading and trailing edge of the blade. The gap curve is then constructed as a linear offset of the hub(or the shroud) according to these values. If the gap curve is externally defined, these values arepurely for information and cannot be changed.

• Cell width controls the cell size imposed at the blade extremity (at the hub or shroud according to thegap type).

• Percentage of Mid-flow Cells controls the number of cells of constant size in the gap region of thechannel.

• Number of Points controls the number of points in the gap in the spanwise direction.

The buttons Show/Hide allow to preview the user defined curve used for the gap before generating theflow paths.

The button Generate Flow Paths is used to regenerate the flow paths in the gap row respecting the modi-fications done in the dialog box.

6-3.4 Blade Fillet

The blade geometry can be connected to the hub or shroud surface of revolution by means of a fillet. Seesection 5-5.2 for more details about the fillet construction and the flow paths control.


AutoGrid5™ 6-17

6-3.5 Bulb Control

For the mesh control of the bulb, more details are presented in section 6-2.4.5. Two specific dialog boxesare dedicated to bulbs, one for the inlet, the other one for the outlet, both dialog boxes being totally similar

( and ). Three topologies are available for bulbs: sharp, rounded or radial.

• With the sharp topology, the mesh in the bulb area is divided into two blocks limited by the inlet of therow and the bulb domain limit and separated by the stagnation line. This topology leads to a mesh pre-senting a singular line in front of the stagnation point.

• With the rounded topology, the bulb area can be meshed with a singular line (triangular cells) or a but-terfly topology. The mesh is then divided into respectively 3 or 5 blocks limited by the inlet of the rowand the bulb domain limit. The Butterfly Smoothing Steps controls the number of iterations to smooth the butterfly bulb area.The Smoothing Steps controls the number of iterations for flow paths smoothing in the bulb.

Sharp Topology Rounded Topology Radial Topology

Singular LineButterfly

Topology


6-18 AutoGrid5™

• With the radial topology, the mesh in the bulb area is divided into two butterfly topology (blocksB1&B2 and B3&B4): a butterfly topology for the radial area of the bulb domain and one for thestreamwise area of the domain.The Butterfly Smoothing Steps controls the number of iterations to smooth the butterfly bulbarea.

The various number of points can be changed by left-clicking on their representation in the dialogbox. An entry box like the following one will popup, press <Enter> to validate the new number ofpoints or <Esc> to close the box and leave the number of points unchanged.

The button Preview Flow Paths is used to regenerate the flow paths in the bulb respecting the mod-ifications done in the dialog box.

� If meridional control lines are added in the bulb, the number of points is controlled inaddition through the dialog box Row Interface Properties (Figure 6.2.4-2). The Stream-wise Npts is controlling, if the meridional control line is respectively at inlet or outlet,the streamwise number of points down or up to the meridional control line.

6-3.6 Bypass Control

For the geometry control of the by-pass, more details are presented in section 6-2.4.5. Two topolo-gies are available for by-pass: H or C mesh around the nozzle. A specific dialog box is dedicated to

by-pass ( ):

• Topology Type allows to choose the H or C topology.

• Nozzle Cell Width controls the cell size imposed at the nozzle.

• Nozzle Index controls the index of the flow path corresponding to the stagnation point of thenozzle, i.e. it controls the proportion of the flow paths below and above the nozzle.


AutoGrid5™ 6-19

FIGURE 6.3.6-1 Bypass dialog box

For the C topology, a various number of points can be changed by left-clicking on their representation inthe dialog box. An entry box like the following one will popup, press <Enter> to validate the new numberof points or <Esc> to close the box and leave the number of points unchanged.

Besides the number of points, two additional controls are available: the C mesh thickness and the spacingbetween meridional control lines on the nozzle, both are expressed as a percentage. For the C mesh thick-ness, it is a percentage of the spanwise size below the nozzle, for the spacing between control lines, it is apercentage of the nozzle thickness (nozzle thickness is a dimension automatically computed according tothe geometry).

The dialog box also displays information about the total number of flow paths in the by-pass: number offlow paths before the nozzle, downstream and upstream from the nozzle. It allows an easier generation ofa matching mesh (matching flow paths) with downstream rows.

The button Preview Flow Paths is used to regenerate the flow paths around the nozzle to display the mod-ifications done in the dialog box.

FIGURE 6.3.6-2 C-mesh (left) & H-mesh (right) topology around nozzle

Topology Type

Meridional ControlLines Spacing

Nozzle Index

Radial

in C MeshNr of points

C MeshThickness


6-20 AutoGrid5™

6-3.7 Fin Control

For the geometry control of the fin, more details are presented in section 6-2.4.5.

� Only fin on fan in a by-pass configuration is allowed.

The dialog box dedicated to by-pass is used to control the fin ( ):

• Fin Index controls the index of the flow path corresponding to the stagnation point of the fin,i.e. it controls the proportion of the flow paths below and above the fin.

• Fin Cell Width controls the cell size imposed at the fin.

FIGURE 6.3.7-1 Bypass - Fin dialog box

6-3.8 Copy - Merge Distributions

Besides the flow paths generation row by row, the copy-merge options allow to obtain matchingflow paths in the spanwise direction at row interfaces.

Copy/Paste are used to copy a distribution from a rotor/stator to another one or to a meridionalcontrol line.

Merge is used to compute a common distribution from the left and right distributions at a rotor/sta-tor. This option is only available for a rotor/stator interface with both hub and shroud gap: e.g.where the left row has a hub gap and the right row a shroud gap (or the opposite).

Clear is used to clean copy/merge operations on selected control line.

Copy/Merge/Clear are accessible through the right-click popup menu on a rotor/stator or meridi-onal control line:


AutoGrid5™ 6-21

• To copy a distribution, move the cursor on the desired rotor/stator from which the user wants tocopy, right-click and press Copy Left Distribution or Copy Right Distribution according tothe side the user wants to copy. Then move the cursor on the desired rotor/stator where the userwants to change the distribution, right-click and press Paste Left Distribution or Paste RightDistribution according to the side the user wants to modify. To modify the distribution on ameridional control line, just press Paste Distribution.

• To merge a distribution, move the cursor on the desired rotor/stator the user wants to merge,right-click and press Merge Distributions.

• To delete all copy/merge operations done on a rotor/stator or meridional control line, right-clickand press Clear Distribution(s).

6-3.8.1 Conditions of Use

• Flow paths need to be generated before copying or merging.

• The distributions to be copied or merged should have the same number of points.

• For the by-pass case with C-mesh topology for the nozzle, the distributions of the fan outletscannot be copied neither merged, as illustrated on the picture below.

FIGURE 6.3.8-1 Forbidden copy-merge operations

6-3.8.2 Representation

Copy-merge operations are symbolized in the meridional view by a text marker on the middle of therotor/stators or meridional control lines:

• C -> L means that the distribution on the left side of the rotor/stator was copied.

• C -> R means that the distribution on the right side of the rotor/stator was copied.

• <- C -> means that the distribution on both sides of the rotor/stator was copied.

• M means that distributions on the rotor/stator were merged.

• C means that the distribution on the meridional control line was copied.

Fan rotor/stator

merge or copy

forbidden if Cmesh topology atnozzle

FANon the left side


6-22 AutoGrid5™

FIGURE 6.3.8-2 Copy-merge meridional representations

6-3.9 Mesh Quality Checks

When the meridional view is active (red border), the menu Grid/Grid Quality allows to control thequality of the flow paths (more details in section 2-3.4.3).

Distributions mergedRight distribution copied Left distribution copied

M MC->R C->L

AutoGrid5™ 7-1

CHAPTER 7: Blade to Blade Control

7-1 OverviewThe 3D mesh created by AutoGrid5™ is obtained by stacking blade to blade meshes on the surfacesof revolution (layers) created by rotation of the flow paths defined in the meridional view of the tur-bomachinery.

The blade to blade meshes are created in the (dm/r,theta) space: the cross-sections of the bladeswith the active layers are projected in the blade to blade space and the mesh is created around theblade sections according to the pitch angle and the inlet and outlet boundaries of the row (moredetails in Chapter 3).

FIGURE 7.1.0-1 Blade to blade mesh

The blade to blade meshes are created using a two dimensional multiblock structured topology.Each block have four edges along which grid points are distributed. The grids inside the blocks arecreated by transfinite interpolation and finally optimized using an elliptic multiblock smoother.

Blade to Blade Control Overview

7-2 AutoGrid5™

FIGURE 7.1.0-2 five blocks topology and grid point clustering

AutoGrid5™ provides two different modes to create the topology of the blade to blade meshes:

• to use predefined topologies for which grid points clustering is chosen automatically accordingto some geometrical criteria and grid level. The predefined topologies have been developed toobtain high quality grid without any user interaction. They are divided in two main types:HHOHH (O4H), HOH and H&I. The O4H type ensures full automatic meshing for all kind ofturbomachinery while the HOH and H&I types give very high quality grids but is not suitablefor all the applications. Afterwards, the user can interact to change the resulting topology.

• to create manually the topology as well as the grid points clustering (user defined topology).

In both modes, the template approach of AutoGrid5™ ensures reusability of the automatic or man-ual settings on similar geometries.

This chapter describes first how to set up a predefined topology and how the user can interact tochange the optimized blade to blade topology defined by AutoGrid5™ (from section 7-3 to 7-5).The user defined topology mode is presented in section 7-6. Finally, the optimization controls aredescribed in section 7-7.

Blade to Blade Topology Management Blade to Blade Control

AutoGrid5™ 7-3

7-2 Blade to Blade Topology Management

7-2.1 Overview

The selection of the predefined blade to blade topology is controlled through the dialog box availa-ble through the menu Mesh Control/Row Mesh Control/B2B Mesh Topology Control in theQuick Access Pad.

FIGURE 6.2.1-1 Define B2B Topology

All the changes performed in this dialog box apply to the active blade(s).

7-2.2 Topology Selection

On the top of the Define B2B Topology for Active Blade dialog box, the topology of the selectedblade can be selected between the three predefined types available in AutoGrid5™ (O4H, HOH andH&I) or in the blade to blade topology library.

When defining the blade topology from scratch using a predefined topology (O4H, HOH and H&I),after imposing the setup of the project (section 3-4.2), AutoGrid5™ will create an optimized topol-ogy according to some geometrical criterion and the grid level when using the button (Re)setDefault Topology of the top menu bar.

Rotor 37Aachen TurbineLSCC

DefaultDefaultDefault

Available topologies

B2B topology library

Library management

Topology control

Grid points control

Boundary layer & Initial mesh control

Intersection control

Blade to Blade Control Blade to Blade Topology Management

7-4 AutoGrid5™

Afterwards, the option Streamwise Weights in the menu Mesh Control/Grid Level allows toincrease the number of grid points in the streamwise direction respectively at the inlet, on the bladeand the outlet of the optimized topology. The feature consists in multiplying the number of gridpoints at inlet, on the blade and at outlet by the streamwise weights when using the button (Re)setDefault Topology. This option is only available for O4H and H&I topology.

Finally, the user can interact to adapt the optimized blade to blade topology defined byAutoGrid5™ by changing the parameters in the Define B2B Topology for Active Blade dialog box(from section 7-3 to 7-5) and in the Optimization Properties dialog box (section 7-7).

In addition, the topology library on the top of the Define B2B Topology for Active Blade dialog box(Figure 6.2.1-1) can be used or an existing topology can be copied (section 7-2.3).

This library contains all the previous saved topologies. The library is managed using the followingfeatures:

• Select a topology: to load a predefined topology, select it in the list and press the button Load. Awarning prompts the user to regenerate and display the mesh in the blade to blade view.

• Save a topology: To save the topology of the current active blade, press the button Save. Thedialog box Save B2B Topology is opened.

inlet

blade

outlet

Blade to Blade Topology Management Blade to Blade Control

AutoGrid5™ 7-5

In this dialog box, the user can overwrite a topology selected in the list or create a new item inthe library by switching on the button New B2B topology name. In this case, a new topologyname must be entered in the related area and the topology will appear in the topology libraryand will be saved in "~/.numeca/tmp/" (in the folder "/_NITurboB2BTopologyLibrary/" and inthe file "NIbladeToBladeTemplateLibraryFiles").

• Remove a topology from the list (Remove button)

• Preview the selected topology (Preview button): this feature opens a new window inside whicha picture of the selected topology is displayed.

Furthermore, in the popup menu of the row, a row topology library is available through the Topol-ogy Library menu.

FIGURE 7.2.2-1 Save a B2B topology

In this dialog box, the topology of the selected row can be selected from the blade to blade rowtopology library. This library contains all the previous saved row topologies. The library is man-aged using the following features:

• Select a topology: to load a predefined topology, select it in the list and press the button Load. Awarning prompts the user to regenerate and display the mesh in the blade to blade view.

• Save a topology: To save the topology of the current active row, press the button Save. The dia-log box Save Row Topology is opened. In this dialog box, the user can overwrite a topologyselected in the list or create a new item in the library by switching on the button New Row topol-ogy name. In this case, a new topology name must be entered in the related area and the topol-ogy will appear in the topology library and will be saved in "~/.numeca/tmp/" (in the folder "/_NITurboRowLibrary/" and in the file "NRowTemplateLibraryFiles").

• Remove a topology from the list (Remove button)

• Preview the selected topology (Preview button): this feature opens a new window inside whicha picture of the selected topology is displayed.

� The blade to blade library is used to apply the topology from one row to another. To copythe blade to blade topology from one blade to another, the Copy/Paste Topology optionof the blade menu should be used (see section 7-2.3).

Blade to Blade Control Blade to Blade Topology Management

7-6 AutoGrid5™

� The predefined topology applied from scratch or selected in the library or copied on theblades of the active row(s) is (re)initialized using the button (Re)set Default Topology.An optimized blade to blade topology is chosen and the grid points distributions are(re)computed based on the setup of the project (section 3-4.2), the grid level and the geo-metrical criterion.

7-2.3 Copy/Paste Topology

The blade to blade topology applied around a blade row or a row can be copied into the activebuffer and applied to other blade row or row using the copy/paste feature available through the con-textual menu of the blade and the row.

FIGURE 7.2.3-1 Blade & row contextual menu

Using this feature, In multistage configuration, the blade to blade topology can be set up for oneblade or row and applied to all the other similar blades or rows.

� To copy the blade to blade topology from one blade to another, use the Copy/PasteTopology option of the blade menu.

� The predefined topology applied from scratch or selected in the library or copied on theblades of the active row(s) is (re)initialized using the button (Re)set Default Topology.An optimized blade to blade topology is chosen and the grid points distributions are(re)computed based on the setup of the project (section 3-4.2), the grid level and the geo-metrical criterion.

bladerow

Default Topology (O4H Topology) Blade to Blade Control

AutoGrid5™ 7-7

7-3 Default Topology (O4H Topology)The default topology is selected through the top left selection button of the dialog box Define B2BTopology For Active Blade.

FIGURE 7.3.0-1 Default topology selection

7-3.1 Default Topology Control

As mentioned previously in this chapter, the default topology is composed by 5 blocks:

1. a O block around the blade named skin block

2. a H block upstream the leading edge of the blade named inlet block

3. a H block downstream the trailing edge named outlet block

4. a H block up to the blade section named up block

5. a H block down to the blade section name down block

FIGURE 7.3.1-1 Defaults blocks & grid points

7-3.1.1 Control Number of Grid Points

The grid points number depends of the grid level and the streamwise weights chosen in the quickaccess pad page Mesh Control/Grid Level before performing the initialization ((Re)set DefaultTopology).



(4)

(5)

(1)(2) (3)

Blade to Blade Control Default Topology (O4H Topology)

7-8 AutoGrid5™

These optimized grid points numbers can be changed in the Grid Points page of the dialog boxDefine B2B Topology For Active Blade (Figure 7.3.1-1). To change a number, left-click on it, enterthe new number of points in the locally displayed input area and <Enter> to confirm or <Esc> tocancel the action.

FIGURE 7.3.1-2 Grid points distribution

� To display the new blade to blade mesh, press the button of the top menu bar GenerateB2B.

FIGURE 7.3.1-3 Default mesh

Up blockOutlet block

Inlet block

Down block

Skin block

Non matching connection


AutoGrid5™ 7-9

7-3.1.2 Control Periodic Boundary Condition Type

As shown in Figure 7.3.1-3, the periodic boundary of the default mesh is non-matching. To obtain amatching periodic boundary condition, switch on the check button Matching Periodicity in theTopology page of the dialog box Define B2B Topology For Active Blade and press the button(Re)set Default Topology or Generate B2B.

FIGURE 7.3.1-4 Control the periodic connection

7-3.1.3 Control Skin Mesh Clustering around the Blade

The O-block around the blade is used to optimize the control of the boundary layer on the blade. Itis created using an hyperbolic mesh.

FIGURE 7.3.1-5 Hyperbolic mesh around the blade

Matching connection

Hyperbolic mesh


7-10 AutoGrid5™

a) Grid Point Number Control

The number of grid points along the solid wall is controlled within the page Grid Points of the dia-log box Define B2B Topology For Active Blade. The grid points clustering along the solid wall issplit in four pieces controlling the leading edge, the trailing edge, the upper side and the lower sideof the blade.

FIGURE 7.3.1-6 Grid points number control

b) Leading Edge & Trailing Edge Clustering Control

The clustering near the leading edge and/or the trailing edge can be fully controlled through the dia-log box Blade Clustering Control. When moving the mouse near the leading edge or the trailingedge, the piece of clustering controlled is automatically highlighted. The length of the piece isnamed "control distance". The inlet/outlet grid points are uniformly distributed along this distance.

FIGURE 7.3.1-7 Leading edge control distance

Leading Edge

Control

Upper Side Control

Lower Side Control

Trailing Edge

Control

Control distance

Right-click


AutoGrid5™ 7-11

Right-clicking when a control distance is highlighted opens a contextual menu. The menu Proper-ties opens the dialog box Blade Clustering Control.

FIGURE 7.3.1-8 Blade clustering control

The control distance along which the grid points are distributed can be modified by selecting themode of specification and the distance value:

1. Absolute Control Distance: the distance is given in absolute units and remain the same foreach layer.

2. Relative Control Distance: the distance is given in relative units (normalized with the bladewidth).

3. First Cell Length: the distance is equal to the product of the cell width given by the user andthe number of nodes.

The control distance is combined with a percentage of cells along the blade that will present a con-stant size (Percentage Cst Cells).

Another feature of this dialog box gives the control of the maximum expansion ratio of the cells inthe streamwise direction along the wall. Switch on the button Desired Expansion Ratio implies thatthe number of grid points on the upper and lower side of the blade will be recomputed to ensure thatthe expansion ratio remain lower than the target value. The total number of points around the bladeis then continuously updated.

c) Move Leading Edge & Trailing Edge Location

When moving the mouse near the leading or trailing edge, the control distance is highlighted indi-cating that it is ready for selection. Left-click (without release) and drag it on the desired locationthen release. The mesh of the skin block is continuously updated during the moving process.

FIGURE 7.3.1-9 Move stagnation point location

Control distance

Expansion ratio control


7-12 AutoGrid5™

d) Control Boundary Layer in the Skin Mesh.

The skin block is created using a hyperbolic mesh. The width of the boundary layer is controlled bythe cell width at the wall, the expansion ratio and the number of points in it. These parameters canbe modified in the page Mesh and Grid Points of the dialog box Define B2B Topology.

FIGURE 7.3.1-10 Boundary layer control

� When AutoGrid5™ detects that the boundary layer width is too big for the geometryconfiguration, it prompts the user to confirm the automatic reevaluation of the expansionratio to a correct value.

� When the blade section has a curved shape, crossing grid lines in the hyperbolic meshcan be detected by AutoGrid5™ and it automatically prompts the user to change theexpansion ratio manually to avoid crossing section.

When activating the option Cell Width at Wall Interpolation, AutoGrid5™ allows to impose acell width different at the hub & shroud of the machine, especially when the speed of the flowbecomes very different at the hub and at the shroud of the machine.

The user inputs the cell width at the hub and the shroud and the boundary layer width. For eachlayer, AutoGrid5™ computes the local cell width (Celllocal) and the local expansion ratio (ERlocal)

using a linear interpolation between the hub and the shroud. The variable used to compute the inter-polation is the relative spanwise location (from 0 to 1) of the layer at the leading edge.

Boundary layer controls

Number of points in Boundarylayer


AutoGrid5™ 7-13

Celllocal = 10x(log10(cell hub)+(log10(cell shroud)-log10(cell hub))*spanwiseLocation)

Bnd. Layer Width = (1+ERlocal+ERlocal2+…+ERlocal

n-2)xCelllocal

with n equal to the number of cells in the boundary layer.

When the option is active, the Expansion ratio and the Cell Width at Wall field are not available formodification. Each time the button Generated B2B is pressed, these fields show the local cell width and thelocal expansion ratio used to compute the blade-to-blade mesh on the active layer.

7-3.1.4 Control Hub/Shroud Gap Mesh

When gap(s) has been defined, AutoGrid5™ adds automatically two new blocks to mesh the domain up ordown to the blade(s). The mesh inside a gap has a butterfly topology: a H block surrounded by a O blockare used to discretize this area.

By default, the gap meshes matches the skin mesh around the blade. Therefore, the only control gives tothe user is the number of points inside the O-block that can be modified in the page Grid Points of the dia-log box Define B2B Topology for Active Blade.

� If the number of points on the upper side and on the lower side of the blade is changed and if agap has to be defined, the change is cancelled automatically by AutoGrid5™ when pressing thebutton Generate B2B to ensure a matching connection between the gap meshes and the skinmesh around the blade.

� When imposing sharp (section 7-3.1.5) at the blunt blade leading/trailing edge (i.e. inducer), a Htopology will be automatically used. The H topology is not available if the number of points isnot equal on the pressure and the suction side of the blade.

FIGURE 7.3.1-11 Butterfly mesh in gap

O block

H blockN

O Mesh Control


7-14 AutoGrid5™

7-3.1.5 Blend/Sharp/Rounded Treatment at Leading/Trailing Edge

In case of blunt blades, AutoGrid5™ automatically detects the bluntness of the blade and the optionto blend, sharp or rounded the blunt blade leading/trailing edge appear in the Topology page of theDefine B2B Topology for Active Blade dialog box.

FIGURE 7.3.1-12 Blend/sharp/rounded treatment option at leading/trailing edge

The selection of the options Sharp Treatment At Leading Edge and Sharp Treatment At Trail-ing Edge automatically closes the blunt edges by a linear edges as shown in Figure 6.3.2-14 Thisnew topology replace the O block around the blade by two H blocks and is recommended forinducer configuration.

FIGURE 7.3.1-13 Effect of sharp leading/trailing edge treatment

The selection of the options Blend the Blade At Leading Edge and Blend the Blade At TrailingEdge automatically closes the blunt edges by a circular shape edges as shown in Figure 7.3.1-14.


AutoGrid5™ 7-15

FIGURE 7.3.1-14 Effect of blend treatment at leading/trailing edge

The selection of the options Rounded Treatment At Leading Edge and Rounded Treatment AtTrailing Edge automatically closes the blunt edges by a straight line to obtain a O-mesh around theblade.

FIGURE 7.3.1-15 Effect of rounded treatment at leading/trailing edge

7-3.1.6 Grid Points in Throat

When the blade is presenting a blunt at the leading and trailing edge, AutoGrid5™ allows an auto-matic control of the number of grids points in the throat by setting the Number of Points In Throatto 1. This parameter can be modified in the page Grid Points of the dialog box Define B2B Topol-ogy for Active Blade and is controlling part of the number of points along the blade as presented onnext figure.


7-16 AutoGrid5™

FIGURE 7.3.1-16 Number of points in throat

For example, when dealing with inducer configuration, in the Define B2B Topology for Active Bladedialog box:

• The Matching Periodicity and the High Staggered modes with High-Low or Low-High Inlet/Outlet Type are imposed in the Topology page,

• The Number of Points in Throat is set to 1 to optimize the blade to blade mesh by an automaticcontrol of the blade points distribution in the throat.

� Throat control is not applicable for multi-splitter configuration.

� Backward is ensured with the previous releases in which the grid points were imposed man-ually in the throat.

When Number of Points In Throat is set to 1, the leading and trailing edge clustering is projected onthe opposite side of the blade using an algorithm using the blade staggered angle. When the staggeredangle is significantly different at inlet and outlet, the option Accurate throat projection can be acti-vated to improve the projection location.

The parameters Inlet/Outlet Projection Relaxation can be used to relax the clustering at the projectionlocation especially when the blade is blunt. It allows to control manually the projection points clusteringof the blade by multiplying the default clustering with the value specified in the entry.

1

Throat

RelaxationRelaxationset to 1 set to 13


AutoGrid5™ 7-17

7-3.1.7 Wake Control

The direction of the mesh downstream the trailing edge can be controlled to capture the wake. Bydefault the wake control is switch off. When the Wake Control check box is selected, the WakeRelative Angle can be imposed in the page Mesh of the dialog box Define B2B Topology for ActiveBlade. The edges of the outlet block are created using straight lines. The angle between thesestraight lines and the dm/r axis is equal to the solid angle + the wake relative angle specified in thedialog box. Figure 7.3.1-17 describes the geometrical detail and the mesh control when modifyingthe wake relative angle feature.

FIGURE 7.3.1-17 Wake control - relative angle

Furthermore, the Wake Prolongation in Downstream Block check box allows to propagate thewake in the downstream H-block (created when a control line is added downstream the trailingedge of the blade). It improves the quality of the mesh downstream of the trailing edge.

FIGURE 7.3.1-18 Wake control - Prolongation

Solid Angle

Solid Angle

Wake Relative Angle

Solid Angle

Solid Angle

Wake Relative Angle

Control Line

Control Line

Control Line

Control Line


7-18 AutoGrid5™

7-3.1.8 Inlet & Outlet Boundary Control

The inlet and outlet boundaries of the blade to blade mesh are located at theta positions computed automati-cally using a parabolic function. If the blade is twisted, the computed values are different for each layer.Therefore the inlet and the outlet surfaces of the 3D mesh can be also twisted.

FIGURE 7.3.1-19 Twist of the inlet 3D boundary

The angle deviation at the inlet and/or the outlet is important and the mesh quality can be seriously affectedalong the spanwise direction. To avoid this phenomenon at the inlet/outlet boundary limit of the mesh, newcontrols have been added in the Mesh page of the dialog box Define B2B Topology for Active Blade. If theFree Inlet/Outlet Angle mode is switched off, the user can freeze the inlet/outlet angle and mesh usingrespectively the Frozen Inlet/Outlet Angle and the Frozen Inlet/Outlet Mesh options. These options con-strain the inlet/outlet optimization and force the mesh at the boundary.

FIGURE 7.3.1-20 Inlet and outlet boundary control

7-3.1.9 Relax Inlet & Outlet Clustering

When Z cst lines are defined upstream or downstream to the blade, upstream and downstream H-blocks arecreated. By default the azimuthal clustering at the control line is extended up to the inlet or the outlet in theblade-to-blade mesh.

In case Z cst lines are defined upstream or downstream to the blade, AutoGrid5™ automatically detects thecontrol lines and new options are available in the Mesh page in the Define B2B Topology for Active Bladedialog box.


AutoGrid5™ 7-19

The Relax Inlet/Outlet Clustering options allow to relax the clustering in the azimuthal directionstarting from the control line up to the inlet or the outlet.


7-20 AutoGrid5™

7-3.1.10 Blunt at Leading/Trailing Edge

In case of blunt blades, AutoGrid5™ automatically detects the bluntness of the blade and newoptions are available in the Mesh page in the Define B2B Topology for Active Blade dialog box.

� This option is not available for staggered topology.

• ZCst line at Leading Edge: Selection of this option defines a Z constant line at the leadingedge.

• ZCst line at Trailing Edge: Selection of this option defines a Z constant line at the trailingedge.

� Zcst line at the leading edge or trailing edge cannot be combined with respectively highstaggered topology at the leading or trailing edge.

� Zcst line should be added at the leading or trailing edge location in the meridional viewto ensure that the flow paths are respecting the shape of the hub and shroud at the leadingor trailing edge. The B2B control option of this control line should be deactivated.

FIGURE 7.3.1-21 Effect of Z constant line in case of blunt leading and trailing edges

• Cell Width At Leading Edge: This entry allows the user to specify the width of the cell at theblunt leading edge. By default the value is set to -1.0 when no user control is applied.

• Cell Width At Trailing Edge: This entry allows the user to specify the width of the cell at theblunt trailing edge. By default the value is set to -1.0 when no user control is applied.


AutoGrid5™ 7-21

� This option is not available for staggered topology.

FIGURE 7.3.1-22 Cell width control at blunt edge

7-3.2 Topology for High Staggered Blades

7-3.2.1 Overview

In several turbomachinery types, the blades are highly staggered. If the solid angle at the inlet (out-let) of the machine becomes greater than 45° and if the location of the inlet (outlet) limits of thedomain is close to the leading edge (trailing edge) of the blades, then the O4H topology is not suit-able anymore: the cells located near the inlet (outlet) boundary becomes very skewed.

FIGURE 7.3.2-1 High staggered blade

To improve this unexpected behaviour, AutoGrid5™ uses the High Staggered Blade Optimizationin the Topology page of the dialog box Define B2B Topology for Active Blade (Figure 7.3.2-3).

solid angle > 450

Inlet close tothe leading edge

Skewed cells


7-22 AutoGrid5™

7-3.2.2 High Staggered Blade Topology Optimization

FIGURE 7.3.2-2 C topology at inlet

When the topology is (re)initialized using the button (Re)set Default Topology, AutoGrid5™ detectsif the two conditions described in the Figure 7.3.2-1 are reached. In this case, AutoGrid5™ auto-matically adapts the default topology to optimize the grid quality: if the solid angle at inlet is lowerthan 0, the H upper block becomes a C-block.

The high staggered blade topology optimization is controlled in the page Topology of the dialogbox Define B2B Topology for Active Blade. The optimization can be switch off through the optionHigh Staggered Blade Optimization to retrieve the default topology (Figure 7.3.2-1). The auto-matic search of the two geometric conditions can be switch off through the button Automatic HighStaggered Blade Detection. In this case, the user has to specify manually which are the inlet and/oroutlet geometrical configuration: Normal, Low Angle or High Angle (Figure 7.3.2-1 is presentinga low inlet angle test case).

FIGURE 7.3.2-3 High staggered optimization control

The following figure is presenting the description of the different types of geometrical configura-tion and their corresponding inlet and outlet types.

C-block


AutoGrid5™ 7-23

FIGURE 7.3.2-4 Blade types

7-3.2.3 Grid Points - Periodic Boundary - Gap Control

When a C-mesh is defining the upper block at inlet, the grid point number on the upper side of theblade and the grid points number at the inlet of the upper side are linked.

The number N1 cannot be greater than N2. When a periodic matching boundary is requested, thenumber of points N1 is always different of N3. Therefore, if a gap mesh is defined, a non-matching

normal - normal normal - low angle normal - high angle

low angle - high angle low angle - low angle high angle - normal

high angle - low angle high angle - high angle low angle - normal


7-24 AutoGrid5™

connection will be automatically used to create the connection between the H-block and the O-blockinside the butterfly mesh.

FIGURE 7.3.2-5 High staggered topology & periodic boundary

7-3.3 Tandem Row

Within AutoGrid5™, turbomachines presenting tandem row can be meshed by activating Tandem Rowin the Row Properties dialog box of the concerned row(s). Row(s) are considered as tandem when it ispresenting:

• a main blade and a splitter without overlap in the streamwise direction (Tandem Row set to Yes),

• two rows (main blade with or without splitter(s)) without overlap in the streamwise direction (Tan-dem Row set to With Next/With Previous).

N1

N2 N1N2

N3

Non matchingconnection

N4

N = N2+N4-N1 --> N1<N2N4N

SplitterMainblade


AutoGrid5™ 7-25

7-3.3.1 Main Blade/Splitter Configuration

When Tandem Row is set to Yes, the blade to blade control will adapt the grid points distribution alongthe main blade and the splitter as presented on figure below.

FIGURE 7.3.3-1 Tandem row mesh definition for Main Blade/Splitter Configuration

row 1

row 2

row 1

row 2

N1

N2

N3

N4

N5

N6

N4 = N1 + N2N3 = N5 + N6

Main Blade

Splitter


7-26 AutoGrid5™

7-3.3.2 Multi-Rows Configuration

When Tandem Row is set to With Previous/With Next, a tandem configuration will be consideredbetween the two selected rows.

� The tandem configuration is applied on only two successive rows.

In order to be able to obtain full matching mesh between both rows, the number of flow paths and theflow paths distribution at the rows interface must be equal. This will lead to continuous flow pathsbetween row1 and row2.

To obtain full matching mesh in the B2B plane, two unfixed control lines are required upstream anddownstream the interface of the rows.

The B2B mesh topology used for each blade row must be the O4H or the H&I topology.

In addition, the number of point in the azimuthal direction at the interface between both rows must be thesame. In the Grid Points section of the dialog box Define B2B Topology for Active Blade, a messageindicates to the user the number of points at the connection in both rows.

When left-clicking on the button (Re)set Default Topology of the top menu bar, the process does not per-form checks and grid manipulation to assume correct linking of tandem rows. The user has to manuallycheck and change the grid point distribution to assume same azimuthal grid point number at the interfacebetween both rows otherwise a warning appears.

To ensure a full matching mesh, the optimization parameters of both rows are strictly linked together.

row 1

row 2Control Lines

O4H

O4HO4H

H&I


AutoGrid5™ 7-27

7-3.4 Control Lines & Blade to Blade Mesh.

The control lines (details in section 6-2.4) are defined in the meridional view to capture discontinu-ities of the hub and/or of the shroud. These lines can be defined upstream, downstream or on theblade(s) definition.

FIGURE 7.3.4-1 Control lines

By default, the control lines are taken into account in the blade to blade meshing process. The inter-section between the flow paths and the control line is performed to obtain m locations in the (dm/r,space). The control line implies that vertical grid lines must be defined at the computed m loca-tions.

FIGURE 7.3.4-2 Blade to blade mesh with control lines

Right-click on a control line in the meridional view gives access to a contextual menu. The menuitem Properties opens a dialog box used to control the parameters of the control line. The parame-

DownstreamUpstream Blade


7-28 AutoGrid5™

ters B2B Control in this dialog box are used to switch off the blade to blade control of the controllines.

FIGURE 7.3.4-3 Control line control

7-3.4.1 Upstream & Downstream Control Lines.

Upstream and downstream control line implies that new H blocks will be added before the inlet orafter the outlet of the O4H topology. The number of points in the azimuthal direction is implicitlydefined by the connection with the blocks of the O4H topology. The number of points in the stream-wise direction n1 and n2 (Figure 7.3.4-4) are controlled by the parameter Streamwise Npts in thedialog box Row Interface Properties (Figure 7.3.4-3) or by right-clicking on the H block in theblade to blade view and selecting the Number of Pts Streamwise menu.

FIGURE 7.3.4-4 Upstream & Downstream H-blocks

Upstream block

Downstream blockn1

n2

Z constant line on blade


AutoGrid5™ 7-29

7-3.4.2 Control Line on Blade

When a control line is defined on a blade, the parameters Streamwise Index of the dialog box Row Inter-face Properties (Figure 7.3.4-3) controls the index of the grid points along the blade distribution linked tothe control line (Figure 7.3.4-5). By default, its value is equal to "0" and the new control line is not takeninto account. When new control line has to be defined on the blade, it is advised to perform the (Re)setDefault Topology process which computes default value for the streamwise index of the new control line.

FIGURE 7.3.4-5 Control line on blade

7-3.4.3 Cell Width around Control Line

The parameters Cell width of the dialog box Row Interface Properties (Figure 7.3.4-3) controls the cellwidth in the streamwise direction around the control line. By default the value is set to "0.0" andAutoGrid5™ computes the most appropriated value automatically.

7-3.4.4 Mesh Quality Improvement with Control Line

For high staggered blades, new topology is automatically select by AutoGrid5™ if two conditions arereached (Figure 7.3.2-1). When the upstream domain and/or the downstream domain are large, the secondcondition is not reached and the high staggered optimization not selected. A method to ensure the selectionof the high staggered optimization consists of creating control lines upstream the blade near the leadingedge and downstream the blade near the trailing edge. In this condition, AutoGrid5™ will choose the highstaggered optimization. By adding these new control lines, we add also constraints into the blade to blademesh definition (vertical grid lines for each control line). These constraints can be suppressed by switchingoff the Fixed Geometry option in the dialog box Row Interface Properties (Figure 7.3.4-3)

FIGURE 7.3.4-6 Control lines improve mesh quality

Streamwise index

Cell width control around control line

MERIDIONAL

ZR


7-30 AutoGrid5™

7-3.5 Intersection Control Options

In AutoGrid5™, the dialog box Define B2B Topology For Active Blade contains a page Intersec-tion Control.

FIGURE 7.3.5-1 Intersection control parameters

These parameters allow in specific cases to control the intersection between the blade and the flowpaths performed during the transformation made from 3D space to 2D blade-to-blade space andfrom 2D domain to 3D space. This intersection is defined by control points (with a certain distribu-tion along the blade) and a number of points in between each control points. This curve describingthe blade in 2D blade-to-blade space is then used to create the mesh and then transformation to 3Ddomain is made. After these two transformations using intersection curves, there may be some(very) small differences between the original 3D geometry and the geometry obtained. InAutoGrid5™ the differences in geometry are so small that in general the impact on the solution ismuch smaller than the use of discretization in a mesh due to the size of cells and the location of thegrid points. Nevertheless AutoGrid5™ allows to use more points to compute the intersection and inthat way to reduce these differences even more. This is at the cost of a much longer mesh genera-tion process.

In few words the Intersection Control parameters control the way the intersections are definedbetween the geometry of the blade and any axisymmetric surface defined by the flow path:

• When defining the geometry using the Import CAD window, there is only one possibility todefine the intersection using Parasolid™ libraries (High mode) and in such way there are nocontrol parameters.

• When defining the geometry using a native ".geomTurbo" file, there is a default way proposedto define the intersection using SISL libraries (Low mode) but there is still the possibility to useHigh mode as well if required (not required usually).

When Low mode is selected, the intersection is defined using by default a Uniform distribution butthe user can use the Curvature distribution when "kinks" do not appear along the spanwise direc-tion on the blade patch. Furthermore, the number of discretization points (Intersection Number ofPoints) between control points defining the intersection curve can be controlled. By default around300 control points are used: that means that 300x10 points are defining each intersection curve).This number has never been changed internally.

� If the geometry is not very well defined and contains some small discontinuities, then itis recommended NOT to use a curvature distribution. Because this type of distributionwill result in a concentration of control points in the small area of the discontinuity, lead-ing to not enough control points left for a good representation of the rest of the geometry.

� If after the mesh generation, the mesh is presenting high value of angular deviation, theLow mode used by default for native ".geomTurbo" file can be switch to High modebefore regenerating the mesh.


AutoGrid5™ 7-31

Furthermore, the Blade Section Reference Angle allows for multisplitter configuration to project correctlyinto the M-theta plane the blade section by specifying an angle of reference (by default set to 0). It can hap-pens that for some configuration this angle is no more suitable for all the blade and some splitter blade M-theta projection becomes wrong (+2.PI). Changing the Blade Section Reference Angle of all the blades to avalue up to 2PI or down to -2PI (according to the azimuthal distribution) solves this problem.

FIGURE 7.3.5-2 Modify reference angle of all the blades to correct the projection

Finally, the Number of Points Used To Define the Chord allows to control the number of control pointsused to generate the chord in the blade to blade view (by default set to 33). Usually this number of points isunchanged but in specific cases (i.e. when the blade is deformed), it is required to increase this parameter.

d = 6.39359005049

Blade to Blade Control HOH Topology

7-32 AutoGrid5™

7-4 HOH Topology

7-4.1 Overview

The HOH topology is used to obtain very high grid quality. The topology is defined with threeblocks named respectively the inlet, O and outlet blocks. The HOH topology is controlled throughthe dialog box Define B2B Topology for Active Blade.

FIGURE 7.4.1-1 HOH topology

This topology is not suitable for all the turbomachinery types. This feature is not applicable:

• for blade with blunt leading edge and/or blunt trailing edge,

• for row with splitter blade(s),

• for blade to blade geometrical configuration with blade chord length lower than the pitch angle,

• for row with control line define on the blade.

7-4.2 HOH Blade to Blade Mesh Control

The HOH blade to blade mesh topology is controlled through the parameters available in the dialogbox Define B2B Topology for Active Blade. The dialog box is divided into five areas.



Inlet block

O-block

Outlet block

HOH Topology Blade to Blade Control

AutoGrid5™ 7-33

In the Topology page, the user controlthe mesh topology of the inlet and theoutlet extension of the mesh. The O-block is running around the blade andcan be extended by upstream anddownstream H or I blocks. In Meshpage, the user is allowed to change theorthogonality and the cell width at thewall through the parameters BoundaryLayer Factor and Cell Width at Wall,respectively. The blade points cluster-ing can also be controlled. In the GridPoints page, the interactive graphicalarea shows the mesh topology in termsof number of points. The user can cus-tomize the grid size by changing thenumber of points displayed in this area.Each label can be selected and modi-fied using the mouse. When clicking ona number of points, a string input areaappears prompting the user to changethis number. When modification havebeen done inside the dialog box, thebutton Generate B2B can be used tocompute and display the mesh accord-ing to the new settings.

7-4.2.1 Upstream & Downstream Extension Control

As described in the previous section, the Define B2B Topology for Active Blade dialog box givesaccess to the upstream and downstream control.

FIGURE 7.4.2-1 Upstream & downstream controls

By default, the upstream and downstream extension blocks are activated (1), the inlet and outletblock type is set to I (2).

As shown in Figure 7.4.2-2, H inlet type allows the user to set up full matching meshes. If the I inlettype is chosen, the periodic boundaries at the inlet are non-matching.

(1)

(2)


7-34 AutoGrid5™

FIGURE 7.4.2-2 H&I upstream topology

The Inlet Position and Outlet Position entered by the user is used to compute the distance betweenthe leading edge and the connection boundary. The computed distance is a ratio between the pitchangle and the specified value.

FIGURE 7.4.2-3 Inlet & outlet location

7-4.2.2 Number of Points Control

The grid points number depends of the grid level chosen in the quick access pad page Mesh Con-trol/Grid Level before performing the initialization ((Re)set Default Topology).

H mesh block at the inlet

I mesh block atthe inlet


AutoGrid5™ 7-35

Afterwards, the interactive graphics area of the Define B2B Topology for Active Blade dialog boxallows the user to change the number of points used to defined the blade to blade mesh. The mousecan be used to select a grid point number by left-clicking on it. A string input area is automaticallydisplayed, prompting the user to specify a new grid point number.

FIGURE 7.4.2-4 HOH number of points

7-4.2.3 Blade Clustering Control

The page Blade Points Distribution opens an area allowing the user to control the clustering nearthe leading edge and near the trailing edge of the blade

FIGURE 7.4.2-5 Blade Points Distribution

Four blade points clustering types are available for the leading and/or the trailing edges:

• (1) None: the grid points are clustered according to the projection of the clustering on the exter-nal boundaries of the block.

(1)

(2)

(3)

(4)

(5)

(6)


7-36 AutoGrid5™

• (2) Absolute Control Distance: a uniform distribution is set along a distance given by the user.

• (3) Relative Control Distance (Default): a uniform distribution is set along a distance com-puted by multiplying the blade width near the leading edge and a factor given by the user.

• (4) First Cell Length: first cell length is given by the user

In addition the obtained clustering can be smoothed (5) and the grid point clustering down to theblade in the azimuthal direction can be controlled by the Drag Clustering factor (6): the cell lengthnear the trailing edge is propagated until the boundary between the O and the outlet H block.

7-4.3 Butterfly Mesh Topology for Hub/Shroud Gap

The mesh on the hub/shroud gap is created using a butterfly topology. Grid Points page providesnew parameters to control the gap mesh.

FIGURE 7.4.3-1 Gap controls

Parameters to control thegrid points in the gap

d1,d2 : leading edge control lengthsd3,d4 : trailing edge controllength

d1+d2, d3+d4,d1/(d1+d2), d3/(d3+d4) : parameters ratiocontrolled by the users

Details of the mesh near the leading edge

d1+d2 = 1 d1+d2 = 2

Buttons to access the gapparameters

Parameters to control the connection with the main mesh


AutoGrid5™ 7-37

The parameters can be changed by selection in the graphics control area. By default the connectionwith the main mesh is matching and a non-matching connection is created between the H and Oblock inside the gap. In non-matching mode, the non-matching connection is located at the inter-face between the main mesh and the mesh of the gap.

� When using the matching mode (non-matching connection is created between the Hand O block inside the gap) it is not recommended to use the optimization in the clear-ance. In some cases that may work but often it will not give a better result.

7-4.4 Hub to Shroud Mesh Control

The two Hub to Shroud Control parameters at Inlet and Outlet in the Mesh page of the DefineB2B Topology for Active Blade dialog box act to reduce fluctuation of the solid angle computed toinitialize the blade to blade mesh using HOH topology. In linear mode the angles are equal to thelinear interpolation between the hub and the shroud angle values. To see a big difference, the bladeshould present the same solid angle on the hub and the shroud and different at mid span. It is used toavoid big fluctuation of the mesh in the spanwise direction due to big fluctuation of the solid angles.

� To avoid a kink, the parameter Hub to Shroud Control should be kept down or equal to0.5 when the solid angles are changing of sign from hub to shroud.


The parameters in the Intersection Control page allow in specific cases to control the intersectionbetween the blade and the flow paths performed during the transformation made from 3D space to2D blade-to-blade space and from 2D domain to 3D space. More details about the parameters areprovided in section 7-3.5.

Blade to Blade Control H&I Topology

7-38 AutoGrid5™

7-5 H&I Topology

7-5.1 Overview

The H&I topology is used to obtain better mesh quality with multisplitters configuration. The H&Itopology is controlled through the dialog box Define B2B Topology for Active Blade.

FIGURE 7.5.1-1 H&I topology

The H&I topology will present leading and trailing edges clustering projected on neighbouringblades, meaning that a non matching connection or a non matching periodic connection will bepresent at inlet and outlet.

FIGURE 7.5.1-2 H&I topology - Projection points

H-block

Outlet blockInlet block

Skin block

PeriodicNon Matching

H&I Topology Blade to Blade Control

AutoGrid5™ 7-39

The H&I topology is composed by:

• One block to mesh the blade passage, contrary to the default topology which creates a mesharound the blade.

• An optional skin block around the blade with two H blocks before and after the skin block.

The topology is not suitable for all turbomachinery types. This feature is not applicable:

• for bypass configuration,

• for configuration presenting a Z constant line on blade,

• for configuration presenting cooling features (holes, basin, ribs,...),

• for full mesh generation with geometry periodicity different than 1,

• for configuration requiring a wake control,

• for multi-splitter configuration where leading or trailing edges are crossing each other.

7-5.2 H&I Topology Control

As mentioned previously in this chapter, the H&I topology is composed by maximum 4 blocks:

• a H block to mesh the blade passage

• an optional O block around the blade (skin block)

• an optional H block upstream the leading edge of the blade if a skin block around the blade

• an optional H block downstream the trailing edge of the blade if a skin block around the blade

By default, the H&I topology will present a full matching connection in the blade passage area anda non matching connection (Figure 7.5.2-1) or a non matching periodic connection (Figure 7.5.2-2)in the inlet and outlet region.

However, a small part just before the leading edge and after the trailing edge will be matching toavoid a non matching connection in these critical regions (Figure 7.5.2-2).

Leading Edge Main Blade

Leading Edge Splitter 1

Leading Edge Splitter 2

Splitter 1

Main Blade


7-40 AutoGrid5™

FIGURE 7.5.2-1 H&I topology - non matching connection

FIGURE 7.5.2-2 H&I topology connections

The number of points involved in the matching connection at the leading and trailing edges is auto-matically imposed by AutoGrid5™ and cannot be adapted manually. These number of points areprovided as info in the Grid Points page.

Non Matching

Non Matching

Periodic Non Matching

Periodic Matching

Periodic Non MatchingPeriodic Matching

Periodic Matching


AutoGrid5™ 7-41

� The matching connection in these critical regions is ensured except if the grid pointsnumber modified by the user at inlet and/or outlet is lower than the number of points setautomatically by AutoGrid5™ in the matching connection. For example, in above figureif the inlet grid points number (set by default to 53) is set to a value down or equal to 29,the matching connection will not be ensured at the leading edge.

In order to ensure a full matching connection, the options H Inlet/H Outlet have to be activated inthe Topology page and the button (Re)set Default Topology should be pressed.

� When the blade is detected highly staggered at inlet and/or outlet, the full matching con-nection will be automatically ensured at respectively the inlet and/or outlet (section 7-5.3).

Non Matching

Matching

Non Matching


7-42 AutoGrid5™

FIGURE 7.5.2-3 H&I topology - H Inlet/Outlet

To enhance the mesh quality for centrifugal and mulsplitter configurations, the H&I topology canbe limited to H block to mesh the blade passage by deactivating the option Skin Block.

FIGURE 7.5.2-4 H&I topology - without Skin Block


AutoGrid5™ 7-43

7-5.2.1 Control Number of Grid Points

The grid points number depends of the grid level and the streamwise weights chosen in the quickaccess pad page Mesh Control/Grid Level before performing the initialization ((Re)set DefaultTopology).

These optimized grid points numbers can be changed in the Grid Points page of the dialog boxDefine B2B Topology For Active Blade. The number of grid points can be adapted as well as thegrid points distribution (number on top of arrows) from the inlet to the outlet. In the figure below,when modifying the grid points distribution from 53 to 45 at the leading edge, the grid pointsnumber at inlet will be reduced to 45 and the number of points on the blade will be increased to (61+ (53-45-1)).

To change a number, left-click on it, enter the new number of points in the locally displayed inputarea and <Enter> to confirm or <Esc> to cancel the action. To display the new blade to blade mesh,click-left on the button Generate B2B.

When modifying a number of grid points, in order to preserve the matching connections of the H&Itopology, all the numbers of grid points will be automatically adapted. For a configuration present-ing splitter(s), when modifying the grid points numbers on one blade (main blade or splitter) of therow, the changes will be automatically applied on all the blades composing the row.

7-5.2.2 Control Skin Mesh Clustering around the Blade

The O block around the blade is used to optimize the control of the boundary layer on the blade. Itis created using an hyperbolic mesh and can be adapted using the options presented in section 7-3.1.3. When the option Skin Block is deactivated (no O block around the blade), a clustering atboth ends will be applied in the H block in the channel.

Grid Points Distribution Control


7-44 AutoGrid5™

7-5.2.3 Control Hub/Shroud Gap Mesh

When gap(s) has been defined, AutoGrid5™ adds automatically blocks to mesh the domain up ordown to the blade(s). More details can be found in the section 7-3.1.4.

7-5.2.4 Blend/Sharp/Rounded Treatment at Leading/Trailing Edge

In case of blunt blades, AutoGrid5™ automatically detects the bluntness of the blade and the optionto blend, sharp or rounded the blunt blade leading/trailing edge appear in the Topology page of theDefine B2B Topology for Active Blade dialog box. More details can be found in the section 7-3.1.5.

However, when the blade is considered as blunt or sharp at both leading and trailing edges, the skinblock (O block) will be removed.

7-5.2.5 Inlet & Outlet Boundary Control

The inlet and outlet boundaries of the blade to blade mesh are located at theta positions computedautomatically using a parabolic function or defined manually. More details can be found in the sec-tion 7-3.1.8.

7-5.2.6 Control Clustering at Projection Points

The H&I topology will present leading and trailing edges clustering projected on neighbouringblades. It means that by default the clustering imposed at the leading and trailing edges will beapplied on the corresponding projected point.

FIGURE 7.5.2-5 H&I topology - Projection Point

AutoGrid5™ allows to relax the clustering of the projected point manually or automatically usingthe parameters available in the Mesh page.


AutoGrid5™ 7-45

FIGURE 7.5.2-6 H&I topology - Projection Point Clustering Automatic Relaxation

The Automatic Clustering Relaxation (projections) option allows to relax automatically the clustering onall projection points simultaneously.This method allows to impose automatically different clustering relaxa-tion depending of the projection point. For example, if the blade is presenting a blunt at trailing edge, thecorresponding projection point clustering will be more relaxed compared to the leading edge projectionpoint clustering as presented in above figure.

The Relaxation Clustering (projections) option allows to control manually the projection points clusteringof the blade by multiplying the default clustering with the value specified in the entry. This method willimpose the same relaxation factor to all the projection points.

When combining the two relaxation methods, first the automatic relaxation will be applied and then the userdefined relaxation clustering factor will be applied in addition.

7-5.3 Topology for High Staggered Blades

By default, AutoGrid5™ will detect automatically if the blade is staggered. When detected at inlet and/oroutlet, the main H block is deviated from streamwise direction to theta direction in order to create a kind ofC topology at the inlet and/or outlet). More details can be found in the section 7-3.2.

Leading Edge Trailing Edge


7-46 AutoGrid5™

FIGURE 7.5.3-1 High staggered topology at inlet

� The topology for high staggered blades is presenting full matching connections in thehigh staggered area.


These parameters allow in specific cases to control the intersection between the blade and the flowpaths performed during the transformation made from 3D space to 2D blade-to-blade space andfrom 2D domain to 3D space. These parameters are detailed in section 7-3.5.

C topology

Inlet close to the leading edge

User Defined Topology Blade to Blade Control

AutoGrid5™ 7-47

7-6 User Defined TopologyTo choose a user defined topology for the selected row, open the Define B2B Topology For ActiveRow dialog box and activate the option User Defined.

FIGURE 7.6.0-1 Blade to blade topology user defined mode

When this user defined mode is activated, the only option remaining in the dialog box is the buttonEdit Topology. It allows to define and control the blade to blade mesh through a dedicated graphicaluser interface:

FIGURE 7.6.0-2 Edit topology graphical user interface

The Quick Access Pad and the graphics area are updated to display the options of the edit topologymode.

To quit this edit topology graphical user interface, press the button Close Edition Mode at the topright corner, it will reenter the classical multistage graphical user interface.



Blade to Blade Control User Defined Topology

7-48 AutoGrid5™

The basic principle in user defined topology is to create manually the blade to blade mesh on thehub, then controlling and modifying it on the shroud, and possibly on additional control layers. Thismesh is created with the blocking and meshing facilities of IGG™. As a support of this blocking, ageometry is automatically created when entering the edit mode and additional geometry can also becreated. Once the mesh is created on the control layers, it is interpolated with transfinite interpola-tion to compute the mesh on all the layers. This gives a continuous initial mesh then all layers areidentically smoothed to give the final 3D mesh.

FIGURE 7.6.0-3 User defined topology principle

7-6.1 Geometry Control

Once entering the edit mode, a geometry of the selected row is automatically created:

• the section of the blade(s) at the hub,

• an offset of this blade section,

• the row inlet curve (upstream row rotor/stator),

• the row outlet curve (downstream row rotor/stator),

• a curve going from the blade leading edge to the inlet,

• a curve going from the blade trailing edge to the outlet,

• two periodic curves on each side of the blade,

• a periodic copy of the preceding curves (except obviously the inlet and outlet),

• the control line curves located between the row inlet and outlet (meridional control lines).

It is possible to control the offset curve and to create additional polylines through the first subpad ofthe Quick Access Pad:

Control layers

Mesh created on hub

Mesh copied andmodified on otherlayers

Mesh computed byinterpolation onintermediate layers


AutoGrid5™ 7-49

The Polyline button allows to create additional polylines on which the blocking can be placed. Thepolyline control points should be located on the existing geometry for the system to work correctly.This option launches a tool:

• Move the mouse cursor to the desired position and left-click to add a control point to the curve.

• The creation of the curve is terminated by right-clicking. Notice that the last curve segment,attached to the mouse movement, is not part of the curve.

• During the specification of the control points, the cursor attraction to existing curves is acti-vated. When it is attracted to a curve, a filled-in circle is displayed.

� The Geometry menu in the top menu bar cannot be used.

The entry Blade Offset Width allows to control the size of the blade offset to define a support skincurve. It is a percentage of the blade thickness (blade thickness is a dimension automatically com-puted according to the geometry).

The entry Blade Offset Width 2 allows to control the size of the blade offset to define a supportcurve in the gap. It is a percentage of the blade thickness (blade thickness is a dimension automati-cally computed according to the geometry).

7-6.2 Mesh Control

The blade to blade mesh should be defined on the hub layer, then it can be modified on other layersif desired. The objective is to fill completely a periodic blade domain, defined by its geometry, byblock faces. All the domain should be meshed, except inside the blade if no blade gap is defined.The domain can be defined either by the two periodic curves and inlet and outlet curves, either bythe inlet and outlet curves, the two blades (main blade + its repetition) and the curves linking theleading and trailing edge to inlet and outlet curves.

FIGURE 7.6.2-1 Periodic domain examples

Periodic domainaround the bladeand betweenperiodic curves

Periodic domainbetween blades andcurves linking leadingand trailing edge toinlet and outlet curves


7-50 AutoGrid5™

Following operations are available on the hub:

• faces creation,

• faces deletion,

• insert vertices and control them,

• insert fixed points and control them,

• set the clustering on segments,

• set the face type,

• control segment boundary conditions (smoother).

Once faces are created on the hub, these faces are automatically copied to other control layers.When going on another control layer, the geometry is replaced and the faces remapped on it. Thenmodifications can be achieved. Modifications available are:

• vertices displacement (including periodic placement),

• segments clustering control.

� Face vertices should absolutely be located on curves for the system to work correctly. Itallows to place correctly vertices when going from one control layer to another. If a ver-tex is mapped on a curve on the hub, it should be mapped on the curve having the samename on other layers, even after modifications, otherwise an error will be raised.

First of all the number of control layers should be chosen, then the mesh created on the hub layerand modified on other layers.

The blade to blade mesh is created and controlled through the Topology Control subpad of theQuick Access Pad, whereas the mesh visualization is controlled through the View subpad.

FIGURE 7.6.2-2 Topology control subpad

The Topology Control subpad is composed of three pages, the first one controlling the layers, thelast two ones being used to create the mesh.


AutoGrid5™ 7-51

7-6.2.1 Control Layer Page

This page is used to control the number of layers and their management. All control layers physi-cally correspond to a flow path. This flow path specifies the surface of revolution and therefore theblade intersection and geometry which will be linked to the control layer.

• Control Layer Spacing (%span) controls the desired number of layers. The percentage of thespacing in the spanwise direction should be specified. The default value is 100, meaning thatthere are two control layers, one at the hub, one at the shroud. For example, specifying 25 wouldcreate five control layers, one at the hub, one at 25% span, 50% span, 75% span and one at theshroud. Changing the number of control layers implies that all previous mesh modificationsdone on control layers different than the hub will be erased.

• Active Layer allows to select the layer to analyze, i.e. select the flow path at which the meshwill be analyzed. If the layer is a control layer, it is possible to work on and modify the mesh,otherwise it is only possible to preview the final mesh after smoothing. The active layer is alsoexpressed as a percentage of the spacing in the spanwise direction. When the active layer corre-sponds to a control layer, the geometry is recomputed at this level and face vertices are rema-pped on this updated geometry.

• Active Layer Index gives the flow path index corresponding to the active control layer.

• The button Reset All Layers to Hub erases all the modifications done on all the layers differentthan the hub. This allows on all the control layers to have an exact copy of the hub mesh.

• The button Preview Initial Mesh allows to reinterpolate all the faces mesh on the active layer.Indeed after smoothing face mesh is optimized and obviously different than its initial shape.

• The button Preview Final Mesh allows to smooth the faces mesh on the active layer, allowing tosee what will be the final smoothed mesh at that level. The smoothing parameters are the classi-

cal ones of the Optimization Properties dialog box ( ).

• The button Detect Unmapped Segments allows to visualize the segments unmapped on a exist-ing blade to blade curves. Check the vertices linked to the segments.

7-6.2.2 Create - Connect Pages

These pages allows to create the mesh and control it.

• The icon Insert New Block allows to create a new face by entering in the graphics area two ofits opposite vertices. Then the four face vertices can be moved freely.

• The icon Delete Block allows to delete faces.

• The icon Define Block Type allows to define if the block should be considered as fluid or solid.It opens the following dialog box:

� In fact it allows to specify if a block is part of a gap or not. If it is included in the gapmesh, its type should be Solid.

• The icon Define Block Bcs allows to visualize boundary conditions set on segments for thesmoother. It opens the following dialog box.


7-52 AutoGrid5™

FIGURE 7.6.2-3 Segment boundary conditions dialog box

The dialog box contains a list of all the face segments. The different filters at the top allow to dis-play specific segments in the browser while hiding others. The Face, Edge and Seg filters arecumulative and allow to display segments by indices.

For example: Face filter: ’*’ (’*’ means all) - Edge filter: ’1 2’ - Seg filter:’*’ shows in the browserall the segments of edges 1 and 2 of all the faces.

The Type filter is very useful to list all the segments of a given type (according to the other filters).

Allowed types are:

• MOVING, meaning that the segment points can move on a curve.

• SOLID_WALL, meaning that the segment points are fixed and a cell size is imposed in themesh.

• UNDEFINED, meaning that no special boundary conditions is set on the segment. Generally itmeans that the segment is internal to the mesh and will be connected to another one. Otherwiseit means that the segment is badly placed (edge not correctly mapped on a curve for example).

The right part contains information on the selected segment:

• its type,

• if its type is SOLID_WALL, the cell width that will be imposed on the segment, the number oflayers on which it will be imposed and the expansion ratio set between the layers. These valuescannot be changed directly through the Segment boundary conditions dialog box. Cell width canbe changed through the Quick Access Pad Mesh Control/Row Mesh Control/Cell Width orthe Define B2B Topology dialog box in Mesh page (accessible when Default topologyselected). The number of layers and expansion ratio are automatically set and cannot bechanged.

Segments can be selected in the dialog box by left-click and left-drag. When selected, they are high-lighted in the graphics area and displayed with four arrows.

• The icon Insert Vertex allows to insert a new vertex in an edge.

� Use the short-cut <i> to activate this command in a faster way.

• The icon Insert Fixed Point allows to insert a new fixed point in an edge.

Filters, allowing selectivevisualization in the segment list


AutoGrid5™ 7-53

• The icon Periodic Vertex allows to start a tool to place vertices at a periodic position. Start thetool, select the reference vertex (which one will not move), and select the vertex to be posi-tioned at a periodic translation from the reference one. Then move the cursor either above orbelow the reference vertex, the second vertex will be automatically located at the periodic posi-tion. If this position is over a curve, the vertex will be automatically mapped on it. Left-click tofix the vertex position. Then it is possible to repeat the same operation with other vertices.

• The icon Cluster Points allows to open the Clustering dialog box (more details in IGG™ UserManual). It allows to apply grid points distribution on the segments. For initial spacing at startand at end, absolute values should be entered, they will be automatically divided by the localradius of the control layer. This means that if the same cell size is desired at the hub and at theshroud, the same value should be entered in the dialog box.

The options Edge - Edge and Whole grid of the Connect page allow to connect either two edges,or all the edges of the blade to blade mesh. The connections allow to modify the mesh more easilyas e.g. moving one vertex will move all connected vertices.

• Edge - EdgeThe connection of two edges requires the selection of a reference edge and a second edge (target).During the different connection operations, AutoGrid™ may need to remap edges affected by theoperation. By convention AutoGrid™ keeps the reference edge unchanged and applies the modifi-cations on the second edge only. This is important when an existing edge cannot be modified at all.

Firstly select the two edges to connect together. The following prompt will appear:

Select First Edge (reference) (<1> to select - <2> to acknowledge - <3> to quit)

Left-click on the desired edge and middle-click to confirm the selection. Then, the second edgemust be selected in the same way. After, the following dialog box will be opened to enable connec-tions at different levels, each level being identified by a button in the dialog box. The All button per-forms all the connections of the previous buttons, if possible.

FIGURE 7.6.2-4 Edge-Edge connection dialog box

� For the first four "topological" levels, an order must be respected from the top to the bot-tom.

For Vertices or Orphan Vertices connections, the topological edges using the replaced vertex areremapped on the geometry. For each level, the successfully connected entities are highlighted ingreen in the graphics area. Entities that were already connected in a previous operation are high-lighted in red. Once a connection is performed, two other edges can be selected to make anotherconnection without leaving the tool. To quit this tool, press <q> or the right mouse button.


7-54 AutoGrid5™

• Whole gridThis tool performs the connection for the whole grid at once.

FIGURE 7.6.2-5 Whole grid connection dialog box

The All button performs all the connections of the previous buttons, if possible. For each connectionlevel selected by a button, a search is made on the whole grid to find matching entities at the speci-fied tolerance and the connection is performed. As the whole grid is examined, and that a connectedentity can be modified, this tool should not be used if any of the block cannot be modified at all.

� For the first four "topological" levels, an order must be respected from the top to the bot-tom.

For Vertices or Orphan Vertices connections, the topological edges using the replaced vertex areremapped on the geometry. For each level, the successfully connected entities are highlighted ingreen in the graphics area. Entities that were already connected in a previous operation are high-lighted in red. To quit this tool, press <q> or the right mouse button.

7-6.3 View Control

This subpad contains several icons allowing to visualize the mesh at different levels: vertices, fixedpoints, segment grid points, edges and faces mesh. The following table summarizes these options:

Icon Command

Toggles vertices.

Toggles fixed points.

Toggles segment grid points.

Toggles edges.

Toggles face grid.

Blade to Blade Optimization Blade to Blade Control

AutoGrid5™ 7-55

7-7 Blade to Blade Optimization

7-7.1 Introduction

FIGURE 7.7.1-1 Blade to blade mesh optimization control

The blade to blade mesh of each row are optimized using an elliptic multiblock smoother. Theparameters controlling the optimization are available in the dialog box Optimization Properties.This dialog box is opened through the option Mesh Control/Row Mesh Control/OptimizationControl of the Quick Access Pad.

7-7.2 Optimization Control

This section describes the optimization parameters available in the dialog box Optimization Proper-ties.

Blade to Blade Control Blade to Blade Optimization

7-56 AutoGrid5™

7-7.2.1 Optimization Steps

The first fields Optimization Steps and Gaps and/or CHT Optimization represent the number ofiteration the elliptic smoother will perform respectively in the channel mesh and in the gap. Thisnumber depends on the skewness level of the original mesh and can be highly reduced if the Multi-grid Acceleration is activated. By default both optimization steps are set to 100.

7-7.2.2 Skewness Control

By default the Optimization Steps controls the orthogonality of the cells only near the solid wall.The parameters Skewness Control/Skewness Control In Gaps set to Full force the optimizationto increase cells skewness everywhere respectively into the blade-to-blade channel mesh and intothe blade-to-blade gap mesh.

FIGURE 7.7.2-1 Optimization with skewness control

When the parameters Skewness Control/Skewness Control In Gaps are set to Medium, the firsthalf of iterations are done without skewness control and the remaining second half with skewnesscontrol.

Theoretical Aspect

Two source term computations have been implemented (details in section 7-7.10).

The first one, with the Skewness Control set to No, computes source terms only in the neighbour-hood of boundary layers, taking into account the expansion ratio provided by the user. The maindrawback of this implementation is that it is easy for the user to enter conflicting inputs that willmake the smoother diverge. For example, requiring a very small cell size on boundary with a smallexpansion ratio while the boundary spreads on a large distance with few cell points cannot beachieved and is a typical case of the smoother divergence.

The second one, with the Skewness Control set to Full, computes source terms everywhere on themesh and does not have expansion ratio as input. The boundary layers are not privileged whichleads to better orthogonality in the central regions but increase skewness near the boundary layers.Moreover, mesh concentrations outgoing from boundary layers propagate all over the mesh.

No Skewness Control Full Skewness Control


AutoGrid5™ 7-57

The main difference between the two methods can be seen in Figure 7.7.2-2.

FIGURE 7.7.2-2 Smoothing without (left) and with (right) skew flag

7-7.2.3 Orthogonality Control

The parameter Orthogonality controls the level of cells orthogonality near the wall or everywherein the mesh depending of the Skewness Control parameter value. By default the orthogonality con-trol parameter is set to 0.5.

FIGURE 7.7.2-3 Orthogonality control


7-58 AutoGrid5™

The parameter Gap Orthogonality is used when a large variation is observed in the first cell width in thegap compared to the blade width. In case of smaller wall cell width, increase the Gap Orthogonality toincrease the skewness and for larger wall cell width, reduce the Gap Orthogonality to avoid overlappingcells in the gap. By default the gap orthogonality value is set to 0.5.

Theoretical Aspect

When the source terms become too high, typically when expansion ratio are too large (>> 2) or angles aretoo small, the numerical scheme that solves the elliptic equation becomes unstable and the smootherdiverges. The source terms are therefore clipped in order to be kept below a certain value depending on thesmoother type.

When aspect ratio are large on the boundary layer while both orthogonality and expansion ratio almost fitCFD requirements, the source terms also become large and clipping them to ensure robustness of thesmoother leads to high skewness in the boundary layers. Fortunately, experience has shown that clippingcan be proportional to the square root of the aspect ratio. The Orthogonality slider controls the proportion-ality factor and allows to obtain good orthogonality and low expansion ratio in the boundary layers. Whenset to "0.000", there is no overclipping and robustness is ensured but there is a risk of increasing the skew-ness in the boundary layer. When set to "1.000", orthogonality constraint increases as well as the probabil-ity that the smoother diverges. The default "0.500", in most of the cases, provides a good boundary layerafter a smooth convergence.

Note that this overclipping method also allows the second type source term computations to privilegeboundary layers (details in section 7-7.10).

7-7.3 Wake Control Level

This option is meaningful only if the Wake Control is activated (See section 7-3.1.7). In that case, thesmoothing is performed in two stages. During the first one, the wake is fixed and released during the sec-ond stage. The Wake Control Level slider controls the proportion of iteration performed in the first andthe second stage.

FIGURE 7.7.3-1 Wake control level


AutoGrid5™ 7-59

7-7.4 Multigrid Acceleration

This functionality allows a faster convergence of the smoother but should nevertheless be carefullyused. Indeed, in this case, the multigrid scheme presents an additional difficulty: the fields that arecomputed, restricted and prolonged are the mesh points themselves. The expansion ratio is thushighly increased on each grid coarsening as well as the resulting source terms. As discussed in sec-tion 7-7.2.3, the stability of the numerical scheme therefore decreases on each coarsening and fewexamples (i.e. when very small expansion ratio on the finest grid) have successfully convergedusing such multigrid approach. The compromise that has been found and implemented in the cur-rent version is to restrict source terms (just copy from the finest mesh) instead of computing them.In such a case, the smoother converges but the solution obtained with the multigrid acceleration canbe somewhat different that the one obtained with a single grid computation.

7-7.5 Non-Matching Control

The Non-Matching Control slider controls the orthogonality at the non-matching periodic bound-aries when Matching Periodicity is deactivated (See section 7-3.1.2). In that case, the smoothing isperformed in two stages. During the first one, the orthogonality is fixed on the periodic boundariesand released during the second stage. The slider controls the proportion of iteration performed inthe first and the second stage.

� This option can be unstable when it is used together with the multigrid acceleration.

� This option must be switched off when kink along spanwise grid lines are observed inthe 3D mesh.

7-7.6 Periodic Boundary Optimization

The parameter Bnd Optimization Steps allows to optimize the shape of the periodic boundaries ofthe initial mesh before applying the Optimization Steps. In specific cases, the option avoids theperiodic boundaries to cross the blade or cells overlaps in the blade-to-blade view resulting in meshoptimization divergence when Optimization Steps applied.

FIGURE 7.7.6-1 Periodic boundaries optimization

The Bnd Straight Control selection box allows to impose a straight (linear) shape to the periodic

boundaries of the initial mesh before applying the Optimization Steps.

OverlappingCells


7-60 AutoGrid5™

7-7.7 Multisplitter Control

The Multisplitter Control selection box is used to control the mesh initialization (ordering) for multi-splitter configuration. By default the parameter is not active and is active when a new multi-splitter tem-plate is initialized.

7-7.8 Skin Mesh Control

The Freeze Skin Mesh selection box is used to freeze the skin block (mesh and boundaries) during theoptimization process. It is suggested to freeze the skin mesh with the introduction of cooling holes, inorder to improve the quality of the full non matching (FNMB) connection between the skin block and thecore flow.

� The option is not available for a blunt leading or trailing edge.

7-7.9 Advice to Users

Try to avoid large expansion ratio (>2) along the blade in the streamwise direction when setting up thenumber of points required along the blade.

When using the smoother without skew flag activated, be careful that the expansion ratio in the azi-muthal direction does not conflict with the number of points in the same direction.

When the user needs a coarse mesh with large expansion ratios and hence, the two previous advices can-not be followed, do not select the Multigrid Acceleration option.

Always check the mesh quality on both hub and shroud blade-to-blade views before starting a 3D meshgeneration

7-7.10 Theoretical Aspect

The aim of this functionality is to optimize both orthogonality and expansion ratio all over the mesh. If

we consider an initial mapping from computational space

to the mesh coordinate domain .

The leading equation for the elliptic smoother is given by:

When the source terms, P = Q = 0, the mesh will converge to an uniform spacing grid without takingaccount of orthogonality or boundary conditions (clustering at wall for example). Therefore, the imple-mentation consist in calculating these source terms in order to minimize skewness and expansion ratiowhile taking into account all boundary condition types available in AutoGrid5™.

x ξ η,( ) x ξ η,( ) y ξ η,( ),( )= 0 m,[ ] 0 n,[ ]×

Ω R2∈

g22 xξξ Pxξ+( ) 2g12xξη– g11 xηη Qxη+( )+ 0=

g11 xξ xξ⋅ xξ2

yξ2

+= =

g12 xξ xη⋅ xξxη yξyη+= =

g22 xη xη⋅ xη2

yη2

+= =

AutoGrid5™ 8-1

CHAPTER 8: 3D Generation

8-1 OverviewThe 3D mesh of a turbomachinery configuration is easily started and automatically generated byAutoGrid5™ using the Generation Control dialog box appearing after clicking on the top menu bar but-ton Generate 3D in Expert Mode or directly the button Generate 3D in Wizard Mode. The 3D genera-tion can be aborted using the button Abort displayed after the beginning of the 3D generation. At the endof the generation, the multiblock structured mesh can be displayed in the 3D view of the graphics areafor quality analysis.

FIGURE 8.1.0-1 3D generation

� Before generating the 3D mesh, the blade-to-blade mesh should be generated on hub andshroud in order to apply an automatic reset of the expansion ratio when necessary.

3D Generation Application Field

8-2 AutoGrid5™

8-2 Application FieldThe button Generate 3D of the top toolbar applies to all the selected entities of the tree. Three typesof entity can be selected: the row, the meridional technological effect and the 3D technologicaleffect. The button Select All is used to select all the entities of the tree. The button Select All Rows isused to select all the rows of the tree.

FIGURE 8.2.0-1 Selection of the application field of the button Generate 3D

� The meridional effects are connected to several rows and must be generated togetherwith these row(s) if these ones are not yet generated. If the 3D meshes of the connectedrow(s) are already generated, the effects can be generated alone excepted if the configu-ration of the row (generation parameters) has been changed after their generation.

� A 3D technological effect belongs to a row. If the selection does not include the row con-taining a selected 3D effect, AutoGrid5™ prompts to confirm the 3D generation of therow.

8-3 3D Mesh - InterpolationThe 3D mesh of the rows of a turbomachinery configuration is generated using a stacking method.The flow paths are used to create the surfaces of revolution (layers) on which the blade to blademeshes are projected. The stacking method is divided into two phases: the computation of intersec-tion between the blade(s) and the layers, and the generation and optimization of the blade to blademesh.

To reduce the generation time, it is possible to reduce the number of layers on which the mesh mustbe optimized. The parameter Layer Control (% span) in the Mesh Control/Row Mesh Controlpage in Expert Mode is used to specify the spanwise space between 2 consecutive layers on whichthe optimization must be done. By default the optimization is done on all the layers. A value of 25%implies that the mesh will be optimized on five layers (0%, 25%, 50%, 75%, 100%) and interpo-lated between them to obtain the entire mesh.

Full selection buttons

Row selection

3D effect selection

Meridional effect selection

3D Mesh - Interpolation 3D Generation

AutoGrid5™ 8-3

FIGURE 8.3.0-1 Mesh interpolation

The order of generation of the selected entities is:

• 3D mesh generation of the selected rows,

• 3D mesh generation of the selected meridional effects,

• 3D mesh generation of the selected 3D technological effects.

8-3.1 3D Blocks Naming

The name of each block is built using the name of the related configuration entities.

� A limitation to the block name length to 32 characters due to the CGNS format used toperform the persistence implies that AutoGrid5™ changes automatically the name of theblock exceeding 32 characters, stored in the CGNS file into ’domain<block number>’.

8-3.1.1 Row Mesh

The name of each block is built using the name of the row and the name of the related blade.

a) Default Topology - H&I Topology - HOH Topology

The block orientation I,J,K is related respectively to the azimuthal, spanwise and streamwise direc-tion. The names of the blocks of a row named ’row 1’ around the blade named ’Main Blade’ are:

• row_1_flux_1_Main_Blade_inlet (not in H&I topology when blade sharp at inlet)

• row_1_flux_1_Main_Blade_outlet (not in H&I topology when blade sharp at outlet)

• row_1_flux_1_Main_Blade_up (not in HOH and H&I topology)

• row_1_flux_1_Main_Blade_down (not in HOH topology)

• row_1_flux_1_Main_Blade_skin (not in H&I topology when blade double blunt and/or sharp)

• row_1_flux_1_Main_Blade_skin_up (only for O4H topology when blade double blunt and/orsharp)

• row_1_flux_1_Main_Blade_hubgap1 (if a hub gap is defined)

• row_1_flux_1_Main_Blade_hubgap2 (if a hub gap is defined)

• row_1_flux_1_Main_Blade_shroudgap1 (if a shroud gap is defined)

• row_1_flux_1_Main_Blade_shroudgap2 (if a shroud gap is defined)

• row_1_flux_1_Main_Blade_upStream (if a upstream control line is defined)

3D Generation 3D Mesh - Interpolation

8-4 AutoGrid5™

• row_1_flux_1_Main_Blade_downStream (if a downstream control line is defined)

In case of bypass configuration, the mesh of the fan is split in two fluxes and therefore the blocks arealso duplicated and named using the suffixes "flux_1"and "flux_2".

b) User Defined Topology

The name of the block of a row named ’row 1’ around the first blade named ’Main Blade’ meshedwith user defined topology with 1 block for the main channel and 1 block for the gap are respectively:"row_1_userTopology_Block_1" and "row_1_userTopology_Block_2_blade_1_hubgap".

8-3.1.2 Mesh in Bulb

If an inlet bulb (hub->R=0) region is detected, the following blocks are added to the 3D mesh:

• bulb_at_inlet_C (if rounded topology is chosen)

• bulb_at_inlet_H1 (if rounded or sharp topology is chosen)

• bulb_at_inlet_H2 (if rounded or sharp topology is chosen)

• bulb_at_inlet_butterfly_1 (if rounded topology without singular line or radial topology is chosen)

• bulb_at_inlet_butterfly_2 (if rounded topology without singular line or radial topology is chosen)

• bulb_at_inlet_butterfly_1_2 (if radial topology is chosen)

• bulb_at_inlet_butterfly_2_2 (if radial topology is chosen)

8-3.1.3 Mesh around Nozzle (Bypass)

If a C topology is chosen to mesh the region around the nozzle of a bypass configuration, a new blocknamed "C_block_around_nozzle" is added.

8-3.1.4 Mesh in Meridional Technological Effect

When the mesh of a meridional effect named ’zr techno effect 1’ is generated, following blocks areadded into the 3D database:

• zr_techno_effect_1_zr_effect__Block_1_3d

• zr_techno_effect_1_zr_effect__Block_2_3d

8-3.1.5 Mesh in 3D Technological Effect

When the mesh of a 3d effect named ’3d techno effect 1’ and belonging to the row named ’row 1’ isgenerated, a prefix ’row_1_3d_techno_effect_1_’ is added to each block name of the blocks gener-ated in the 3d effect.

8-3.2 3D Boundary Condition Patches

8-3.2.1 Generation

At the end of the 3D generation, all the faces of the 3D blocks are automatically divided into patches.Each patch type is defined automatically (INL, OUT, SOL, PER, PERNM, CON, ROT, EXT,...)according to the turbomachine configuration. The boundary conditions are stored in the ".bcs" and inthe ".cgns" files.

8-3.2.2 Patch Naming

Solid patches contain the name of their related entities and the location (hub,shroud,noz-zle,skin_blade). Following is the list of the solid patches created for the ’row 1’ around the ’Mainblade’ with a default topology:

3D Mesh - Interpolation 3D Generation

AutoGrid5™ 8-5

• row_1_flux_1_Main_Blade_inlet__hub_identifier_

• row_1_flux_1_Main_Blade_outlet__hub_identifier_

• row_1_flux_1_Main_Blade_up__hub_identifier_

• row_1_flux_1_Main_Blade_down__hub_identifier_

• row_1_flux_1_Main_Blade_skin__hub_identifier_

• row_1_flux_1_Main_Blade_inlet__shroud_identifier_

• row_1_flux_1_Main_Blade_outlet__shroud_identifier_

• row_1_flux_1_Main_Blade_up__shroud_identifier_

• row_1_flux_1_Main_Blade_down__shroud_identifier_

• row_1_flux_1_Main_Blade_skin__shroud_identifier_

• row_1_flux_1_Main_Blade_skin_blade_(aap-ps)

• row_1_flux_1_Main_Blade_skin_blade_(aap-ss)

8-3.3 Block Order

As the blocks are created after each call to the Generate 3D button relatively to the user selection,the block order in the final block list depends strongly on the sequence of the user interaction. Toobtain similar order for similar configuration, the entire mesh must be generated using the sameinteractive sequence of calls to the Generate 3D button (not easy to manage). Another way toensure a same block order is to set up the configuration and to start the full mesh generation (SelectAll+Generate 3D). The batch mode ensures also the same block order.

8-3.4 Generate Full Mesh

By default, the mesh is generated for 1 main blade passage. The parameter Generate Full Mesh inthe dialog box Row Properties can be switched on to generate all the blade passages. The mesh isobtained by repetition of the first blade passage.

8-3.5 Number of Mesh Points.

The Mesh Control subpad displays and updates continuously an approximation of the total numberof grid points of the selected entities in the Row Definition subpad. After the grid generation, thereal grid points number is displayed in the information area (lower left corner of the interface).

Selection

Total number of grid points in the current generated 3D mesh

Approximation of the total number ofgrid points in the selection

3D Generation Mesh Quality

8-6 AutoGrid5™

8-4 Mesh Quality

After the grid generation, the menu item Grid/Grid Quality Report ( ) displays the character-

istics of the mesh in terms of minimum and maximum of the expansion ratio, the aspect ratio andthe cells skewness. These data are available for the entire mesh or by configurations entity (row,technological effect, bulb). Negative cells are detected and indicated on top of the histogram. Thenumber of multigrid levels of each entity (row and technological effects) is listed in the Mg. Levelcolumn.

FIGURE 8.4.0-1 Grid quality report

After each 3D generation, all the data of the grid quality report are stored in a report file (".qualit-yReport"). This file is stored beside the template file (".trb"). If the project has not yet been saved,the report file creation is aborted.

The quality of the 3D mesh can also be analysed block per block using the Grid/Grid Quality,

Grid/Negative Cells ( ) and View/Sweep Surfaces ( ) tools (Chapter 2).

Finally, the Grid/Grid Quality Report (HTML) menu (not available on Windows) allows to auto-matically write a mesh quality report. When selecting the menu, a window enables to select theimages that will be inserted into the report and provides disk usage necessary for the report andimages (refer to section 2-3.4.5 for more details).

8-5 Template & Mesh FilesTo manage complete mesh generation, AutoGrid5™ integrates the concept of project. AnAutoGrid5™ project involves template files and mesh files:

B2B Cut 3D Generation

AutoGrid5™ 8-7

8-5.1 Mesh Files

The mesh files contains the multiblock mesh topology, geometry, grid points, patch grouping andthe boundary condition types:

• new_prefix.bcs: boundary conditions files,

• new_prefix.cgns: grid points files (CGNS format),

• new_prefix.geom and new_prefix.xmt_txt (.X_T): geometry files,

• new_prefix.igg: topology file,

• new_prefix.qualityReport: mesh quality report file,

• new_prefix.config: mesh configuration file used for the grouping in FINE™ GUI and for theSubProject (more details in FINE™ User Manual).


� The hub and shroud curves definition are saved in the .cgns file. These data are readwithin CFView™ and used to define both blade-to-blade and meridional views.


8-5.2 Template Files

The template files contain the parameters and the geometry needed to reproduce the mesh withAutoGrid5™:

• new_prefix.geomTurbo and new_prefix.geomTurbo.xmt_txt (.geomTurbo.X_T): the geometryfiles (geomTurbo format),

• new_prefix.trb: the template file containing the grid generation parameters,

• new_prefix.info: the information file,

• new_prefix_b2b.png: a picture of the blade to blade view,

• new_prefix_merid.png: a picture of the meridional view.

8-6 B2B CutAutoGrid5™ allows to extract a blade to blade template and mesh (two layers in spanwise direc-tion) from a 3D template (license key required). Click on the Quick Access Pad/Row Definition/Add B2B Cut button to add a new folder B2B Cut containing an item B2B Cut 1 in the projecttree. Right click on that item to open a contextual menu.

3D Generation B2B Cut

8-8 AutoGrid5™

8-6.1 Edit B2B Cut

Select Edit to open the B2B Cut Definition dialog box. This dialog box is used to define the cutgeometry based on two parameters:

• Spanwise Location. The user can set the spanwise location of the cut geometry based on thepercentage value. The total span is considered as 100.0. By default the Spanwise Location isset to 50.0, which is located at the mid span.

• Spanwise Width. The width of the cut geometry is given as a percentage of the local spanwisewidth. Therefore, the width of the mesh can change along the streamwise direction.

FIGURE 8.6.1-1 Blade to blade cut at middle span

In case the flow path is already generated for all the rows, the cut definition is automatically dis-played in the meridional view with yellow lines. Two yellow lines define the domain of theexpected B2B mesh. These lines are derived from the flow paths definition of the 3D template andare controlled by the two parameters: spanwise location and width.

B2B Cut 3D Generation

AutoGrid5™ 8-9

FIGURE 8.6.1-2 Blade to blade cut with 20% of span width

8-6.2 Delete B2B Cut

The menu item Delete is used to remove the B2B cut definition from the template.

� All the files related to the B2B cut are NOT removed from the disk.

8-6.3 Create B2B Cut

The menu item Create is used to start the generation of the new template, which will be used to cre-ate the B2B mesh. An error message is displayed if the selected flow path is not generated for allthe rows.

A new directory is created using the name of the main template as prefix. In this directory,AutoGrid5™ saves the new template derived from the main geometry but with a new hub andshroud definition, based on the curves defined by the B2B Cut Definition dialog box. The new tem-plate is automatically loaded and can be used to create the B2B mesh.

� Before starting the blade to blade cut geometry creation, the current AutoGrid5™ tem-plate must be saved.

� The hub and shroud patches of the mesh are defined as mirror boundary condition.

3D Generation B2B Cut

8-10 AutoGrid5™

AutoGrid5™ 9-1

CHAPTER 9: Meridional Technological Effect

9-1 OverviewA turbomachinery configuration contains usually blade rows and also meridional effects like sealleakage, bleed or cavities. The solid body of the meridional effects is axisymmetric. Their geometryis defined by meridional curves (z,r coordinates). The domain of a meridional effect must always beconnected to one or more blade row(s).

FIGURE 9.1.0-1 Blade row with meridional effect

The mesh of these configuration entities are generated in five steps:

• definition of the meridional geometry defining the technological effect,

• definition of the new technological effect entities in the configuration database,

• choice of the connection type with the main blade channel,

• definition of the meridional mesh:

— manual blocking in the meridional space,

— automatic settings of the mesh point clustering in the meridional space,

• 3D mesh generation obtained by the combination of the meridional blocking and the mesh at theconnection(s) with the blade row(s).

Meridional effect

Meridional Technological Effect Configuration Management

9-2 AutoGrid5™

This chapter describes the grid generation of the meridional effects. The number of meridionaleffects is unlimited.

9-2 Configuration ManagementThe Rows Definition subpad of the Quick Access Pad contains features used to control the meridi-onal effects. New effects can be added into the configuration tree and managed through their con-textual menus.

FIGURE 9.2.0-1 Meridional effect management

The option Add ZR Effect creates a new entity in the configuration database and displays it intothe Meridional Techno Effects list of the tree. Right-click on this new items of the tree opens thecontextual menu of the meridional effects. It gives access to the editing mode allowing the user todefine the new effects or to delete the selected effects.

� The effects can be renamed by double-clicking on their name into the tree. An interactionarea prompts to enter a new name for the selected effect.

9-3 Geometry DefinitionThe geometry of a meridional effects is defined by (z,r) curves displayed in the meridional view.Before starting the definition of a technological effect, the geometry must be imported in the merid-ional view.

� Notice that the Geometry menu available in the meridional effect edition mode can beused to define the geometry. Nevertheless, the name (Geometry/Modify Curve/SetName...) of the created curve must contain the keyword "inlet", "outlet", "solid", "exter-nal" or "rotor_stator" to ensure the automatic definition of the boundary conditions.

Effect list

New effects

Edit selected effect

Delete selected effect(s)

Right-clickAdd a new effect

Geometry Definition Meridional Technological Effect

AutoGrid5™ 9-3

9-3.1 The ".geomTurbo" File

The curves defining the meridional effects are specified in the ".geomTurbo" file using the basic curveformat (Chapter 3).

9-3.2 CAD Import

The solid bodies of the meridional effects can be imported (Import Meridional) from external CADfiles using Import CAD window. The curves defining these bodies are selected interactively and pro-jected in the meridional view (Chapter 5).

FIGURE 9.3.2-1 Import CAD window - Import Meridional

9-3.3 User Defined

AutoGrid5™ provides geometrical features used to create the solid body of meridional effects interac-tively. New polylines can be created using Geometry Control subpad in the meridional effect editionmode and the steps needed to create these polylines are stored in the template file.

FIGURE 9.3.3-1 Edition mode - geometry control subpad

Meridional Technological Effect Definition of Meridional Mesh

9-4 AutoGrid5™

9-4 Definition of Meridional Mesh

9-4.1 Start Edition Mode

The meridional mesh of a technological effect is built into the edition mode available through the Edit menuitem of the contextual menu open when right-click on a ZR technological effect of the tree. The Quick AccessPad is updated to access the features needed to create the meridional mesh. The graphical area displays themeridional view of all the curves defining the meridional solid body of the turbomachinery. The button CloseEdition Mode of the top menu bar is used to quit the edition mode. All the actions performed during an editingsession are stored in the template file (".trb") and can be replayed on similar geometries.

The Quick Access Pad is divided into four main areas (subpad):

• the Geometry Control provides options used to create polyline.

• the Topology Control is used to fill the domain of the effect with several structured 2D blocks.

• the Topology Default is used to set up automatically the grid points clustering into the defined blocks

• the View page is used to control the visualization inside the graphics area.

FIGURE 9.4.1-1 Edition mode

Quit Edition Mode

Definition of Meridional Mesh Meridional Technological Effect

AutoGrid5™ 9-5

9-4.2 Edition Mode

An editing session is divided into three main steps.

9-4.2.1 Geometry Control

The Geometry Control subpad of the Quick Access Pad provides five options to add polylines. Thesecurves are eventually used to close the domain defined by the solid body or to create the separation linein case of multiple connections (see section 9-5.2).

� It is not required to add a curve at the connection between the blade channel (hub or shroud)and the meridional effect. Automatically the hub and shroud curves will be used as limit ofthe meridional effect.

When a button is pressed, an interactive tool is started waiting for points input:

• Left-click to confirm the creation of a new control point of the polyline.

• Right-click to finish the creation process and stop the tool.

During the creation process, automatic attraction is done on the curve display in the graphics area.

FIGURE 9.4.2-1 Geometry generation

polyline generation tool

Open geometry must be closed using a polyline

Effect with multiple connections withthe main blade channel must be dividedby a rotor/stator polyline


9-6 AutoGrid5™

The type of the polyline can be inlet, outlet, external, solid or rotor/stator. The type is chosenaccording to the CFD requirement.

� It is not recommended to have a meridional effect covering a rotor/stator control line inthe blade channel.

FIGURE 9.4.2-2 Meridional effect vs. rotor/stator interface

� When creating a separation line, a rotor/stator polyline must be used.

In case of blunt edges, meridional control lines (Zcst line) can be added at the leading and/or thetrailing edge(s) by activating the corresponding options in the Mesh page of the Define B2B Topol-ogy for Active Blade dialog box (section 6-2.4.1). At the end of the 3D generation, the hub and theshroud patches of the mesh are divided (black dots) at the Z cst lines located at the leading and/ortrailing edge in order to allow a matching connection with a ZR effect. When editing the ZR effect,new points (black dots) are displayed to attract the block vertices at the exact point to assume amatching connection between the ZR effect and the core flow.

FIGURE 9.4.2-3 Block management with the control points

9-4.2.2 Topology Control

The domain defining a technological effect must be filled by several structured 2D blocks. Theblock edges are mapped on the geometry. The Topology Control subpad provides the tools to cre-ates and control the blocks.

BLADE 1BLADE 2

Rotor/Stator Interface

Meridional Effect

OUTLETINLET LEADINGEDGE

TRAILINGEDGE

BLADE

HUB

SHROUD

mapping


AutoGrid5™ 9-7

FIGURE 9.4.2-4 Topology definition

The Topology Control subpad provides six tools used to create and control the blocks topology.

a) Create & Modify New Block

The icon starts the block creation tools. When moving the mouse into the graphics area a defaultblock geometry appears. Left-click twice to select the location of two opposite corners of the blockand left-click again to confirm the creation. The four vertices defining the corners of the block aredisplayed. These vertices can be selected interactively (left-click) and mapped (attracted) onto thegeometry. The block edges are automatically mapped on the geometry curves if their vertices aremapped on an underlying curve.

� Block connection must be established on the separation lines (Figure 9.4.2-5) and themapping of vertices respected (no orphan vertices).

� When a separation line is used, the block should be connected to the rotor/stator polylinewith a complete face. For example, in Figure 9.4.2-6, in both cases, the block 2 is onlypresenting a vertex linked to the rotor/stator polyline and not a full face. In such cases,the meridional effect will not be meshed and lead to a warning. The solution is thus tomove the separation line in a more appropriate area.

FIGURE 9.4.2-5 Block vertices mapping

Four blocks topology

Topology controltools

separation line


9-8 AutoGrid5™

FIGURE 9.4.2-6 Block face not fully connected on separation line (rotor/stator polyline)

b) Delete Existing Blocks

The icon opens the dialog box used to delete several existing block.

FIGURE 9.4.2-7 Delete block(s)

Select the block interactively (left-click on an edge) and press the button Delete into the dialog boxDelete blocks. Confirm the deletion into the confirmation box.

c) Insert New Control Vertices

The icon is used to insert a new control vertex on a edge. It is needed when the edge must bemapped on multiple curves: a vertex must be added at each boundary of the mapped curves.

� Use the short-cut <i> to activate this command in a faster way.

d) Grid Points Clustering

The icon opens a dialog box use to control manually the grid points clustering along each edge ofthe blocks when the automatic default topology is not used (Default Topology subpad).

e) Grid Point Number Control

The number of points on each edge can be controlled manually through the dialog box Set Numberof Points when the automatic default topology is not used (Default Topology subpad). Right-clickon the desired edge to access the contextual menu and select the item Set Number of Points.

Rotor/Stator Interfacein ZR Effect

Block 2

Block 1

Rotor/Stator Interfacein ZR Effect

Block 2

Block 1

ZR Effect 1 ZR Effect 2

Confirmation box


AutoGrid5™ 9-9

FIGURE 9.4.2-8 Control the number of points

Enter the new number of points in the Set Number of Points area and press Apply.

9-4.2.3 Automatic Default Topology

The manual settings described in section 9-4.2.2.d and section 9-4.2.2.e are optional. AutoGrid5™provides a feature to set up automatically the number of points and the grid points clustering.Before starting if necessary the manual edition of the grid point number and the grid point cluster-ing, described in section 9-4.2.2.d and section 9-4.2.2.e, an automatic setting must be performed.The defaults are computed according to four parameters:

• the maximum expansion ratio of the cells along the solid body of the effect.

• the percentage of cells with equal width on the solid boundaries.

• the first cell width in the boundary layer.

• the coarsest grid level requested to impose the number of grid points that will respect the con-straints related to the multigrid treatment within FINE™ GUI (default level is set to 3).

FIGURE 9.4.2-9 Default grid points clustering

expansion ratio = 1.8% cst. cell = 0

expansion ratio = 1.4% cst. cell = 33


9-10 AutoGrid5™

� Each time the button Default Topology is pressed, all the manual settings are erased bythe new default.

9-4.2.4 Optimization Steps

The Optimization Steps parameter in the Topology Default subpad allows the user to specify thenumber of iteration done by the optimization system.

9-4.2.5 Radial Expansion

When the effect simulate the expansion of the main blade channel mesh to the far field (wind tur-bine), the Radial Expansion option activates full optimization of the far field mesh to avoid highclustering of the mesh in this region of the domain. The Far Field Smoothing Steps parameter con-trols the number of optimization steps that will be applied.

9-4.2.6 Automatic Detection Tools

The button Detect Unmapped Edges is used to visualize the face edge unmapped on an existingmeridional curves. Check the vertices linked to the edges. The unmapped edges are displayed in theview and the number of detected unmapped segments appears in the message area.

FIGURE 9.4.2-10 Visualize unmapped edges

The buttons Detect Channel Matching/FNMB Connection are used to detect the type of connectionbetween the meridional effect and the blade channel (more details in section 9-5.1) according to anabsolute connectivity tolerance (Matching Tolerance) by default set to 1e-8.

FIGURE 9.4.2-11 Visualize channel matching connection


AutoGrid5™ 9-11

When the Periodic Full Non Matching option is active, the full non matching connection of themeridional effect with the channel mesh will not follow the shape of the blade to blade mesh. Thatallows to reach a better mesh quality in the meridional effect. In Figure 9.4.2-12, the blocks of themeridional effect connected to the channel mesh are twisted when the option is not active and thatmay damage the grid quality.

FIGURE 9.4.2-12 Periodic Full Non Matching option

When the Propagate Theta Deviation option is active, when the number of blocks is above 2 inthe ZR effect, the angle deviation of the connected mesh will be propagated and allow in specificcases to avoid mesh with bad orthogonality.

Two blocks inZR effect

Meridional Technological Effect Connection with Main Blade Channel

9-12 AutoGrid5™

9-5 Connection with Main Blade Channel

9-5.1 Connection Types

The connections between the main blade channel row meshes and the mesh created into a ZR tech-nological effect domain are full non-matching by default. To obtain a matching connection, controllines must be added (Chapter 6) at the connection points between the meridional effect and the mainblade channel.

FIGURE 9.5.1-1 Connection with main blade channel

When the option Periodic Full Non Matching is active (by default), a periodic full non matchingconnection with repetition (section 2-3.4.2) will be created between the ZR effect and the meshchannel to improve the mesh quality in the ZR effect.

� To improve non-matching connections, it is advised to add control lines at the connectionpoints and to switch off their B2B Control (Figure 6.2.4-2).

� When the grid points distributions in the streamwise direction in the blade row mesh istoo coarse at the connection level, mesh overlaps can appear in the mesh of the con-nected effect. Too avoid this, the number of points in the row can be increased or match-ing connection must be used.

FIGURE 9.5.1-2 Mesh problem with non-matching connection

Z constant lines

Connections

Row Mesh

Connection with Main Blade Channel Meridional Technological Effect

AutoGrid5™ 9-13

If the control lines are correctly set, the matching connection can be ensured for all the connectiontypes:

FIGURE 9.5.1-3 Connection types

9-5.2 Multiple Connections

Some of the technological effects have several connections with the main blade channel, i.e. a sealleakage have a connection upstream the blade and a connection downstream the blade. In this casethe mesh created inside the domain of the effect is divided into two parts: one starting from the inletand one starting from the outlet. At the middle part of the seal leakage, a line must be defined indi-cating the location of the division. At this line (Rotor-Stator Polyline), defined in the edition mode(Figure 9.4.2-1), the two parts of the mesh will be connected by a non-matching periodic connec-tion if the connections with the main blade channel are related to the same row (case 1) or a rotor/stator interface if the connections with the main blade channel are related to different rows (case 2).

FIGURE 9.5.2-1 Multiple connections with main blade channel

upstream - blade - downstream connections

from inlet to outlet connection

both on upstream & blade connection

both on downstream & blade connection

Part 1 Part 2

Connection line

Connection with main blade channel

Part 1 Part 2

Connection line

Connection with main blade channel CASE 2: connection line becomes aCASE 1: connection line becomes a

non-matching connection between part 1and part 2

rotor/stator interface between part 1 and part2

Meridional Technological Effect 3D Generation

9-14 AutoGrid5™

9-6 3D Generation

FIGURE 9.6.0-1 3D mesh of the technological effect

The 3D generation of the meridional effect must be performed together with the generation of therow(s) connected with them. Select the row(s) and their attached meridional effects and press theGenerate 3D button of the top menu bar.

Selection of the technological effectand the connected row(s) start 3D generation

Row Mesh

Part 1 and Part2of the effect

Periodic connection

AutoGrid5™ 10-1

CHAPTER 10: 3D Technological Effect

10-1 OverviewA turbomachinery configuration contains usually blade rows and also 3D effects like cooling holes.The solid body of the 3D effects are non-axisymmetric. Their geometries are defined by 3D curvesor surfaces (x,y,z coordinates). The 3D effects are always linked to one blade row(s).

The mesh of these configuration entities are generated in 3 steps:

• definition of the new technological effect entities in the configuration database

• geometry definition of the domain defining the technological effect

• definition of the 3D mesh:

— manual blocking in the 3D space

— load a existing template in the effect library

This chapter describes the grid generation of 3D effects. The number of 3D effects is unlimited.

10-2 Configuration ManagementThe Rows Definition subpad of the left Quick Access Pad contains features used to control the 3Deffects. New effects can be added into the configuration tree and managed through their contextualmenus.

A 3D effect belongs to a row. The related row must be selected before creating a new effect. Theoption Add 3D Effect creates a new entity in the configuration database and display it into the rowselected in the tree. Right-click on this new items of the tree opens the contextual menu of the 3Deffects. It gives access to:

• Edit : the editing mode allowing the user to define mesh of the new effects

• Load Geometry : the geometry definition. A file chooser is used to select the geometry data filecontaining the curves and surfaces defining the effect body.

• Delete Effect(s) : the effect deletion tools

• Library : the effect library

3D Technological Effect Geometry Definition

10-2 AutoGrid5™

• Copy/Paste Topology : the copy/paste topology feature allowing the user to apply to an effectthe topology of another.

The effects can be renamed by double clicking on their name into the tree. A interaction areaprompts to enter a new name for the selected effect.

FIGURE 10.2.0-1 3D effect management

10-3 Geometry DefinitionThe geometry of a 3D effects is defined by (x,y,z) curves and/or surfaces displayed in the XYZview when editing the effect. Before starting the definition of the mesh of a technological effect, thegeometry can be defined through:

10-3.1 External Data File

The curves and surfaces defining the solid body of one effect are stored into one file. The contex-tual menu item Load Geometry opens a file chooser to select this file.

10-3.2 CAD Import

The solid bodies of the 3D effects are stored in multiple data files. The Geometry Definition/Import and Link CAD menu opens the Import CAD window allowing the user to select and linkdata curves and surfaces defining the solid body of the selected effect in the tree.

� All the grid generation process of the 3D effect is stored into a python script. During thegrid generation, the names of the geometry entities are used to identify the topologylinks. As the name of each geometry entity must be unique, it is impossible to reuse thegrid generation method of one effect to another without respecting the following rule: thename of each entity must be composed with a prefix and a suffix separated by a # charac-ter. The prefix is used to identify the effect and the suffix is used to make the link withthe topology (i.e.: effect1#curve1).

contextual 3d effect menu

Effect list

New effects

Edition Mode 3D Technological Effect

AutoGrid5™ 10-3

10-4 Edition ModeThe meridional mesh of a technological effect is build into the edition mode available through theEdit menu item of the contextual menu open when right click on a 3D technological effect of thetree. The Quick Access Pad is updated to access the features needed to create the 3D mesh. Thegraphical area displays in the 3D view all the curves and surfaces linked to the effect and the rowmesh related to the effect.

FIGURE 10.4.0-1 Start edition mode

All the operations performed during an editing session are stored into a script. The grid generationoptions available in the Quick Access Pad are fully described in the IGG™ User Manual.

The mesh generation of a 3D technological effect is performed by creating structured blocks used tofill the domain covered by the effect.

Right click on the desired effect opens acontextual menu. The menu itemEdit start the edition mode

Quit Edition Mode

Hole geometry

Row mesh

3D Technological Effect Topology Management

10-4 AutoGrid5™

FIGURE 10.4.0-2 Effect domain and mesh

The edition mode is left by clicking on the Close Edition Mode button.

10-5 Topology Management

10-5.1 3D effect library

When an effect has been created, the mesh definition process can be stored in a dynamic library.

FIGURE 10.5.1-1 3D effect library management

Topology list

Overwrite or createa new library item

Library access

Topology Management 3D Technological Effect

AutoGrid5™ 10-5

The contextual menu item Library opens the dialog box 3D Technological Effect Library. This dia-log box contains the list of the available topology. The selected topology can be loaded and apply tothe selected 3D effect using the button Load. The selected topology can be remove from the listusing the button Remove. The topology of the active 3D effect can be stored in the library using thebutton Save: the dialog box Save 3D Topology is opened allowing the user to define a new 3Dtopology or to overwrite an existing one.

� The selected topology can be applied simultaneously to several similar 3D effect. If thegeometry of the effect is already loaded, the mesh is automatically generated using theselected topology.

10-5.2 Copy/Paste Feature

The 3D mesh topology of the selected 3D effect can be copied into a buffer and apply to other effectusing the contextual menus Copy Topology and Paste Topology. Several similar effects can beselected to apply simultaneously the topology stored in the buffer using the Paste Topologyoptions.

FIGURE 10.5.2-1 Topology copy & paste on several effects

Copy/Paste Topology access

3D Technological Effect 3D Generation & Persistency

10-6 AutoGrid5™

10-6 3D Generation & PersistencyThe mesh generation is performed by the Generate 3D button. All the selected 3D effects are gener-ated after the selected rows and the selected meridional effects.

FIGURE 10.6.0-1 3D mesh of the technological effect

The 3D effect generation is stored into the template file (".trb") using python script format:

NI_BEGIN 3d effect NAME3d techno effect 1NI_BEGIN ni3dlayer_recorderNI_BEGIN ni3dlayer_recordeffect_techno3d_Block_1=new_block(Point(0.0710714235901833,0.169539034366608,-0.071651391685009),Point(0.0710714235862563,0.169539034370535,-0.0786721184810469),Point(0.0710714235811796,0.175077691649889,-0.071651391681911),Point(0.0710714235772526,0.175077691653816,-0.0786721184779489),Point(0.0836308076926963,0.169539034346191,-0.071651391692034),Point(0.0836308076887693,0.169539034350118,-0.0786721184880719),Point(0.0836308077017,0.175077691670305,-0.071651391688936),Point(0.083630807697773,0.175077691674232,-0.0786721184849739))move_vertex(vertex("effect_techno3d_Block_1",2,1,2),CurvePointNorm("surface1_bnd_3",0.326043824876047))move_vertex(vertex("effect_techno3d_Block_1",2,1,1),CurvePointNorm("surface1_bnd_3",0.710139595042077))move_vertex(vertex("effect_techno3d_Block_1",2,2,1),CurvePointNorm("surface1_bnd_1",0))move_vertex(vertex("effect_techno3d_Block_1",2,2,2),CurvePointNorm("surface1_bnd_3",0.157843756497119))move_vertex(vertex("effect_techno3d_Block_1",1,2,1),CurvePointNorm("curve1",1))move_vertex(vertex("effect_techno3d_Block_1",1,2,2),CurvePointNorm("curve1",0.162994599914628))move_vertex(vertex("effect_techno3d_Block_1",1,1,1),CurvePointNorm("curve1",0.728237079858547))move_vertex(vertex("effect_techno3d_Block_1",1,1,2),CurvePointNorm("curve1",0.431818181829508))NI_END ni3dlayer_recordNI_END ni3dlayer_recorderNI_END 3d effect

� When making a 3D effect in AutoGrid5™, it may be necessary to create some additionalcurves. The steps creating these curves are recorded in the template but the template can-not be replayed without manual modification as the curve names vary per IGG™ ses-sion. Therefore the user should either import an external CAD file with pre-definednames or the user should (re)name the curve immediately after creation in the interface,otherwise because of the curves and surfaces naming, the project may fail.

Selection of the technological effectand the connected row start 3D generation

Row Mesh

3D Effects

AutoGrid5™ 11-1

CHAPTER 11: Cooling & Conjugate Heat Transfer Modules

11-1 OverviewThis chapter describes the conjugate heat transfer and the cooling capabilities included inAutoGrid5™:

• The conjugate heat transfer (CHT) capability allows the mesh generation of the blade and theend wall solid bodies.

• The cooling capability allows the mesh generation of basin, basin holes, blade holes, end wallholes and cooling channel with pins fins and ribs.

� The module is only compatible with the default O4H topology on single blade configura-tion and thus not for splitter(s) or tandem rows configuration

11-2 Conjugate Heat TransferBy default AutoGrid5™ generates the mesh of the core flow around the blades including the huband shroud gap area. The conjugate heat transfer module allows the mesh generation of the solidbody of the blade and the end walls.

11-2.1 Mesh of Blade Solid Body

The menu item Blade/Add Solid Body can be used to activate the generation of the solid body ofthe blades. A new item is automatically added into the configuration tree indicating that the solidbody generation is activated.

Right-click

Cooling & Conjugate Heat Transfer Modules Conjugate Heat Transfer

11-2 AutoGrid5™

The mesh into the blade is created using a butterfly topology like in the shroud/hub gap. The con-nection between the solid body and the fluid area is matching.

FIGURE 11.2.1-1 Mesh of the blade solid body

Once the solid body generation has been activated, right-clicking on the new item in the tree opensa contextual menu of the solid body.

This menu gives access to:

• Delete: deletes the solid body entry from the configuration tree.

• Configuration: opens a dialog box to choose one of the twelve solid body configurations. Clickon the desired image to choose the solid body configuration.

FIGURE 11.2.1-2 Blade solid body configuration

Conjugate Heat Transfer Cooling & Conjugate Heat Transfer Modules

AutoGrid5™ 11-3

By default, the blade solid body configuration ( ) type is chosen. All the other choices imply

the definition of an internal offset shape of the blade. This is used to define the basin, the squillertip, the cooling channel area or the area inside which spanwise holes are defined. In such cases, themesh topology covering the solid body area of the blade is divided into four blocks: two blocks fora butterfly topology covering the area inside the internal offset shape and two blocks defininganother butterfly topology in the area between the offset and the blade definition.

The blade solid body is not applicable:

• for multi-splitter configuration (except for the default blade solid body configuration)

• for blunt blades (except for the default blade solid body configuration)

11-2.1.1 Solid Body Configuration

Depending of the type of the solid body, the configuration tree will automatically updated. Indeed,the entries controlling the basin depth, the basin wall width, the cooling channel, the tip wall widthwill be automatically introduced into the Solid Body folder in the configuration tree. In addition,shroud gap and or hub gap entry can also be added or removed automatically when changing thetype of solid body. Following sections describes the twelve available types of solid body and theircorresponding configuration tree.

a) Solid Body Configuration (Default)

In this configuration, the blade solid body is meshed using a butterfly topology like in the shroud/hub gap. The connection between the solid body and the fluid area is matching (Figure 11.2.1-1).

b) Solid Body + Spanwise Holes Configuration

In this configuration, the blade solid body is meshed and spanwise holes are allowed. A shroud gapor hub gap can be defined.

internal offsetblade


11-4 AutoGrid5™

c) Solid Body + Cooling Channel Configuration

A shroud gap must be defined in this configuration. The blade solid body is meshed and a tip walland a cooling channel are defined. Spanwise tip wall holes and blade holes are allowed.

� Similar configuration with hub gap is not available

d) Solid Body + Basin Configuration

A shroud gap must be defined in this configuration. The blade solid body is meshed and a basin isdefined. Spanwise holes are allowed.


e) Solid Body + Basin + Cooling Channel Configuration

A shroud gap must be defined in this configuration. The blade solid body is meshed and a coolingchannel, a basin and a basin wall are defined. Spanwise basin wall holes and blade holes areallowed.



AutoGrid5™ 11-5

f) Solid Body + Cooling Channel Configuration

In this configuration, the blade solid body is meshed and a cooling channel is defined. Blade holesare allowed. A shroud gap or hub gap can be defined but the tip wall has no width.

g) Solid Body + Penny Configuration

A shroud and/or hub gap must be defined in this configuration. The blade solid body is meshed anda penny is defined at hub and/or shroud. Spanwise tip wall holes and blade holes are not allowed.

The location and the diameter of the penny can be controlled in a way similar to the basin hole.

h) Solid Body + Squiller Tip Configuration

A shroud gap must be defined in this configuration. The blade solid body is meshed and a squillertip is defined. Spanwise tip wall holes and blade holes are not allowed. Three types of squiller tipsare available.



11-6 AutoGrid5™

11-2.1.2 Internal Offset Shape Control

In a cooled turbine blade, basin and internal cooling channel area are defined by a unique offset sur-face area of the blade. The squiller tips are defined in a similar way.

The geometry definition of the offset surface is done using the Cooling Geometry Definition dialogbox available when right-clicking on Solid Body in the configuration tree and selecting the DefineInternal Geometry menu.

The surface(s) defining the internal lateral cooling area and the basin can be defined as a blade def-inition from:

• a parametric definition using the blade definition as reference.

• an external ".geomTurbo" file.

• an external CAD data file.

a) Parametric Mode

By default when a cooling wall has been defined, AutoGrid5™ is using a parametric definition forthe cooling wall. The default parameters can be modified in the Cooling Geometry Definition dia-log box.

internal offset

blade

left-click


AutoGrid5™ 11-7

The user can control the shape of the offset (by left-clicking on the entity when highlighted in red)and the type of offset at the trailing edge (Blunt Trailing Edge option). If the blade to blade gener-ation has already been performed, the new curve defining the offset is automatically displayed inthe blade to blade view.

In addition, the Control Points Number along the chord used to defined the offset can be alsomodified.

The shape of the offset area is defined according to starting and ending distance along the chord andthe width is computed normally to the chord definition.

b) External ".geomTurbo" File

If the internal offset surface is defined using a ".geomTurbo" file, the option From External Datahas to be activated.

When clicking on the Load a Geometry File button, a file chooser allows to select an external".geomTurbo" file. If the offset definition is blunt, an automatic blending (using circular shape) canbe performed to close the cooling wall surface (Blend at Leading/Trailing Edge options).

A geometry check can be performed when clicking on the Check Geometry button to detect possi-ble problems in the geometry definition (the dialog box is presented in section 5-7.1).

c) External CAD Data File

If the internal offset surface is defined using an external CAD file, the option From External Datahas to be activated.

When clicking on the Load a Geometry File button, a file chooser allows to select an external CADfile. After the selection, the Import CAD window displays the data and the manual linking must beperformed to define the blade surfaces, the leading edge and the trailing edge as for the blade defi-nition (more details in section 5-3).

If the offset definition is blunt, an automatic blending (using circular shape) can be performed toclose the cooling wall surface (Blend at Leading/Trailing Edge options)


11-8 AutoGrid5™

A geometry check can be performed when clicking on the Check Geometry button to detect possi-ble problems in the geometry definition (the dialog box is presented in section 5-7.1).

11-2.1.3 Leading/Trailing Edge Wizard

The leading and trailing edge curves can be defined by the user by adding a wizard to the solid bodythrough the menu Add Wizard LE TE. This menu will add an item Wizard LE TE in the solidbody configuration tree. More details are available in section 5-5.3.

11-2.1.4 Basin / Tip Wall / Basin Bottom Wall Definition

The basin depth, the tip wall and the bottom basin wall width are defined as for shroud/hub gaps, bygiving a width at the leading edge and at the trailing edge. In addition as for the gaps, the number oflayer (Number of Points) and the layer clustering (Cell Width and Percentage of Mid-flow Cells)to define the basin, tip wall and basin wall in the meridional view can be controlled.

The contextual menu Properties when right-clicking on the configuration tree on Basin, Tip Walland Basin Wall opens the corresponding dialog box allowing to control these parameters.


The Mesh Properties dialog box gives access to the mesh generation control parameters, whenright-clicking on Solid Body in the configuration tree and selecting the Mesh Properties menu;


AutoGrid5™ 11-9

a) Blade to Blade Control

a.1) Internal Cooling Wall Streamwise Distribution.

Near the trailing edge, by default (Optimized option) the grid points distribution along the solidwall of the blade is clustered around the location of the internal cooling wall definition.

If the option Same as blade Wall is selected, the grid points distribution along the internal solidwall will follow the clustering of the blade wall.

The number of points (N) located between the end of the cooling wall and the trailing edge can bemodified using the parameters Number of Points at Trailing Edge. When this number isincreased, the number of points on both sides of the blade also is increasing.

Clustering

N

n

N2


11-10 AutoGrid5™

a.2) Number of Points in O-Mesh (Solid Blade Area)

The number of points (N2 in above figure) in the azimuthal direction defining the width of the blade solidmesh can be modified with the parameters Number of points in O mesh (Solid Blade Area).

The clustering in the azimuthal direction defining the width of the blade solid mesh can be switched offwith the parameter Relax the B2B Mesh Clustering.

a.3) Special Configuration: Inserted Cooling Tube

When the configuration is presenting inserted cooling tubes, these entities can be meshed by defining acooling channel (section 11-2.1.2) and a skin wall.

The inserted cooling tube will be considered as a blade including a cooling channel (fluid block) and theskin wall will be used to mesh the fluid area outside of the tube but inside of the real blade.

Blade Solid Body

Inserted Cooling Tube

Skin WallCooling Channel

Inserted Cooling Tube

Skin WallCooling Channel

Blade

Blade

Skin Block

Cooling Channel

Blade


AutoGrid5™ 11-11

The clustering near the trailing edge of the cooling wall is no more suitable for inserted coolingtubes. Furthermore, the parameter Internal Cooling Wall Streamwise Distribution must be set tothe value Same as blade Wall.

The boundary shape of the skin mesh around the blade can also be imposed using the Add SkinWall menu when right-clicking on the Main Blade in the configuration tree. A new entity namedSkin Mesh Boundary is displayed in the configuration tree.

The contextual menu Define Geometry when right-clicking on the Skin Mesh Boundary in the con-figuration tree allows to select a ".geomTurbo" file defining the boundary of the skin mesh.

After selecting Skin Mesh Boundary in the configuration tree, the skin wall can also be definedusing the Import CAD window by linking the blade surfaces, the leading edge and the trailing edgeas for the blade definition (more details in section 5-3).

In addition, two control lines (defined in the spanwise direction) can be added into the ".geom-Turbo" file to define two local points of the skin wall shape that needs to be captured by the mesh.These grid lines are useful in case of a skin wall that has to be connected (full non matching con-nection) afterwards with the solid mesh parts of the real blade.

These lines are defined using the following format into the geomTurbo:

trailing_edge_ctrl_lineDown

XYZ

17

20.8472883616038 260.874260274711 34.1192884895623

21.7475411710475 264.244225444529 33.8239451407291 …

trailing_edge_ctrl_lineUp

XYZ

17

15.6694535592452 261.001553719178 29.429748564263

16.4764220438766 264.405454725162 29.0497779354983 …

Right-click

Right-click


11-12 AutoGrid5™

Finally, when the cooling channel and the skin wall are defined, the mesh of the inserted coolingtube area can be meshed after deactivating the option Around the Skin Mesh in the 3D Control aspresented in section below.

b) 3D Control

The Activate Mesh Generation parameters control the areas that will be removed from the meshafter the grid generation of the blade holes (section 11-3).

� The Layer Control (%span) in the Mesh Control/Row Mesh Control area of theQuick Access Pad is not available when generating the mesh of the blade solid body.

11-2.2 Mesh of End Wall Solid Body

By default, AutoGrid5™ creates the fluid core flow around the blade and the boundary conditionwith the solid body of the end walls is set to solid. The menu items Row/Add Hub Wall and Row/Add Shroud Wall can be used to mesh a part of the end walls automatically within AutoGrid5™.The items Hub Wall and Shroud Wall are automatically added into the configuration tree.

Solid Block

Solid Block

Full Non Matching

Connections

Trailing Edge Curves

Right-click


AutoGrid5™ 11-13

11-2.2.1 Geometry Definition

The Properties menu available when right-clicking on the Hub Wall and/or Shroud Wall in the con-figuration tree opens a dialog box used to control the width of the selected end wall.

The end walls representation is automatically displayed in the meridional view.

11-2.2.2 Topology Definition

The Properties menu available when right-clicking on the Hub Wall and/or Shroud Wall in the con-figuration tree opens a dialog box used to control the number of points used to mesh the end wall inthe spanwise direction and the width of the end wall.

The mesh is created using a matching connection between the core flow and the solid body of theend wall and therefore no more parameters are needed to control the mesh generation.

The Generation Type allows to control the mesh generation in the end walls: normal to the wall oralong Z-cst lines (Radial (Z cst)).

Cooling & Conjugate Heat Transfer Modules Cooling - Blade Holes

11-14 AutoGrid5™

11-2.2.3 3D Mesh Generation

The Generate menu available when right-clicking on the Hub Wall and/or Shroud Wall in the con-figuration tree is used to start the 3D generation of the selected end wall. The 3D mesh of theselected end wall will only be generated if the 3D mesh of the core flow is already available.

The option Generate End Wall available when pressing the Generate 3D button of the top menubar can also be activated to involve the grid generation of the end wall after the mesh generation ofthe selected row.

11-3 Cooling - Blade HolesThe meshes generated by AutoGrid5™ using the default topology contain one block surroundingthe blade, called the skin block. This block is used to generate high grid quality in the boundarylayer. The solid body of the blade contains also a similar O-block connected to the skin block usinga matching connection in configurations where a cooling wall has been defined,

These blocks will take an important place in the methodology used to create the mesh in the bladeholes and around the blade holes. They will be called matrix blocks in the following sections.

11-3.1 Blade Holes Methodology

When adding a cooling hole in the blade, the following steps will be performed to create the meshin the blade hole and around the blade hole:

Cooling - Blade Holes Cooling & Conjugate Heat Transfer Modules

AutoGrid5™ 11-15

1. ·The intersections between the hole (or hole line) and the matrix are computed by AutoGrid5™.

2. ·The intersection curves are projected in the parametric space of the matrix.

3. ·A default mesh topology inside and around the hole definition is created.

The topology is composed by eight blocks surrounding the holes, a butterfly topology inside theholes and a O block defining the boundary layer around the hole.

4. ·A default mesh is created using the row mesh clustering based on the parameters selected in theMesh Control/Row Mesh Control area of the Quick Access Pad.

5. The mesh is optimized.

6. ·The hole mesh is projected in the 3D space and the matrix block is divided. The hole meshesreplace some of the divided matrix areas.

7. The connection between the matrix area and the core flow becomes full non matching.

8. The connection between the internal cooling area (cooling channel, basin, basin wall) and thesolid body of the blade becomes full non matching.


11-16 AutoGrid5™

9. The matrix is divided in spanwise direction near the hub and the shroud to preserve the bound-ary layer of the main channel. The connection between the upper part of the matrix and the mid-dle part becomes full non matching. The connection between the lower part of the matrix andthe middle part becomes full non matching.

10. The matrix is divided in meridional direction according to the hole line mesh location. The con-nection between the hole line mesh and the matrix becomes full non matching.

11-3.2 Blade Holes Properties

The Add Hole Line menu available when right-clicking on Main Blade adds a new hole line entityin the configuration tree. By default a new hole line contains a single hole that is automatically dis-played in the meridional view.

Right-click


AutoGrid5™ 11-17

The Properties menu available when right-clicking on the holes line 1 opens a dialog box to control thegeometry and the mesh of the selected line of holes.

The Preview 3D and Hide 3D buttons (as the Preview/Hide 3D Location menus) are used to perform aquick display of the 3D definition of the cylinder used to define the holes. The 3D display is only available ifthe matrix block is available when the 3D mesh generation of the row has already been completed. Eachmodification of any hole lines parameter implies an automatic refresh of the display.


In the Blade Cooling Holes Line Definition, the Geometry thumbnail gives access to the parameters control-ling the geometry of the line of holes.

a) Holes Number Control

The number of holes in a line can be modified through the parameter Number of Hole on the Line.

b) Holes Shape Control

Seven different types of holes can be defined: circular, rectangular, oval, circular at trailing edge (trailingedge holes), groove at trailing edge, 4 sided and oval at trailing edge.

Right-click


11-18 AutoGrid5™

For each type, the parameters controlling the geometry are different.

� The trailing edge grooves are only available for mesh with blunt cooling wall.

c) Holes Location Control

The location of a hole is defined by the 3D anchor point of its axis. Three modes can be used todefine this point.

c.1) Parametric Mode

Using the Parametric mode, the side (Upper Side/Lower Side) of the blade where the holes mustbe located is selected as well as the Spanwise Location and the Streamwise Location.

The Spanwise Location is defined by the meridional starting (Start) and ending (End) point of theline. These locations are given in percentage of span. The holes are automatically redistributedusing an equidistant distribution.

The Streamwise Location can be entered using three modes:

• % of meridional chord: the streamwise location is computed in the meridional plane by givinga percentage of the distance between the leading edge and the trailing edge.

• % of arc length from LE: the streamwise location is computed in the 3D space by giving a per-centage of the arc length along the blade definition starting from the leading edge.

• % of arc length from TE: the streamwise location is computed in the 3D space by giving a per-centage of the arc length along the blade definition starting from the trailing edge.

� When using the % of meridional chord mode, the quick display will be an approxima-tion of the hole location.

c.2) XYZ Mode (Px,Py,Pz)

Using the Px,Py,Pz mode, the axis anchor point location of each hole of the line is directly enteredin absolute Cartesian coordinates.

c.3) RTHZ Mode (Pr,Pth,Pz)

Using the Pr,Pth,Pz mode, the axis anchor point location of each hole of the line is directly enteredin absolute cylindrical coordinates.

� The Parametric mode is applied to the entire holes line. Each modification of a parame-ter affects all the holes of the line. To modify a single hole location, first the parametricmode is used to define globally the hole line, than the mode can be switched to XYZ(Px,Py,Pz) or RTHZ (Pr,Pth,Pz) mode to relocate the selected hole.


AutoGrid5™ 11-19

d) Holes Axis Control

The axis of each hole can be controlled separately and/or globally for all the holes belonging to aline using three different modes.

d.1) Parametric Mode

The axis is controlled by giving the spanwise (Alpha) and the streamwise (Beta) deviation from theblade surface normal.

d.2) XYZ Mode (Vx,Vy,Vz)

The axis is given by entering the three absolute Cartesian coordinates of the vector (Vx,Vy,Vz).

d.3) RTHZ Mode (Pr,Pth,Pz)

The axis is given by entering the three cylindrical coordinates of the vector (Vr,Vth,Vz).

� The Parametric mode is applied to the entire holes line. Each modification of a parame-ter affects all the holes of the line. To modify a single hole axis, first the parametric modeis used to define globally the hole line, than the mode can be switched to XYZ(Vx,Vy,Vz) or RTHZ (Vr,Vth,Vz) mode to change the axis of the selected hole.

e) Holes Dimension Control

The dimension of the holes depends of the shape chosen in section 11-3.2.1.b.

e.1) Circular Shape

When circular shape is selected, the diameter and the depth of the holes can be imposed (each holecan be controlled separately).

� When a cooling wall is defined, the depth is only used for quick visualization of the holelocation.

e.2) Rectangular & Oval Shapes

When rectangular or oval shape is selected, the width, the height and the depth of the holes can beimposed (each hole can be controlled separately).

� When a cooling wall is defined, the depth is only used for quick visualization of the holelocation.


11-20 AutoGrid5™

e.3) Trailing Edge Groove Shape

When the location of the groove is defined using the Parametric mode, the height of the groovemust be entered.

e.4) 4-Sided Shape

The four points coordinates defining the shape of the quadrilateron must be entered.

f) Holes Orientation Control

For rectangular, oval and 4-sided shapes, the holes height is aligned with the spanwise direction.The rotation angle around the normal to the blade surface can be specified (Angle).

g) External Holes Definition File

The hole geometry can be defined using an external data file through the Load Geometry Filemenu available when right-clicking on the holes line 1. A file chooser allows to select an externalhole line file. The file formats used to define hole line are presented in sections below.

The Export Holes Geometry menu available when right-clicking on the holes line 1 is used toexport the hole line definition into an external file. The name of the file is automatically chosenaccording to the grid configuration and the project file name. Therefore, before exporting a holeline geometry, the project must be saved. For example, when exporting the "holes line 5" of aproject named "moduleCHT-section_2", the name of the data file will be "moduleCHT-section_2_row_2_Main_Blade_holes_line_5.dat" and it will be located where the project wassaved.

g.1) Data File for Circular Shape Holes Line

NAME holes line 1

SCALE_FACTOR 1

SHAPE CIRCULAR

NI_BEGIN NIHole

NAME hole 1


AutoGrid5™ 11-21

POINT 0.2721 0.014104 0.0718381

AXIS 0.0563309 -0.996603 -0.0600856

DIAMETER 0.0011

NI_END NIHole

...

g.2) Data File for Rectangular Shape Holes Line

NAME holes line 2

SCALE_FACTOR 1

SHAPE SQUARE

NI_BEGIN NIHole

NAME hole 1

POINT 0.272459 0.00174071 0.0691802

AXIS -0.00578617 0.90566 0.423965

SIZE1 0.0011

SIZE2 0.0011

ORIENTATION_ANGLE 0

NI_END NIHole

…

g.3) Data File for Oval Shape Holes Line

NAME holes line 3

SCALE_FACTOR 1

SHAPE OVAL

NI_BEGIN NIHole

NAME hole 1

POINT 0.272459 0.00174071 0.0691802

AXIS -0.00578617 0.90566 0.423965

SIZE1 0.0011

SIZE2 0.0011

ORIENTATION_ANGLE 0

NI_END NIHole

…

g.4) Data File for Trailing Edge Groove Holes Line

NAME holes line 4

SCALE_FACTOR 1

SHAPE GROOVE_AT_TRAILING_EDGE

SIDE LOWER_SIDE

NI_BEGIN NIHole

NAME hole 1

POINT 0.270542 0.0428518 0.112722


11-22 AutoGrid5™

AXIS 0 0 0

POINT2 0.271642 0.0428532 0.112722

NI_END NIHole

…

g.5) Data File for Trailing Edge Circular Holes File

NAME holes line 5

SCALE_FACTOR 1

SHAPE CIRCULAR_AT_TRAILING_EDGE

NI_BEGIN NIHole

NAME hole 1

POINT 0.2725 0 0.112722

AXIS 0 0 0

DIAMETER 0.0011

NI_END NIHole

...

g.6) Data File for 4-Sided Shape Holes Line

NAME holes line 6

SCALE_FACTOR 1

SHAPE QUADRILATERAL

NI_BEGIN NIHole

NAME hole 1

POINT 0.272459 0.00174071 0.0691802

AXIS -0.00578617 0.90566 0.423965

POINTS -0.0011 -0.0011 0.0011 -0.0011 -0.0011 0.0011 0.0011 0.0011

ORIENTATION_ANGLE 0

NI_END

...

� The SCALE_FACTOR is optional. It is used to convert the data if it is not specified inmeter (i.e.: data in millimeter needs to set the SCALE_FACTOR to 0.001).


AutoGrid5™ 11-23


In the Blade Cooling Holes Line Definition, the Mesh Control thumbnail gives access to theparameters controlling the mesh topology around and inside the holes.

a) Grid Points Distribution

The grid point distribution panel allows the user to change the grid point number (by left-clickingon the it when highlighted in red) around the holes. According to the shape of the holes, the param-eters to define can be different.

� When defining a hole line in the end walls, additional parameters Upper/Lower clus-tering relaxation allow to relax the clustering on the top and bottom. When the value isset to 0 the clustering is fully relaxed otherwise the value entered by the user is used toset up a cluster at both ends distribution.


11-24 AutoGrid5™

b) Optimization Control

The number of smoothing steps around (Optimization Steps Around Hole) and inside (Optimiza-tion Steps Inside Holes) the holes can be modified. The type of smoothing can also be chosen withor without skewness control (Skewness Control Around/Inside Holes option).

� For the trailing edge grooves, only the smoothing steps inside the holes can be control-led.


AutoGrid5™ 11-25

c) Wake Control

The size of the mesh upstream and downstream the holes (Upstream/Downstream NormalizedDistance) can be controlled by normalized parameters. These parameters allow the user to changethe downstream length and the upstream length of the area where the mesh around the holes will becreated.

d) Mesh Shape Control

When two lines of holes are close to each other and one of the holes line spanwise shape must drivethe shape of the mesh of the second holes line, the option Holes Line Mesh Shape Control can beapplied on the second holes according to the holes line spanwise shape configuration.

11-3.2.3 Global Control

By default, when lines of holes are defined, AutoGrid5™ will first divide the matrix block in span-wise direction near the hub and near the shroud to keep as much as possible of the end wall bound-ary layer of the matrix mesh. The indices of division can be controlled by the user in the thumbnailGlobal Control.

The tolerance used to compute the intersection of the holes with the matrix block can be modifiedby modifying the Holes Intersection Tolerance available in the Expert page.

Because the preview using Preview 3D button can be slightly different from the final computedlocation, the Preview Tube Mesh button is used to display the real location of the holes.


11-26 AutoGrid5™

11-3.3 Blade Holes Mesh Generation

Once the matrix and the holes definition are completed, the Generate Holes menu available whenright-clicking on the Main Blade in the configuration tree allows to start the holes mesh generationwithout regenerating the row mesh.

The option Generate Blades Cooling Holes available when pressing the Generate 3D button of thetop menu bar can also be activated to mesh the holes after the selected row mesh generation.

Right-click

Cooling - Basin Holes/Separator Cooling & Conjugate Heat Transfer Modules

AutoGrid5™ 11-27

11-3.4 Blade Holes Project Management

As explained at the beginning of the section 10-3, the blade hole(s) meshes are inserted into thematrix block of the default mesh computed by AutoGrid5™ (skin block around the blade). There-fore, before starting the blade holes mesh generation, the default mesh inside the row must havebeen computed using Generate 3D button. This mesh is usually called the matrix mesh. It isstrongly advised to save and store this mesh on disk (File/Save Project As) before starting theblade holes generation. Once the matrix mesh has been generated and saved into a matrix project,the blades holes definition can be modified and saved using the menu File/Save Template.

Using this method, the template on disk contains the new holes definition and the matrix mesh.Each time the user wants to modify the holes definition and regenerate a new mesh, the matrixproject can be reloaded, the holes definition changed and the holes mesh generation started withoutregenerating the default row mesh (matrix).

� By default, the mesh (matrix) generated inside the solid body of the blade contains twoblocks (butterfly topology at the trailing edge - section 11-2.1.5.a). Due to the mesh gen-eration method, the matrix mesh is different if trailing edge holes or grooves must begenerated. The butterfly topology is degenerated into a single O-block. Therefore, if anew line of holes of these types is added after having generated the matrix, the systemwill prompt the user to regenerate the matrix before starting the holes line. The samebehaviour can be observed if the matrix has been generated with trailing edge holes orgrooves defined that are removed afterwards.

11-4 Cooling - Basin Holes/SeparatorWhen the blade configuration contains a cooling wall definition, a basin and a basin wall, holes intothe basin wall and a solid separator into the basin can be defined within AutoGrid5™.

Cooling & Conjugate Heat Transfer Modules Cooling - Basin Holes/Separator

11-28 AutoGrid5™

11-4.1 Basin Holes/Separator Methodology

The blade to blade mesh into the cooling wall area is composed by two blocks (butterfly topology -section 10-2.1.4.a). After defining the basin holes and separator, AutoGrid5™ will compute thelocation of the basin holes and the separator into this mesh and than replace the butterfly topologyby a new complex topology capturing the defined holes and separator. The connection between thecooling wall area and the solid body of the blade becomes full non matching.

This process is repeated on each layer from the bottom to the top of the domain. It assumes thesame block topology and matching connections between the cooling channel, the basin wall, thebasin and the shroud gap area.

separator

basin holes

separator

basin holes


AutoGrid5™ 11-29

11-4.2 Basin Holes Properties

The Add Radial Holes menu available when right-clicking on Solid Body adds a new hole entity inthe configuration tree.

The Properties menu available when right-clicking on holes 1 opens a dialog box to control thegeometry and the mesh of the selected hole.

� When selecting a solid body configuration with penny, the same dialog box is used todefine the penny. However, a rotation around the penny can be specified.

Right-click

Right-click


11-30 AutoGrid5™


a) Parametric Mode

When the option Use Parametric Definition is active, a parametric location is used to define thebasin holes. Two parameters fully define the location of the holes:

• Location (% of chord): this parameter defines the hole center on the chord by giving a percent-age of the chord length of the cooling wall definition ("A" in figure below).

• Location (% of width): once the hole center is located on the chord, a deviation normal to thechord can be defined. The amplitude of the deviation is given in % of cooling wall width ("B" infigure below).

The Diameter of the selected basin hole has to be specified.

b) XYZ Mode

When the option Use Parametric Definition is switch off, the holes geometry is defined in the Car-tesian space by an anchor point (Anchor) and an axis vector (Axis).

Once a new hole is defined using non-parametric definition, when pressing Generate B2B, the sys-tem indicates to the user two layer indices on which Generate B2B must be applied before launch-ing the 3D generation.

AB


AutoGrid5™ 11-31

The parametrization of the holes is done during these phases and it assumes that the axis given bythe user will be followed by the holes. Each time the user wants to modify the hole location (i.echanging the anchor and/or the axis), the same procedure must be performed.

The Diameter of the selected basin hole has to be specified.

The Preview and Hide buttons are used to perform a quick display of the 3D definition of the cylin-der used to define the holes. The 3D display is only available if the matrix block is available whenthe 3D mesh generation of the row has already been completed. Each modification of any hole linesparameter implies an automatic refresh of the display.

� Due to the stacking technique used to define the basin holes, the holes are always normalto the surface of the basin and are following the spanwise direction (J-direction) of theblade.

c) External Holes Definition File

The basin holes geometry can be defined using an external data file through the Init Radial HolesFrom File menu available when right-clicking on the Solid Body. A file chooser allows to select anexternal hole file. The file format used to define a basin hole is presented below.

The Export Radial Holes Geometry menu available when right-clicking on the Solid Body is usedto export the basin hole definition into an external file.

The data file format is the following:

SCALE_FACTOR 1000

NI_BEGIN cylinder

ORIGIN -0.00767000036430546 0.314414877301847 0.0786000028177822

AXIS 7.16351112721767e-14 -1 -2.54702617856629e-14

RADIUS 0.000250000011874398

NI_END cylinder

NI_BEGIN cylinder

ORIGIN -0.00781000037095512 0.314414877301847 0.0812700029446004


11-32 AutoGrid5™

AXIS 7.16351112721767e-14 -1 -5.09405235713257e-14

RADIUS 0.000250000011874376

NI_END cylinder

After the selection, the holes are automatically initialized in the configuration tree and the proce-dure described in the previous section must be followed to initialize the holes parametrization.


The mesh inside and around the holes can be controlled using the following parameters.

• Number of Point Along Radius: this parameter is used to modify the number of points in theboundary layer of the holes.

• Number of Point Along Sides: this parameter is used to modify the number of points aroundthe holes.


AutoGrid5™ 11-33

• Location Bnd Smoothing Steps: this parameter is used to smooth the limit of the blocks at theboundary with the solid body of a hole located between others holes/separator.

• Optimization Steps: this parameter is global for all the basin holes and controls the number of opti-mization steps used to optimise the mesh inside and around the holes.

• Streamwise Mesh Resolution: this parameter allows the user to increase the default number ofpoints in the streamwise direction. When set to 1, AutoGrid5™ computes automatically the numberof points in the streamwise direction for the blocks inserted between holes according to the externalgrid point distribution. This is not always sufficient to assume a correct expansion ratio.

11-4.3 Basin Separator Properties

The Add Separator menu available when right-clicking on Solid Body adds a new separator entity inthe configuration tree.

Streamwise Mesh Resolution set to 1 Streamwise Mesh Resolution set to 3

Cooling & Conjugate Heat Transfer Modules Cooling - End Wall Holes

11-34 AutoGrid5™

The Properties menu available when right-clicking on the separator 1 opens a dialog box to control thegeometry and the mesh of the selected separator.

The separator location (Location (% chord)) is defined by giving a percentage of the cooling wall chordarc length (indicated as "A" in the figure of section 11-4.2.1.a). The width of the separator is given inabsolute value (Width) and the number of points in the streamwise direction (Number of Point AlongStream) controls the mesh into the separator.

11-4.4 Basin Holes/Separator Mesh Generation

The mesh inside the cooling channel is automatically computed during the stacking process of the row.The full non matching connections are automatically created between the solid body and the basin, basinwall, cooling channel and the shroud gap area.

� No control is given on the streamwise number of points between the holes. AutoGrid5™ tries tokeep the same clustering as in the solid body to avoid too high difference of grid points alongthe full non matching connections.

11-5 Cooling - End Wall HolesIn the section 11-2.2, the grid generation of the end walls solid body is presented. In addition, lines ofholes located on the end walls can be defined and meshed within AutoGrid5™.

Right-click

end walls holes

Cooling - End Wall Holes Cooling & Conjugate Heat Transfer Modules

AutoGrid5™ 11-35

11-5.1 End Wall Holes Methodology

The method is similar to the grid generation of blade line holes describes in the section 11-3. As forthe blades line holes, the grid generation of the line of holes on the end walls is based on the inser-tion of the mesh around the holes into a matrix mesh. This matrix mesh is created automatically byAutoGrid5™. It consists in two H blocks used to mesh the solid body of the end wall and the con-nected fluid boundary layer.

The Properties menu available when right-clicking on Hub Wall or Shroud Wall opens a dialog boxto control the mesh generation of the matrix. The blade to blade visualization of the H block can becontrolled using the menu View B2B Mesh and Hide B2B Mesh.

The user can control the smoothing steps (Hole Matrix Optimization Steps) and the multigridacceleration (Hole Matrix Multigrid Optimization) to optimize the H block of the matrix. Thenumber of layers on which the end walls holes block will be extended into the fluid boundary layeris controlled by the Connected Layers parameters.

11-5.2 End Wall Holes Properties

The Add Holes line menu available when right-clicking on Hub Wall or Shroud Wall adds a newholes line entity in the configuration tree.

Cooling & Conjugate Heat Transfer Modules Cooling - End Wall Holes

11-36 AutoGrid5™

The holes geometry and mesh controls are similar to the ones presented for the blade holes in section11-3.2.

� A quick display of the end walls holes is also available in the blade to blade view but itappears only if the active blade to blade layer corresponds to the hub or the shroud.

� Due to the matrix concept which is using a H block, the grid quality in the hub wall bound-ary layer can be downgraded compared to the default topology.

� Due to the location of the matrix, it is not obvious to define holes in front of the leadingedge.

11-5.3 ·End Wall Holes Mesh Generation

Once the matrix, the end walls and the holes definition are completed, the Generate Holes menu,available when right-clicking on Hub Wall or Shroud Wall in the configuration tree, allows to start theholes mesh generation without regenerating the row mesh.

Right-click

Right-click

Cooling - Pin Fins Cooling & Conjugate Heat Transfer Modules

AutoGrid5™ 11-37

The options Generate End Wall and Generate End Wall Cooling Holes available when pressingthe Generate 3D button of the top menu bar can also be activated to mesh the holes after theselected row mesh generation.

11-6 Cooling - Pin FinsThe pin fins are usually located in the cooling channel of the blade and used to promote the turbu-lence and to exchange heat. These entities can be defined and meshed within AutoGrid5™.

coolingchannel

Cooling & Conjugate Heat Transfer Modules Cooling - Pin Fins

11-38 AutoGrid5™

11-6.1 Pin Fins Properties

The Add Pin Fins Channel menu available when right-clicking on Cooling Channels adds a pinfins channel entity in the configuration tree.

11-6.1.1 Pin Fins Box Definition

A pin fins channel entity is used to mesh solid pin fins lines into a box (cooling channel) defined bythe user. The box is a IGG™ block created manually or imported from an external block data file.The block orientation I and J must correspond respectively to the pin fins axis and the pin fine linedirection. This block will be used in a similar way as the matrix mesh used for the blade and endwalls holes.

a) From IGG™ Edit Mode

The Edit menu, available when right-clicking on pin fins channel 1 in the configuration tree, allowsto start the edition mode. Under this mode, the box will be created using IGG™ functionalities.When closing this edition mode (Close Edition Mode button), the first block created will be consid-ered as the new pin fins box.

b) From External Block File

The Define from Box File menu, available when right-clicking on pin fins channel 1 in the config-uration tree, opens a file chooser used to select an external IGG™ block coordinate file. Once thefile selected, a dialog box prompts the user to specify how much points must be used in the I, J andK directions to create the box using the geometry of the imported block file.

11-6.1.2 Pin Fins Lines Definition

The Add Pin Fins Line menu, available when right-clicking on pin fins channel 1 in the configura-tion tree, is used to add a new pin fins line into the configuration tree.

Right-clickRight-click

Cooling - Pin Fins Cooling & Conjugate Heat Transfer Modules

AutoGrid5™ 11-39

The pin fins lines management is similar to the blade holes management presented in the previous sections.The Properties menu available when right-clicking on pin fins 1 opens a dialog box to control the geome-try and the mesh of the selected hole.

The holes geometry and mesh controls are similar to the ones presented for the blade holes in section 11-3.2.

In addition to the holes control parameters, the pin fins can have a fillet defined in the Dimension panel.The Minimum Fillet Angle avoids a zero skewness angle of the cell connected with the boundary of thebox.

� The grid points distribution can be imposed for the entire pin fins line but not for only one pinfin of the line in order to ensure matching connection.

Right-click

Right-click

Cooling & Conjugate Heat Transfer Modules Cooling - Pin Fins

11-40 AutoGrid5™

11-6.2 Pin Fins Mesh Generation

The mesh inside the cooling channel including the pin fins is automatically computed when select-ing the Generate Pin Fins menu when right-clicking on pin fins channel 1 in the configuration tree.

� When generating the pin fins, the cell width defined in the Mesh Control subpad of thequick access pad is taken into account. Using the default cell width of 1e-5 may lead toproblems if the geometry is defined in mm.

The final mesh contains solid blocks defining the pins fins and fluid blocks around the pin finsdefining the fluid area of the box (cooling channel). The mesh includes six full non matching con-nections with only left patches defined. These connections are useful to define the link between thepin fins boxes and the surrounding areas such as the blade solid body.

In addition the Mesh properties menu when right-clicking on pin fins channel 1 in the configura-tion tree, opens a dialog box providing to the user easy ways to:

• Revert the fluid and solid block.

• Define inlet boundaries at the left or right side of the pin fins.

• Preserved mesh boundary on the left and right side of the pin fins.

Right-click

Cooling - Ribs Cooling & Conjugate Heat Transfer Modules

AutoGrid5™ 11-41

11-7 Cooling - RibsThe ribs are usually located in the cooling channel of the blade and used to promote the turbulenceand to exchange heat. These entities can be defined and meshed within AutoGrid5™.

11-7.1 Ribs Properties

The Add Ribs Channel menu available when right-clicking on Cooling Channels adds a ribs chan-nel entity in the configuration tree.

11-7.1.1 Ribs Box Definition

A ribs channel entity is used to mesh solid ribs lines into a box (cooling channel) defined by theuser. The box is a IGG™ block created manually. The block should have a special orientation:

• the I direction from front to back (front side being the side where the rib is located),

• the J direction from hub to shroud,

• the K direction from left to right (left side being at the left when looking in the direction front->back).

This block will be used in a similar way as the matrix mesh used for the blade and end walls holes.

coolingchannel

Right-click

Right-click

Cooling & Conjugate Heat Transfer Modules Cooling - Ribs

11-42 AutoGrid5™

a) From IGG™ Edit Mode

The Edit menu, available when right-clicking on ribs channel 1 in the configuration tree, allows tostart the edition mode. Under this mode, the box can be created using IGG™ functionalities. Whenclosing this edition mode (Close Edition Mode button), the first block created will be considered asthe new ribs box.

b) From 3D View

After selecting the 3D view in AutoGrid5™, a IGG™ mesh (".igg" file) can be imported in the 3Dview (File/Import/IGG Project). The desired block representing the cooling channel needs to beactivated by left-clicking on it in the 3D view. The Define Box from Active Block menu, availablewhen right-clicking on ribs channel 1 in the configuration tree, allows to link the active block to theribs channel. After defining the box, the template has to be saved (File/Save Template) and reo-pened (File/Open Project) otherwise the blocks of the imported IGG™ mesh will stay in the 3Dview and conflict with new created blocks in AutoGrid5™.

11-7.1.2 Ribs Geometry Control

The Define Geometry menu, available when right-clicking on ribs channel 1 in the configurationtree, is used to control the geometry and the mesh of the ribs.

A rib can be seen as a "bar" located in the cooling channel (box). The ribs can be located on only oneside of the cooling channel box (called the "front" side, the opposite being the "back" side).

The basic (mandatory) geometry is defined by:

• a basic plane (plane origin and normal direction) representing the lower side (Define basic planesbutton),

• a height (Height) representing the upper side (basic plane shifted by height along its normal),

• a thickness (Thickness) representing the back side (front side offset of the thickness).

In addition, optional rib geometry extensions are possible:

• a left extension (bar extension on the left side with the same height and thickness as the main bar)defined by a plane (Define left extensions button).


AutoGrid5™ 11-43

• a right extension (bar extension on the right side with the same height and thickness as the mainbar) defined by a plane (Define right extensions button).

• separation(s) (an interruption in the main bar, through which the fluid will pass) defined by twoplanes (defining the start and the end of the bar cut) (Add separations button).

• a Full Channel option allowing to completely fill the channel with ribs, meaning that no fluidcan pass perpendicularly to the ribs.

The figure below is illustrating the options in a section of a rib channel.

As mentioned above, the ribs geometry is composed by basic planes defined by an external ".dat"file illustrated below:

SCALE_FACTOR 1000

REVERSE_NORMAL 1

PLANE -0.0001 0.2554 0.0992 -6.1422e-15 -0.866 0.5

PLANE -0.0007 0.2579 0.0984 -3.1258e-14 -0.866 0.4999

PLANE 0.0002 0.2611 0.0988 -7.8737e-15 -0.866 0.4999

...

The first line (optional) allows to impose a scaling factor to the plane coordinates (useful when theplanes are not defined in the scale of the cooling channel).

The second line (optional) allows to inverse the plane normal orientation. The plane normal shouldbe oriented from the lower to the upper ribs channel side.

The following lines beginning by the keyword "PLANE" identify the ribs (the number of ribs willcorrespond to the number of "PLANE" lines). The keyword "PLANE" is followed by the plane ori-gin and normal coordinates.

The file format for the left extension, right extension and separation planes is similar to the one pre-sented above. For the separation definition, the number of planes should be twice the number of ribsas a rib separation is defined by a starting and ending plane.

When separations are positioned in staggered rows of successive ribs, the Alternate separationsbutton improves the mesh quality. This option will insert artificially in a rib the separation of theprevious one and in the previous rib the separation of the current one. As these artificial separationsare not real, they will be meshed with solid blocks.

Left Extension

Right Extension

Main Bar Separation 1 Separation 2


11-44 AutoGrid5™

11-7.1.3 Ribs Mesh Control

The Define Geometry menu, available when right-clicking on ribs channel 1 in the configurationtree, is used to control the geometry and the mesh of the ribs.

The mesh will be fully matching in the complete ribs channel. That means that increasing thenumber of points somewhere will be propagated all over the domain through matching block con-nections.

The mesh parameters that can be controlled are:

• the number of points in the I direction (from front to back) - Number of pts I,

• the number of points in the J direction for a rib itself (from bottom to top) - Number of pts J,

• the number of intermediate points in J direction between 2 ribs (from bottom to top) - Numberof Inter pts,

• the number of points in the K direction (from left to right) - Number of pts K,

• the clustering by defining the Cell width and the number of constant cells (Number of cstcells).

These values are constant for all the ribs in the channel. The figure below is illustrating the abovecontrols in a section of a rib channel.


AutoGrid5™ 11-45

11-7.2 Ribs Mesh Generation

The mesh inside the cooling channel including the ribs is automatically computed when selectingthe Generate menu when right-clicking on ribs channel 1 in the configuration tree.

� When generating the ribs, the cell width defined in the Mesh Control subpad of thequick access pad is taken into account. Using the default cell width of 1e-5 may lead toproblems if the geometry is defined in mm.

The final mesh contains solid blocks defining the ribs and fluid blocks around the ribs defining thefluid area of the box (cooling channel). The mesh includes six full non matching connections withonly left patches defined. These connections are useful to define the link between the ribs boxes andthe surrounding areas such as the blade solid body.


11-46 AutoGrid5™

AutoGrid5™ 12-1

CHAPTER 12: Python Script

12-1 OverviewScripts are available in AutoGrid5™, like in IGG™, through the object-oriented Python language.For a more complete description of python language and generic commands, see the IGG™ man-ual.

Specific commands are dedicated to AutoGrid5™ and are described here after. More details on theavailable python commands are available in the file "AUTOGRID.py" provided in the NUMECAdistribution after installation (i.e. under Windows, the file is available in "~/_python/_autogrid/").

12-2 Running a Script FileScript files can be run from the command line or directly through a python interpreter.

• From the command line, a script can be run by launching AutoGrid5™ with the -script option.For example: igg -autogrid5 -script my_script.py. AutoGrid5™ will execute the script and thenopen the graphical user interface.When running a script from the command line, it is possible to execute a process in batch mode,avoiding to open the GUI. To do so, the -batch option should be used: igg -autogrid5 -batch -script my_script.py.

� IGG™ scripts and AutoGrid5™ scripts are not interchangeable.

Python Script Commands Description

12-2 AutoGrid5™

12-3 Commands DescriptionCommands are classified by categories and by classes. Several classes are defined in AutoGrid5™ togroup functions related to generic entities: Row, Blade, Gap, RSInterface, StagnationPoint, Techno-logicalEffect,...

� Note for Windows users:

The specification of path names when using commands requiring file names as input must beperformed using a UNIX style coding. This practically means that ‘/’ should be used as sepa-rator between directories instead of ‘\’ and path names should be written between quotes:"/usr/people/test.trb".

12-3.1 Configuration Commands

• a5_open_project (trb_file_name)

• a5_open_template(trb_file_name)

• a5_save_template(trb_file_name)

• a5_save_project(trb_file_name)

• a5_save_mesh(mesh_file_name)

• a5_save_mesh_V61(mesh_file_name)




• a5_save_and_merge_project_mesh()

• a5_init_html_report_file()

• a5_export_fluid_mesh()

• a5_new_project(bypass)Creates a new project from scratch. Bypass is a boolean value specifying if the project shouldcontain a bypass.

• a5_set_cascade_project(cascade)

• a5_get_cascade_project()

• a5_init_new_project_from_a_geomTurbo_file(geomTurbo_file_name,cascademode=0)

• a5_start_3d_generation()Generates 3D mesh of all selected entities.

• a5_control_and_start_3d_generation(holes,endwall,endwallholes)

• a5_generate_basin_mesh()

• a5_reset_default_topology()Resets default topology of all selected rows.

• a5_generate_b2b()Generates B2B mesh of all selected rows at the active control layer.

• a5_generate_flow_paths()Generates flow paths of all selected rows.

• set_active_control_layer_index(value)Set the active layer of all rows. Value should be between 0 and 100.

Commands Description Python Script

AutoGrid5™ 12-3

• calc_row_2D_mesh_quality(type, row_list, range_start, range_end, range_number, show=0,show_marker=0, show_cells=1)

Computes the mesh quality in the blade to blade space. Returns a list giving a spreadnumber of cells as in a bar chart.

• calc_row_pointer_2D_mesh_quality(type,row_pointer_list,range_start,range_end,range_number,show=0,show_marker=0,show_cells=1)

• calc_row_2D_mesh_quality_inter_block(type, row_list, range_start, range_end,range_number, show=0, show_marker=0, show_cells=1)

Computes the mesh quality at block boundaries in the blade to blade space. Returns a listgiving a spread number of cells as in a bar chart.

• delete_row_topology(topology_name)Deletes from the library the topology identified by its name.

• delete_b2b_topology(topology_name)Deletes from the library the topology identified by its name.

• a5_get_row_number()Returns the number of rows of the machine.

• a5_row_at_the_end_of_the_channel()Adds a row at the end of the machine.

• a5_set_support_curve_control_pts(value)

• a5_get_support_curve_control_pts()

• a5_row_on_the_nozzle_of_the_engine()

• a5_row_in_the_bypass()

• a5_row_at_the_outlet_of_the_compressor()

• row(B):# indices from 1Returns an object of class Row.B can be either a row name or a row index.

• select_all_rows()

• unselect_all_rows()

• select_all()

• unselect_all()

• z_cst_line(name)Gives access to meridional control lines. Returns an object of class RSInterface.

• delete_z_cst_line(RSInterface)

• compute_default_z_cst_line(point, channel_curve_type)z_cst_line = compute_default_z_cst_line(Point(8.2,19,0), 0): this command is creating anew control line on the hub at a location close to the point (Z=8.2,R=19,theta=0).

• compute_default_relative_z_cst_line(row_ref,row_location,relative_location)Row_locaion should be "0" if control line between inlet and leading edge of the row(row_ref), "1" if between its leading edge and its trailing edge, and "2" if between its trail-ing edge and outlet or rotor/stator.

• a5_add_B2B_cut()

• set_by_pass_configuration_topologyType(value)Value should be "0" for H-Topology or "1" for C-topology.

• get_by_pass_configuration_topologyType()

• set_by_pass_configuration_Bnd_layer_Width(value)


12-4 AutoGrid5™

• get_by_pass_configuration_Bnd_layer_Width()

• set_by_pass_configuration_nozzle_index(value)

• get_by_pass_configuration_nozzle_index()

• set_by_pass_configuration_clustering(value)

• get_by_pass_configuration_clustering()

• set_by_pass_configuration_numberOfSpanwisePoints(value)

• get_by_pass_configuration_numberOfSpanwisePoints()

• set_by_pass_configuration_numberOfStreamwisePoints(value)

• get_by_pass_configuration_numberOfStreamwisePoints()

• set_by_pass_configuration_relativeControlDistance(value)

• get_by_pass_configuration_relativeControlDistance()

• set_by_pass_configuration_nup(value)

• get_by_pass_configuration_nup()

• set_by_pass_configuration_ndown(value)

• get_by_pass_configuration_ndown()

12-3.2 Geometry Import Commands

• a5_set_import_geometry_rotation_axis(orig, stream_direction,span_direction)Defines the rotation axis for CAD import.

• a5_import_geometry_file(file_name)Imports a geometry file, either CATIA, Parasolid™, .dat, .geom, .geomTurbo 4 & 5 orIGES formats.

• a5_import_and_replace_geometry_file(file_name)

• a5_get_import_geometry_repository()

• a5_clean_import_geometry()Deletes all the geometry entities already loaded.

• a5_link_to_hub(curve_names)Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• a5_link_to_hub_surface(row,surface_names) Surface_names should be a list, even if it is composed of only 1 element (use [ ]).

• a5_link_to_shroud(curve_names)Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• a5_link_to_shroud_surface(row,surface_names) Surface_names should be a list, even if it is composed of only 1 element (use [ ]).

• a5_link_to_tip_gap_surface(row,surface_names) Surface_names should be a list, even if it is composed of only 1 element (use [ ]).

• a5_link_to_nozzle(curve_names)Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• a5_link_to_basic_curve(curve_names)Imports the curves specified by their names in the meridional space by creating basiccurves.Curve_names should be a list, even if it is composed of only 1 element (use [ ]).


AutoGrid5™ 12-5

• a5_link_to_basic_curve

• a5_define_hub(point_list)

• a5_define_shroud(point_list)

• a5_define_nozzle(point_list)

• basic_curve(name)

12-3.3 Viewing Commands

• a5_treetclUpdate() is used to update the AutoGrid5™ tree on the top left of the screen.

• a5_tclUpdate() is used to update the remaining part of the AutoGrid5™ GUI.

• hoops_Update() is used to update all the views of the AutoGrid5™ GUI.

• a5_update_dialog_box() is used to update the opened dialog boxes

• a5_waitLeftClick() is used to stop the execution of the script until user left click

• a5_switch_to_wizard_mode()

• a5_switch_to_expert_mode()

• a5_focus_ZR_view()

• a5_focus_B2B_view()

• a5_focus_3D_view()

• a5_full_view()Set in full view mode the focused view.

• a5_multi_view()

• a5_focus_b2b_view_on_active_rows()Set the focus on the B2B view and fit the view around the selected rows.

• a5_view_b2b_repetition_number(number)

• a5_view_b2b_repetition()

• a5_hide_b2b_repetition()

• a5_print_b2b_png(file_name)

• a5_print_3D_png(file_name)

• a5_print_ZR_png(file_name)

• a5_enable_full_display_smoothing_mode()Updates the interface after each B2B smoothing step. Only working with default topology.

• a5_disable_full_display_smoothing_mode()

• a5_enable_full_display_quality_mode(type)Updates the interface after each B2B smoothing step and computes quality in B2B viewaccording to type criterion.

• a5_disable_full_display_quality_mode()

• a5_view_3d_mesh(coarseLevel,pointOfView,zoom,grid,row_list)

• a5_remove_Cooling_Wall_B2B_Rep(blade)

• zoomFromAt(centerx1,centery1,centerz1,centerx2,centery2,centerz2,zoom1,zoomstep,nstep)

• a5_view_3d_mesh_default()

• a5_view_3d_mesh_fixed()


12-6 AutoGrid5™

• a5_view_3d_mesh_fixed_repet()

• a5_hide_3d_mesh()

• a5_toggle_b2b_mesh()

• a5_toggle_b2b_grid_point()

• a5_toggle_b2b_edges()

• a5_merge_fnmb(name1,name2,sens)

12-3.4 NIConfigurationEntities Class Commands

• select()

• unselect()

• meshConfigurationDomain()

• select_configuration()

• unselect_configuration()

• parent()

12-3.5 RowWizard Class Commands

• initialize(machine_type,row_type,rotationSpeed,periodicity)Machine_type should be between 1 and 9:

1: wind turbine (more info in WindTurbine Class)2: axial turbine3: Francis turbine4: Kaplan turbine5: inducer6: axial compressor7: centrifugal impeller8: centrifugal diffuser9: return channel

Row_type : 0 for stator and 1 for rotor

• copy()

• paste()

• generate()

• set_grid_level(value)

• get_grid_level()

• set_flow_path_number(value)

• get_flow_path_number()

• set_full_matching_topology(value)

• get_full_matching_topology()

• set_row_cell_width_at_wall(value)

• get_row_cell_width_at_wall()

• hub_gap_is_asked(value)

• is_hub_gap_asked()

• tip_gap_is_asked(value)


AutoGrid5™ 12-7

• is_tip_gap_asked()

• hub_fillet_is_asked(value)

• is_hub_fillet_asked()

• tip_fillet_is_asked(value)

• is_tip_fillet_asked()

• set_hub_gap_width_at_leading_edge(value)

• get_hub_gap_width_at_leading_edge()

• set_hub_gap_width_at_trailing_edge(value)

• get_hub_gap_width_at_trailing_edge()

• set_tip_gap_width_at_leading_edge(value)

• get_tip_gap_width_at_leading_edge()

• set_tip_gap_width_at_trailing_edge(value)

• get_tip_gap_width_at_trailing_edge()

• increaseNpts()

• decreaseNpts()

12-3.6 WindTurbine Class Commands

• select()

• delete()

• initialize(tipRmax,hubRmin,Zmin,Zmax,RFarField,radialPtsNr,cstCellsNr)tipRmax : relative shroud distance to the real tip of the blade (default 1)hubRmin : relative hub distance to the real hub of the blade (default 0)Zmin : relative inlet length (in blade height unit) (default -4)Zmax : relative outlet length (in blade height unit) (default 10)RFarField : relative far field expansion height (in blade height unit) (default 5)radialPtsNr : number of points in far field expansion (default 33)cstCellsNr : % of constant cell number in far field expansion (default 33)

• generate()

• set_tip_cut_relative_value(value)

• get_tip_cut_relative_value()

• set_hub_cut_relative_value(value)

• get_hub_cut_relative_value()

• set_expansion_cst_cell_percentage_number(value)

• get_expansion_cst_cell_percentage_number()

• set_expansion_number_of_layer(value)

• get_expansion_number_of_layer()

• set_expansion_height(value)

• get_expansion_height()

• set_inlet_width(value)

• get_inlet_width()

• set_outlet_width(value)


12-8 AutoGrid5™

• get_outlet_width()

• set_number_of_layer(value)

• get_number_of_layer()

• set_cst_cell_percentage_number(value)

• get_cst_cell_percentage_number()

• increaseNpts()

• decreaseNpts()

12-3.7 B2B Cut Class Commands

• delete()

• select()

• set_name(name)

• get_name()

• create()

• set_width(value)

• get_width()

• set_location(value)

• get_location()

• b2bCut(B):# indices from 1

12-3.8 Row Class Commands

• delete()

• block_list()

• setGraphicsRepetition(value)

• setDefaultGraphicsRepetition()

• get_index()

• select()

• unselect()

• load_geometry(geomTurbo_file_name)The file specified should have the geomTurbo format 4 or 5. Only the row geometry isreplaced and not the hub and/or shroud.

• zoom_at_inlet(level,location)Location should be between -1 and 1.

• zoom_at_outlet(level,location)Location should be between -1 and 1.

• zoom_at_inlet_up(level)

• zoom_at_outlet_up(level)

• zoom_at_inlet_down(level)

• zoom_at_outlet_down(level)


AutoGrid5™ 12-9

12-3.8.1 Topology Management

• load_topology(file_name)

• save_topology(file_name)

• copy_topology()

• paste_topology()

• save_b2b_topology(file_name)

• load_b2b_topology(file_name)

• wind_turbine_wizard()

• row_wizard()

12-3.8.2 Row Boundaries Access

• inlet()Returns an object of class RSInterface.

• outlet()Returns an object of class RSInterface.

• outlet2()Returns an object of class RSInterface.

12-3.8.3 Row Technological Effects 3D Access

• num_effect3D()

• effect3D(i)

• new_effect3D()Returns an object of class TechnologicalEffect3D.

12-3.8.4 Row Blades Properties

• num_blades()

• blade(i)

• add_blade()

• add_hub_gap()Add a gap at hub to all row blades.

• add_shroud_gap()Add a gap at shroud to all row blades.

• add_hub_fillet()

• add_shroud_fillet()

12-3.8.5 Row Properties

• set_name(name)

• get_name()

• set_clustering(value)

• get_clustering()

• set_upstream_block_relaxation(a)

• get_upstream_block_relaxation()


12-10 AutoGrid5™

• set_downstream_block_relaxation(a)

• get_downstream_block_relaxation()

• set_row_interpolation_spacing(value)Value should be between 0 and 100.

• get_row_interpolation_spacing()

• set_coarse_grid_level(level, target=250000)Level specifies the grid level desired; 1 for coarse, 2 for medium, 3 for fine and 4 for userdefined.Target is an optional argument only useful when level==4 and represents the desirednumber of points.

• get_coarse_grid_level()

• get_coarse_grid_level_target()

• set_streamwise_weight(inlet, outlet, blade)

• get_streamwise_weight_inlet()

• get_streamwise_weight_blade()

• get_streamwise_weight_outlet()

• set_periodicity(n)

• get_periodicity()

• set_number_of_periodicity_geometry(n)

• get_number_of_periodicity_geometry()

• set_rotation_speed(rotation_speed)

• get_rotation_speed()

• enable_low_memory_usage()

• disable_low_memory_usage()

• get_low_memory_usage()

• enable_full_mesh_generation()

• disable_full_mesh_generation()

• get_full_mesh_generation()

• is_a_tandem_row()

• is_a_tandem_row_with_next()

• is_a_tandem_row_with_previous()

• is_not_a_tandem_row()

• get_is_a_tandem_row()

• is_a_rotor()

• is_a_stator()

• is_a_inducer()

• is_a_pump()

• is_a_impeller()

• is_a_diffuser()

• is_a_return_channel()

• get_row_type()


AutoGrid5™ 12-11

• is_axial()

• is_centrifugal()

• get_row_orientation()

12-3.8.6 Row Hub/Shroud Non-Axisymmetric

• set_non_axisymmetric_hub()

• get_non_axisymmetric_hub()

• unset_non_axisymmetric_hub()

• set_non_axisymmetric_hub_repair_damage()

• get_non_axisymmetric_hub_repair_damage()

• unset_non_axisymmetric_hub_repair_damage()

• set_non_axisymmetric_hub_projection_type_face_normal()

• get_non_axisymmetric_hub_projection_type_face_normal()

• set_non_axisymmetric_hub_projection_type_spanwise_grid_line()

• set_non_axisymmetric_hub_repetition(value)

• get_non_axisymmetric_hub_repetition()

• set_non_axisymmetric_shroud()

• get_non_axisymmetric_shroud()

• unset_non_axisymmetric_shroud()

• set_non_axisymmetric_shroud_repair_damage()

• get_non_axisymmetric_shroud_repair_damage()

• unset_non_axisymmetric_shroud_repair_damage()

• set_non_axisymmetric_shroud_projection_type_face_normal()

• get_non_axisymmetric_shroud_projection_type_face_normal()

• set_non_axisymmetric_shroud_projection_type_spanwise_grid_line()

• set_non_axisymmetric_shroud_repetition(value)

• get_non_axisymmetric_shroud_repetition()

12-3.8.7 Row Shroud Gap Non-Axisymmetric

• set_non_axisymmetric_tip_gap()

• get_non_axisymmetric_tip_gap()

• unset_non_axisymmetric_tip_gap()

• set_non_axisymmetric_tip_gap_repair_damage()

• get_non_axisymmetric_tip_gap_repair_damage()

• unset_non_axisymmetric_tip_gap_repair_damage()

• set_non_axisymmetric_tip_gap_repetition(value)

• get_non_axisymmetric_tip_gap_repetition()

12-3.8.8 Row Hub/Shroud Solid Mesh

• hub_end_wall()

• shroud_end_wall()


12-12 AutoGrid5™

• add_hub_end_wall()

• add_shroud_end_wall()

12-3.8.9 Flow Paths Control

• set_flow_path_control_hub_clustering(value)

• get_flow_path_control_hub_clustering()

• set_flow_path_control_shroud_clustering(value)

• get_flow_path_control_shroud_clustering()

• set_flow_path_control_cst_cells_number(value)

• get_flow_path_control_cst_cells_number()

• set_flow_path_control_control_point_number(value)

• get_flow_path_control_control_point_number()

• set_flow_path_control_intermediate_point_number(value)

• get_flow_path_control_intermediate_point_number()

• set_flow_path_control_smoothing_steps(value)

• get_flow_path_control_smoothing_steps()

• set_flow_path_control_hub_distribution_uniform()

• set_flow_path_control_hub_distribution_curvature()

• get_flow_path_control_hub_distribution()

• set_flow_path_control_shroud_distribution_same()

• set_flow_path_control_shroud_distribution_projection()

• set_flow_path_control_shroud_distribution_minimal_distance()

• get_flow_path_control_shroud_distribution()

• set_row_flow_path_number(n)n=1 for coarse, 2 for medium, 3 for fine and 4 for userdef. If n=4, target should be specified.

• get_row_flow_path_number()

• generate_flow_paths()

• generate_flow_paths2(check_quality)

12-3.8.10Optimization

• set_row_optimization_steps(number_of_steps)

• get_row_optimization_steps()

• set_row_optimization_steps_in_gap(number_of_steps)

• get_row_optimization_steps_in_gap()

• set_row_optimization_skewness_control(value)Value should be "yes", "no" or "medium".

• get_row_optimization_type()

• set_row_optimization_skewness_control_in_gap(value)Value should be "yes", "no" or "medium".

• get_row_optimization_type_in_gap()

• set_row_optimization_orthogonality_control(value)


AutoGrid5™ 12-13

Value should be between 0 and 1.

• get_row_optimization_orthogonality_control()

• set_row_optimization_orthogonality_control_in_gap(value)Value should be between 0 and 1.

• get_row_optimization_orthogonality_control_in_gap()

• set_row_optimization_wake_control(value)Value should be between 0 and 1.

• get_row_optimization_wake_control()

• set_row_bnd_optimization_steps(number_of_steps)

• get_row_bnd_optimization_steps()

• set_row_optimization_multigrid_control(value)Value should be "yes" or "no".

• get_row_optimization_multigrid_control()

• set_row_optimization_nmb_control(value)Value should be between 0 and 1.

• get_row_optimization_nmb_control()

• set_row_straight_bnd_control(value)Value should be "0" or "1".

• get_row_straight_bnd_control()

• set_row_multisplitter_bnd_control(value)Value should be "0" or "1".

• get_row_multisplitter_bnd_control()

12-3.9 Blade Class Commands

• select()

• delete()

• set_name(name)

• get_name()

• basin()

• add_basin()

• sheet()

• hub_gap()Returns an object of class Gap. If gap does not exist, creates it.

• shroud_gap()Returns an object of class Gap. If gap does not exist, creates it.

• add_hub_gap()Returns an object of class Gap.

• add_shroud_gap()Returns an object of class Gap.

• hub_fillet()Returns an object of class Fillet. If fillet does not exist, creates it.

• shroud_fillet()


12-14 AutoGrid5™

Returns an object of class Fillet. If fillet does not exist, creates it.

• add_hub_fillet()Returns an object of class Fillet.

• add_shroud_fillet()Returns an object of class Fillet.

• wizard_le_te()

• zoom_at_leading_edge(level)

• zoom_at_trailing_edge(level)

• leadingEdgeControl()Returns an object of class StagnationPoint.

• trailingEdgeControl()Returns an object of class StagnationPoint.

• load_geometry(name)

• export_geometry()

• export_geometry(flowpath,nsections,ninlet,nblade,noutlet,ncst,leadwidth,trailwidth,expor-tendwall)

• link_geometry(surface_names)Defines the geometry of the blade.Surface_names should be a list, even if it is composed of only 1 element (use [ ]).

• link_pressure(surface_names)

• link_suction(surface_names)

• link_to_leading_edge(curve_names)Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• link_to_trailing_edge(curve_names)Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• link_to_hub_gap(curve_names)Defines the geometry of the hub gap. The gap should already be created.Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• link_to_shroud_gap(curve_names)Defines the geometry of the shroud gap. The gap should already be created.Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• set_b2b_topology_type(value)Value should be either 0 for default topology, 1 for HOH or 2 for user defined topology.

• get_b2b_topology_type()

• copy_topology()


12-3.9.1 Blade Expansion & Rotation Parameters

• expand_at_hub(expansion_factor, extent_offset=0)

• expand_at_shroud(expansion_factor, extent_offset=0)

• apply_rotation(x,y,z,nx,ny,nz,angle)

12-3.9.2 Blunt & Sharp Blade Parameters

• set_blunt_treatment_at_leading_edge()


AutoGrid5™ 12-15

• unset_blunt_treatment_at_leading_edge()

• set_blunt_treatment_at_trailing_edge()

• unset_blunt_treatment_at_trailing_edge()

• set_sharp_treatment_at_leading_edge()

• unset_sharp_treatment_at_leading_edge()

• set_sharp_treatment_at_trailing_edge()

• unset_sharp_treatment_at_trailing_edge()

12-3.9.3 Default Topology Parameters

a) Topology Control

• set_b2b_default_topology_periodicity_type(value)Value should be either 0 for non matching periodicity or 1 for matching.

• get_b2b_default_topology_periodicity_type()

• set_b2b_default_topology_enable_high_staggered_optimization()

• set_b2b_default_topology_disable_high_staggered_optimization()

• get_b2b_default_topology_disable_high_staggered_optimization()

• set_b2b_default_topology_disable_high_staggered_detection()

• set_b2b_default_topology_enable_high_staggered_detection()

• get_b2b_default_topology_enable_high_staggered_detection()

• set_b2b_default_topology_normal_inlet_angle()

• set_b2b_default_topology_low_staggered_inlet_angle()

• set_b2b_default_topology_high_staggered_inlet_angle()

• get_b2b_default_topology_inlet_angle()

• set_b2b_default_topology_normal_outlet_angle()

• set_b2b_default_topology_low_staggered_outlet_angle()

• set_b2b_default_topology_high_staggered_outlet_angle()

• get_b2b_default_topology_outlet_angle()

• set_b2b_default_topology_throat_control(value)

• get_b2b_default_topology_throat_control()

• set_b2b_default_topology_throat_projection_type(value)

• get_b2b_default_topology_throat_projection_type()

• set_b2b_default_topology_throat_projection_inlet_relaxation()

• get_b2b_default_topology_throat_projection_inlet_relaxation()

• set_b2b_default_topology_throat_projection_outlet_relaxation()

• get_b2b_default_topology_throat_projection_outlet_relaxation()

b) Grid Points Control

• set_b2b_default_topology_grid_point_number_azimutal_inlet(value)

• get_b2b_default_topology_grid_point_number_azimutal_inlet()

• set_b2b_default_topology_grid_point_number_azimutal_outlet(value)


12-16 AutoGrid5™

• get_b2b_default_topology_grid_point_number_azimutal_outlet()

• set_b2b_default_topology_grid_point_number_azimutal_inlet_up(value)

• get_b2b_default_topology_grid_point_number_azimutal_inlet_up()

• set_b2b_default_topology_grid_point_number_azimutal_outlet_up(value)

• get_b2b_default_topology_grid_point_number_azimutal_outlet_up()

• set_b2b_default_topology_grid_point_number_azimutal_inlet_down(value)

• get_b2b_default_topology_grid_point_number_azimutal_inlet_down()

• set_b2b_default_topology_grid_point_number_azimutal_outlet_down(value)

• get_b2b_default_topology_grid_point_number_azimutal_outlet_down()

• set_b2b_default_topology_grid_point_number_streamwise_inlet(value)

• get_b2b_default_topology_grid_point_number_streamwise_inlet()

• set_b2b_default_topology_grid_point_number_streamwise_outlet(value)

• get_b2b_default_topology_grid_point_number_streamwise_outlet()

• set_b2b_default_topology_grid_point_number_streamwise_blade_upper_side(value)

• get_b2b_default_topology_grid_point_number_streamwise_blade_upper_side()

• set_b2b_default_topology_grid_point_number_streamwise_blade_lower_side(value)

• get_b2b_default_topology_grid_point_number_streamwise_blade_lower_side()

• set_b2b_default_topology_grid_point_number_in_boundary_layer(value)

• get_b2b_default_topology_grid_point_number_in_boundary_layer()

• set_b2b_default_topology_grid_point_number_in_boundary_layer_of_gaps(value)

• get_b2b_default_topology_grid_point_number_in_boundary_layer_of_gaps()

c) Mesh Control

• set_b2b_default_topology_cell_width_at_wall(value)

• get_b2b_default_topology_cell_width_at_wall()

• set_b2b_default_topology_cell_width_at_wall_at_hub(value)

• get_b2b_default_topology_cell_width_at_wall_at_hub()

• set_b2b_default_topology_cell_width_at_wall_at_shroud(value)

• get_b2b_default_topology_cell_width_at_wall_at_shroud()

• set_b2b_default_topology_bnd_layer_width(value)

• get_b2b_default_topology_bnd_layer_width()

• get_b2b_default_topology_cell_width_at_wall_interpolation()

• set_b2b_default_topology_cell_width_at_trailing_edge(value)

• set_b2b_default_topology_cell_width_at_leading_edge(value)

• set_b2b_default_topology_expansion_ratio_in_bnd_layer(value)

• get_b2b_default_topology_expansion_ratio_in_bnd_layer()

• set_b2b_default_topology_free_outlet_angle(value)

• get_b2b_default_topology_free_outlet_angle()

• set_b2b_default_topology_free_inlet_angle(value)

• get_b2b_default_topology_free_inlet_angle()


AutoGrid5™ 12-17

• set_b2b_default_topology_fix_outlet_angle(value)

• get_b2b_default_topology_fix_outlet_angle()

• set_b2b_default_topology_fix_inlet_angle(value)

• get_b2b_default_topology_fix_inlet_angle()

• set_b2b_default_topology_outlet_angle(value)

• get_b2b_default_topology_outlet_angle()

• set_b2b_default_topology_inlet_angle(value)

• get_b2b_default_topology_inlet_angle()

• set_b2b_default_topology_enable_wake_control()

• set_b2b_default_topology_disable_wake_control()

• get_b2b_default_topology_wake_control()

• set_b2b_default_topology_enable_wake_prolongation()

• set_b2b_default_topology_wake_control_deviation_angle(value)

• get_b2b_default_topology_wake_control_deviation_angle()

• set_b2b_default_topology_enable_leading_edge_zcstline()

• set_b2b_default_topology_disable_trailing_edge_zcstline()

d) Intersection Control

• set_b2b_default_topology_chord_control_points_number(value)

• get_b2b_default_topology_chord_control_points_number()

• set_b2b_default_topology_intersection_quality(value)Value should be either 0 for low quality or 1 for high quality.

• get_b2b_default_topology_intersection_quality()

• set_b2b_default_topology_intersection_law(value)Value should be 0 for curvature or 1 for uniform.

• get_b2b_default_topology_intersection_law()

• set_b2b_default_topology_intersection_control_point_number(value)Useful only if low quality intersection and intersection law set to uniform.

• get_b2b_default_topology_intersection_control_point_number()

• set_b2b_blade_reference_angle(value)

• get_b2b_blade_reference_angle()

12-3.9.4 HOH Topology Parameters

a) Topology Control

• set_b2b_hoh_topology_enable_inlet_extension()

• set_b2b_hoh_topology_disable_inlet_extension()

• get_b2b_hoh_topology_inlet_extension()

• set_b2b_hoh_topology_enable_outlet_extension()

• set_b2b_hoh_topology_disable_outlet_extension()

• get_b2b_hoh_topology_outlet_extension()


12-18 AutoGrid5™

• set_b2b_hoh_topology_inlet_I_extension_type()

• set_b2b_hoh_topology_inlet_H_extension_type()

• get_b2b_hoh_topology_inlet_H_extension_type()

• set_b2b_hoh_topology_outlet_I_extension_type()

• set_b2b_hoh_topology_outlet_H_extension_type()

• get_b2b_hoh_topology_outlet_H_extension_type()

• set_b2b_hoh_topology_inlet_extension_location(value)

• get_b2b_hoh_topology_inlet_extension_location()

• set_b2b_hoh_topology_outlet_extension_location(value)

• get_b2b_hoh_topology_outlet_extension_location()


• set_b2b_hoh_topology_inlet_extension_streamwise_npts(value)

• get_b2b_hoh_topology_inlet_extension_streamwise_npts()

• set_b2b_hoh_topology_outlet_extension_streamwise_npts(value)

• get_b2b_hoh_topology_outlet_extension_streamwise_npts()

• set_b2b_hoh_topology_npts_in_boundary_layer(value)

• get_b2b_hoh_topology_npts_in_boundary_layer()

• set_b2b_hoh_topology_npts_around_boundary_layer(value)

• get_b2b_hoh_topology_npts_around_boundary_layer()

• set_b2b_hoh_topology_suction_and_pressure_side_npts(value)

• get_b2b_hoh_topology_suction_and_pressure_side_npts()

• set_b2b_hoh_topology_H_inlet_azimuthal_npts_1(value)

• get_b2b_hoh_topology_H_inlet_azimuthal_npts_1()





• set_b2b_hoh_topology_I_inlet_azimuthal_npts(value)

• get_b2b_hoh_topology_I_inlet_azimuthal_npts()

• set_b2b_hoh_topology_H_outlet_azimuthal_npts_1(value)

• get_b2b_hoh_topology_H_outlet_azimuthal_npts_1()





• set_b2b_hoh_topology_I_outlet_azimuthal_npts(value)

• get_b2b_hoh_topology_I_outlet_azimuthal_npts()

• set_b2b_hoh_topology_I_inlet_periodic_npts(value)

• get_b2b_hoh_topology_I_inlet_periodic_npts()


AutoGrid5™ 12-19

• set_b2b_hoh_topology_I_outlet_periodic_npts(value)

• get_b2b_hoh_topology_I_outlet_periodic_npts()

• set_b2b_hoh_topology_gap_matching_with_main_channel()

• get_b2b_hoh_topology_gap_matching_with_main_channel()

• set_b2b_hoh_topology_gap_non_matching_with_main_channel()

• set_b2b_hoh_topology_gap_azimuthal_O_number_of_points(value)

• get_b2b_hoh_topology_gap_azimuthal_O_number_of_points()

• set_b2b_hoh_topology_gap_azimuthal_H_number_of_points(value)

• get_b2b_hoh_topology_gap_azimuthal_H_number_of_points()

• set_b2b_hoh_topology_gap_streamwise_H_number_of_points(value)

• get_b2b_hoh_topology_gap_streamwise_H_number_of_points()

• set_b2b_hoh_topology_gap_d1_d2_addition(value)

• get_b2b_hoh_topology_gap_d1_d2_addition()

• set_b2b_hoh_topology_gap_d1_d2_ratio(value)

• get_b2b_hoh_topology_gap_d1_d2_ratio()

• set_b2b_hoh_topology_gap_d3_d4_addition(value)

• get_b2b_hoh_topology_gap_d3_d4_addition()

• set_b2b_hoh_topology_gap_d3_d4_ratio(value)

• get_b2b_hoh_topology_gap_d3_d4_ratio()

c) Leading Edge Grid Points Distribution Control

• set_b2b_hoh_leading_edge_control_type_none()

• set_b2b_hoh_leading_edge_control_type_absolute_distance()

• set_b2b_hoh_leading_edge_control_type_relative_distance()

• set_b2b_hoh_leading_edge_control_type_cell_lenght()

• get_b2b_hoh_leading_edge_control_type()

• set_b2b_hoh_leading_edge_control_absolute_distance(value)

• get_b2b_hoh_leading_edge_control_absolute_distance()

• set_b2b_hoh_leading_edge_control_relative_distance(value)

• get_b2b_hoh_leading_edge_control_relative_distance()

• set_b2b_hoh_leading_edge_control_cell_lenght(value)

• get_b2b_hoh_leading_edge_control_cell_lenght()

d) Trailing Edge Grid Points Distribution Control

• set_b2b_hoh_trailing_edge_control_type_none()

• set_b2b_hoh_trailing_edge_control_type_absolute_distance()

• set_b2b_hoh_trailing_edge_control_type_relative_distance()

• set_b2b_hoh_trailing_edge_control_type_cell_lenght()

• get_b2b_hoh_trailing_edge_control_type()

• set_b2b_hoh_trailing_edge_control_absolute_distance(value)


12-20 AutoGrid5™

• get_b2b_hoh_trailing_edge_control_absolute_distance()

• set_b2b_hoh_trailing_edge_control_relative_distance(value)

• get_b2b_hoh_trailing_edge_control_relative_distance()

• set_b2b_hoh_trailing_edge_control_cell_lenght(value)

• get_b2b_hoh_trailing_edge_control_cell_lenght()

• set_b2b_hoh_blade_points_distribution_smoothing_steps(value)

• get_b2b_hoh_blade_points_distribution_smoothing_steps()

• set_b2b_hoh_wake_clustering(value)

• get_b2b_hoh_wake_clustering()

e) Mesh Control

• set_b2b_mesh_control_bnd_layer_factor(value)

• get_b2b_mesh_control_bnd_layer_factor()

• set_b2b_mesh_control_bnd_layer_cell_width(value)

• get_b2b_mesh_control_bnd_layer_cell_width()

12-3.9.5 H&I Topology Parameters

a) Topology Control

• set_b2b_HI_topology_H_inlet(value)

• get_b2b_HI_topology_H_inlet()

• set_b2b_HI_topology_H_outlet(value)

• get_b2b_HI_topology_H_outlet()

• set_b2b_HI_topology_skin_block(value)

• get_b2b_HI_topology_skin_block()


• set_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_down(value)

• get_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_down()

• set_b2b_HI_topology_grid_point_number_streamwise_blade_down(value)

• get_b2b_HI_topology_grid_point_number_streamwise_blade_down()

• set_b2b_HI_topology_grid_point_number_streamwise_blade_lower_side(value)

• get_b2b_HI_topology_grid_point_number_streamwise_blade_lower_side()

• set_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_down(value)

• get_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_down()

• set_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_up(value)

• get_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_up()

• set_b2b_HI_topology_grid_point_number_streamwise_blade_up(value)

• get_b2b_HI_topology_grid_point_number_streamwise_blade_up()

• set_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_up(value)

• get_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_up()


AutoGrid5™ 12-21

• set_b2b_HI_topology_grid_point_number_azimutal_inlet(value)

• get_b2b_HI_topology_grid_point_number_azimutal_inlet()

• set_b2b_HI_topology_grid_point_number_azimutal_outlet(value)

• get_b2b_HI_topology_grid_point_number_azimutal_outlet()

• set_b2b_HI_topology_grid_point_number_azimutal_inlet_up(value)

• get_b2b_HI_topology_grid_point_number_azimutal_inlet_up()

• set_b2b_HI_topology_grid_point_number_azimutal_outlet_up(value)

• get_b2b_HI_topology_grid_point_number_azimutal_outlet_up()

• set_b2b_HI_topology_grid_point_number_leading_edge_index(value)

• set_b2b_HI_topology_grid_point_number_trailing_edge_index(value)

c) Mesh Control

• set_b2b_HI_topology_automatic_clustering_relaxation(value)

• get_b2b_HI_topology_automatic_clustering_relaxation()

• set_b2b_HI_topology_clustering_relaxation(value)

• get_b2b_HI_topology_clustering_relaxation()

12-3.9.6 Cooling - Conjugate Heat Transfer Parameters

• set_solid_body_configuration(type)Type should be between 0 and 12:

0: disable solid body mesh generation1: basin+cooling channel2: basin3: cooling channel4: radial holes without basin and without cooling channel5: solid body alone6: cooling channel without tip wall7: pennies at hub8: pennies at shroud9: pennies at hub & shroud10: squiller tip on lower side11: squiller tip on upper side12: squiller tip on camber line

• get_solid_body_configuration()

a) Blade Cooling Holes Control

• number_of_holes_lines()

• add_holes_line()

• holes_line(i)

• generate_holes()

b) Cooling Channel & Basin Control

• solid_body()

• cooling_channel()


12-22 AutoGrid5™

• is_solid_body_parametric()

• enable_solid_body_parametric_definition()

• disable_solid_body_parametric_definition()

• enable_solid_body_shape_blunt_trailing_edge()

• disable_solid_body_shape_blunt_trailing_edge()

• get_solid_body_shape_blunt_trailing_edge()

• set_solid_body_shape_number_of_control_points(value)

• get_solid_body_shape_number_of_control_points()

• set_solid_body_shape_start_location(value)

• get_solid_body_shape_start_location()

• set_solid_body_shape_end_location(value)

• get_solid_body_shape_end_location()

• set_solid_body_shape_start_width(value)

• get_solid_body_shape_start_width()

• set_solid_body_shape_middle_width(value)

• get_solid_body_shape_middle_width()

• set_solid_body_shape_end_width(value)

• get_solid_body_shape_end_width()

• set_solid_body_geometry_from_geomTurbo_file(geomTurbo_file)

• set_solid_body_streamwise_distribution_type_same_as_blade()

• set_solid_body_streamwise_distribution_type_adapted()

• get_solid_body_streamwise_distribution_type()

• set_solid_body_number_of_points_azimutal(value)

• get_solid_body_number_of_points_azimutal()

c) Basin Holes & Separator Control

• number_of_basin_holes()

• add_basin_hole()

• basin_hole(i)

• init_basin_holes_from_external_file(filename)

• export_basin_holes_geometry()

• export_basin_holes_definition()

• number_of_basin_separators()

• add_basin_separator()

• basin_separator(i)

d) Pin Fins & Ribs Control

• add_pin_fins_channel()


AutoGrid5™ 12-23

12-3.10 Gap Class Commands

• select()

• delete()

• link_non_axisymmetric_geometry(surface_names)

• set_non_axisymmetric_hub()

• unset_non_axisymmetric_hub()

• set_non_axisymmetric_hub_repair_damage()

• unset_non_axisymmetric_hub_repair_damage()

• create_chimera_block()

• skip_chimera_block()

• set_topology_HO()

• set_topology_O()

• get_topology_type()

• set_width_at_leading_edge(value)

• get_width_at_leading_edge()

• set_width_at_trailing_edge(value)

• get_width_at_trailing_edge()



• set_constant_cell_number(value)

• get_constant_cell_number()

• set_number_of_points_in_spanwise_direction(value)

• get_number_of_points_in_spanwise_direction()

• enable_defined_shape()

• disable_defined_shape()

• define_shape(curve_file_name)

• get_defined_shape()

12-3.11 Fillet Class Commands

• select()

• set_radius_at_leading_edge(value)

• get_radius_at_leading_edge()

• set_radius_at_trailing_edge(value)

• get_radius_at_trailing_edge()

• set_minimum_angle(value)

• get_minimum_angle()



• set_constant_cell_number(value)


12-24 AutoGrid5™

• get_constant_cell_number()

• set_number_of_points_in_spanwise_direction(value)

• get_number_of_points_in_spanwise_direction()

• enable_defined_shape()

• disable_defined_shape()

• define_shape(curve_file_name)

• get_defined_shape()

12-3.12 WizardLETE Class Commands

• select()

• delete()

• generate(replace_le=1,replace_te=1)

• set_layer_upstream_hub_location(value,update=0)

• get_layer_upstream_hub_location()

• set_layer_downstream_hub_location(value,update=0)

• get_layer_downstream_hub_location()

• set_layer_upstream_shroud_location(value,update=0)

• get_layer_upstream_shroud_location()

• set_layer_downstream_shroud_location(value,update=0)

• get_layer_downstream_shroud_location()

• set_layer_hub_clustering(value,update=0)

• get_layer_hub_clustering()

• set_layer_shroud_clustering(value,update=0)

• get_layer_shroud_clustering()

• set_layer_number(value,update=0)

• get_layer_number()

• set_layer_number_of_control_points(value,update=0)

• get_layer_number_of_control_points()

• set_layer_number_of_constant_cells(value,update=0)

• get_layer_number_of_constant_cells()

• last_section_is_used()

• last_section_is_not_used()

• is_last_section_used()

• first_section_is_used()

• first_section_is_not_used()

• is_first_section_used()

• set_blade_normal_type()

• set_blade_very_low_angle_type()

• set_blade_very_high_angle_type()


AutoGrid5™ 12-25

• get_blade_type()

• set_hub_expansion(value,update=0)

• get_hub_expansion()

• set_shroud_expansion(value,update=0)

• get_shroud_expansion()

• set_leading_edge_location(layer,value,update=0)

• get_leading_edge_location(layer)

• set_trailing_edge_location(layer,value,update=0)

• get_trailing_edge_location(layer)

• set_chord_tolerance_at_le(value,update=0)

• get_chord_tolerance_at_le()

• set_chord_tolerance_at_te(value,update=0)

• get_chord_tolerance_at_te()

• set_iteration_steps(value,update=0)

• get_iteration_steps()

• set_active_layer(index)

• get_number_of_control_point()

• get_point_leading_edge_xyz (index)

• get_point_trailing_edge_xyz (index)

• get_point_leading_edge_mt (index)

• get_point_trailing_edge_mt (index)

12-3.13 Blade Sheet Class Commands

• select()

• delete()

• lower_zone()

• upper_zone()

• set_type(value)Value should be either 0 for lower side, 1 for upper side or 2 for both sides.

• get_type()


• get_width()

• set_distance_from_leading_edge(value)

• get_distance_from_leading_edge()

• set_distance_from_trailing_edge(value)

• get_distance_from_trailing_edge()

• set_npts_near_leading_edge(value)

• get_npts_near_leading_edge()

• set_npts_near_trailing_edge(value)


12-26 AutoGrid5™

• get_npts_near_trailing_edge()

12-3.14 RSInterface Class Commands

• select()

• copy_left_meridional_distribution()

• copy_right_meridional_distribution()

• paste_left_meridional_distribution()

• paste_right_meridional_distribution()

• merge_meridional_distribution()

• set_name(value)

• get_name()

• streamwise_number_of_points(value)

• get_streamwise_number_of_points()

• streamwise_index(value)

• get_streamwise_index()

• enable_b2b_control()

• disable_b2b_control()

• get_b2b_control()

• geometry_is_fixed()

• geometry_is_not_fixed()

• get_geometry_is_fixed()

• cell_width_in_streamwise_direction(value)

• get_cell_width_in_streamwise_direction()

• set_linear_shape()

• set_default_shape()

• set_z_cst_shape(value)

• set_r_cst_shape(value)

• get_shape()

• get_r_cst_value()

• get_z_cst_value()

• set_relative_location(value)

• set_external_curve(file_name)

• link_geometry(curve_names)Curve_names should be a list, even if it is composed of only 1 element (use [ ]).

• set_reference_frame_relative()

• set_reference_frame_absolute()

• get_reference_frame()

• get_relative_location()

• get_reference_row()


AutoGrid5™ 12-27

• get_reference_row_location()

• move_control_point(i,point)

12-3.15 BasicCurve Class Commands

This class gives access to parameters of basic curves defining the channel, nozzle and ZR effects.

• delete()

• set_discretisation(i)

• get_discretisation()

• check_geometry()

• set_data_reduction(reduction, min_dist=1e-6, max_angle=80)

• get_data_reduction()

• get_data_reduction_minimal_distance()

• get_data_reduction_maximum_angle()

12-3.16 StagnationPoint Class Commands

This class gives access to parameters of blade leading and trailing edge in blade to blade view (onlyaccessible in default topology).

• set_distribution_type_absolute_distance()

• set_distribution_type_relative_distance()

• set_distribution_type_cell_lenght()

• get_distribution_type()

• set_distribution_absolute_distance(value)

• get_distribution_absolute_distance()

• set_distribution_relative_distance(value)

• get_distribution_relative_distance()

• set_distribution_cell_lenght(value)

• get_distribution_cell_lenght()

• enable_distribution_from_expansion_ratio()

• disable_distribution_from_expansion_ratio()

• get_distribution_from_expansion_ratio()

• desired_expansion_ratio(value)

• get_desired_expansion_ratio()

• set_percentage_cst_cell(value)

• get_percentage_cst_cell()

12-3.17 TechnologicalEffectZR Class Commands

• select()


12-28 AutoGrid5™

• block_list()

• set_parameters(expMax,w,opt,cst,exp,opt2,per,coarse,tol,p)expMax : maximum expansion ratiow : wall cell widthopt : smoothing stepscst : percentage constant cellexp : radial expansionopt2 : far field smooth smoothing stepsper : periodic fnmbcoarse : coarse grid leveltol : connection tolerancep : propagate theta deviation

• technoEffectmeridional_toggle_grid_rep()

• technoEffectmeridional_computeDefaultMesh()

• technologicalEffectZR(B,row):# indices from 1Returns an object of class ZR effect.B can be either a ZR effect name or a ZR effect index.

• technoEffectmeridional_start_edit_mode()

• technoEffectmeridional_stop_edit_mode()

12-3.18 TechnologicalEffect3D Class Commands

• select()

• delete()

• block_list()

• set_name(name)

• load_geometry(file_name)

• load_topology(name)

• save_topology(name)

• copy_topology()


• link_geometry(curve_names, surface_names)Curve_names and surface_names should be a list, even if it is composed of only 1 element(use [ ]).

12-3.19 Cooling Channel Class Commands

• select()

• pinFinsChannel(i)Returns an object of class PinFinsChannel.

12-3.20 Hole Class Commands

• select()

• delete()


AutoGrid5™ 12-29

• setName(value)

• getName()

12-3.20.1Hole Location Control

a) Parametric Mode (all hole type excepted grooves)

• set_spanwise_location(value,highlight=1)

• get_spanwise_location()

• set_streamwise_location_from_leading_edge(value,highlight=1)

• get_streamwise_location_from_leading_edge()

• set_streamwise_location_from_trailing_edge(value,highlight=1)

• get_streamwise_location_from_trailing_edge()

• set_streamwise_location_on_chord_lenght(value,highlight=1)

• get_streamwise_location_on_chord_lenght()

b) XYZ Mode

• set_x_location(value,highlight=1)

• get_x_location()

• set_y_location(value,highlight=1)

• get_y_location()

• set_z_location(value,highlight=1)

• get_z_location()

• set_x2_location(value,highlight=1)

• get_x2_location()

• set_y2_location(value,highlight=1)

• get_y2_location()

• set_z2_location(value,highlight=1)

• get_z2_location()

c) RTHZ Mode

• set_r_location(value,highlight=1)

• get_r_location()

• set_theta_location(value,highlight=1)

• get_theta_location()



• set_r2_location(value,highlight=1)

• get_r2_location()

• set_theta2_location(value,highlight=1)

• get_theta2_location()



12-30 AutoGrid5™


12-3.20.2Hole Axis Control

a) Parametric Mode (all hole type excepted grooves)

• set_streamwise_angle(value,highlight=1)

• get_streamwise_angle()

• set_spanwise_angle(value,highlight=1)

• get_spanwise_angle()

b) XYZ Mode (all hole type excepted grooves)

• set_x_axis(value,highlight=1)

• get_x_axis()

• set_y_axis(value,highlight=1)

• get_y_axis()

• set_z_axis(value,highlight=1)

• get_z_axis()

c) RTHZ Mode (all hole type excepted grooves)

• set_r_axis(value,highlight=1)

• get_r_axis()

• set_theta_axis(value,highlight=1)

• get_theta_axis()


• get_z_axis()

12-3.20.3Hole Dimension Control

• set_depth(value,highlight=1)

• get_depth()

a) Circular Shape

• set_diameter(value,highlight=1)

• get_diameter()

b) Rectangular/Oval Shape

• set_width(value,highlight=1)

• get_width()

c) Grooves (Parametric Mode)

• set_heigth(value,highlight=1)

• get_heigth()


AutoGrid5™ 12-31

d) Quadrilateral Shape (4-Sided)

• set_holes_p1x(value,highlight=1)

• get_holes_p1x()


• get_holes_p2x()


• get_holes_p3x()


• get_holes_p4x()

• set_holes_p1y(value,highlight=1)

• get_holes_p1y()


• get_holes_p2y()


• get_holes_p3y()


• get_holes_p4y()

12-3.20.4Hole Orientation Control

• set_orientation_angle(value,highlight=1)

• get_orientation_angle()

12-3.21 HolesLine Class Commands

• select()

• delete()

• number_of_holes()

• hole(i)

• setName(value)

• getName()

• preview3D()

• hide2D()

12-3.21.1External File Control

• exportGeometry()

• exportDefinition()

• defineGeometry(file_name)


12-32 AutoGrid5™

12-3.21.2Hole Line Geometry Control

a) Holes Number

• set_holes_number(value,highlight=1)

• get_holes_number()

b) Hole Shape

• set_circular_shape(highlight=1)

• set_rectangular_shape(highlight=1)

• set_oval_shape(highlight=1)

• set_trailing_edge_groove_shape(highlight=1)

• set_trailing_edge_circular_hole_shape(highlight=1)

• set_quadrilateral_shape(highlight=1)

• get_shape(highlight=1)

c) Hole Location

• set_location_to_blade_upper_side(highlight=1)

• set_location_to_blade_lower_side(highlight=1)


• enable_parametric_holes_location(highlight=1)

• set_first_spanwise_parametric_location(value,highlight=1)

• get_first_spanwise_parametric_location(highlight=1)

• set_last_spanwise_parametric_location(value,highlight=1)

• get_last_spanwise_parametric_location()

• set_streamwise_location_on_meridional_chord(value,highlight=1)

• set_streamwise_location_from_leading_edge(value,highlight=1)

• set_streamwise_location_from_trailing_edge(value,highlight=1)

• set_first_streamwise_location_on_meridional_chord(value,highlight=1)

• get_first_streamwise_location_on_meridional_chord()

• set_first_streamwise_location_from_leading_edge(value,highlight=1)

• get_first_streamwise_location_from_leading_edge()

• set_first_streamwise_location_from_trailing_edge(value,highlight=1)

• get_first_streamwise_location_from_trailing_edge()

• set_last_streamwise_location_on_meridional_chord(value,highlight=1)

• get_last_streamwise_location_on_meridional_chord()

• set_last_streamwise_location_from_leading_edge(value,highlight=1)

• get_last_streamwise_location_from_leading_edge()

• set_last_streamwise_location_from_trailing_edge(value,highlight=1)

• get_last_streamwise_location_from_trailing_edge()


AutoGrid5™ 12-33

c.2) XYZ Mode

• enable_xyz_holes_location(highlight=1)







• set_x2_location(value,highlight=1)

• get_x2_location()

• set_y2_location(value,highlight=1)

• get_y2_location()



c.3) RTHZ Mode

• enable_mtheta_holes_location(highlight=1)

• set_r_location(value,highlight=1)

• get_r_location()





• set_r2_location(value,highlight=1)

• get_r2_location()

• set_theta2_location(value,highlight=1)

• get_theta2_location()



d) Hole Axis


• enable_parametric_holes_axis(highlight=1)





d.2) XYZ Mode

• enable_xyz_holes_axis(highlight=1)



12-34 AutoGrid5™

• get_x_axis()


• get_y_axis()


• get_z_axis()

d.3) RTHZ Mode

• enable_rthz_holes_axis(highlight=1)

• set_r_axis(value,highlight=1)

• get_r_axis()

• set_theta_axis(value,highlight=1)

• get_theta_axis()


• get_z_axis()

e) Hole Dimension


• get_depth()

e.1) Circular Shape


• get_diameter()

e.2) Rectangular/Oval Shape


• get_width()

e.3) Grooves (Parametric Mode)


• get_heigth()

e.4) Quadrilateral Shape (4-Sided)


• get_holes_p1x()


• get_holes_p2x()


• get_holes_p3x()


• get_holes_p4x()


• get_holes_p1y()


AutoGrid5™ 12-35


• get_holes_p2y()


• get_holes_p3y()


• get_holes_p4y()

f) Hole Orientation



12-3.21.3Hole Line Mesh Control

a) Grid Points Number

• set_number_of_points_in_boundary_layer(value,highlight=1)

• get_number_of_points_in_boundary_layer()

• set_number_of_points_streamwise(value,highlight=1)

• get_number_of_points_streamwise()

• set_number_of_points_spanwise(value,highlight=1)

• get_number_of_points_spanwise()

• set_number_of_points_streamwise_left(value,highlight=1)

• get_number_of_points_streamwise_left()

• set_number_of_points_streamwise_right(value,highlight=1)

• get_number_of_points_streamwise_right()

• set_number_of_points_spanwise_up(value,highlight=1)

• get_number_of_points_spanwise_up()

• set_number_of_points_spanwise_down(value,highlight=1)

• get_number_of_points_spanwise_down()

b) Optimization

• set_number_of_optimization_steps_inside_holes(value,highlight=1)

• get_number_of_optimization_steps_inside_holes()

• enable_skewness_control_inside_holes()

• disable_skewness_control_inside_holes()

• get_skewness_control_inside_holes()

• set_number_of_optimization_steps_arround_holes(value,highlight=1)

• get_number_of_optimization_steps_arround_holes()

• enable_skewness_control_arround_holes()

• disable_skewness_control_arround_holes()

• get_skewness_control_arround_holes()


12-36 AutoGrid5™

c) Wake Control

• set_upstream_wake_lenght(value,highlight=1)

• get_upstream_wake_lenght()

• set_downstream_wake_lenght(value,highlight=1)

• get_downstream_wake_lenght()

d) Holes Line Mesh Shape Control

• set_hole_line_shape_link_to_next_hole_line_shape(value,highlight=1)

• get_hole_line_shape_link_to_next_hole_line_shape()

• set_hole_line_shape_link_to_previous_hole_line_shape(value,highlight=1)

• get_hole_line_shape_link_to_previous_hole_line_shape()

12-3.21.4Global Mesh Control

• set_preserved_layers_on_lower_side(value,highlight=1)

• get_preserved_layers_on_lower_side()

• set_preserved_layers_on_upper_side(value,highlight=1)

• get_preserved_layers_on_upper_side()

• set_intersection_tolerance(value,highlight=1)

• get_intersection_tolerance()

12-3.22 Basin Class Commands

• select()

• delete()

12-3.22.1Global Parameters

• reset_parametrization_up()

• reset_parametrization_down()

• set_optimization_steps(value)

• get_optimization_steps()

12-3.22.2Hole Parameters

• set_boundary_optimization_steps()

• get_boundary_optimization_steps()

• enable_parametric_location()

• enable_XYZ_location(value)

• set_parametric_streamwise_location(value)

• get_parametric_streamwise_location()

• set_anchor_points_x_coordinate(value)

• get_anchor_points_x_coordinate()

• set_anchor_points_y_coordinate(value)


AutoGrid5™ 12-37

• get_anchor_points_y_coordinate()

• set_anchor_points_z_coordinate(value)

• get_anchor_points_z_coordinate()

• set_axis_x_coordinate(value)

• get_axis_x_coordinate()

• set_axis_y_coordinate(value)

• get_axis_y_coordinate()

• set_axis_z_coordinate(value)

• get_axis_z_coordinate()

• set_number_of_points_on_hole_side(value)

• get_number_of_points_on_hole_side()

a) Basin Hole

• set_diameter(value)

• get_diameter()

• set_number_of_points_in_bnd_layer(value)

• get_number_of_points_in_bnd_layer()

• set_parametric_azimutal_deviation(value)

• get_parametric_azimutal_deviation()

b) Separator


• get_width()

c) Penny

• set_diameter(value)

• get_diameter()

• set_number_of_points_in_bnd_layer(value)

• get_number_of_points_in_bnd_layer()

• set_parametric_azimutal_deviation(value)

• get_parametric_azimutal_deviation()

• set_rotation_angle(value)

• get_rotation_angle()

12-3.23 PinFinsChannel Class Commands

• select()

• delete()

• box()

• view_mesh(pinfinstype,boxtype,boxside,clear=1)


12-38 AutoGrid5™

pinfinstype : 0, 1 for grid, 2 for solid and 3 for bothbox type : 0, 1, 2 or 3box side : 0, 1 or 2.

• viewbox(side,rep)

• hidebox()

• link_geometry(curve_names,surfaces_name)

• edit()

• stop_edit()

• generate()

• number_of_pinFins_line()

• add_pinFins_line()

• pinFins_line(i)Returns an object of class PinFinsLine.

12-3.24 PinFinsLine Class Commands

• select()

• delete()

• getName()

• number_of_pinFins()

• pinFin(i)Returns an object of class PinFin.

• preview3D()

• hide3D()





12-3.24.2Pin Fins Line Geometry Control

a) Pin Fins Number

• set_pinfins_number(value,highlight=1)

• get_pinfins_number()

b) Pin Fin Shape







AutoGrid5™ 12-39

c) Pin Fin Location


• enable_parametric_pinfins_location(highlight=1)


• get_first_spanwise_parametric_location()



• set_streamwise_location(value,highlight=1)

• get_streamwise_location()

c.2) XYZ Mode

• enable_xyz_pinfins_location(highlight=1)







c.3) UV Mode

• enable_UV_pinfins_location(highlight=1)

• set_U_location(value,highlight=1)

• get_U_location()

• set_V_location(value,highlight=1)

• get_V_location()

d) Pin Fin Axis Control


• enable_parametric_pinfins_axis(highlight=1)





d.2) XYZ Mode

• enable_xyz_pinfins_axis(highlight=1)


• get_x_axis()


• get_y_axis()



12-40 AutoGrid5™

• get_z_axis()

e) Pin Fin Dimension Control


• get_depth()

e.1) Circular Shape


• get_diameter()

• set_diameter2(value,highlight=1)

• get_diameter2()



• get_width()


• get_heigth()



• get_holes_p1x()


• get_holes_p2x()


• get_holes_p3x()


• get_holes_p4x()


• get_holes_p1y()


• get_holes_p2y()


• get_holes_p3y()


• get_holes_p4y()

f) Pin Fin Orientation Control




AutoGrid5™ 12-41

12-3.24.3Pin Fin Mesh Control






• set_number_of_points_spanwise(value,highlight=1)

• get_number_of_points_spanwise()





• set_number_of_points_spanwise_up(value,highlight=1)

• get_number_of_points_spanwise_up()

• set_number_of_points_spanwise_down(value,highlight=1)

• get_number_of_points_spanwise_down()

b) Optimization










• get_skewness_control_arround_holes()

c) Wake Control











12-42 AutoGrid5™








12-3.25 PinFin Class Commands

• select()

• delete()

• getName()

12-3.25.1Pin Fin Location

a) Parametric Mode


• get_first_spanwise_parametric_location()




• get_streamwise_location()

b) XYZ Mode







c) UV Mode

• set_U_location(value,highlight=1)

• get_U_location()

• set_V_location(value,highlight=1)

• get_V_location()


AutoGrid5™ 12-43

12-3.25.2Pin Fin Axis Control

a) Parametric Mode





b) XYZ Mode


• get_x_axis()


• get_y_axis()


• get_z_axis()

12-3.25.3Pin Fin Dimension Control


• get_depth()

a) Circular Shape


• get_diameter()

• set_diameter2(value,highlight=1)

• get_diameter2()



• get_width()


• get_heigth()

c) Quadrilateral Shape (4-Sided)


• get_holes_p1x()


• get_holes_p2x()


• get_holes_p3x()



12-44 AutoGrid5™

• get_holes_p4x()


• get_holes_p1y()


• get_holes_p2y()


• get_holes_p3y()


• get_holes_p4y()

12-3.25.4Pin Fin Orientation Control



12-3.26 EndWall Class Commands

• select()

• delete()

12-3.26.1End Wall Generation Control

• generate()

• generate_holes()

12-3.26.2End Wall Parameters Control


• get_width()

• set_number_of_spanwise_points(value)

• get_number_of_spanwise_points()

• set_number_of_optimization_steps(value)

• get_number_of_optimization_steps()

• enable_multigrid_optimization(value)

• disable_multigrid_optimization(value)

• get_multigrid_optimization_status()

• number_of_holes_lines()

• add_holes_line()

• holes_line(i)

12-3.27 EndWallHole Class Commands

• select()

• delete()


AutoGrid5™ 12-45

• setName(value)

• getName()

12-3.27.1Hole Location Control

a) XYZ Mode







b) MTheta Mode

• set_m_location(value,highlight=1)

• get_m_location()



12-3.27.2Hole Axis Control

a) Parametric Mode





b) XYZ Mode


• get_x_axis()


• get_y_axis()


• get_z_axis()


a) Circular Shape

• set_holes_diameter(value,highlight=1)

• get_holes_diameter()


12-46 AutoGrid5™


• set_holes_width(value,highlight=1)

• get_holes_width()

• set_holes_heigth(value,highlight=1)

• get_holes_heigth()

c) Quadrilateral Shape (4-Sided)


• get_holes_p1x()


• get_holes_p2x()


• get_holes_p3x()


• get_holes_p4x()


• get_holes_p1y()


• get_holes_p2y()


• get_holes_p3y()


• get_holes_p4y()




12-3.28 EndWallHolesLine Class Commands

• select()

• delete()

• number_of_holes()

• hole(i)

• setName(value)

• getName()





AutoGrid5™ 12-47


12-3.28.2Hole Line Geometry Control

a) Holes Number

• set_holes_number(value,highlight=1)

• get_holes_number()

b) Hole Shape






c) Hole Location


• enable_parametric_holes_location(highlight=1)

• set_first_theta_location(value,highlight=1)

• get_first_theta_location(highlight=1)

• set_last_theta_location(value,highlight=1)

• get_last_theta_location(highlight=1)


• get_streamwise_location(highlight=1)

c.2) XYZ Mode

• enable_xyz_holes_location(highlight=1)







c.3) MTheta Mode

• enable_mtheta_holes_location(highlight=1)

• set_m_location(value,highlight=1)

• get_m_location()




12-48 AutoGrid5™

d) Hole Axis


• enable_parametric_holes_axis(highlight=1)





d.2) XYZ Mode

• enable_xyz_holes_axis(highlight=1)


• get_x_axis()


• get_y_axis()


• get_z_axis()

e) Hole Dimension

e.1) Circular Shape

• set_holes_diameter(value,highlight=1)

• get_holes_diameter()


• set_holes_width(value,highlight=1)

• get_holes_width()

• set_holes_heigth(value,highlight=1)

• get_holes_heigth()



• get_holes_p1x()


• get_holes_p2x()


• get_holes_p3x()


• get_holes_p4x()


• get_holes_p1y()


• get_holes_p2y()


AutoGrid5™ 12-49


• get_holes_p3y()


• get_holes_p4y()

f) Hole Orientation



12-3.28.3Hole Line Mesh Control






• set_number_of_points_azimutal(value,highlight=1)

• get_number_of_points_azimutal()





• set_number_of_points_azimutal_up(value,highlight=1)

• get_number_of_points_azimutal_up()

• set_number_of_points_azimutal_down(value,highlight=1)

• get_number_of_points_azimutal_down()

• set_up_clustering_relaxation(value,highlight=1)

• get_up_clustering_relaxation()

• set_down_clustering_relaxation(value,highlight=1)

• get_down_clustering_relaxation()

b) Optimization











12-50 AutoGrid5™

• get_skewness_control_arround_holesc

c) Wake Control

















Index

AutoGrid5™ i

INDEX

Numerics3D Block Naming 8-3

3D Effect 10-1

3D Generation 10-6

AActive B2B Layer 2-54

Active Layer 3-18

Add Wizard LE TE 5-23

ADT algorithm 2-33

Angular Deviation 2-36

Aspect Ratio 2-36

Axial Compressor 4-22

Axial Fan 4-24

Axial Turbine 4-20

BB2B Cut 8-7

Background Color 1-6

Balloon Help 2-18

Basic Curves 6-1

Basin 11-4, 11-8

Holes 11-27

Separator 11-27

Basin Bottom Wall 11-8

Batch 3-23Blade

Clustering 7-35

Configuration 11-2

Definition 3-3

Expansion 5-18

Management Icons 2-47

Offset 7-49

Rotation 5-37

Solid Mesh 11-1

Tip 4-17

Blade Holes 11-14

Geometry 11-17

Mesh 11-23Blade to Blade

Control 3-14, 4-11

Mesh Visibility 2-18

Optimization 7-55

Quality Visibility 2-18

Settings 4-14

Topology 7-3

Blend 5-20, 7-14, 7-44Block

Group 2-57

Sweep 2-20

Blunt 5-18, 5-12, 7-20

Throat 7-15

Bnd Straight Control 7-59

Boundaries Optimization 7-59

Boundary Conditions 2-26, 8-4

Filters 2-27

Inlet 7-18

Outlet 7-18

Periodic 7-9

Types 2-27

Boundary Layer Factor 7-33Bulb

Control 6-17

Control Lines 6-9Bypass

Control 6-18

Control Lines 6-9

Geometry 5-11, 5-13

CCAD Format 3-9

CAD Import Interface 5-3

Cascade 5-33

CATIA V5 2-12

Cell Width 2-36, 3-13, 7-29

Cell Width Ratio 2-39

CGNS 2-15Channel

Connection 9-10

Control 6-11

Shading 2-18

Check Meridional Curves 6-11

Clustering 3-17

Clustering around Blade 7-9

Coarse Grid 2-21

Command 12-2

Configuration 11-2

Configuration Tree 2-50

Conformal Mapping 3-15

Conjugate Heat Transfer 3-3, 11-1

Connection 2-28

Edge-Edge 7-53

Whole Grid 7-54

Control Area 2-69

Control Line 7-27

Cell Width 7-29

Downstream 7-28

ii AutoGrid5™

Index

INDEX

On Blade 7-29

Upstream 7-28

Control Lines 6-6

Control Points 2-8, 6-6

Convention 1-4

Convergence History 2-18

Cooling 3-3, 11-1

Blades Holes 11-14

Cooling Channel 11-4

Mesh Control 11-8

Offset Shape 11-6

Coordinate Axis 2-72

Copy 4-13

Copy Distribution 6-20

Copy Topology 7-6, 10-2, 10-5

Counter Rotative Fan 4-23Create

Project 2-2

Template 2-2

Create Project 3-10

Criterion Quality 2-36

Curves 6-1

Cut 8-7

Cut Offset 5-19

DData Reduction 5-36

Default Topology 3-15, 7-7

ZR Effect 9-9

Define Geometry 5-2Delete

Basic Curve 6-2Detect

Channel Connection 9-10

Unmapped Edges 9-10

Diffuser 4-22

Discretization Basic Curve 6-2

Domain 2-62, 3-2

Boundaries 2-65

Delete 2-64

Group 2-63

Properties 2-63

Rename 2-63

Driver 1-5, 2-17

Duplicate 2-59, 2-61

EEdge-Edge 7-53

Edit Hub 5-13

Edit Shroud 5-13

Edition Mode 10-3

End Wall Holes 11-34

End Wall Solid Body 11-12

Exit AutoGrid5 2-18

Expansion 5-18

Factor 5-19

Ratio 2-36

Export 5-37

Block Coordinates 2-8

Control Points 2-8

Face Coordinates 2-8

Geometry 2-8

IGES 2-8

Patch Coordinates 2-9

Plot3D 2-9

Extension Control 7-33

Extension Offset 5-19

External Grid 2-11

FFace Displacement 2-22

Fan 4-23, 4-24

Far Field 4-17, 9-10

Features 1-1

File Chooser 2-77

File Management 1-3, 8-6

Files 3-21

Mesh 1-3, 8-7

Template 1-3, 8-7

Fillet 4-10, 5-21

Filters 2-27

Fin 5-11

Control 6-20

Control Line 6-9

Fitting 5-18

Flow Path 3-14, 4-10

Control 6-14

Manual Editing 6-14

Fluid Domain 2-6

Fomat Channel 3-4

Foreground Color 1-6Format

".geomTurbo" 3-4

Blade 3-6

CAD 3-9

Index

AutoGrid5™ iii

INDEX

Francis Turbine 4-20

Freeze Skin Mesh 7-60

Full Matching Mesh 4-12

Full Mesh Generation 3-13

Full Non Matching 2-31, 9-10

GGap

Definition 4-10


Topology 6-16Generation

3D Mesh 3-20

Status 2-71

Geometry 2-8, 2-18

Check 4-9, 5-34

Definition 2-52, 4-7

Export 5-37

Group 2-55, 5-9

Geometry Axis 5-6

Geometry Definition 5-2

".geomTurbo" Format 3-4

Getting Start 1-1

Global Control 11-25

Graphics 1-5

Area 2-74

Window 2-74Grid

Configuration 2-58

Level 2-53, 4-12

Parameters Area 2-70

Points Control 7-7

Save 2-6

Grid Quality 2-34

Report 2-41

GridPro 2-16

HH&I Topology 7-38

Gap Control 7-44

Grid Clustering 7-43

Grid Points 7-40

High Staggered Blade 7-21, 7-45

HOH Topology 7-32

Clustering 7-35

Grid Points 7-34

Hub 3-2

Edition 6-3

Non-Axisymmetric 5-14

Hub Gap Control 6-16, 7-13, 7-36

IIGES 2-8, 2-13

IGG Data 2-10

Impeller 4-22Import

Block File 2-11

CATIA V5 2-12

CGNS 2-15

External Grid 2-11

GridPro 2-16

IGES 2-13

IGG Data 2-10

Mesh 2-9

Parasolid 2-12

Plot3D 2-14

Topology 2-12Import CAD

Edit 5-6

File 5-3

Geometry 5-6

Geometry File 5-2

Link to... 5-10

Menu 5-3

Quick Access Pad 5-9

View 5-6

Viewing Buttons 5-9

Inducer 4-21

Info 3-21

Information Area 2-70

Inlet Control 7-18

Inner Gap 2-39

Inserted Cooling Tube 11-10

Installation 1-5

Interface 1-6, 2-1

KKaplan Turbine 4-21

Keyboard Input Area 2-70

LLayer Control 8-2

Leading Control 7-10

Leading Edge Wizard 5-23

Library 10-1, 10-4

Library Project 3-20

License 1-7

Lights 2-17

iv AutoGrid5™

Index

INDEX

Loop Detection 5-35

Low Memory 3-13

MMachine Type 4-9

Main Project 2-59

Duplicate 2-59

Merge 2-60

Manual Editing 6-14

Matching 9-10

Menu Bar 4-2Merge

Distribution 6-20

Project 2-6

Meridional Check 6-11Meridional Effect

3D Generation 9-14

Edition Mode 9-2

Geometry Definition 9-2

Matching Connections 9-12

Polylines 9-5

Topology Definition 9-6Mesh

Control 2-53, 4-7, 6-12

Domain 3-2

Files 1-3, 8-7

Generation 2-45, 3-10, 3-13, 4-4

Icons 2-46

Quality 6-22, 8-6

Visibility 2-18

Mesh Quality Report 8-6

Message Area 2-70

Mouse Coordinates Area 2-70

MSW 1-5

Multigrid Acceleration 7-59

MultiSplitter Control 7-60

Multistage 4-13

NNegative Cells 2-43

Non-Axi Tip Gap 5-11


Non-Matching Control 7-59

Nozzle 5-11

Edition 6-3

Number of Blades 3-12

Number of Mesh Points 8-5

OOpen Project 2-3

OPENGL 1-5

Optimization 3-18, 7-55, 9-10

High Staggered Blade 7-22

Steps 7-56

Orthogonality 2-36, 7-57

Outlet Control 7-18

Overlap 2-36

PParasolid 2-12

Paste 4-13

Paste Distribution 6-20

Paste Topology 7-6, 10-2, 10-5

Patch 2-26

Divide 2-28

Visualization 2-19

Penny 11-5

Periodic Boundary Conditions 7-9

Periodic Full Non Matching 9-11

Periodicity 2-25, 3-12

Persistency 10-6

Pin Fins 11-37

Plot3D 2-14

Polyline 9-5

Preferences 2-16

Saving 2-18

Pressure Side 5-12Print

PNG file 2-7

PostScript file 2-7

Progess Status 2-18Project

Batch 3-23

Create 2-2, 3-10

Files 3-21

Icons 4-3

Import 2-9

Info 3-21

Library 3-20, 3-21

List 2-6

Management 1-3, 2-45, 2-50, 11-27

Merge 2-6

Open 2-3

Persistency 3-20

Save 2-5

Setup 3-11

Index

AutoGrid5™ v

INDEX

Projection 5-16

Projection Clustering 7-45

Propagate Theta Deviation 9-11

Pump 4-23

QQuality

Criterion 2-36

Icons 2-46, 4-4

Visibility 2-18

Quick Access Pad 2-48

Quit AutoGrid5 2-18

RRadial Diffuser 4-22

Radial Expansion 9-10

Relative Inner Gap 2-39

Relax Clustering 7-18, 7-45

Relaxation 7-45

Repetition 2-22, 2-32, 3-13

Report 2-41, 8-6

Return Channel 4-23

Ribs 11-41

Rotation 5-18Rotor/Stator

Edition 6-4

Properties 6-5

ZR Effect 9-7

Rotor-Stator 2-33

Rounded 7-14, 7-44Row

Definition 2-50, 4-7


Mesh Control 2-54

Periodicity 3-7

Type 3-7, 4-9

Row Wizard 4-8

Ruled Surface 3-9

SSave

Fluid Domain 2-6

Grid 2-6

PNG file 2-7

PostScript file 2-7

Project 2-5

Template 2-5

Script 10-6, 12-1

Select Geometry 5-6

Sewing 5-19

Sharp 7-14, 7-44

Sheet 5-28

SHF Pump 4-23ShroudDefinition 3-2

Definition 3-2

Edition 6-3


Shroud Gap Control 6-16, 7-13, 7-36

Skewness Control 7-56

Skin Block 7-42

Skin Mesh 7-9, 7-12

Skin Wall 11-11

Solid Body End Wall 11-12

Solid Mesh Blade 11-1

Squiller Tip 11-5

Staggered 3-16

Start 1-1

Stick 5-18

Straight 7-59

Streamwise Weights 7-4

Structured 1-2

SubProject 2-60

Delete 2-62

Duplicate 2-61

Load 2-61

Merge 2-62

Rename 2-60

Save 2-61

Suction Side 5-12

Surface Ruled 3-9

Sweep 2-20

TTandem Row 3-13, 7-24

Technological Effect 3-3, 10-1Template

Create 2-2

Files 1-3, 8-7

Save 2-5

Throat 7-15Tip Gap

Control 6-16, 7-13, 7-36


Tip Wall 11-8

Toggle 2-24, 2-69

Toolbar 2-44, 4-3

vi AutoGrid5™

Index

INDEX

Topology 7-3

Copy 7-6

Default 3-15

Default (O4H) 7-7

High Staggered Blade 7-21

HOH 7-32

Library 7-5

Optimization 7-22

Paste 7-6

Staggered 3-16

User Defined 7-47

Trailing Control 7-10

Trailing Edge Curve 11-11

Trailing Edge Wizard 5-23

Tree 2-50

Popup Menu 2-51

Type of Boundary Conditions 2-27

UUnstructured 1-2

User Defined Topology 7-47

Control Layer 7-51

Create Mesh 7-51

Geometry Control 7-48

Mesh Control 7-49

View Control 7-54

User Mode 4-3

VView 2-55, 4-8

3D 2-76

Blade-to-Blade 2-76

Buttons 2-72

Depth 2-22

Displacement 2-22

Interaction 2-77

Meridional 2-75

Symbolic 2-75

View Management 4-5

Viewing Scope 2-68

Visibility 2-17, 4-11

WWake Control 7-17, 7-58

Whole Grid 7-54

Width 2-17

Wind Turbine 4-17

Wizard 4-2

XX11 1-5

_userManual_AUTOGRID5_87

Documents

conjugate

orientationangle

quick access

main menu

numerical

menu item

parametric

cooling channels