getfem-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

## [Getfem-commits] (no subject)

 From: Tetsuo Koyama Subject: [Getfem-commits] (no subject) Date: Mon, 17 Dec 2018 07:58:55 -0500 (EST)

branch: fixmisspell
commit 366dceeabaae21436738ca425b91c00ccf0bba78
Author: Tetsuo Koyama <address@hidden>
Date:   Mon Dec 17 21:52:09 2018 +0900

Fix typo in docs
---
doc/sphinx/source/project/libdesc_cont.rst            | 2 +-
doc/sphinx/source/project/libdesc_gmm.rst             | 2 +-
doc/sphinx/source/project/libdesc_high_gen_assemb.rst | 2 +-
doc/sphinx/source/project/libdesc_mesh.rst            | 4 ++--
doc/sphinx/source/tutorial/basic_usage.rst            | 2 +-
doc/sphinx/source/tutorial/install.rst                | 2 +-
doc/sphinx/source/tutorial/intro.rst                  | 4 ++--
doc/sphinx/source/tutorial/thermo_coupling.rst        | 2 +-
8 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/doc/sphinx/source/project/libdesc_cont.rst
b/doc/sphinx/source/project/libdesc_cont.rst
index 4b943e6..90b61a2 100644
--- a/doc/sphinx/source/project/libdesc_cont.rst
+++ b/doc/sphinx/source/project/libdesc_cont.rst
@@ -29,7 +29,7 @@ Files
State
^^^^^

-Have already generic and advanced fonctionalities.
+Have already generic and advanced functionalities.

Perspectives
^^^^^^^^^^^^
diff --git a/doc/sphinx/source/project/libdesc_gmm.rst
b/doc/sphinx/source/project/libdesc_gmm.rst
index cd0fe47..1d2abc9 100644
--- a/doc/sphinx/source/project/libdesc_gmm.rst
+++ b/doc/sphinx/source/project/libdesc_gmm.rst
@@ -53,7 +53,7 @@ procedures.
Perspectives
^^^^^^^^^^^^

