[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Getfem-commits] [getfem-commits] branch fixmisspell updated: :hammer_an
From: |
Tetsuo Koyama |
Subject: |
[Getfem-commits] [getfem-commits] branch fixmisspell updated: :hammer_and_wrench: typo and sample code |
Date: |
Sat, 11 Jan 2020 01:14:16 -0500 |
This is an automated email from the git hooks/post-receive script.
tkoyama010 pushed a commit to branch fixmisspell
in repository getfem.
The following commit(s) were added to refs/heads/fixmisspell by this push:
new 02517ed :hammer_and_wrench: typo and sample code
02517ed is described below
commit 02517edcc4827d3639ed1223c8bfa73ae0755378
Author: Tetsuo Koyama <address@hidden>
AuthorDate: Sat Jan 11 15:09:51 2020 +0900
:hammer_and_wrench: typo and sample code
---
doc/sphinx/source/documenting/markup.rst | 2 +-
doc/sphinx/source/glossary.rst | 2 +-
doc/sphinx/source/gmm/denseqr.rst | 2 +-
doc/sphinx/source/license.rst | 2 +-
doc/sphinx/source/lists.rst | 2 +-
doc/sphinx/source/matlab/examples.rst | 2 +-
doc/sphinx/source/matlab/mlabgf.rst | 2 +-
doc/sphinx/source/matlab/pre.rst | 2 +-
doc/sphinx/source/python/code_samples/demo_tripod_alt.py | 4 ++--
doc/sphinx/source/python/examples.rst | 2 +-
doc/sphinx/source/python/pre.rst | 2 +-
doc/sphinx/source/python/pygf.rst | 2 +-
doc/sphinx/source/scilab/intro.rst | 2 +-
doc/sphinx/source/scilab/scilabgf.rst | 2 +-
doc/sphinx/source/tutorial/wheel.rst | 1 -
doc/sphinx/source/userdoc/gasm_high.rst | 2 +-
doc/sphinx/source/userdoc/model_continuation.rst | 2 +-
doc/sphinx/source/userdoc/model_dirichlet.rst | 2 +-
18 files changed, 18 insertions(+), 19 deletions(-)
diff --git a/doc/sphinx/source/documenting/markup.rst
b/doc/sphinx/source/documenting/markup.rst
index 4fb2f2c..df44530 100644
--- a/doc/sphinx/source/documenting/markup.rst
+++ b/doc/sphinx/source/documenting/markup.rst
@@ -460,7 +460,7 @@ in a different style:
The name of an RFC 822-style mail header. This markup does not imply that
the header is being used in an email message, but can be used to refer to
any
- header of the same "style." This is also used for headers defined by the
+ header of the same "style". This is also used for headers defined by the
various MIME specifications. The header name should be entered in the same
way it would normally be found in practice, with the camel-casing
conventions
being preferred where there is more than one common usage. For example:
diff --git a/doc/sphinx/source/glossary.rst b/doc/sphinx/source/glossary.rst
index 0a1ad68..76174a0 100644
--- a/doc/sphinx/source/glossary.rst
+++ b/doc/sphinx/source/glossary.rst
@@ -28,7 +28,7 @@ Glossary
Element
An element is a small piece of a domain with a special shape (a segment,
- a triangle, a quadrilateron, an tetrahedron, a hexahedron or a prism
+ a triangle, a quadrilateron, an tetrahedron, a hexahedron or a prism)
for dimensions less or equal to three. A mesh is the union of
non intersecting elements.
diff --git a/doc/sphinx/source/gmm/denseqr.rst
b/doc/sphinx/source/gmm/denseqr.rst
index fa7538a..7708694 100644
--- a/doc/sphinx/source/gmm/denseqr.rst
+++ b/doc/sphinx/source/gmm/denseqr.rst
@@ -33,7 +33,7 @@ The following procedures are available in the file
``gmm/gmm\_dense\_qr.h`` for
-`Remark`: The computation of eigenvectors for non hermitian matrices is not
yet implemented. You can use for the moment the functions
``geev_interface_left`` and ``geev_interface_right`` from the LAPACK interface
(see ``gmm/gmm_lapack_interface.h``. These LAPACK functions compute right and
left eigenvectors.
+`Remark`: The computation of eigenvectors for non hermitian matrices is not
yet implemented. You can use for the moment the functions
``geev_interface_left`` and ``geev_interface_right`` from the LAPACK interface
(see ``gmm/gmm_lapack_interface.h``). These LAPACK functions compute right and
left eigenvectors.
The following function defined in the file ``gmm/gmm\_condition\_number.h``::
diff --git a/doc/sphinx/source/license.rst b/doc/sphinx/source/license.rst
index 91affb1..f764a5c 100644
--- a/doc/sphinx/source/license.rst
+++ b/doc/sphinx/source/license.rst
@@ -8,7 +8,7 @@
History and License
*******************
-GetFEM was born during the PhD thesis of Yves Renard (1994-1998, the first
files dating from 1995). The fondamental bases of GetFEM (assembly in any
dimension, separation of geometric transformations, finite element methods and
cubature methods) date from 1999. However, GetFEM did not take the size it is
now without the contributions of Julien Pommier since 2001. His major
contributions are generic assembly, Matlab and Python interfaces and the
graphical postprocessing (including nice Ma [...]
+GetFEM was born during the PhD thesis of Yves Renard (1994-1998, the first
files dating from 1995). The fundamental bases of GetFEM (assembly in any
dimension, separation of geometric transformations, finite element methods and
cubature methods) date from 1999. However, GetFEM did not take the size it is
now without the contributions of Julien Pommier since 2001. His major
contributions are generic assembly, Matlab and Python interfaces and the
graphical postprocessing (including nice Ma [...]
diff --git a/doc/sphinx/source/lists.rst b/doc/sphinx/source/lists.rst
index da4edc3..62b51e5 100644
--- a/doc/sphinx/source/lists.rst
+++ b/doc/sphinx/source/lists.rst
@@ -12,7 +12,7 @@ GetFEM++ is maintened on the `Savannah
<http://Savannah.gnu.org>`_ collaborative
The mailing lists of GetFEM++ are listed on the page `getfem mailing lists
<https://savannah.nongnu.org/mail/?group=getfem>`_
-The main mainling list is the `user one
<https://lists.nongnu.org/mailman/listinfo/getfem-users>`_. All kind of
problems or questions about using, install or improve GetFEM++ can be posted
there. Don't forget to register to the list before to post a message.
+The main mailing list is the `user one
<https://lists.nongnu.org/mailman/listinfo/getfem-users>`_. All kind of
problems or questions about using, install or improve GetFEM++ can be posted
there. Don't forget to register to the list before to post a message.
If you make contributions to Getfem, you should register to the
`getfem-commits mailing list
<https://lists.nongnu.org/mailman/listinfo/getfem-commits>`_.
diff --git a/doc/sphinx/source/matlab/examples.rst
b/doc/sphinx/source/matlab/examples.rst
index 4a045c4..d6582ed 100644
--- a/doc/sphinx/source/matlab/examples.rst
+++ b/doc/sphinx/source/matlab/examples.rst
@@ -20,7 +20,7 @@ with the Dirichlet condition :math:`u = g(x)` on the domain
boundary. You can fi
the **m-file** of this example under the name **demo_step_by_step.m** in the
directory ``interface/tests/matlab/`` of the |gf| distribution.
-The first step is to **create a mesh**. It is possible to create simple
structured meshes or unstructured meshes for simple geometries (see
``gf_mesh('generate', mesher_object mo, scalar h))``) or to rely on an external
mesher (see ``gf_mesh('import', string
+The first step is to **create a mesh**. It is possible to create simple
structured meshes or unstructured meshes for simple geometries (see
``gf_mesh('generate', mesher_object mo, scalar h)``) or to rely on an external
mesher (see ``gf_mesh('import', string
FORMAT, string FILENAME))``). For this example, we
just consider a regular **cartesian mesh** whose nodes are
:math:`\{x_{i=0\ldots10,j=0..10}=(i/10,j/10)\}`::
diff --git a/doc/sphinx/source/matlab/mlabgf.rst
b/doc/sphinx/source/matlab/mlabgf.rst
index 7fa6036..98b8706 100644
--- a/doc/sphinx/source/matlab/mlabgf.rst
+++ b/doc/sphinx/source/matlab/mlabgf.rst
@@ -100,7 +100,7 @@ important objects.
* :envvar:`gfCvStruct` : stores formal information convex structures (nb. of
points,
nb. of faces which are themselves convex structures).
* :envvar:`gfMeshFem` : object linked to a mesh, where each convex has been
assigned
- a FEM. Created with ``gf_mesh_fem``.
+ an FEM. Created with ``gf_mesh_fem``.
* :envvar:`gfMeshImM` : object linked to a mesh, where each convex has been
assigned
an integration method. Created with ``gf_mesh_im``.
* :envvar:`gfMeshSlice` : object linked to a mesh, very similar to a
diff --git a/doc/sphinx/source/matlab/pre.rst b/doc/sphinx/source/matlab/pre.rst
index 6474ce9..5303ddf 100644
--- a/doc/sphinx/source/matlab/pre.rst
+++ b/doc/sphinx/source/matlab/pre.rst
@@ -78,7 +78,7 @@ PDEs involve various coefficients, for example:
\nabla\cdot(\lambda(x)\nabla u) = f(x).
-Hence one has to define a FEM for the main unknown :math:`u`, but also for the
+Hence one has to define an FEM for the main unknown :math:`u`, but also for the
data :math:`\lambda(x)` and :math:`f(x)` if they are not constant. In order to
interpolate easily these coefficients in their finite element space, one often
choose a Lagrangian FEM.
diff --git a/doc/sphinx/source/python/code_samples/demo_tripod_alt.py
b/doc/sphinx/source/python/code_samples/demo_tripod_alt.py
index 6abae18..116df5a 100644
--- a/doc/sphinx/source/python/code_samples/demo_tripod_alt.py
+++ b/doc/sphinx/source/python/code_samples/demo_tripod_alt.py
@@ -61,10 +61,10 @@ print "np.repeat([Lambda], nbd).shape:",np.repeat([Lambda],
nbd).shape
print "np.repeat([Mu], nbd).shape:",np.repeat([Mu], nbd).shape
# handle Dirichlet condition
-(H,R) = gf.asm_dirichlet(DIRICHLET_BOUNDARY, mim, mfu, mfd,
mfd.eval('numpy.identity(3)'), mfd.eval('[0,0,0]'))
+(H,R) = gf.asm_dirichlet(DIRICHLET_BOUNDARY, mim, mfu, mfd,
mfd.eval('identity(3)'), mfd.eval('[0,0,0]'))
print "H.info: ",H.info # Spmat instance
print "R.shape: ",R.shape
-print "mfd.eval('numpy.identity(3)').shape:
",mfd.eval('numpy.identity(3)').shape
+print "mfd.eval('identity(3)').shape: ",mfd.eval('identity(3)').shape
print "mfd.eval('[0,0,0]').shape: ",mfd.eval('[0,0,0]').shape
(N,U0) = H.dirichlet_nullspace(R)
diff --git a/doc/sphinx/source/python/examples.rst
b/doc/sphinx/source/python/examples.rst
index 966acc3..3f4b66c 100644
--- a/doc/sphinx/source/python/examples.rst
+++ b/doc/sphinx/source/python/examples.rst
@@ -22,7 +22,7 @@ with the Dirichlet condition :math:`u = g(x)` on the domain
boundary. You can fi
the **py-file** of this example under the name **demo_step_by_step.py** in the
directory ``interface/tests/python/`` of the |gf| distribution.
-The first step is to **create a Mesh object**. It is possible to create simple
structured meshes or unstructured meshes for simple geometries (see
``getfem.Mesh('generate', mesher_object mo, scalar h))``) or to rely on an
external mesher (see ``getfem.Mesh('import',
+The first step is to **create a Mesh object**. It is possible to create simple
structured meshes or unstructured meshes for simple geometries (see
``getfem.Mesh('generate', mesher_object mo, scalar h)``) or to rely on an
external mesher (see ``getfem.Mesh('import',
string FORMAT, string FILENAME)``), or use very simple meshes. For this
example,
we just consider a regular mesh\index{cartesian mesh} whose nodes are
:math:`\{x_{i=0\ldots10,j=0..10}=(i/10,j/10)\}`
diff --git a/doc/sphinx/source/python/pre.rst b/doc/sphinx/source/python/pre.rst
index 4bc0b5b..f9b6ce1 100644
--- a/doc/sphinx/source/python/pre.rst
+++ b/doc/sphinx/source/python/pre.rst
@@ -78,7 +78,7 @@ PDEs involve various coefficients, for example:
\nabla\cdot(\lambda(x)\nabla u) = f(x).
-Hence one has to define a FEM for the main unknown :math:`u`, but also for the
+Hence one has to define an FEM for the main unknown :math:`u`, but also for the
data :math:`\lambda(x)` and :math:`f(x)` if they are not constant. In order to
interpolate easily these coefficients in their finite element space, one often
choose a Lagrangian FEM.
diff --git a/doc/sphinx/source/python/pygf.rst
b/doc/sphinx/source/python/pygf.rst
index 239df9b..1316912 100644
--- a/doc/sphinx/source/python/pygf.rst
+++ b/doc/sphinx/source/python/pygf.rst
@@ -126,7 +126,7 @@ The general organization of the python-interface is the
following:
.. class:: MeshFem(self, *args)
Descriptor for object linked to a mesh, where each convex has been assigned
- a FEM.
+ an FEM.
.. class:: MeshIm(self, *args)
diff --git a/doc/sphinx/source/scilab/intro.rst
b/doc/sphinx/source/scilab/intro.rst
index e3fa55f..a25242d 100644
--- a/doc/sphinx/source/scilab/intro.rst
+++ b/doc/sphinx/source/scilab/intro.rst
@@ -13,6 +13,6 @@ particular refer to the `user documentation`_ to have a more
extensive
description of the structures algorithms and concepts used.
-This documentation is still under construction. It is still a to close copy of
the Matlab interface documentation.
+This documentation is still under construction. It is still close to copy of
the Matlab interface documentation.
.. include:: ../license.txt
diff --git a/doc/sphinx/source/scilab/scilabgf.rst
b/doc/sphinx/source/scilab/scilabgf.rst
index 1e21d62..8b832ee 100644
--- a/doc/sphinx/source/scilab/scilabgf.rst
+++ b/doc/sphinx/source/scilab/scilabgf.rst
@@ -104,7 +104,7 @@ important objects.
* :envvar:`gfCvStruct` : stores formal information convex structures (nb. of
points,
nb. of faces which are themselves convex structures).
* :envvar:`gfMeshFem` : object linked to a mesh, where each convex has been
assigned
- a FEM. Created with ``gf_mesh_fem``.
+ an FEM. Created with ``gf_mesh_fem``.
* :envvar:`gfMeshImM` : object linked to a mesh, where each convex has been
assigned
an integration method. Created with ``gf_mesh_im``.
* :envvar:`gfMeshSlice` : object linked to a mesh, very similar to a
diff --git a/doc/sphinx/source/tutorial/wheel.rst
b/doc/sphinx/source/tutorial/wheel.rst
index fc5eac5..a553928 100644
--- a/doc/sphinx/source/tutorial/wheel.rst
+++ b/doc/sphinx/source/tutorial/wheel.rst
@@ -207,7 +207,6 @@ This could be added to the model with the weak form
language:
.. code-block:: python
- md.add_filtered_fem_variable('lambda_D', mflambda, HOLE_BOUND)
md.add_initialized_data('F', [applied_force/(8*2*np.pi)])
md.add_linear_term(mim1, '-lambda_D.Test_u1 +
(alpha_D*[0;1]-u1).Test_lambda_D'
' + (lambda_D.[0;1]+F)*Test_alpha_D', HOLE_BOUND)
diff --git a/doc/sphinx/source/userdoc/gasm_high.rst
b/doc/sphinx/source/userdoc/gasm_high.rst
index 8dc50df..19711dd 100644
--- a/doc/sphinx/source/userdoc/gasm_high.rst
+++ b/doc/sphinx/source/userdoc/gasm_high.rst
@@ -954,7 +954,7 @@ Some other transformations are available for the use into
Hybrid High-Order meth
Xfem discontinuity evaluation (with mesh_fem_level_set)
-------------------------------------------------------
-When using a fem cut by a level-set (using fem_level_set or mesh_fem_level_set
objects), it is often interesting to integrate the discontinuity jump of a
variable, or the jump in gradient or the average value. For this purpose, the
weak form language furnishes the following expressions for ``u`` a FEM
variable::
+When using a fem cut by a level-set (using fem_level_set or mesh_fem_level_set
objects), it is often interesting to integrate the discontinuity jump of a
variable, or the jump in gradient or the average value. For this purpose, the
weak form language furnishes the following expressions for ``u`` an FEM
variable::
Xfem_plus(u)
Xfem_plus(Grad_u)
diff --git a/doc/sphinx/source/userdoc/model_continuation.rst
b/doc/sphinx/source/userdoc/model_continuation.rst
index 5e999f7..9a67242 100644
--- a/doc/sphinx/source/userdoc/model_continuation.rst
+++ b/doc/sphinx/source/userdoc/model_continuation.rst
@@ -13,7 +13,7 @@
Numerical continuation and bifurcation
--------------------------------------
-Let an algebraic problem coming from discretisation of a FEM-model can be
+Let an algebraic problem coming from discretisation of an FEM-model can be
written in the form
.. math::
diff --git a/doc/sphinx/source/userdoc/model_dirichlet.rst
b/doc/sphinx/source/userdoc/model_dirichlet.rst
index 082cc96..43f89ff 100644
--- a/doc/sphinx/source/userdoc/model_dirichlet.rst
+++ b/doc/sphinx/source/userdoc/model_dirichlet.rst
@@ -38,7 +38,7 @@ adding a Dirichlet condition on ``varname`` thanks to a
multiplier variable
of the variable on that boundary is described by the data ``dataname`` which
should be previously defined in the model. If the data is omitted, the
Dirichlet
condition is assumed to be an homogeneous one (vanishing variable on the
-boundary). The data can be constant or described on a FEM. It can also be
scalar
+boundary). The data can be constant or described on an FEM. It can also be
scalar
or vector valued, depending on the variable. The variable ``multname`` should
be
added to the model by the method ``add_multiplier``. The function returns the
brick index in the model. The second function is::
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Getfem-commits] [getfem-commits] branch fixmisspell updated: :hammer_and_wrench: typo and sample code,
Tetsuo Koyama <=