From: ageay Date: Tue, 3 Nov 2009 09:15:20 +0000 (+0000) Subject: Dealing polyhedra for 3D P0P0 non conservative interpolation. X-Git-Tag: V5_1_main_FINAL~295 X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=79349aab5d18b2e43884ed1eb292119f38f767ab;p=tools%2Fmedcoupling.git Dealing polyhedra for 3D P0P0 non conservative interpolation. --- diff --git a/doc/doxygen/remapping.dox b/doc/doxygen/remapping.dox index 76d413b8a..9c0d229f1 100755 --- a/doc/doxygen/remapping.dox +++ b/doc/doxygen/remapping.dox @@ -26,13 +26,19 @@ meshes with mixed triangular and quadrangular elements. - Geometric2D: Any type of 2D cells (linear, quadratic, convex-polygons, non-convex polygons) is supported by this algorithm. Due to its flexibility this algo is slower than the other. +- PointLocator: This is \b non \b conservative interpolator. For P0P0, it +locate the barycenter of target cell in the source cells. For P1P0, it +locates barycenter of target cell and compute barycentric coordinates +in source cell (Works only with trangle). For P0P1 locate target nodes +in source cells. For P1P1 compute for each target node its barycentric +coordinates in source cell. The following options are available for the 2D intersection computations: * * * + * Triangle, Convex, \ref interpkernelGeo2D "Geometric2D", PointLocator * * *
OptionDescription Admitted valuesDefault
Intersection_typeSpecifies the algorithm to be * used in the computation of the cell-cell intersections - * Triangle, Convex, \ref interpkernelGeo2D "Geometric2D" Triangle
Triangle
Precision Accuracy of the computations is precision times the characteristic size of the meshes positive real numbers 1.0E-12
PrintLevel Level of verboseness during the computations 0, 1, 2, 3 0
@@ -72,11 +78,30 @@ more details. \subsection InterpKer3DIntFeatureP0P0 P0->P0 intersectors features. -When remapping three dimensional fields, volumes of intersection between polyhedral cells are to be computed. We use the method of Jeffrey Grandy, 1999 (see \ref references) to intersect arbitrary polyhedra. The basic algorithm computes the intersection of a tetrahedron with an arbitrary (possibly non convex) polyhedron. Using splitting techniques, it is possible to transform the problem of computing the intersection between two general polyhedra into several tetrahedron-polyhedron intersection calculations. For the moment it is only possible to remap fields on meshes having mixed tetrahedral and hexahedral cells. When using a mesh with hexahedral cells, several splitting techniques may be employed depending mainly on wether the faces are planar or not. The following options are available for the splitting: +When remapping three dimensional fields, volumes of intersection +between polyhedral cells are to be computed. +Two methods are available : +- Triangle : the method of Jeffrey Grandy, 1999 (see \ref references) +to intersect arbitrary polyhedra. The basic algorithm computes the +intersection of a tetrahedron with an arbitrary (possibly non convex) +polyhedron. Using splitting techniques, it is possible to transform +the problem of computing the intersection between two general +polyhedra into several tetrahedron-polyhedron intersection +calculations. For the moment it is only possible to remap fields on +meshes having mixed tetrahedral and hexahedral cells. When using a +mesh with hexahedral cells, several splitting techniques may be +employed depending mainly on wether the faces are planar or not. The +following options are available for the splitting: +- PointLocator : \b non \b conservative intersector based on the same +principle than described in 2D. * * - * + * + * * *
OptionDescription Admitted valuesDefault
SplittingPolicy Way in which the hexahedra are split into tetrahedra PLANAR_FACE_5, PLANAR_FACE_6, GENERAL_24, GENERAL_48 GENERAL_48
Intersection_typeSpecifies the algorithm to be + * used in the computation of the cell-cell intersections + * Triangle, PointLocator Triangle
SplittingPolicy Way in which the hexahedra are + * split into tetrahedra (only if Intersection_type==Triangle) PLANAR_FACE_5, PLANAR_FACE_6, GENERAL_24, GENERAL_48 GENERAL_48
PrintLevel Level of verboseness during the computations 1, 2, 3, 4, 5 0