One fix that I have found (PETSc does this) is to assign every object its
own duplicated communicator which can then keep track of its own tags with
MPI's own get and set attributes functions.
Sometime back in the day (in the 2005-2010 range) I spent an inordinate amount
of time going through
Hello everyone!
This is deal.II newsletter #154.
It automatically reports recently merged features and discussions about the
deal.II finite element library.
## Below you find a list of recently proposed or merged features:
#11767: Update changelogs (proposed by drwells)
https://github.com/dea
Dear everyone,
I have a question on tagged messages and the best way to generate tags. A while
back we went through the whole library and consistently tagged all of our MPI
point-to-point messages - there was a long discussion about how to do this in
https://github.com/dealii/dealii/issues/8958
..just noted that the order is exactly the point in the loop framework.
I cannot assume a certain order in my boundary data (or I need to choose an
order corresponding to the loop function).
Special thanks to @peterrum for pointing this out. This thread is therefore
resolved.
Thank you very mu
Hi Martin,
thank you for your reply.
before going into detail and providing more information let me ask again in
order to avoid a misunderstanding. You say
> apart from when exactly the cells and faces are scheduled, i.e., possibly
a change in the order of roundoff errors.
As I said, my bounda
