[Dune] [#750] Prametrized boundary not working for ALUSimplexGrid<2, 2>

Dune flyspray at dune-project.org
Wed Mar 3 21:30:10 CET 2010


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#750 - Prametrized boundary not working for ALUSimplexGrid<2,2>
User who did this - Andreas Dedner (dedner)

----------
There was a decision in Berlin 2009. But since then there has been a lot of
discussion on this and some further points came up, which (for me) even make
the sequential interface questionable. The main problem is the internal
generation of these boundary segments and the problem pops up in two places:
load balancing and restart. This problem was also discussed in FS672.

It seems to me to be much simpler and clearer to add one boundary function to the
grid which sort of is a discrete function on the boundary, e.g. has a method
evaluate(intersection, localX). For element projections this could object
could also have a method evaluate(entity,localX).Not all the boundary segments reside
in this object (so not a lot is changed from the implementation already available in
DUNE). There is no question of who owns these projections and load balancing and
restart is a problem of the user who should be in position to handle it. 
Basically it boils down to the question, if boundary segments should be user data
or something handles by the grid - some people found that question quite easy to
answer for boundary ids why not for boundary projections?

----------

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

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.




More information about the Dune mailing list