On Mon, May 2, 2011 at 2:04 PM, Kirk, Benjamin (JSC-EG311)
wrote:
>> class BoundaryElem : public Elem
>> {
>> Elem* _interior_parent;
>> Elem* self;
>> }
>>
>> All the Elem functionality could be implemented by forwarding to the
>> underlying "self" pointer, which represents some actual elemen
> class BoundaryElem : public Elem
> {
> Elem* _interior_parent;
> Elem* self;
> }
>
> All the Elem functionality could be implemented by forwarding to the
> underlying "self" pointer, which represents some actual element.
>
> But... that might be way too much work for something that could be
On Mon, May 2, 2011 at 1:24 PM, Roy Stogner wrote:
>
> Right now BoundaryMesh is kind of a second-class citizen.
> BoundaryInfo::sync only copies over active elements, so the refinement
> tree is lost, and in the 3D->2D AMR case neighbor information ends up
> being incorrect. Sync then uses the p
