* When creating the sparsity pattern as well as when assembling the linear
* system, we need to know about constraints on degrees of freedom, for
* example resulting from hanging nodes or boundary conditions. Like the
- * DynamicSparsityPattern class, the ConstraintMatrix can also take
+ * DynamicSparsityPattern class, the AffineConstraints container can also take
* an IndexSet upon construction that indicates for which of the possibly very
* large number of degrees of freedom it should actually store
* constraints. Unlike for the sparsity pattern, these are now only those
* this chain of constraints, it may not be sufficient to only store
* constraints on locally active degrees of freedom but one may also need to
* have constraints available on locally relevant ones. In that case, the
- * ConstraintMatrix object needs to be initialized with the IndexSet produced
- * by DoFTools::extract_locally_relevant_dofs() .
+ * AffineConstraints object needs to be initialized with the IndexSet
+ * produced by DoFTools::extract_locally_relevant_dofs() .
*
* In general, your program will continue to do something if you happen to not
* store all necessary constraints on each processor: you will just generate
* In addition to the DoF handler classes, this module holds a number of
* auxiliary classes not commonly used in application programs, as well as
* three classes that are not directly associated with the data structures of
- * the DoFHandler class. The first of these is the ConstraintMatrix class that
+ * the DoFHandler class. The first of these is the AffineConstraints class that
* stores and treats the constraints associated with hanging nodes. Secondly,
* the DoFRenumbering namespace offers functions that can reorder degrees of
* freedom; among its functions are ones that sort degrees of freedom in
* <dd>
* The numbers of row and column are types::global_dof_index even if it is not
* expected that someone will create a FullMatrix with so many entries.
- * However, some functions of ConstraintMatrix are templated on the matrix
- * type and thus, the
- * size of a FullMatrix has to be of the same type than the size of
- * SparseMatrix.
+ * However, some methods of the AffineConstraints class are templated on
+ * the matrix type and thus, the size of a FullMatrix has to be of the same
+ * type than the size of SparseMatrix.
* </dd>
*
* <dt class="glossary">@anchor GlobalDoFIndexSparseMatrix
*
* 1. At the end of your assembly loop on matrices and vectors. This needs to
* be done if you write entries directly or if you use
- * ConstraintMatrix::distribute_local_to_global. Use VectorOperation::add.
+ * AffineConstraints::distribute_local_to_global. Use VectorOperation::add.
*
* 2. When you are done setting individual elements in a matrix/vector before
* any other operations are done (adding to elements, other operations like
* VectorOperation::add.
*
* All other operations like scaling or adding vectors, assignments, calls
- * into deal.II (VectorTools, ConstraintMatrix, ...) or solvers do not require
- * calls to compress().
+ * into deal.II (VectorTools, AffineConstraints, ...) or solvers do not
+ * require calls to compress().
* </dd>
*
* @note Compressing is an operation that only applies to vectors whose
* <td>step-22</td>
* <td> Solving the Stokes equations of slow fluid flow on adaptive
* meshes. More on Schur complement solvers. Advanced use of the
- * ConstraintMatrix class.
+ * AffineConstraints class.
* </td></tr>
*
* <tr valign="top">