User:Mcmor/sandbox

= NITROS Project =

The NITROS (Network for Innovative Training on ROtorcraft Safety) project is an ongoing project which began in November, 2016 composing of 12 different Early Stage Researchers (ESRs). It is funded through the Marie Skłodowska-Curie Actions (MSCA) research grant which is an Innovative Training Network (ITN) to support European Joint Doctorates (EJD). The collective aim of this specific MSCA scheme is for fostering new skills by means of excellent initial training of researchers.

The focus of NITROS is to train the next generation of talented young aerospace engineers apt in developing innovative approaches in a unique cross-disciplinary research program encompassing Control Engineering, Computational Fluid Dynamics (CFD), Modeling and Simulation, Structural Dynamics and Human perception cognition and action, to address complex solutions for rotorcraft safety. Rotorcraft accident rates remain disproportionately high in comparison with fixed-wing aircraft and the complexity of the phenomena involved in rotorcraft flight calls for the training of engineers with a genuine multidisciplinary background.

The network is composed of four different universities spread over four different countries namely: Politecnico di Milano (Italy), Delft University of Technology (Netherlands), University of Liverpool (England) and the University of Glasgow (Scotland). Whilst there are also six different international industrial partners involved in helping collaborate: Bristow Helicopters, Civil Aviation Authority, Eurocontrol, Leonardo Helicopter, National Aerospace Laboratory and the Max Plank Institute.

The NITROS project will be presented at the 44th European Rotorcraft Forum in Delft as well as the subsequent 45th and 46th European Rotorcraft Forums where the 12 different projects will be presented.

Each research project is focused on a problem that affects the safety of the current or innovative rotorcraft configurations:


 * Simulation and Prevention of Ice Formation and Shedding on Rotorcraft
 * In Service Health Monitoring for Rotorcraft Structures
 * Innovative Design for Tiltrotor Cockpit for the Reduction of Pilot Workload
 * Robust Flight Control of Rotorcraft Maneuvers Immersed in Obstactle's Turbulence
 * Rotorcraft Wake Modelling
 * Development of Phase Agression Criterion for Adverse Rotorcraft Pilot Coupling Prediction and Real-Time Detection
 * Mitigation of Airwake Hazards
 * Modelling of Brown/White-Out
 * Enhanced Helicopter Handling Qualities through Vibratory Loads Exploration
 * Revealing Adverse Rotorcraft Pilot Couplings Induced by Flight Control Systems
 * Understanding the Use of Automation in Helicopters
 * Alleviating Flight Simulator Negative Transference for Helicopter Operations

Reference
= ICEM CFD = ANSYS ICEM CFD is a popular proprietary software package which provides advanced geometry and mesh generation and mesh diagnostics and repair functions useful for in-depth analysis. Its design is centered around engineering applications with a specific focus on computational fluid dynamics and structural analysis.

General Meshing Overview




ANSYS ICEM CFD's offers mesh generation with the capacity to compute meshes with various different structures depending on the users requirements. It is a powerful and highly manipulative software which allows the user to generate grids of high resolution. This is a requirement as mesh generation is an inherently geometry dependent problem meaning there is no singular meshing method which can be used for every problem. ICEM CFD allows the following different types of grid structures to be created:


 * Multi-block structured meshes
 * Unstructured meshes
 * Hybrid meshes

A simplified overview of the meshing methodology provides an indication of how to begin the meshing procedure with the different stages shown.

User Interface
ICEM CFD provides a user interface which includes several components to make mesh generation intuitive and easy to use once its full capabilities are understood. The user interface contains a complete environment to create, modify and manage computational grids:


 * Main Menu: Create/Open/Save/Close projects, Geometry/Mesh/Blocking options and parameters, Import/Export Model/Geometry/Mesh


 * Utilities for visualisation purposes: View/Zoom/Refresh screen, Undo/Redo commands, Wireframe/Solid Simple Display
 * A hierarchical Display Control Tree: Model,Geometry/Mesh/Blocking/Parts
 * Function Tabs to modify the mesh: Geometry/Mesh/Blocking, Edit Mesh, Properties/Constraints/Loads/FEA solver options, Output Mesh
 * Selection Toolbar
 * Data Entry Zone
 * Message Window
 * Histogram Window

The user interface window can also be personalised in the settings menu.

