AutoGrid5 User Guide
AutoGrid5 User Guide
IGG™/AutoGrid5™ 12.2
www.numeca.com
CONTENTS
CHAPTER 1. GETTING STARTED
1.1 Introduction 8
1.2 How To Use This Manual 11
1.3 First Time Use 12
1.3.1 Basic Installation 12
1.3.2 Expert Graphics Options 12
A. Graphics Driver 12
B. Background & Foreground Colors 13
1.4 How to Start AutoGrid5™ Interface 14
1.5 Required Licenses 14
CHAPTER 9. 3D GENERATION
9.1 Application Field 414
9.2 3D Mesh Generation 415
9.3 Mesh Quality 419
9.4 Template & Mesh Files 420
9.5 B2B Cut 421
GETTING STARTED
Welcome to the AutoGrid5™ User's Guide, a presentation of NUMECA's fully automatic grid
generator for turbomachines. This chapter presents the basic concepts of AutoGrid5™ and shows how
to get started with the program by describing:
In this section
1.1 Introduction 8
1.2 How To Use This Manual 11
1.3 First Time Use 12
1.4 How to Start AutoGrid5™ Interface 14
1.5 Required Licenses 14
What is AutoGrid5™
Features
The advanced tools of AutoGrid5™ enable to create mesh for a large range of gas turbines, fans
and compressors:
l turbofan, turboprop, turboshaft,
l turbojet and after burning turbojet,
l axial or centrifugal,
l single or multistage,
l including or not bulbs on the hub,
l with one or multiple splitter blades (centrifugal),
l with hub or shroud clearances,
l with bypass,
l with seal leakages,
l with meridional or 3D technological effects.
Depending on the geometry complexity, the user should define the requested mesh type:
structured or unstructured. Structured meshes are to be preferred for reasons of accuracy in cases
of aligned flow even if their generation can sometimes be difficult and cumbersome. Unstructured
meshes can be easily generated independently of the geometrical complexity and owing to their
nature generally tend to generate less points than in the structured case. For turbomachinery
design, because of a request of high accuracy, it is recommended to use AutoGrid5™ which
enables to provide adapted structured meshes.
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 blade
grids onto surfaces of revolution. The generation based on a conformal mapping between the 3D
Cartesian 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:
l The blade surface description.
l The curves for the definition of the hub and shroud surfaces of revolution.
l The additional data needed to handle special features such as splitters, meridional or 3D
technological effects.
2. Generation of meridional flow paths. These flow paths define the meridional trace of the
surfaces 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
user to control the mesh topology, the grid clustering and the mesh orthogonality along the
solid walls.
4. Generation of the final 3D mesh. This generation combines the meridional flow paths and the
2D blade to blade meshes to create the mesh on surfaces of revolution. The use of the
conformal mapping between the 3D Cartesian space and the 2D blade to blade space ensures
conservation of 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 of
the grid generation process, all the parameters can be saved in a template file (".trb"). Meshes for
similar geometries can be created automatically using this file.
Project Management
Mesh files
The mesh files contains the multiblock mesh topology, geometry, grid points, patch grouping and
the boundary condition types:
The mesh quality file is saved at the end of the grid generation. If the new project has not yet been
saved before launching the 3D generation, no grid quality report file will be saved because the system
is not able to determine automatically the file location.
Template files
The files when saving the template contain the parameters and the geometry needed to reproduced
the mesh with AutoGrid5™:
l new_prefix.geomTurbo and new_prefix.geomTurbo.xmt_txt: the geometry files (geomTurbo
format)
l new_prefix.trb: the template file containing the grid generation parameters.
l new_prefix.info: the information file
l new_prefix_b2b.png: a picture of the blade to blade view only available on LINUX
l new_prefix_merid.png: a picture of the meridional view only available on LINUX
Outline
Conventions
Some conventions are used to ease information access throughout this guide:
l Commands to type in are in italic.
l Keys to press are in italic and surrounded by <> (e.g.: press <Ctrl>).
l Names of menu, sub-menu items and names of buttons in dialog boxes are in bold.
l Numbered sentences are steps to follow to complete a task. Sentences that follow a step and
are preceded with a dot (•) are substeps; they describe in detail how to accomplish the step.
When using AutoGrid5™ for first time it is necessary that AutoGrid5™ is properly installed
according to the installation note. The installation note provided with the installation software
should be read carefully and the following points are specifically important:
l Hardware and operating system requirements should be verified to see whether the chosen
machine is supported.
l Installation of AutoGrid5™ according to the described procedure in a directory chosen by the
user and referenced in the installation note as 'NUMECA_INSTALLATION_DIRECTORY'.
l A license should be requested that allows for the use of AutoGrid5™ and the desired
component and modules (see Required Licenses for all available licenses). The license should
be installed according to the described procedure in the installation note.
l Each user willing to use AutoGrid5™ or any other NUMECA software must perform a user
configuration as described in the installation note.
When these points are checked the software can be started as described in the installation note or
section How to Start AutoGrid5™ Interface of this users guide.
A. Graphics Driver
The graphics area of AutoGrid5™ interface uses by default an OPENGL driver that takes
advantage of the available graphics card. When the activation of OPENGL is source of issues,
AutoGrid5™ uses an X11 or OPENGL2 driver (on Linux) or MSW driver (for Windows)
instead.
On Linux
l Log in as Administrator.
l Launch regedit from the Start/Run menu.
l Go to the HKEY_ LOCAL_ MACHINE/SOFTWARE/NUMECA International/Fine# or
AutoGrid# register.
l Modify the DRIVER entry to either OPENGL or MSW.
The selection will take effect at the next session.
The driver used in AutoGrid5™ when launched alone can be controlled in the File/Preferences
menu in the Graphics page.
The selection will take effect at the next session.
The background and foreground colors of the graphics area can be adapted through
File/Preferences menu available within IGG™ in the Colors page.
On Linux
On Windows
The standard license for AutoGrid5™ allows for the use of all basic features of AutoGrid5™
including:
l CAD importation and geometry management (except CATIA V5),
l single row and multistage management,
l skin, HOH and H&I blade-to-blade topology management,
l mesh wizard (except for wind turbine and propeller),
l introduction of blade to blade cut,
l no meridional technological effect,
l no 3D technological effect,
Additional Licenses
Within AutoGrid5™ the following features are available that require a separate license:
l CATIA V5 importation,
l introduction of bypass configuration,
l introduction of meridional technological effect,
l wind turbine and propeller mesh wizard,
l introduction of 3D technological effect,
l introduction of solid mesh, cooling channel, holes, pin fins and ribs.
l introduction of an acoustic surface trace.
Next to AutoGrid5™ other products are available that require a separate license:
l FINE™/Turbo (structured mesh generator - solver - visualization software),
l FINE™/Design3D (3D inverse design),
l HEXPRESS™ (unstructured mesh generator),
l HEXPRESS™/Hybrid (unstructured mesh generator),
l FINE™/Open (unstructured mesh generator - solver - visualization software),
l FINE™/Marine (unstructured mesh generator - solver - visualization software).
When launching AutoGrid5™ as described in chapter Getting Started the interface appears in its
default layout ( Basic Mode ) as shown in FIGURE 2.1. Two user modes Basic Mode /Expert Mode
are available and accessible in the toolbar ( User Mode ).
FIGURE 2.1
AutoGrid5™ Basic Mode Interface
The Basic Mode GUI will give access to a simplified graphical user interface. For most projects the
available parameters in the Basic Mode are sufficient. When selecting Expert Mode ( FIGURE 2.2),
the user will have access to all parameters presented in the Expert Mode GUI section and in Chapters
5 to 12. These parameters may be useful in some more complex projects.
FIGURE 2.2
AutoGrid5™ Expert Mode Interface.
Together with the AutoGrid5™ interface, a Open Turbo Project Wizard window is opened, which
allows to open an existing project. See Open Existing Template/Project for description of this
window.
A File Chooser window is available for browsing through the file system and to select a file. More
detail is given on the File Chooser section.
In this section
2.1 Project Selection 18
2.2 Basic Mode GUI 21
2.3 Expert Mode GUI 73
2.4 File Chooser 156
Together with the AutoGrid5™ interface, a Open Turbo Project Wizard window is opened,
which allows to open an existing template with or without the corresponding mesh. See Open
Existing Template/Project for description of this window. After use of this window it is closed.
To create or open a template or a project is also possible using the File menu.
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 two
or four possibilities in respectively Basic Mode or Expert Mode:
l to start a new project presenting no bypass and no cascade configuration from scratch.
l to start a new project presenting a bypass (if license key) from scratch only in Expert
Mode.
l to start a new project presenting a cascade configuration from scratch only in Expert
Mode.
l to initialize a new project from an existing ".geomTurbo" file. Then a File Chooser
window is available for browsing through the file system and to select a file. When clicking
on OK (Open) the geometry is loaded in AutoGrid5™.
If the Open Turbo Project Wizard window is closed, select File/Open Project. A new window
will appear, which allows to confirm. Click yes to confirm.
To open an existing project the following possibilities are available in the Open Turbo Project
Wizard window:
l Click on the icon Select a Project File. A File Chooser will appear that allows to browse to
the location of the existing template. Automatically the filter in the File Chooser is set to
display only the files with extension ".trb", the default extension for a template file. If the
option Load Mesh is active, the corresponding mesh will also be loaded.
l Select a Project in the List by left clicking on it, this list contains all projects available in the
local 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 template
click 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.
FIGURE 2.3
AutoGrid5™ Graphical User Interface (Basic Mode)
An overview of the complete layout and all items in the AutoGrid5™ Basic Mode interface are
described in more detail.
The menu bar contains a part of available options of AutoGrid5™. Menu items can be activated
using click and drag or click and release modes.
Open Project
The menu item File/Open Project allows to open an existing AutoGrid5™ project. When
clicking on File/Open Project a new window will appear, which allows to confirm. Click yes to
confirm and to open the Open Turbo Project Wizard window presented in Open Existing
Template/Project.
New Project
The menu item File/New Project allows to create a new AutoGrid5™ project. When clicking on
File/New Project a new window will appear, which allows to confirm. Click yes to confirm and
to open the project initialization window presented in Create New Template/Project section.
The File/Save Project or File/Save Project As menu item stores the project file (template and
mesh) on disk. When clicking on File/Save Project As a new window will appear, which allows
to:
l Save the project (template and grid) under a new name when clicking on the icon Select a new
Project File Name.
l Save the project (template and grid) under an existing name selected in the list when clicking
on the icon Overwrite the Selected Project.
l Add information to the project in the Enter Project Info area.
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
window will appear, which allows to:
l Save the template under a new name when clicking on the icon Select a new Template File
Name.
l Save the template under an existing name selected in the list when clicking on the icon
Overwrite the Selected Template.
l Add information to the project in the Enter Template Info area.
Quit
File/Quit is used to end the interactive session. A dialog box is inserted to confirm the end of the
session. Please notice that the current work is NOT automatically saved when exiting
AutoGrid5™.
B. View Menu
Patch Viewer
View/Patch Viewer... is used to visualize selected patches in wireframe or solid mode to produce
full rendered pictures of the grid. The dialog box provides control over the colour and
transparency effects for each patch.
Patch Browser
The patch browser (see FIGURE 2.4) 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:
l While holding the <Ctrl> key down, select the desired patches in the browser.
l While holding the <Shift> key down, select two patches delimiting a range of patches.
l While pressing the left mouse button, drag the mouse and release the left button to select a
range of patches.
Filters
The different filters allow to display specific patches of a grid in the browser while hiding the
others. The Block, Face and Patch filters work together and allow to display patches by indices.
For example:
Block Filter: '*'
Face filter: '1 2'
Patch filter: '*'
shows in the browser all the patches of faces 1 and 2 of all the blocks. '*' means ALL. The Face
filter allows also to select a boundary face by choosing imin, imax, jmin, jmax, kmin or kmax.
These items 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).
In particular 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
Sweep Surfaces
View/Sweep Surfaces... is used to scroll the constant grid index surfaces within 3D grid blocks.
If the active block is not generated or has been modified since the last generation (by moving a
vertex, for example), the following message will appear:
It asks for block regeneration. If the block is not generated and that the no button is pressed, the
dialog box of the next figure will appear but without being able to do something except pressing the
Close button. If the block has been modified since the last generation (a block is not automatically
regenerated after modifications of its topology) and that the no button is pressed, the mesh that will
be interactively displayed may look quite strange.
FIGURE 2.6
Sweep Surfaces dialog box.
The Block box allows to choose the active block in which the surface grids will be scrolled. Next
to this box, the active block name and the amount of grid points in each direction (according to
the coarse grid levels selected) are displayed.
It is to be noticed that setting the Block to 0 allows to scroll the grid surface on all blocks.
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.
View/Coarse Grid is used to view in the meridional, blade to blade and 3D views the selected
coarse grid level in the active view. When selecting the menu, a dialog box allows to impose the
Coarse Grid Level to plot.
FIGURE 2.7
Coarse level viewer
In the meridional and blade to blade views, the option is available when respectively the flow
paths and 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
description) to Block or Grid mode. The active coarse grid levels are taken into consideration
while:
l displaying the block faces and boundary conditions patches on all active views,
l saving the block or face coordinates,
l scrolling the block surface grids or cells.
These graphical representations are automatically updated after each change to the coarse grid
levels.
The finest grid level is identified as 1. The smallest number of grid points for coarse levels is 2.
The coarsest level is computed and updated in each index direction separately. The keyboard
input area is used to enter the desired levels within available ranges.
View/Repetition... opens the following dialog box to control the repetition of the blocks on the
active view (in 3D and blade-to-blade views only):
FIGURE 2.8
View Repetition dialog box
For each block, the number of repetition desired can be set in the Nb Repet entry. The repetition
of all blocks can be displayed or hidden respectively by pressing the Show or Hide button.
To perform a repetition, AutoGrid5™ takes the information about the periodicity of each block
(angle, rotation axis,...) in the Grid/Periodicity dialog box (menu available in Expert Mode). By
default, the repetition is not displayed.
Face Displacement
View/Face Displacement menu allows to adapt the view if interferences are appearing between
the grid lines and the shading.
When the block face grids are visualized, in both wireframe and solid modes (shading), visual
interference 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 which
the grid is shifted along the view plane normal vector (normal to the screen), and is used to correct
the 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.
View/view 3D Solid Mesh and View/hide 3D Solid Mesh are used to respectively show or hide
in the 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.
View/toggle 3D Solid View is used as a toggle to show shaded view of the complete hub and
single blade on each of the rows of the turbomachine in the 3D view.
In Expert Mode , the number of blades in the graphics area can be repeated for each row
individually using the Number Of Graphics Repetition parameter available in the Row
Properties dialog box. Activate the Default option to see a complete view of all the blades of the
selected row.
C. Grid Menu
The Grid menu includes the connectivity and boundary conditions definitions, as well as the grid
quality tools.
Boundary Conditions
Grid/Boundary Conditions... menu item allows to check or to serve three different purposes
performed 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:
The patch browser lists all the patches in the grid, according to the current " Block", " Face",
"Patch", "Type", "Nb levels" or "Name" filters. In this browser, a patch can be selected with the
left mouse button. This patch is automatically visualized in the graphics area according to the
visualization options in the dialog box:
l Show Grid will display the grid of the patch.
l 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.
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 a
range of patches.
The last patch selected is always the ’current patch’ for manual connections and patch editing.
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. For
example:
Block Filter: ’*’ (’*’ means ALL)
An option menu allows the setting of the boundary condition type for the selected patch(es). The
possible boundary condition types are the following:
l UND : undefined type.
l INL : inlet.
l OUT : outlet.
l EXT : external. Used to impose farfield conditions.
l SOL : solid. Used for walls.
l SNG : singular. Used for patch degenerated into a line.
l MIR : mirror. Used to impose a symmetry plane.
l ROT : rotating. Used for rotor-stator interaction.
l CON : matching connection.
l NMB : non matching connection.
l PER : periodic matching connection.
l PERNM : periodic non matching connection.
The following types can be set manually: INL, OUT, EXT, SOL, SNG, ROT, MIR. To set such
a type, left-press on the Set Patch Type button of the dialog box; a list with all the types that can
be set manually appears. Move the cursor to the desired type and release the left button to set it to
the selected patch(es).
If a patch is involved in a full non matching connection, a "*" will appear next to the patch type.
The patch definition mode is enabled by pressing the Edit Patch >> button. The dialog box is
then enlarged to show a symbolic definition of the current face, as shown in the next figure.
In this example the active face has three patches with a topology indicated in the figure. The
current patch is represented in yellow.
The current patch can be changed by clicking with the left mouse button within the rectangle
corresponding to the desired patch. The current patch is automatically updated in the browser and
in the graphics area.
An information area is used to display information about the current patch (limits, indices and
relative orientation of the connected patch if existing, and patch type). See Manual Connectivity
Settings section for information about the relative orientation.
The patch definition mode is disabled by pressing the "<<" button.
Automatic connectivity search allows to perform connections between patches (matching and non
matching, periodic or not).
For periodic connections, the block periodicity must be set previously by using the
Grid/Periodicity... menu item.
To make a new automatic connectivity search on all the patches, left-click on the Delete All
button to delete all connections currently set. To delete only some connections, select the
corresponding patches 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
units in 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. The default value that is set at the dialog box opening is 1e-5.
The search can be started by clicking on the Search button. At the end of the operation, the
number of simple connections found as well as the number of periodic connections are displayed
in the information area. The " Type" filter is automatically set to CON and the corresponding
patches are listed in the Patch browser.
It is advised to do this search operation after all the blocks have been properly defined and are ready
to be used by the solver.
When automatic connectivity search fails, the manual connectivity option can be activated by
pressing the Manual... button. Within this option, the relative orientation of the two selected
patches must be entered manually and checks are performed according to the connection type
selected to detect if the connection is possible or not.
This option opens a dialog box shown below:
FIGURE 2.10
Manual Connectivity dialog box
Firstly, specify the indices of the patch that will be connected to the current patch and the
connection type. Patch indices are defined as follows: Block, Face and Patch index. Enter them
with the keyboard and validate them by pressing <Enter>.
Secondly, the correct relative orientation of the two patches must be chosen. To define this, a
reference 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 relative orientation will be different.
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,
while Patch 1 axis J increasing corresponds to Patch 2 axis I increasing. The correct relative
orientation specification should consequently be: "Klow", "Ihigh".
After pressing " Apply " , AutoGrid5™ checks whether the connection is possible or not. A
warning appears if the connection cannot be set.
This type of connection allows to connect several patches of several blocks with non matching
boundaries. The definition of such connection consists of the following:
l A connection name.
l A list of "left" patches defining one side of the connection.
l 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.
FIGURE 2.11
Full Non Matching Connections dialog box
The process of the computation involves that one side of the connection is triangulated whereas
the other 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,
therefore to be taken into account they must be set before creating the connection or the button
Create/update must be pressed once a parameter is modified.
ADT algorithm: to use the new projection algorithm based on the use of the Alternating Digital
Trees (ADT). The main advantage of this method is a decrease of the time required by the
projection stage.
Reverse triangulated side: to reverse the triangulated side which is by default the one containing
the greater number of points.
Maximum projection distance: when the projection distance of a point is greater than this value,
it is rejected.
Minimum projection distance: when all the points of a patch (contained in the projected side of
the connection) have a projection distance greater than this value, the patch projection is rejected.
Normals smoothing steps: before projection, some smoothing steps are done on the projection
normals.
Edge attraction: after the triangulation process, while projecting the vertices on both the sides of
the FNMB, sometimes the projections end close to some boundary of the triangles, which impacts
negatively on the robustness of the treatment. The edge attraction tolerance removes this impact
and forces the projected point to belong to the triangle boundaries whenever necessary.
Rotor/Stator Connections
The tool is available when Save CGNS patch info / family name control option is active in the
Autogrid Preferences dialog box (Preferences). This type of connection allows to connect
several patches of several blocks with rotor/stator boundaries. The definition of such connection
consists of the following:
l A connection name.
l A list of "left" patches defining one side of the connection.
l 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 this tool is only required to have a grouping of patches in several output
formats, including the ".cgns" format, and only when saving from IGG™ but not from AutoGrid5™.
Family Names
The tool is available when Save CGNS patch info / family name control option is active in the
Autogrid Preferencesdialog box (Preferences). The tool allows to impose user-defined family
names on selected patches. To define user-defined family names:
l Select patch(es) in the list,
l Type user-defined family name under Set Family Name and <Enter>.
The specified family names are only saved to have a grouping of patches in several output formats,
including the ".cgns" format, for external solver and are not read when reading a project. Therefore, if
a project is read and directly saved, the specified family names will disappear.
Grid Quality
This item gives access to a tool for performing an analysis of the flow paths quality (if meridional
view active), of the grid quality of the blade-to-blade mesh (if blade-to-blade view active) and on
the final 3D mesh generated (if 3D view active). The following dialog box will appear:
FIGURE 2.13
Mesh Quality dialog box
This dialog box contains two or three pages, one dedicated to analyze the grid quality on all block
cells (inside the blocks and not between the blocks), and the second to the grid quality at the block
boundaries (boundary faces), including matching connections with adjacent blocks. The items for
both pages are similar and described here after. The quality criteria are just slightly different. The
last page (FNMB) only available for the 3D mesh 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
analyzed. It is selected by respectively its name or its number. Each change must be validated by
pressing <Enter> to recompute the quality checking.
FIGURE 2.14
Message indicating that the block may be regenerated
It asks for block regeneration. If the no button is pressed, the quality analysis is not performed.
The next entry Butterfly block is a special item dedicated to butterfly topologies allowing to
choose the butterfly block in which the quality will be checked. When the block selected in the
first entry is a parent 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 buffer blocks. 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
the block cells quality. The criterion is chosen through the Type pull-down menu. According to
the criterion, a preferential direction can be chosen through the second pull-down menu Direction
(only for Block page in 3D view). It is used when the criterion gives different results along
different directions (for example 2D criterion 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 by pressing <Enter>.
The Display frame is used to show in the AutoGrid5™ graphics area the cells falling inside the
quality criterion range. The Display all cells (All cells) button shows all the bad quality cells of the
selected block(s). The Sweep cells scrollers, only available in 3D view, allow to sweep the
selected block 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 AutoGrid5™ graphics area.
FIGURE 2.15
Quality analysis histogram
These criteria are dedicated to evaluate the grid quality on whole cells of a block.
l Criterion class
Two classes can be defined according to the type of cell on which criterion is applied:
l 2D criteria: application on surfacic cells (quadrilateral cells)
l 3D criteria: application on volumic cells (hexahedral cells)
Obviously, the number of cells falling in the criterion range is always greater for a 2D criterion
than for the equivalent 3D one because an hexahedral cell contains six quadrilateral cells. This
means that, for a 2D criterion, the number of cells falling in the range can easily be greater than
the block number of points.
On the other hand, as 2D criteria are applied on surfacic cells, they are all direction dependent.
l Criteria definition
Following criteria are available:
l Overlap,
l Orthogonality,
l Angular Deviation,
l Aspect Ratio,
l Expansion Ratio,
l 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.
Angular deviation
3D criterion available in 3D view. Range: 0 - 180 degrees. Angular deviation is a measure of the
angular variation between two adjacent cells in I, J and K directions.
FIGURE 2.16
Angular deviation definition
Aspect ratio
2D criterion available in blade-to-blade and 3D views. Range: 1 - 50,000. If the calculated value
is outside the range, the value is reset to 50,000.3
FIGURE 2.17
Aspect Ratio definition
FIGURE 2.18
Expansion Ratio definition
Cell width
3D criterion available in 3D view. Range: 0 - 1,000,000. Cell width is the height of the cell
measured along I, J and K directions. If the calculated value is outside the range, the value is reset
to 1,000,000.
These criteria are dedicated to evaluate the grid quality at the boundaries of a block (boundary
faces), including matching connections with adjacent blocks (only CON and PER boundary faces
are considered).
Following criteria are available:
l Orthogonality (available in blade-to-blade and 3D views),
l Angular Deviation (available in blade-to-blade and 3D views),
l Expansion Ratio (available in meridional, blade-to-blade and 3D views),
l Cell Width (available in 3D view),
l Cell Width at Wall (available in 3D view).
Each one is described here below.
FIGURE 2.19
Orthogonality definition
Angular deviation
Range: 0 - 90 degrees. Angular deviation is a measure of the angular variation between two
adjacent cells, the first one being in the current block and the adjacent one in the matching
connected block. Obviously, this criterion is nonsense if there is no matching connected block.
FIGURE 2.20
Angular deviation definition
Expansion ratio
Range: 1 - 100. Expansion Ratio is a measure of the size variation between two adjacent cells, the
first one being in the current block and the adjacent one in the matching connected block.
Obviously, this criterion is nonsense if there is no matching connected block. The definition is the
same as for the Block page (see before).
As the criterion is applied on all solid patches, it will also be applied on solid patches of FNMB
connections, even if there are not real walls (e.g. periodic FNMB streamwise connection inside a ZR
effect or periodic FNMB connection of a row).
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 quality.
Expansion Ratio
Range: 1 - 100. This computes the expansion ratio perpendicularly and through the FNMB for
each cell involved in the FNMB connection. This criterion is symmetric, which means the result is
the same on the left and right parts of the FNMB.
For this criteria the lower values are not too important, it is more the maximum value that should
be considered. Really small values (~1e-5) can easily happen on the boundaries (due to the
difference of mesh discretization even a value 0 as in the above example for cell 2 that is not
crossing cell A.
Inner Gap
Range: 0 - 1e6. This computes the gap between the left and right side of the FNMB (absolute
distance). It is available for each cell involved in the FNMB connection. This criterion is
symmetric.
A mesh quality report can be displayed with the top menu item Grid/Grid Quality Report. It
includes the characteristics of the mesh in terms of minimum and maximum of the expansion ratio,
the expansion ratio and the angular deviation along spanwise direction (J), the aspect ratio and the
cells skewness (orthogonality). These data are available for the entire mesh or by configurations
entity (row, technological effect, bulb).
FIGURE 2.21
3D grid generation and quality check
Negative cells are detected and indicated on top of the histogram as well as the blocks where there
are located at the bottom of the histogram. The number of multigrid levels of each entity (row and
technological effects) is listed in the Nb levels column.
If the spanwise angular deviation exceeds 40 degrees, a warning appears at the bottom of the
window that indicates the blocks where the maximum value has been reached.
Negative Cells
Grid/Negative cells... is used to compute, store the indices and show the cells with a negative
volume. The following dialog box is provided to select calculation preferences:
The View neg cells button allows to visualize cells with negative volume. The computation of the
negative volumes is performed automatically as a first step. Cells with negative volumes are
displayed in a shaded representation and with markers, which are useful to detect cells that cannot
be seen only with the shaded representation.
Beware that the visualization of negative cells can be memory consuming when a large number of
cells must be displayed. It is then advised to first check the number of negative cells by pressing the
Apply button.
If no cell with negative volume is detected, the message " No negative cells" appears. On the
contrary, if there are cells with negative volumes after the complete search, a message like the
following will appear:
FIGURE 2.24
Grid contains cells with negative volume
It shows the number of each block containing negative cells and the corresponding number of
negative cells.
For butterfly topologies, the calculation is performed on all the butterfly blocks of the
corresponding parent block. The number of negative cells of each butterfly block is added and
displayed in the previous dialog box by referencing the parent block.
D. Tools Menu
The Tools menu includes tools to measure distance or angle in the graphics area.
Tools/Distance is useful to measure the distance between two points or between a point and a
line. The following dialog box will appear, showing the distances computed along principal
directions between the two points:
Angle
Tools/Angle is useful to measure the angle between two points projected in a specified plane.
The following prompt appears, asking to enter the origin of the angle (origin of the plane):
Enter origin (o = (0,0,0))
The origin can be specified in the keyboard input area or by left-clicking in graphics area (with
attraction on curves, surfaces and edges) or with the shortcut <o> to impose the origin at (0,0,0).
Once the origin is specified, a second prompt appears asking to enter the plane normal:
Enter normal (<1> = view plane normal; <x>,<y> or <z> to select axis)
The plane normal can be specified in the keyboard input area or by left-clicking in graphics area
(with attraction on curves, surfaces and edges) or with the shortcuts <x>, <y> or <z> to impose
normal respectively along X, Y or Z.
The following prompt appears, asking to enter the first point:
Enter start point
The point can be specified in the keyboard input area or by left-clicking in graphics area (with
attraction on curves, surfaces and edges).
Once the first point is entered, a last prompt appears, asking to enter the second point:
Enter end point
The point can be specified in the keyboard input area or by left-clicking in graphics area (with
attraction on curves, surfaces and edges).
The resulting angle is displayed in the graphics area and in the information area. The angle is
expressed in degrees in the range [0,180] and with a sign according to the normal direction (+
sign if moving first point on second point leads to a crossproduct of same direction as normal).
The toolbar contains icons and buttons providing fast input/output options (See in the related
chapters the complete description of the icon functions). These are divided into 6 sections.
FIGURE 2.25
Top toolbar
User Mode
By clicking on the arrow at the right the user may select the user mode.
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
Closes the current project and opens a new empty one.
See the File/New Project
Saves the current work in the files of the current project.
See the File/Save Project
These buttons are used to start the mesh wizard or the 3D mesh generation.
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
These icons are related to view management and the mesh quality analysis.
Icon Description
Open the Mesh Quality dialog box of AutoGrid5™.
See the Grid/Grid Quality
Open the Grid Quality Check dialog box of AutoGrid5™.
See the Grid/Grid Quality Report
Open the Negative Cells dialog box of AutoGrid5™.
See the Grid/Negative Cells
Open the Patch Selector dialog box of AutoGrid5™.
See the Grid/Boundary Conditions
Select the grid level used by AutoGrid5™ to visualize the mesh.
See the View/Coarse Grid
Open the Sweep Surface dialog box of AutoGrid5™.
See the View/Sweep Surface
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
Visualize or hide the solid model of the machine in the 3D view.
See the View/toggle 3D Solid View
Set the active view in full display mode.
These icons allow to set any view in full display mode or to reset the display mode to multiview.
Icon Description
Set meridional view in full display mode.
The copy/paste wizard settings icons allow the user to apply same row wizard options from one
row to others. It is especially dedicated for multistage machine with several rows of same type
(i.e. axial compressor or axial turbine).
Icon Description
Copy the selected row wizard options into a buffer.
The Quick Access Pad is located in the left part of the GUI. It contains icons and more evolved
options providing a fast access to the more used functions of AutoGrid5™. Some of these
functions are only accessible through the Quick Access Pad whereas others are also accessible
through the menu 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:
l Rows Definition subpad
l Geometry Definition subpad
l Mesh Control subpad
l View subpad
All the commands and options accessible with these subpads are described in detail in this section.
The rows definition subpad is used to control the machine configuration through project
management buttons and a tree. In the rows definition tree subpad, the user can access following
options:
l Select all the rows
l Define new rows
l Define or remove new blade(s) through the row contextual menu (right-click)
l Define and control the blade geometry through the blade contextual menu (right-click)
FIGURE 2.27
Contextual popup menus
The mesh control subpad displays the number of mesh points of the selected row(s) and allows to
choose the layer (Active Layer (% span)) on which the user wants to display the blade-to-blade
mesh by pressing the button Update B2B View.
View Subpad
The view control subpad is used to control the display of mesh entities in the blade-to-blade view
and in the 3D view. When clicking in the 3D view or pressing the viewing icon View 3D, the
viewing buttons are associated to the mesh field of application buttons and the Geometry
Definition and Mesh Control subpads are closed.
Message Area
To mesh 3D technological effects, AutoGrid5™ gives access to the structured multiblock grid
generation module IGG™. Some of the options in IGG™ require numerical inputs from the user.
For example, rotating a curve around a given line requires to specify the direction of the line, its
origin and the rotation angle.
The keyboard input area is provided to allow such inputs. When an option requires numerical
inputs, a message is indicated in the Message area. Without leaving the graphics area, the user
can then type the required data. The keystrokes are automatically echoed in the keyboard input
area and the 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
followed by <Enter>.
The Keyboard input area can also be used to select the active block, face, edge or segment.
Simply enter the related indices separated by blanks and press <Enter> to make the corresponding
entity active. This obviously causes the update of the Grid parameters area.
Mouse Coordinates
This area displays the mouse cursor coordinates in the Graphics area. If the cursor is out of it, it
indicates the last cursor position in it.
Information Area
This area gives general informations (about edges, curves,...). For example, when moving a
vertex and attracting it to a curve, the name of that curve is displayed in this area.
During grid generation process, the status of each steps is displayed in this area.
When left- clicking in this area, playing with keyboard arrows or mouse wheel allow to access all
progress content especially to check history of the warnings and find origin of problems.
In addition a pop-up window can also be displayed to control the progress status of all the
generation steps. The window is optional and can be deactivated by toggle the button Show this
next time.
Viewing Buttons
The Viewing buttons are used to perform viewing manipulations on the active view, such as
scrolling, zooming and rotating. The manipulations use the left, middle and right buttons of the
mouse in different ways. The sub-sections below describe the function associated with each
mouse button for each viewing button.
For systems that only accept a mouse with two buttons, the middle mouse button can be emulated for
viewing options by holding the <Ctrl> key with the left mouse button.
During viewing operations, AutoGrid5™ automatically removes from the active view all 'heavy'
graphics representations such as solid model or color shading. This is done to keep a reasonable speed
during rotation, translation or zoom operations. The complete picture is restored after a viewing
operation is finished. A 'full visibility' can be explicitly requested during viewing operations by
calling the Autogrid Preferences dialog box and setting the visibility flag to Full in the Graphics
page.
Coordinate Axis
The coordinate axis button acts as a toggle to display different types of coordinate axis on the
active view using the following mouse buttons:
l Left : press to turn on/off the display of symbolic coordinate axis at the lower right corner of
the view.
l Middle : press to turn on/off the display of scaled coordinate axis for the active view. The
axis surrounds all objects in the view and may not be visible when the view is zoomed in.
l Right : press to turn on/off the display of IJK axis at the origin of the active block (in Block
Viewing Scope) or of all the blocks (in Grid Viewing Scope). (For more information about
the viewing scope, see the View/Grid page of the Quick Access Pad).
Scrolling
This button is used to translate the contents of active view within the plane of graphics window in
the direction specified by the user. Following functions can be performed with the mouse buttons:
l Left: press and drag the left mouse button to indicate the translation direction. The translation
is proportional to the mouse displacement. Release the button when finished.
The translation magnitude is automatically calculated by measuring the distance between the
initial clicked point and the current position of the cursor.
3D Viewing Button
This button allows to perform viewing operations directly in the graphics area. Allowed
operations are 3D rotation, scrolling and zooming.
After having selected the option, move the mouse to the active view, then:
l Press and drag the left mouse button to perform a 3D rotation
l Press and drag the middle mouse button to perform a translation
l Press and drag the middle mouse button, while holding the <Shift> key, to perform a zoom
l To select the centre of rotation, hold the <Shift> key and press the left mouse button on a
geometry curve, a vertex or a surface (even if this one is visualized with a wireframe model).
The centre of rotation is always located in the center of the screen. So, when changing it, the
model is moved according to its new value.
The rotation buttons are used to rotate graphical objects on the active view around the X, Y or Z
axis. The rotations are always performed around the centre of the active view. Following
functions can be performed with the mouse buttons:
l Left : press and drag the left mouse button to the left or to the right. A clockwise or
counterclockwise rotation will be performed, proportional to the mouse displacement. Release
the button when finished.
l Middle : press and drag the middle mouse button to the left or to the right. A continuous
rotation will be performed, clockwise or counterclockwise. Release the button when finished.
Zoom In/Out
Region Zoom
This button allows to specify a rectangular area of the active view that will be fitted to the view
dimensions. After having selected the button,
l Move the mouse to the active view
l Press and drag the left mouse button to select the rectangular region
l Release the button to perform the zoom operation
l These operations can be repeated several times to perform more zooming.
l Press <q> or the right mouse button to quit the option.
Fit Button
The fit button is used to fit the content of the view to the view limits without changing the current
orientation of the camera (which can be interpreted as the user's eyes).
Original Button
The original button is used to fit the content of the view and to give a default orientation to the
camera.
Cutting Plane
The graphics area is the region of the screen dedicated to the display of all graphical objects
created by the system. These graphical objects may be distributed in different windows called
'views' in the AutoGrid5™ terminology.
FIGURE 2.29
Graphics area
Selecting the Full View item display the active view on the entire graphics area. To return to the
multiview environment, right click on the item MultiView.
Full View can also be accessed by double left-clicking in the view. MultiView mode can be
retrieved by pressing <Esc>.
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.30
Symbolic view
The meridional view displays the entities of the machine projected in (z,r) coordinates. This view
is mainly used to create and control the flow paths in each row.
FIGURE 2.31
Meridional 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 (cell
orthogonality) and the distances (expansion ratio and boundary cell width) are kept by the
conformal mapping (x,y,z → dm/r,theta).
The blade to blade view is mainly used to control blade to blade generation of the mesh.
3D View
The 3D view is used to display the solid body of the geometry and the 3D generated mesh, to
check the mesh quality.
The graphical object displayed in the symbolic, meridional and blade to blade view are related to
entities of the configuration tree (row, blade, domain limit, shroud & hub gap). Object under the
mouse are automatically highlighted in yellow indicating that their selection can be operated by
left-click. Right-click displays contextual menus related to the underlying object. To unselect all
objects, left-click on a empty location.
An overview of the complete layout and all items in the AutoGrid5™ Expert Mode interface are
described in more detail.
The menu bar contains a part of available options of AutoGrid5™. Menu items can be activated
using click and drag or click and release modes.
Open Project
New Project
The menu is described in detail in section Save Project / Save Project As.
The menu is described in detail in section Save Template / Save Template As.
The File/Save Grid/Save Grid As Fine 7.4 allows to save the grids generated in the current
version of AutoGrid5™ in a format compatible with IGG™ 5.7 (FINE™/Turbo 7.4).
The File/Save Grid/Save Grid As Fine 8.6 allows to save the grids generated in the current
version of AutoGrid5™ in a format compatible with IGG™ 8.6.
The File/Save Grid/Merge Project Grid menu item allows when dealing with multistage
machine already generated to adapt the ".cgns" file when regenerating one or more rows of the
machine based 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
In addition to the save subproject feature, the menu Save Fluid Domain(s) creates and saves a
subproject named SubProject Fluid containing only the fluid blocks of the project.
The File/Project List/Transfer File List menu item enables to store a library of project files
contained in the project list when selecting File/Open Project.
The File/Project List/Open File List menu item enables to load a library of project files
accessible afterwards through the Project Selection and Template Selection windows
File/Scripts/Edit... opens a dialog box displaying some of the commands performed by the user
when 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 available commands are presented in the Python Script chapter.
The dialog box contains two pull-down menus. File menu allows to open a script in a separate
dialog box and to save the script in a file. Run menu allows to run the script shown in the
window under the current session ("Rerun on top").
File/Scripts/Save All... is used to save the dynamic recording of all commands performed by the
user since the beginning of its session.
File/Script/Re- execute Last can be used to rerun the last script that was run using the
Scripts/Execute... command. This option is most useful when writing own scripts manually to
rapidly test it on the fly.
File/Print/As PostScript is used to dump the graphics area in a true PostScript file. This option
uses true Postscript statements to save the graphics content and can produce compact files when
all graphics entities in AutoGrid5™ consist of lines (i.e. visualization of the grid in wireframe).
When displaying surfaces in solid model, the quality of the saving reduces considerably while the
size of the file can become very large.
File/Print/As Bitmap PostScript is used to dump the graphics area in a bitmap PostScript file. In
this 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 line
mode appear in the graphics area.
File/Export/IGES... menu is used to export geometry entities in the standard IGES format.
The file created in this way can be read back by using the File/Import/IGES Data... menu item.
File/Export/Parasolid... is used to save the selected geometry curves and surfaces into a
Parasolid™ format. It was already automatically done when saving the project for Parasolid™
entities (e.g. from Parasolid™ or CATIA import) but not for SISL entities (e.g. entities manually
created in AutoGrid5™, IGES import). In AutoGrid5™, only wireframe and sheet bodies are
created from a collection of curves and surfaces and no volume model.
File/Export/Geometry Selection... is used to save the selected geometry curves and surfaces into
an ASCII file.
Only the curves and surfaces selected respectively by the Geometry/Select/Curves and by the
Geometry/Select/Surfaces options are saved.
When selected geometry is containing Parasolid™ and/or CATIA V5 entities, a Parasolid™ file will
also be saved in addition of ".dat" file.
File/Export/Geometry Control Points... is used to save the control points of the selected
geometry curves into an ASCII file. It does not save the complete information about the curve
(type, parametrization,...). 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.
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
menu item). A warning is given if the grid has not been created yet. The standard block grid file
format is used and is detailed in IGG™ User Manual - Input & Output Files.
The block range to save must be determined by two points, specified by their IJK coordinates in
the keyboard input area (indices start at 1):
Enter imin jmin kmin (q)
Enter imax jmax kmax (q)
File/Export/Face Coor... is used to save the coordinates of the active face in ASCII format,
according 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 - Input & Output Files.
File/Export/Patch Coor... is used to save the coordinates of the active face patches in ASCII
format, according to the level of coarseness selected for the grid (set by using the View/Coarse
Grid menu item).
The standard face grid file format is used and is detailed in the IGG™ User Manual - Input &
Output Files. One file is created for each patch of the active face and is named automatically by
appending the patch number to the specified file name. The files are written with a ".dat"
extension.
File/Export/Face Boundary Coor... is used to save the active face boundary grid point
coordinates in ASCII format.
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 - Input & Output Files.
The following dialog box is opened to select a file with a ".g" extension and the corresponding
file format.
The following file types can be selected in the File type entry:
l ASCII
l Binary single
l Binary double
l Unformatted single
l Unformatted double
Binary stands for C binary files whereas Unformatted stands for Fortran binary files. Single and
double describe the precision of reals.
Then two radio buttons are provided to select the binary order desired in the output file: little or
big endian. This information must be specified only for binary files (the buttons are deactivated
when ASCII 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.
File/Export/CEDRE... is used to save the mesh in CEDRE native format. It opens a dialog box
including several options to select the blocks to export (list of block IDs, group of blocks, all
blocks or row by row), and an option specifying if these blocks have to be merged in one single
domain.
Non matching connection type is not allowed for export because CEDRE does not support such
connection.
If the block selection contains CON or PER patches and the connected block is not contained in the
list, the export cannot be performed.
When exporting Row by Row , only row meshes are saved and not the zr effect meshes. A zr effect
mesh can be only exported when using other block selection options.
If family names are available (AutoGrid5™ mesh), a mark name is created based on them as
presented below.
l When Family name options/Short name active:
row_name = 'R(<i>)' where i is the row number
blade_name = 'B(<i>)' where i is the blade number
l When Family name options/Short name deactivate and Keep row name deactivate:
row_name = 'ROW(<i>)' where i is the row number
blade_name ='BLADE(<i>)' where i is the blade number
l When Family name options/Short name deactivate and Keep row name active:
row_name = 'row name'
blade_name = 'blade name'
If Family name options/Blade pressure/suction sides active, the Row Blade will be splitted
in two groups, one for the pressure side (<row_name>+"_"+<blade_name>+"_PS") and one for
the suction side (<row_name>+"_"+<blade_name>+"_SS") instead of one family name (<row_
name>+"_"+<blade_name>) to group all blade patches.
File/Export/Fluent... is used to save the mesh in Fluent native format. It will open a file chooser
to select the exported file name and location. A file name with extension ".msh" will be created.
For each patch, a dedicated face section is written in exported file and a boundary condition ID is
assigned. Next table gives the correspondence between AutoGrid5™ patch type and Fluent
boundary condition type:
For patches defining rotor-stator, they will be exported as "pressure-inlet", "pressure-outlet" or "wall"
if their name is respectively containing the keyword "inlet_rotor-stator", "outlet_rotor-stator" or none
of the previous keywords.
It it possible to define a boundary condition name in Fluent format through the use of a dedicated
section. If this section is not defined, when loading the mesh, Fluent will automatically define a
boundary condition name by adding an increment to the boundary condition description, e.g.
"outflow_1" or "fluid_1".
Such section will be created for a patch only if the patch family name is defined. The boundary
condition name will be "familyName_i", "i" being an index incremented each time this family
name is encountered. The family names are defined as presented in previous section
( File/Export/CEDRE... ) and the option Family name options/Short name in the menu
File/Preferences allows to use shorter family names.
A similar section will also be created for each block, specifying if the block is fluid or solid. The
boundary condition name will be "fluid(solid)_blockName".
This way of defining boundary condition names will allow an easy patch/block grouping or merging
in Fluent. Among others as the block name in AutoGrid5™ contains the row name, it allows quite
easily in Fluent to merge all the zones related to a row.
File/Export/CFD++... is used to save the mesh in Metacomp CFD++ solver native format.
Metacomp CFD++ uses unstructured meshes. Therefore, the structured meshes from
IGG™/AutoGrid5™ must be converted, similarly to the existing unstructured outputs to Fluent and
CEDRE formats.
When exporting, the user is asked to give a base name for the output files of the CFD++ format
filtered by the .bin file ending. The name <base name>_<file ending> is then assigned to the
output files except in the following cases:
There are several IDs used to identify nodes, boundary conditions, and cell groups.
l The node ID uniquely identifies each node. It starts with 0 and is given by the position of the
node in the file "nodesin.bin".
l The cell group ID is written if at least one block of the structured grid has a family name.
Then, all cells from blocks with the same family name are assigned the same ID. All cells from
blocks without a family name get a common ID. If no family names are set, the cell group ID
is not written. It starts with 0.
l All patches with the same family name are assigned the same boundary conditions ID. It starts
with 1.
If a patch has a family name, the boundary condition name will be identical otherwise the patch
gets assigned a boundary condition name according to its type, as described in the following table:
PER_ LEFT_ i and PERNM_ LEFT_ i will be used if AutoGrid5™ patch periodic sign is negative,
otherwise respectively PER_RIGHT_i and PERNM_RIGHT_i will be used.
For NMB, the keywords LEFT and RIGHT are arbitrarily set, and their only purpose is to identify the
connected faces.
File/Export/CRUNCH CFD... is used to save the mesh in CRUNCH CFD® solver native
format.
CRUNCH CFD® uses unstructured meshes. Therefore, the structured meshes from
IGG™/AutoGrid5™ must be converted, similarly to the existing unstructured outputs to Fluent,
CEDRE, Metacomp CFD++ or OpenFOAM formats.
When exporting, the user is asked to give a base name for the output file(s) of the CRUNCH
CFD® format filtered by the .precrunch file ending. The name <base name>_ <group
name>.precrunch is then assigned to the output file (e.g. rotor37_row_3.precrunch), except if
there is only one group of blocks in which case the group name is omitted. The group name is set
to the row name containing at least one block of the group. For a tandem row, the group name is
the name of the two rows connected by an underline.
The CRUNCH CFD® output file is an unformatted Fortran file in big endian format and has the
following sections:
Patch family names can be manually created through the Family Name option in the boundary
conditions dialog box (available when the preference Save CGNS patch info / family name
control is active).
The periodic edges of the rotor-stator interface have to be straight radial lines. This can be achieved
by using in AutoGrid5™ the option Frozen Inlet/Outlet Angle in the blade-to-blade control dialog
box.
The axis of rotation is the x axis in the CRUNCH CFD® solver. Therefore, the IGG™/AutoGrid5™
coordinates are automatically rotated via the mapping (x,y,z) -> (z,x,y).
When exporting, the user is asked to give a folder name for the output file(s) of the OpenFOAM
format.
The OpenFOAM mesh consists of five formatted files with predefined names: "boundary",
"faces", "neighbour", "owner" and "points". In addition a "cellZones" file is saved and contains
one cell zone per block family name.
If the grid is including unsplit butterfly blocks, both parent and butterfly blocks will be exported.
Each AutoGrid5™ patch will obtain a separate entry in the "boundary" file. Its name is the patch
family name appended by an index. If the family name is not set, we use the naming convention
from the CFD++ output.
The "inGroups" keyword is used to group patches and use the patch family name as group name. This
option allows easier specification of the boundary/initial conditions which otherwise must be
prescribed patch by patch. It is not available in the extend branch.
If boundary tags should be merged in AutoGrid5™, patch family names can be manually created and
adapted through the Family Name option in the boundary conditions dialog box (available when the
preference Save CGNS patch info / family name control is active).
Each of the following boundary conditions requires a certain set of additional information to be
written to the boundary file.
FNMB connections will not be recognized in OpenFOAM. The original type (usually SOL) of the
patches involved in the FNMB connection will be considered.
A rotor-stator interface must consist of only one patch. In case it consists of several patches, their type
will be set to "patch".
A periodic connection at the rotor-stator interface of a meridional technological effect cannot be read
into OpenFOAM.
When the "checkMesh" utility is run on cyclic patches, it depends on the grid quality whether the
check is successful. If the test is not successful, then the mesh should be modified and in particular the
aspect ratio should be decreased. If this does not help:
l in OpenFOAM v2.4.0 (official branch), it is recommended to change the "matchTolerance"
keyword in the "boundary" file to higher values, or change the type of the boundary condition to
"cyclicAMI".
l in OpenFOAM v3.1 (extend branch), it is recommended to change the type of the boundary
condition to "cyclicGgi" and to set the "bridgeOverlap" parameter to "true".
File/Export/Meridional Mesh... is used to save the meridional mesh in CGNS format. The
export is based on a row selection and only the meridional mesh of the selected rows will be
exported. The faces used to build the row flow paths will be exported. The faces go from inlet to
outlet, without capturing the leading and trailing edges. There can be several blocks per row,
generally one main block and one per gap.
After selecting rows in AutoGrid5™, select the menu to open file-chooser to select the exported
file name and location. The exported CGNS file will only contain the block points coordinates of
the mesh.
Rows meridional mesh does not need to be generated before export, it will be done automatically.
File/Export/B2B Mesh... is used to save the blade-to-blade mesh in CGNS format. The export is
based on a row selection and only the blade-to-blade mesh of the selected rows will be exported
for the selected spanwise layer.
After selecting rows and the spanwise layer (Active Layer (% span)) in AutoGrid5™, select the
menu to open file-chooser to select the exported file name and location. The exported CGNS file
will only contain the block points coordinates of the mesh.
Rows blade-to-blade mesh does not need to be generated before export, it will be done automatically.
The blade- to- blade mesh does not include 3D mesh controls as non- axi treatment, hub/shroud
interpolation, etc.
File/Export/Abaqus... is used to save all the solid blocks to a single Abaqus formatted file.
Only solid blocks are considered. If other blocks should be exported, the block type has to be changed
to solid.
When exporting, the user is asked to give a base name for the output file of the Abaqus format
filtered by the .inp file ending. The name <base name>.inp is then assigned to the output file.
The Abaqus output file consists of:
l the header;
l the nodes definition;
l the elements definition;
l the definition of node sets and surfaces for the specification of the boundary conditions.
The header includes comments on the exported model.
The nodes are identified using a unique number and can be grouped using the NSET keyword
into node sets. The node set ALL contains all nodes of a row.
The boundary conditions are not defined in the exported file, but must be defined later on the
solver side. Separate node sets must be defined for periodic boundaries and fully non matching
boundaries (FNMB) using the NSET keyword. Therefore, a node set is defined per patch family
name. If a patch does not have a family name, it gets assigned a boundary condition name
according to its type (e.g. NMB or SOL appended by an index per patch).
In Abaqus, surfaces are used to apply loads (e.g. pressure) to the mesh. Therefore, we create a
surface per node set using the *SURFACE keyword. For each surface, we give a list of all
elements which possess a face touching the corresponding surface, and the corresponding face
index.
The elements can be assigned to element sets using the ELSET keyword. We create an element
set per block family name. When the export is done through the graphical interface, the element
type is always C3D8. Other element types than C3D8 are available in Abaqus. The
corresponding python command includes an optional argument to change the element type.
The family names are used to define the node sets. When exporting the solid blocks in Abaqus
format:
l for blocks in a hub or a tip wall, the base family name is the row family name appended by _
HUB_WALL or _TIP_WALL. If the short family names option is activated, the suffixes are _
HW and _TW. For all other solid blocks, the base name is the row name appended by the
blade name.
l for the periodic patches, the suffixes _PER1 and _PER2 are appended. All patches connected
to fluid blocks obtain the suffix _ FLUID_ CONNECTION. If the preference Blade
pressure/suction sides is activated, _PS is appended if the patch lies on the blade pressure
side, or _SS if it lies on the blade suction side. For solid patches connected to the hub, _HUB_
CONNECTION is appended, and for those connected to the shroud, _ SHROUD_
CONNECTION. All other solid patches obtain a family name consisting only of the base
name.
l for FNMB connections, the corresponding patches will be named with the name of the FNMB
and the suffixes _LEFT or _RIGHT, depending on which side of the FNMB the patch is. If
the short family names option is activated, the name is set to FNMB_ with an index unique per
FNMB followed by the _LEFT or _RIGHT keyword.
File/Import/IGG Project... is used to merge an existing IGG™ project stored on disk with the
currently opened project. It allows several people working on large projects to perform the
meshing in separate sessions and to merge their work at a later stage.
Prefix
To easily recognize blocks and groups of an imported project from those in the current project, a
prefix 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 block
groups will be automatically prepended with the prefix. For example, if a block being imported is
named "Inlet" and a prefix "stage1" is specified, the name of the block within the current session
will be "stage1#Inlet". Due to limitations in the CGNS format, the length of the prefix should be
limited 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
holds however when an imported block has the same name as a block in the current project. In
that case an underscore will be automatically appended to the name.
Pressing on the Cancel button will cancel the importation of the selected project in AutoGrid5™.
Importation operations
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 in
IGG™ User Manual - Input & Output Files.
When using the option, a file chooser is opened to select files with ".dat" or ".dst" extensions.
Upon acceptance, the entities are automatically stored in the geometry repository and displayed in
the graphical 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 entity
being loaded has the same name as an existing entity in the current session, a dialog box is opened
with different possibilities:
FIGURE 2.36
Importation options dialog box.
Replace:
When using this mode, AutoGrid5™ replaces the existing curve or surface by the one being
imported. At the end of importation, AutoGrid5™ remaps all the vertices and edges lying on the
replaced 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 to
templates 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:
File/Import/External Grid... is used to import inside the current AutoGrid5™ project a block
grid generated either by IGG™/AutoGrid5™ (using File/Export/Block Coor... menu item) or by
another grid generator. A file chooser is opened to select a file with a ".dat" extension. Several file
formats are available:
l Block data file
l Surface data file (2D or 3D wireframe)
l Multiple surface data file (2D or 3D wireframe)
See the IGG™ User Manual - Input & Output Files for a detailed description of the formats.
Upon selection of a valid file, a new block (or several for multiple data files) is created and put at
the end of the list of blocks. For "Surface data file", which represent surfacic meshes, only face 1
of the block is created. For 2D meshes, the z coordinate is set automatically to 0 for all the points.
AutoGrid5™ automatically creates the block topology (edges) by using the boundary grid points
of the block.
File/Import/Face Grid... is used to import and copy a 2D or 3D grid surface to the active face or
to a BC patch on this face. A file chooser is opened to select a file, which must have a ".dat"
extension and have the Surface data file format (see the IGG™ User Manual - Input & Output
Files for more information about this format). The type of surface and the edge creation mode are
indicated from the keyboard input area. If the edges of selected surface are on the boundaries
and the edge creation flag is 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
or on one of its patches. In this case, the following prompt(s) appear:
Surface (=0) or Patch (=1) ? (q)
>> 1
Patch 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 face
boundary grid points:
Create boundary segments (y/n) ?
>> y
The option File/Import/CATIA V5... reads external geometry files in CATIA format up to R26.
Several CATIA files can be opened when defining the geometry.
Whatever the units of the CATIA V5 geometry, it will be automatically converted in meters. For
example a curve of 100 [Millimeter] length will present a length of 0.1 into AutoGrid5™.
CATIA V5 file is read by the DATAKIT cross-CAD library and converted into a Parasolid™ file.
The DATAKIT feature added in the NUMECA license will replace TTF- based libraries, also
maintained to ensure backward compatibility. The TTF library is upgraded to v7.9.0.9 to allow
importation of CATIA V5 files up to R19.
Running Windows 64-bits, an additional Windows security patch is required to enable CATIA V5
import with Datakit. For more details, link to http://www.microsoft.com/
downloads/details.aspx?dispalylang=en&FamilyID=766a6af7-ec73-40ff-b072-9112bab119c2.
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
geometry.
A geometry can be correctly represented only if it is fully included in a cube between the points (-
500,-500,-500) and (500,500,500) due to the Parasolid™ library limitation.
File/Import/IGES... menu is used to import CAD data stored in the standard IGES format. When
names are defined for entities the IGES file, AutoGrid5™ uses them for the new entities created
in the repository. When these names are already used by existing entities, a dialog box is opened
to resolve the conflict. See the menu option File/Import/IGG Data... for details about the dialog
box.
This option provides a powerful browser to scan the content of an IGES file and selectively
import IGES entities recognized by AutoGrid5™. In the case of composite curves and surfaces,
the browser 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
corresponds to a criterion defining if entities with the corresponding attribute set accordingly will
be displayed in the browser/imported.
It might be useful to uncheck the Blank Filter/Blanked item in order to import only the entities
meant to be visible and get a clear view of the intended geometry. The same holds for the Entity
Use Filter with only the geometry item checked.
FIGURE 2.37
IGES file browser
See the IGES reference manual for a complete understanding of all filter values. The list of
available IGES entities that can be imported in AutoGrid5™ are presented in the next table.
When units are imposed in the IGES file, these are purely informative and will not be used by
AutoGrid5™.
File/Import/PLOT3D... is used to import inside the current AutoGrid5™ project block (s)
generated either by IGG™/AutoGrid5™ (using File/Export/PLOT3D... menu item) or by
another grid generator. The imported file must have a ".g" extension and have the PLOT3D file
format, as described in IGG™ User Manual - Input & Output Files.
FIGURE 2.38
Input file and file format selection
The following file types can be selected in the File type entry:
l ASCII
l Binary single
l Binary double
l Unformatted single
l Unformatted double
Binary stands for C binary files whereas Unformatted stands for Fortran binary files. Single and
double describe the precision of reals.
Then three buttons are provided to select the remaining file specifications. These ones must be
specified only for binary files (the buttons are deactivated when ASCII type is selected). The two
first radio buttons allow to select the binary order in the file: little or big ending. The last button
specifies 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 the
current list of blocks. AutoGrid5™ automatically creates the block topology by using the block
coordinates.
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
to exchange meshes and boundary conditions between heterogeneous systems. Block coordinates
and boundary conditions are read from the ".cgns" file. Only connections of type CON can be
read and performed automatically by AutoGrid5™.
It is to be noticed that a CGNS file is automatically created during the saving of a project, using
the File/Save options. This file can be reread by AutoGrid5™ using this option or exchanged
with other CGNS compliant systems.
The imported file must have a ".cgns" extension and must be a valid CGNS format, as described
in IGG™ User Manual - Input & Output Files.
A file chooser is opened to select a file with a ".cgns" extension. Upon selection of a valid file,
the blocks 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.
File/Import/GridPro... is used to import inside the current AutoGrid5™ project block(s) created
by the GridPro grid generator.
A file chooser is opened to select a GridPro file. Upon selection of a valid file, the blocks of the
imported file are created and put at the end of the current list of blocks. A message indicating
what block is read appears in the AutoGrid5™ message area. AutoGrid5™ automatically creates
the block 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 the file and must be specified manually within AutoGrid5™, when required, using the
Grid/Periodicity... and Grid/Boundary Conditions... menu items.
Preferences
The File/Preferences opens a dialog box to control the default settings of AutoGrid5™.
This dialog box contains four 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. When starting AutoGrid5™, this file is read automatically and the
preferences are restored directly. If this file cannot be found, the system is initialized with default
settings.
Import CAD Streamwise Direction is used to specify the preference for streamwise direction
during CAD import.
Number of grid levels is used to define the default number of grid levels (lower or equal to 7) of
the generated mesh when starting a project from scratch.
Number of threads is used to define the default number of processors used when generating the
mesh but also when performing block interpolation, grid quality checks and block negative cells
computation. (New in AutoGrid5™ v12.1)
When no parallel license is available, a warning will appear in the shell ("Warning: no parallel
license available, will run sequentially") and the mesh generation will start in sequential.
Depending on the case, there is no warranty on the scalability, especially on its linearity with the
number of threads (e.g. the multi- threading performances are not optimal when dealing with
Parasolid due to the layers intersection process). It can even occur that increases too much the number
of threads will increase the total generation time (e.g. a lot of threads for a quite small mesh).
Saving Page
Backup when saving (.bak) is used to make a backup of the geometry and topology files at
saving. AutoGrid5™ makes a backup of 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 each
time a project is saved. It includes:
l A calculation of the number of multigrid levels available in the I, J and K directions for the
whole grid.
l A calculation of the negative cells in single and double precision.
l A rough idea of the grid quality (extremum values) in terms of orthogonality, aspect ratio and
expansion ratio.
The results are displayed in a dialog box appearing automatically just after the saving.
CGNS Format/ADF (Compatible with CGNS2) and CGNS Format/HDF5 options are used
to select the format of the CGNS v3 file. The default format is ADF and is compatible with
CGNS v2. (New in AutoGrid5™ v12.1)
When option is active, the Keep row name option has no effect and is considered as not active.
Family name options/Blade pressure/suction sides option allows to create two family names,
one for the pressure side (<row_name>+"_"+<blade_name>+"_PS") and one for the suction side
(<row_ name>+"_ "+<blade_ name>+"_ SS") instead of one family name (<row_ name>+"_
"+<blade_name>) to group all blade patches.
To consider the new preferences, the project should be reloaded or regenerated in AutoGrid5™
To consider the new names of row or blade in the family names after generating the 3D mesh, the
mesh should be regenerated otherwise family names will still contain the previous names.
Graphics Page
The Graphics Driver flag is used to select the driver OPENGL or OPENGL2/X11 (on Linux)
or MSW (on Windows).
When launching AutoGrid5™ from FINE™ (through Modules menu), the graphic driver will be
read from the registry key but when launching AutoGrid5™ alone, the graphic driver will be read
from the preferences.
The Visibility flag is used to control the rendering of graphic objects during dynamic viewing
operations. With full visibility, all graphic objects are displayed during viewing operations, which
may slow down the system response. When partial visibility is selected, only grid boundaries are
displayed during viewing operations.
Turn On Additional Lights option allows to enhance the lightening for shaded representations.
Layout Page
This page allows to control some aspects of the AutoGrid5™ 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. It allows to use a larger part of the screen for better graphics rendering, but cannot be
used during the interactive 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 AutoGrid5™.
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.
Quit
File/Quit is used to end the interactive session. A dialog box is inserted to confirm the end of the
session. Please notice that the current work is NOT automatically saved when exiting
AutoGrid5™.
All menus are described in detail in the dedicated IGG™ User Manual - Geometry Menu. This
menu is only available when selecting the 3D view or when adding a 3D technological effects
For Blade-to-Blade and Meridional views, only the Distance tool is available.
In addition in Meridional view, a tool is available to create an acoustic surface trace (under
licence) to predict within FINE™/Turbo the acoustic response around a turbomachinery
component (more details in FINE™/Turbo User Manual). When selecting the tool, a graphical
interface allows the user to create a curve using the options (Draw CSpline, Draw Polyline,...) in
the Geometry menu, to select (Geometry/Select Curves ) the created curve (highlighted in
yellow) and to assign it as an acoustic surface trace by clicking on button Save Source Trace in
Quick Access Pad and on Close Edit Mode button. A new "project_prefix_permeable_curve.dat"
file is created in the project folder and will be used within acoustic project in FINE™/Turbo
(more details in FINE™/Turbo User Manual).
C. View Menu
The View menu options provide a set of display options to visualize the grid boundaries, surface
and block grids, repetition, hidden lines and rendered surfaces. The viewing parameters and
projection can also be modified interactively.
Patch Viewer
Coarse Grid
Repetition
Face Displacement
View Depth
View/View Depth menu allows to control the view depth. This depth is used for all interactive
geometry editing operations with the mouse.
When using the option, the new depth for the active view is imposed by entering the coordinates
of the reference point:
New reference pt coordinates (q)
>> 0 0 0
All subsequent inputs with the mouse will be at z = 0. To quit this option, enter <q> and press
<Enter>.
View/view 3D Solid Block is used to show in the 3D view the mesh on the solid blocks (shading
and mesh).This option is not a toggle, the View/Patch Viewer... menu has to be used to adapt or
to clean the visualized solid mesh.
View/toggle throughflow mesh is used as a toggle to show the throughflow mesh in the
meridional view. This mesh is used for the initial turbomachinery solution available in FINE™
GUI.
View/Toggle Tool Bar is used as a toggle to show or hide the toolbar presented in Toolbar.
View/Toggle Symbolic View is used as a toggle to show or hide the symbolic view presented in
Symbolic View.
D. Grid Menu
The Grid menu includes the connectivity and boundary conditions definitions, as well as the grid
quality tools.
Periodicity
Grid/Periodicity... menu is used to define the periodicity for each block of the grid to generate. It
can be done in the following dialog box:
The first thing to choose is the Block(s). Four possibilities are available (simply left-click on the
desired one in the box):
1. Active Block. Select only the active block.
2. Selected Block(s). Select the desired blocks by entering with the keyboard their number in the
dedicated box entry. The numbers must be separated by spaces. A range of blocks can also be
selected by entering two numbers separated by a '-'. For example, enter '4 6 10-15' to select the
blocks 4, 6 and the range 10->15. The numbers do not have to be ordered. If a syntax error is
made, a warning message will appear.
3. Block Group. Select all the blocks of the group. To see all the group names and select the
desired one, left-click on the dedicated arrow.
4. All Blocks. Select all blocks of the project.
Next, the type of periodicity which will be applied to the block(s) must be selected. There are four
types available: none, rotation, translation and mirror. Simply left-click on it to select one type.
l None: When no periodicity are needed on block(s).
l Rotation: A rotation periodicity rotates a block around a given axis by a specified angle. The
rotation axis is specified by a rotation axis direction (axis) and an anchor point (origin). The
angle is indirectly specified by indicating the number of periodicity for the block (e.g. a
compressor with 4 blades should have a number of periodic i ties of 4) and the number of
meshed passages is directly specified.
l Translation: A translation periodicity, e.g. a cascade in turbomachinery, is obtained by
specifying 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.
l Mirror: A mirror periodicity mirrors a block with respect to a symmetry plane and is
specified by the origin and normal of the mirror plane.
The dialog box contains also three buttons at the bottom:
l View/Hide Selection: it highlights the selected block(s) in the graphics area.
l Apply: it applies the current settings to the specified block(s).
l Close: it closes the dialog box.
Grid Settings
Grid/Grid Settings... menu is used to examine or modify all important grid parameters of the
segments, edges, faces and blocks of the current project, using a dialog box.
There is no Apply button which implies that the changes in the different input fields take effect
IMMEDIATELY after pressing < Enter > or selecting another field, without any possibility of
automatic undo.
The Family Name field is available when Save CGNS patch info / family name control
option is active in the Autogrid Preferences dialog box.
The specified family names are only saved in ".cgns" file for external solver and are not read
when reading a project. Therefore, if a project is read and directly saved, the specified family
names will disappear in the ".cgns" file.
The family names imposed to butterfly parent block are not transferred to butterfly children.
A domain type can be stamped as a fluid or solid domain using the Type drop down menu.
Fluid or Solid domain type can be specified for the active block. It helps to enhance the
grouping capability as obtained from Grid Configuration page in the View subpad (see View
Subpad for more details). The settings imposed here, will also be transferred automatically to
the FINE™ GUI.
l Face data: The active face index can be specified from the Face box. When changing the
active face index, the edge and segment informations are automatically updated.
l Edge data: The active edge index can be specified from the Edge box. The total number of
segments of the active edge is displayed (it cannot be changed here, it is only for information
purpose).
l Segment data : The active segment index can be specified from the Segment box. The
number of grid points on that segment is displayed next to this area. The low and high limits of
the active segment can be changed with the keyboard from the min and max boxes. Once a
new value is entered, press <Enter> to activate the change. The following constraints must be
respected:
l new lower limit > lower index of the previous segment
l new upper limit < upper index of the next segment
When changing the limits of a segment, the index of the fixed points delimiting it will be
obviously changed. If the new values imply the change of an internal grid line index, it is done
automatically without asking any confirmation. However, if the new values imply the change of
an internal face index, the following message appears:
If the no button is pressed, the index will not be changed and the limit will be reset to the previous
one.
The dialog box also contains at its bottom two buttons: MG Levels and Close buttons. The first
one opens a box containing the table of the MultiGrid levels. It allows to choose a number of grid
points in order to have multigrid meshes. The second one is obviously used to close the dialog
box.
The following considerations have to be taken into account when changing block limits:
1. The minimum number of grid points in one direction is 2, which corresponds to one cell.
2. When changing the number of grid points in the I, J or K direction, the faces and block grids
affected by the modification are deleted. For example, when modifying the number of points in
the K direction, the grids of the faces 3, 4, 5 and 6 are deleted.
3. Connections with patches of the touched faces are also deleted. Moreover, patch boundaries
are resized automatically in order to cover the whole face.
4. Connected segments remain connected, even if there is an inconsistency with the number of
points. It allows to change after the number of points on the connected segment and to keep
the connection. Despite this, if the number of points remains different for the two connected
segments, the connection will be deleted at the next loading of the project.
5. When increasing the number of points in one direction, these points are added to the last
segment of edges aligned on this direction.
6. If a block contains an internal face whose constant direction is the same as the one in which
the number of points has to be decreased, a message appears when the new number of points
is lower than or equal to the internal face index:
It gives the possibility to change the internal face index without leaving the Topology Settings
dialog box. If the no button is pressed, the index will not be changed and the limit will be reset
to the previous one.
FIGURE 2.42
Example of segment division
It will not be possible to reduce Imax below 41, since segment s2 on the figure has its lower
bound equal to 40. To reduce Imax to 30, for instance, the lower limit of segments s1, s2 and s3
must be manually changed below 30 (the last segment must have at least 2 points). The segments
before the last ones may also need to be changed (recall that a segment must have at least two grid
points).
If a bad limit is entered, an error message similar to the following will appear:
It indicates the segment(s) that have to be modified to impose the new block limits. Once the
Close button is pressed, the limits are reset to the previous ones.
FIGURE 2.43
Example of resized block
The distribution of the grid points among the segments of an edge will be proportional to the
overlapping between the segments and the initial resized segment. In the previous example, the
segment s3 does not overlap with the resized segment and consequently its number of points
remains unchanged. Only segments s1 and s2 are affected. The index of the internal edges and
internal faces will be adapted consistently.
Boundary Conditions
Grid Quality
The Grid/Grid Quality Report (HTML) menu (not available on Windows) allows to
automatically write a mesh quality report. When selecting the menu, a window enables to select
the images that will be inserted into the report and provides disk usage necessary for the report
and images.
Grid/Compute All Fnmbs is used to ease the calculation of the full non matching connections by
computing all full non matching connections defined in the menu Grid/Boundary Conditions at
once on all available grid levels. A window appear when full non matchings are failing on
specific grid level(s).
E. Tools Menu
2.3.2 Toolbar
The toolbar contains icons and buttons providing fast input/output options (See in the related
chapters the complete description of the icon functions). These are divided into 6 sections.
User Mode
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
Closes the current project and opens a new empty one.
See the File/New Project
Saves the current work in the files of the current project.
See the File/Save Project
These buttons are used to start the mesh generation with different scope of application.
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
Meridional Control.
Generate the flow paths and the blade to blade mesh of the
selected rows.
See the Generate B2B button description on Blade to
Blade Control.
These icons are related to view management and the mesh quality analysis.
Icon Description
Open the Mesh Quality dialog box of AutoGrid5™.
See the Grid/Grid Quality
Open the Grid Quality Check dialog box of AutoGrid5™.
See the Grid/Grid Quality Report
Open the Negative Cells dialog box of AutoGrid5™.
See the Grid/Negative Cells
Open the Patch Selector dialog box of AutoGrid5™.
See the Grid/Boundary Conditions
Select the grid level used by AutoGrid5™ to visualize the mesh.
See the View/Coarse Grid
Open the Sweep Surface dialog box of AutoGrid5™.
See the View/Sweep Surface
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
Visualize or hide the solid model of the machine in the 3D view.
See the View/toggle 3D Solid View
Set the active view in full display mode.
These icons open dialog boxes use to change the mesh parameters.
Icon Description
Select all the rows of the current project.
Open the dialog box dedicated to the blade to blade topology control.
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 machine with by-pass
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.
Icon Description
Remove the selected row(s) from the project database.
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).
Icon Description
Remove the selected blade(s) from the project database.
Replace the selected blade to blade topology by the topology stored into the current buffer.
Open a file chooser used to select a ".geomTurbo" file which contains the (new) blade geometry.
Icon Description
Remove the selected gap(s) from the project database.
Replace the selected gap(s) topology by the topology stored into the current buffer.
The Quick Access Pad is located in the left part of the GUI. It contains icons and more evolved
options providing a fast access to the more used functions of AutoGrid5™. Some of these
functions are only accessible through the Quick Access Pad whereas others are also accessible
through the menu 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:
l Rows Definition subpad
l Geometry Definition subpad
l Mesh Control subpad
l 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
perform specific function related to the subpad and the page. Each page can also be toggled by a
simple mouse left-click.
The rows definition subpad is used to control the machine configuration through project
management buttons and a tree. All the turbomachinery entities, rows or technological effects
(seal leakage, cooling holes,...) composing a project are symbolically displayed into the tree.
FIGURE 2.46
Row definition subpad
These buttons are used to select or add entities into the tree.
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.
Configuration Tree
The configuration tree is used to navigate through the project configuration, to select and modify
the configuration entities.
FIGURE 2.47
Configuration Tree
The entities of the tree can be managed with the features available through their related quick
access popup menu. After selection, right-click displays these menus. For quick access, they
appears above the mouse location and allows the user to add, remove or modify the properties of
all selected entity.
FIGURE 2.48
Contextual popup menus
The geometry definition subpad contains button and interaction area used to define or modify the
geometry of the configuration entities.
The geometry defining the channel and the blades as well as the technological effects can be
specified from external CAD files and/or from ".geomTurbo" file (native geometry format).
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 upper limit defining the blade
channel from the basic meridional curves
defined in the geometry file.
Start the editing tool used to define the
meridional trace of the nozzle. Available only
if the project has a configuration with bypass.
Open a dialog box to control the number of
control points defining the channel curves used
to define the inlet, outlet, rotor-stator 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 geometry 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
Geometry Definition.
The Units page allows to select the "units" of the imported geometry in order to apply an internal
scaling and tolerance adaptation transparent for the user that will ensure correct treatment during
the grid generation when computing for example the intersection. If the global geometry size is
below 100 it is recommended to keep the default settings (Scale Factor set to 1), otherwise the
value should be adapted to the geometry units.
The mesh control subpad is divided into three pages containing buttons and interaction areas used
to control the mesh of the active row(s). Left click to open or close the desired page.
FIGURE 2.50
Mesh control subpad
In this subpad, the number of points used to mesh the selected entities (rows and technological
effects) is displayed and continuously updated following the modifications of the mesh generation
parameters.
The buttons and the input area of the grid level page are used to set up a default mesh.Four grid
levels are available to define the number of points used to mesh the selected row(s). The button
Initialize Topology & Grid Points Distribution (re)set a new default mesh topology according to
the geometry configuration and the chosen grid level. The button Row Wizard allows to access
the mesh wizard mode in order to mesh the selected row in few steps by defining few parameters
(more details in Geometry Definition).
FIGURE 2.51
Grid level control
When loaded project/template is presenting a number of grid levels different from user preference, a
warning will appear.
The number of grid levels is not respected when using userdefined or HOH B2B topology and when
adding 3D technological effect.
For bypass configuration, the blocks near the nozzle at the rotor/stator interface will respect number
of grid level of the main channel row and not the one of the bypass row if different.
When the number of points becomes very important (e.g. in a gap), the B2B mesh generation
algorithm may fail. Workaround: decrease manually the cell width and/or expansion ratio.
For high staggered topologies, for the inlet (- outlet)Up(- Down) number of points that have to be
projected on the blade, it is not possible to find a location on the blade that ensures a good
orthogonality of the mesh. Workaround: increase manually number of points on blade.
For bulb configuration, to ensure number of grid level in the final 3D mesh, number of grid level +1
should be imposed locally manually.
l to increase the number of points in the streamwise direction respectively at the inlet, on the
blade and the outlet.
The buttons and input area of the row mesh control page are used to control all the grid generation
parameters of the selected row(s).
FIGURE 2.52
Row mesh control
Quick access is given for the main parameter defining the cell width.
Additional buttons give access to several dialog boxes used to control all the expert grid
generation parameters.
Icon Description
Open the flow paths control dialog box.
The input area of the active B2B layer page, is used to change the flow path on which the mesh is
computed and displayed in the blade to blade view.
D. View Subpad
When the blade-to-blade view active, the View subpad contains five buttons allowing viewing
operations on the blade to blade grid. The selected rows define the scope of the 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).
When the 3D view active, the View subpad provides commands and tools that allow viewing
operations on the geometry and the grid. In particular, the three first pages provide options
permitting the creation and the visualization of geometry and block groups. The four pages of this
subpad are described in the following sections.
Geometry groups are powerful means of classifying geometrical entities by grouping them under
the same name. This tool proves to be essential as soon as the input geometry gets a little
complicated. Using groups, the user can easily perform selective visualization of parts of interest
and focus on the current region being meshed.
The geometry group page allows the creation, the deletion and the visualization of geometry
groups, which can contain curves and/or surfaces. Different groups can contain the same curve(s)
or surface(s).
All the existing geometry groups are listed by name in the browser of the page. Each group name
is preceded by two buttons. Left-clicking on the first one toggles the list of curves and surfaces of
the corresponding group in the Quick Access Pad. Left-clicking on the second one toggles the
display of 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 hide
the item.
The page contains four buttons at the bottom:
l Create Group. Before pressing this button, curves and surfaces that will be put in the new
group must be selected (see the Geometry/Select menu in IGG™ User Manual). The
following dialog box will be opened:
Simply enter the new group name and press the Create button to create the new group.
l Delete Group. It opens the following dialog box:
This page allows the creation, deletion and the visualization of block groups. Different groups can
contain the same block(s).
All the existing block groups are listed by name in the browser of the page. Each group name is
preceded by two buttons. Left- clicking on the first one toggles the list of blocks of the
corresponding group in the Quick Access Pad. Left-clicking on the second one toggles the
display of blocks 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 hide
the item.
The page contains four buttons at the bottom:
l Create Group. The following dialog box will open:
Simply enter the new group name and press the Create button to select the group blocks. The
following prompt will appear:
<1> Select a Block, <2> Add to Group, <3> Quit, <Keyboard Area>: Add Block by
Indices to Group
Left-click on a block to select it. The block will be highlighted. Then, middle-click to add the
block to the group. This block will remain highlighted until leaving this tool. Add in the same
manner as many blocks as desired.
Blocks can also be added to the group by entering their number in the keyboard input area. In
this case, the blocks are directly added to the group without being highlighted and without any
validation. The numbers must be separated by spaces. A range of blocks can also be added by
entering two numbers separated by a '-'. For example, enter <1 5 10-15 3><Enter> 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 be entered 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.
l Delete Group. It opens the following dialog box:
All existing block groups are listed in the box. Simply select a group by left-clicking on its
name and press the Delete button to delete it (this will not delete the related blocks).
l Show All. This button shows all the blocks in the graphics area.
l 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
page browser:
FIGURE 2.57
Block group pop-up menus
When creating a mesh with AutoGrid5™, the multiblock data structure can become very
complex. A new database, named Grid Configuration, is created by AutoGrid5™ at the end of
the mesh generation, 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
domains interconnected together through domain interfaces. Each domain contains a set of
subdomains and a set of interfaces. Each domain interface contains a type of boundary condition,
a type of free boundary condition and the possible connected domain reference. The domain
encapsulates the list of structured blocks defining the domain. The domain interface encapsulated
the list of structured patches defining the interface.
This new data structure is very useful. It can be used to reduce the time needed to analyse the
mesh of 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
each 3D generation as well as after loading or saving a project. This configuration is composed by
a tree of domains similar to the configuration tree used to set the template configuration. The Main
Project of an AutoGrid5™ configuration contains a single subdomain named "AG5 <project
name>" where project name is the name of the template. The AutoGrid5™ domain contains the
list of subdomain related to each row and each technological effect 3D.
The menu option Duplicate is used to create an new instance of the Main Project into the
configuration. This new instance is called a SubProject and is a perfect copy of the main project
configuration.
The option Merge can be used to merge together subprojects with the main project. A new
instance of the Main Project is created and if mesh and template files exist on disk for the selected
subproject, new mesh and template files are created for the new merged subproject resulting of the
concatenation of the main project mesh and template files with the subproject mesh and template
files.
Subprojects are useful when part of the main configuration must be analysed separately. In
addition AutoGrid5™ allows also to redefine geometry in a subproject through template
manipulation and remeshing partially the machine. Each subproject can have its own mesh and
template inside which the user can modify locally some part of the geometry (i.e. a blade
definition). Once the computation is fruitful on the subproject a merge process allow the user to
concatenate the main project with the selected subproject to analyse the complete configuration
with the new geometry defined in the subproject.
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 the
name is already used.
Duplicate SubProject
The menu option Duplicate is used to create an new instance of the SubProject into the
configuration.
Save SubProject
The menu item Save is used to save the mesh and the template of the selected subproject. By
default, when a subproject is created from the main project, the mesh and the template files are not
duplicated. Once the subproject editing done, the option Save creates a new directory <main-
project-file-name>_<subproject-name>. The partial mesh and template related to the subproject
are automatically created and stored in this directory.
All the structured patches boundary condition type of the mesh belonging to a domain interface
connected to a subdomain removed in the subproject are switched to the free boundary condition
define in the interface properties. In the next example, the patch type of the RS Connection With
row 1 are switched to Inlet when saving the subproject mesh.
Load SubProject
The menu Load can be used to load the mesh (and the template) of a subproject if the file exists
on disk. If not a warning prompts the user to first save the subproject.
Merge SubProject
The menu Merge can be used to merge together subprojects and/or with the main project. The
figure illustrates the process to merge together the subproject 1 & subproject 2 into a subproject 3.
Delete SubProject
The menu Delete can be used to delete the mesh (and the template) of a subproject if the file
exists on disk.
Domain Management
Each domain edges are automatically highlighted in red in the XYZ view when selected (click-
left) in the configuration.
Each subdomain contains a list of IGG™ blocks. When dealing with butterfly topology created in
IGG™ or as 3D technological effect in AutoGrid5™, the button Update assumes that all the blocks
are now included in the grid configuration except the parent blocks. This is a suitable behavior for the
usage of the grid configuration in the FINE™ GUI.
Domain Properties
The menu Properties opens the dialog box use to control the type and the rotation speed of the
domain.
Rename Domain
Group Domain
The menu Group can be used to group the domain together. The resulting domain contains a list
of subdomains equal to the selected list. This menu is available only in the grid configuration
within IGG™.
Delete Domain
The menu Delete can be used to remove the selected domain from the related main project and/or
from the related subprojects.
Each domain of the main project or a subproject contains domain interfaces defining the physical
boundaries of the configuration and the connections between the domains. These interfaces are
stored in the Domain Boundaries folder of the domain. If the button Highlight Boundaries is
checked, the selected domain interfaces are automatically displayed using grid and color shading
representations as presented in the next figure.
Each subfolder contains a list of interfaces and/or subfolders. The interfaces are given by their full
composite name. The composite name is composed by the name of the tree entity and all its
parents separated by a character "/". The subfolders (i.e. row 1 Connection(Fluid->Fluid)) contain
a list of interfaces. These subfolders represent interfaces groups and are defined for quick access.
These groups are defined automatically by AutoGrid5™ or manually using the features dedicated
to the domain boundary management. These features are available through the right-click menu of
the domain boundaries.
The menu Properties opens a dialog box dedicated to the management of the interfaces
properties.
In the dialog box, the rotation speed, the option to assign acoustic source, the name, the type of
the boundary in the main project (Boundary Condition Type) and in the subproject (Free
Boundary Condition Type) are available.
In a subproject, some domains can be removed by the user. When saving the grid of a subproject,
all the boundary condition type of the domain boundaries connected to the removed domains are
set to the free boundary condition type.
In addition, when the interface selected is a rotor-stator, the side (upstream or downstream) of the
interface can be setup (Rotor/Stator Side).
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
group appears only when at least two boundaries of the same type of a subproject or the main
project are selected.
By default the name of the group is composed by the "type name" + "group id" (i.e. Solid 1). A
new subfolder is automatically displayed in the tree and contains all the selected 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.
3. The Outlet 1 and Inlet 2 are selected than connected together using the menu Connect.
Interface Viewer
The menu Interface Viewer opens a dialog box dedicated to the domain interface visualization. It
allows to select the display of the grid and/or a solid representation of the selected interfaces.
Export Surfaces
The menu Export Surfaces is used to export a IGG™ data file format of the surfaces created as
new wireframe of each patches defining the interface. The file name is defined automatically
using as prefix the name of the configuration file (".config" file) and the name the interface.
This page provides visualization commands on the grid. It consists of two rows: a row of buttons
and a row of icons.
The first row of buttons is used to determine the viewing scope, that is the grid scope on which
the viewing commands provided by the icons of the second row will apply. There are five modes
determining the scope, each one being represented by a button: Segment, Edge, Face, Block,
Grid (all blocks). Only one mode is active at a time and the current mode is highlighted. Simply
left-click on a button to select the desired mode.
l In Segment mode, a viewing operation applies to the active segment only.
l In Edge mode, a viewing operation applies to the active edge only.
l In Face mode, a viewing operation applies to the active face only.
l In Block mode, a viewing operation applies to the active block only.
l 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 next table:
Icon Description
Toggles vertices
Toggles edges
Toggles shading
The menu is described in detail in section "Graphics Area & Views" (p. 69).
For file management (opening and saving of files) AutoGrid5™ uses the standard file chooser
window. The layout of the file chooser depends on the used operating system but a typical layout
is shown in FIGURE 2.58. The directories and files list allows to browsing through the available
directory 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 appropriate
extension.
In the Files of type bar the default file type is set by default to list only the files of the required
type.
MESHING FUNDAMENTALS
AutoGrid5™ has been developed to ensure a quick management of the grid generation process of
turbomachinery configurations. The software is able to take into account the most used components of
a turbomachinery. These components are divided into five types:
l the blade rows
l the meridional technological effects (seal leakage, bleed,...)
l the 3d technological effects (volute, cooling holes,...)
l the solid mesh
l the cooling holes, cooling channel and basin
The software provides a highly interactive user interface ( Graphical User Interface ) and a mesh
wizard ( Row Wizard) allowing an easy setup of the mesh generation process for complex geometries.
Based on a template approach, it ensures reusability of the interactive work on similar geometries
through the full batch mode capability.
The application field of AutoGrid5™ covers all the turbomachinery types:
l axial and centrifugal machine
l multistage machine
l turbine, compressor
l multisplitters
l tandem rows
l return channel
l inducer
l airplane engine compressor stages with fan and by-pass
In this section
3.1 Mesh Domain Definition 159
3.2 Geometry Definition 161
3.3 Mesh Generation Steps 162
3.4 Meshing Similar Geometry & Batch Mode 179
A turbomachinery configuration domain is defined by the space located between the hub, the
shroud and the blades of the machine. Additional domains can be added to the configuration to
mesh technological effects (bleed, seal leakage, cooling holes)
FIGURE 3.1
Turbomachinery domain
The hub & shroud are defined by their meridional trace (ZR coordinates). They define the
spanwise boundaries of the domain. The 3D blade to blade domain is meshed on surface of
revolution located between the hub and the shroud definition. The geometry of the hub and the
shroud are defined using curves in (x,y,z), (r,theta,z) or (r,z).
Row Definition
The turbomachine is composed by rows defined by one type of blade (main blade) or several
(main blade & splitter(s)).
Blade Definition
The blades are defined (x,y,z coordinates) by several surfaces and two curves defining their
leading and trailing edge locations. During the mesh generation the blades surfaces are intersected
by surfaces of revolutions defined from the hub to the shroud.
The inlet and outlet limits of the domain are by default automatically defined by AutoGrid5™
using two straight lines joining the limits of the hub and shroud definitions. The shape and the
location of the inlet and outlet boundaries can be interactively modified in the meridional view. In
case of multistage configuration (multiple rows), the location of the rotor/stator mixing plane is
also automatically defined by AutoGrid5™. Their default location are set at the average
streamwise location between the upstream trailing edge and the downstream leading edge.
Furthermore, the shape and the location of the rotor/stator can be interactively modified in the
meridional view.
Technological Effects
The technological effects are divided in two types: the meridional and the 3d effects. They define
additional domains stuck to the main channel domain.
The seal leakages, the cavities and the bleed belong to the meridional effect types. The meridional
effect is axisymmetric and its geometry is defined by meridional curves (z,r coordinates). The
domain 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:
3D Technological Effects
The draft tube, pipe diffuser, volute belong to the 3D technological effects. These effects are
defined by 3D surfaces or 3D curves (x,y,z coordinates). Their meshes are created manually using
the structured multiblock grid generation system IGG™. The steps used to create the mesh (more
details in IGG™ user manual and in dedicated tutorial) are automatically saved and can be
replayed on similar geometry.
AutoGrid5™ allows the mesh generation of the blade and the end wall solid bodies (Conjugate
Heat Transfer module). Furthermore, the cooling module allows the mesh generation of basin,
basin holes, blade holes, end wall holes, cooling channel with or without pin fins and ribs. More
details are presented in Cooling & Conjugate Heat Transfer Modules.
The geometry curves and surfaces defining the turbomachinery domain can be entered using two
different ways:
l ".geomTurbo" native files (NUMECA turbomachinery geometry file format)
l external CAD files (Parasolid™, CATIA V5, IGES format, ".geomTurbo" native, ".dat" files)
The ".geomTurbo" native file is containing the surfaces and the curves defining the blades and the
meridional contour of the turbomachinery that can be imported within AutoGrid5™.
The ".geomTurbo" file format is structured in three main blocks: the header, the channel and the
row(s) definitions. More details are available on The ".geomTurbo" File Format section.
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
the blades and the meridional contour of the turbomachinery are loaded and displayed. Easy
selection of the geometrical entities can be operated interactively and linked to the project
configuration through contextual menu (see "Geometry Definition" (p. 182) for more details). The
blade channel must be defined by a set of curves (i.e. axisymmetric boundary of a surface of
revolution). The blade(s) of each row are defined by a set of surfaces and two curves defining the
leading and the trailing edges. As long as these curves are not defined, AutoGrid5™ is not able to
create the inlet, outlet and mixing plane boundary of the domain.
Parasolid™ and CATIA V5 import is not available on specific platforms. Please refer to the
installation note for more details.
AutoGrid5™ provides two different ways to initialize a new project according to the type of the
geometry definition (".geomTurbo" or external CAD file). The dialog box Create a new Project
(available through the menu item File/New Project ) lets the choice between a manual
initialization from external CAD file and an automatic initialization from a ".geomTurbo" file.
FIGURE 3.3
Project initialization dialog box
The geometry & configuration definition step is only needed if the project is initialized from
external CAD file. In this case, the configuration of the machine must be set through the subpad
Row Definition of the Quick Access Pad (for example the row contextual menu items Add
Row Downstream/Upstream in Expert Mode allow to add respectively a row downstream or
upstream the selected row). The link with the geometry must be done manually through the
Import CAD window before starting the grid generation.
The global parameters settings involves the definition of the periodicity for each row, the shroud
and hub gap definition and the first cell width at the solid wall definition.
Row Properties
The row contextual menu item Properties in Expert Mode opens the dialog box Row
Properties. The options and parameters available in this dialog box control the mesh generation
of the rows.
Rotation Speed
The parameter Rotation Speed is an information not used by the grid generation process.
However it will be used in FINE™ GUI.
Tandem Row
The parameters Tandem Row must be set to Yes or to With Next/With Previous in case of
tandem row. This is taken into account during the blade to blade grid generation process to
improve the quality of the initial mesh (before optimization).
The multiple mesh passages generation is not available for blade or end-walls including coolings.
Number of Repetition
By default, when selecting the menu View/toggle 3D Solid View, a single blade of each row will
appear in the 3D view.
The number of blades in the graphics area can be repeated for each row individually using the
Number Of Graphics Repetition parameter available in the Row Properties dialog box.
Activate the Default option to see a complete view of all the blades of the selected row.
The row contextual menu item Gap/Fillet/Define Hub/Shroud Gap in Expert Mode opens the
dialog box allowing to control the geometry and the meshing parameters of the gap as presented
in section Hub/Shroud Gaps Control.
Cell Width
The Cell Width imposed in the subpad Mesh Control in Expert Mode will allow to impose the
cell width at the hub, shroud, shroud and hub gap, and the cell width at the wall in the blade to
blade mesh. Afterwards, the cell width can be controlled in the meridional and in the blade to
blade views (refer to Meridional Control and Blade to Blade Control chapters).
The mesh topology is controlled by either the type of machines and the expected number of points
in the row wizard steps (more details in Row Wizard) or by Mesh Control/Grid Level page of
the Quick Access Pad and the button Initialize Topology & Grid Points Distribution of the top
menu bar in Expert Mode:
l When using the row wizard, according to the machine type and the expected number of points,
AutoGrid5™ will choose and adapt the most appropriated mesh generation parameters
available in AutoGrid5™ Expert Mode.
l When using the button Initialize Topology & Grid Points Distribution of the top menu bar in
Expert Mode, the default O4H topology is set up automatically. It defines the topology and
the grid points distribution in the mesh. During this process, AutoGrid5™ searches an
optimized topology according to some geometrical criterion and the grid level selected through
the Mesh Control/Grid Level page of the Quick Access Pad:
The button Initialize Topology & Grid Points Distribution applies to the active row(s).
The 3D row meshes generated with AutoGrid5™ are obtained by stacking blade to blade meshes
on surfaces of revolution generated from meridional curves called flow paths. Each row of the
project has its own 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 initialization (coarse, medium or fine mesh) when clicking on button
Initialize Topology & Grid Points Distribution of the top menu bar. This number can be modified
in the dialog box available through the menu item Mesh Control/Row Mesh Control/Flow
Path Control in Expert Mode . When using the row wizard, the number of flow paths is
controlled in the Control Layer dialog box.
FIGURE 3.4
Flow path definition
If the default flow path definition generated by AutoGrid5™ is not suitable for the project
configuration or for the CFD computation, the features of the dialog box Row: Flow Paths
Control can be used to obtain a complete control of the flow path definition. This dialog box is
available through the menu item Mesh Control/Row Mesh Control/Flow Path Control in
Expert Mode.
The 3D row meshes generated with AutoGrid5™ are obtained by stacking blade to blade meshes
created in the (dm/r,theta) space. Each blade to blade mesh is related to a flow path. The "m"
coordinate is equal to the curvilinear coordinate along this flow path. A blade to blade mesh is
generated in four steps:
The button Initialize Topology & Grid Points Distribution ( Expert Mode ) and the button
Preview B2B in the B2B Control dialog box (row wizard) perform automatically these steps.
Afterwards, the user is able to modify manually the default settings proposed by AutoGrid5™ in
Expert Mode.
Conformal Mapping
The flow paths defined in the meridional space are used to create surfaces of revolution named
layers. 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 , preserves the angles and
ensures reciprocity of the distances.
FIGURE 3.6
Default mesh topology
The inlet, outlet, upper and lower blocks use a H-topology. The skin block around the blade uses
a O-topology.
The Initialize Topology & Grid Points Distribution settings algorithm can change the upper
and/or the lower blocks topologies from H to C-topology if one of the following criteria is
reached:
l The inlet solid angle of the blade becomes higher than 45 degrees and the distance between the
inlet and the stagnation points (in the (dm/r,theta) space) becomes smaller than the pitch angle
divided by 4.
l The outlet solid angle of the blade becomes higher than 45 degrees and the distance between
the outlet and the trailing edge (in the (dm/r,theta) space) becomes smaller than the pitch angle
divided by 4.
This mesh topology adaptation is called high staggered blade topology optimization:
Beside the default (O4H) topology (5 blocks), AutoGrid5™ allows the use of HOH and H&I
topology.
The topology can be modified through the dialog box Define B2B Topology For Active Blade . This
dialog box is available through the menu item Mesh Control/Row Mesh Control/B2B Mesh
Topology Control in Expert Mode .
The feature Initialize Topology & Grid Points Distribution or the row wizard compute the most
appropriated grid points clustering on each block edge of the default topology (and possibly the
HOH or H&I topology) according to either the chosen grid level or the type of the turbomachine
and the expected number of points for the row wizard.
Initial Mesh
The initial mesh is computed using transfinite interpolation techniques inside all the blocks of the
default topology except in the skin block inside which a hyperbolic mesh is generated.
FIGURE 3.8
Initial mesh for a normal blade
The parameters used to control the initial mesh can be modified through the dialog box Define B2B
Topology For Active Blade . This dialog box is available through the menu item Mesh
Control/Row Mesh Control/B2B Mesh Topology Control in Expert Mode .
The optimization system is based on a multiblock elliptic smoother with source terms. All the
blocks of the initial mesh (all edges included except the solid wall) are optimized to increase the
cells orthogonality and to reduce the cells expansion ratio
The parameters used to control the optimization can be modified through the dialog box
Optimization Properties . This dialog box is available through the menu item Mesh Control/Row
Mesh Control/Optimization Control in Expert Mode .
The blade to blade view is used to display and control the quality of the blade to blade mesh of
the rows. The blade to blade mesh quality can also be controlled using the menu Grid/Grid
Quality... or the corresponding icon ( )
Display Update
After each modification of the blade to blade topology, the grid points number, the initial mesh or
the optimization parameters, the blade to blade view of the active row(s) can be updated using the
top menu bar button Generate B2B in Expert Mode or the button Preview B2B in the B2B
Control dialog box in the row wizard.
Active Layer
The blade to blade view of the row is related to an active layer. By default, the active layer is the
hub of the machine (and mid- span when starting row wizard). The interaction area Mesh
Control/Active B2B Layer is used to change the active layer on which the blade to blade mesh
is computed and displayed.
In multistage configuration, the user controls row by row the blade to blade display. A particular
attention must be focused on the undesirable behavior obtained when different blade to blade row
meshes are displayed for different active layers: as the blade to blade view abscissa is the arc
length on the active layer, the blade to blade mesh of different rows could overlap if they are
displayed on different layers. To avoid this and retrieve a correct display, all the rows must be
selected and the top menu bar button Generate B2B in Expert Mode or the button Update B2B
View in the Mesh Control/Active B2B Layer area in Basic Mode, applied after selecting the
new active layer.
The 3D mesh generation of the active blade rows is performed through the top menu bar button
Generate 3D. The 3D mesh is automatically computed by AutoGrid5™ and displayed in the 3D
view. A mesh quality report can be computed and displayed with the top menu item Grid/Grid
Quality Report ( ).
The project persistence is performed using the menu items of the File menu. The name and the
location of the project files are entered through the dialog box Save Project available through the
top menu item File/Save Project.
The button Select a new Project File Name opens a file chooser used to specify the location and
the prefix use to save the new project files. The new prefix is automatically added in the project
library.
The button Overwrite the Selected Project overwrites all the project files of the project selected in
the project library.
Project Library
The project library is the list of all projects saved previously. It is ordered using alphabetical order
and a quick search can be performed using the Search interaction area.
Project Info
The interaction area Enter Project Info is used to specify or modify text information about the
saved project. When scanning the library, the interaction area is automatically updated with the
text of the selected project.
Two types of files are saved by AutoGrid5™: the mesh and the template files.
Mesh files
The mesh files contain the multiblock mesh topology, geometry, grid points, patch grouping and
the boundary condition types:
l new_prefix.bcs: boundary conditions files,
l new_prefix.cgns: grid points files (CGNS format described in IGG™ User Manual - Input &
Output Files),
l new_prefix.geom and new_prefix.xmt_txt: geometry files,
l new_prefix.igg: topology file,
l new_prefix.qualityReport: mesh quality report file,
l new_prefix.config: mesh configuration file used for the grouping in FINE™ GUI and for the
subProject (more details in FINE™ User Manual).
These files can be loaded into the structured multiblock grid generation system IGG™ and by the
CFD integrated environment FINE™/Turbo.
The mesh quality file is saved at the end of the grid generation. If the new project has not yet been
saved before launching the 3D generation, no grid quality report file will be saved because the system
is not able to determine automatically the file location.
Template files
The template files contain the parameters and the geometry needed to reproduced the mesh with
AutoGrid5™:
l new_prefix.geomTurbo and new_prefix.geomTurbo.xmt_txt: the geometry files (geomTurbo
format),
l new_prefix.info: the information file,
l new_prefix.trb: the template file containing the grid generation parameters,
l new_prefix_b2b.png: a picture of the blade to blade view only available on LINUX,
l new_prefix_merid.png: a picture of the meridional view only available on LINUX.
Open an existing project is performed using the menu item Open Project of the top menu File.
The geometry, the parameters and the existing mesh are loaded during this process. The project is
opened by selecting its template file (".trb" extension). The template file of the project can be
selected 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.13.
This button opens a file chooser used to select a template file (".trb" extension).
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.
The button Info>> opens the information area containing two pictures of the selected project, the
userdefined and global information of the project. This information are automatically updated
when scanning the projects of the list.
When a particular turbomachinery configuration has been meshed within AutoGrid5™, the
original template 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 sufficient to rename
the template as the ".geomTurbo" file (as in AutoGrid4™). It is mandatory to use a ".geomTurbo" file
presenting the same row and blade names as the ones used in the template (e.g. when using a new
".geomTurbo", only the geometrical entities 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/Save Template As. The geometry in the duplicated ".geomTurbo" file is then replaced by
the user by a similar geometry. Finally, AutoGrid5™ is launched in batch mode using command
lines arguments specifying the template ".trb" file, the geometry ".geomTurbo" file and the target
location of the mesh files:
igg -niversion <version> -autogrid5 -batch -trb <template file> -geomTurbo <geomTurbo file>
-mesh <mesh file> -print on Linux,
iggx86_64.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
version number and the full path names of the template file (".trb" extension), the geometry file
(".geomTurbo" extension) and the mesh file (".igg" extension).
(New in AutoGrid5™ v12.1)
Multithreading can be used with the additional argument -numproc <np>:
igg -niversion <version> -autogrid5 -batch -numproc <np> -trb <template file> -geomTurbo
<geomTurbo file> -mesh <mesh file> -print on Linux,
iggx86_64.exe -autogrid5 -batch -numproc <np> -trb <template file> -geomTurbo <geomTurbo
file> -mesh <mesh file> -print on Windows.
Example
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 mode without the
need of a display: igg -niversion 122 -real-batch -autogrid5 -trb ... When using this option the
generation of meshes based on python scripts may fail since not all the functions can be used in real-
batch mode.
When the original geometry has been specified through external CAD geometry files, the similar
geometry CAD files can also be specified using the command lines: -dat <geometry file 1> -dat
<geometry file 2> ...
GEOMETRY DEFINITION
In addition to define the geometry using a ".geomTurbo" file, the geometry definition can be
performed interactively through the Import CAD window. Geometry data can be imported from
several CAD 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. The
blade geometry is defined by selecting one or more surfaces while the definition of other configuration
features such as the leading edge, the trailing edge, the hub, the shroud, is performed by selecting one
or more curves and attaching that curve selection to the required feature.
In this section
4.1 Import ".geomTurbo" File 183
4.2 Import CAD 193
4.3 Hub/Shroud Editing 212
4.4 Blade Editing 218
4.5 Cascade Configuration 247
4.6 Blade Geometry Check 249
4.7 Blade Geometry Export 253
Within AutoGrid5™, the ".geomTurbo" file format can be imported in different ways:
l 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
Chooser window is available for browsing through the file system and to select a file. When
clicking on OK (Open) the geometry is loaded in AutoGrid5™.
l in the Quick Access Pad Geometry Definition subpad, the Import Geometry File menu (in
Expert Mode) and the Init From a GeomTurbo File menu (in Basic Mode) allows to select
and load geometry file (IGES, IGG™ geometry, Parasolid™ coupled with ".dat",
".geomturbo", CATIA V5 files) to define or replace the geometry of the entities found in the
file.
l 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 of the row (blades, shroud/hub gap, cooling wall,...) selected. To import a new hub
or shroud, the Import CAD window must be used.
In AutoGrid5™ "geomTurbo" (native format without import CAD) when using an existing template
for different geometry, it is not sufficient to rename the template as the ".geomTurbo" file (as in
AutoGrid4™). It is mandatory to use a ".geomTurbo" file presenting the same row and blade names
as the ones used in the template. When using a new ".geomTurbo" for a row containing several
blades, only the geometrical entities with the same naming as the ones used in the template file will
be replaced.
In AutoGrid5™ "geomTurbo" (with import CAD), all surfaces and curves whatever row or blade
name in the file will replace the corresponding entity name in original row or blade. Note that if
original row or blade name cannot be found in ".geomTurbo", warning will be issued even if some
geometry is replaced.
The ".geomTurbo" file format is structured in three main blocks: the header, the channel and the
row (s) definitions. Following is a example of a ".geomTurbo" file format structure for a
turbomachinery with three blade rows respectively named impeller, diffuser and return channel.
The UNITS-FACTOR parameter allows to select the "units" of the imported geometry in order to
apply an internal scaling and tolerance adaptation transparent for the user that will ensure correct
treatment during the grid generation when computing for example the intersection. If the global
geometry size is below 100 it is recommended to keep the default settings (UNITS-FACTOR set
to 1), otherwise the value should be adapted to the geometry units.
The SCALE-GEOMETRY-FACTOR is an optional parameter. It allows to scale the imported
geometry when defined in native .geomTurbo file.
The bypass parameter must be set to yes in case of a project configuration with bypass (airplane
engine,...)
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:
l The basic curves defined by a set of points.
l The channel curves defined as a composite of basic curves.
The ".geomTurbo" file must contain two channel curves named respectively hub and shroud.
Basic Curves
The basic curve format is used to defined a curve and project it in the meridional space (z,r). The
curve is defined by a name, an interpolation method (c-spline or polyline), the coordinate type, the
number of control points and the points coordinates:
A basic curve name cannot contain the keyword "rotating" if its properties are set to non rotating,
because corresponding patch name will finally contain the keyword "rotating".
By default a c-spline interpolation between the control points is applied. The keyword polyline can be
added beside the coordinate type (ZR) to switch off the c-spline interpolation. In this case, the basic
curve is defined by straight lines joining the control points.
The DATA_REDUCTION when set to 1 allows to perform a data reduction of the basic curve based
on DATA_REDUCTION_ANGLE and DATA_REDUCTION_DISTANCE.
Channel Curves
The channel curves are used to define the hub, the shroud and possibly the nozzle in case of
bypass configuration. A channel curve is a composite of defined basic curves. It is defined by a
name and vertices. Each vertex belong to a basic curves and is defined by its parametric location
(normalized arc length).
The name of the channel curve is part of the format definition and should stay "hub", "shroud" or
"nozzle" by using lower case letters.
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 the outlet (shroud direction).
The row format contains the geometry definition of a complete row. It is defined by a row name,
a row type, a periodicity and the definition of the main blade and possibly the splitter(s):
A row name should not end with the name of another row. For example "row 1" and "row 11" are
allowed but not "row1" and "uprow1".
The row type is used to specify the row location in case of bypass configuration. Four types,
identified by the keyword normal, on nozzle, in bypass and down bypass, are respectively used to
locate the row before the nozzle (inlet fan), on the nozzle (arm), in the bypass and in the
compressor.
Row Periodicity
The row rotation speed will always be read from ".trb" file, but it will be saved in both ".trb" and
".geomTurbo" files to avoid loosing this data in ".geomTurbo" file. However when initializing a
project from a ".geomTurbo" file, the rotation speed can be read from ".geomTurbo" if keyword
"ROTATION_SPEED" available.
Blade Definition
The blade(s) and possibly the splitter(s) are defined by a name and two surfaces defining the
pressure and the suction side. The surfaces are identified by the keywords pressure and suction:
The gap and/or fillet can be defined and are saved in both ".geomTurbo" and ".trb" files. The info
provided in the ".geomTurbo" will have the priority if different from the info in ".trb" file.
The pressure side and the suction side are defined by a set of cross sections of the blade at several
spanwise location. Each section is defined by a set of points:
In AutoGrid5™ the rows and blades can be named by the user. These names are appearing in the
".geomTurbo" file and are used in the ".trb" file. In case the user wants to use a template for different
".geomTurbo" files, the row and blade names should be the same.
When the surfaces defining the blade are physically ruled and that the blade is defined through a
set of sections within the ".geomTurbo" file, user must take care to select the same number of
points to define each section. In addition, when using the keyword uniform_parametrization,
the ith point of the first section will be connected to ith point of the second section.
Example:
Section_1
XYZ uniform_parametrization
The definition of the control lines as inlet, outlet, rotor-stator or additional control lines can be
defined as polylines by the user by adding a section in the ".geomTurbo" file after the channel
definition and before the row(s) definition.
The Import CAD window is started by clicking on Import and Link CAD (in Expert Mode)
or Init From an External CAD File (in Basic Mode) in the Quick Access Pad Geometry
Definition subpad.
The menu bar gives access to several options which can be useful during the setup of a project.
l The pull-down menu File used to import and/or export geometry data in several CAD formats.
l The pull-down menu Geometry used to perform some geometry editing operations such as
creation of geometric entities
l The pull-down menu Edit used to specify the rotation axis of the configuration being defined.
l The pull-down menu View used to perform interactive viewing operations.
l The pull-down menu Select used to perform interactive selection operations.
l The pull-down menu Tools used to measure distance and angle in the view.
File Menu
File/Open... is used to import geometry data from a file. A file chooser is opened to select a CAD
file with one of the following extensions:
l '.igs', '.IGS', '.iges', '.IGES' : IGES files.
l '.dat', '.geom', '.dst' : IGG™ geometry files.
l '.X_T', '.xmt_txt' : Parasolid™ files.
l '.geomturbo', '.geomTurbo' : AutoGrid™ geometry files.
l '.CATpart' : CATIA V5 files (license key required).
FIGURE 4.3
Data Files selection window
A geometry can be correctly represented only if it is fully included in a cube between the points (-
500,-500,-500) and (500,500,500) due to the Parasolid™ library limitation.
When units are imposed in the IGES file, these are purely informative and will not be used by
AutoGrid5™.
File/Open IGES is used to import CAD data stored in the standard IGES format. When names
are defined for entities in the IGES file, AutoGrid5™ uses them for the new entities created in the
repository.
FIGURE 4.4
IGES file browser
This option provides a powerful browser to scan the content of an IGES file and selectively
import IGES entities recognized by AutoGrid5™. In the case of composite curves and surfaces,
the browser 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
corresponds to a criterion defining if entities with the corresponding attribute set accordingly will
be displayed in the browser/imported.
When units are imposed in the IGES file, these are purely informative and will not be used by
AutoGrid5™.
File/Export/All Geometry... 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.
Export/Parasolid...
File/Export/Parasolid... is used to save the selected geometry curves and surfaces into a
Parasolid™ format. It was already automatically done when saving the project for Parasolid™
entities (e.g. from Parasolid™ or CATIA import) but not for SISL entities (e.g. entities manually
created in AutoGrid5™, IGES import). In AutoGrid5™, only wireframe and sheet bodies are
created from a collection of curves and surfaces and no volume model.
Close
File/Close closes the current Import CAD session and opens a new one. All curves and surfaces
are removed without been saved from the geometry repository.
Exit
The geometry entities imported in the Import CAD window session are not deleted by this action.
When reopening the Import CAD window, it shows still all entities.
The Geometry menu provides simple and efficient tools to create, edit and delete points, curves
and surfaces. Without having the complexity of CAD systems, it allows to create wire or surface
models from scratch or to complement imported geometries. The menu allows to:
l create and edit basic and advanced curves and surfaces,
l visualize and probe the geometry entities,
l 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.
Edit Menu
Geometry Axis...
View Menu
View Solid
View/View Solid is used to toggle the display of the solid triangulated representation for the
selected surfaces. If a surface does not have any triangulated representation yet, one will be
created with default settings.
Select Menu
Surfaces
Subsequent operations are done with the mouse in the graphics area:
l Move the mouse to a surface to select (unselect). The surface is ready for selection
(unselection) when it becomes highlighted in blue.
l Left-click to select (or unselect) the surface. The surface changes its highlight to reflect its new
selection status.
l It is possible to select several surfaces at once by defining a selection rectangle. This rectangle
can be specified by pressing the left mouse button without releasing it and dragging the mouse.
Releasing the left button will select all the surfaces totally included in this rectangle.
l 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 through the
surfaces by middle-clicking the mouse, until the desired surface is highlighted. Left-click then
allows to select the highlighted surface.
l 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 graphics area. The first
time <a> is pressed all the surfaces are unselected. The next time, <a> acts as a toggle.
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
following prompt appears when selecting this option:
Subsequent operations are done with the mouse in the graphics area:
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 toggle.
A surface chooser, showing all the surfaces in the geometry repository, is opened to select the
surfaces. The selected surfaces are highlighted. To make one or more surfaces selected, choose
them with the left mouse button in the chooser, then press Apply. The boundary curves of the
surfaces are automatically highlighted in 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
the chooser. A range of surfaces can also be selected by pressing the left button, dragging the
mouse and releasing the left button.
A curve chooser, showing all the curves in the geometry repository, is opened to select the curves.
The selected curves are highlighted. To make one or more curves part of the selection, select them
with the left mouse button in the chooser, then press Apply. The curves automatically appear
highlighted in yellow in the graphics area.
The <Ctrl> key is used in combination with the left mouse button to select several curves in the
chooser.
The <Shift> key is used in combination with the left mouse button to select a range of curves in
the chooser. A range of curves can also be selected by pressing the left button, dragging the
mouse and releasing the left button.
A filter, using regular expression search, is provided to select or unselect curves by their name.
Invert Selection
Select/Invert Selection toggles the selection status for each curve and surface in the geometry
repository. The geometry selection representation, which is highlighted in yellow in the graphics
area, is automatically updated
Hide Selection
Select/Hide Selection hides the selected curves and surfaces, i.e. the selected curves and surfaces
are no longer visible in the graphics area.
Tools Menu
Tools/Distance and Tools/Angle allow the user to respectively measure a distance or an angle in
the view.
The viewing buttons allow the user to perform viewing manipulations on the geometry data. They
are all inherited from the IGG™ technology.
The Quick Access Pad is located on the left of the Import CAD window. It contains one subpad
Geometry including the Geometry Groups page allowing the creation, the deletion and the
visualization of geometry groups, which can contain curves and/or surfaces.
When importing CATIA V5 data, a geometry group is automatically created for each solid model
contained within the file. The name of the group is the name of the corresponding solid model.
Overview
The Import CAD window allows the user to define the geometry for a configuration by importing
external geometry files. The curves and surfaces in the geometry repository can be interactively
selected by the user. Once selected, geometry entities can be linked to a configuration entity such
as the hub, the shroud, the blade,...
The Check Surfaces option allows to automatic check the geometry when linking the blade
surfaces, blade leading/trailing edges. The status of the checks is displayed into a Blade Geometry
Check dialog box.
In the graphics area of the Import CAD window, the capabilities of linking geometry curves and
surfaces to configuration entities, whether in meridional representation or in 3D- space, are
accessed by pressing the right mouse button after selecting the curves and surfaces (highlighted in
yellow) in the graphics area.
All operations on a body (edge reversing, transformation,...) in import CAD should be done before
the first link involving some entities of this body.
The operation is linking a geometry to a specific entity of the configuration that should be selected
in the configuration before performing the link otherwise the user may be requested to specify the
entity. For example when linking curve to leading edge of the blade, the concerned blade should
be selected in the configuration.
Link to Hub is used to link a curve selection to the hub of the configuration. The meridional
representation of the hub is updated to display the new hub geometry.
When importing a single curve, the orientation of the curve will be taken into account.
When importing several curves, the Z minimum from all the end points of the imported curves will
be set as the starting point of the meridional curve whatever the orientation of the curves is. This may
lead to a reversed hub/shroud curve that needs to be manually reversed. Merging the curves in a
single curve in the Import CAD window allows to control the curve orientation before importing it.
Link to Shroud
Link to Shroud is used to link a curve selection to the shroud of the configuration. The
meridional representation of the shroud is updated to display the new shroud geometry.
When importing a single curve, the orientation of the curve will be taken into account.
Link Non Axi to Hub is used to link a surface selection to the active row of the configuration in
case of a non-axisymmetric hub.
Link Non Axi to Shroud is used to link a surface selection to the active row of the configuration
in case of a non-axisymmetric shroud.
Link Non Axi to Shroud Gap is used to link a surface selection to the tip gap of the
configuration in case of a non-axisymmetric shroud gap.
Link to Nozzle
Link to Nozzle is used to link a curve selection to the nozzle of the configuration. The meridional
representation of the nozzle is updated to display the new nozzle geometry. This item only
appears in case of bypass configuration
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 import
process. Only the curves in the geometry selection will effectively be imported and displayed in
the meridional representation.
Link to 3D Effect
Import 3D is used to import the geometry selection and link it to the selected 3D effects.
Link to Blade
Link to Blade is used to link a surface selection to the active blade. That surfaces set will thus
compose the blade surface geometry. The meridional representation of the blade is updated in
order to display the new blade representation.
Link to Pressure Side/Link to Suction Side is used to link a selection of surfaces respectively to
the pressure/suction side of the active blade. The blade is assumed blunt at both edges and is not
compatible with Link to Blade. In particular, this link overrides the link to the blade geometry.
Link to Leading Edge is used to link a curve selection to the leading edge of the active blade.
The meridional representation is updated in order to display the new leading edge geometry.
For a blunt leading edge, only one leading edge curve of the two blade sides should be selected.
Link to Trailing Edge is used to link a curve selection to the trailing edge of the active blade.
The meridional representation is updated in order to display the new trailing edge geometry.
For a blunt trailing edge, only one trailing edge curve of the two blade sides should be selected.
Link to Hub Gap is used to link a curve selection to the hub gap geometry for the active blade.
The curve orientation must be from leading to trailing edge. The meridional representation is
updated in order to display the hub gap geometry.
Link to Shroud Gap is used to link a curve selection to the shroud gap geometry for the active
blade. The curve orientation must be from leading to trailing edge. The meridional representation
is updated in order to display the shroud gap geometry.
Link to Hub Fillet is used to link a surface selection to the active blade including a fillet at hub.
That surfaces set will thus compose the blade fillet surface geometry. Before linking fillet
geometry, a fillet should be added on the blade with Gap/Fillet / Define Hub Fillet menu in the
Row Definition subpad (Quick Access Pad).
Link to Shroud Fillet is used to link a surface selection to the active blade including a fillet at
shroud. That surfaces set will thus compose the blade fillet surface geometry. Before linking fillet
geometry, a fillet should be added on the blade with Gap/Fillet / Define Shroud Fillet menu in
the Row Definition subpad (Quick Access Pad).
In this configuration in the Fillet Properties dialog box ( "Blade Fillet" (p. 228) ), the fillet is
automatically set with a Butterfly topology, and is specified as Defined Shape and the
corresponding meridional curve (where the skin block will be split) is automatically computed at
linking.
Link to Inlet
Link to Inlet is used to link a curve selection to the inlet geometry of the active row.
Link to Outlet
Link to Outlet is used to link a curve selection to the outlet geometry of the active row.
Link to Outlet Up
Link to Outlet Up is used to link a curve selection to the second outlet (upper outlet) geometry of
the active row. Therefore the active row should be the row just before or on the nozzle. This item
only appears in case of bypass configuration.
All link operations replace the previous link, if any. If the entity is composed of multiple curves or
surfaces, a multiple selection is therefore required (using < Shift > - left- click) before the link
operation is applied. For instance, the two sides surfaces of a blade must be selected before invoking
the link command.
Link to Snubber... is used to link a geometry selection to the active snubber. Before linking the
snubber geometry, a snubber should be added on the row with Add Snubber menu in the Row
Definition subpad (Quick Access Pad).
Curves used to define meridional curve up and down parts should be defined from inlet to outlet and
not as B-splines.
l If the geometry is 3D, three snubber parts should be defined: the snubber surfaces, the snubber
leading and trailing edge.
l If the snubber geometry is created in a blade passage, there is then only one link per part
and it should be linked on the blade pressure side: Link to Snubber... > Surfaces on
Blade Pressure Side/Leading Edge on Blade Pressure Side/Trailing Edge on Blade
Pressure Side.
l If the snubber geometry is created on each side of the blade, there will be two links per part,
one link for the blade pressure side (Link to Snubber... > Surfaces on Blade Pressure
Side/Leading Edge on Blade Pressure Side/Trailing Edge on Blade Pressure Side)
and one for the blade suction side (Link to Snubber... > Surfaces on Blade Suction
Side/Leading Edge on Blade Suction Side/Trailing Edge on Blade Suction Side).
The possible closing surfaces at the snubber periodic side should not be part of the geometry
definition.
The snubber surfaces should clearly and completely intersect blade geometry even if it may work if
lying completely on blade surface.
When the snubber is defined by a 3D geometry, a fillet can be added on the snubber on both
blade sides. Link to Snubber.... > Fillet on Blade Pressure/Suction Side is used to link a
surface selection to the active snubber including a fillet on respectively the blade pressure and
suction side. That surfaces set will thus compose the snubber fillet surface geometry.
When the fillet geometry is added on each side of the blade, the side should be coherent with the
snubber geometry definition.
The hub & shroud are defined by their meridional trace (ZR coordinates). They define the
spanwise boundaries 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 external CAD files (Parasolid™, CATIA V5, IGES format).
Edit Hub/Shroud
Furthermore, in the Quick Access Pad Geometry Definition subpad, the Edit Hub/Edit Shroud
(Edit Nozzle in by-pass configuration) menus allow to edit and adapt the shape of the hub and
shroud (nozzle) in the meridional view.
FIGURE 4.5
Move/Add vertex
Once the edge is correctly positioned, right-click to quit the editing tool. All the channel is
recomputed according to the modification as shown in the next figure where the hub is
represented by a green dashed line (representation mode when the hub is not completely mapping
on basic curves).
Non-Axisymmetric Hub/Shroud
The end walls of a usual turbomachinery configuration are defined by axisymmetric surfaces. The
geometry 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:
l generate an axisymmetric mesh,
l axisymmetric mesh adaptation to the specified non-axisymmetric end walls.
Please refer to dedicated tutorial for more details.
When a configuration is including a bulb, the bulb hub surface points are not projected on the non-
axisymmetric surfaces even if the definition covers the hub surface in bulb blocks.
FIGURE 4.7
Non-axisymmetric end walls
In addition to the axisymmetric hub and shroud curves defining the meridional domain, 3D
surfaces defining 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™.
The non-axisymmetric surfaces are stored in external IGG™ data file and specified into the
".geomTurbo" file using the following format:
The non-axisymmetric surfaces can be imported from external CAD files. The contextual menu of
the import window allows the user to link imported surfaces to the hub and/or shroud definition.
FIGURE 4.8
Import CAD contextual menu for non-axisymmetric end walls
The non-axisymmetric end walls generation is controlled into the Row Properties dialog box
accessed by right- clicking on the selected row in the main graphics area and by selecting
Properties from the list of commands. An alternate method consists in right-clicking over the row
i in the Rows Definition subpad of the Quick Access Pad, then in selecting Properties from the
list of commands.
The options Non- Axisymmetric Hub & Shroud are used to enable or disabled the mesh
adaptation on the specified non axisymmetric surfaces.
If the non axisymmetric surfaces do not intersect the axisymmetric mesh, the 3D mesh needs to be
projected on the end walls. This can be done in two ways:
l Projection Along Grid Line (active by default). The mesh is projected on the end walls based
on the spanwise grid line direction. This method allows to avoid non matching connections
that may appear when using the Projection Along the Face Normal.
l Projection Along the Face Normal. The mesh is projected on the end walls, based on the
normal direction of the hub or shroud face.
The option Repair Non-projected Points allows to correct non-well projected points (i.e. when
the mesh points on boundaries are close to hub or shroud surface limits).
When the option is active, it is advised to cover whole row's hub/shroud surfaces with non-
axisymmetric surfaces definition otherwise the repair may result into unexpected hub/shroud points
projection. In the case, the non-axisymmetrc hub/shroud surfaces definition is not covering all row's
hub/shroud surface it is advised to not activate the option.
The options Display Non-Axisymmetric Hub & Shroud are used to display the surfaces in the
3D view.
To obtain a correct behavior, the surfaces must cover all the hub or shroud blade to blade domain
of the axisymmetric mesh. If the specified surfaces do not cover the entire domain in azimuthal
direction as shown in FIGURE 4.10, the Geometry Repetition options allow the user to repeat
the entered surfaces by rotation until the new surfaces cover the domain.
At the end of the 3D blade row generation, the mesh adaptation is performed automatically. The
axisymmetric mesh is adapted by hub to shroud grid points redistribution along the curve obtained
by intersecting the surfaces with the hub to shroud grid lines.
The Blade Expansion dialog box is accessed by right-clicking on the selected blade in the main
graphics area and by selecting Geometry/Expand from the list of commands. An alternate
method consists in right-clicking over the Main Blade (splitter) in the Rows Definition subpad
of the Quick Access Pad, then in selecting Geometry/Expand from the list of commands.
Force blunt at leading edge is used to specify whether or not the blade geometry has to be
considered as blunt in the region of the leading edge.
Force blunt at trailing edge is used to specify whether or not the blade geometry has to be
considered as blunt in the region of the trailing edge.
Stitch surfaces at LE & TE is used when a blade geometry is defined by a native ".geomTurbo"
file to fit leading and trailing edge of pressure and suction sides along 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 discontinuous shape in the blade-to-
blade view may result when reconstructing the section. This option is by default set to None and
to Lofting with guide if a fillet has its geometry creation from meridional curve.
Apply a Rotation
Apply a rotation is used to rotate the blade around a user-defined axis, but is only available for
native ".geomTurbo" blades. The axis and anchor point fields expect three floating point
coordinates while the angle value is given in degrees.
This item is not available if the blade has been linked by mean of the CAD import tool.
Sewing Tolerance
Sewing tolerance is used to define a tolerance value during CAD import, in order to sew the
surfaces that define the blade. The default tolerance value is set as 1e-006. Too small values may
leave many unwanted holes/gaps, while too large values can result in the unwanted deletion of
some faces, and can also lead to unwanted gaps.
An optional expansion can be applied when the blade geometry has to be extended towards the
hub and/ or shroud surface of revolution. Four options are available.
Unchanged
This choice is the default and leaves the original blade surfaces unchanged or restores the original
surfaces when another option was previously activated.
Expand
An expansion can be specified by the user when the blade geometry has to be extended towards
the hub and/ or shroud surface of revolution so that the blade intersects the hub/ shroud definition.
l In case of native "geomTurbo" format, the input value is treated as an expansion factor.
l In case of geometry definition through CAD import, two input boxes appear: Cut offset and
Extension offset. These inputs allow respectively to define the absolute hub/ shroud offset to
cut the blade and the absolute blade extension over the hub/ shroud.
FIGURE 4.12
Definition of blade offset from hub with schematic sketch
Treat blend
When the blade geometry and the hub/ shroud surface of revolution connect tangentially by mean
of a blend, a special treatment needs to be applied in order to ensure proper intersection
computation between the blade and the hub/ shroud.
The method used to handle such cases can be summarized as follows:
This treatment consists in the same steps as treat blend, but the cutting offset is input directly as a
distance.
Cut fillet
This treatment is automatically used and only used when defining a fillet on blade without
geometry creation (only for fillet butterfly topology ("Blade Fillet" (p. 228)) when the fillet
definition is included in the blade definition) to cut the blade at the fillet layer (specified radius in
Fillet Properties dialog box), remove the fillet part (keeping it for fillet meshing) and expand the
resulting straight blade towards the channel.
Section extension
This treatment is automatically used and only used when defining a blade with rounded tip
topology using the marine propeller row wizard. This blade extension method is based on a
section translation:
l the blade is intersected at the gap layer.
l the blade is intersected at a second layer above the gap layer defined by the parameter Span
Cut Percentage (from gap). This parameter defines the relative distance from 0 to 1 between
the gap layer and the leading/trailing edge end point where the blade will be intersected the
second time.
l this second intersection is translated above the shroud.
l the original blade is split at the first intersection and the upper part is removed.
l lofted surfaces are created between the first and the translated second intersection.
l lofted surfaces are added to the split blade definition to obtain the final geometry.
The section extension method is not valid for native geomTurbo format and is only applicable for
geometries linked by mean of the CAD import tool.
When the blade geometry is not connected to the hub or shroud surface of revolution, a gap
should be defined on the blade. The Gap Properties dialog box (more details in Hub/Shroud
Gaps Control) is accessed by right-clicking on the selected blade or row in the main graphics area
and by selecting Gap/Fillet/Define Hub Gap or Gap/Fillet/Define Shroud Gap from the list of
commands. An alternate method consists in right-clicking over the row or the Main Blade
(splitter) in the Rows Definition subpad of the Quick Access Pad.
When the gap has been added, a popup menu is available in the Rows Definition subpad of the
Quick Access Pad when right-clicking on Hub gap or Shroud gap items allowing to modify the
settings of the gap or to delete the gap.
In some configurations a blade can be rotated on itself. For that purpose the blade is attached to a
penny (at hub and/or shroud) which represents the rotation axis. In order to avoid that the blade
intersects the channel during its rotation, a partial gap is created before and/or after the penny,
depending on the penny size and location.
FIGURE 4.15
Partial Gap Properties dialog box
When the partial gap has been added, popup menu is available in the Rows Definition subpad of
the Quick Access Pad when right-clicking on Hub partial gap or Shroud partial gap items
allowing to modify the settings of the partial gap or to delete the partial gap.
In AutoGrid5™, meshing a multiblade (one or more splitters) configuration with different tip gap
heights is possible at the condition that tip gap meridional profiles do not intersect and that there is
enough space between each of them to be able to insert mesh layers (flow paths).
In order to overcome this limitation, a technique similar to hub and shroud non-axisymmetric
treatment (more details here) is available for non-axisymmetric tip gap.
When the real tip gap is defined by non-axisymmetric surfaces, the mesh is obtained in two steps:
l generate a mesh with an axisymmetric tip gap,
l 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 the gap
mesh intersects these surfaces. Otherwise gap spanwise grid lines should be extended to intersect these
surfaces and it will lead to a non matching connection with the channel mesh.
In addition to the axisymmetric curve defining the shroud gap, 3D surfaces defining the non-
axisymmetric shroud gap must be defined. These can be directly specified in the ".geomTurbo"
file or imported through the Import CAD window of AutoGrid5™.
To obtain a correct behavior, the non-axisymmetric surface(s) defining the shroud gap:
l should cover all the domain (blades + channel parts),
l should cross all the blades including the non-axisymmetric shroud gap.
The non-axisymmetric surfaces are stored in external IGG™ data file and specified into the
".geomTurbo" file using the following format:
NI_BEGIN NINonAxiSurfaces tip_gap
NAME non axisymmetric tip gap
The non-axisymmetric surfaces can be imported from external CAD files. The contextual menu of
the import window allows the user to link imported surfaces to the shroud gap definition.
FIGURE 4.17
Import CAD contextual menu for non-axisymmetric shroud gap
The non-axisymmetric shroud gap generation is controlled into the Row Properties dialog box.
The option Non-Axisymmetric Shroud Gap is used to enable or disabled the mesh adaptation
on the specified non axisymmetric surfaces.
The option Repair Non-projected Points allows to correct non-well projected points (i.e. when
the mesh 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 3D
view.
To obtain a correct behavior, the surfaces must cover all the domain (blades + channel parts) of
the axisymmetric mesh. If the specified surfaces do not cover the entire domain, the Geometry
Repetition option allows the user to repeat the surfaces by rotation until the new surfaces cover
the domain.
At the end of the 3D blade row generation, the mesh adaptation is performed automatically. The
axisymmetric mesh is adapted by hub to shroud grid points redistribution along the curve obtain
by intersecting the surfaces with the hub to shroud grid lines.
The blade geometry can be connected to the hub or shroud surface of revolution by means of a
fillet. The Fillet Properties dialog box is accessed by right-clicking on the selected blade or row
in the main graphics area and by selecting Gap/Fillet/Define Hub Fillet or Gap/Fillet/Define
Shroud Fillet from the list of commands. An alternate method consists in right-clicking over the
row or the Main Blade (splitter) in the Rows Definition subpad of the Quick Access Pad.
When the fillet has been added, popup menu is available in the Rows Definition subpad of the
Quick Access Pad when right-clicking on Hub Fillet or Shroud Fillet items allowing to modify
the settings of the fillet or to delete the fillet.
FIGURE 4.20
Fillet popup menu
Depending of the mesh topology in the fillet, different methods are proposed in AutoGrid5™ to
create the fillet:
The B2B section offset method is available when the Topology is set ( (New in AutoGrid5™
v12.1)) or not set to Butterfly.
When the Topology is not set to Butterfly:
l starting from the fillet flow path (defined either by radius at leading/ trailing edge or an
external curve) towards the channel flow paths (hub/ shroud), on a certain hard-coded
number of layers (distributed differently than the flow paths in spanwise direction), the
intersection of the blade is computed.
l starting from this intersection, the blade geometry is enlarged according to the local radius.
The blade offset is computed to ensure the tangency of the fillet with the channel flow paths
(hub/ shroud).
The method B2B section offset is not compatible with non- axisymmetric hub/shroud. An error
message "Could not create fillet geometry for blade. Fillet creation by B2B section offset is not
compatible with non axisymmetric channel" is appearing during the mesh generation.
The From meridional curve method only available when the Topology is set to Butterfly: the
fillet is created between the specified meridional curve (defined either by radius at leading/ trailing
edge or an external curve) and the channel (hub/ shroud) and will allow to impose the fillet
tangency at hub or shroud and on blade.
The method From meridional curve is not fully compatible with non-axisymmetric hub/ shroud
especially if the non-axi deviation is too large.
The method From meridional curve may lead to problem due to Parasolid limitations when the
specified radius is equal or bigger than the leading/ trailing edge radius.
Constant radius
The Constant radius method only available when the Topology is set to Butterfly . This
approach creates the fillet by rolling a ball along the blade (rolling ball method) on the hub/shroud
surface. This method will allow to impose the fillet tangency at hub or shroud and on blade but
also remove limitations of the From meridional curve method when combining fillet creation
with non axi hub/shroud surface.
When selecting the Constant radius method, the radius of the fillet is specified by the user, the
option Defined Shape option is automatically activated and the fillet meridional curve will be
computed to ensure that it is located everywhere above the fillet.
In AutoGrid5™, a snubber can be added to the row. The snubber is added on the active row in
the Add Snubber menu by right-clicking on the selected row in the Row Definition subpad
(Quick Access Pad).
The channel orientation should be mainly streamwise otherwise problems may occur during the 3D
smoothing.
The snubber should not be too close to the blade leading and/or trailing edge, which could lead to
mesh generation failure. Similarly, when the snubber is including a fillet, there must always remain a
distance between the blade leading and trailing edges and the fillet surfaces. These surfaces must not
reach the blocks at the leading and trailing edge marked by the red dots in the following figure.
Geometry Control
The snubber geometry is defined in 2D using meridional curves or in 3D using surfaces and
curves of the full 3D geometry. These can be directly specified in the ".geomTurbo" file or
imported through the Import CAD window of AutoGrid5™ (more details in Import CAD ).
When the snubber is defined in 3D, a fillet can be added to the snubber.
Example of ".geomTurbo" when the snubber 3D geometry is created in a blade passage and
the snubber fillet on both blade sides.
For a non-axisymmetric snubber, the periodicity of the snubber geometry has to be equal to the one
of the blade
A popup menu is available in the Rows Definition subpad of the Quick Access Pad when right-
clicking on the snubber item allowing to modify the settings of the snubber (Properties) or to
delete the snubber (Delete).
The snubber generation is controlled into the Snubber Properties dialog box (more details in
Snubber Controls).
FIGURE 4.21
Snubber Properties dialog box
For some turbomachinery configuration like aircraft engines, it could be interesting to mesh the
stator upstream the nozzle arms with staggered angle varying with the azimuthal location of the
blade. Starting from a single stator blade, the option allows to duplicate the blade together with a
rotation around the blade and the rotation axis as presented in the next figure.
FIGURE 4.22
Aicraft engine configuration
The Blade Duplication dialog box is accessed by right-clicking on the selected blade in the main
graphics area and by selecting Duplicate from the list of commands. An alternate method consists
in right-clicking over the Main Blade (splitter) in the Rows Definition subpad of the Quick
Access Pad, then in selecting Duplicate from the list of commands.
FIGURE 4.24
Rotation around the blade axis
When pressing the button Duplicate, new blades are automatically added to the configuration tree.
Their geometries are copied from the original blade and rotated using the defined parameters. The
new blades inherit all the topological settings of the original blade.
When the blade is duplicated, in the Row Properties dialog box, the Number Of Geometry
Periodicity of the row and the Number Of Meshed Passages fields are automatically updated
according to the amount of duplicates.
The leading and trailing edge curves can be defined by the user by adding a wizard to the blade
through the blade menu Geometry/Add Wizard LE TE. This menu will add an item Wizard
LE TE in the blade configuration tree.
When starting the wizard, the dialog box controlling the layers is opened and the default layers are
displayed in the meridional view.
The default layer limit can be controlled through the parameters Upstream control layer limit
and Downstream control layer limit. Their values are given in relative arc length location on the
hub.
The clustering at hub and shroud (Hub clustering/Shroud clustering) is controlled by giving a
ratio 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,
the user can control the percentage of cell of constant width (% of Constant Cells), the number
of layers and the number of control points used to defined each layer.
When the blade has a very high staggered angle close to 90°, the technology that uses dm/r
minimum and maximum value is no more suitable. The options Very low leading edge angle
and Very high leading edge angle allow the user to switch to a more suitable technology (using
theta minimum and maximum).
The tolerance used to create the chord at leading or/and trailing edge can be decreased especially
in case of blade 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.
When the button Next>> is pressed in the Leading Edge & Trailing Edge: Control Layer dialog
box, default leading edge and trailing edge locations are computed and displayed in the XYZ
view and the dialog box Leading Edge & Trailing Edge: Edges Control is opened.
Active Layer
By default, all the layers are activated (displayed in yellow). The Active layer (0:all) parameters
can be used to select the layer on which the values of the following parameters will be applied.
When the value is not equal to 0, the active layer is automatically displayed in yellow and the
others ones in blue.
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 in the XYZ space of the points defined in the B2B space) are created and expanded
using first order prolongation.
The parameters Leading Edge Location and Trailing Edge Location allow the user to modify
the default location by giving a deviation of its parametrical position on the blade intersection. The
parameters can vary from 0 to 1.
The parameters Hub Expansion and Shroud Expansion control the expansion of the leading
edge and trailing edge curves in percentage of the spanwise height.
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
by the one created by the wizard. The options Update Leading Edge and Update Trailing
Edge are used to choose if the leading, trailing or both edges must be replaced.
The wizard is not available for blunt leading and trailing edge.
A sheet can be added on the blade by right-clicking on the selected blade in the main graphics
area and by selecting Define Sheet from the list of commands. An alternate method consists in
right-clicking over the Main Blade (splitter) in the Rows Definition subpad of the Quick Access
Pad, then in selecting Define Sheet from the list of commands.
The sheet on blade is not compatible with sharp treatment, control lines on blade, throat control and
conjugate heat transfer/cooling options.
In the meridional plane, AutoGrid5™ imposes flow paths at the upper and lower sheet limit,
while in the blade-to-blade view, AutoGrid5™ imposes grid point clustering at the upstream and
downstream limits. The blade sheet is defined by 5 geometry characteristics:
l the upper and lower limits,
l the upstream and downstream limits,
l the sheet width.
The lower/upper zone are identical for all the blades of the same row.
Lower Side, Upper Side, Both Side. A sheet can be added on the lower, the upper or on both
sides of the blade.
Distance From Leading/Trailing Edge. The sheet upstream and downstream limits are defined
by giving a 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
controlled before and after the sheet definition (N1,N2). The number of points on the sheet is
equal to the number of points on the blade lower side and/or on the blade upper side - (N1+N2-2).
FIGURE 4.26
Cascade Configuration - Periodicity
FIGURE 4.27
Cascade Configuration - 3D Mesh
Check Geometry
Once the properties of the blade geometry are defined, the user can check the correctness of the
definitions of the blade geometry using the Blade Geometry Check dialog box. This dialog box is
available from the Geometry/Check option in the contextual menu, and appears by right-clicking
on the Main Blade or Splitter in the Rows Definition subpad of the Quick Access Pad. When
the dialog box is opened, the blade sections and orientations are automatically displayed in the 3D
view.
The blade sections must be streamwise oriented. If the hub and shroud are defined, AutoGrid5™
warns the user if the blade section is not correctly oriented.
The distance check in loop detection process warns the user if the Control Points Distance
Criteria is reached. The default value of the distance between 2 consecutive blade sections
control points is 1e-006.
The angle check in loop detection process warns the user if the Control Points Angle Criteria is
reached. The default value of the angle between 3 consecutive blade sections control points is
90.0.
Adapt Geometry
Once the blade geometry is checked, the blade definition can be adapted by performing the
following actions:
l data reduction, so as to remove potential loops,
l blade rotation around the Z axis,
l re-orientation of the blade sections,
l data reduction using the distribution of control points.
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.
A second check is done on intermediate blade section curve to see if the interpolation of the
sections does not contain loops.
If the loops are detected in the intermediate curve section, then the loop locations are displayed in
the 3D view. A warning indicates that interpolation is wrong and contains loops. Problem of
interpolation often arises due to the way the sections are defined and in particular the control
points distributions on the sections. It is strongly advised to define the control points as smooth as
possible. If this process does not work, the Blade Geometry Check dialog box can be used to
redistribute the control points on each section by activating the option Control Points
Redistribution. When the option is checked, the blade sections are automatically recomputed
based on a user-defined control point 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 4.28
Control points redistribution settings
A geometric progression is used to assume minimum expansion ratio between the control points
to minimize the risk of loops after sections interpolation. In 99% of the test cases, after selecting
the Check button and discovering interpolation loop for one time, the default values provided by
AutoGrid5™ gives appropriated results.
This option can also be really useful in case of very accurate data entered for each section by the
user. This can be a reason of the slowness of the intersection process. To improve, Control
Points Redistribution option can be tried.
Blade Rotation
A blade section rotation is applied around the Z-axis using the angle specified in the Original
Blade Data Rotation Angle input data field.
FIGURE 4.29
Export Blade Geometry dialog box
This option is available only if the original blade geometry data exists in a "geomTurbo" format.
l Set the Number Of Sections to define the number of blade sections to be computed in the
exported ".geomTurbo" file.
l Set the Number Of Points Near Leading Edge to define the number of control points at the
leading edge.
This option is not taken into account for blunt or sharp leading edge.
l Set the Number Of Points On Blade Sides to define the number of control points on pressure
and suction sides of the blade.
l Set the Number Of Points Near Trailing Edge to define the number of control points at the
trailing edge.
This option is not taken into account for blunt or sharp trailing edge.
l The clustering law between the leading edge area and the trailing edge area is defined by:
l The Number of Cst Cells. This number has to be less than the number of control points on
the blade sides defined in the Number Of Points On Blade Sides data input field.
l The Clustering At Leading Edge, defined as the normalized length of the leading edge
area.
l The Clustering At Trailing Edge, defined as the normalized length of the trailing edge
area.
l 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
geometry to be exported.
If there is any blank space in the parent directory path, AutoGrid5™ does not allow to export the
".geomTurbo" file and displays an error message.
ROW WIZARD
After defining the geometry, the row wizard offers an easy way to set up the mesh generation
parameters according to the type of the machine:
l wind turbine,
l axial, Francis, Kaplan turbine,
l inducer,
l axial compressor,
l centrifugal impeller,
l centrifugal diffuser,
l return channel,
l contra rotating fan,
l centrifugal pump,
l axial fan,
l marine propeller.
The row wizard is available using the button Row Wizard of the top menu bar in Basic Mode or
using the button Row Wizard through the Mesh Control/Grid Level page of the Quick Access
Pad in Expert Mode .
In this section
5.1 Geometry Check 258
5.2 Machine Characteristics Definition 258
5.3 Gap/Fillet Definition 259
5.4 Flow Paths Definition 261
5.5 Blade-to-Blade Mesh Definition 261
5.6 Initialization End 263
5.7 MultiStage Management 264
5.8 Automatic Settings 265
When launching the row wizard, AutoGrid5™ warns the user that mesh generation parameters
will be modified by the wizard and prompts the user to continue. This reset will keep the
modifications performed by the user in the row wizard 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 is OK, 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 are selected,
AutoGrid5™ warns the user and quits the wizard.
After the geometry check, the Blade row type dialog box is opened.
Only the centrifugal impeller wizard is designed for multi-bladed row. All the others, when used for
multi-bladed rows, may lead to improper H&I topology.
The next step of the wizard is used to define the gaps and the blade fillets if needed.
When gap or fillet is already existing in the project configuration before launching the wizard, its
width is used as wizard parameters instead of the default.
When selecting the hub gap or tip gap option, the respective hub fillet or tip fillet option is
automatically frozen and reversibly.
When pressing the button Next>> , a message warns the user if the fillet does cut the limit of the
domain.
The fourth stage of the wizard controls the cell width at the wall and the number of flow paths.
The spanwise expansion ratio is continuously updated after each user's change. The flow paths
are automatically displayed and updated into the meridional view.
By default, the number of flow paths is set to 57. If tip and/or hub gap/fillet are defined previously
in the Gap and Blending Control dialog box, the number of flow paths is increased by 16 or 32
(73 or 89 flow paths).
When increasing or decreasing the number of flow paths, the number of flow paths in the gaps
and fillets is automatically updated as well as the percentage of constant cells:
l the flow paths in the gap or fillet will be 25 for N>=129, 21 for N>=97, 17 for N>=65, 13 for
N>=33 and 9 for N<33 (N is the number of flow paths).
l the percentage of constant cells will be 80 for N'>=157, 70 for N'>=129, 60 for N'>=97, 50
for N'>=81, 40 for N'>=65, 30 for N'>=33, 0 for N'<33 (N' is the number of mid flow paths
corresponding to N - gap/fillet flow paths).
The last stage of the wizard is used to set up all the blade-to-blade parameters for the mesh
generation. All the expert parameters are set automatically according to the type of machine and
the blade-to-blade geometry configuration.
In addition, the option Skewness (orthogonality) and Expansion Ratio can be used to display the
quality color contour.
If the machine type is not an inducer, a Kaplan turbine or a centrifugal pump and the high
staggered blade optimization is high at inlet, low at outlet or low at inlet and high at outlet, a full
matching mesh can be imposed between the channel and the gap when a hub or tip gap is defined
with the option Full Matching Mesh.
When previewing the mesh (Preview B2B button in B2B Control dialog box or Update B2B
View in Mesh 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
ensure streamwise continuity through the rotor stator line. The minimum value between two
successive blades is chosen.
When clicking on the button Finish, AutoGrid5™ proposes to start the 3D mesh generation of the
selected row by clicking on yes.
The 3D generation of the meridional effect (far field of the wind turbine, propeller and contra
rotating fan machine type) must be performed together with the generation of the row(s) connected
with it.
The row wizard is useful for a quick setup of the mesh for all the rotors and stators of a multistage
turbomachine:
l the row wizard is applied on the first rotor and on the first stator
l the first rotor is selected and the button Copy Row Wizard Settings pressed
l all the other rotors are selected and the button Paste Row Wizard Settings pressed to apply the
same wizard parameters to the other rotors.
l the first stator is selected and the button Copy Row Wizard Settings pressed
l all the other stators are selected and the button Paste Row Wizard Settings pressed to apply the
same wizard parameters to the other stators.
AutoGrid5™ automatically is adding and unfixing upstream and downstream control lines
following the blade leading and trailing meridional shapes. These lines are created for all the
machine types 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
the downstream control line (N3) is computed automatically based on the length and the number
of points (N2) in the streamwise direction between the control lines.
N1 = 0.5*N2*L1/L2
N3 = 0.5*N2*L3/L2
The default matching O4H topology is used by the wizard. When the row geometry contains
splitter blades 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.
According to the blade solid angle ("Topology for High Staggered Blades" (p. 361)) computed
on the hub (β hub ) and shroud (β shroud ) layer, the high staggered topology optimization is
automatically activated.
The topology is highly staggered if:
l βhub>35° and βshroud>35°
l βhub>60° and βshroud>-20°
l βshroud>60° and βhub>-20°
l βshroud>50° and βhub>-10°
l βshroud>45° and βhub>=-1°
l βhub>45° and βshroud>=-1°
For grid level 0, the default number of points on the blade is set to 81. When decreasing or
increasing the grid level the number of points on the blade is set to ensure 3 multigrid levels. The
number of points in the blade-to-blade mesh is controlled by the number of flow paths (N):
In addition when high staggered mode is active, the number of points is computed in up & down
blocks to obtain a high quality mesh. The method also ensures at least 3 multigrid levels.
l The number of points along the blunt leading or trailing edge is automatically updated to
reduce the 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 and
AutoGrid5™ imposes variation of the streamwise weight to recompute grid points distribution.
Throat Control
The sharp treatment is automatically activated for blunt blade edge angle lower than 25 degrees. If
the blade is not blunt, the blade edge angle should be lower than 90 degrees to activate the sharp
treatment
The rounded treatment is automatically activated for blunt blade of Kaplan and Francis turbines.
Optimization Parameters
According to the type of machine, the defaults settings described above can be changed.
The wizard of the wind turbine is composed of the following steps controlling the main
parameters of the mesh generation of the wind turbine:
l Geometry check (optional)
l Dedicated pseudo shroud and upstream and downstream limit definition (the pseudo-shroud
should intersect the tip of the blade),
l Gap and fillet definition (New in AutoGrid5™ v12.1),
l Blade flow paths definition,
l Dedicated far field limit and far field flow path definition,
l Blade-to-blade mesh accuracy definition,
l 3D mesh generation.
When the wizard is launched, the Channel Control dialog box allows to control the pseudo
shroud location and the upstream/ downstream limits.
After imposing a reset hub and shroud, if Next>> is pressed they become the new hub and shroud
that will be considered when reset hub and shroud is deactivated. It is thus not possible to come
back to the original hub and shroud of the imported geomTurbo if Cancel is pressed at any step of
the same wizard.
When the parameter Reset Hub & Shroud is activated, AutoGrid5™ creates automatically a
horizontal pseudo shroud and/ or hub located at a radius (Rhub/shroud) defined by:
with BladeRadiusMin = maximum of the minimum blade radii computed on leading and trailing
edge and BladeRadiusMax = minimum of the maximum blade radii computed on leading and
trailing edge.
Upstream Z = Zref-Lupstream
Downstream Z = Zref+Ldownstream
Upstream Z = Zref+Lupstream
Downstream Z = Zref-Ldownstream
The Far Field Control dialog box is used to control the domain up to the blade (far field).
The far field limit is controlled by the parameter Far Field Thickness normalized with the
BladeRadiusMax (minimum of the maximum blade radii computed on leading and trailing edge):
l A rounded treatment is applied to the topology at trailing edge (Rounded Streamwise and
Rounded Azimuthal default topologies).
l The optimization steps is set to 5000.
l The multigrid acceleration is set to off.
l The free inlet and outlet angle are set to off.
l The straight boundary initialization is set to on.
l The interpolation level is set to 10%.
Inducer Settings
The mesh generation set up of the contra rotating fan is similar to the wind turbine set up:
l The new topology (Rounded Azimuthal) is used automatically if the blade solid angle at mid
span is higher than 60° and the number of blades (periodicity) below 5.
l A rounded treatment is applied at the blunt trailing edge.
l The optimization steps is set to 500.
l The free inlet and outlet angle are set to off and mesh is frozen (if the blade solid angle is lower
than 45°).
l The straight boundary initialization is set to on.
l The rounded bulb topology without singular line is applied when the configuration is
presenting a bulb.
The mesh generation set up of the marine propeller is similar to the wind turbine set up:
l Geometry check (optional)
l Dedicated pseudo shroud and upstream and downstream limit definition (the pseudo-shroud
should intersect the tip of the blade),
l Gap and fillet definition (New in AutoGrid5™ v12.1),
l Blade flow paths definition,
Starting AutoGrid5™ v12.2, the following dedicated settings are changed automatically (New in
AutoGrid5™ v12.2):
l Four control lines are added: two curvilinear unfixed ones close to the blade and two fixed
lines at constant z at a much larger distance.
l Depending on the units, the row clustering is adapted.
l For high staggered topology, the hub layer instead of the midspan layer is considered as
reference section to initialize the blade-to-blade number of points.
l Matching gap mesh is enforced.
l Frozen inlet and outlet angles.
l Relax inlet and outlet clusterings.
l Smoothing steps are set to 200 on fine grid and to 300 on full multigrid.
l If bulb configuration, the untwist inlet and/or outlet treatment is applied.
The option Blade Tip Rounded Topology (New in AutoGrid5™ v12.2) allows to impose a specific
topology adapted for the rounded tip configuration.
The option Blade Tip Rounded Topology is only applicable to double rounded blade (no blunt)
and is under license.
If the option Blade Tip Rounded Topology is active while the blade tip is not rounded (i.e. the tip
is not defined geometrically by surfaces), the topology is adapted to have a butterfly topology above
the blade instead of an H block: the flat tip topology.
When the propeller configuration is presenting a small hole at the tip, the option Blade Tip
Rounded Topology may not work because the hole is too small such that the flat tip topology
cannot be used as well.
l "sorry, row wizard initialization failed: blunt leading or trailing edge not compatible with rounded
tip topology" because a blunt leading/trailing edge has be detected. In case a blunt is only detected
due to geometry tolerance, the options force blunt at leading/trailing edge can be deactivated
into the blade expansion dialog box ( Blade Expansion);
l "sorry, row wizard initialization failed: blade cannot be expanded" because the loaded blade
geometry is not intersecting the hub. To solve the issue, the expansion at hub settings can be
adapted into the blade expansion dialog box ( Blade Expansion);
l "sorry, row wizard initialization failed: blade cannot be expanded" because no valid blade sheet
can be created (reported in the shell or terminal). The sewing tolerance can be increased into the
blade expansion dialog box ( Blade Expansion);
l "sorry, row wizard initialization failed: blade cannot be expanded" because gap intersection
contains too high angular deviation (reported in the shell or terminal). The check ratio can be
increased into the blade-to-blade controls dialog box ( Intersection Controls).
MERIDIONAL CONTROL
The meridional space allows first to control the geometry of a machine and the related parameters:
l Basic curves: these are general 2D meridional curves.
l Channel curves: hub, shroud, nozzle. They are based on basic curves, i.e. lying on them.
l Rotor/stator curves. They define the row domain in the streamwise direction.
l Meridional control lines. Optional control lines geometrically similar to rotor/stator. They can have
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 surfaces for
the final mesh.
In this section
6.1 Geometry Control 284
6.2 Mesh Control 302
Basic curves are 2D meridional curves which can be used to define channel curves (hub, shroud
or nozzle) and meridional technological effects. They are defined as general NURBS curves and
then discretized to be used as polylines.
Creation
Basic curves can be created through the ".geomTurbo" file (more details in Import - >
geomTurbo) or through the import CAD facility (more details in Import CAD).
Properties
Basic curves can be discretized through the right-click popup menu Properties. The following
dialog box will appear:
In the Discretisation field, enter the number of discretization points desired between each basic
curve control points. Several basic curves can be selected to change the discretization in one time.
All channel curves using the modified basic curve will be updated and all rotor/stators and control
lines recomputed if necessary.
The Rotating option when active allows to define the selected basic curve (channel curves and
meridional technological effects) as rotating to automate corresponding block and patch
(extension "_rotating") settings.
Deletion
Basic curves can be deleted through the right-click popup menu when basic curve highlighted in
meridional view.
Basic curves can be checked through a Channel Geometry Check dialog box. This meridional
geometry checking process helps to check the completeness of the geometry as well as the
validity of the end walls, before starting the mesh generation when clicking on Check button. It is
also useful as it could repair the curves wherever it is required by clicking on Apply Data
Reduction button after imposing the Control Points Distance/Angle Criteria.
The option Check All Meridional Curves allows to perform the operations with the buttons
Check, Apply Data Reduction and Reset Original Data to all meridional curves, otherwise it is
applied to the last selected curve in the meridional view.
The Check button checks the curves quality according to the current values of their data reduction
and control points distance/angle criteria without modifying their values.
The Apply Data Reduction button applies the data reduction on the meridional curve(s), checks
their quality and remove points if needed according to control points distance/angle criteria values.
The Reset Original Data button resets the copy of the set of points equal to the original set of
points, and checks the curves quality.
Once defined, all these channel curves can be controlled interactively to change their shape and/or
orientation. The control is accessible from the Edit Hub - Edit Shroud - Edit Nozzle menus of
the Quick Access Pad Geometry Definition subpad or directly by right-clicking on a basic curve.
FIGURE 6.1
Shroud editing
Once the edge is correctly positioned, right-click to quit the editing tool. All the channel is
recomputed according to the modification as shown in the following figure:
FIGURE 6.3
Channel regenerated
When hub/shroud/nozzle are not completely mapping the basic curves, there are represented by a
green dashed line
6.1.3 Rotor/Stator
Rotor/stators define the limits of a row, either the interface between two rows or the inlet or outlet
of a row. They are created automatically when initializing the configuration (defining the rows)
and can 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 dedicated dialog box.
To display the control points, simply left-click on a rotor/stator (FIGURE 6.4) and then left-click
to move them. To open the dialog box (FIGURE 6.5), right-click on it and select Properties in
the popup menu.
Properties
The dialog box is divided in two main parts, allowing to control the shape of the rotor/stator and
other properties.
The Reference frame allows to specify the frame on which the position of the rotor/stator
depends. For consistency reasons, when switching to relative to channel frame, the rotor/stator
shape is switched to curvilinear.
l Absolute . The rotor/stator control points are absolute (i.e. R/Z constant or defined from
geometry file).
l Relative to Channel. The rotor/stator control points are relative to the channel (i.e. the hub
and shroud).
l Relative to Row . The rotor/stator control points are relative to the rotor/stator neighboring
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
automatically the rotor/stator and its control points in the graphical area.
l Linear. Impose a linear shape. Additionally the rotor/stator can be located at a R or Z constant
position by activating the corresponding button and entering the desired value.
l Curvilinear. Just for information, does not change the current shape, it indicates that a control
point was moved manually.
l Defined Shape. This button is activated if the rotor/stator was defined by an external curve.
An external curve can be imposed by selecting a simple ".dat" file through the button Select
Geometry File. When imposed by a file, the location of the rotor/stator will be defined in a
totally absolute position. It also means that if the hub or shroud changes, it should still intersect
the user defined rotor/stator.
The specified geometry should be inside the domain bounded by the hub and shroud limits.
l 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
useful for a rotor/stator, it imposes the cell size in the blade to blade mesh at the rotor/stator
location. A default optimized value is always computed, symbolised by "0.0" in the dialog box.
Each control point of a rotor/stator can be moved on a "support curve" automatically created,
which shape is fixed and cannot be changed (this "support curve" is not displayed). The number
of control points is fixed and 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 automatically
updated. The control point can be moved from the upstream row trailing edge to the
downstream row leading edge. If there is no upstream or no downstream row, the limit is a
straight line going from 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 the rotor/stator will be updated.
FIGURE 6.6
Control point (R,Z) control
3. Once the dialog box is opened, another control point can be selected to change its (R,Z)
coordinates. Simply left-click on it, its current coordinates will be updated in the dialog box.
4. Close the dialog box.
Export Curve
Right-click on a rotor/stator, an inlet or an outlet and select Export Curve in the popup menu to
export the selected rotor/stator in an output file (".dat").
The output file is composed by the ZR coordinates of the control points of the rotor/stator curve.
This file format can be directly read when defining a rotor/stator from external curve using the
Defined Shape/Select Geometry File button.
The file name of the output file is specified by the user via a dialog box.
Control lines can be added in meridional space to control the meridional mesh (spanwise flow
paths distribution), to change the topology of the 3D mesh (additional H block created upstream
or downstream the control line) or to impose a z constant line in the meridional space (i.e. to
capture corner). They are displayed in blue in meridional view.
FIGURE 6.7
Meridional control line example
Using this feature, the seal leakage defined at the trailing edge of a blunt centrifugal impeller can now
be connected using matching connection (see Meridional Technological Effect).
Adding two or more consecutive unfixed geometry control lines in upstream or downstream block
does not make sense and when combined with fixed geometry control line (s) that may lead to
clustering in azimuthal direction and non smooth boundaries in the concerned block.
Creation
Editing
Meridional control lines are very similar to rotor/stators. They are also defined by a set of control
points which are allowed to move on a "support curve". Therefore they can be edited in the same
manner as for rotor/stators: directly through the control points by left-clicking on it or through the
dedicated dialog box (FIGURE 6.5) by right-clicking on it and select Properties in the popup
menu.
Properties
The properties of a meridional control line can be controlled through the dedicated dialog box, the
same as for rotor/stators.
FIGURE 6.8
Control lines properties dialog box
The relaxation is interesting for z constant lines used to get a matching connection between the
channel and a zr effect where a clustering is applied on the whole z constant line to respect the zr
effect cell width at wall, giving a clustering wall in the final channel mesh.
The option is not available for inlet/outlet of a row, control lines involved in bulb, in nozzle and in a
snubber (H-topology type) on fan definition.
l Streamwise Index is used when the control line is located on a blade and specifies the index
(streamwise index) of the mesh line corresponding to the control line location in the blade to
blade view. It corresponds to the vertex index from the beginning of the inlet block along the
periodic face. The H block upstream the O4H (default) topology is not taken into account.
l Streamwise Npts is used when the control line is not located on a blade and specifies the
number of streamwise points in the H block upstream or downstream the control line in the
blade to blade view if, respectively, the control line is upstream or downstream from the blade.
l B2B control specifies if the meridional control line should also be a blade to blade control
line:
None: the meridional control line is not affecting the blade to blade mesh and allows to control
the flow paths,
FIGURE 6.9
Control lines upstream and downstream from the blade
FIGURE 6.10
Control line located on the blade
FIGURE 6.11
Non-uniform tip gap configuration
To control the mesh on the blade in the spanwise direction, control lines with B2B control set to
Partial are added on the blade. When using the B2B control: Partial, AutoGrid5™ computes
automatically two references indices along the blade mesh (one for the pressure side and one for
the suction side) to link the spanwise mesh with the shape of the Zcst line. This affects only the
mesh on the blade and therefore can be safely used in any case.
As the mesh reference indices are computed on the active layer before the 3D generation, the final
mesh depends of the active layer. In case of tip gap, it is highly advised to choose 100% for the active
layer before launching the 3d generation.
This option is available with default topology and is not available with control lines on blade in full
control mode, with cooling module, for blade on bypass.
When meshing a row with non-uniform tip gap, to improve the skewness in the tip gap the option
"hub/shroud gap interpolation" can be used instead of adding control lines on the blade with B2B
control set to Partial.
l Fixed Geometry specifies if the blade to blade control line should be a z constant line or can
be relaxed and have the shape obtained by the optimizer (blade to blade control line is
considered as a z cst line instead of a normal connection).
FIGURE 6.13
Control line blade to blade geometry
Export Curve
Right-click on a meridional control line and select Export Curve in the popup menu to export the
selected control line in an output file (".dat").
The output file is composed by the ZR coordinates of the control points of the control line curve.
This file format can be directly read when defining a control line from external curve using the
Defined Shape/Select Geometry File button.
The file name of the output file is specified by the user via a dialog box.
Meridional control lines are created automatically in three specific cases to capture discontinuity
generated by a bypass engine, a snubber (H-topology type) on fan and/or bulbs. In these three
cases, the specific meridional control lines cannot 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 its inlet and/or its outlet.
Bulbs are automatically detected, the condition being that the hub has a zero radius at one point
(not a line). The domain is automatically extended from this point at zero radius to the shroud
axial position extremity. One or two meridional control lines are automatically created, the first
one representing the machine inlet (outlet), the second one to capture either the zero radius point
for sharp topology (H-topology) or the limit between the radial and the axial domain for radial
topology. The hub extension allows to move the meridional control lines before the bulb. The
rotor/stator (inlet) of the row following the bulb is positioned after the control line capturing the
zero radius point or the limit between the radial and axial domain, and should not be moved
before it (the opposite if the bulb is at the outlet of the machine). The zone between the entry
control line and the rotor/stator is the bulb region and its meshing is controlled through a specific
dialog box dedicated to the bulb.
The type of bulb topology is automatically imposed by AutoGrid5™ depending of the value of
two angles. More details in section Bulb Control.
FIGURE 6.16
Snubber (H-topology type) case
If a control line is added between the fan and the nozzle, the user can unfix the geometry.
Nevertheless undefined or non- matching instead of matching connections can be detected at the
connection between the downstream blocks. In case of problems (non-matching or undefined patches)
the additional control line must be fixed again.
In case of a geometry defined in "millimeter", the tolerance used to define the connection in the
Patch Selector dialog box ( Grid/Boundary Conditions menu) can be increased to obtain matching
connections.
When a snubber (H- topology type) is defined, the two control lines defining the leading and the
trailing edge of the fin must be defined with a unique cell width and must be kept fixed.
FIGURE 6.17
Channel geometry check
Selection of the Check All Meridional Curves check box allows to check all the meridional
curves at once, otherwise the selected meridional curve can be checked one by one. The Check
button application computes the Minimum Distance and the Maximum Angular Deviation
between two curve control points either for all the curves or for the selected curve. While
computing for all the meridional curves, the name of the curve also appears on which the
minimum distance and maximum angular deviation exist as shown in FIGURE 6.4.
Meridional curve checking process cannot detect the discontinuity between two curves defined in the
meridional plane.
After defining the setup of the project, AutoGrid5™ will define for each selected row the number
and the distribution of the flow paths automatically when using the button Initialize Topology &
Grid Points Distribution of the top menu bar or when running the row wizard.
Afterwards, the flow paths are mainly controlled row by row and some interactions are available
between rows.
All the row parameters for flow paths control, including the number of flow paths, are accessible
through the dialog box by left-clicking on Flow Paths Control in Mesh Control subpad.
FIGURE 6.18
Flow Paths Control
The dialog box is divided in two main parts, a first part controlling flow paths spanwise
distribution and a second expert part allowing to tune some parameters, useful in some specific
cases. All parameters are applied for the selected rows.
l Flow Paths Number controls the number of flow paths in the selected row.
l Cell width at Hub controls the cell size imposed at the hub.
l Cell width at Shroud controls the cell size imposed at the shroud.
l Percentage of Mid-flow Cells controls the number of cells of constant size in the main part of
the channel (excluding gaps).
l View Flow Path allows to visualize the grid used to generate the flow paths. Deactivate the
button to display the grid.
Flow
l Paths Control Points Number controls the streamwise number of points of the grid
used to generate the flow paths. Can be increased if the machine is very long. This number of
points will also be the number of control points of the flow paths.
l Number Of Intermediate Points controls the number of discretization points between each
control point of the flow paths.
l Smoothing Steps controls the number of iterations for flow paths smoothing.
l Hub & Shroud Distribution Smoothing Steps controls the number of iterations for points
distribution smoothing.
l Hub Control Points Distribution controls the distribution of flow path control points on the
hub. The distribution can be uniform or concentrated around curvature.
l Shroud Control Points Distribution controls the distribution of flow path control points on
the shroud. It can be the same distribution as on the hub, a distribution obtained from an
orthogonal projection of the hub points on the shroud, or a distribution obtained from the
minimal distance with hub points (hub closest points on the shroud).
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
segments can be controlled. As block faces need to be created for editing, flow paths of the row to
be controlled should be generated before activating the tool.
FIGURE 6.20
Vertex displacement on vertical edge
l fixed point insertion. Right-click on a vertical edge to popup the Divide edge menu item. It
will launch the fixed point insertion tool.
l fixed point deletion. Right-click on a fixed point to popup the Delete menu item.
l fixed point displacement on vertical edges. Left-click on a fixed point to select it, move it, left-
click again to fix its new position.
FIGURE 6.21
Fixed point insertion on vertical edge
FIGURE 6.22
Manual editing activated
After each operation, faces mesh are regenerated basically (i.e. without smoothing) to display
directly the changes on flow paths shape. To regenerate completely the faces (including
smoothing), regenerate the flow 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 in the Row:Flow Paths Control dialog box ( FIGURE 6.4 ). Then flow paths
generation becomes the default one again.
Gaps are controlled through their dedicated dialog box. It allows to control the geometry and the
meshing parameters of the gap.
l Defined Shape. This button is activated if the gap curve was defined by an external curve. An
external curve can be imposed by selecting a simple ".dat" file through the button Select
Geometry File.The file is a curve defined by a set of points from leading to trailing edge.
More details on the format in section Curve data files of IGG™ User Manual.
When generating the flow paths, one flow path will respect the full imported curve. It is thus
recommended to have a curve covering the meridional minimum and maximum of the blade and
without overlap in the meridional space.
The imported gap curve cannot intersect any control lines defined outside the blade.
l Width At Leading Edge - Width At Trailing Edge. It allows to specify the size of the gap
at the leading 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 are purely for information and cannot be changed.
l Cell Width controls the cell size imposed at the blade extremity (at the hub or shroud
according to the gap type).
l Percentage of Mid-flow Cells controls the number of cells of constant size in the gap region
of the channel.
l 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 the flow paths.
The button Generate Flow Paths is used to regenerate the flow paths in the gap row respecting
the modifications done in the dialog box.
When the row is composed by several blades including different gap width or fillet radius, the
specified grid points between the various blade gap or fillet definition should remain in proportion
with the difference in width or radius (e.g. a bigger width or radius should have more grid points, so
as to have a reference flow path positioned at a higher index and avoid too much distortion when
connecting the fillet or gap blocks of the various blades).
Partial gaps are controlled through their dedicated dialog box. It allows to control the geometry
and the meshing parameters of the gap. To consider the partial gap, a mesh is first generated
considering a full gap (same spanwise parameters as in Hub/Shroud Gaps Control) and then the
mesh in the gap is split in the streamwise direction (streamwise parameters) and some blocks
removed to consider the solid part of the partial gap.
FIGURE 6.24
Partial Gap dialog box
Several limitations are due to the fact the generated mesh has to be matching (e.g. the number of
points on the blade have to be the same on lower and upper part) when adding a partial gap:
l partial gap only available for blade with default O4H topology,
l partial gap only available for rows with only one blade,
l partial gap only available for blade with following topology: high staggered at inlet and low
staggered at outlet or low staggered at inlet and high staggered at outlet or normal at inlet and
outlet.
No control line on blade is allowed if this blade contains a partial gap. In such a case, the partial gap
will not be generated and an entire gap will be generated instead.
The throat control of a blade can not be activated if this blade contains a partial gap. In such a case,
the partial gap will not be generated and an entire gap will be generated instead.
Limitations linked to full gap are applicable to partial gap except compatibility with fillet. Partial gap
is not allowed with butterfly topology fillet.
The dialog box is divided in two main parts, a first part controlling flow paths spanwise
distribution and a second part controlling the streamwise parameters.
l Spanwise Parameters:Defined Shape. This button is activated if the partial gap bounding
curve was defined by an external curve (from leading to trailing edge). An external curve can
be imposed by selecting a simple ".dat" file through the button Select Geometry File. More
details on the format in section Curve data files of IGG™ User Manual.
When generating the flow paths, one flow path will respect the full imported curve. It is thus
recommended to have a curve covering the meridional minimum and maximum of the blade and
without overlap in the meridional space.
The imported partial gap bounding curve cannot intersect any control lines defined outside the blade.
l Spanwise Parameters:Cell Width controls the cell size imposed at the blade extremity (at the
hub or shroud according to the gap type).
l Spanwise Parameters:Percentage of Mid-flow Cells controls the number of cells of constant
size in the gap region of the channel.
l Spanwise Parameters:Number of Points controls the number of points in the gap in the
spanwise direction.
l Streamwise Parameters:Graphic controls the streamwise bounds of the partial gap and the
number of points in streamwise direction. The bounds are defined from the leading/trailing
edge as a distance in percentage of the mean line length, with mean line being the middle
curve between the suction and pressure sides.
If the LE/TE partial gap length is the same between hub and shroud, AutoGrid5™ will use
automatically the same number of LE/TE points on both hub and shroud partial gap.
If the sum of the leading and trailing edge distance reaches 100% of the mean line length, then the
gap mesh is generated as a classic gap.
A pop-up message will appear if the sum of the two number of points is higher than the number of
points on blade. When changing the number of points on blade in Define B2B Topology For Active
Blade dialog box, then the partial gap will not be generated and a full gap will be generated instead.
In the next figure, one can clearly see on this picture the inlet points that are projected on the blade.
When defining a partial chord gap, if the leading edge distance is too low, so that the gap blocks
should be cut in the inlet points projection area, the mesh can not be generated. In such case, if the
defined partial mean line length is too low, it is automatically reset to 0 (i.e. no partial gap at inlet),
and a warning message appears to inform the user. The same comment can be done for the trailing
edge region and the outlet points projected on the blade.
When two partial gaps have been defined on the same blade, the associated number of points and
the leading/trailing edge distances must fulfill some restrictions (if not respected, warning will pop
up):
The partial gap will follow the curvature of the cylinder, as can be seen in the following figure:
If the option is deactivated, then the partial gap is not respecting the cylinder definition and is
generated using the classical algorithm: the same chord length percentages for all layers.
In case the algorithm fails to compute an intersection between the cylinder and the reference flow
path surface of revolution, a warning message appears at the bottom of the dialog box:
Invalid input. Please Check Cylinder Parameters
In order to generate a partial gap defined by a cylinder, there has to be an intersection of the
cylinder with both sides of the blade for all spanwise layers of the partial gap. If this is not the
case, an error message will appear, warning the user that the imposed cylinder is not suitable. In
this case, the partial gap will be generated using straight edges.
Generating a partial gap defined by a cylinder is not compatible with z constant lines with partial
B2B control. If these are found, a pop-up message and a warning message are displayed and the
partial gap is generated using straight edges. If the B2B control of these z constant lines is set to
'None', the partial gap can be generated following the shape of the cylinder.
If the number of LE/TE points is the same between hub and shroud, the streamwise cell width on both
hub and shroud is driven only by the width defined for hub gap.
The cell width expansion may lead to bad mesh quality if there is not enough space on blade to
expand the partial gap cell width with the given expansion factor. Reasonable expansion factor with
respect to the geometry should therefore be defined.
The buttons Show /Hide allow to preview the user defined bounding curve used for the gap
before generating the flow paths.
The button Generate Flow Paths is used to regenerate the flow paths in the gap row respecting
the modifications done in the dialog box.
Fillets are controlled through their dedicated dialog box. It allows to control the geometry and the
meshing parameters of the fillet.
The dialog box is divided in three main parts, a first part controlling flow paths spanwise
distribution, a second part controlling the mesh topology in the fillet and a third part controlling
the fillet geometry creation.
When generating the flow paths, one flow path will respect the full imported curve. It is thus
recommended to have a curve covering the meridional minimum and maximum of the blade and
without overlap in the meridional space.
The imported spanwise bounding curve cannot intersect any control lines defined outside the
blade.
When the fillet is incorporated in the blade definition (either in native ".geomTurbo" or through
Import CAD window ( Link to Blade )), the specified radii or meridional curve should be
imposed in the area of the blade-fillet junction (can be approximative).
l Spanwise Parameters:Cell Width At Leading/Trailing Edge controls the cell size imposed
at the junction between the straight blade and the fillet (at the hub or shroud according to the
fillet type) on all the control lines before the leading edge (Cell Width At Leading Edge) and
on all the control lines after the trailing edge (Cell Width At Trailing Edge). By default set to
0.0 to allow AutoGrid5™ to compute an optimized value at the leading and trailing edge.
l Spanwise Parameters:Percentage of Mid-flow Cells controls the number of cells of constant
size in the fillet region of the channel.
l Spanwise Parameters:Number of Points controls the number of points in the fillet in the
spanwise direction.
l Topology:Butterfly. This button is activated to mesh the fillet with a butterfly topology. In
this approach a first mesh is generated considering a straight blade. Then the skin block is split
at the fillet meridional layer, the block in the fillet area is replaced by a butterfly topology
respecting the created or imported fillet geometry. If the skin block of the O4H default mesh is
thicker than the fillet, the endwall is partly included in the butterfly topology and the same
treatment is applied everywhere. While if the fillet is thicker than the skin block, the butterfly
topology is applied in the skin block and out of this block a non-axisymmetric treatment is
performed.
The Butterfly Radial Number of Points parameter directly influences the grid quality in general
and the grid point distribution on the fillet in particular. It determines in the fillet the number of
points and therefore the distances marked by the curly brackets in the following figure. To keep
the matching connection with the surrounding blocks, the grid point distribution on the two
corresponding edges is not changed by the generation of the butterfly topology.
When increasing the Butterfly Radial Number of Points parameter, at some moment the
orthogonality in the fillet will start to decrease because of quite dissymmetric fillet section (a side
is largely wider than the other) as presented in the following figure.
The butterfly topology is not compatible with blunt blade. Even if the fillet geometry is imported
through the Import CAD window, the radii at the leading and trailing edges will not be respected. It
will be redefined automatically by AutoGrid5™ using the computed values instead.
The butterfly topology is not compatible with cooling options (e.g. blade holes, basin, radial holes,...),
blade sheet, partial gap and HOH/H&I(without skin block) topologies.
The fillet without butterfly topology is not allowed with the rounded treatment at leading/trailing
edge ( Blend/Sharp/Rounded Treatment at Leading/Trailing Edge ) and thus not allowed for HOH
topology on a blade with a blunt at leading/trailing edge.
For the mesh control of the bulb, more details are presented in Specific Cases: Bypass, Fin &
Bulb. Two specific dialog boxes are 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.
The type of bulb topology is automatically imposed by AutoGrid5™ depending of the value of
two angles:
l the angle formed by the segment between the first/last point of the hub and the intersection
point between the leading/trailing edge of the blade and the hub curve.
l the angle formed by the two first/last points of the hub with axis of rotation.
If the first angle is greater than 80 degrees, then the topology is radial. If it is not the case, then the
second angle is used. If it is lower than 45 degrees, the sharp topology is used otherwise the
rounded topology is used.
l With the sharp topology, the mesh in the bulb area is divided into two blocks limited by the
inlet of the row and the bulb domain limit and separated by the stagnation line. This topology
leads to a mesh presenting a singular line in front of the stagnation point.
l With the rounded topology, the bulb area can be meshed with a singular line (triangular cells)
or a butterfly topology. The mesh is then divided into respectively 3 or 5 blocks limited by the
inlet of the row and the bulb domain limit.
l With the radial topology, the mesh in the bulb area is divided into two butterfly topology: a
butterfly topology for the radial area of the bulb domain and one for the streamwise area of the
domain.
The Butterfly Smoothing Steps controls the number of iterations to smooth the butterfly bulb
area.
The number of points in azimuthal direction is controlled by the blade- to- blade mesh of the row
upstream/downstream the bulb (if bulb at respectively outlet/inlet). Grid points (in Define B2B
Topology For Active Blade dialog box) at respectively outlet or inlet of the row (if bulb at
outlet/inlet) will control the azimuthal number of points in bulb and it is recommended to impose
middle value (leading/trailing edge control) as 8n+1 to guarantee 3 grid levels.
The button Preview Flow Paths is used to regenerate the flow paths in the bulb respecting the
modifications done in the dialog box.
If meridional control lines are added in the bulb, the number of points is controlled in addition
through the dialog box Row Interface Properties ( FIGURE 6.5 ). The Streamwise 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.
For the geometry control of the by-pass, more details are presented in section Specific Cases:
Bypass, Fin & Bulb. Two topologies are available for by-pass: H or C mesh around the nozzle
(also called radial splitter or splitter nose). A specific dialog box is dedicated to by-pass ( ):
l Topology Type allows to choose the H or C topology.
l Nozzle Cell Width controls the cell size imposed at the nozzle.
l Nozzle Index controls the index of the flow path corresponding to the stagnation point of the
nozzle, i.e. it controls the proportion of the flow paths below and above the nozzle.
l Inlet Distribution Relaxation allows the user to relax the flow path clustering coming from
the nozzle at the inlet. The inlet distribution relaxation is controlled by a parameter, ranging
from 0 to 1. If the parameter is set to 0 (default), the same spacing as on the nozzle is
maintained. If the parameter is set to 1, the flow paths will be placed according to a uniform
distribution at the inlet. In practice, small values of the inlet distribution relaxation parameter,
typically below 0.5, will enable a sufficiently relaxed inlet distribution. The inlet relaxation is
propagated up to the inlet or rotor/ stator interface of the row directly upstream of the nozzle.
FIGURE 6.26
Bypass dialog box with H topology
FIGURE 6.27
Bypass dialog box with C topology
Besides the number of points, two additional controls are available: the C mesh thickness and the
spacing between meridional control lines on the nozzle, both are expressed as a percentage. For
the C mesh thickness, it is a percentage of the spanwise size below the nozzle, for the spacing
between control lines, it is a percentage of the nozzle thickness (nozzle thickness is a dimension
automatically computed according to the geometry).
The dialog box also displays information about the total number of flow paths in the by-pass:
number of flow paths before the nozzle, downstream and upstream from the nozzle. It allows an
easier generation of a 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 modifications done in the dialog box.
FIGURE 6.28
C-mesh (left) & H-mesh (right) topology around nozzle
A snubber on a blade is controlled through the dedicated dialog box. It allows to control the
meshing parameters of the snubber.
l Topology Type: H. This topology is kept for backward when loading old project with a
configuration fin on fan (bypass) generated before AutoGrid5™ v11.1. For the geometry and
the meridional controls of the snubber (H-topology type), more details are presented in sections
Snubber and Specific Cases: Bypass, Snubber & Bulb. When H-topology, the only meshing
parameters in the Snubber Properties dialog box are the Spanwise Index and the Cell
Width.
When starting a new project, the H- topology is not available and the O- topology will be
automatically applied.
The IJK orientation of the skin blocks in the snubber will be the same as for the blade skin block: I
perpendicular to the snubber wall, K around the snubber and J azimuthal.
When a snubber (O-topology type) is defined, an additional block is created in the meridional
view to control the flow paths. Its number of points is controlled in the Snubber Properties
dialog box with the parameters Spanwise Index (the middle of the snubber block) and the
spanwise number of points in the graphic.
FIGURE 6.30
Flow paths control
The block boundaries can be moved and controlled manually in the meridional view using the button
Manual Edit of the Row:Flow Paths Control dialog box (more details in Flow Paths Manual
Editing).
l Spanwise Index controls the index of the flow path corresponding to the stagnation point of
the snubber. It is automatically recomputed when doing a reset default topology or launching a
row wizard. The index corresponds to the number of flow paths divided by 2 (then adapted to
respect multigrid levels).
In case of a bypass configuration it is computed such that it will be always above the nozzle (nozzle
index + (number of flow paths - nozzle index)/2).
It is recommended to optimize the mesh (before the snubber post-processing) using the full multigrid
and fine grid optimization in the Optimization Properties dialog box.
l Leading/Trailing Edge Relative Control Distance. A snubber can be seen as a blade and its
streamwise points distribution will be controlled from leading edge to trailing edge. On some
distance at leading and trailing edge, a uniform distribution with a spanwise number of points
is applied. This distance is controlled independently at leading and trailing edge with these
parameters.
l Fillet Butterfly Radial Number of Points . When the 3D geometry of the snubber is
including a fillet, a first mesh is generated considering the snubber without fillet. Then the
snubber skin block is split at a computed azimuthal layer, the block in the fillet area is replaced
by a butterfly topology respecting the imported fillet geometry.
The Fillet Butterfly Radial Number of Points parameter controls the radial number of points in
buffer blocks of the butterfly topology. By default the value is set to 0 to allow AutoGrid5™ to
compute an optimized value. When the value is imposed by the user, the streamwise number of
points in the inner block of the butterfly topology will be the difference between the snubber skin
block number of points and the Fillet Butterfly Radial Number of Points.
FIGURE 6.31
Fillet on snubber
When increasing the Fillet Butterfly Radial Number of Points parameter, the cell size in the
middle of the fillet surface will increase while the total number of points on the fillet surface will
decrease and at some moment the orthogonality in the fillet will start to decrease because of quite
dissymmetric fillet section (a side is largely wider than the other). More details at the end of the
Blade Fillet.
When increasing the blade number of points, the streamwise number of points on the snubber is
increasing while the streamwise upstream and downstream number of points are kept.
As the generated mesh will be fully matching, the streamwise distribution in the snubber should
reflect as much as possible the snubber geometric size and positioning compare to the blade. Some
deviation is allowed but deviating too much from the ideal distribution (computed by AutoGrid5™
when initializing topology & grid points distribution or running the row wizard) will decrease the
mesh quality. This distribution is automatically computed when initializing topology & grid points
distribution or running the wizard.
Besides the flow paths generation row by row, the copy-merge options allow to obtain matching
flow 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 meridional
control line.
Merge is used to compute a common distribution from the left and right distributions at a
rotor/stator. 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
meridional control line:
Conditions of Use
FIGURE 6.32
Forbidden copy-merge operations
Copy-merge operations are symbolized in the meridional view by a text marker on the middle of
the rotor/stators or meridional control lines:
l C -> L means that the distribution on the left side of the rotor/stator was copied.
l C -> R means that the distribution on the right side of the rotor/stator was copied.
l <- C -> means that the distribution on both sides of the rotor/stator was copied.
l M means that distributions on the rotor/stator were merged.
l C means that the distribution on the meridional control line was copied.
FIGURE 6.33
Copy-merge meridional representations
When the meridional view is active (red border), the menu Grid/Grid Quality allows to control
the quality of the flow paths.
The 3D mesh created by AutoGrid5™ is obtained by stacking blade to blade meshes on the surfaces of
revolution (layers) created by rotation of the flow paths defined in the meridional view of the
turbomachinery.
The blade to blade meshes are created in the (dm/r,theta) space: the cross-sections of the blades with
the active layers are projected in the blade to blade space and the mesh is created around the blade
sections according to the pitch angle and the inlet and outlet boundaries of the row (more details in
Meshing Fundamentals).
FIGURE 7.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 are created
by transfinite interpolation and finally optimized using an elliptic multiblock smoother.
AutoGrid5™ provides predefined topologies for which grid points clustering is chosen automatically
according to some geometrical criteria and grid level. The predefined topologies have been developed
to obtain high quality grid without any user interaction. They are divided in three main types: HHOHH
(O4H), HOH and H&I. The O4H type ensures full automatic meshing for all kinds of turbomachinery
while the HOH and H&I types give very high quality grids but are not suitable for all the applications.
Afterwards, the user can interact to change the resulting topology.
For all topologies, the template approach of AutoGrid5™ ensures reusability of the automatic or
manual settings on similar geometries.
This chapter describes first how to set up a predefined topology and how the user can interact to
change the optimized blade to blade topology defined by AutoGrid5™. Finally, the optimization
controls are described.
In this section
7.1 Blade to Blade Topology Management 334
7.2 Default Topology (O4H Topology) 339
7.3 HOH Topology 376
7.4 H&I Topology 383
7.5 Blade to Blade Optimization 395
Overview
The selection of the predefined blade to blade topology is controlled through the dialog box
available through the menu Mesh Control/Row Mesh Control/B2B Mesh Topology Control
in the Quick Access Pad.
FIGURE 7.3
Define B2B Topology
Topology Selection
On the top of the Define B2B Topology for Active Blade dialog box, the topology of the selected
blade can be selected between the three predefined types available in AutoGrid5™(O4H, HOH
and H&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, AutoGrid5™ will create an optimized topology
according to some geometrical criterion and the grid level (Number Of Grid Levels in the menu
Mesh Control/Grid Level/Detailed Control) when using the button Initialize Topology & Grid
Points Distribution of the top menu bar.
Afterwards, the options Streamwise Weights in the menu Mesh Control/Grid Level/Detailed
Control allow to increase the number of grid points in the streamwise direction respectively at the
inlet, on the blade and the outlet of the optimized topology. The feature consists in multiplying the
number of grid points at inlet, on the blade and at outlet by the streamwise weights when using
the button Initialize Topology & Grid Points Distribution. 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 by
AutoGrid5™ by changing the parameters in the Define B2B Topology for Active Blade dialog
box (from "Default Topology (O4H Topology)" (p. 339) to 7- 5) and in the Optimization
Properties dialog box ("Blade to Blade Optimization" (p. 395)).
In addition, the topology library on the top of the Define B2B Topology for Active Blade dialog
box (FIGURE 7.3) can be used or an existing topology can be copied ("Copy/Paste Topology"
(p. 338)).
In this dialog box, the user can overwrite a topology selected in the list or create a new item in the
library by switching on the button New B2B topology name. In this case, a new topology name
must be entered in the related area and the topology will appear in the topology library and will be
saved in "~/.numeca/tmp/" (in the folder "/_ NITurboB2BTopologyLibrary/" and in the file
"NIbladeToBladeTemplateLibraryFiles").
l Remove a topology from the list (Remove button)
l Preview the selected topology (Preview button): this feature opens a new window inside
which a picture of the selected topology is displayed.
Furthermore, in the popup menu of the row, a row topology library is available through the
Topology/Library menu.
In this dialog box, the topology of the selected row can be selected from the blade to blade row
topology library. This library contains all the previous saved row topologies. The library is
managed using the following features:
l Select a topology: to load a predefined topology, select it in the list and press the button Load.
A warning prompts the user to regenerate and display the mesh in the blade to blade view.
l Save a topology: To save the topology of the current active row, press the button Save. The
dialog box Save Row Topology is opened. In this dialog box, the user can overwrite a
topology selected in the list or create a new item in the library by switching on the button New
Row topology name. In this case, a new topology name must be entered in the related area and
the topology will appear in the topology library and will be saved in "~/.numeca/tmp/" (in the
folder "/_NITurboRowLibrary/" and in the file "NRowTemplateLibraryFiles").
l Remove a topology from the list (Remove button)
l Preview the selected topology (Preview button): this feature opens a new window inside
which a picture of the selected topology is displayed.
The blade to blade library is used to apply the topology from one row to another. To copy the blade
to blade topology from one blade to another, the Topology/Copy and Topology/Paste options of the
blade menu should be used (see "Copy/Paste Topology" (p. 338)).
Copy/Paste Topology
The blade to blade topology applied around a blade row or a row can be copied into the active
buffer and applied to other blade row or row using the copy/paste feature available through the
contextual menu of the blade and the row.
FIGURE 7.5
Blade & row contextual menu
Using this feature, In multistage configuration, the blade to blade topology can be set up for one
blade or row and applied to all the other similar blades or rows.
For the rows, the following settings will be copied:
l the meridional topology;
l the flow paths settings;
l the optimization settings;
l the row clustering;
l the span interpolation;
l the desired accuracy and number of points.
For the blades, the following settings will be copied:
l the blade sheet settings;
l the tip and hub gap settings;
l the tip & hub fillet settings;
l the blade-to-blade topology;
l the blade clustering.
The predefined topology applied from scratch or selected in the library or copied on the blades of the
active row(s) is (re)initialized using the button Initialize Topology & Grid Points Distribution. An
optimized blade to blade topology is chosen and the grid points distributions are (re)computed based
on the setup of the project, the grid level and the geometrical criterion.
The default topology is selected through the top left selection button of the dialog box Define B2B
Topology For Active Blade.
FIGURE 7.6
Default topology selection
When using the row wizard for the wind turbine, marine propeller, axial fan or contra rotating fan,
new types of default topology are available in addition to the default one named Streamwise:
Rounded Streamwise and Rounded Azimuthal.
FIGURE 7.8
Default topology types
The Rounded Streamwise topology is imposing a rounded topology at the trailing edge and is
similar to the Streamwise topology when rounded treatment at blunt trailing edge is applied or
when the blade is not blunt. Only the block boundaries are slightly different at the trailing edge.
The grid points number depends of the grid level and the streamwise weights chosen in the quick
access pad page Mesh Control/Grid Level before performing the initialization ( Initialize
Topology & Grid Points Distribution).
These optimized grid points numbers can be changed in the Grid Points page of the dialog box
Define B2B Topology For Active Blade (FIGURE 7.7). To change a number, left-click on it,
enter the new number of points in the locally displayed input area and <Enter> to confirm or
<Esc> to cancel the action.
To display the new blade to blade mesh, press the button of the top menu bar Generate B2B.
FIGURE 7.10
Default mesh
As shown in FIGURE 7.10, the periodic boundary of the default mesh is non-matching.
To obtain a matching periodic boundary condition:
1. Switch on the check button Matching Periodicity in the Topology page of the dialog box
Define B2B Topology For Active Blade.
2. Press the button Initialize Topology & Grid Points Distribution or Generate B2B.
3. In case of splitter blades (multi-blade configuration) notice that the previous two steps also
ensure a matching connection between the blades. The matching connections will remain
enforced if the grid points distribution or the blunt treatment are adapted manually.
The O-block around the blade is used to optimize the control of the boundary layer on the blade.
It is created using an hyperbolic mesh.
The number of grid points along the solid wall is controlled within the page Grid Points of the
dialog box Define B2B Topology For Active Blade. The grid points clustering along the solid
wall is split in four pieces controlling the leading edge, the trailing edge, the upper side and the
lower side of the blade.
FIGURE 7.13
Grid points number control
If the high staggered topology (more details in section "Topology for High Staggered Blades" (p.
361)) is not used, additional blue control boxes are available to modify the distribution of the
number of points between the inlet, the outlet and the blade.
The clustering near the leading edge and/or the trailing edge can be fully controlled through the
dialog box Blade Clustering Control. When moving the mouse near the leading edge or the
trailing edge, the piece of clustering controlled is automatically highlighted. The length of the
piece is named "control distance". The inlet/outlet grid points are uniformly distributed along this
distance.
FIGURE 7.15
Leading edge control distance
Right- clicking when a control distance is highlighted opens a contextual menu. The menu
Properties opens the dialog box Blade Clustering Control.
The control distance along which the grid points are distributed can be modified by selecting the
mode of specification and the distance value:
1. Absolute Control Distance: the distance is given in absolute units and remain the same for
each layer.
2. Relative Control Distance: the distance is given in relative units (normalized with the blade
width).
3. First Cell Length: the distance is equal to the product of the cell width given by the user and
the number of nodes.
The control distance is combined with a percentage of cells along the blade that will present a
constant size (Percentage Cst Cells).
Another feature of this dialog box gives the control of the maximum expansion ratio of the cells in
the streamwise direction along the wall. Switch on the button Desired Expansion Ratio implies
that the number of grid points on the upper and lower side of the blade will be recomputed to
ensure that the expansion ratio remain lower than the target value. The total number of points
around the blade is then continuously updated.
When moving the mouse near the leading or trailing edge, the control distance is highlighted
indicating that it is ready for selection. Left-click (without release) and drag it on the desired
location then release. The mesh of the skin block is continuously updated during the moving
process.
The skin block is created using a hyperbolic mesh. The width of the boundary layer in the initial
mesh before optimization is controlled by the cell width at the wall, the expansion ratio and the
number of points in it. These parameters can be modified in the page Mesh and Grid Points of
the dialog box Define B2B Topology.
During the optimization step, the smoother will modify the grid points distribution of the blade-to-
blade mesh layers to reach a higher mesh quality. The parameter Skin Block Expansion Ratio
Control (%) allows to bring additional constraints to the smoother to better control the skin block
layers.
l When the parameter is set to 0 (corresponding to the behavior before this parameter was
introduced), a default number of skin block layers, about half of them, starting from the blade,
will be constrained to respect the imposed expansion ratio together with the orthogonality to
the blade.
l When the parameter is set to 100, the remaining skin block layers will be constrained not to
exceed the imposed expansion ratio.
The parameter Skin Block Expansion Ratio Control (%) applies only to the skin block, therefore
it will have no influence on blunt boundary layers, neither on H&I topology without skin block.
For rounded topology at trailing edge (i.e. Kaplan or Francis turbine wizard), when the parameter
Skin Block Expansion Ratio Control (%) is set to 0, the additional constraints to the smoother are
applied to all the layers in the skin block except the last three ones.
When AutoGrid5™ detects that the boundary layer width is too big for the geometry configuration, it
prompts the user to confirm the automatic reevaluation of the expansion ratio to a correct value.
When the blade section has a curved shape, crossing grid lines in the hyperbolic mesh can be detected
by AutoGrid5™ and it automatically prompts the user to change the expansion ratio manually to
avoid crossing section.
When activating the option Cell Width at Wall Interpolation, AutoGrid5™ allows to impose a
cell width different at the hub & shroud of the machine, especially when the speed of the flow
becomes very different at the hub and at the shroud of the machine.
When full or partial gap(s) has been defined, AutoGrid5™ adds automatically two new blocks to
mesh the domain up or down to the blade(s). The mesh inside a gap has a butterfly topology: a H
block surrounded by a O block are used to discretize this area. When the gap is partial the two
blocks are split in maximum five blocks.
By default, the gap meshes matches the skin mesh around the blade. Therefore, the only control
gives to the user is the number of points inside the O-block that can be modified in the page Grid
Points of the dialog 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 a gap
has to be defined, the change is canceled automatically by AutoGrid5™ when pressing the button
Generate B2B to ensure a matching connection between the gap meshes and the skin mesh around
the blade.
In case of blunt blades, AutoGrid5™ automatically detects the bluntness of the blade and the
option to blend, sharp the blunt blade leading/trailing edge or rounded the blunt blade trailing
edge appear in the Topology page of the Define B2B Topology for Active Blade dialog box.
The selection of the options Sharp Treatment At Leading Edge and Sharp Treatment At
Trailing Edge replaces the local topology by two H blocks. The option is recommended for
inducer configuration.
FIGURE 7.21
Effect of sharp leading/trailing edge treatment
The selection of the options Blend the Blade At Leading Edge and Blend the Blade At
Trailing Edge automatically closes the blunt edges by a circular shape edges as shown in
FIGURE 7.22. When these treatments are activated in the GUI, the keywords "BLENT_AT_
LEADING_EDGE" and "BLENT_AT_TRAILING_EDGE" are saved in the ".geomTurbo"
file.
The selection of the option Rounded Treatment At Trailing Edge replaces the local H-mesh
topology by an O-mesh around the blade.
FIGURE 7.23
Effect of rounded treatment at leading/trailing edge
AutoGrid5™ allows an automatic control of the number of grids points in the throat by setting the
Number of Points In Throat to 1. This parameter can be modified in the page Grid Points of
the dialog box Define B2B Topology for Active Blade and is controlling part of the number of
points along the blade as presented on next figure.
FIGURE 7.24
Number of points in throat
For example, when dealing with inducer configuration, in the Define B2B Topology for Active
Blade dialog box:
l The Matching Periodicity and the High Staggered modes with High-Low or Low-High
Inlet/Outlet Type are imposed in the Topology page,
l The Number of Points in Throat is set to 1 to optimize the blade to blade mesh by an
automatic control of the blade points distribution in the throat.
Backward is ensured with the previous releases in which the grid points were imposed manually in
the throat.
When Number of Points In Throat is set to 1, the leading and trailing edge clustering is
projected on the opposite side of the blade using an algorithm using the blade staggered angle.
When the staggered angle is significantly different at inlet and outlet, the option Accurate throat
projection can be activated to improve the projection location.
This option projects the leading and trailing edge on the other blade. When the throat angle is
important and the pitch angle relatively large compare to the blade length, there may be simply no
intersection or very close to the leading or trailing edge. This is resulting to a poor quality mesh or a
too high concentration of points at leading/trailing edge.
The parameters Inlet/Outlet Projection Relaxation can be used to relax the clustering at the
projection location especially when the blade is blunt. It allows to control manually the projection
points clustering of the blade by multiplying the default clustering with the value specified in the
entry.
The direction of the mesh downstream the trailing edge can be controlled to capture the wake. By
default the wake control is switch off. When the Wake Control check box is selected, the Wake
Relative Angle can be imposed in the page Mesh of the dialog box Define B2B Topology for
Active Blade. The edges of the outlet block are created using straight lines. The angle between
these straight lines and the dm/r axis is equal to the solid angle + the wake relative angle specified
in the dialog box. FIGURE 7.25 describes the geometrical detail and the mesh control when
modifying the wake relative angle feature.
FIGURE 7.25
Wake control - relative angle
Furthermore, the Wake Prolongation in Downstream Block check box allows to propagate the
wake in the downstream H-block (created when a control line is added downstream the trailing
edge of the blade). It improves the quality of the mesh downstream of the trailing edge.
If the wake control is activated, the outlet angular position is indirectly fixed and the outlet angle
cannot be imposed anymore.
The inlet and outlet boundaries of the blade to blade mesh are located at theta positions computed
automatically 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.27
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
affected along the spanwise direction. To avoid this phenomenon at the inlet/outlet boundary limit
of the mesh, new controls have been added in the Mesh page of the dialog box Define B2B
Topology for Active Blade. If the Free Inlet/Outlet Angle mode is switched off, the user can
freeze the inlet/outlet angle and mesh using respectively the Frozen Inlet/Outlet Angle and the
Frozen Inlet/Outlet Mesh options. These options constrain the inlet/outlet optimization and force
the mesh at the boundary.
When Z cst lines are defined upstream or downstream to the blade, upstream and downstream H-
blocks are created. By default the azimuthal clustering at the control line is extended up to the
inlet or the outlet in the blade-to-blade mesh.
In case Z cst lines are defined upstream or downstream to the blade, AutoGrid5™ automatically
detects the control lines and new options are available in the Mesh page in the Define B2B
Topology for Active Blade dialog box.
In case of blunt blades, AutoGrid5™ automatically detects the bluntness of the blade and new
options are available in the Mesh page in the Define B2B Topology for Active Blade dialog
box.
l ZCst line at Leading Edge: Selection of this option defines a Z constant line at the leading
edge.
l ZCst line at Trailing Edge: Selection of this option defines a Z constant line at the trailing
edge.
Zcst line at the leading edge or trailing edge cannot be combined with respectively high staggered
topology at the leading or trailing edge.
Zcst line should be added at the leading or trailing edge location in the meridional view to ensure that
the flow paths are respecting the shape of the hub and shroud at the leading or trailing edge. The B2B
control option of this control line should be deactivated.
l Cell Width At Leading Edge: This entry allows the user to specify the width of the cell at the
blunt leading edge. By default the value is set to the cell width value imposed under Mesh
Control/Row Mesh Control in the Quick Access Pad or in the Row Wizard. When the
value is set to -1, the value will be calculated from a uniform distribution on this edge using the
leading edge number of points.
l Cell Width At Trailing Edge: This entry allows the user to specify the width of the cell at the
blunt trailing edge. By default the value is set to the cell width value imposed under Mesh
Control/Row Mesh Control in the Quick Access Pad or in the Row Wizard. When the
value is set to -1, the value will be calculated from a uniform distribution on this edge using the
trailing edge number of points.
Overview
In several turbomachinery types, the blades are highly staggered. If the solid angle at the inlet
(outlet) of the machine becomes greater than 45° and if the location of the inlet (outlet) limits of
the domain is close to the leading edge (trailing edge) of the blades, then the O4H topology is not
suitable anymore: the cells located near the inlet (outlet) boundary becomes very skewed.
To improve this unexpected behavior, AutoGrid5™ uses the High Staggered Blade
Optimization in the Topology page of the dialog box Define B2B Topology for Active Blade
(FIGURE 7.32).
FIGURE 7.31
C topology at inlet
When the topology is (re)initialized using the button ( Initialize Topology & Grid Points
Distribution , AutoGrid5™ detects if the two conditions described in the FIGURE 7.30 are
reached. In this case, AutoGrid5™ automatically adapts the default topology to optimize the grid
quality: if the solid angle at inlet is lower than 0, the H upper block becomes a C-block.
FIGURE 7.32
High staggered optimization control
The next figure is presenting the description of the different types of geometrical configuration
and their corresponding inlet and outlet types.
When a C-mesh is defining the upper block at inlet, the grid point number on the upper side of the
blade 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, the
number of points N1 is always different of N3. Therefore, if a gap mesh is defined, a non-
matching connection will be automatically used to create the connection between the H-block and
the O-block inside the butterfly mesh.
l two rows (main blade with or without splitter(s)) without overlap in the streamwise direction
(Tandem Row set to With Next/With Previous).
When Tandem Row is set to Yes, the blade to blade control will adapt the grid points distribution
along the main blade and the splitter as presented on next figure.
Multi-Rows Configuration
When Tandem Row is set to With Previous/With Next , a tandem configuration will be
considered between the two selected rows.
In order to be able to obtain full matching mesh between both rows, the number of flow paths and
the flow paths distribution at the rows interface must be equal. This will lead to continuous flow
paths between row1 and row2.
To obtain full matching mesh in the B2B plane, two unfixed control lines are required upstream
and downstream the interface of the rows.
In addition, the number of point in the azimuthal direction at the interface between both rows must
be the same. In the Grid Points section of the dialog box Define B2B Topology for Active Blade,
a message indicates to the user the number of points at the connection in both rows.
When left-clicking on the button Initialize Topology & Grid Points Distribution of the top menu
bar, the process does not perform checks and grid manipulation to assume correct linking of
tandem rows. The user has to manually check and change the grid point distribution to assume
same azimuthal grid point number at the interface between both rows otherwise a warning
appears.
To ensure a full matching mesh, the optimization parameters of both rows are strictly linked
together.
The control lines are defined in the meridional view to capture discontinuities of the hub and/or of
the shroud. These lines can be defined upstream, downstream or on the blade(s) definition.
FIGURE 7.36
Control lines
By default, the control lines are taken into account in the blade to blade meshing process. The
intersection 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
locations.
FIGURE 7.37
Blade to blade mesh with control lines
FIGURE 7.38
Control line control
Upstream and downstream control line implies that new H blocks will be added before the inlet or
after the outlet of the O4H topology. The number of points in the azimuthal direction is implicitly
defined by the connection with the blocks of the O4H topology. The number of points in the
streamwise direction n1 and n2 (FIGURE 7.39) are controlled by the parameter Streamwise
Npts in the dialog box Row Interface Properties (FIGURE 7.38) or by right-clicking on the H
block in the blade to blade view and selecting the Number of Pts Streamwise menu.
Adding two or more consecutive unfixed geometry control lines in upstream or downstream block
does not make sense and when combined with fixed geometry control line (s) that may lead to
clustering in azimtuthal direction and non smooth boundaries in the concerned block.
When a control line is defined on a blade, the parameters Streamwise Index of the dialog box
Row Interface Properties (FIGURE 7.38) controls the index of the grid points along the blade
distribution linked to the control line (FIGURE 7.40). By default, its value is equal to "0" and the
new control line is not taken into account. When new control line has to be defined on the blade,
it is advised to perform the Initialize Topology & Grid Points Distribution process which
computes default value for the streamwise index of the new control line.
The parameter Cell width of the dialog box Row Interface Properties (FIGURE 7.38) controls
the cell width in the streamwise direction around the control line. By default the value is set to
"0.0" and AutoGrid5™ computes the most appropriated value automatically.
The parameters Relaxation Location / Relaxation Factor of the dialog box Row Interface
Properties (FIGURE 7.38) control the relaxation of the cell width in the streamwise direction
around the control line. By default the relaxation is not applied (Relaxation Location set to
None).
For high staggered blades, new topology is automatically select by AutoGrid5™ if two conditions
are reached (FIGURE 7.30). When the upstream domain and/or the downstream domain are
large, the second condition is not reached and the high staggered optimization not selected. A
method to ensure the selection of the high staggered optimization consists of creating control lines
upstream the blade near the leading edge and downstream the blade near the trailing edge. In this
condition, AutoGrid5™ will choose the high staggered optimization. By adding these new
control lines, we add also constraints into the blade to blade mesh definition (vertical grid lines for
each control line). These constraints can be suppressed by switching off the Fixed Geometry
option in the dialog box Row Interface Properties (FIGURE 7.38).
FIGURE 7.41
Control lines improve mesh quality
In AutoGrid5™, the dialog box Define B2B Topology For Active Blade contains a page
Intersection Control.
FIGURE 7.42
Intersection control parameters
These parameters allow in specific cases to control the intersection between the blade and the
flow paths performed during the transformation made from 3D space to 2D blade-to-blade space
and from 2D domain to 3D space. This intersection is defined by control points (with a certain
distribution along the blade) and a number of points in between each control points. This curve
describing the blade in 2D blade- to- blade space is then used to create the mesh and then
transformation to 3D domain 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. In AutoGrid5™ the differences in geometry are so small that in general the impact on
the solution is much smaller than the use of discretization in a mesh due to the size of cells and the
location of the grid points. Nevertheless AutoGrid5™ allows to use more points to compute the
intersection and in that way to reduce these differences even more. This is at the cost of a much
longer mesh generation process.
In few words the Intersection Control parameters control the way the intersections are defined
between the geometry of the blade and any axisymmetric surface defined by the flow path.
The Intersection Quality parameter allows to choose the algorithm used to compute the
intersections:
l Low mode is only available when the row blades geometry is defined by a native format
(pressure and suctions sides defined by a set of sections in the ".geomTurbo" file). This mode
uses SISL library.
l High mode uses Parasolid™ library. This mode is very precise but maybe more time
consuming.
The Intersection Number of Points parameter controls the number of discretization points
between control points defining the intersection curve. This parameter is not used in Low mode
with Curvature distribution.
If the geometry is not very well defined and contains some small discontinuities, then it is
recommended NOT to use a Curvature distribution. Because this type of distribution will result in a
concentration of control points in the small area of the discontinuity, leading 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, the Low mode
used by default for native ".geomTurbo" file can be switch to High mode before regenerating the
mesh.
In bypass configuration, the High mode intersection should be applied on the row on the nozzle if
any.
When High mode intersection, for blunt blades, there is no check to verify that the intersection is
complete at the blunt. If a piece between the start/end of the curve and the blunt is missing, it is not
detected.
FIGURE 7.43
Modify reference angle of all the blades to correct the projection
When using the Compute For Row button, AutoGrid5™ assumes that all blades are either aligned
at leading or at trailing edge. It might fail if this is not the case.
Finally, the Number of Points Used To Define the Chord allows to control the number of
control points used to generate the chord in the blade to blade view (by default set to 33). Usually
this number of points is unchanged but in specific cases (i.e. when the blade is deformed), it is
required to increase this parameter.
7.3.1 Overview
The HOH topology is defined with three blocks named respectively the inlet, O and outlet blocks.
The topology is controlled through the dialog box Define B2B Topology for Active Blade.
FIGURE 7.44
HOH topology
This topology is not suitable for all the turbomachinery types. This feature is not applicable:
l for blade with blunt leading edge and/or blunt trailing edge,
l for row with splitter blade(s),
l for blade to blade geometrical configuration with blade chord length lower than the pitch
angle,
l for row with control line defined on the blade.
The HOH blade to blade mesh topology is controlled through the parameters available in the
dialog box Define B2B Topology for Active Blade. The dialog box is divided into five areas.
In the Topology page, the user control the mesh topology of the inlet and the outlet extension of
the mesh. The O-block is running around the blade and can be extended by upstream and
downstream H or I blocks. In Mesh page, the user is allowed to change the orthogonality and the
cell width at the wall through the parameters Boundary Layer Factor and Cell Width at Wall,
respectively. The blade points clustering can also be controlled. In the Grid Points page, the
interactive graphical area shows the mesh topology in terms of number of points. The user can
customize the grid size by changing the number of points displayed in this area. Each label can be
selected and modified using the mouse. When clicking on a number of points, a string input area
appears prompting the user to change this number. When modification have been done inside the
dialog box, the button Generate B2B can be used to compute and display the mesh according to
the new settings.
As described in the previous section, the Define B2B Topology for Active Blade dialog box gives
access to the upstream and downstream control.
FIGURE 7.45
Upstream & downstream controls
By default, the upstream and downstream extension blocks are activated (1), the inlet and outlet
block type is set to I (2).
As shown in FIGURE 7.46, H inlet type allows the user to set up full matching meshes. If the I
inlet type is chosen, the periodic boundaries at the inlet are non-matching.
FIGURE 7.46
H&I upstream topology
The Inlet Position and Outlet Position entered by the user is used to compute the distance
between the leading edge and the connection boundary. The specified value is a ratio between the
pitch angle and the computed distance.
The grid points number depends on the grid level chosen in the quick access pad page Mesh
Control/Grid Level before performing the initialization ( Initialize Topology & Grid Points
Distribution).
Afterwards, the interactive graphics area of the Define B2B Topology for Active Blade dialog box
allows the user to change the number of points used to defined the blade to blade mesh. The
mouse can be used to select a grid point number by left-clicking on it. A string input area is
automatically displayed, prompting the user to specify a new grid point number.
FIGURE 7.48
HOH number of points
The page Blade Points Distribution opens an area allowing the user to control the clustering
near the leading edge and near the trailing edge of the blade
FIGURE 7.49
Blade Points Distribution
Four blade points clustering types are available for the leading and/or the trailing edges:
l (1) None: the grid points are clustered according to the projection of the clustering on the
external boundaries of the block.
l (2) Absolute Control Distance: a uniform distribution is set along a distance given by the
user.
l (3) Relative Control Distance (Default): a uniform distribution is set along a distance
computed by multiplying the blade width near the leading edge and a factor given by the user.
l (4) First Cell Length: first cell length is given by the user
The mesh on the hub/shroud gap is created using a butterfly topology. Grid Points page provides
new parameters to control the gap mesh.
FIGURE 7.50
Gap controls
When using the matching mode (non-matching connection is created between the H and O block
inside the gap) it is not recommended to use the optimization in the clearance. In some cases that may
work but most of the time it will not give any better result.
The two Hub to Shroud Control parameters at Inlet and Outlet in the Mesh page of the Define
B2B Topology for Active Blade dialog box act to reduce fluctuation of the solid angle computed
to initialize the blade to blade mesh using HOH topology. In linear mode the angles are equal to
the linear interpolation between the hub and the shroud angle values. To see a big difference, the
blade should present the same solid angle on the hub and the shroud and different at mid span. It
is used to avoid 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 to 0.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 intersection
between the blade and the flow paths performed during the transformation made from 3D space to
2D blade-to-blade space and from 2D domain to 3D space. More details about the parameters are
provided in the "Intersection Control Options" (p. 373) section.
7.4.1 Overview
The H&I topology is used to obtain better mesh quality with multiblades (one or more splitters)
configuration. The H&I topology is controlled through the dialog box Define B2B Topology for
Active Blade.
The H&I topology will present leading and trailing edges clustering projected on neighboring
blades, meaning that a non matching connection or a non matching periodic connection will be
present at inlet and outlet.
FIGURE 7.52
H&I topology - Projection points
As mentioned previously in this chapter, the H&I topology is composed by maximum 4 blocks:
l a H block to mesh the blade passage
l an optional O block around the blade (skin block)
l an optional H block upstream the leading edge of the blade if a skin block around the blade
l 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
and a non matching connection (FIGURE 7.53) or a non matching periodic connection (FIGURE
7.54) in the inlet and outlet region.
However, a small part just before the leading edge and after the trailing edge will be matching to
avoid a non matching connection in these critical regions (FIGURE 7.54).
FIGURE 7.54
H&I topology connections
The number of points involved in the matching connection at the leading and trailing edges is
automatically imposed by AutoGrid5™ and cannot be adapted manually. These number of points
are provided as info in the Grid Points page.
The options H topology: Inlet/Outlet have to be activated in the Topology page in order to
ensure a full matching connection at respectively inlet or outlet when the blade is not detected
highly staggered at inlet or outlet. To apply these options, the button Initialize Topology & Grid
Points Distribution should be pressed.
FIGURE 7.55
H&I topology - H Inlet/Outlet
The option H topology: Full has to be activated in the Topology page in order to enforce full
matching connections in the whole blade-to-blade mesh including in the gap. To apply this
option, the button Initialize Topology & Grid Points Distribution should be pressed (i.e. staggered
topology is reset to normal).
The H&I topology can be limited to H block to mesh the blade passage by deactivating the option
Skin Block.
FIGURE 7.57
H&I topology - without Skin Block
The grid points number depends of the grid level and the streamwise weights chosen in the quick
access pad page Mesh Control/Grid Level before performing the initialization ( Initialize
Topology & Grid Points Distribution).
When modifying a number of grid points, in order to preserve the matching connections of the
H&I topology, all the numbers of grid points will be automatically adapted. For a configuration
presenting splitter(s), when modifying the grid points numbers on one blade (main blade or
splitter) of the row, the changes will be automatically applied on all the blades composing the
row.
The O block around the blade is used to optimize the control of the boundary layer on the blade.
It is created using an hyperbolic mesh and can be adapted using the options presented in section
Control Skin Mesh Clustering around the Blade. When the option Skin Block is deactivated (no
O block around the blade), a clustering at both ends will be applied in the H block in the channel.
When gap(s) has been defined, AutoGrid5™ adds automatically blocks to mesh the domain up or
down to the blade(s). More details can be found in the Control Hub/Shroud Gap Mesh section.
In case of blunt blades, AutoGrid5™ automatically detects the bluntness of the blade and the
option to blend, sharp or rounded the blunt blade leading/trailing edge appear in the Topology
page of the Define B2B Topology for Active Blade dialog box. More details can be found in the
Blend/Sharp/Rounded Treatment at Leading/Trailing Edge.
However, when the blade is considered as blunt or sharp at both leading and trailing edges, the
skin block (O block) will be removed.
The skin block is created using a hyperbolic mesh. The width of the boundary layer is controlled
by the cell width at the wall, the expansion ratio and the number of points in it. These parameters
can be modified in the page Mesh and Grid Points of the dialog box.
The H&I topology will present leading and trailing edges clustering projected on neighboring
blades. It means that by default the clustering imposed at the leading and trailing edges will be
applied on the corresponding projected point.
FIGURE 7.58
H&I topology - Projection Point
AutoGrid5™ allows to relax the clustering of the projected point manually or automatically using
the parameters available in the Mesh page.
The Automatic Clustering Relaxation (projections) option allows to relax automatically the
clustering on all projection points simultaneously.This method allows to impose automatically
different clustering relaxation depending of the projection point. For example, if the blade is
presenting a blunt at trailing edge, the corresponding projection point clustering will be more
relaxed compared to the leading edge projection point clustering as presented in FIGURE 7.59.
The inlet and outlet boundaries of the blade to blade mesh are located at theta positions computed
automatically using a parabolic function or defined manually. More details can be found in the
Inlet & Outlet Boundary Control section.
The Relax Inlet/Outlet Clusteringoptions allow to relax the clustering in the azimuthal direction
starting from the control line up to the inlet or the outlet.
In case of blunt blades, AutoGrid5™ automatically detects the bluntness of the blade and new
options ZCst line at Leading/Trailing Edge are available in the Mesh page in the Define B2B
Topology for Active Blade dialog box. More details can be found in the Blunt at Leading/Trailing
Edge section.
FIGURE 7.60
High staggered topology at inlet
By default, AutoGrid5™will detect automatically if the blade is staggered. When detected at inlet
and/or outlet, the main H block is deviated from streamwise direction to theta direction in order to
create a kind of C topology at the inlet and/or outlet). More details can be found in section
"Topology for High Staggered Blades" (p. 361).
The topology for high staggered blades is presenting full matching connections in the high staggered
area.
These parameters allow in specific cases to control the intersection between the blade and the flow
paths performed during the transformation made from 3D space to 2D blade-to-blade space and
from 2D domain to 3D space. These parameters are detailed in section "Intersection Control
Options" (p. 373).
FIGURE 7.61
Blade to blade mesh optimization control
This section describes the optimization parameters available in the dialog box Optimization
Properties.
The first fields Optimization Steps on Fine Grid and Gaps and/or CHT Optimization
represent the number of iteration the elliptic smoother will perform respectively in the channel
mesh and in the gap. This number depends on the skewness (orthogonality) level of the original
mesh and can be highly reduced if the Multigrid Acceleration is activated. By default both
optimization steps are set to 100.
The field Full Multigrid Optimization Steps represents the number of iteration the smoother will
performed on all coarse grids to optimize each coarser grid before performing optimization steps
on finest grid level (Optimization Steps on Fine Grid) with or without Multigrid Acceleration.
The full multigrid smoother allows to accelerate the blade-to-blade smoothing process especially
when dealing with fine mesh or mesh requesting high amount of iteration steps on fine grid to
reach a good mesh quality (initial mesh far from final mesh, e.g. configuration with large skin
block). The full multigrid smoother reduces the kinks in the spanwise direction. By default full
multigrid optimization steps are set to 0.
This option is not recommended for coarse meshes having few multigrid levels for which fine grid
smoothing is already quite fast.
As full multigrid smoother produces already a quite good mesh, therefore a reduced number of
iteration steps on fine grid is needed after.
The full multigrid smoother as the fine grid smoother may lead to angular deviation problems if the
mesh is including non-matching and/or non-matching periodic connections.
The full multigrid smoother is not recommended when dealing with rounded leading/trailing edge
blade and H&I topology without skin block.
Skewness Control
By default the Optimization Steps on fine grid control the orthogonality of the cells only near the
solid wall. The parameters Skewness Control/Skewness Control In Gaps set to Full force the
optimization to increase cells orthogonality everywhere respectively into the blade- to- blade
channel mesh and into the blade-to-blade gap mesh.
When the parameters Skewness Control/Skewness Control In Gaps are set to Medium, the
first half of iterations are done without skewness control and the remaining second half with
skewness control.
FIGURE 7.62
Optimization with skewness control
Two source term computations have been implemented ("Theoretical Aspect" (p. 403)).
The first one, with the Skewness Control set to No , computes source terms only in the
neighbourhood of boundary layers, taking into account the expansion ratio provided by the user.
The main drawback of this implementation is that it is easy for the user to enter conflicting inputs
that will make the smoother diverge. For example, requiring a very small cell size on boundary
with a small expansion ratio while the boundary spreads on a large distance with few cell points
cannot be achieved and is a typical case of the smoother divergence.
The second one, with the Skewness Control set to Full, computes source terms everywhere on
the mesh and does not have expansion ratio as input. The boundary layers are not privileged
which leads to better orthogonality in the central regions but decrease orthogonality near the
boundary layers. Moreover, mesh concentrations outgoing from boundary layers propagate all
over the mesh.
The main difference between the two methods can be seen in FIGURE 7.63.
FIGURE 7.63
Smoothing without (left) and with (right) skew flag
Orthogonality Control
The parameter Orthogonality controls the level of cells orthogonality near the wall or
everywhere in the mesh depending of the Skewness Control parameter value. By default the
orthogonality control parameter is set to 0.5.
The parameter Gap Orthogonality is used when a large variation is observed in the first cell
width in the gap compared to the blade width. In case of smaller wall cell width, increase the Gap
Orthogonality to increase the orthogonality and for larger wall cell width, reduce the Gap
Orthogonality to avoid overlapping cells 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 are too small, the numerical scheme that solves the elliptic equation becomes unstable and
the smoother diverges. The source terms are therefore clipped in order to be kept below a certain
value depending on the smoother type.
This option is meaningful only if the Wake Control is activated. In that case, the smoothing is
performed in two stages. During the first one, the wake is fixed and released during the second
stage. The Wake Control Level slider controls the proportion of iteration performed in the first
and the second stage.
FIGURE 7.65
Wake control level
This functionality allows a faster convergence of the smoother but should nevertheless be
carefully used. Indeed, in this case, the multigrid scheme presents an additional difficulty: the
fields that are computed, restricted and prolonged are the mesh points themselves. The expansion
ratio is thus highly increased on each grid coarsening as well as the resulting source terms. As
discussed in the Orthogonality Control section, the stability of the numerical scheme therefore
decreases on each coarsening and few examples (i.e. when very small expansion ratio on the
finest grid) have successfully converged using such multigrid approach. The compromise that has
been found and implemented in the current 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 can be somewhat different that the one obtained with a
single grid computation.
The Non- Matching Control slider controls the orthogonality at the non- matching periodic
boundaries when Matching Periodicity is deactivated (See Control Periodic Boundary Condition
Type ). In that case, the smoothing is performed in two stages. During the first one, the
orthogonality is fixed on the periodic boundaries and released during the second stage. The slider
controls the proportion of iteration performed in the 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 in the 3D mesh.
The parameter Bnd Optimization Steps allows to optimize the shape of the block boundaries of
the initial mesh before applying the Optimization Steps. In specific cases, the option avoids the
periodic boundaries to cross the blade or cells overlaps in the blade-to-blade view resulting in
mesh optimization divergence when Optimization Steps applied.
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.
The Multisplitter Control selection box is used to control the mesh initialization (ordering) for
multisplitter configuration. By default the parameter is not active and is active when a new
multisplitter template is initialized.
The Freeze Skin Mesh selection box is used to freeze the skin block (mesh and boundaries)
during the optimization process. It is suggested to freeze the skin mesh with the introduction of
cooling holes, in order to improve the quality of the full non matching (FNMB) connection
between the skin block and the core flow.
Try to avoid large expansion ratio (>2) along the blade in the streamwise direction when setting
up the number of points required along the blade.
When the user needs a coarse mesh with large expansion ratios and hence, the previous advice
cannot 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
mesh generation
The aim of this functionality is to optimize both orthogonality and expansion ratio all over the
mesh. If we consider an initial mapping
When the source terms, P = Q = 0, the mesh will converge to an uniform spacing grid without
taking account of orthogonality or boundary conditions (clustering at wall for example).
Therefore, the implementation consist in calculating these source terms in order to maximize
orthogonality and to minimize expansion ratio while taking into account all boundary condition
types available in AutoGrid5™.
3D MESH CONTROL
The 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 blade meshes are
projected. The stacking method is divided into two phases: the computation of intersection between the
blade(s) and the layers, and the generation and optimization of the blade to blade mesh.
To modify this stacking method, 3D mesh controls are available to improve the mesh quality in
specific configurations. They are accessible through the dialog box available in Mesh Control/Row
Mesh Control/3D Mesh Control from the Quick Access Pad or the icon from the toolbar as shown
in FIGURE 8.1.
FIGURE 8.1
3D Mesh Control
To reduce the generation time, it is possible to reduce the number of layers on which the mesh
must be optimized. The parameter Span Interpolation (%) is used to specify the spanwise space
between 2 consecutive layers on which the 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 interpolated between them to obtain the entire mesh.
When Z cst lines are defined upstream or downstream to the blade, upstream and downstream H-
blocks are created. In some cases, mainly centrifugal machines, blade trailing edge shows some
theta spanwise twist, propagating till the outlet, the total spanwise twist being even more
important at the outlet (in radial configurations). This leads to an outlet block with a poor
orthogonality all over its extend, while the orthogonality could reach 90 degrees at the outlet.
The options Untwist Inlet/Untwist Outlet allow the user to impose outlet/inlet faces with straight
bounds at constant theta and to propagate the modification along a streamwise length
(Streamwise Starting Point (%)) defined in percentage starting from the control line close to
trailing/leading edge and respectively outlet/inlet.
When combined with wake prolongation, due to the untwisting method, the wake angle imposed by
the user is no more respected and the difference may be highly different depending of the twisting of
the original mesh outlet patch.
This option is not available for row just upstream the bypass nozzle.
FIGURE 8.3
Untwist outlet on centrifugal machine
If a hub and/or shroud gap with a high width variation is defined on a blade, e.g. Kaplan turbine,
then the generated 3D mesh will contain huge spanwise angular deviation in all the blade blocks,
in the layers around the gap(s). This is inherent to the 3D stacking process and cannot be avoided.
The Hub/Shroud Gap Interpolation options provide a post-treatment which can be applied on
the original 3D mesh. This post-treatment will reduce the spanwise angular deviation by re-
interpolating all blocks of the row between two layers.
FIGURE 8.4
Shroud gap interpolation on Kaplan turbine
In case the leading/trailing edge of the blade is too curved in the zone where the treatment will be
applied, this postprocess may lead to generation of cells with high expansion ratio on the nodes
mapped on the blade. It may also lead to overlapping blocks, e.g. inlet/outlet block passing through
the blade surface.
The gap interpolation is not applied when the solid body configuration is not default ( Solid Body
Configuration).
For some of the projects in AutoGrid5™, the cell width at blade walls on the 3D mesh can
deviate from the cell width imposed by the user. One reason is that a constant cell width is used to
generate the blade-to-blade mesh while the radius can vary a lot along the corresponding flow
path.
The Enforce Cell Width At Blade Wall option is introduced to minimize the difference between
the expected cell width and the measured one. Two treatments are applied when this option is
activated:
l in the blade-to-blade mesh generation, a variable cell width is imposed on the blade wall in
function of the radius.
l 3D mesh is postprocessed to respect cell width on the blade, i.e. modifications of the skin
block.
The 3D postprocess assumes that the cell width varies continuously around the blade. Therefore, if
there are discontinuities in the cell width of the blade, the postprocess tends to produce huge kinks.
The 3D postprocess is not applied around the snubber and in gap blocks. In gap blocks, it may lead to
an increase of the inter-block expansion ratio between for example the skin block and the gap blocks.
The Swap Blade Patches Name option is introduced to allow the user to swap the pressure side
and the suction side definition (used in the patch names) of each row to respect the physics. By
default in AutoGrid5™, considering the rotation axis Z, the convention of the pressure/suction
sides is presented in FIGURE 8.5.
In addition a new preference Family name options/Blade pressure/suction sides is available for
CEDRE/CGNS export to split the blade family name into a pressure side "_PS" and a suction
side "_SS" family names.
3D GENERATION
FIGURE 9.1
3D generation
In this section
9.1 Application Field 414
9.2 3D Mesh Generation 415
9.3 Mesh Quality 419
9.4 Template & Mesh Files 420
9.5 B2B Cut 421
The button Generate 3D of the top toolbar applies to all the selected entities of the tree. Three
types of entity can be selected: the row, the meridional technological effect and the 3D
technological effect. The button Select All is used to select all the entities of the tree. The button
Select All Rows is used to select all the rows of the tree.
FIGURE 9.2
Selection of the application field of the button Generate 3D
The meridional effects are connected to several rows and must be generated together with these row
(s) if these ones are not yet generated. If the 3D meshes of the connected row (s) are already
generated, the effects can be generated alone excepted if the configuration 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 containing a
selected 3D effect, AutoGrid5™ prompts to confirm the 3D generation of the row.
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 to perform the
persistence implies that AutoGrid5™ changes automatically the name of the block exceeding 32
characters, stored in the CGNS file into 'domain<block number>'.
Row Mesh
The name of each block is built using the name of the row and the name of the related blade.
Mesh in Bulb
If an inlet bulb (hub->R=0) region is detected, the following blocks are added to the 3D mesh:
l bulb_at_inlet_C (if rounded topology is chosen)
l bulb_at_inlet_H1 (if rounded or sharp topology is chosen)
l bulb_at_inlet_H2 (if rounded or sharp topology is chosen)
l bulb_ at_ inlet_ butterfly_ 1 (if rounded topology without singular line or radial topology is
chosen)
l bulb_ at_ inlet_ butterfly_ 2 (if rounded topology without singular line or radial topology is
chosen)
l bulb_at_inlet_butterfly_1_2 (if radial topology is chosen)
l bulb_at_inlet_butterfly_2_2 (if radial topology is chosen)
If a C topology is chosen to mesh the region around the nozzle of a bypass configuration, a new
block named "C_block_around_nozzle" is added.
When the mesh of a meridional effect named 'zr techno effect 1' is generated, following blocks are
added into the 3D database:
l zr_techno_effect_1_zr_effect__Block_1_3d
l zr_techno_effect_1_zr_effect__Block_2_3d
When the mesh of a 3d effect named '3d techno effect 1' and belonging to the row named 'row 1'
is generated, a prefix 'row_1_3d_techno_effect_1_' is added to each block name of the blocks
generated in the 3d effect.
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 in the ".cgns" files.
Patch Naming
Solid patches contain the name of their related entities and the location (hub,shroud,nozzle,skin_
blade). Following is the list of the solid patches created for the 'row 1' around the 'Main blade'
with a default topology:
l row_1_flux_1_Main_Blade_inlet__hub_identifier_
l row_1_flux_1_Main_Blade_outlet__hub_identifier_
l row_1_flux_1_Main_Blade_up__hub_identifier_
l row_1_flux_1_Main_Blade_down__hub_identifier_
l row_1_flux_1_Main_Blade_skin__hub_identifier_
l row_1_flux_1_Main_Blade_inlet__shroud_identifier_
l row_1_flux_1_Main_Blade_outlet__shroud_identifier_
l row_1_flux_1_Main_Blade_up__shroud_identifier_
l row_1_flux_1_Main_Blade_down__shroud_identifier_
l row_1_flux_1_Main_Blade_skin__shroud_identifier_
l row_1_flux_1_Main_Blade_skin_blade_(aap-ps)
l row_1_flux_1_Main_Blade_skin_blade_(aap-ss)
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. To
obtain similar order for similar configuration, the entire mesh must be generated using the same
interactive sequence of calls to the Generate 3D button (not easy to manage). Another way to
ensure a same block order is to set up the configuration and to start the full mesh generation
(Select All+Generate 3D). The batch mode ensures also the same block order.
By default, the mesh is generated for 1 main blade passage. The option Number Of Meshed
Passages in the dialog box Row Properties can be changed to generate more than one main blade
passage. The mesh is obtained by repetition of the first blade passage.
The Mesh Control subpad displays and updates continuously an approximation of the total
number of grid points of the selected entities in the Row Definition subpad. After the grid
generation, the real grid points number is displayed in the information area (lower left corner of
the interface).
After the grid generation, the menu item Grid/Grid Quality Report ( ) displays the
characteristics of the mesh in terms of minimum and maximum of the expansion ratio, the aspect
ratio and the cells skewness (orthogonality). 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. The number of multigrid levels of each entity (row and technological
effects) is listed in the Nb levels column.
FIGURE 9.3
Grid quality report
After each 3D generation, all the data of the grid quality report are stored in a report file
(".qualityReport"). 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 (Graphical User Interface).
Finally, the Grid/Grid Quality Report (HTML) menu (not available on Windows) allows to
automatically write a mesh quality report. When selecting the menu, a window enables to select
the images that will be inserted into the report and provides disk usage necessary for the report
and images (refer to Grid Quality Report (HTML)) for more details).
Mesh Files
The mesh files contains the multiblock mesh topology, geometry, grid points, patch grouping and
the boundary condition types:
l new_prefix.bcs: boundary conditions files,
l new_prefix.cgns: grid points files (CGNS format described in IGG™ User Manual - Input &
Output Files),
l new_prefix.geom and new_prefix.xmt_txt: geometry files,
l new_prefix.igg: topology file,
l new_prefix.qualityReport: mesh quality report file,
l new_prefix.config: mesh configuration file used for the grouping in FINE™ GUI and for the
SubProject (more details in FINE™ User Manual).
These files can be loaded into the structured multiblock grid generation system IGG™ and by the
CFD integrated environment FINE™/Turbo.
The hub and shroud curves definition are saved in the .cgns file. These data are read within CFView™
and used to define both blade-to-blade and meridional views.
The mesh quality file is saved at the end of the grid generation. If the new project has not yet been
saved before launching the 3D generation, no grid quality report file will be saved because the system
is not able to determine automatically the file location.
Template Files
The files when saving the template contain the parameters and the geometry needed to reproduce
the mesh with AutoGrid5™:
l new_prefix.geomTurbo and new_prefix.geomTurbo.xmt_txt: the geometry files (geomTurbo
format),
l new_prefix.trb: the template file containing the grid generation parameters,
AutoGrid5™ allows to extract a blade to blade template and mesh (two layers in spanwise
direction) 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 project tree. Right click on that item to open a contextual menu.
The B2B cut is not available for bypass configuration since the B2B cut is applied on all the rows,
this can not work in a bypass configuration with a common span position.
Select Edit to open the B2B Cut Definition dialog box. This dialog box is used to define the cut
geometry based on two parameters:
l Spanwise Location. The user can set the spanwise location of the cut geometry based on the
percentage value. The total span is considered as 100.0. By default the Spanwise Location is
set to 50.0, which is located at the mid span.
l Spanwise Width . The width of the cut geometry is given as a percentage of the local
spanwise width. Therefore, the width of the mesh can change along the streamwise direction.
In case the flow path is already generated for all the rows, the cut definition is automatically
displayed in the meridional view with yellow lines. Two yellow lines define the domain of the
expected B2B mesh. These lines are derived from the flow paths definition of the 3D template
and are controlled by the two parameters: spanwise location and width.
FIGURE 9.5
Blade to blade cut with 20% of span width
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.
The menu item Create is used to start the generation of the new template, which will be used to
create the B2B mesh. An error message is displayed if the selected flow path is not generated for
all the 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 and
shroud definition, based on the curves defined by the B2B Cut Definition dialog box. The new
template is automatically loaded and can be used to create the B2B mesh.
Before starting the blade to blade cut geometry creation, the current AutoGrid5™ template must be
saved.
The hub and shroud patches of the mesh are defined as mirror boundary condition.
A turbomachinery configuration contains usually blade rows and also meridional effects like seal
leakage, bleed or cavities. The solid body of the meridional effects is axisymmetric. Their geometry is
defined by meridional curves (z,r coordinates). The domain of a meridional effect must always be
connected to one or more blade row(s).
FIGURE 10.1
Blade row with meridional effect
In this section
10.1 Configuration Management 425
The Rows Definition subpad of the Quick Access Pad contains features used to control the
meridional effects. New effects can be added into the configuration tree and managed through
their contextual menus.
FIGURE 10.2
Meridional effect management
The option Add ZR Effect creates a new entity in the configuration database and displays it into
the Meridional Techno Effects list of the tree. Right-click on this new items of the tree opens the
contextual menu of the meridional effects. It gives access to the editing mode allowing the user to
define the new effects or to delete the selected effects.
The effects can be renamed by double- clicking on their name into the tree. An interaction area
prompts to enter a new name for the selected effect.
The 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 should be defined in the
meridional view.
The curves defining the meridional effects are specified in the ".geomTurbo" file using the basic
curve format (Geometry Definition).
CAD Import
The solid bodies of the meridional effects can be imported (Import Meridional) from external
CAD files using Import CAD window. The curves defining these bodies are selected interactively
and projected in the meridional view (Geometry Definition).
FIGURE 10.3
Import CAD window - Import Meridional
AutoGrid5™ provides geometrical features used to create the solid body of meridional effects
interactively. New polylines can be created using Geometry Control subpad in the meridional
effect edit mode and the steps needed to create these polylines are stored in the template file.
FIGURE 10.4
Edit mode - geometry control subpad
Notice that the Geometry menu available in the meridional effect edit mode can be used to define
the geometry. Nevertheless, the name ( Geometry/Modify Curve/Set Name... ) of the created curve
must contain the keyword "inlet", "outlet", "solid", "solid_rotating", "external" or "rotor_stator" to
ensure the automatic definition of the boundary conditions.
The meridional mesh of a technological effect is built into the edit mode available through the
Edit menu item of the contextual menu open when right-click on a ZR technological effect of the
tree. The Quick Access Pad is updated to access the features needed to create the meridional
mesh. The graphical area displays the meridional view of all the curves defining the meridional
solid body of the turbomachinery. The button Close Edit Mode of the top menu bar is used to quit
the edit mode. All the actions performed during an editing session are stored in the template file
(".trb") and can be replayed on similar geometries.
The Quick Access Pad is divided into five main areas (subpad):
FIGURE 10.5
Edit mode
The Properties and Geometry Control subpads of the Quick Access Pad provides respectively
the rotation speed of the rotating geometry (i.e. solid polyline rotating) and six options to add
polylines. These curves are eventually used to close the domain defined by the solid body or to
create the separation line in case of multiple connections (see Multiple Connections).
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 of the meridional
effect.
When a button is pressed, an interactive tool is started waiting for points input:
l Left-click to confirm the creation of a new control point of the polyline.
l 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.
The type of the polyline can be inlet, outlet, external, solid, solid rotating or rotor/stator. The type
is chosen according to the CFD requirement.
It is not recommended to have a meridional effect covering a rotor/stator control line in the blade
channel.
If a cavity (ZR technological effect) is composed by one fluid block and one solid block (CHT), in
order to limit the position of the solid block, no solid curve should be used inside the ZR effect
definition. This is also true between two fluid blocks.
B. Topology Control
The domain defining a technological effect must be filled by several structured 2D blocks. The
block edges are mapped on the geometry. The Topology Control subpad provides the tools to
create and control the blocks.
Automatic Blocking
To perform the automatic blocking of a technological effect, the steps to follow are:
l adapt the solid wall cell width at the wall in Mesh Control subpad, used as reference during
the domain definition and the automatic blocking processes,
l define the limits of the technological effect with the Domain Definition button,
l adapt the automatic blocking expert parameters (optional),
l start automatic blocking with the Automatic Blocking button.
Before using the Automatic Blocking button, the limits of the technological effect should be
specified to define a closed domain. This is the aim of the button Domain Definition.
To define the limits of the technological effect:
1. Left-click on the button Domain Definition. A tool opens that allows to select a point on the
existing zr effect curves.
2. Left-click in the graphics area on a zr effect curve. From this point, a set of curves starting
from the selected point and joining the channel curves is highlighted in yellow. If channel
connection curves cannot be found, the domain definition will fail (most likely the problem is
located where the highlight stops) with an error message. If the selected zr effect has only one
connection with the channel, the domain definition is completed and right-click to leave the
tool.
3. If the zr effect has a double connection with the channel, a second point has to be selected on a
still unhighlighted curve of the zr effect. Once again, starting from this point and joining the
channel curves, a set of curve is highlighted in yellow. From there, the domain definition is
completed. Right-click to leave the tool or left-click to restart the domain definition if incorrect.
When the domain is failing, the automatic blocking cannot be performed. The domain may fail
because of gaps (higher than a tenth of the solid wall cell width) or overlaps between zr effect curves
or a curve sharing its start or end point with more than one curve or no curve (in the next example
each solid polyline is not sharing its end point with a curve).
Automatic Blocking
The automatic blocking algorithm needs a reference parameter that is representative of the
technological effect geometry size. The solid wall cell width in the Mesh Control subpad is used
as reference parameter.
When clicking on Automatic Blocking button, the following steps are performed to impose an
automatic blocking in the selected domain:
1. Compute the skeleton of the domain boundaries,
2. Compute a first blocking based on the skeleton curves,
3. Modify and/or delete some blocks for better mesh quality,
4. Modify/split some blocks to catch boundaries discontinuities.
For blades with blunt configuration at LE/TE and technological effect(s) connected right at this blunt
location, if the user wants a matching connection with the channel, vertices of the blocks in the
technological effect at the connection have to be manually moved on a dot. These dots are
automatically drawn in the technological effect edit mode for each blunt blades.
In case of a technological effect with a double connection to the channel, a rotor/stator polyline
should be added manually and the automatic blocking algorithm tries to catch the polyline (separation
line) by splitting the blocks passing through it. The polyline should be placed so that it passes through
only 2 blocks, otherwise the rotor/stator polyline will most likely not be automatically mapped. The
location will most likely be good if placed in a long, thin and straight channel of the technological
effect. However, in some cases, this might still not be sufficient.
When the automatic blocking is performed, the Manual section provides a few tools to adapt the
proposed blocking.
Expert Parameters
The expert parameters H Topology Around Corners and H Topology Around Thin Films
(activated by default) allow to control which topology will be used in T-shaped and L-shaped
parts of the domain.
H Topology Around Corners option allows to get a topology with higher orthogonality, but the
topology leads to some propagation of the solid wall clustering. This may lead to convergence
issues for the flow solver.
H Topology Around Thin Films option allows to avoid blocks of high section variation, which
will most likely lead to a very high number of points compared to the block's lowest section size.
It also give a better orthogonality, but the topology may lead to some clustering propagation as
well.
The icon starts the block creation tools. When moving the mouse into the graphics area a default
block geometry appears. Left-click twice to select the location of two opposite corners of the
block and left-click again to confirm the creation. The four vertices defining the corners of the
block are displayed. These vertices can be selected interactively (left-click) and mapped (attracted)
onto the geometry. The block edges are automatically mapped on the geometry curves if their
vertices are mapped on an underlying curve.
To fill or adapt manually the geometry defining the meridional effect the following rules should
be respected:
l When the edge mapping is not performed as required, a vertex needs to be inserted.
l A block connected to the channel should not have a multisegment edge otherwise some UND
may appear if a FNMB or a matching connection is imposed.
l When the meridional effect has several connections with the main blade channel, specific rules
have to be respected and are presented in section Multiple Connections.
The icon opens the dialog box used to delete several existing block.
Select the block interactively (left-click on an edge) and press the button Delete into the dialog
box Delete blocks. Confirm the deletion into the confirmation box.
The icon is used to insert a new control vertex on a edge. It is needed when the edge must be
mapped 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.
The icon opens the Clustering dialog box use to control manually the grid points clustering along
each edge of the blocks to adapt the automatic default mesh (Mesh Control subpad). The dialog
box can also be accessed when right-clicking on the desired edge and selecting the Distribution
menu.
An edge can be split in several segments by attaching a fixed point to an existing vertex. To attach
a fixed point to a vertex:
1. The vertex must first exist. If this is not the case, create one vertex as indicated in previous
section.
2. Right-click on the vertex to pop-up the menu.
3. Select the Attach Fixed Point menu item.
4. The vertex and fixed point markers are merged as a diamond, indicating that the vertex is
attached to the fixed point.
Blocks in the technological effect connected to the blade channel (except if periodic fnmb
connection) or the rotor/stator polyline (separation line) should not present multi-segments edge.
The number of points on each edge can be controlled manually through the dialog box Set
Number of Points to adapt the automatic default mesh (Mesh Control subpad). Right-click on the
desired edge to access the contextual menu and select the item Set Number of Points.
Enter the new number of points in the Set Number of Points area and press Apply.
The Propagate option indicates whether segment resizing should also be applied to the blocks
connected to the active block. We recommend to keep propagation always active.
The Preview button evaluates the effect of a segment resizing on the active block and all the
blocks connected through a segment connection. The segments affected by the evaluation will be
highlighted in yellow.
At the bottom of the dialog box, the warning is informing that multi-segment edges are allowed in
the technological effect. If the number of points are adapted manually on segments or edges the
user has to check manually that the imposed number of points propagated on concerned edges
and segments is still respecting the number of grid level imposed.
If blocks have been added in a ZR effect, it is necessary to connect these new blocks. The button
Default Mesh in Mesh Control subpad will generate and connect these new blocks but will also
delete all the existing distributions made manually.
When creating manually a ZR effect or adding/adapting blocks in existing ZR effect, the button
Connect Blocks allows to enforce the connections of all blocks in the ZR effect without applying
a default mesh and thus keeping all manual adaptations performed by the user.
As a consequence, before performing the Connect Blocks the edges of the blocks to be connected
have to present the same number of points and distribution. Otherwise,
l if the edge distributions are different clicking on Connect Blocks will connect these two edges
and apply the distribution of one of these 2 edges to the other.
l if the edge number of points are different (except at the RS polyline interface), the 3D mesh
generation will not be completed.
Detection Tools
The button Detect Unmapped Edges is used to visualize the face edge unmapped on an existing
meridional curves. Check the vertices linked to the edges. The unmapped edges are displayed in
the view and the number of detected unmapped segments appears in the message area.
The button Toggle Rotating Boundaries is a toggle used to highlight the rotating boundaries
(Solid Polyline Rotating and imported rotating basic curves) of the meridional effect.
FIGURE 10.12
Visualize rotating boundaries
The buttons Detect Channel Matching/FNMB Connection are used to detect the type of
connection between the meridional effect and the blade channel (more details in Connection
Types) according to an absolute connectivity tolerance (Matching Tolerance) by default set to
1e-8.
C. Mesh Control
The Mesh Control subpad of the Quick Access Pad provides options to control the default mesh
(ZR Mesh Settings section) and the type of connection with the blade channel and at the
rotor/stator polyline (3D Mesh Settings section).
Default Mesh
AutoGrid5™ provides a feature to set up automatically the number of points and the grid points
clustering. Before starting if necessary the manual editing of the grid point number and the grid
point clustering, described in Manual Blocking, an automatic setting must be performed. The
defaults are computed with the Default Mesh button according to two parameters and four
advanced parameters:
l Solid Wall Cell Width: the first cell width in the boundary layer.
l the number of grid level respecting the number of grid level of the project (more details in
Mesh Control Subpad) when the concerned zr effect has been created. It should respect the
constraints related to the multigrid treatment within FINE™ GUI (default level is set to 3 and
means that we have minimum 3 grid levels: 000, 111 and 222).
l the Default Mesh Expert Parameters button opens a dialog box controlling the advanced
parameters of the default mesh:
l Max. Expansion Ratio In Boundary Layer: the maximum expansion ratio of the cells in
the boundary layer.
l Max. Expansion Ratio Along Boundary: the maximum expansion ratio of the cells along
the solid boundaries of the zr effect.
l Max. Expansion Ratio General: the maximum expansion ratio of the cells where both
previous expansion ratios are not relevant.
l Clustering Relaxation Angle : the angle to propagate clustering from an edge to the
opposite one. Maximum value allowed is 10.
The buttons Default Mesh or Connect Blocks ( Connect Blocks Tool) should be pressed once in
order to establish the connection between the blocks.
Each time the button Default Mesh is pressed, all the manual settings are erased by the new default.
To avoid that, the button Connect Blocks ( Connect Blocks Tool) is available.
Optimize Mesh
The Optimization Steps parameter allows the user to specify the number of iteration done by the
optimization system. Before AutoGrid5™ v9.0, the smoother used is highly dependent of the
original mesh quality. This smoother type was intended to give a smoothed mesh with an
orthogonality as close as possible to the unsmoothed one, which explains this dependency.
Starting AutoGrid5™ v9.0, the smoother used for newly created zr effects is the same as the one
used in the blade-to-blade view.
The Optimize Mesh button allows to display the optimized mesh.
Once the user has created the technological effect topology, clicking on the button Add Matching
Z Cst Lines allows to automatically add the control lines in the blade channel at the connection
points with the blocks of the technological effect and to impose the right control line cell width
(based on the solid wall cell width imposed in the technological effect) to obtain a matching
connection between the blade channel and the technological effect. If a control line is already
existing, no new control line is created at this location and the cell width is not adapted.
Created control lines are created with a default shape in exactly the same way as when the user adds a
control line manually. These control lines may thus not be optimally shaped and may also cross other
previously defined control lines. The user has thus to check the control lines shape and properties and
modify them manually if necessary.
For blades with blunt configuration at LE/TE and technological effect(s) connected right at this blunt
location, no control line is added at TE/LE and user needs still to add it manually.
3D Mesh Settings
When the effect simulate the expansion of the main blade channel mesh to the far field (wind
turbine), the Radial Expansion option activates full optimization of the far field mesh to avoid
high clustering of the mesh in this region of the domain. The Far Field Smoothing Steps
parameter controls the number of optimization steps that will be applied.
When the FNMB:Periodic option is active, the full non matching connection of the meridional
effect with the channel mesh will not follow the shape of the blade to blade mesh. That allows to
reach a better mesh quality in the meridional effect. In FIGURE 10.15 , the blocks of the
meridional effect connected to the channel mesh are twisted when the option is not active and that
may damage the grid quality.
When the meridional effect is connected to the channel with a full non matching connection, the
FNMB:Theta Number Of Points parameter controls the azimuthal number of points in the
meridional effect. When the value is set to 0 (default), the azimuthal number of points in the
meridional effect is currently the one at the inlet of the connected row.
When the meridional effect is connected to the channel with a matching connection, the
FNMB:Theta Number Of Points parameter will have no effect.
When the Propagate Theta Deviation option is active, when the number of blocks is above 2 in
the ZR effect, the angle deviation of the connected mesh will be propagated and allow in specific
cases to avoid mesh with bad orthogonality.
RS Interface Connection
When the ZR effect is containing a rotor/stator polyline (Multiple Connections), the type of
connection at the rotor/stator polyline can be enforced if the connections with the main blade
channel are related to the same row.
If the connections with the main blade channel are related to different rows, the connection at the
rotor/stator polyline will be a rotor/stator interface except if the different rows are presenting the
same periodicity.
If the connections with the main blade channel are related to the same row or rows with same
periodicity, the connection at the rotor/stator polyline will be:
l non-matching periodic if RS Interface Connection is set to Periodic except if the theta
deviation between the two sides of the effect is low enough and/or mesh of both faces very
similar (distribution & number of points), then the connection may be non-matching, matching
or periodic matching.
l enforced full non-matching periodic if RS Interface Connection is set to FNMB.
l enforced matching periodic if RS Interface Connection is set to Periodic and Matching.
l enforced matching if RS Interface Connection is set to Matching.
To enforce periodic matching or matching connection at the rotor/stator polyline, the connected
blocks at the rotor/stator polyline should present same number of points in azimuthal and "spanwise"
directions. When connections with the main blade channel are matching, the B2B grid points of the
row and the streamwise number of points in the channel should manually be adapted to ensure same
number of points at both sides of the rotor/stator polyline otherwise matching connection at the
rotor/stator polyline won't be enforced and a warning will appear: "connection at rotor- stator
interface is not matching".
Connection Types
The connections between the main blade channel row meshes and the mesh created into a ZR
technological effect domain are full non-matching by default. To obtain a matching connection,
control lines must be added automatically (Add Matching Z Cst Lines) or manually (Meridional
Control) at the connection points between the meridional effect and the main blade channel and
the wall cell width imposed in the ZR technological effect should be applied to the control lines.
FIGURE 10.18
Connection with main blade channel
When the option FNMB:Periodic is active (by default), a periodic full non matching connection
with repetition (Grid Menu) will be created between the ZR effect and the mesh channel to
improve the mesh quality in the ZR effect.
To improve non-matching connections, it is advised to add control lines at the connection points and
to switch to None their B2B Control( FIGURE 6.5).
When the grid points distributions in the streamwise direction in the blade row mesh is too coarse at
the connection level, mesh overlaps can appear in the mesh of the connected effect. To avoid this, the
number of points in the row can be increased or matching connection must be used.
If the control lines are correctly set, the matching connection can be ensured for all the connection
types:
FIGURE 10.20
Connection types
When the technological effect is just representing the far field and the connection is matching
between the technological effect and the blade channel, it is recommended to create manually the
blocking by just using one block for the whole far field per row instead of using the automatic
blocking that will generate a topology with more blocks. When more than one block, mesh generation
problems may occur in the zr effect because the blade channel mesh will be extruded in the far field
zr effect block(s).
FIGURE 10.21
Block management with the control points
Multiple Connections
Some of the technological effects have several connections with the main blade channel, i.e. a seal
leakage have a connection upstream the blade and a connection downstream the blade.
In this case the mesh created inside the domain of the effect is divided into two parts: one starting
from the inlet and one starting from the outlet. At the middle part of the seal leakage, a line must
be defined indicating the location of the division. At this line (Rotor/Stator Polyline), defined in
the edit mode (FIGURE 10.6), the two parts of the mesh will be connected by default by a non-
matching periodic connection if the connections with the main blade channel are related to the
same row (case 1 in FIGURE 10.22) but matching, periodic matching or full non matching
periodic connection can be enforced, or a rotor/stator interface if the connections with the main
blade channel are related to different rows (case 2 in FIGURE 10.22).
At the connection line (Rotor/Stator Polyline) the following rules should be respected:
l Block connection must be established on the separation lines and the mapping of vertices
respected (no orphan vertices).
l The 2D blocks should be connected to the rotor/stator polyline with a complete edge and not
with only one vertex or a partial edge.
In the ZR effect edit mode, the Grid/Grid Quality... menu or the icon in the toolbar give
access to a tool for performing an analysis of the grid quality of the technological effect 2D mesh
before generating the 3D mesh.
The dialog box contains two pages, one dedicated to analyse the grid quality on whole block
cells, and the second to the grid quality at the block boundaries (boundary faces), including
matching connections with adjacent blocks. The dialog box is similar to the one used for the grid
quality of the blade-to-blade mesh. More details are available in section Patch Browser.
10.6 3D GENERATION
The 3D generation of the meridional effect must be performed together with the generation of the
row(s) connected with them. Select the row(s) and their attached meridional effects and press the
Generate 3D button of the top menu bar.
Block rotation speed is computed automatically but are not interfaced per block. Therefore if some
blocks of a ZR effect are modified after 3D generation (block splitting, transformation,...) the rotation
speed may be lost.
If the mesh is loaded in IGG™ and resaved, it will still be correct because block rotation speed comes
from the configuration which has been reread. However if the mesh is loaded in AutoGrid5™ and
resaved, block rotation speed still comes from configuration but which is recomputed, and therefore
block rotation speed will be null.
l the boundary (patch) rotation speed in the ZR effect is imposed under Properties in the QAP
and is applied if the patch belongs to a rotating geometry. The geometry curve is considered as
rotating if created as Solid Polyline Rotating in the ZR effect edit mode or if imported and
defined as "rotating" basic curve.
3D TECHNOLOGICAL EFFECT
A 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 curves or
surfaces (x,y,z coordinates). The 3D effects are always linked to one row.
The mesh of these configuration entities is generated in 3 steps:
l definition of the new technological effect entities in the configuration database
l geometry definition of the domain defining the technological effect
l definition of the 3D mesh:
l manual blocking in the 3D space
l load an existing template in the effect library
This chapter describes the grid generation of 3D effects. The number of 3D effects is unlimited.
In this section
11.1 Configuration Management 459
11.2 Geometry Definition 460
11.3 Edit Mode 460
11.4 Topology Management 462
11.5 3D Generation & Persistence 464
The Rows Definition subpad of the left Quick Access Pad contains features used to control the
3D effects. New effects can be added into the configuration tree and managed through their
contextual menus.
A 3D effect belongs to a row. The related row must be selected before creating a new effect. The
option Add 3D Effect creates a new entity in the configuration database and display it into the
row selected in the tree. Right-click on this new items of the tree opens the contextual menu of the
3D effects. It gives access to:
l Edit : the editing mode allowing the user to define mesh of the new effects
l Load Geometry : the geometry definition. A file chooser is used to select the geometry data
file containing the curves and surfaces defining the effect body.
l Delete Effect(s) : the effect deletion tools
l Library : the effect library
l Copy/Paste Topology : the copy/paste topology feature allowing the user to apply to an effect
the topology of another.
The effects can be renamed by double clicking on their name into the tree. A interaction area
prompts to enter a new name for the selected effect.
FIGURE 11.1
3D effect management
The geometry of a 3D effects is defined by (x,y,z) curves and/or surfaces displayed in the XYZ
view when editing the effect. Before starting the definition of the mesh of a technological effect,
the geometry can be defined through:
The curves and surfaces defining the solid body of one effect are stored into one file. The
contextual menu item Load Geometry opens a file chooser to select this file.
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 link data 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 the grid
generation, the names of the geometry entities are used to identify the topology links. As the name of
each geometry entity must be unique, it is impossible to reuse the grid generation method of one
effect to another without respecting the following rule: the name of each entity must be composed
with a prefix and a suffix separated by a # character. The prefix is used to identify the effect and the
suffix is used to make the link with the topology (i.e.: effect1#curve1).
The meridional mesh of a technological effect is build into the edit mode available through the
Edit menu item of the contextual menu open when right click on a 3D technological effect of the
tree. The Quick Access Pad is updated to access the features needed to create the 3D mesh. The
graphical area displays in the 3D view all the curves and surfaces linked to the effect and the row
mesh related to the effect.
All the operations performed during an editing session are stored into a script. The grid generation
options 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
to fill the domain covered by the effect.
The edit mode is left by clicking on the Close Edit Mode button.
3D effect library
When an effect has been created, the mesh definition process can be stored in a dynamic library.
The contextual menu item Library opens the dialog box 3D Technological Effect Library. This
dialog box contains the list of the available topology. The selected topology can be loaded and
apply to the selected 3D effect using the button Load. The selected topology can be remove from
the list using the button Remove. The topology of the active 3D effect can be stored in the library
using the button Save: the dialog box Save 3D Topology is opened allowing the user to define a
new 3D topology or to overwrite an existing one.
The selected topology can be applied simultaneously to several similar 3D effect. If the geometry of
the effect is already loaded, the mesh is automatically generated using the selected topology.
Copy/Paste Feature
The 3D mesh topology of the selected 3D effect can be copied into a buffer and apply to other
effect using the contextual menus Copy Topology and Paste Topology. Several similar effects
can be selected to apply simultaneously the topology stored in the buffer using the Paste
Topology options.
The mesh generation is performed by the Generate 3D button. All the selected 3D effects are
generated after the selected rows and the selected meridional effects.
The 3D effect generation is stored into the template file (".trb") using python script format:
NI_BEGIN 3d effect
NAME 3d techno effect 1
NI_BEGIN ni3dlayer_recorder
NI_BEGIN ni3dlayer_record
effect_ 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))
When making a 3D effect in AutoGrid5™, it may be necessary to create some additional curves. The
steps creating these curves are recorded in the template but the template cannot be replayed without
manual modification as the curve names vary per IGG™ session. Therefore the user should either
import an external CAD file with pre- defined names 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.
If the user modifies (number of points, clustering,...) an existing block created automatically by
AutoGrid5™ in IGG™ or in a 3D effect in AutoGrid5™, the corresponding faces are reinterpolated .
Due to this, the benefit of the smoothing is lost and the face may not lie on the geometrical surface
anymore.
Blocks created in a 3D effect (by creation or splitting an existing block) are still present even if the
mesh of the row is regenerated. For instance, if a 3D effect is used in order to split the blocks and if
the user asks to mesh again only the row, then the final mesh will contain the initial block and the
two blocks resulting from the splitting of the block. This leads to undefined patches since some
patches of the split blocks are not connected.
This chapter describes the conjugate heat transfer and the cooling capabilities included in AutoGrid5™:
l The conjugate heat transfer (CHT) capability allows the mesh generation of the blade and the end
wall solid bodies.
l The cooling capability allows the mesh generation of basin, basin holes, blade holes, end wall holes
and cooling channel with pins fins and ribs.
The module is only compatible with the default O4H topology on single blade configuration and thus not for
splitter(s) or tandem rows configuration
In this section
12.1 Conjugate Heat Transfer 468
12.2 Cooling - Blade Holes 489
12.3 Cooling - Basin Holes/Separator 506
12.4 Cooling - End Wall Holes 514
12.5 Cooling - Pin Fins 518
12.6 Cooling - Ribs 522
By default AutoGrid5™ generates the mesh of the core flow around the blades including the hub
and shroud gap area. The conjugate heat transfer module allows the mesh generation of the solid
body of the blade and the end walls.
The menu item Cooling/Add Solid Body in the blade contextual menu can be used to activate
the generation of the solid body of the blades. A new item is automatically added into the
configuration tree indicating that the solid body generation is activated.
The mesh into the blade is created using a butterfly topology like in the shroud/hub gap. The
connection between the solid body and the fluid area is matching.
Once the solid body generation has been activated, right-clicking on the new item in the tree
opens a contextual menu of the solid body.
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 squealer
tip, the cooling channel area or the area inside which spanwise holes are defined. In such cases,
the mesh topology covering the solid body area of the blade is divided into four blocks: two
blocks for a butterfly topology covering the area inside the internal offset shape and two blocks
defining another butterfly topology in the area between the offset and the blade definition.
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 width will 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 the type of solid body. Following sections describes the twelve available types of solid
body and their corresponding configuration tree.
When the solid body configuration is not default, the Hub & Shroud Gap Interpolation is not
applied.
In this configuration, the blade solid body is meshed and spanwise holes are allowed. A shroud
gap or hub gap can be defined.
A shroud gap must be defined in this configuration. The blade solid body is meshed and a basin is
defined. Spanwise holes are allowed.
A shroud gap must be defined in this configuration. The blade solid body is meshed and a cooling
channel, a basin and a basin wall are defined. Spanwise basin wall holes and blade holes are
allowed.
In this configuration, the blade solid body is meshed and a cooling channel is defined. Blade holes
are allowed. A shroud gap or hub gap can be defined but the tip wall has no width.
A shroud and/or hub gap must be defined in this configuration. The blade solid body is meshed
and a penny is defined at hub and/or shroud. Spanwise tip wall holes and blade holes are not
allowed.
A shroud gap must be defined in this configuration. The blade solid body is meshed and a
squealer tip is defined. Spanwise tip wall holes and blade holes are not allowed. Three types of
squealer tips are available.
In a cooled turbine blade, basin and internal cooling channel area are defined by a unique offset
surface area of the blade. The squealer tips are defined in a similar way.
The geometry definition of the offset surface is done using the Cooling Geometry Definition
dialog box available when right-clicking on Solid Body in the configuration tree and selecting the
Define Internal Geometry menu.
The surface(s) defining the internal lateral cooling area and the basin can be defined as a blade
definition from:
l a parametric definition using the blade definition as reference.
l an external ".geomTurbo" file.
l an external CAD data file.
By default when a cooling wall has been defined, AutoGrid5™ is using a parametric definition
for the cooling wall. The default parameters can be modified in the Cooling Geometry Definition
dialog box.
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
generation has already been performed, the new curve defining the offset is automatically
displayed in the blade to blade view.
In addition, the Control Points Number along the chord used to defined the offset can be also
modified.
The shape of the offset area is defined according to starting and ending distance along the chord
and the width is computed normally to the chord definition.
If the internal offset surface is defined using a ".geomTurbo" file, the option From External
Data has to be activated.
If the internal offset surface is defined using an external CAD file, the option From External
Data has to be activated.
When clicking on the Load a Geometry File button, a file chooser allows to select an external
CAD file. After the selection, the Import CAD window displays the data and the manual linking
must be performed to define the blade surfaces, the leading edge and the trailing edge as for the
blade definition.
If the offset definition is blunt, an automatic blending (using circular shape) can be performed to
close the cooling wall surface (Blend at Leading/Trailing Edge options)
A geometry check can be performed when clicking on the Check Geometrybutton to detect
possible problems in the geometry definition.
The leading and trailing edge curves can be defined by the user by adding a wizard to the solid
body through the menu Add Wizard LE TE. This menu will add an item Wizard LE TE in the
solid body configuration tree. More details are available in section Leading/Trailing Edge Wizard.
The basin depth, the squealer tip and the bottom basin wall width are defined as for shroud/hub
gaps, by giving a width at the leading edge and at the trailing edge. In addition as for the gaps, the
number of layer (Number of Points) and the layer clustering (Cell Width and Percentage of
Mid-flow Cells) to define the basin, squealer tip and basin wall in the meridional view can be
controlled.
The contextual menu Properties when right-clicking on the configuration tree on Basin, Squealer
Tip and 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, when
right-clicking on Solid Body in the configuration tree and selecting the Mesh Properties menu;
Near the trailing edge, by default (Optimized option) the grid points distribution along the solid
wall of the blade is clustered around the location of the internal cooling wall definition.
The number of points (N2 in previous figure) in the azimuthal direction defining the width of the
blade solid mesh 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 off with the parameter Relax the B2B Mesh Clustering.
When the configuration is presenting inserted cooling tubes, these entities can be meshed by
defining a cooling channel (Internal Offset Shape Control) and a skin wall.
The inserted cooling tube will be considered as a blade including a cooling channel (fluid block)
and the skin wall will be used to mesh the fluid area outside of the tube but inside of the real
blade.
The contextual menu Define Geometry when right-clicking on the Skin Mesh Boundary in the
configuration 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 defined
using the Import CAD window by linking the blade surfaces, the leading edge and the trailing
edge as for the blade definition.
In addition, two control lines (defined in the spanwise direction) can be added into the
".geomTurbo" 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 connection) afterwards with the solid mesh parts of the real blade.
Finally, when the cooling channel and the skin wall are defined, the mesh of the inserted cooling
tube area can be meshed after deactivating the option Around the Skin Mesh in the 3D Control
as presented in next section.
3D Control
The Activate Mesh Generation parameters control the areas that will be removed from the mesh
after the grid generation of the blade holes (Cooling - Blade Holes).
By default, AutoGrid5™ creates the fluid core flow around the blade and the boundary condition
with the solid body of the end walls is set to solid. The contextual row menu items Cooling/Add
Hub Wall and Cooling/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.
The hub/shroud end walls are not available for blade with blunt/sharp leading or trailing edge, for
multi-bladed row and HOH/H&I B2B topologies.
Geometry Definition
The Properties menu available when right-clicking on the Hub Wall and/or Shroud Wall in the
configuration tree opens a dialog box used to control the width of the selected end wall.
Topology Definition
The Properties menu available when right-clicking on the Hub Wall and/or Shroud Wall in the
configuration tree opens a dialog box used to control the number of points used to mesh the end
wall in the spanwise direction and the width of the end wall.
3D Mesh Generation
The Generate menu available when right-clicking on the Hub Wall and/or Shroud Wall in the
configuration tree is used to start the 3D generation of the selected end wall. The 3D mesh of the
selected 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 menu
bar can also be activated to involve the grid generation of the end wall after the mesh generation
of the selected row.
The meshes generated by AutoGrid5™ using the default topology contain one block surrounding
the blade, called the skin block. This block is used to generate high grid quality in the boundary
layer. The solid body of the blade contains also a similar O-block connected to the skin block
using a 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 blade
holes and around the blade holes. They will be called matrix blocks in the following sections.
It is suggested to freeze the skin mesh in the Optimization Properties dialog box ( Skin Mesh
Control ) with the introduction of cooling holes, in order to improve the quality of the full non
matching (FNMB) connection between the skin block and the core flow. The option is not available
for a blunt leading or trailing edge.
The fillet with butterfly topology is not compatible with cooling holes on the blade.
The non-axisymmetric end walls are not compatible with cooling holes on the blade.
The cooling blade hole is not compatible with a double blunt blade.
When adding a cooling hole in the blade, the following steps will be performed to create the mesh
in the blade hole and around the blade hole:
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.
3. The hole mesh is projected in the 3D space and the matrix block is divided. The hole meshes
replace some of the divided matrix areas.
4. The connection between the matrix area and the core flow becomes full non matching.
5. The connection between the internal cooling area (cooling channel, basin, basin wall) and the
solid body of the blade becomes full non matching.
6. The matrix is divided in spanwise direction near the hub and the shroud to preserve the
boundary layer of the main channel. The connection between the upper part of the matrix and
the middle part becomes full non matching. The connection between the lower part of the
matrix and the middle part becomes full non matching.
7. The matrix is divided in meridional direction according to the hole line mesh location. The
connection between the hole line mesh and the matrix becomes full non matching.
The Cooling/Add Holes Line menu available when right-clicking on Main Blade adds a new
hole line entity in the configuration tree. By default a new hole line contains a single hole that is
automatically displayed in the meridional view.
The Preview 3D and Hide 3D buttons (as the Preview/Hide 3D Location menus) are used to
perform a quick display of the 3D definition of the cylinder used to define the holes. The 3D
display is only available if the matrix block is available when the 3D mesh generation of the row
has already been completed. Each modification of any hole lines parameter implies an automatic
refresh of the display.
Geometry Control
In the Blade Cooling Holes Line Definition , the Geometry thumbnail gives access to the
parameters controlling the geometry of the line of holes.
The number of holes in a line can be modified through the parameter Number of Hole on the
Line.
Seven different types of holes can be defined: circular, rectangular, oval, circular at trailing edge
(trailing edge holes), groove at trailing edge, 4 sided and oval at trailing edge.
For each type, the parameters controlling the geometry are different.
The trailing edge grooves are only available for mesh with blunt cooling wall.
The location of a hole is defined by the 3D anchor point of its axis. Three modes can be used to
define this point.
When using the % of meridional chord mode, the quick display will be an approximation of the
hole location.
Parametric Mode
The axis is controlled by giving the spanwise (Alpha) and the streamwise (Beta) deviation from
the blade surface normal.
The Parametric mode is applied to the entire holes line. Each modification of a parameter affects all
the holes of the line. To modify a single hole axis, first the parametric mode is 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.
The dimension of the holes depends of the shape chosen in Holes Number Control.
Circular Shape
When circular shape is selected, the diameter and the depth of the holes can be imposed (each
hole can be controlled separately).
When a cooling wall is defined, the depth is only used for quick visualization of the hole location.
4-Sided Shape
The four points coordinates defining the shape of the quadrilateron must be entered.
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).
The hole geometry can be defined using an external data file through the Load Geometry File
menu available when right-clicking on the holes line 1. A file chooser allows to select an external
hole line file. The file formats used to define hole line are presented in next sections.
The Export Holes Geometry menu available when right-clicking on the holes line 1 is used to
export the hole line definition into an external file. The name of the file is automatically chosen
according to the grid configuration and the project file name. Therefore, before exporting a hole
line geometry, the project must be saved. For example, when exporting the "holes line 5" of a
project 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 was saved.
The SCALE_FACTOR is optional. It is used to convert the data if it is not specified in meter (i.e.:
data in millimeter needs to set the SCALE_FACTOR to 0.001).
Mesh Control
In the Blade Cooling Holes Line Definition, the Mesh Control thumbnail gives access to the
parameters controlling the mesh topology around and inside the holes.
The grid point distribution panel allows the user to change the grid point number (by left-clicking
on the it when highlighted in red) around the holes. According to the shape of the holes, the
parameters to define can be different.
Optimization Control
The number of smoothing steps around ( Optimization Steps Around Hole ) and inside
(Optimization Steps Inside Holes) the holes can be modified. The type of smoothing can also be
chosen with or without skewness control (Skewness Control Around/Inside Holes option).
For the trailing edge grooves, only the smoothing steps inside the holes can be controlled.
The size of the mesh upstream and downstream can be controlled by Upstream/Downstream
Normalized Distance. These parameters allow the user to change the upstream and downstream
length of the area where the mesh around the holes will be created.
The upstream and downstream length is calculated in the parametric space of the surface built
from the skin mesh. The hole size is then measured and multiplied by the normalized parameters.
By adding the value calculated to the hole center, the upstream and downstream distance is
obtained. The final distance in physical space is approximately proportional to
Upstream/Downstream Normalized Distance since it is calculated in the parametric space.
When two lines of holes are close to each other and one of the holes line spanwise shape must
drive the shape of the mesh of the second holes line, the option Holes Line Mesh Shape Control
can be applied on the second holes according to the holes line spanwise shape configuration.
By default, when lines of holes are defined, AutoGrid5™ will first divide the matrix block in
spanwise direction near the hub and near the shroud to keep as much as possible of the end wall
boundary layer of the matrix mesh. The indices of division can be controlled by the user in the
thumbnail Global Control.
The tolerance used to compute the intersection of the holes with the matrix block can be modified
by modifying the Holes Intersection Tolerance available in the Expert page.
Because the preview using Preview 3D button can be slightly different from the final computed
location, the Preview Tube Mesh button is used to display the real location of the holes.
Once the matrix and the holes definition are completed, the Cooling/Generate Holes menu
available when right-clicking on the Main Blade in the configuration tree allows to start the holes
mesh generation without regenerating the row mesh.
The option Generate Blades Cooling Holes available when pressing the Generate 3D button of
the top menu bar can also be activated to mesh the holes after the selected row mesh generation.
As explained at the beginning of the section Geometry Definition, the blade hole(s) meshes are
inserted into the matrix block of the default mesh computed by AutoGrid5™ (skin block around
the blade). Therefore, before starting the blade holes mesh generation, the default mesh inside the
row must have been computed using Generate 3D button. This mesh is usually called the matrix
mesh. It is strongly advised to save and store this mesh on disk (File/Save Project As) before
starting the blade 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 matrix
project can be reloaded, the holes definition changed and the holes mesh generation started
without regenerating the default row mesh (matrix).
By default, the mesh (matrix) generated inside the solid body of the blade contains two blocks
(butterfly topology at the trailing edge - Blade to Blade Control ). Due to the mesh generation
method, the matrix mesh is different if trailing edge holes or grooves must be generated. The
butterfly topology is degenerated into a single O- block. Therefore, if a new line of holes of these
types is added after having generated the matrix, the system will prompt the user to regenerate the
matrix before starting the holes line. The same behavior can be observed if the matrix has been
generated with trailing edge holes or grooves defined that are removed afterwards.
When the blade configuration contains a cooling wall definition, a basin and a basin wall, holes
into the basin wall and a solid separator into the basin can be defined within AutoGrid5™.
The blade to blade mesh into the cooling wall area is composed by two blocks. After defining the
basin holes and separator, AutoGrid5™ will compute the location of the basin holes and the
separator into this mesh and than replace the butterfly topology by a new complex topology
capturing the defined holes and separator. The connection between the cooling 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 the
same block topology and matching connections between the cooling channel, the basin wall, the
basin and the shroud gap area.
The Add Radial Hole menu available when right-clicking on Solid Body adds a new hole entity
in the configuration tree.
The Properties menu available when right-clicking on hole 1 opens a dialog box to control the
geometry and the mesh of the selected hole.
Geometry Control
Parametric Mode
When the option Use Parametric Definition is active, a parametric location is used to define the
basin holes. Two parameters fully define the location of the holes:
l Location (% of mean line): this parameter defines the hole center on the mean line by giving
a percentage of the mean line length of the cooling wall definition ("A" in next figure).
l Location (% of width): once the hole center is located on the mean line, a deviation normal to
the mean line can be defined. The amplitude of the deviation is given in % of cooling wall
width ("B" in next figure).
Radial cooling holes cannot be generated on the same chord position (same % of mean line ).
XYZ Mode
When the option Use Parametric Definition is switch off, the holes geometry is defined in the
Cartesian 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
system indicates to the user two layer indices on which Generate B2B must be applied before
launching the 3D generation.
The parametrization of the holes is done during these phases and it assumes that the axis given by
the user will be followed by the holes. Each time the user wants to modify the hole location (i.e
changing 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
cylinder used to define the holes. The 3D display is only available if the matrix block is available
when the 3D mesh generation of the row has already been completed. Each modification of any
hole lines parameter implies an automatic refresh of the display.
Due to the stacking technique used to define the basin holes, the holes are always normal to the
surface of the basin and are following the spanwise direction (J-direction) of the blade.
Mesh Control
The mesh inside and around the holes can be controlled using the following parameters.
l Number of Point Along Sides: this parameter is used to modify the number of points around
the holes.
l Location Bnd Smoothing Steps: this parameter is used to smooth the limit of the blocks at the
boundary with the solid body of a hole located between others holes/separator.
The Add Separator menu available when right-clicking on Solid Body adds a new separator
entity in the configuration tree.
The Properties menu available when right-clicking on the separator 1 opens a dialog box to
control the geometry and the mesh of the selected separator.
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, basin wall, cooling channel and the shroud gap area.
No control is given on the streamwise number of points between the holes. AutoGrid5™ tries to keep
the same clustering as in the solid body to avoid too high difference of grid points along the full non
matching connections.
In the section Mesh of End Wall Solid Body, the grid generation of the end walls solid body is
presented. In addition, lines of holes located on the end walls can be defined and meshed within
AutoGrid5™.
The method is similar to the grid generation of blade line holes describes in the section Cooling -
Blade Holes. As for the blades line holes, the grid generation of the line of holes on the end walls
is based on the insertion of the mesh around the holes into a matrix mesh. This matrix mesh is
created automatically by AutoGrid5™. It consists in two H blocks used to mesh the solid body of
the end wall and the connected fluid boundary layer.
The Properties menu available when right-clicking on Hub Wall or Shroud Wall opens a dialog
box to control the mesh generation of the matrix. The blade to blade visualization of the H block
can be controlled using the menu View B2B Mesh and Hide B2B Mesh.
The user can control the smoothing steps (Hole Matrix Optimization Steps) and the multigrid
acceleration (Hole Matrix Multigrid Optimization) to optimize the H block of the matrix. The
number of layers on which the end walls holes block will be extended into the fluid boundary
layer is controlled by the Connected Layers parameters.
The Add Holes line menu available when right-clicking on Hub Wall or Shroud Wall adds a new
holes line entity in the configuration tree.
The holes geometry and mesh controls are similar to the ones presented for the blade holes in
Blade Holes Properties.
A quick display of the end walls holes is also available in the blade to blade view but it appears 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 boundary 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 leading edge.
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
the holes mesh generation without regenerating the row mesh.
The options Generate End Wall and Generate End Wall Cooling Holes available when
pressing the Generate 3D button of the top menu bar can also be activated to mesh the holes after
the selected row mesh generation.
The pin fins are usually located in the cooling channel of the blade and used to promote the
turbulence and to exchange heat. These entities can be defined and meshed within AutoGrid5™.
The Add Pin Fins Channel menu available when right-clicking on Cooling Channels adds a pin
fins channel entity in the configuration tree.
A pin fins channel entity is used to mesh solid pin fins lines into a box (cooling channel) defined
by the 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
line direction. This block will be used in a similar way as the matrix mesh used for the blade and
end walls holes.
The Add Pin Fins Line menu, available when right-clicking on pin fins channel 1 in the
configuration tree, is used to add a new pin fins line into the configuration tree.
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 geometry and the mesh of the selected hole.
The grid points distribution can be imposed for the entire pin fins line but not for only one pin fin of
the line in order to ensure matching connection.
The mesh inside the cooling channel including the pin fins is automatically computed when
selecting 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 the quick access
pad is taken into account. Using the default cell width of 1e-5 may lead to problems if the geometry
is defined in mm.
The ribs are usually located in the cooling channel of the blade and used to promote the
turbulence and to exchange heat. These entities can be defined and meshed within AutoGrid5™.
Ribs Properties
The Add Ribs Channel menu available when right-clicking on Cooling Channels adds a ribs
channel entity in the configuration tree.
A ribs channel entity is used to mesh solid ribs lines into a box (cooling channel) defined by the
user. The box is a IGG™ block created manually. The block should have a special orientation:
l the I direction from front to back (front side being the side where the rib is located),
l the J direction from hub to shroud,
l 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.
From 3D View
After selecting the 3D view in AutoGrid5™, a IGG™ mesh (".igg" file) can be imported in the
3D view (File/Import/IGG Project). The desired block representing the cooling channel needs
to be activated by left-clicking on it in the 3D view. The Define Box from Active Block menu,
available when right-clicking on ribs channel 1 in the configuration tree, allows to link the active
block to the ribs channel. After defining the box, the template has to be saved ( File/Save
Template) and reopened (File/Open Project) otherwise the blocks of the imported IGG™ mesh
will stay in the 3D view and conflict with new created blocks in AutoGrid5™.
The Define Geometry menu, available when right-clicking on ribs channel 1 in the configuration
tree, 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
one side of the cooling channel box (called the "front" side, the opposite being the "back" side).
The basic (mandatory) geometry is defined by:
l a basic plane (plane origin and normal direction) representing the lower side (Define basic
planes button),
l a height (Height) representing the upper side (basic plane shifted by height along its normal),
l a thickness (Thickness) representing the back side (front side offset of the thickness).
In addition, optional rib geometry extensions are possible:
l 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).
l a right extension (bar extension on the right side with the same height and thickness as the
main bar) defined by a plane (Define right extensions button).
l separation(s) (an interruption in the main bar, through which the fluid will pass) defined by
two planes (defining the start and the end of the bar cut) (Add separations button).
l a Full Channel option allowing to completely fill the channel with ribs, meaning that no fluid
can pass perpendicularly to the ribs.
The next figure is illustrating the options in a section of a rib channel.
The Define Geometry menu, available when right-clicking on ribs channel 1 in the configuration
tree, is used to control the geometry and the mesh of the ribs.
The mesh inside the cooling channel including the ribs is automatically computed when selecting
the 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 the quick access pad
is taken into account. Using the default cell width of 1e-5 may lead to problems if the geometry is
defined in mm.
The final mesh contains solid blocks defining the ribs and fluid blocks around the ribs defining the
fluid area of the box (cooling channel). The mesh includes six full non matching connections with
only left patches defined. These connections are useful to define the link between the ribs boxes
and the surrounding areas such as the blade solid body.
PYTHON SCRIPT
Scripts 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™ User Manual.
Specific commands are dedicated to AutoGrid5™ and are described here after. More details on the
available python commands are available in the file "AUTOGRID.py" provided in the NUMECA
distribution after installation (i.e. under Windows, the file is available in "~/_python/_autogrid/").
By default, French accents cannot be included in a script except if the string # coding=utf-8 is added as first
line of the script.
In this section
13.1 Running a Script File 529
13.2 Commands Description 529
Script 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 then
open 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.
Commands are classified by categories and by classes. Several classes are defined in
AutoGrid5™ to group functions related to generic entities: Row, Blade, Gap, RSInterface,
StagnationPoint, TechnologicalEffect,...
The organization charts shown below aim to provide a global overview of how the different
classes are organized in dependent levels and how they interact with each other.
Example
To access a meridional control line the command z_cst_line(i) can be used and the actions as
listed in "RSInterface Class Commands" (p. 583) can be applied:
z_cst_line(1).get_clustering_relaxation_location()
To access a rotor/ stator interface, an access command like inlet() can be used and the actions as
listed in "RSInterface Class Commands" (p. 583) can be applied:
row(1).inlet().get_shape()
To access the hub gap of the first blade of the second row the access command row(2).blade
(1).hub_gap() can be used. Actions as listed in "Gap Class Commands" (p. 574) can then be
applied, e.g.:
row(2).blade(1).hub_gap().set_width_at_leading_edge(value)
On Windows:
The specification of path names when using commands requiring file names as input must be
performed using a Linux style coding. This practically means that / should be used as separator
between directories instead of \ and path names should be written between quotes:
"/usr/people/test.trb".
l a5_open_project (trb_file_name)
l a5_open_template(trb_file_name)
l a5_save_template(trb_file_name)
l a5_save_project(trb_file_name)
l a5_save_mesh(mesh_file_name)
l a5_save_mesh_V61(mesh_file_name)
l a5_save_mesh_V62(mesh_file_name)
l a5_save_mesh_V72(mesh_file_name)
l a5_save_mesh_V86(mesh_file_name)
l a5_save_and_merge_project_mesh()
l CGNS_format(value) (New in AutoGrid5™ v12.1)
Set the type of the CGNS format. Value should be between 0 for ADF and 1 for HDF5.
l a5_get_project_path()
Returns the path to the current project. The project path does not contain the name of the
project. A directory separator - '/' on Linux and '\' on Windows - is added at the end of the
path. This command can be combined with a5_get_project_name() to obtain the location and
name of the current project.
l a5_get_project_name()
Returns the name of the current project. Only the name of the project is given, without the path
to the project. The project name is returned as projectname.trb . This command can be
combined with a5_get_project_path() to obtain the location and name of the current project.
l a5_init_html_report_file()
l a5_export_CEDRE(filename)
Exports a mesh in CEDRE format with the specified filename.
l a5_export_CEDRE_all_blocks(filename,merging,merged_blockname)
Exports all the blocks of the mesh in CEDRE format with the specified filename.
merging is set to 1 to group all blocks in a single CEDRE domain during export, or set to 0 to
create a domain per block.
merged_blockname is the userdefined name of the merged block when merging is set to 1.
l a5_export_CEDRE_row_by_row(filename,merging,merged_blockname)
Exports all the blocks of the mesh of each row in CEDRE format with the specified filename.
l a5_set_import_geometry_rotation_axis(orig, stream_direction,span_direction)
Defines the rotation axis for CAD import.
l a5_import_geometry_file(file_name)
Imports a geometry file, either CATIA, Parasolid™, .dat, .geom, .geomTurbo 4 & 5 or IGES
formats.
l a5_import_and_replace_geometry_file(file_name)
l a5_get_import_geometry_repository()
l a5_clean_import_geometry()
Deletes all the geometry entities already loaded.
l a5_link_to_hub(curve_names)
Curve_names should be a list, even if it is composed of only 1 element (use [ ]).
l a5_link_to_hub_surface(row,surface_names)
Surface_names should be a list, even if it is composed of only 1 element (use [ ]).
l select()
l unselect()
l meshConfigurationDomain()
l select_configuration()
l unselect_configuration()
l parent()
²
l initialize(machine_type,row_type,rotationSpeed,periodicity)
Machine_type should be between 1 and 13:
1: wind turbine
2: axial turbine
3: Francis turbine
4: Kaplan turbine
5: inducer
6: axial compressor
7: centrifugal impeller
8: centrifugal diffuser
9: return channel
10: contra rotating fan
11: centrifugal pump
12: axial fan
l delete()
l select()
l set_name(name)
l get_name()
l create()
l set_width(value)
l get_width()
l set_location(value)
l get_location()
l delete()
l block_list()
l setGraphicsRepetition(value)
l setDefaultGraphicsRepetition()
l get_index()
l select()
l unselect()
l load_geometry(geomTurbo_file_name)
The file specified should have the geomTurbo format 4 or 5. Only the row geometry is
replaced and not the hub and/or shroud.
l add_row_upstream()
l add_row_downstream()
l zoom_at_inlet(level,location)
Location should be between -1 and 1.
l zoom_at_outlet(level,location)
Location should be between -1 and 1.
Topology Management
l load_topology(file_name)
l save_topology(file_name)
l copy_topology()
l paste_topology()
l save_b2b_topology(file_name)
l load_b2b_topology(file_name)
l row_wizard()
l get_bypass_location()
Returns the row type: 0 if normal, 1 if on nozzle, 2 if bypass or 3 if down bypass.
l inlet()
Returns an object of class RSInterface.
l outlet()
Returns an object of class RSInterface.
l outlet2()
Returns an object of class RSInterface.
l num_effect3D()
l effect3D(i)
l new_effect3D()
Returns an object of class TechnologicalEffect3D.
l num_blades()
l blade(i)
l add_blade()
l add_hub_gap()
Returns an object of class Gap. If gap does not exist, creates it to all row blades.
l add_shroud_gap()
Returns an object of class Gap. If gap does not exist, creates it to all row blades.
l get_hub_gap()
get_shroud_gap()
Return the presence of a gap.
l add_hub_fillet()
l add_shroud_fillet()
Row Properties
l set_name(name)
l get_name()
l set_clustering(value)
l get_clustering()
l set_upstream_block_relaxation(a)
l get_upstream_block_relaxation()
l set_downstream_block_relaxation(a)
l get_downstream_block_relaxation()
l 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 user
defined.
l set_non_axisymmetric_hub(a)
l get_non_axisymmetric_hub()
l set_non_axisymmetric_hub_repair_damage(a)
l get_non_axisymmetric_hub_repair_damage()
l set_non_axisymmetric_hub_projection_type_face_normal()
l get_non_axisymmetric_hub_projection_type_face_normal()
l set_non_axisymmetric_tip_gap(a)
l get_non_axisymmetric_tip_gap()
l set_non_axisymmetric_tip_gap_repair_damage(a)
l get_non_axisymmetric_tip_gap_repair_damage()
l set_non_axisymmetric_tip_gap_repetition(value)
l get_non_axisymmetric_tip_gap_repetition()
l set_non_axisymmetric_tip_gap_display(a)
a = 1, draw non axisymmetric surface if it is not drawn.
a = 0, remove non axisymmetric surface drawing if it is drawn.
Row Snubber
l add_snubber()
Returns an object of class Snubber.
l get_number_of_snubbers()
l hub_end_wall()
l shroud_end_wall()
l add_hub_end_wall()
l add_shroud_end_wall()
l set_flow_path_control_hub_clustering(value)
l get_flow_path_control_hub_clustering()
l set_flow_path_control_shroud_clustering(value)
l get_flow_path_control_shroud_clustering()
l set_flow_path_control_cst_cells_number(value)
l get_flow_path_control_cst_cells_number()
l set_flow_path_control_control_point_number(value)
l get_flow_path_control_control_point_number()
l set_flow_path_control_intermediate_point_number(value)
l get_flow_path_control_intermediate_point_number()
l set_flow_path_control_smoothing_steps(value)
l get_flow_path_control_smoothing_steps()
l set_flow_path_control_distribution_smoothing_steps(value)
l get_flow_path_control_distribution_smoothing_steps(()
l set_flow_path_control_hub_distribution_uniform()
l set_flow_path_control_hub_distribution_curvature()
l get_flow_path_control_hub_distribution()
l set_flow_path_control_shroud_distribution_same()
l set_flow_path_control_shroud_distribution_projection()
l set_flow_path_control_shroud_distribution_minimal_distance()
l get_flow_path_control_shroud_distribution()
B2B Control
l initialize_blades_reference_angle()
Initializes the blade reference angle for all the blades of the row.
Optimization
l set_row_optimization_steps(number_of_steps)
l get_row_optimization_steps()
l set_row_optimization_steps_in_gap(number_of_steps)
l get_row_optimization_steps_in_gap()
l set_row_full_multigrid_optimization_steps(value)
l get_row_full_multigrid_optimization_steps()
l set_row_optimization_skewness_control(value)
Value should be "0" or "no", "1" or "medium", "2" or "yes".
l get_row_optimization_type()
l set_row_optimization_skewness_control_in_gap(value)
Value should be "0" or "no", "1" or "medium", "2" or "yes".
l get_row_optimization_type_in_gap()
3D Mesh Control
l set_span_interpolation(value)
Value should be between 0 and 100.
l get_span_interpolation()
l set_untwist_upstream_block(a)
l get_untwist_upstream_block()
l set_untwist_upstream_block_stream_location(value)
Value should be between 0 and 100.
l select()
l delete()
l set_name(name)
l get_name()
l basin()
l add_basin()
l sheet()
l hub_gap()
Returns an object of class Gap. If gap does not exist, creates it.
l set_stitch_surfaces_at_LE_TE(value)
Value should be either 0 if the blade surfaces will not be stitched, 1 for the option inverse
lofting or 2 for the option lofting with guide.
l get_stitch_surfaces_at_LE_TE()
Returns 0 if the blade surfaces are not stitched, 1 if the option inverse lofting is selected or 2 if
the option lofting with guide is selected.
l expand_at_hub(expansion_factor, extent_offset=0)
l expand_at_shroud(expansion_factor, extent_offset=0)
Applies an expansion treatment at hub or shroud (more details in "Expand" (p. 221)). When
the blade is defined with a native ".geomTurbo" format (sectional data) the value of the
expansion_factor is a fraction of the normalized spanwise height (0=hub, 1=shroud) and the
extent_offset should be set to 0 (i.e. this parameter is not needed). If the blade geometry is
imported via CAD, then the expansion treatment requires a distance value different from zero
for both the expansion_factor (Cut offset parameter) and the extent_offset (Extension offset
parameter).
l apply_rotation(x,y,z,nx,ny,nz,angle)
Applies a rotation of the selected blade and takes as inputs the rotation axis (unit vectors), the
anchor point and the rotation angle in degrees (more details in "Apply a Rotation" (p. 220)).
The option can only be used when the blade geometry is defined with sectional data (native
".geomTurbo" file).
l set_hub_treatment(treatmentType, *args)
Set the hub expansion treatment type and its corresponding arguments.
l set_shroud_treatment(treatmentType, *args)
Set the shroud expansion treatment type and its corresponding arguments.
The expansion treatment at the hub and shroud can be specified with multiple options. For
more details on these options see also: "Expansion at Hub/ shroud" (p. 221). Every treatment
type has an index, which is given as the first argument of the command. Depending on the
treatment type, a number of additional arguments may be required, described in the table
below. The complete set of arguments is thus made up of the treatment type index, followed
by the additional required arguments, if any.
0 Unchanged None 1
Treat blend
3 Cut offset, extension offset 3
with offset
l get_hub_treatment()
Get the current hub expansion treatment type and its corresponding arguments. The output is a
list following the same format as the input for the set_hub_treatment() command described in
the table above.
l get_shroud_treatment()
Get the current shroud expansion treatment type and its corresponding arguments. The output
is a list following the same format as the input for the set_shroud_treatment() command
described in the table above.
Blade Duplicate
l compute_default_blade_rotation_axis(location)
Computes the rotation axis and the center of rotation of the selected blade.
l duplicate(Zangle,bladeangle,n,rotation_center,rotation_axis)
l set_geometry_data_reduction_distance_criteria(a)
l get_geometry_data_reduction_distance_criteria()
l set_geometry_data_reduction_angle_criteria(a)
l get_geometry_data_reduction_angle_criteria()
l set_geometry_data_reduction(a)
l get_geometry_data_reduction()
l set_geometry_control_points_redistribution(a)
l get_geometry_control_points_redistribution()
l set_geometry_control_points_redistribution_npts_at_le(a)
l get_geometry_control_points_redistribution_npts_at_le()
l set_geometry_control_points_redistribution_npts_on_middle(a)
l get_geometry_control_points_redistribution_npts_on_middle()
l set_geometry_control_points_redistribution_cst_cells_on_middle(a)
l get_geometry_control_points_redistribution_cst_cells_on_middle()
l set_geometry_control_points_redistribution_npts_at_te(a)
l get_geometry_control_points_redistribution_npts_at_te()
l set_geometry_control_points_redistribution_spacing_at_le(a)
l get_geometry_control_points_redistribution_spacing_at_le()
l set_geometry_control_points_redistribution_spacing_at_te(a)
l get_geometry_control_points_redistribution_spacing_at_te()
l set_blunt_treatment_at_leading_edge(a)
l get_blunt_treatment_at_leading_edge()
l set_blunt_treatment_at_trailing_edge(a)
l get_blunt_treatment_at_trailing_edge()
l set_sharp_treatment_at_leading_edge(a)
Closes the blunt leading edge by a linear edge.
a = 1, activate sharp treatment at leading edge.
a = 0, deactivate sharp treatment at leading edge.
l get_sharp_treatment_at_leading_edge()
l set_blend_treatment_at_leading_edge(a)
Closes the blunt leading edge by a circular shape.
l get_blend_treatment_at_leading_edge()
l set_sharp_treatment_at_trailing_edge(a)
Closes the blunt trailing edge by a linear edge.
l get_sharp_treatment_at_trailing_edge()
l set_rounded_treatment_at_trailing_edge(a)
Closes the blunt trailing edge by a straight line to obtain a O-mesh around the blade.
l get_rounded_treatment_at_trailing_edge()
l set_blend_treatment_at_trailing_edge(a)
Closes the blunt trailing edge by a circular shape.
Topology Control
l set_b2b_default_topology_type(value)
Value should be either 0 for streamwise default topology, 1 for rounded azimuthal default
topology or 2 for rounded streamwise default topology.
l get_b2b_default_topology_type()
Returns 0 for streamwise default topology, 1 for rounded azimuthal default topology or 2
for rounded streamwise default topology.
l set_b2b_default_topology_periodicity_type(value)
Value should be either 0 for non matching periodicity or 1 for matching.
l get_b2b_default_topology_periodicity_type()
l set_b2b_default_topology_enable_high_staggered_optimization()
l set_b2b_default_topology_disable_high_staggered_optimization()
l get_b2b_default_topology_disable_high_staggered_optimization()
l set_b2b_default_topology_disable_high_staggered_detection()
l set_b2b_default_topology_enable_high_staggered_detection()
l get_b2b_default_topology_enable_high_staggered_detection()
l set_b2b_default_topology_normal_inlet_angle()
l set_b2b_default_topology_low_staggered_inlet_angle()
l set_b2b_default_topology_high_staggered_inlet_angle()
l get_b2b_default_topology_inlet_angle()
l get_b2b_default_topology_inlet_staggered_angle()
Returns the type of staggered topology (0 normal, 1 low and 2 high).
l set_b2b_default_topology_normal_outlet_angle()
l set_b2b_default_topology_low_staggered_outlet_angle()
l set_b2b_default_topology_high_staggered_outlet_angle()
l get_b2b_default_topology_outlet_angle()
l get_b2b_default_topology_outlet_staggered_angle()
Returns the type of staggered topology (0 normal, 1 low and 2 high).
l set_b2b_default_topology_throat_control(value)
l set_b2b_default_topology_grid_point_number_azimutal_inlet(value)
l get_b2b_default_topology_grid_point_number_azimutal_inlet()
l set_b2b_default_topology_grid_point_number_azimutal_outlet(value)
l get_b2b_default_topology_grid_point_number_azimutal_outlet()
l set_b2b_default_topology_grid_point_number_azimutal_inlet_up(value)
l get_b2b_default_topology_grid_point_number_azimutal_inlet_up()
l set_b2b_default_topology_grid_point_number_azimutal_outlet_up(value)
l get_b2b_default_topology_grid_point_number_azimutal_outlet_up()
l set_b2b_default_topology_grid_point_number_azimutal_inlet_down(value)
l get_b2b_default_topology_grid_point_number_azimutal_inlet_down()
l set_b2b_default_topology_grid_point_number_azimutal_outlet_down(value)
l get_b2b_default_topology_grid_point_number_azimutal_outlet_down()
l set_b2b_default_topology_grid_point_number_streamwise_inlet(value)
l get_b2b_default_topology_grid_point_number_streamwise_inlet()
l set_b2b_default_topology_grid_point_number_streamwise_outlet(value)
l get_b2b_default_topology_grid_point_number_streamwise_outlet()
l set_b2b_default_topology_grid_point_number_streamwise_blade_upper_side(value)
l get_b2b_default_topology_grid_point_number_streamwise_blade_upper_side()
l set_b2b_default_topology_grid_point_number_streamwise_blade_lower_side(value)
l get_b2b_default_topology_grid_point_number_streamwise_blade_lower_side()
l set_b2b_default_topology_grid_point_number_leading_edge_index(value)
Value is the grid point number controlling the distribution of the number of points between the
inlet and the blade. More details in "Grid Point Number Control" (p. 344).
l get_b2b_default_topology_grid_point_number_leading_edge_index()
Mesh Control
l set_b2b_default_topology_skin_block_expansion_ratio_control(value)
Value is the percentage to further improve/control the expansion ratio of the remaining half of
the layers of the skin block.
l get_b2b_default_topology_skin_block_expansion_ratio_control()
Returns the percentage to further improve/control the expansion ratio of the remaining half of
the layers of the skin block.
l set_b2b_default_topology_cell_width_at_wall(value)
l get_b2b_default_topology_cell_width_at_wall()
l set_b2b_default_topology_cell_width_at_wall_at_hub(value)
l get_b2b_default_topology_cell_width_at_wall_at_hub()
l set_b2b_default_topology_cell_width_at_wall_at_shroud(value)
l get_b2b_default_topology_cell_width_at_wall_at_shroud()
l set_b2b_default_topology_bnd_layer_width(value)
l get_b2b_default_topology_bnd_layer_width()
l get_b2b_default_topology_cell_width_at_wall_interpolation()
l set_b2b_default_topology_cell_width_at_trailing_edge(value)
l set_b2b_default_topology_cell_width_at_leading_edge(value)
l set_b2b_default_topology_expansion_ratio_in_bnd_layer(value)
l get_b2b_default_topology_expansion_ratio_in_bnd_layer()
l set_b2b_default_topology_free_outlet_angle(value)
l get_b2b_default_topology_free_outlet_angle()
l set_b2b_default_topology_free_inlet_angle(value)
l get_b2b_default_topology_free_inlet_angle()
Intersection Control
l set_b2b_default_topology_chord_control_points_number(value)
l get_b2b_default_topology_chord_control_points_number()
l set_b2b_default_topology_intersection_quality(value)
Value should be either 0 for low quality or 1 for high quality.
l get_b2b_default_topology_intersection_quality()
l set_b2b_default_topology_intersection_law(value)
Value should be 0 for curvature or 1 for uniform. Useful only if low quality intersection.
l get_b2b_default_topology_intersection_law()
l set_b2b_intersection_precision_check_ratio(doubleValue) (New in AutoGrid5™ v12.2)
Topology Control
l set_b2b_hoh_topology_enable_inlet_extension()
l set_b2b_hoh_topology_disable_inlet_extension()
l get_b2b_hoh_topology_inlet_extension()
l set_b2b_hoh_topology_enable_outlet_extension()
l set_b2b_hoh_topology_disable_outlet_extension()
l get_b2b_hoh_topology_outlet_extension()
l set_b2b_hoh_topology_inlet_I_extension_type()
l set_b2b_hoh_topology_inlet_H_extension_type()
l get_b2b_hoh_topology_inlet_H_extension_type()
l set_b2b_hoh_topology_outlet_I_extension_type()
l set_b2b_hoh_topology_outlet_H_extension_type()
l get_b2b_hoh_topology_outlet_H_extension_type()
l set_b2b_hoh_topology_inlet_extension_location(value)
l get_b2b_hoh_topology_inlet_extension_location()
l set_b2b_hoh_topology_outlet_extension_location(value)
l get_b2b_hoh_topology_outlet_extension_location()
l set_b2b_hoh_topology_inlet_extension_streamwise_npts(value)
l get_b2b_hoh_topology_inlet_extension_streamwise_npts()
l set_b2b_hoh_topology_outlet_extension_streamwise_npts(value)
l get_b2b_hoh_topology_outlet_extension_streamwise_npts()
l set_b2b_hoh_topology_npts_in_boundary_layer(value)
l get_b2b_hoh_topology_npts_in_boundary_layer()
l set_b2b_hoh_topology_npts_around_boundary_layer(value)
l get_b2b_hoh_topology_npts_around_boundary_layer()
l set_b2b_hoh_topology_suction_and_pressure_side_npts(value)
l get_b2b_hoh_topology_suction_and_pressure_side_npts()
l set_b2b_hoh_topology_H_inlet_azimuthal_npts_1(value)
l get_b2b_hoh_topology_H_inlet_azimuthal_npts_1()
l set_b2b_hoh_topology_H_inlet_azimuthal_npts_2(value)
l get_b2b_hoh_topology_H_inlet_azimuthal_npts_2()
l set_b2b_hoh_topology_H_inlet_azimuthal_npts_3(value)
l get_b2b_hoh_topology_H_inlet_azimuthal_npts_3()
l set_b2b_hoh_topology_I_inlet_azimuthal_npts(value)
l get_b2b_hoh_topology_I_inlet_azimuthal_npts()
l set_b2b_hoh_topology_H_outlet_azimuthal_npts_1(value)
l get_b2b_hoh_topology_H_outlet_azimuthal_npts_1()
l set_b2b_hoh_topology_H_outlet_azimuthal_npts_2(value)
l get_b2b_hoh_topology_H_outlet_azimuthal_npts_2()
l set_b2b_hoh_topology_H_outlet_azimuthal_npts_3(value)
l get_b2b_hoh_topology_H_outlet_azimuthal_npts_3()
l set_b2b_hoh_topology_I_outlet_azimuthal_npts(value)
l get_b2b_hoh_topology_I_outlet_azimuthal_npts()
l set_b2b_hoh_topology_I_inlet_periodic_npts(value)
l get_b2b_hoh_topology_I_inlet_periodic_npts()
l set_b2b_hoh_topology_I_outlet_periodic_npts(value)
l get_b2b_hoh_topology_I_outlet_periodic_npts()
l set_b2b_hoh_topology_gap_matching_with_main_channel()
l set_b2b_hoh_leading_edge_control_type_none()
l set_b2b_hoh_leading_edge_control_type_absolute_distance()
l set_b2b_hoh_leading_edge_control_type_relative_distance()
l set_b2b_hoh_leading_edge_control_type_cell_lenght()
l get_b2b_hoh_leading_edge_control_type()
l set_b2b_hoh_leading_edge_control_absolute_distance(value)
l get_b2b_hoh_leading_edge_control_absolute_distance()
l set_b2b_hoh_leading_edge_control_relative_distance(value)
l get_b2b_hoh_leading_edge_control_relative_distance()
l set_b2b_hoh_leading_edge_control_cell_lenght(value)
l get_b2b_hoh_leading_edge_control_cell_lenght()
l set_b2b_hoh_trailing_edge_control_type_none()
l set_b2b_hoh_trailing_edge_control_type_absolute_distance()
l set_b2b_hoh_trailing_edge_control_type_relative_distance()
l set_b2b_hoh_trailing_edge_control_type_cell_lenght()
l get_b2b_hoh_trailing_edge_control_type()
l set_b2b_hoh_trailing_edge_control_absolute_distance(value)
l get_b2b_hoh_trailing_edge_control_absolute_distance()
l set_b2b_hoh_trailing_edge_control_relative_distance(value)
l get_b2b_hoh_trailing_edge_control_relative_distance()
l set_b2b_hoh_trailing_edge_control_cell_lenght(value)
l get_b2b_hoh_trailing_edge_control_cell_lenght()
l set_b2b_hoh_blade_points_distribution_smoothing_steps(value)
l get_b2b_hoh_blade_points_distribution_smoothing_steps()
l set_b2b_hoh_wake_clustering(value)
l get_b2b_hoh_wake_clustering()
Mesh Control
l set_b2b_mesh_control_bnd_layer_factor(value)
l get_b2b_mesh_control_bnd_layer_factor()
l set_b2b_mesh_control_bnd_layer_cell_width(value)
l get_b2b_mesh_control_bnd_layer_cell_width()
Topology Control
l set_b2b_HI_topology_H_inlet(value)
l get_b2b_HI_topology_H_inlet()
l set_b2b_HI_topology_H_outlet(value)
l get_b2b_HI_topology_H_outlet()
l set_b2b_HI_topology_skin_block(value)
l get_b2b_HI_topology_skin_block()
l set_b2b_HI_topology_H_full(value)
l set_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_down(value)
l get_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_down()
l set_b2b_HI_topology_grid_point_number_streamwise_blade_down(value)
l get_b2b_HI_topology_grid_point_number_streamwise_blade_down()
l set_b2b_HI_topology_grid_point_number_streamwise_blade_lower_side(value)
l get_b2b_HI_topology_grid_point_number_streamwise_blade_lower_side()
l set_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_down(value)
l get_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_down()
l set_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_up(value)
l get_b2b_HI_topology_grid_point_number_streamwise_blade_inlet_up()
l set_b2b_HI_topology_grid_point_number_streamwise_blade_up(value)
l get_b2b_HI_topology_grid_point_number_streamwise_blade_up()
l set_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_up(value)
l get_b2b_HI_topology_grid_point_number_streamwise_blade_outlet_up()
l set_b2b_HI_topology_grid_point_number_azimutal_inlet(value)
l get_b2b_HI_topology_grid_point_number_azimutal_inlet()
l set_b2b_HI_topology_grid_point_number_azimutal_outlet(value)
l get_b2b_HI_topology_grid_point_number_azimutal_outlet()
l set_b2b_HI_topology_grid_point_number_azimutal_inlet_up(value)
l get_b2b_HI_topology_grid_point_number_azimutal_inlet_up()
l set_b2b_HI_topology_grid_point_number_azimutal_outlet_up(value)
l get_b2b_HI_topology_grid_point_number_azimutal_outlet_up()
l set_b2b_HI_topology_grid_point_number_leading_edge_index(value)
l set_b2b_HI_topology_grid_point_number_trailing_edge_index(value)
Mesh Control
l set_b2b_HI_topology_automatic_clustering_relaxation(value)
l get_b2b_HI_topology_automatic_clustering_relaxation()
l set_b2b_HI_topology_clustering_relaxation(value)
l get_b2b_HI_topology_clustering_relaxation()
l set_solid_body_configuration(type)
Type should be between 0 and 12:
0: disable solid body mesh generation
1: basin+cooling channel
2: basin
3: cooling channel
4: radial holes without basin and without cooling channel
5: solid body alone
6: cooling channel without tip wall
7: pennies at hub
8: pennies at shroud
9: pennies at hub & shroud
10: squealer tip on lower side
11: squealer tip on upper side
12: squealer tip on camber line
l get_solid_body_configuration()
l number_of_holes_lines()
l add_holes_line()
l holes_line(i)
l generate_holes()
l solid_body()
l cooling_channel()
l is_solid_body_parametric()
l enable_solid_body_parametric_definition()
l disable_solid_body_parametric_definition()
l enable_solid_body_shape_blunt_trailing_edge()
l disable_solid_body_shape_blunt_trailing_edge()
l number_of_basin_holes()
l add_basin_hole()
l basin_hole(i)
l init_basin_holes_from_external_file(filename)
l export_basin_holes_geometry()
l export_basin_holes_definition()
l number_of_basin_separators()
l add_basin_separator()
l basin_separator(i)
l add_pin_fins_channel()
l select()
l delete()
l link_non_axisymmetric_geometry(surface_names)
l set_non_axisymmetric_hub(a)
l set_non_axisymmetric_hub_repair_damage(a)
l create_chimera_block()
l skip_chimera_block()
l set_topology_HO()
l set_topology_O()
l get_topology_type()
l set_width_at_leading_edge(value)
l get_width_at_leading_edge()
l set_width_at_trailing_edge(value)
l get_width_at_trailing_edge()
l set_clustering(value)
l get_clustering()
l select()
l delete()
l set_chord_length_at_leading_edge(value)
l get_chord_length_at_leading_edge()
l set_chord_length_at_trailing_edge(value)
l get_chord_length_at_trailing_edge()
l set_number_of_points_at_leading_edge(value)
l get_number_of_points_at_leading_edge()
l set_number_of_points_at_trailing_edge(value)
l get_number_of_points_at_trailing_edge()
l set_streamwise_cell_width(value)
l get_streamwise_cell_width()
l set_clustering_relaxation(value)
l get_clustering_relaxation()
l set_width_at_leading_edge(value)
l get_width_at_leading_edge()
l set_width_at_trailing_edge(value)
l get_width_at_trailing_edge()
l set_spanwise_cell_width(value)
l get_spanwise_cell_width()
l set_constant_cell_number(value)
l select()
Selects the current blade fillet item.
l delete()
Deletes the current blade fillet item.
l set_radius_at_leading_edge(value)
l get_radius_at_leading_edge()
Sets or returns the fillet radius assigned at the blade leading edge (more details in "Blade Fillet"
(p. 314): Spanwise Parameters:Radius At Leading Edge).
l set_radius_at_trailing_edge(value)
l get_radius_at_trailing_edge()
Sets or returns the fillet radius assigned at the blade trailing edge (more details in "Blade Fillet"
(p. 314): Spanwise Parameters:Radius At Trailing Edge.
l set_minimum_angle(value)
l get_minimum_angle()
Sets or returns the minimum angle used to treat the fillet geometry when the B2B section
offset method is used (more details in "Blade Fillet" (p. 228) : Geometry Creation
Method:Minimum Angle).
l set_clustering(value)
l get_clustering()
Sets or returns the spanwise cell with (value) at the junction between the straight blade and the
fillet (at the hub or shroud according to the fillet type) on all the control lines before the leading
edge and after the trailing edge (more details in "Blade Fillet" (p. 314) : Spanwise
Parameters:Cell Width At Leading Edge and Spanwise Parameters:Cell Width At
Trailing Edge)
l set_clustering_at_leading_edge(value)
l get_clustering_at_leading_edge()
Sets or returns the spanwise cell with (value) at the junction between the straight blade and the
fillet (at the hub or shroud according to the fillet type) on all the control lines before the leading
edge (more details in "Blade Fillet" (p. 314): Spanwise Parameters:Cell Width At Leading
Edge).
l set_clustering_at_trailing_edge(value)
l get_clustering_at_trailing_edge()
l select()
Selects the current row snubber item.
l delete()
Deletes the current row snubber item.
l link_to_meridional_curve_up(curve_names)
l link_to_meridional_curve_down(curve_names)
Curve_names should be a list of curve names to link to the upper or lower meridional curve
defining the axisymmetric snubber, even if it is composed of only 1 element (use [ ]).
l link_to_geometry_on_blade_pressure_side(surface_names)
l link_to_geometry_on_blade_suction_side(surface_names)
Surface_names should be a list of surface names to link to the 3D snubber defined on the
blade pressure or suction side, even if it is composed of only 1 element (use [ ]).
l link_to_leading_edge_on_blade_pressure_side(curve_names)
l link_to_leading_edge_on_blade_suction_side(curve_names)
l select()
l delete()
l generate(replace_le=1,replace_te=1)
l set_layer_upstream_hub_location(value,update=0)
l get_layer_upstream_hub_location()
l set_layer_downstream_hub_location(value,update=0)
l get_layer_downstream_hub_location()
l set_layer_upstream_shroud_location(value,update=0)
l get_layer_upstream_shroud_location()
l set_layer_downstream_shroud_location(value,update=0)
l get_layer_downstream_shroud_location()
l set_layer_hub_clustering(value,update=0)
l get_layer_hub_clustering()
l set_layer_shroud_clustering(value,update=0)
l get_layer_shroud_clustering()
l set_layer_number(value,update=0)
l get_layer_number()
l set_layer_number_of_control_points(value,update=0)
l get_layer_number_of_control_points()
l set_layer_number_of_constant_cells(value,update=0)
l get_layer_number_of_constant_cells()
l last_section_is_used()
l last_section_is_not_used()
l is_last_section_used()
l first_section_is_used()
l first_section_is_not_used()
l is_first_section_used()
l set_blade_normal_type()
l set_blade_very_low_angle_type()
l set_blade_very_high_angle_type()
l select()
l delete()
l lower_zone()
l upper_zone()
l set_type(value)
Value should be either 0 for lower side, 1 for upper side or 2 for both sides.
l get_type()
l set_width(value)
l select()
l copy_left_meridional_distribution()
l copy_right_meridional_distribution()
l paste_left_meridional_distribution()
l paste_right_meridional_distribution()
l merge_meridional_distribution()
l set_name(value)
l get_name()
l streamwise_number_of_points(value)
l get_streamwise_number_of_points()
l streamwise_index(value)
l get_streamwise_index()
l enable_b2b_control()
l disable_b2b_control()
l get_b2b_control()
l geometry_is_fixed()
l geometry_is_not_fixed()
l get_geometry_is_fixed()
l cell_width_in_streamwise_direction(value)
l get_cell_width_in_streamwise_direction()
l set_end_parameter(norm_param)
Controls the relative position (norm_param) of the last point of the flow path subdivision or
the first point of the next subdivision. Norm_param is relative to the complete control section
and not the subdivision (0 for hub and 1 for shroud).
FIGURE 13.1
Flow path control sections and subdivisions
This class gives access to parameters of basic curves defining the channel, nozzle and ZR effects.
l delete()
l set_discretisation(i)
l get_discretisation()
l set_rotating_property(i)
l get_rotating_property()
l check_geometry()
l set_data_reduction(reduction, min_dist=1e-6, max_angle=80)
l get_data_reduction()
l get_data_reduction_minimal_distance()
l get_data_reduction_maximum_angle()
This class gives access to parameters of blade leading and trailing edge in blade to blade view
(only accessible in default topology). The following commands can be applied to the leading or
trailing edge. Thus, these commands must always be preceded by leadingEdgeControl() or
trailingEdgeControl(), respectively.
l set_distribution_type_absolute_distance()
l set_distribution_type_relative_distance()
l set_distribution_type_cell_lenght()
l get_distribution_type()
l set_distribution_absolute_distance(value)
l get_distribution_absolute_distance()
l set_distribution_relative_distance(value)
l get_distribution_relative_distance()
l set_distribution_cell_lenght(value)
l get_distribution_cell_lenght()
FIGURE 13.3
Parametric location of the leading and trailing edges in B2B view
l get_parametric_location()
Get the parametric location of the leading or trailing edge.
l select()
l delete()
l block_list()
l set_name(name)
l get_name()
l set_parameters(expMax,w,opt,cst,exp,opt2,per,coarse,tol,p,rs1,rs2,rs3)
expMax : maximum expansion ratio in boundary layer, along boundary and general
w : wall cell width
opt : smoothing steps
cst : percentage constant cell
exp : radial expansion
opt2 : far field smooth smoothing steps
per : periodic fnmb
coarse : coarse grid level
tol : connection tolerance
p : propagate theta deviation
rs1 : connection at rotor-stator polyline is periodic FNMB. If set to 1, rs2 and rs3 will not be
considered
rs2 : connection at rotor-stator polyline is matching (1) or non-matching (0)
rs3 : connection at rotor-stator polyline is periodic (1) or non-periodic (0)
Example: technologicalEffectZR (1).set_ parameters (1.4,0.000001,100,50,1,200,1,5,1e-
12,0,0,0,1)
l set_type(i)
l set_rotating_boundaries_rotation_speed(i)
l set_automatic_connection(i)
l set_automatic_number_of_points(i)
l set_maximum_expansion_ratio(i)
Sets maximum expansion ratio in boundary layer, along boundary and general.
l set_maximum_expansion_ratio_general(i)
l set_maximum_expansion_ratio_in_boundary_layer(i)
l set_maximum_expansion_ratio_along_boundary(i)
l select()
l delete()
l block_list()
l set_name(name)
l load_geometry(file_name)
l load_topology(name)
l save_topology(name)
l copy_topology()
l paste_topology()
l 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 [ ]).
l techno_effect_3d_start_edit_mode()
l techno_effect_3d_stop_edit_mode()
l select()
l pinFinsChannel(i)
Returns an object of class PinFinsChannel.
l select()
l delete()
l setName(value)
l getName()
l set_spanwise_location(value,highlight=1)
l get_spanwise_location()
l set_streamwise_location_from_leading_edge(value,highlight=1)
l get_streamwise_location_from_leading_edge()
l set_streamwise_location_from_trailing_edge(value,highlight=1)
l get_streamwise_location_from_trailing_edge()
l set_streamwise_location_on_chord_lenght(value,highlight=1)
l get_streamwise_location_on_chord_lenght()
XYZ Mode
l set_x_location(value,highlight=1)
l get_x_location()
l set_y_location(value,highlight=1)
l get_y_location()
l set_z_location(value,highlight=1)
l get_z_location()
l set_x2_location(value,highlight=1)
l get_x2_location()
l set_y2_location(value,highlight=1)
l get_y2_location()
l set_z2_location(value,highlight=1)
l get_z2_location()
l set_r_location(value,highlight=1)
l get_r_location()
l set_theta_location(value,highlight=1)
l get_theta_location()
l set_z_location(value,highlight=1)
l get_z_location()
l set_r2_location(value,highlight=1)
l get_r2_location()
l set_theta2_location(value,highlight=1)
l get_theta2_location()
l set_z2_location(value,highlight=1)
l get_z2_location()
l set_streamwise_angle(value,highlight=1)
l get_streamwise_angle()
l set_spanwise_angle(value,highlight=1)
l get_spanwise_angle()
l set_x_axis(value,highlight=1)
l get_x_axis()
l set_y_axis(value,highlight=1)
l get_y_axis()
l set_z_axis(value,highlight=1)
l get_z_axis()
l set_r_axis(value,highlight=1)
l get_r_axis()
l set_theta_axis(value,highlight=1)
l get_theta_axis()
l set_z_axis(value,highlight=1)
l get_z_axis()
l set_depth(value,highlight=1)
l get_depth()
Circular Shape
l set_diameter(value,highlight=1)
l get_diameter()
Rectangular/Oval Shape
l set_width(value,highlight=1)
l get_width()
l set_heigth(value,highlight=1)
l get_heigth()
l set_holes_p1x(value,highlight=1)
l get_holes_p1x()
l set_holes_p2x(value,highlight=1)
l get_holes_p2x()
l set_holes_p3x(value,highlight=1)
l get_holes_p3x()
l set_holes_p4x(value,highlight=1)
l get_holes_p4x()
l set_orientation_angle(value,highlight=1)
l get_orientation_angle()
l select()
l delete()
l number_of_holes()
l hole(i)
l setName(value)
l getName()
l preview3D()
l hide2D()
l exportGeometry()
l exportDefinition()
l defineGeometry(file_name)
Holes Number
l set_holes_number(value,highlight=1)
l get_holes_number()
Hole Shape
l set_circular_shape(highlight=1)
l set_rectangular_shape(highlight=1)
l set_oval_shape(highlight=1)
l set_trailing_edge_groove_shape(highlight=1)
l set_trailing_edge_circular_hole_shape(highlight=1)
l set_quadrilateral_shape(highlight=1)
l get_shape(highlight=1)
Hole Location
l set_location_to_blade_upper_side(highlight=1)
l set_location_to_blade_lower_side(highlight=1)
Parametric Mode
l enable_parametric_holes_location(highlight=1)
l set_first_spanwise_parametric_location(value,highlight=1)
l get_first_spanwise_parametric_location(highlight=1)
l set_last_spanwise_parametric_location(value,highlight=1)
l get_last_spanwise_parametric_location()
l set_streamwise_location_on_meridional_chord (value,highlight=1)
l set_streamwise_location_from_leading_edge(value,highlight=1)
l set_streamwise_location_from_trailing_edge(value,highlight=1)
l set_first_streamwise_location_on_meridional_chord(value,highlight=1)
l get_first_streamwise_location_on_meridional_chord()
l set_first_streamwise_location_from_leading_edge(value,highlight=1)
l get_first_streamwise_location_from_leading_edge()
l set_first_streamwise_location_from_trailing_edge(value,highlight=1)
l get_first_streamwise_location_from_trailing_edge()
XYZ Mode
l enable_xyz_holes_location(highlight=1)
l set_x_location(value,highlight=1)
l get_x_location()
l set_y_location(value,highlight=1)
l get_y_location()
l set_z_location(value,highlight=1)
l get_z_location()
l set_x2_location(value,highlight=1)
l get_x2_location()
l set_y2_location(value,highlight=1)
l get_y2_location()
l set_z2_location(value,highlight=1)
l get_z2_location()
RTHZ Mode
l enable_mtheta_holes_location(highlight=1)
l set_r_location(value,highlight=1)
l get_r_location()
l set_theta_location(value,highlight=1)
l get_theta_location()
l set_z_location(value,highlight=1)
l get_z_location()
l set_r2_location(value,highlight=1)
l get_r2_location()
l set_theta2_location(value,highlight=1)
l get_theta2_location()
Hole Axis
Parametric Mode
l enable_parametric_holes_axis(highlight=1)
l set_streamwise_angle(value,highlight=1)
l get_streamwise_angle()
l set_spanwise_angle(value,highlight=1)
l get_spanwise_angle()
XYZ Mode
l enable_xyz_holes_axis(highlight=1)
l set_x_axis(value,highlight=1)
l get_x_axis()
l set_y_axis(value,highlight=1)
l get_y_axis()
l set_z_axis(value,highlight=1)
l get_z_axis()
RTHZ Mode
l enable_rthz_holes_axis(highlight=1)
l set_r_axis(value,highlight=1)
l get_r_axis()
l set_theta_axis(value,highlight=1)
l get_theta_axis()
l set_z_axis(value,highlight=1)
l get_z_axis()
Hole Dimension
l set_depth(value,highlight=1)
l get_depth()
Rectangular/Oval Shape
l set_width(value,highlight=1)
l get_width()
Hole Orientation
l set_orientation_angle(value,highlight=1)
l get_orientation_angle()
l set_number_of_points_in_boundary_layer(value,highlight=1)
l get_number_of_points_in_boundary_layer()
l set_number_of_points_streamwise(value,highlight=1)
l get_number_of_points_streamwise()
l set_number_of_points_spanwise(value,highlight=1)
l get_number_of_points_spanwise()
l set_number_of_points_streamwise_left(value,highlight=1)
l get_number_of_points_streamwise_left()
l set_number_of_points_streamwise_right(value,highlight=1)
l get_number_of_points_streamwise_right()
l set_number_of_points_spanwise_up(value,highlight=1)
l get_number_of_points_spanwise_up()
l set_number_of_points_spanwise_down(value,highlight=1)
l get_number_of_points_spanwise_down()
Optimization
l set_number_of_optimization_steps_inside_holes(value,highlight=1)
l get_number_of_optimization_steps_inside_holes()
l enable_skewness_control_inside_holes()
l disable_skewness_control_inside_holes()
l get_skewness_control_inside_holes()
l set_number_of_optimization_steps_arround_holes(value,highlight=1)
l get_number_of_optimization_steps_arround_holes()
l enable_skewness_control_arround_holes()
l disable_skewness_control_arround_holes()
l get_skewness_control_arround_holes()
l set_upstream_wake_lenght(value,highlight=1)
l get_upstream_wake_lenght()
l set_downstream_wake_lenght(value,highlight=1)
l get_downstream_wake_lenght()
l set_hole_line_shape_link_to_next_hole_line_shape(value,highlight=1)
l get_hole_line_shape_link_to_next_hole_line_shape()
l set_hole_line_shape_link_to_previous_hole_line_shape(value,highlight=1)
l get_hole_line_shape_link_to_previous_hole_line_shape()
l set_preserved_layers_on_lower_side(value,highlight=1)
l get_preserved_layers_on_lower_side()
l set_preserved_layers_on_upper_side(value,highlight=1)
l get_preserved_layers_on_upper_side()
l set_intersection_tolerance(value,highlight=1)
l get_intersection_tolerance()
l select()
l delete()
Global Parameters
l reset_parametrization_up()
l reset_parametrization_down()
l set_optimization_steps(value)
l get_optimization_steps()
l set_boundary_optimization_steps()
l get_boundary_optimization_steps()
l enable_parametric_location()
l enable_XYZ_location(value)
l set_parametric_streamwise_location(value)
l get_parametric_streamwise_location()
l set_anchor_points_x_coordinate(value)
l get_anchor_points_x_coordinate()
l set_anchor_points_y_coordinate(value)
l get_anchor_points_y_coordinate()
l set_anchor_points_z_coordinate(value)
l get_anchor_points_z_coordinate()
l set_axis_x_coordinate(value)
l get_axis_x_coordinate()
l set_axis_y_coordinate(value)
l get_axis_y_coordinate()
l set_axis_z_coordinate(value)
l get_axis_z_coordinate()
l set_number_of_points_on_hole_side(value)
l get_number_of_points_on_hole_side()
Basin Hole
l set_diameter(value)
l get_diameter()
l set_number_of_points_in_bnd_layer(value)
l get_number_of_points_in_bnd_layer()
l set_parametric_azimutal_deviation(value)
l get_parametric_azimutal_deviation()
l set_width(value)
l get_width()
Penny
l set_diameter(value)
l get_diameter()
l set_number_of_points_in_bnd_layer(value)
l get_number_of_points_in_bnd_layer()
l set_parametric_azimutal_deviation(value)
l get_parametric_azimutal_deviation()
l set_rotation_angle(value)
l get_rotation_angle()
l select()
l delete()
l box()
l view_mesh(pinfinstype,boxtype,boxside,clear=1)
pinfinstype : 0, 1 for grid, 2 for solid and 3 for both
box type : 0, 1, 2 or 3
box side : 0, 1 or 2.
l viewbox(side,rep)
l hidebox()
l link_geometry(curve_names,surfaces_name)
l edit()
l stop_edit()
l generate()
l number_of_pinFins_line()
l add_pinFins_line()
l pinFins_line(i)
l select()
l delete()
l getName()
l number_of_pinFins()
l pinFin(i)
Returns an object of class PinFin.
l preview3D()
l hide3D()
l exportGeometry()
l exportDefinition()
l defineGeometry(file_name)
l set_pinfins_number(value,highlight=1)
l get_pinfins_number()
l set_circular_shape(highlight=1)
l set_rectangular_shape(highlight=1)
l set_oval_shape(highlight=1)
l set_quadrilateral_shape(highlight=1)
l get_shape(highlight=1)
Parametric Mode
l enable_parametric_pinfins_location(highlight=1)
l set_first_spanwise_parametric_location(value,highlight=1)
l get_first_spanwise_parametric_location()
l set_last_spanwise_parametric_location(value,highlight=1)
l get_last_spanwise_parametric_location()
l set_streamwise_location(value,highlight=1)
l get_streamwise_location()
XYZ Mode
l enable_xyz_pinfins_location(highlight=1)
l set_x_location(value,highlight=1)
l get_x_location()
l set_y_location(value,highlight=1)
l get_y_location()
l set_z_location(value,highlight=1)
l get_z_location()
UV Mode
l enable_UV_pinfins_location(highlight=1)
l set_U_location(value,highlight=1)
l get_U_location()
l set_V_location(value,highlight=1)
l get_V_location()
Parametric Mode
l enable_parametric_pinfins_axis(highlight=1)
l set_streamwise_angle(value,highlight=1)
l get_streamwise_angle()
l set_spanwise_angle(value,highlight=1)
l get_spanwise_angle()
l set_depth(value,highlight=1)
l get_depth()
eCircular Shape
l set_diameter(value,highlight=1)
l get_diameter()
l set_diameter2(value,highlight=1)
l get_diameter2()
Rectangular/Oval Shape
l set_width(value,highlight=1)
l get_width()
l set_heigth(value,highlight=1)
l get_heigth()
l set_orientation_angle(value,highlight=1)
l get_orientation_angle()
l set_number_of_points_in_boundary_layer(value,highlight=1)
l get_number_of_points_in_boundary_layer()
l set_number_of_points_streamwise(value,highlight=1)
l get_number_of_points_streamwise()
l set_number_of_points_spanwise(value,highlight=1)
l get_number_of_points_spanwise()
l set_number_of_points_streamwise_left(value,highlight=1)
l get_number_of_points_streamwise_left()
l set_number_of_points_streamwise_right(value,highlight=1)
l get_number_of_points_streamwise_right()
l set_number_of_points_spanwise_up(value,highlight=1)
l get_number_of_points_spanwise_up()
l set_number_of_points_spanwise_down(value,highlight=1)
l get_number_of_points_spanwise_down()
l set_number_of_optimization_steps_inside_holes(value,highlight=1)
l get_number_of_optimization_steps_inside_holes()
l enable_skewness_control_inside_holes()
l disable_skewness_control_inside_holes()
l get_skewness_control_inside_holes()
l set_number_of_optimization_steps_arround_holes(value,highlight=1)
l get_number_of_optimization_steps_arround_holes()
l enable_skewness_control_arround_holes()
l disable_skewness_control_arround_holes()
l get_skewness_control_arround_holes()
Wake Control
l set_upstream_wake_lenght(value,highlight=1)
l get_upstream_wake_lenght()
l set_downstream_wake_lenght(value,highlight=1)
l get_downstream_wake_lenght()
l set_hole_line_shape_link_to_next_hole_line_shape(value,highlight=1)
l get_hole_line_shape_link_to_next_hole_line_shape()
l set_hole_line_shape_link_to_previous_hole_line_shape(value,highlight=1)
l get_hole_line_shape_link_to_previous_hole_line_shape()
l set_preserved_layers_on_lower_side(value,highlight=1)
l get_preserved_layers_on_lower_side()
l set_preserved_layers_on_upper_side(value,highlight=1)
l get_preserved_layers_on_upper_side()
l set_intersection_tolerance(value,highlight=1)
l get_intersection_tolerance()
l select()
l delete()
l getName()
Parametric Mode
l set_first_spanwise_parametric_location(value,highlight=1)
l get_first_spanwise_parametric_location()
l set_last_spanwise_parametric_location(value,highlight=1)
l get_last_spanwise_parametric_location()
l set_streamwise_location(value,highlight=1)
l get_streamwise_location()
XYZ Mode
l set_x_location(value,highlight=1)
l get_x_location()
l set_y_location(value,highlight=1)
l get_y_location()
l set_z_location(value,highlight=1)
l get_z_location()
UV Mode
l set_U_location(value,highlight=1)
l get_U_location()
l set_V_location(value,highlight=1)
l get_V_location()
Parametric Mode
l set_streamwise_angle(value,highlight=1)
l get_streamwise_angle()
l set_spanwise_angle(value,highlight=1)
l get_spanwise_angle()
XYZ Mode
l set_x_axis(value,highlight=1)
l get_x_axis()
l set_y_axis(value,highlight=1)
l get_y_axis()
l set_z_axis(value,highlight=1)
l get_z_axis()
l set_depth(value,highlight=1)
l get_depth()
Circular Shape
l set_diameter(value,highlight=1)
l get_diameter()
l set_diameter2(value,highlight=1)
l get_diameter2()
Rectangular/Oval Shape
l set_width(value,highlight=1)
l get_width()
l set_heigth(value,highlight=1)
l get_heigth()
l set_holes_p1x(value,highlight=1)
l get_holes_p1x()
l set_holes_p2x(value,highlight=1)
l get_holes_p2x()
l set_holes_p3x(value,highlight=1)
l get_holes_p3x()
l set_holes_p4x(value,highlight=1)
l get_holes_p4x()
l set_holes_p1y(value,highlight=1)
l get_holes_p1y()
l set_holes_p2y(value,highlight=1)
l get_holes_p2y()
l set_holes_p3y(value,highlight=1)
l get_holes_p3y()
l set_holes_p4y(value,highlight=1)
l get_holes_p4y()
l set_orientation_angle(value,highlight=1)
l get_orientation_angle()
l select()
l delete()
l generate()
l generate_holes()
l set_width(value)
l get_width()
l set_number_of_spanwise_points(value)
l get_number_of_spanwise_points()
l set_number_of_optimization_steps(value)
l get_number_of_optimization_steps()
l enable_multigrid_optimization(value)
l disable_multigrid_optimization(value)
l get_multigrid_optimization_status()
l number_of_holes_lines()
l add_holes_line()
l holes_line(i)
l select()
l delete()
l setName(value)
l getName()
XYZ Mode
l set_x_location(value,highlight=1)
l get_x_location()
l set_y_location(value,highlight=1)
l get_y_location()
l set_z_location(value,highlight=1)
l get_z_location()
l set_m_location(value,highlight=1)
l get_m_location()
l set_theta_location(value,highlight=1)
l get_theta_location()
Parametric Mode
l set_streamwise_angle(value,highlight=1)
l get_streamwise_angle()
l set_spanwise_angle(value,highlight=1)
l get_spanwise_angle()
XYZ Mode
l set_x_axis(value,highlight=1)
l get_x_axis()
l set_y_axis(value,highlight=1)
l get_y_axis()
l set_z_axis(value,highlight=1)
l get_z_axis()
Circular Shape
l set_holes_diameter(value,highlight=1)
l get_holes_diameter()
Rectangular/Oval Shape
l set_holes_width(value,highlight=1)
l get_holes_width()
l set_holes_heigth(value,highlight=1)
l get_holes_heigth()
l set_holes_p1x(value,highlight=1)
l get_holes_p1x()
l set_holes_p2x(value,highlight=1)
l get_holes_p2x()
l set_holes_p3x(value,highlight=1)
l get_holes_p3x()
l set_holes_p4x(value,highlight=1)
l get_holes_p4x()
l set_holes_p1y(value,highlight=1)
l get_holes_p1y()
l set_holes_p2y(value,highlight=1)
l get_holes_p2y()
l set_holes_p3y(value,highlight=1)
l get_holes_p3y()
l set_holes_p4y(value,highlight=1)
l get_holes_p4y()
l set_orientation_angle(value,highlight=1)
l get_orientation_angle ()
l select()
l delete()
l number_of_holes()
l hole(i)
l setName(value)
l getName()
l exportGeometry()
l exportDefinition()
l defineGeometry(file_name)
Holes Number
l set_holes_number(value,highlight=1)
l get_holes_number()
Hole Shape
l set_circular_shape(highlight=1)
l set_rectangular_shape(highlight=1)
l set_oval_shape(highlight=1)
l set_quadrilateral_shape(highlight=1)
l get_shape(highlight=1)
Hole Location
Parametric Mode
l enable_parametric_holes_location(highlight=1)
l set_first_theta_location(value,highlight=1)
l get_first_theta_location(highlight=1)
l set_last_theta_location(value,highlight=1)
l get_last_theta_location(highlight=1)
l set_streamwise_location (value,highlight=1)
l get_streamwise_location(highlight=1)
XYZ Mode
l enable_xyz_holes_location(highlight=1)
l set_x_location(value,highlight=1)
l get_x_location()
l set_y_location(value,highlight=1)
MTheta Mode
l enable_mtheta_holes_location(highlight=1)
l set_m_location(value,highlight=1)
l get_m_location()
l set_theta_location(value,highlight=1)
l get_theta_location()
Hole Axis
Parametric Mode
l enable_parametric_holes_axis(highlight=1)
l set_streamwise_angle(value,highlight=1)
l get_streamwise_angle()
l set_spanwise_angle(value,highlight=1)
l get_spanwise_angle()
XYZ Mode
l enable_xyz_holes_axis(highlight=1)
l set_x_axis(value,highlight=1)
l get_x_axis()
l set_y_axis(value,highlight=1)
l get_y_axis()
l set_z_axis(value,highlight=1)
l get_z_axis()
Hole Dimension
Circular Shape
l set_holes_diameter(value,highlight=1)
l get_holes_diameter()
Hole Orientation
l set_orientation_angle(value,highlight=1)
l get_orientation_angle()
l set_number_of_points_in_boundary_layer(value,highlight=1)
l get_number_of_points_in_boundary_layer()
l set_number_of_points_streamwise(value,highlight=1)
Optimization
l set_number_of_optimization_steps_inside_holes(value,highlight=1)
l get_number_of_optimization_steps_inside_holes()
l enable_skewness_control_inside_holes()
l disable_skewness_control_inside_holes()
l get_skewness_control_inside_holes()
l set_number_of_optimization_steps_arround_holes(value,highlight=1)
l get_number_of_optimization_steps_arround_holes()
l enable_skewness_control_arround_holes()
l disable_skewness_control_arround_holes()
l get_skewness_control_arround_holesc
Wake Control
l set_upstream_wake_lenght(value,highlight=1)
l get_upstream_wake_lenght()
l set_downstream_wake_lenght(value,highlight=1)
l get_downstream_wake_lenght()
l set_hole_line_shape_link_to_next_hole_line_shape(value,highlight=1)
l get_hole_line_shape_link_to_next_hole_line_shape()
l set_hole_line_shape_link_to_previous_hole_line_shape(value,highlight=1)
l get_hole_line_shape_link_to_previous_hole_line_shape()
l set_preserved_layers_on_lower_side(value,highlight=1)
l get_preserved_layers_on_lower_side()
l set_preserved_layers_on_upper_side(value,highlight=1)
l get_preserved_layers_on_upper_side()
l set_intersection_tolerance(value,highlight=1)
l get_intersection_tolerance()