From: ageay Date: Thu, 11 Mar 2010 16:23:52 +0000 (+0000) Subject: *** empty log message *** X-Git-Tag: V5_1_main_FINAL~154 X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=6cae34ad9a9b7bfe2526843c70f0f1681d93edf3;p=tools%2Fmedcoupling.git *** empty log message *** --- diff --git a/doc/doxygen/Doxyfile_med_user.in b/doc/doxygen/Doxyfile_med_user.in index 5e354293d..9e5f39f97 100644 --- a/doc/doxygen/Doxyfile_med_user.in +++ b/doc/doxygen/Doxyfile_med_user.in @@ -111,6 +111,7 @@ FILE_PATTERNS = MEDMEM_Mesh.* \ MEDCouplingUMeshDesc.* \ MEDCouplingPointSet.* \ MEDCouplingCMesh.* \ + MEDCouplingExtrudedMesh.* \ MEDCouplingFieldDouble.* \ MEDCouplingFieldDiscretization.* \ MEDCouplingTimeDiscretization.* \ diff --git a/doc/doxygen/medcoupling.dox b/doc/doxygen/medcoupling.dox index 6096857b2..cd5fdb3d1 100644 --- a/doc/doxygen/medcoupling.dox +++ b/doc/doxygen/medcoupling.dox @@ -317,7 +317,18 @@ type, only n arrays are needed. In this type of mesh space dimension \b and mesh dimension are equals and the value is n. The n arrays will have only one component and the values contained in these arrays will be ascendantly sorted. -The class that incarnate this concept in MEDCoupling is : \ref ParaMEDMEM::MEDCouplingCMesh. +The class that incarnates this concept in MEDCoupling is : \ref ParaMEDMEM::MEDCouplingCMesh. + +\section MEDCouplingExtrudedMeshes Extruded Mesh + +An extruded mesh is a mesh also called 2.5 D. It a convolution of 2D +unstructured mesh with 1D unstructured mesh. The problem is that this +type of mesh is not managed by any file format that's why to build an +instance of this mesh you need 3D unstructured mesh and a 2D +unstructured mesh lying on the same coordinates. The advantage of this +structure is that the interpolation time is optimized. + +The class that incarnates this concept in MEDCoupling is : \ref ParaMEDMEM::MEDCouplingExtrudedMesh. */ /*!