From: wolf Date: Mon, 20 Jun 2005 17:09:46 +0000 (+0000) Subject: Add a few links into the documentation for the extension ideas. X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c5adf288bb6e8b1a3fb0fdc546ae0c857ba982e2;p=dealii-svn.git Add a few links into the documentation for the extension ideas. git-svn-id: https://svn.dealii.org/trunk@10888 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.html b/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.html index ae9e29a258..2038065ada 100644 --- a/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.html +++ b/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.html @@ -1365,7 +1365,11 @@ in fact, but has been left for future tutorial programs or as an exercise, if you wish. The main complication one has to overcome is that one has to transfer the data that is stored in the quadrature points of the cells of the old mesh to the new mesh, preferably by some sort of projection scheme. This -is only slightly messy in the sequential case. However, it becomes complicated once +is only slightly messy in the sequential case; in fact, the functions +FETools::get_projection_from_quadrature_points_matrix will do +the projection, and the FiniteElement::get_restriction_matrix and +FiniteElement::get_prolongation_matrix functions will do the +transfer between mother and child cells. However, it becomes complicated once we run the program in parallel, since then each process only stores this data for the cells it owned on the old mesh, and it may need to know the values of the quadrature point data on other cells if the corresponding cells on the new diff --git a/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.pdf b/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.pdf index ded5e9569d..05a5e2e4b8 100644 Binary files a/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.pdf and b/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.pdf differ diff --git a/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.tex b/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.tex index 3fddef76cf..b03c86c8e2 100644 --- a/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.tex +++ b/deal.II/doc/tutorial/chapter-2.step-by-step/step-18.data/intro.tex @@ -616,13 +616,17 @@ in fact, but has been left for future tutorial programs or as an exercise, if you wish. The main complication one has to overcome is that one has to transfer the data that is stored in the quadrature points of the cells of the old mesh to the new mesh, preferably by some sort of projection scheme. This -is only slightly messy in the sequential case. However, it becomes complicated once -we run the program in parallel, since then each process only stores this data -for the cells it owned on the old mesh, and it may need to know the values of -the quadrature point data on other cells if the corresponding cells on the new -mesh are assigned to this process after subdividing the new mesh. A global -communication of these data elements is therefore necessary, making the entire -process a little more unpleasant. +is only slightly messy in the sequential case; in fact, the functions +\texttt{FETools} \texttt{::} \texttt{get\_projection\_from\_quadrature\_points\_matrix} will do +the projection, and the \texttt{FiniteElement} \texttt{::} \texttt{get\_restriction\_matrix} and +\texttt{FiniteElement} \texttt{::} \texttt{get\_prolongation\_matrix} functions will do the +transfer between mother and child cells. However, it becomes complicated +once we run the program in parallel, since then each process only stores this +data for the cells it owned on the old mesh, and it may need to know the +values of the quadrature point data on other cells if the corresponding cells +on the new mesh are assigned to this process after subdividing the new mesh. A +global communication of these data elements is therefore necessary, making the +entire process a little more unpleasant. \paragraph*{Ensuring mesh regularity.} At present, the program makes no attempt