← Back to team overview

dolfin team mailing list archive

Re: DOLFIN-stable

 

On Tue, Dec 05, 2006 at 05:17:45PM +0100, Garth N. Wells wrote:
> 
> 
> Johan Jansson wrote:
> > On Tue, Dec 05, 2006 at 04:20:53PM +0100, Garth N. Wells wrote:
> >> For the Navier-Stokes equations, the latter is preferable since there 
> >> are a truck load of possibilities, which holds for a lot of other 
> >> problems too.
> >>
> >> Let's start with
> >>
> >>    /src/modules/
> >>    /src/modules/solvers
> >>    /src/modules/demo
> >>
> >> Garth
> >>
> > 
> > I'd like to get rid of "solvers". Why not:
> > 
> > /src/modules/module1/
> > /src/modules/module1/demo
> > /src/modules/module2/
> > /src/modules/module2/demo
> > 
> > ?
> >
> 
> This looks a bit messy to me. I like it with demos, tests, benchmarks 
> grouped together.

Grouping demo, test and benchmark for all modules signals that
the modules somehow belong together.

By separating demo, test and benchmark for the modules from the
corresponding demo, test and benchmark for the kernel signals that the
modules are separate from the kernel. It also indicates that we could
move the modules to a separate tree. A consequence of not putting them
separate is that users are forced to download the modules even if they
don't want to build them.

If we put demo, test and benchmark inside each individual module, then
we would signal that each individual module could be put in a separate
tree and this is what we have objected to before.

So my suggestion would be to have common demo, test and benchmark for
all modules, and maybe at some point (when someone is willing to
maintain it) put them in a separate tree.

/Anders

> How are we going to reach consensus?
> 
> Garth
> 
> > The naming issue is the same, i.e. we would have:
> > 
> > /src/modules/navierstokes
> > 
> > instead of:
> > 
> > /src/modules/solvers/navierstokes
> > 
> >   Johan
> > 
> 
> 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev


Follow ups

References