From 40e742edb95ca9fb5a6553604adb9258d25349d6 Mon Sep 17 00:00:00 2001 From: hartmann Date: Wed, 6 Jul 2005 15:21:13 +0000 Subject: [PATCH] Reformatting. git-svn-id: https://svn.dealii.org/trunk@11077 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/news/changes.html | 210 +++++++++++++++++++--------------- 1 file changed, 115 insertions(+), 95 deletions(-) diff --git a/deal.II/doc/news/changes.html b/deal.II/doc/news/changes.html index 16abfc7836..a1b9017f7b 100644 --- a/deal.II/doc/news/changes.html +++ b/deal.II/doc/news/changes.html @@ -42,86 +42,100 @@ inconvenience this causes.
    -
  1. Changed: The way boundary constraints were handled in the step-17 - tutorial program was conceptually flawed. We tried to eliminate boundary - nodes locally on the cell level, and hanging node constraints subsequently - when transferring into the global matrix. However, this doesn't work in - general: the elimination of hanging node constraints could re-populate rows - and columns that had already been vacated during boundary node - elimination. At the end of a long though process, we came to the conclusion - that it is impossible to revert the traditional order of operations: first - eliminate all hanging node constraints, then eliminate all boundary - nodes. This leads to a situation where the MatrixTools::local_apply_boundary_values function is - not very useful any more, except for the special case where there are no - hanging nodes. The step-17 example program has therefore been changed to use - the MatrixTools::apply_boundary_values function - again, though hanging node elimination still happens during transfer into - the global matrix. -
    (WB 2005/05/05) -

    - -
  2. Changed: The class MGCoarseGridLACIteration lost two template - arguments. Since the matrix and preconditioner are now stored in - form of PointerMatrix objects, handling - of the class is much simpler, in particular when exchanging - preconditioners. -
    (GK 2005/05/03) -

    - -
  3. Changed: The template argument of BlockMatrixArray was changed to - number, equal to the same argument of the used BlockVector. Furthermore, its constructor - requires an additional argument of type VectorMemory<Vector<number> > - providing space for auxiliary vectors. Since the entries are now of - type PointerMatrixBase, even matrices - with blocks of different types can be constructed. -
    (GK 2005/03/21) -

    - -
  4. Changed: The GeometryInfo::vertices_adjacent_to_line function has been - renamed to GeometryInfo::line_to_cell_vertices to be named analogous to - the face_to_cell_vertices, face_to_cell_lines and child_to_cell_coordinates functions. -
    - (RH 2005/03/14) -

    - -
  5. Changed: the file multigrid/mg_dof_tools.h was - renamed to multigrid/mg_tools.h in order to match the name - of the class contained. -
    - (GK 2005/03/09) -

    - -
  6. Changed: DoFTools::make_flux_sparsity_pattern, MGTools::make_flux_sparsity_pattern and similar - functions in these classes do not receive arguments of type FullMatrix<double> anymore. Instead, they - get a Table<2,DoFTools::Coupling>, - which contains more meaningful enums. -
    - (GK 2005/03/09) -

    - -
  7. Changed: Multigrid::Multigrid receives an argument determining the - type of multigrid cycle istead of the minimum and maximum - levels. The latter were rarely used anyway and can be modified by - set_minlevel() and set_maxlevel() -
    - (GK 2005/03/09) -

    +
  8. + Changed: The way boundary constraints were handled in the + step-17 tutorial program was conceptually flawed. We tried to + eliminate boundary nodes locally on the cell level, and hanging + node constraints subsequently when transferring into the global + matrix. However, this doesn't work in general: the elimination + of hanging node constraints could re-populate rows and columns + that had already been vacated during boundary node + elimination. At the end of a long though process, we came to + the conclusion that it is impossible to revert the traditional + order of operations: first eliminate all hanging node + constraints, then eliminate all boundary nodes. This leads to a + situation where the MatrixTools::local_apply_boundary_values + function is not very useful any more, except for the special + case where there are no hanging nodes. The step-17 example + program has therefore been changed to use the MatrixTools::apply_boundary_values + function again, though hanging node elimination still happens + during transfer into the global matrix. +
    + (WB 2005/05/05) +

    + +
  9. + Changed: The class MGCoarseGridLACIteration lost two template + arguments. Since the matrix and preconditioner are now stored + in form of PointerMatrix objects, + handling of the class is much simpler, in particular when + exchanging preconditioners. +
    + (GK 2005/05/03) +

    + +
  10. + Changed: The template argument of BlockMatrixArray was changed to + number, equal to the same argument of the used BlockVector. Furthermore, its constructor + requires an additional argument of type VectorMemory<Vector<number> > + providing space for auxiliary vectors. Since the entries are + now of type PointerMatrixBase, even + matrices with blocks of different types can be constructed. +
    + (GK 2005/03/21) +

    + +
  11. + Changed: The GeometryInfo::vertices_adjacent_to_line function has + been renamed to GeometryInfo::line_to_cell_vertices to be named + analogous to the face_to_cell_vertices, face_to_cell_lines and child_to_cell_coordinates functions. +
    + (RH 2005/03/14) +

    + +
  12. + Changed: the file multigrid/mg_dof_tools.h was renamed + to multigrid/mg_tools.h in order to match the name of + the class contained. +
    + (GK 2005/03/09) +

    + +
  13. + Changed: DoFTools::make_flux_sparsity_pattern, MGTools::make_flux_sparsity_pattern and similar + functions in these classes do not receive arguments of type + FullMatrix<double> + anymore. Instead, they get a Table<2,DoFTools::Coupling>, which + contains more meaningful enums. +
    + (GK 2005/03/09) +

    +
  14. + Changed: Multigrid::Multigrid receives an argument + determining the type of multigrid cycle istead of the minimum + and maximum levels. The latter were rarely used anyway and can + be modified by set_minlevel() and + set_maxlevel() +
    + (GK 2005/03/09) +

@@ -515,11 +529,13 @@ inconvenience this causes.

deal.II

    -
  1. Improved: The class FiniteElementData now stores information on the - Sobolev space a finite element space conforms with. -
    (GK 2005/06/29) -

    +
  2. + Improved: The class FiniteElementData now stores information + on the Sobolev space a finite element space conforms with. +
    + (GK 2005/06/29) +

  3. New: Added function -

  4. Improved: The function DoFTools::count_dofs_per_component and its counterpart - in MGTools got an additional - argument. This argument allows to count the degrees of freedom of - nonprimitive vector valued elements only once, instead of in every component. - Although this argument defaults to the previous behavior, it had to be put - into the argument list ahead of target_component in order to make - use of default arguments more efficiently. The old order of - arguments can still be used through a wrapper function. -
    (GK 2005/06/22) -

    +
  5. + Improved: The function DoFTools::count_dofs_per_component and its + counterpart in MGTools got an + additional argument. This argument allows to count the degrees + of freedom of nonprimitive vector valued elements only once, + instead of in every component. Although this argument defaults + to the previous behavior, it had to be put into the argument + list ahead of target_component in order to make use of + default arguments more efficiently. The old order of arguments + can still be used through a wrapper function. +
    + (GK 2005/06/22) +

  6. Improved: The GeometryInfo::