dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #05050
Re: [HG dolfin] merge.
On Wed, May 30, 2007 at 05:20:41PM +0200, DOLFIN wrote:
> One or more new changesets pushed to the primary DOLFIN repository.
> A short summary of the last three changesets is included below.
>
> changeset: 3174:3d1ad43bb4b43f156f8f2c1c9396f48738047b44
> tag: tip
> parent: 3173:9eb93291f2ca7929641ad6627ec7e677f8dd08df
> parent: 3172:875335d58397e6d45415eb28ac9755c670114b57
> user: "Garth N. Wells <g.n.wells@xxxxxxxxxx>"
> date: Wed May 30 17:20:25 2007 +0200
> files: src/demo/plot/cpp/cow.xml.gz src/demo/plot/python/cow.xml.gz
> description:
> merge.
>
>
> changeset: 3173:9eb93291f2ca7929641ad6627ec7e677f8dd08df
> parent: 3166:731dab85580fffe60a46f6c5d5ccfdbeee6ba422
> user: "Garth N. Wells <g.n.wells@xxxxxxxxxx>"
> date: Wed May 30 17:19:34 2007 +0200
> files: src/kernel/mesh/Makefile.am src/kernel/mesh/Makefile.in src/kernel/mesh/dolfin/Makefile.am src/kernel/mesh/dolfin/Makefile.in src/kernel/mesh/dolfin/dolfin_mesh.h
> description:
> Add class MPIMeshCommunicator.
>
> This class will handle the transfer of meshes and MeshFuntions between processes. It doesn't do anything yet.
Did you forget to add it?
Also, would it be practical to collect the parallell stuff in a
separate sub directory? Some suggestions:
src/kernel/para
src/kernel/mpi
/Anders
> changeset: 3172:875335d58397e6d45415eb28ac9755c670114b57
> user: "Anders Logg <logg@xxxxxxxxx>"
> date: Wed May 30 16:58:16 2007 +0200
> files: src/demo/plot/cpp/cow.xml.gz src/demo/plot/cpp/dolfin-2.xml.gz src/demo/plot/cpp/main.cpp src/demo/plot/python/cow.xml.gz src/demo/plot/python/demo.py src/demo/plot/python/dolfin-2.xml.gz
> description:
> Add something a little more interesting for Python plotting demo.
> Will look nice when get this to work with continuous plotting in Viper.
>
>
> ----------------------------------------------------------------------
> For more details, visit http://www.fenics.org/hg/dolfin
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev
Follow ups
References