From: Luca Heltai Date: Mon, 14 Jul 2014 15:54:06 +0000 (+0000) Subject: Added set_manifold with two arguments. X-Git-Tag: v8.2.0-rc1~303 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6fa9d90d974a23d4c78c90f913e3e6abc414b6fb;p=dealii.git Added set_manifold with two arguments. git-svn-id: https://svn.dealii.org/trunk@33168 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/include/deal.II/grid/tria.h b/deal.II/include/deal.II/grid/tria.h index 5af6ef9b29..e1bb6c5b1a 100644 --- a/deal.II/include/deal.II/grid/tria.h +++ b/deal.II/include/deal.II/grid/tria.h @@ -1781,59 +1781,39 @@ public: virtual void set_mesh_smoothing (const MeshSmoothing mesh_smoothing); /** - * If @p dim==spacedim, assign a boundary - * object to a certain part of the - * boundary of a the triangulation. If a - * face with boundary number @p number is - * refined, this object is used to find - * the location of new vertices on the - * boundary (see the results section of step-49 - * for a more in-depth discussion of this, with examples). - * It is also used for - * non-linear (i.e.: non-Q1) - * transformations of cells to the unit - * cell in shape function calculations. - * - * If @p dim!=spacedim the boundary object - * is in fact the exact manifold that the - * triangulation is approximating (for - * example a circle approximated by a - * polygon triangulation). As above, the - * refinement is made in such a way that - * the new points are located on the exact - * manifold. - * - * Numbers of boundary objects correspond - * to material numbers of faces at the - * boundary, for instance the material id - * in a UCD input file. They are not - * necessarily consecutive but must be in - * the range 0-(types::boundary_id-1). - * Material IDs on boundaries are also - * called boundary indicators and are - * accessed with accessor functions - * of that name. - * - * The @p boundary_object is not copied - * and MUST persist until the - * triangulation is destroyed. This is - * also true for triangulations generated - * from this one by @p - * copy_triangulation. - * - * It is possible to remove or replace - * the boundary object during the - * lifetime of a non-empty - * triangulation. Usually, this is done - * before the first refinement and is - * dangerous afterwards. Removal of a - * boundary object is done by - * set_boundary(number), - * i.e. the function of same name but - * only one argument. This operation then - * replaces the boundary object given - * before by a straight boundary - * approximation. + * If @p dim==spacedim, assign a boundary object to a certain part + * of the boundary of a the triangulation. If a face with boundary + * number @p number is refined, this object is used to find the + * location of new vertices on the boundary (see the results section + * of step-49 for a more in-depth discussion of this, with + * examples). It is also used for non-linear (i.e.: non-Q1) + * transformations of cells to the unit cell in shape function + * calculations. + * + * If @p dim!=spacedim the boundary object is in fact the exact + * manifold that the triangulation is approximating (for example a + * circle approximated by a polygon triangulation). As above, the + * refinement is made in such a way that the new points are located + * on the exact manifold. + * + * Numbers of boundary objects correspond to material numbers of + * faces at the boundary, for instance the material id in a UCD + * input file. They are not necessarily consecutive but must be in + * the range 0-(types::boundary_id-1). Material IDs on boundaries + * are also called boundary indicators and are accessed with + * accessor functions of that name. + * + * The @p boundary_object is not copied and MUST persist until the + * triangulation is destroyed. This is also true for triangulations + * generated from this one by @p copy_triangulation. + * + * It is possible to remove or replace the boundary object during + * the lifetime of a non-empty triangulation. Usually, this is done + * before the first refinement and is dangerous afterwards. Removal + * of a boundary object is done by set_boundary(number), + * i.e. the function of same name but only one argument. This + * operation then replaces the boundary object given before by a + * straight boundary approximation. * * @ingroup boundary * @@ -1854,6 +1834,35 @@ public: * @see @ref GlossBoundaryIndicator "Glossary entry on boundary indicators" */ void set_boundary (const types::manifold_id number); + + /** + * Assign a manifold object to a certain part of the the + * triangulation. If an object with manfifold number @p number is + * refined, this object is used to find the location of new vertices + * (see the results section of step-49 for a more in-depth + * discussion of this, with examples). It is also used for + * non-linear (i.e.: non-Q1) transformations of cells to the unit + * cell in shape function calculations. + * + * The @p manifold_object is not copied and MUST persist until the + * triangulation is destroyed. This is also true for triangulations + * generated from this one by @p copy_triangulation. + * + * It is possible to remove or replace the boundary object during + * the lifetime of a non-empty triangulation. Usually, this is done + * before the first refinement and is dangerous afterwards. Removal + * of a manifold object is done by set_manifold(number), + * i.e. the function of same name but only one argument. This + * operation then replaces the manifold object given before by a + * straight manifold approximation. + * + * @ingroup manifold + * + * @see @ref GlossManifoldIndicator "Glossary entry on manifold indicators" + */ + void set_manifold (const types::manifold_id number, + const Boundary &manifold_object); + /** * Reset those parts of the triangulation with the given manifold_id diff --git a/deal.II/source/grid/tria.cc b/deal.II/source/grid/tria.cc index 3ed89fc573..eeeef5adc9 100644 --- a/deal.II/source/grid/tria.cc +++ b/deal.II/source/grid/tria.cc @@ -9591,11 +9591,19 @@ template void Triangulation::set_boundary (const types::manifold_id m_number, const Boundary &boundary_object) +{ + set_manifold(m_number, boundary_object); +} + +template +void +Triangulation::set_manifold (const types::manifold_id m_number, + const Boundary &manifold_object) { Assert(m_number < numbers::invalid_manifold_id, ExcIndexRange(m_number,0,numbers::invalid_manifold_id)); - manifold[m_number] = &boundary_object; + manifold[m_number] = &manifold_object; } diff --git a/tests/manifold/manifold_id_05.cc b/tests/manifold/manifold_id_05.cc index e6a5a52b55..5a4ca3e063 100644 --- a/tests/manifold/manifold_id_05.cc +++ b/tests/manifold/manifold_id_05.cc @@ -41,7 +41,7 @@ void test(unsigned int ref=1){ typename Triangulation::active_cell_iterator cell; tria.begin_active()->face(0)->set_manifold_id(1); - tria.set_boundary(1,boundary); + tria.set_manifold(1,boundary); tria.refine_global(2); diff --git a/tests/manifold/manifold_id_06.cc b/tests/manifold/manifold_id_06.cc index 8fa4e892ca..442a291da0 100644 --- a/tests/manifold/manifold_id_06.cc +++ b/tests/manifold/manifold_id_06.cc @@ -52,7 +52,7 @@ void test(unsigned int ref=1){ if(cell->face(f)->center().distance(center)< radius) cell->face(f)->set_all_manifold_ids(1); - tria.set_boundary(1,boundary); + tria.set_manifold(1,boundary); tria.refine_global(2); GridOut gridout; diff --git a/tests/manifold/manifold_id_07.cc b/tests/manifold/manifold_id_07.cc index 9e0662f45a..204f66e0e2 100644 --- a/tests/manifold/manifold_id_07.cc +++ b/tests/manifold/manifold_id_07.cc @@ -43,7 +43,7 @@ void test(unsigned int ref=1){ typename Triangulation::active_cell_iterator cell; tria.begin_active()->face(0)->set_manifold_id(1); - tria.set_boundary(1,boundary); + tria.set_manifold(1,boundary); tria.refine_global(2);