From 244d2ed2d687233488f21f183e2f2fb8c1a6a914 Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Tue, 19 Apr 2011 00:11:23 +0000 Subject: [PATCH] Augment documentation. git-svn-id: https://svn.dealii.org/trunk@23607 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/examples/step-46/doc/intro.dox | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/deal.II/examples/step-46/doc/intro.dox b/deal.II/examples/step-46/doc/intro.dox index a9f9eb426b..aade0b5846 100644 --- a/deal.II/examples/step-46/doc/intro.dox +++ b/deal.II/examples/step-46/doc/intro.dox @@ -313,7 +313,7 @@ entry $i,j$: \mathbf n)_{\partial K \cap \Gamma_i}. @f] Although it isn't immediately obvious, this term presents a slight -complication: while $\psi_i[\mathbf u]$ and $\mathbf n$ are evaluate +complication: while $\psi_i[\mathbf u]$ and $\mathbf n$ are evaluated on the solid side of the interface (they are test functions for the displacement and the normal vector to $\Omega_s$, respectively, we need to evaluate $\psi_j[\mathbf v],\psi_j[p]$ on the fluid @@ -323,7 +323,18 @@ need FEFaceValue objects for both sides of the interface. To make things slightly worse, we may also have to deal with the fact that one side or the other may be refined, leaving us with the need to integrate over parts of a face. Take a look at the implementation -below on how to deal with this. +below on how to deal with this. + +As an additional complication, the matrix entries that result from this term +need to be added to the sparsity pattern of the matrix somehow. This, however, +is not too difficult: the term couples degrees of freedom from two adjacent +cells along a face, which is exactly the kind of thing one would do in +discontinuous Galerkin schemes for which the function +DoFTools::make_flux_sparsity_pattern was written. In the current context it +computes a superset of matrix entries compared to the usual +DoFTools::make_sparsity_pattern: it will also add the ones for faces where the +solution is discontinuous, which is exactlty the case at the interface between +the two subdomains. The second difficulty is that while we know how to enforce a zero velocity or stress on the external boundary (using -- 2.39.5