dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

Very good. Since the mesh and the assembly are at the very core of
DOLFIN, I'd prefer if the development took place in the main DOLFIN
tree and that it happens in small steps. If changes are needed to the
mesh and to the assembly, I want to know what's going on (and help
out).

The mesh refinement is separate and can just be added when it works so
that can be done in a separate branch.

/Anders


        On Thu, Oct 12, 2006 at 05:46:44PM +0200, Johan Jansson wrote:
> Hi everyone,
> 
> I just wanted to notify you that I'm working on transitioning to the
> new mesh, so that there isn't any duplication of the effort. I've
> selected the strategy of throwing out the old mesh, so the new mesh is
> named Mesh, and there is no other.
> 
> I'm at the stage where everything compiles, but the assembly is
> breaking (I know how to proceed though).
> 
> The plan is to use the new mesh in DOLFIN-KTH where we will work on a
> new refinement/coarsening strategy. When that has matured a bit, we
> can merge it back into the main DOLFIN branch.
> 
> You can view the work so far at the Mercurial repository:
> 
> static-http://www.nada.kth.se/~jjan/hg/dolfin-newmesh
> 
> (It takes forever to clone through static-http, it's better to clone
> from the main repository, then pull and do update -C)
> 
> Some minor changes are also needed for FFC, perhaps the simplest
> solution is to make a branch of that too.
> 
> When the transition starts working (sans refinement) it should appear
> in:
> 
> http://www.fenics.org/hg/dolfin-kth
> 
>   Johan
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev