From 1726b51abe4e4eede9d59acbcfeb8c98d0c9aa87 Mon Sep 17 00:00:00 2001 From: hartmann Date: Thu, 14 Apr 2005 18:56:14 +0000 Subject: [PATCH] Don't maintain doc directory on branch_anisotropic. Instead add this file to main branch. git-svn-id: https://svn.dealii.org/trunk@10496 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/news/anisotropic.html | 249 ++++++++++++++++++++++++++++++ 1 file changed, 249 insertions(+) create mode 100644 deal.II/doc/news/anisotropic.html diff --git a/deal.II/doc/news/anisotropic.html b/deal.II/doc/news/anisotropic.html new file mode 100644 index 0000000000..b1d6cab59d --- /dev/null +++ b/deal.II/doc/news/anisotropic.html @@ -0,0 +1,249 @@ + + + + + The deal.II news page + + + + + + +

Changes between the main branch and the anisotropic branch

+ +

+This is the list of changes between the main cvs branch and the +anisotropic branch of deal.II library. It is +subdivided into changes made to the three sub-libraries base, lac, and deal.II, as well as changes to the general infrastructure, documentation, etc. +

+ +

+All entries are signed with the names of the author. Regular +contributor's names are abbreviated by WB (Wolfgang Bangerth), GK +(Guido Kanschat), RH (Ralf Hartmann). +

+ + + +

Incompatibilities

+ +

+Following are a few modifications to the library that unfortunately +are incompatible with previous versions of the library, but which we +deem necessary for the extension of the library to anisotropic +refinement. +

+ + +
    +
  1. + Changed: GeometryInfo::children_per_cell has been replaced by + GeometryInfo::max_children_per_cell, which represents + the maximum number of children a cell might have, i.e. the + number of children in the case of isotropic refinement. But + note, that this number will rarely be needed in user codes. In + general, the number of children of a cell varies from cell to + cell and can be obtained by cell->n_children(), + which gives the number of children of a specific + cell which is refined iso- or anisotropically. +
    + (RH 2005/02/26) +

    + +
  2. + Changed: The analogous change applies to the number of children + of a face. GeometryInfo::subfaces_per_face has been replaced by + GeometryInfo::max_children_per_face, which represents + the maximum number of children a face might have, i.e. the + number of children in the case of an isotropic refined face. + But note, that this number will rarely be needed in user + codes. In general, the number of children of a face varies from + face to face and can be obtained by + face->n_children(), which gives the number of + children of a specific face which is refined iso- + or anisotropically. +
    + (RH 2005/02/26) +

    + +
  3. + Changed: The GeometryInfo::child_cell_on_face is generalized to + anisotropic refinement and has now an additional + RefineCase::Type argument. This function will + rarely be used in user codes, as e.g. the neighbor's child at a + specific face and subface should be accessed through + cell->neighbor_child_on_subface rather than + through the GeometryInfo::child_cell_on_face function. +
    + (RH 2005/02/27) +

    +
+ + + +

General

+ +
    +
  1. + New but temporarily: A global + anisotropic_refinement flag has been introduced + (defined in geometry_info.h, initialized in + data_out_base.cc) indicating whether an + anisotropic refinement has been performed or not. This flag is + checked throughout the code and throws an exception in all + parts of the library which are not yet generalized to + anisotropic refinement. This flag can be removed once + anisotropic refinement is fully incorporated into deal.II. +
    + (RH 2005/02/26) +

    +
+ + + + +

base

+ +
    +
+ + + + +

lac

+ +
    +
+ + + + +

deal.II

+ +
    +
  1. + Changed: When allowing anisotropic refinement it cannot be + garantueed that all children of a cell are stored in + consecutive components of the quads.quads or the + hexes.hexes vector, respectively. It is only known + that children are stored at least in pairs. Therefore, it is + not sufficient any more to store the index of the first child + of a cell, only. Now the indices of every second child, i.e. of + the even numbered children, must be stored. For this, the + cell->set_children + function now has a new argument representing the number of the + child for which the index shall be set. This function can only + be called for even numbered children. The same applies to the + face->set_children + function. +
    + Finally, we note that these functions are for internal use, + only. +
    + (RH 2005/03/03) +

    + +
  2. + Changed: The cell->refine_flag_set function now returns a + RefineCase::Type argument instead of a boolean. Be + aware, that you now still can ask + if(!cell->refine_flag_set()) , + if(cell->refine_flag_set()==false) and + if(cell->refine_flag_set()) , but you cannot ask + if(cell->refine_flag_set()==true) any more.
    + (RH 2005/03/03) +

    + +
  3. + Extended: The cell->set_refine_flag function now has a new + RefineCase::Type argument which defaults to GeometryInfo<dim>::isotropic_refinement.
    (RH + 2005/03/03) +

    + +
  4. + New: There is now a new GeometryInfo<dim>::isotropic_refinement variable of type + RefineCase::Type representing the isotropic + refinement case in dim dimensions, + i.e. GeometryInfo<1>::isotropic_refinement=RefineCase::cut_x, + GeometryInfo<2>::isotropic_refinement=RefineCase::cut_xy + and + GeometryInfo<3>::isotropic_refinement=RefineCase::cut_xyz. +
    + (RH 2005/03/03) +

    + +
  5. + New: There is now a new enum RefineCase::Type + defined in geometry_info.h, which allows to + describe all possible (anisotropic and isotropic) refinement + cases in (1,) 2 and 3 dimensions. +
    + (RH 2005/02/26) +

    + +
  6. + New: There is now a new TriaObjectAccessor::n_children function which returns the + number of children of the cell or face it was invoked for. +
    + (RH 2005/02/26) +

    + +
  7. + New: There is now a new TriaObjectAccessor::refine_case function which returns the + RefineCase::Type a cell or face is refined with. +
    + (RH 2005/02/26) +

    + +
  8. + New: There is now a new TriaObjectAccessor::set_refine_case function. This function + is mainly for internal use (required by Triangulation::execute_coarsening_and_refinement). It is + not provided for dim=1 as there the refinement + case defaults to isotropic refinement. +
    + (RH 2005/02/26) +

    + +
  9. + New: New vector<RefineCase::Type> + refine_cases vectors have been introduced in TriangulationLevel<2>::QuadsData and + TriangulationLevel<3>::HexesData. For + memory efficiency (but with a penalty on run-time) they might + be replaced by vector<vector<bool> > (dim, + vector<bool> (n_quads/n_hexes)), later. +
    + (RH 2005/02/26) +

    +
+ +
+Last update $Date$ + + + -- 2.39.5