Metafor

ULiege - Aerospace & Mechanical Engineering

User Tools

Site Tools

You are here: metafor.ltas.ulg.ac.be » doc » Documentation » general » Glossary
Trace:
doc:user:general:glossaire

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
doc:user:general:glossaire [2017/10/25 10:44] – bomandoc:user:general:glossaire [2017/10/25 11:51] (current) – boman
Line 12: Line 12:
 ==== Abaqus ==== ==== Abaqus ====
  
-{{ doc:user:abaqus-6-6.jpg?100|doc:user:abaqus-6-6.jpg}} 
 Commercial software suite for finite element analysis, usually considered as the reference in nonlinear mechanics. [[#Metafor]] deals with similar mechanical problems as [[wp>ABAQUS]]. Commercial software suite for finite element analysis, usually considered as the reference in nonlinear mechanics. [[#Metafor]] deals with similar mechanical problems as [[wp>ABAQUS]].
  
Line 38: Line 37:
 ==== Battery ==== ==== Battery ====
  
-Also called the "test battery". The "battery" is actually a test suite made of all the input files that are checked for each new version of [[#Metafor]].+Also called the "test battery". It is actually a **test suite** made of more than 2000 input files that are checked for each new version of [[#Metafor]]. It is also an interesting source of examples for people who want to learn how to use Metafor. The main folder of the battery is ''apps''.
  
 ==== Bfac ==== ==== Bfac ====
Line 53: Line 52:
 {{ doc:user:bjarne-stroustrup.jpg?80|doc:user:bjarne-stroustrup.jpg}} {{ doc:user:bjarne-stroustrup.jpg?80|doc:user:bjarne-stroustrup.jpg}}
 [[#Object-oriented]] programming language used to develop [[#Metafor]]. See also [[wp>C++]]. [[#Object-oriented]] programming language used to develop [[#Metafor]]. See also [[wp>C++]].
- 
-==== CAD ==== 
-{{ doc:user:modell-cad.jpg?200|doc:user:modell-cad.jpg}} 
-[[wp>Computer-aided_design|Computer Aided Design]]. By extension, the CAD of a test case is its geometry. 
  
 ==== Contact ==== ==== Contact ====
Line 64: Line 59:
 ==== Contact Matrices ==== ==== Contact Matrices ====
  
-Also called "contact tools" in Metal Forming. A contact matrix is a perfectly rigid geometric object (a cylinder, a plane, ...) which can come into contact with a mesh. For instance, a drawing punch may be modeled by a contact matrix.+Also called "contact tools" in metal forming. A contact matrix is a perfectly rigid geometric object (a cylinder, a plane, ...) which can come into contact with a mesh. For instance, a drawing punch or a blankholder may be modeled by a contact matrix.
  
 ==== Curves ==== ==== Curves ====
Line 97: Line 92:
 Finite Element. See also [[Wp>Finite_element]]. Finite Element. See also [[Wp>Finite_element]].
  
-In [[#Metafor]], elements are objects that compute forces and send them back to the integration algorithm. +In [[#Metafor]], elements are objects that compute forces and send them back to the time integration algorithm. 
  
 ==== FEM ==== ==== FEM ====
Line 105: Line 100:
 ==== Fortran ==== ==== Fortran ====
  
-Obsolete language still used by the elderly. +Obsolete programming language still used by many commercial finite element codes.
- +
-==== Franglais ==== +
- +
-Langue utilisée entre autres par [[#Metafor]] (voir [[#BFac]] par exemple) malgré nos efforts pour l'éviter.+
  
 ==== FV ==== ==== FV ====
  
 Finite Volume. Alternative discretization technique, in opposition with Finite Element. Finite Volumes are used to model convection with the [[#ALE]] formulation. Finite Volume. Alternative discretization technique, in opposition with Finite Element. Finite Volumes are used to model convection with the [[#ALE]] formulation.
- 
- 
----- 
- 
- 
-===== G ===== 
- 
- 
-==== GPL ==== 
- 
-[[wp>GNU Public License]] : most widely used free software license, see [[http://www.gnu.org/copyleft/gpl.html|site GNU]]. [[#Metafor]] license is unfortunately not GPL. 
- 
  
  
Line 140: Line 119:
 ==== Interaction ==== ==== Interaction ====
  
-At first, an interaction was the object managing the boundary condition [[#fe|éléments]] on the surface of a mesh (contact, pressure). Nowadays, this concept has been extended to the generation of any [[#fe|finite element]], even [[#Volume Element]].+At first, an interaction was the object managing the boundary condition [[#fe|elements]] on the surface of a mesh (contact, pressure). Nowadays, this concept has been extended to the generation of any [[#fe|finite element]], even [[#Volume Element]].
  
 ==== Interpreter ==== ==== Interpreter ====
Line 148: Line 127:
 ==== Iterations ==== ==== Iterations ====
  
-On its own, iteration means mechanical iteration of the [[#Newton-Raphson]] algorithm, used at each time step to converge to the right solution.+On its own, iteration means mechanical iteration of the [[#Newton-Raphson]] algorithm, used at each time step to converge to an equilibrated solution.
  
  
Line 158: Line 137:
 ==== Jacobian ==== ==== Jacobian ====
  
-The jacobian of a [[#fe|element]] characterizes the factor by which the volume of this element expands or shrinks between a given configuration and the reference one. It is always positive, unless the element orientation was reversed, in which case the computation cannot continue further. +The jacobian of a [[#fe|element]] characterizes the factor by which the volume of this element expands or shrinks between a given configuration and the reference one. It is always positive, unless the element orientation was inverted or distorted, in which case the computation cannot continue further.
- +
- +
----- +
- +
- +
-===== L ===== +
- +
-==== LGPL ==== +
- +
-License derived from [[#GPL]] (Lesser GPL), usually used for libraries, allowing the developer to use LGPL without having to make its code GPL. Consequently, a commercial software may use LGPL libraries. See [[http://www.gnu.org/copyleft/lgpl.html|site GNU]]. For example, [[#Metafor]] uses [[http://libnurbs.sourceforge.net/|Nurbs++]], which is LGPL.+
  
  
Line 178: Line 147:
 ==== Machine ==== ==== Machine ====
  
-Dans le contexte de ce site, une machine n'est pas une perceuse ni un une scie électrique mais plutôt un PC ou, à la rigueur, la machine à café.+In the context of this website, a "machine" is neither a power saw nor a pneumatic drill but rather a PC or sometimes a coffee machine.
  
  
 ==== Material ==== ==== Material ====
  
-A material defines the evolution of stresses with respect to strains. By extension, contact material is the name used when talking about friction laws.+A material is the implementation of a constitutive law which defines the evolution of stresses with respect to strains. By extension, a contact material is the name used when talking about friction laws.
  
 ==== Memory leak ==== ==== Memory leak ====
  
 Quite often seen when programming with an [[#object-oriented]] language. It is due to allocated memory which is never freed. So solve this, destructors can be programmed or more RAM bought. Quite often seen when programming with an [[#object-oriented]] language. It is due to allocated memory which is never freed. So solve this, destructors can be programmed or more RAM bought.
- 
-==== Mesh ==== 
- 
-In [[#Metafor]], the mesh geometry is simply called mesh, in opposition with the user geometry, which is the one encoded by the user in its [[#data set]]. 
  
 ==== Mesh element ==== ==== Mesh element ====
  
-In [[#Metafor]], a mesh element is the geometric part of a [[#fe|finite element]]. A mesh element can be quadrangular, triangular, ... Mesh elements are created by meshers. The user applies finite elements on mesh elements through [[#interaction|interactions]].+In [[#Metafor]], a mesh element is the geometric part of a [[#fe|finite element]]. A mesh element can be quadrangular, triangular, ... Mesh elements are created by meshers. The user creates finite elements on mesh elements through [[#interaction|interactions]].
  
 ==== Metafor ==== ==== Metafor ====
  
-Thermo-mechanical [[#fe|Finite Element]] software developed in the LTAS-MN2L, taking large strains of solids into account. Initially started by J.-P. Ponthot, Metafor has grown and now gathers the contributions from all scientists in the laboratory. it is also used on a commercial way by [[http://www.gdtech.net/|GDTech]].+Thermo-mechanical [[#fe|Finite Element]] software developed in the LTAS-MN2L, taking large strains of solids into account. Initially started by J.-P. Ponthot, Metafor has become bigger and bigger and now gathers the contributions from all researchers in the laboratory. It is also used on a commercial way by [[http://www.gdtech.eu/|GDTech]], [[http://www.crmgroup.be/|CRM]] and [[https://www.safran-aero-boosters.com/fr|Safran Aero Boosters]].
  
 ==== Module ==== ==== Module ====
Line 208: Line 173:
 ==== Multiphysics ==== ==== Multiphysics ====
  
-Which can manage more than one field of unknown. For example, mechanical unknowns (''x'', ''y'', ''z''), temperature field ''T'', electric and magnetic fields...+Which can manage more than one field of unknown. For example, mechanical unknowns (''x'', ''y'', ''z''), temperature field ''T'', electric and magnetic fields, ...
 In [[#Metafor]], only mechanical and thermal fields are considered. In [[#Metafor]], only mechanical and thermal fields are considered.
  
Line 219: Line 184:
 ==== Newton-Raphson ==== ==== Newton-Raphson ====
  
-Iterative algorithm which can solve a system of nonlinear equations. In [[#Metafor]], with an implicit integration scheme, Newton's equation is solved at each time step by Newton-Raphson algorithm.+Iterative algorithm which can solve a system of nonlinear equations. In [[#Metafor]], with an implicit time integration scheme, The balance of forces is solved at each time step by a Newton-Raphson algorithm.
  
  
Line 230: Line 195:
 ==== Object-Oriented ==== ==== Object-Oriented ====
  
-Programming method which consists in dividing concepts in classes, to which data and functions to process this data are associated. It is possible to program this way with every language, but it is easier with some. [[#C++]] was used in [[#Metafor]], and [[#Python]] is also object-oriented.+Programming method which consists in dividing concepts in objects. [[#C++]]  and [[#Python]] are both object-oriented languages.
  
 ==== oo_meta ==== ==== oo_meta ====
  
-Old name of the [[#C++]] version of [[#Metafor]], when one was certain the conversion from [[#Fortran]] was successful.+Old name of the [[#C++]] version of [[#Metafor]], when the translation from [[#Fortran]] was not yet fully performed.
  
 ==== Oofelie ==== ==== Oofelie ====
doc/user/general/glossaire.1508921058.txt.gz · Last modified: 2017/10/25 10:44 by boman
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki