Several matching updates in MappingQ{,1}Eulerian.

diff --git a/doc/news/changes.h b/doc/news/changes.h
index f13477b36d7e6edb4c586c4eff5066f4f3e35ab9..3ca965d8686b5d4dd5d4ea186b5e8adf6259d9e7 100644 (file)
--- a/doc/news/changes.h
+++ b/doc/news/changes.h
@@ -139,8 +139,8 @@ inconvenience this causes.
 <h3>General</h3>
 
 <ol>
- <li> Changed: As MappingQEulerian before, MappingQ1Eulerian has gained
- a second constructor that reverts the order of the arguments to indicate
+ <li> Changed: Similar to MappingQEulerian, MappingQ1Eulerian has gained
+ a second constructor that reverses the order of the arguments to indicate
  which DoFHandler a vector is based on. The old constructor is now
  deprecated and will be removed in a future version.
  <br>

diff --git a/include/deal.II/fe/mapping_q1_eulerian.h b/include/deal.II/fe/mapping_q1_eulerian.h
index 69f7302f828eff79faada24a55fa2edb4c74638c..9809a40c9cbbf9028aa290843531c29ef9dbbbf5 100644 (file)
--- a/include/deal.II/fe/mapping_q1_eulerian.h
+++ b/include/deal.II/fe/mapping_q1_eulerian.h
@@ -68,8 +68,8 @@ template <typename> class Vector;
  *    FESystem<dim> fe(FE_Q<dim>(1), dim);
  *    DoFHandler<dim> flowfield_dof_handler(triangulation);
  *    flowfield_dof_handler.distribute_dofs(fe);
- *    Vector<double> map_points(flowfield_dof_handler.n_dofs());
- *    MappingQ1Eulerian<dim> mymapping(map_points, flowfield_dof_handler);
+ *    Vector<double> displacement_field(flowfield_dof_handler.n_dofs());
+ *    MappingQ1Eulerian<dim> mymapping(flowfield_dof_handler, displacement_field);
  * @endcode
  *
  * Note that since the vector of shift values and the dof handler are only
@@ -77,11 +77,8 @@ template <typename> class Vector;
  * whenever you use this object, the given objects still represent valid data.
  *
  * To enable the use of the MappingQ1Eulerian class also in the context of
- * parallel codes using the PETSc wrapper classes, the type of the vector can
- * be specified as template parameter <tt>EulerVectorType</tt> Not specifying
- * this template argument in applications using the PETSc vector classes leads
- * to the construction of a copy of the vector which is not acccessible
- * afterwards!
+ * parallel codes using the PETSc or Trilinos wrapper classes, the type of
+ * the vector can be specified as template parameter <tt>VectorType</tt>.
  *
  * For more information about the <tt>spacedim</tt> template parameter check
  * the documentation of FiniteElement or the one of Triangulation.

diff --git a/include/deal.II/fe/mapping_q_eulerian.h b/include/deal.II/fe/mapping_q_eulerian.h
index f046f690b5ed15cab79f1779760b3568228f3d47..c7de1fd904482c54a80ccf9a2c20f8dcaba0a6f8 100644 (file)
--- a/include/deal.II/fe/mapping_q_eulerian.h
+++ b/include/deal.II/fe/mapping_q_eulerian.h
@@ -81,11 +81,8 @@ template <typename> class Vector;
  * data.
  *
  * To enable the use of the MappingQ1Eulerian class also in the context of
- * parallel codes using the PETSc wrapper classes, the type of the vector can
- * be specified as template parameter <tt>EulerVectorType</tt> Not specifying
- * this template argument in applications using the PETSc vector classes leads
- * to the construction of a copy of the vector which is not accessible
- * afterwards!
+ * parallel codes using the PETSc or Trilinos wrapper classes, the type
+ * of the vector can be specified as template parameter <tt>VectorType</tt>.
  *
  * @author Joshua White, 2008
  */