From 11b5329a00cbb0e622d3e38510a9997193674479 Mon Sep 17 00:00:00 2001 From: Guido Kanschat Date: Thu, 3 Jul 2003 10:20:25 +0000 Subject: [PATCH] Update documentation git-svn-id: https://svn.dealii.org/trunk@7832 0785d39b-7218-0410-832d-ea1e28bc413d --- .../deal.II/include/dofs/dof_renumbering.h | 33 ++++++++++--------- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/deal.II/deal.II/include/dofs/dof_renumbering.h b/deal.II/deal.II/include/dofs/dof_renumbering.h index 96fac9c929..ea31a9d14c 100644 --- a/deal.II/deal.II/include/dofs/dof_renumbering.h +++ b/deal.II/deal.II/include/dofs/dof_renumbering.h @@ -274,21 +274,24 @@ class DoFRenumbering * $n(i)n(j)$ if $i>j$. * - * You may want to give the order in - * which the components are to be ordered - * (e.g. if the second argument contains - * the numbers @p{(0, 3, 2, 1)}, then all - * indices of component @p{0} will be - * before those of component @p{3}, before - * those of component @p{2}, ...). The - * length of this list has to be the - * same as the number of components - * in the finite element, and has to - * contain all numbers counted from - * zero onwards. If - * you omit this argument, the same - * order as given by the finite element - * is used. + * You can specify that the + * components are ordered in a + * different way than suggested + * by the @p{FESystem} object you + * use. To this end, Set up the + * vector @p{component_order} + * such that the entry at index + * @p{i} denotes the number of + * the target component for dofs + * with component @p{i} in the + * @p{FESystem}. Naming the same + * component more than once is + * possible and results in a + * blocking of several components + * into one. + * If you omit this argument, the + * same order as given by the + * finite element is used. * * If one of the base finite * elements from which the global -- 2.39.5