[Dune] [#442] Periodic boundary conditions in YaspGrid don't work

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#442 - Periodic boundary conditions in YaspGrid don't work
User who did this - Peter Bastian (peter)

----------
Hi,

1) I fixed the bug that caused the communicate method to crash in the periodic case in the sequential case (it might even have crashed in some parallel cases if one processor had to send more than one message to the same remote processor).

2) Christian Engwer was right that the global IDs for vertices are not those that one would expect (ie vertices that are identified on the periodic boundary do not have the same global id). I cannot fix this at the moment BUT I have a workaround that uses one communication to compute the correct global ids that have to be stored as user data then. I am happy to share this code with anyone who needs it.

3) Remarks of Oliver concerning the concept of periodic boundaries in YaspGrid. From a sequential perspective you are right that one would like to have periodic boundaries in a different way. BUT when you ever write a parallel code for periodic boundaries using iterative solvers you will find that it is quite natural how it is done in YaspGrid because your code runs parallel with and without periodic boundaries with almost zero change to the code. However, I never thought enough about P1 elements with periodic boundaries maybe it gets more difficult then...

----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=442#comment588

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.