Project Structure
It is possible to either create or open a pre-existing project. Every project will contain a series of file types dependent upon the mesh type and structure. The series of file types contained within the working directory are:


 * Project Settings (*.prj): This file consists of the necessary information to manage the data files associated within the project itself.
 * Tetin (*.tin): This file consists of the geometry components, material bodies, part associations and global mesh sizes.
 * Mesh (*.uns): This file consists of the line, shell, and volume mesh elements. The shell mesh elements contain triangular and quadrilateral elements whilst the volume mesh elements contain hexahedra, pyramids and prisms.
 * Blocking (*.blk): This file consists of the framework used to create a structured mesh with the details of each individual block.
 * Attributes (*.atr)(*.fbc): This file consists of the mesh dependent data specified during any edge, surface or vertices association as well as data for parts, element properties, loads and constraints of the mesh.
 * Parameters (*.par): This file consists of the mesh independent data such as material properties, local coordinates and run parameters. This data is then passed onto the attributes file.
 * Cartesian (*.crt): This file consists of the information regarding the Cartesian grid. This is hence only ever apparent in Cartesian grids.
 * Journal (*.jrf): This file consists of the record of the operations performed.
 * Replay (*.rpl): This file consists of the replay script.



Geometry Modelling
ICEM CFD allows for its geometry to either be made using its own geometry topology package or to import geometry via external CAD software. For simple geometries the former tends to be used and for more complex geometries the latter is often used. Regardless of this, the geometry should be checked using the geometry analysis to ensure the model contains a closed volume, meaning there are no holes or gaps within the geometry, so that further down the line, no negative volume elements are present. Negative volume elements are not permitted in external solvers. These maybe present due to differences in geometrical and meshing tolerances.There is hence an emphasis in ICEM CFD to create a mesh that has a 'water-tight' geometry. It means if there is a source of water inside a region, the water should be contained and not leak out of the BODY.

Apart from the regular points, curves, surface creation and editing tools, ICEM CFD especially has the capability to do BUILD TOPOLOGY which removes unwanted surfaces and then you can view if there are any 'holes' in the region of interest for meshing. Existence of holes would mean that the algorithm which generates the mesh would cause the mesh to 'leak out' of the domain. Holes are typically identified through the colour of the curves. The following is the colour coding in ICEM CFD, after the BUILD TOPOLOGY option has been implemented:


 * YELLOW: curve attached to a single surface
 * RED: curve shared by two surface
 * BLUE: curve shared by more than two surface.
 * Green: curve not attached to any surface

An analysis post building the topology is then required, whereby if it is clear a curve is supposed to share two surfaces yet is being displayed as yellow, a hole exists and it is likely there will be meshing problems.

Geometrical entities which may include points, curves and surfaces must also be associated to a given part. Each part can then be controlled for meshing, visualisation or various other purposes and is stored within the aforementioned tetin file.

Structured vs. Unstructured Background
There are often some misunderstandings regarding structured/unstructured mesh, meshing algorithm, and solver. A mesh may look like a structured mesh but may or may not have been created using a structured algorithm-based tool. For example, GAMBIT is an unstructured meshing tool. Therefore, even if it creates a mesh that looks like a structured (single or multi-block) mesh through pain-staking efforts in geometry decomposition, the algorithm employed was still an unstructured one. On top of it, most of the popular CFD tools like: ANSYS FLUENT, ANSYS CFX, Star CCM+, OpenFOAM, AxSTREAM CFD, etc. are unstructured solvers. Unstructured solvers can only work on an unstructured mesh even if provided with a structured-looking mesh created using structured/unstructured algorithm based meshing tools. ANSYS ICEM CFD can generate both structured and unstructured meshes using structured or unstructured algorithms which can be given as inputs to structured as well as unstructured solvers, respectively.

The classification of structured or unstructured grid is only by the book-keeping of the grid. In structured grid representation we use indices i, j, k to locate a node. And we know if a grid line is represented by i=2, the next grid line is i=3 and the next is i=4 and so on. But in unstructured notation we use node number, element number etc. Element 5 may be adjacent to element 4 and element 6 need not be adjacent to element 4 or 5. It can be anywhere in the domain. The same mesh represented by i, j, k indices can be written with node number, element number etc. Now the former structured mesh is written in unstructured mesh format. But a tetrahedral unstructured mesh can not be represented by indices like i, j, k.

examples of the two types inserted here.

Unstructured Meshing
The unstructured mesh generation creates tetrahedral volume meshes based on the users created or imported geometry. The unstructured mesh generation has the capability of using different meshing algorithms for meshing surfaces and volumes as well as incorporating a power smoothing algorithm to locally adapt the mesh for improved mesh quality.