-There is potentatialy several points to be improved in |gmm| (partial
+There is potentially several points to be improved in |gmm| (partial
introduction of expression template for some base types of matrix and vectors,
think about the way to represent in a more coherent manner sparse sub-vectors
and sub-matrices, introduction of C++ concepts, etc.). However, since |gmm|
diff --git a/doc/sphinx/source/project/libdesc_high_gen_assemb.rst
b/doc/sphinx/source/project/libdesc_high_gen_assemb.rst
index bcbf041..35e1697 100644
--- a/doc/sphinx/source/project/libdesc_high_gen_assemb.rst
+++ b/doc/sphinx/source/project/libdesc_high_gen_assemb.rst
@@ -26,7 +26,7 @@ Files

:file:getfem_generic_assembly.h, "Main header for exported definitions.
Only this header has to be included to use the generic assembly. Other headers
of the module are for internal use only."
:file:getfem_generic_assembly_tree.h and
:file:getfem_generic_assembly_tree.cc, "Definition of the tree structure and
basic operations on it, including reading an assembly string and transform it
in a syntax tree and make the invert transformation of a tree into a string."
-   :file:getfem_generic_assembly_fonction_and_operators.h and
:file:getfem_generic_assembly_fonction_and_operators.cc, "Definition of
redefined function and nonlinear operator of the weak form language."
+   :file:getfem_generic_assembly_function_and_operators.h and
:file:getfem_generic_assembly_function_and_operators.cc, "Definition of
redefined function and nonlinear operator of the weak form language."
:file:getfem_generic_assembly_semantic.h and
:file:getfem_generic_assembly_semantic.cc, "Semantic analysis and enrichment
of the syntax tree. Include some operations such as making the derivation of a
tree with respect to a variable or computing the tree corresponding to the
gradient of an expression."
:file:getfem_generic_assembly_workspace.cc, "Methodes of the workspace
object (defined in :file:getfem_generic_assembly.h)."
:file:getfem_generic_assembly_compile_and_exec.h and
:file:getfem_generic_assembly_compile_and_exec.cc, "Definition of the
optimized instructions, compilation into a sequel of optimize instructions and
execution of the instructions on Gauss point/interpolation points."
diff --git a/doc/sphinx/source/project/libdesc_mesh.rst
b/doc/sphinx/source/project/libdesc_mesh.rst
index 6b64cb4..d0525eb 100644
--- a/doc/sphinx/source/project/libdesc_mesh.rst
+++ b/doc/sphinx/source/project/libdesc_mesh.rst
@@ -51,7 +51,7 @@ Files
:file:bgeot_geotrans_inv.h and :file:bgeot_geotrans_inv.cc, "A tool to
invert geometric transformations."
:file:getfem_mesh.h and :file:getfem_mesh.cc, "Fully describes a mesh
(with the geometric transformations, subparts of the mesh, support for
parallelization). Includes the Bank algorithm to refine a mesh."
:file:getfem_deformable_mesh.h, "defines an object capable to deform a
mesh with respect to a displacement field and capable to restore it"
-   :file:getfem_mesher.h and :file:getfem_mesher.cc, "An experimental
mesher, in arbitrary dimension. To be used with care and  quite slow (because
of node optimization). it meshes geometries defined by some level sets."
+   :file:getfem_mesher.h and :file:getfem_mesher.cc, "An experimental
mesher, in arbitrary dimension. To be used with care and  quite slow (because
of node optimization). It meshes geometries defined by some level sets."
:file:getfem_import.h and :file:getfem_import.cc, "Import mesh files in
various formats"
:file:getfem_regular_meshes.h and :file:getfem_regular_meshes.cc,
"Produces structured meshes"
:file:getfem_mesh_slicers.h and :file:getfem_mesh_slicers.cc, "A slice
is built from a mesh, by applying some slicing operations (cut the mesh with a
plane, intersect with a sphere, take the boundary faces, etc..). They are used
for post-treatment (exportation of results to VTK or OpenDX,  etc.)."
@@ -74,7 +74,7 @@ namespace (getfem).

The file :file:bgeot_mesh.h could be renamed :file:getfem_basic_mesh.h.

-A  bibliographical review on how to efficiently store a mesh and implement the
main opertions (add a node, an element, deal with faces, find the neighbour
elements, the isolated faces ...) would be interesting to make the mesh
structure evolve.
+A  bibliographical review on how to efficiently store a mesh and implement the
main operations (add a node, an element, deal with faces, find the neighbour
elements, the isolated faces ...) would be interesting to make the mesh
structure evolve.

A senstive algorithm is the one (in bgeot_node_tab.cc) which identify the too
much close nodes. More investigations (and documentation) are probably
necessary.

diff --git a/doc/sphinx/source/tutorial/basic_usage.rst
b/doc/sphinx/source/tutorial/basic_usage.rst
index dd5c2f1..5a9111f 100644
--- a/doc/sphinx/source/tutorial/basic_usage.rst
+++ b/doc/sphinx/source/tutorial/basic_usage.rst
@@ -38,4 +38,4 @@ A program using getfem will often have the following
structure ::

Model.solve(...options)

-Note that instead of defining your pde terms with the weak form language (see
:ref:ud-gasm-high for more details on the syntaxt of the weak form language),
you can use predefined bricks for standard terms : generic eliptic term,
linearized or finite strain elasticity, standard boundary conditions ...
+Note that instead of defining your pde terms with the weak form language (see
:ref:ud-gasm-high for more details on the syntax of the weak form language),
you can use predefined bricks for standard terms : generic eliptic term,
linearized or finite strain elasticity, standard boundary conditions ...
diff --git a/doc/sphinx/source/tutorial/install.rst
b/doc/sphinx/source/tutorial/install.rst
index 6712794..65d58a9 100644
--- a/doc/sphinx/source/tutorial/install.rst
+++ b/doc/sphinx/source/tutorial/install.rst
@@ -21,7 +21,7 @@ The main dependences of |Gf| on other libraries are

* sequential MUMPS package (direct solver for sparse matrices) if you want to
use it instead of the SuperLU version distributed along with |gf|.

-* Parallel MUMPS, METIS and MPI4PY packages if you want to ue the MPI
parallelized version of |gf|.
+* Parallel MUMPS, METIS and MPI4PY packages if you want to use the MPI
parallelized version of |gf|.

* qhull package for mesh generation and fictitious domain applications

diff --git a/doc/sphinx/source/tutorial/intro.rst
b/doc/sphinx/source/tutorial/intro.rst
index 497f741..72251f6 100644
--- a/doc/sphinx/source/tutorial/intro.rst
+++ b/doc/sphinx/source/tutorial/intro.rst
@@ -16,12 +16,12 @@ The main presented functionalities are the following
- Approximation of multiphysics problems and the use of the generic assembly.
- The use of fixed-size variables.
- Contact problems.
-  - Fictitious domain fonctionalities and transformations allowing inter-mesh
or inter-region assembly.
+  - Fictitious domain functionalities and transformations allowing inter-mesh
or inter-region assembly.
- Continuation / bifurcation problems.

This tutorial does not of course takes the place of the various
documentations. The user documentation (that of the C++ library) is the
reference one concerning the description of implemented methods. Interfaces
documentations describe the use of the different functionalities from
interfaces but do not repeat the description of methods. 'Developpers's guide'
documentation describes more internal concerning the organization of the
library.

-| Gf | is a free collaborative project hosted by the Savannah
<http://savannah.gnu.org>_ site (see
https://savannah.nongnu.org/projects/getfem). New contributors are welcome to
all aspects of the project.
+|Gf| is a free collaborative project hosted by the Savannah
<http://savannah.gnu.org>_ site (see
https://savannah.nongnu.org/projects/getfem). New contributors are welcome to
all aspects of the project.

diff --git a/doc/sphinx/source/tutorial/thermo_coupling.rst
b/doc/sphinx/source/tutorial/thermo_coupling.rst
index 49dbaf2..29ae155 100644
--- a/doc/sphinx/source/tutorial/thermo_coupling.rst
+++ b/doc/sphinx/source/tutorial/thermo_coupling.rst
@@ -511,7 +511,7 @@ Let us now begin by the elastic deformation problem. We
will use the predefined

\int_{\Omega} (\lambda^* \mbox{div}(u) I + 2\mu
\bar{\varepsilon}(u)):\bar{\varepsilon}(\delta_u)dx,

-to the tangent linear system. In order to use this model brick, the data
corresponding to he |Lame| coefficient have to be added to the model first.
Here, the |Lame| coefficients are constant over the domain. However, it it also
possible to define some non-constant data. Note also that instead of using this
predefined brick, one can use equivalently the weak form language term
add_linear_term(md mim, "lambda*(Div_u*Div_Test_u) + mu*((Grad_u +
Grad_u'):Grad_Test_u)".
+to the tangent linear system. In order to use this model brick, the data
corresponding to the |Lame| coefficient have to be added to the model first.
Here, the |Lame| coefficients are constant over the domain. However, it it also
possible to define some non-constant data. Note also that instead of using this
predefined brick, one can use equivalently the weak form language term
add_linear_term(md mim, "lambda*(Div_u*Div_Test_u) + mu*((Grad_u +
Grad_u'):Grad_Test_u)".

Concerning the coupling term



reply via email to

 [Prev in Thread] Current Thread [Next in Thread]