[Getfem-commits] (no subject)

[Yves Renard]

branch: devel-tetsuo-Add-mixed-methods-with-different-meshes
commit 710de081b9a2d195983659b5827743ac82bf36cf
Author: Yves Renard <address@hidden>
Date:   Mon Feb 11 16:53:28 2019 +0100

    some documentation improvements
---
 doc/sphinx/source/userdoc/interNMM.rst     | 10 +++++-----
 doc/sphinx/source/userdoc/model_object.rst | 13 +++++++------
 2 files changed, 12 insertions(+), 11 deletions(-)

diff --git a/doc/sphinx/source/userdoc/interNMM.rst 
b/doc/sphinx/source/userdoc/interNMM.rst
index f2189b6..c8db3c6 100644
--- a/doc/sphinx/source/userdoc/interNMM.rst
+++ b/doc/sphinx/source/userdoc/interNMM.rst
@@ -6,8 +6,8 @@
 
 .. _ud-internmm:
 
-Interpolation of a finite element method on non-matching meshes
-===============================================================
+Interpolation/projection of a finite element method on non-matching meshes
+==========================================================================
 
 A special finite element method is defined in
 :file:`getfem/getfem_interpolated_fem.h` which is not a real finite element
@@ -26,7 +26,7 @@ such a computation can be a heavy procedure. By default, the 
interpolated fem
 object store the interpolation data.
 
 The interpolation is made on each Gauss point of the integration methods of
-``mim``, so that you have to use these integration methods in the assembling
+``mim``, so only this integration method can be used in assembly
 procedures.
 
 For instance if you need to compute the mass matrix between two different 
finite
@@ -51,9 +51,9 @@ order.
 
 mixed methods with different meshes
 -----------------------------------
-  to be described ...
+Instead of using the previous tools (interpolated and projected fems), It is 
possible to use a finite element variable defined on an another mesh than the 
one on which an assembly is computed using the "interpolate transformation" 
tool of the weak form language (see :ref:`ud-gasm-high-transf`), the finite 
element variables will be interpolated on each Gauss point. There is no 
restriction on the dimensions of the mesh used, which means in particular that 
a two-dimensional fem variable can [...]
 
 
 mortar methods
 --------------
-  to be described ...
+ Mortar methods are supported by |gf|. The coupling term between non matching 
meshes can in particular be computed using the interpolate transformations of 
the weak form language (see :ref:`ud-gasm-high-transf`).
diff --git a/doc/sphinx/source/userdoc/model_object.rst 
b/doc/sphinx/source/userdoc/model_object.rst
index a77cadf..2eb2e8e 100644
--- a/doc/sphinx/source/userdoc/model_object.rst
+++ b/doc/sphinx/source/userdoc/model_object.rst
@@ -102,13 +102,14 @@ The main useful methods on a |mo| object are
 
 .. c:function:: add_filtered_fem_variable(name, mf, region)
 
-   Add a variable being the dofs of a finite element method ``mf`` only 
specific region.
+   Add a variable being the dofs of a finite element method ``mf`` only
+   specific to a given region.
    (The standard way to define ``mf`` in |gf| is to define in the whole 
domain.)
-   ``name`` is a string which designate the variable. ``region`` is the number 
of region.
-   This function will select the degree of freedom whose shape function is 
non-zero on
-   the given region. It is also possible to select the degrees of freedom by
-   `partial_mesh_fem`. If  |mo| object have different mesh, you can add the 
coupling
-   terms using the interpolation transformations. (See :ref:`ud-interNMM` )
+   ``name`` is a string which designate the variable. ``region`` is the region
+   number. This function will select the degree of freedom whose shape
+   function is non-zero on the given region. Internally, a ``partial_mesh_fem``
+   object will be used. The method ``mesh_fem_of_variable('name')`` allows to
+   access to the ``partial_mesh_fem`` built. 
 
 .. c:function:: add_fem_data(name, mf, niter=1)