The unstructured mesh generation procedure will now be considered:


 * 1) Create/Import geometry
 * 2) Repair geometry ensuring a closed volume
 * 3) Determine global meshing parameter
 * 4) Specify part mesh setup
 * 5) Specify curves and surface mesh size
 * 6) Compute mesh

The mesh can then later be further refined by adding prism layers, regional refinement, curvature/proximity based refinement, etc. without the need to recompute the entire mesh again by simply computing the mesh based on the already existing mesh. This permits iteratively improving and updating the mesh for high quality mesh resolution.

When using the unstructured meshing method the most important consideration is to determine which meshing algorithm is most appropriate for the problem. ICEM supports four different meshing algorithms for generating unstructured meshes: Robust (Octree), Quick (Delaunay), Smooth (Advancing Front) and Fluent Meshing. They are listed as Tetra/Mixed as each method includes the possibility of adding a boundary layer of prism elements to the tetra volume mesh. As previously mentioned, although containing prism elements the mesh is still considered unstructured due to the orientation of the the indices.

The Robust (Octree) method generates its volume mesh first then later generates the surface mesh. This uses a patch-independent approach meaning an existing surface is not required as one is generated during the Octree process.

The Quick (Delaunay) method generates a surface mesh then the volume mesh. This process hence uses a patch-dependent approach as it requires a closed surface when using the Delaunay Tetra algorithm. If the geometry does not have a closed volume this meshing method will automatically create the surface using the global meshing parameters.

The Smooth (Advancing Front) method generates a surface mesh then the volume mesh similar to that of the Quick (Delaunay) method. The Smooth (Advancing Front) method however produces a smoother transition from surface elements to volume elements. This will hence also require a relatively high level of mesh quality to mesh without failures. The surface mesh should be one enclosed volume with no abrupt changes in element size and no single edge, multiple edges, non-manifolded vertices, overlapping elements or duplicate elements.

The Fluent Meshing method generates its mesh in a batch process. In case no closed volume surface is present before the batch process begins it will create a surface mesh then start the Fluent batch meshing method. It also allows for creating the volume mesh from the surface on a part-by-part basis. Furthermore, optional prism layers may be created using either its pre or post inflation prism creating. Pre inflation prism generation first creates the boundary layer from the existing surface mesh then later generates the volume mesh. Post inflation prism generation first creates the volume mesh then replaces the tetrahedral volume elements at the surface with prism elements. If this mesh is highly skewed at the surface the post inflation method will fail to create prism elements. Fluent Meshing also also for control of the expansion ration of elements away from the surface which directly affects the size of the volume mesh.

Structured Meshing
With structured meshing, the basic steps necessary to generate a structured mesh are the same regardless of the model complexity. Initialising the block creates one block which surrounds the entire geometry. This block is then modified into a series of block topologies which embody the shape of the model geometry. This is known as blocking the geometry. These modifications can be done through splitting the block into further sub-blocks, merging sub-blocks together into whole blocks and Ogrid operations which splits a block into a circular "O"-type shape. Splitting a block can be applied over entire blocks or just applied to individual faces or edges. Merging can also merge faces or edges of blocks as well as whole blocks. Creating Ogrids is a powerful technique used to achieve O-type block shapes localised round objects which would not be possible without this technique. Importantly, Ogrids can not be later be merge together as the index direction is not the same around the O-type blocks. O-type block structures are particularly useful when considering very complex geometries. Each block then contains both geometric data and block topological data. The geometrical data contains: Points with x, y and z positions, curves and surfaces. The hexahedral block topological data contains: At least eight vertices per hexaheron, which are the corner points of blocks. Four edges per face and twelve per block. Six faces per block. Each block volume is hence comprised of vertices, edges and faces.

The structured mesh generation procedure will now be considered:


 * 1) Create/Import geometry.
 * 2) Initialise blocking.
 * 3) Generate block structure using the split, merge, Ogrid definition.
 * 4) Associate vertices, edges and faces to points, curves and surfaces.
 * 5) Check block structure quality to ensure the block model meets specified quality threshold.
 * 6) Determine edge meshing parameters.
 * 7) Generate mesh.
 * 8) Check the cell quality of the mesh once its generated.
 * 9) Write output files to desired solver

In case of any problems arise, the blocking structure can be saved at any time and previous block topologies can be returned to.

Without associating vertices, edges and faces is not a problem, in that it will not directly cause the mesh generation solver to fail, however it does mean that the blocks will not follow any of the predefined user geometry.

The following are the different multi-block strategies available which can be implemented using ANSYS ICEM CFD.


 * O-grid
 * C-grid
 * H-grid

These strategies can also be combined for hybrid block designs, for instance C-H-grid types.