← Back to team overview

dolfin team mailing list archive

Re: [noreply@xxxxxxxxxxxxx: [Branch ~dolfin-core/dolfin/rognes] Rev 5663: Add init to child after mesh refinement (why is this needed?!) and]

 

On Sun, Feb 13, 2011 at 09:23:36PM +0000, Garth N. Wells wrote:
>
>
> On 13/02/11 21:21, Anders Logg wrote:
> > On Sun, Feb 13, 2011 at 09:17:18PM +0000, Garth N. Wells wrote:
> >>
> >>
> >> On 13/02/11 21:02, Anders Logg wrote:
> >>> mesh.init() computes all connectivity and should almost never be
> >>> called, at least not from inside DOLFIN.
> >>>
> >>> Instead, the proper init function for the connectivity that is
> >>> actually used should be called, like mesh.init(1, 2) or similar.
> >>>
> >>> Note that calling init functions is not needed when using iterators
> >>> since the connectivity is then automatically initialized.
> >>>
> >>> The mesh that comes out of refine()
> >>
> >> Which you were going to change to 'adapt.
> >
> > Yes, but this depends on a merge with Marie's branch, which depends on
> > a release of UFC, which depends on you commenting on the proposed
> > changes of UFC. ;-)
> >
>
> Mark all the proposals as Blueprints for 1.6 - then I can see them all
> in one place and add comments.

Sure, but one thing to decide first is whether we do 1.6 or 2.0. It
depends on which blueprints we choose (listed in previous post). Some
of them require changing the names of some functions/classes which
makes 2.0 appropriate.

--
Anders




References