[Dune] [Dune-Commit] dune-grid r7996 - trunk/dune/grid/common

[Carsten Gräser]

Hi Andreas,

Am 20.04.2012 20:52, schrieb Dedner, Andreas:
> Hi,
> 
> just to clarify:
> you iterate once over the whole grid per different type of boundary condition or
> you store some entity seeds? 
currently we indeed loop over all elements. But this is only an
implementation detail. Changing the implementation to only store
entity seeds of the adjacent elements is on our agenda.

Best,
Carsten


> 
> Best
> Andreas
> ________________________________________
> From: dune-bounces+a.s.dedner=warwick.ac.uk at dune-project.org [dune-bounces+a.s.dedner=warwick.ac.uk at dune-project.org] on behalf of Oliver Sander [sander at mi.fu-berlin.de]
> Sent: Friday, April 20, 2012 7:37 PM
> To: dune at dune-project.org
> Subject: Re: [Dune] [Dune-Commit] dune-grid r7996 - trunk/dune/grid/common
> 
> Hi,
> for each type of boundary condition that is not homogeneous Neumann
> I set up a file with a '1' for each vertex that is part of the
> corresponding boundary part.  dune-fufem has a class BoundaryPatch,
> which encapsulates parts of the boundary, and which you can set
> up with a per-vertex bitfield (which you read from the file).
> The BoundaryPatch provides an iterator over all boundary segments
> that are part of the patch, and we have a special type of assemblers
> that uses this iterator to assemble boundary conditions.
> 
> While having individual files for the different types of boundary
> conditions may not be the most elegant way, our approach has
> its advantages.  First of all, it doesn't rely on anything special
> in the grid interface.  More importantly, my boundary conditions
> need not be resolved by the macro grid boundary.  Sometimes that
> is very useful.
> 
> best,
> Oliver
> 
> Am 20.04.2012 20:02, schrieb Patrick Leidenberger:
>> Hi Oliver,
>>
>> in your comment about the boundaryId you wrote that you have a good
>> solution how to handle different boundary condition:
>>
>> On 04/18/2012 06:45 PM, Oliver Sander wrote:
>>> I am a bit surprised
>>> that so many people use boundaryId given that I have personally
>>> never had to use one of these methods, even though some of my problems
>>> have quite complicated boundary conditions.
>>
>> Can you please enlight me, how you handle them? I use the boundaryId in
>> my code, but I am always open for new ideas.
>>
>> Best regards
>>
>> Patrick