Hi all,
I have a question about the constructor initialization list. In some
tutorials, we initialize the dof_handler in the constructor with parameter
triangulation, however, the triangulation is initialized in some member
function within this class, which means when we initialize the class,
Bruno,
> Is there a different between how DynamicSparsityPatterns and
> BlockDynamicSparsityPatterns behave?
The latter is just an array of the former. Under the hood, every block
is simply a DynamicSparsityPattern that can be initialized in the same
way one always does.
> When you look
Dear community
I am trying to find a good way to deal with the following problem.
I am interested in a Laplace-Beltrami simulation (say with unknown scalar
field c) on a surface that advects (with displacement field u) enclosesing
a volume of say elastic material.
The two problems are per se
Giorgos,
You can find a discussion for how constraints are handled in deal.II in
https://www.dealii.org/developer/doxygen/deal.II/group__constraints.html.
Thank you for your feedback.
> I'll try to explain what I try to calculate with the help of a standard
> FEM textbook:
>
> [...]
>
> In the
Thank you for your feedback.
I'll try to explain what I try to calculate with the help of a standard FEM
textbook:
[image: CaptureFEMbook.PNG]
In the book the global system is partitioned so that the first row contains
the known U1 dofs and the second row the unknown the dofs U2.
They solve
On 9/3/19 2:40 AM, Konrad wrote:
>
> I have a little technical question though: Can I attach the mpi_communicators
> that you use in the deal.ii tutorials also somehow to a
> boost::mpi::communicator?
>
> https://www.boost.org/doc/libs/1_48_0/doc/html/boost/mpi/communicator.html
>
> Never
Dear Daniel,
Thank you very much for your reply! You are absolutely right. I used the
Debug mode where this issue occurs. In Release mode, the problem is gone.
Best,
Andreas
--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see
Thank you, Wolfgang, problem solved. But in a much simpler way. My basis
object is not easily serializable so I have to recreate it and destroy the
old one anyway (for now) once cells are moved to other nodes. So I do not
send send them but rather create them and work with them on each node (if
