dolfin team mailing list archive

["Garth N. Wells" <gnw20@xxxxxxxxx>]

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:   6970:5d7fc35d3e597db508a005826efacb8dea6a00d9
> tag:         tip
> user:        Anders Logg <logg@xxxxxxxxx>
> date:        Tue Sep 08 00:50:08 2009 +0200
> files:       dolfin/parameter/GlobalParameters.h dolfin/plot/plot.cpp
> description:
> Work on parallel plotting from C++. Not yet working. Getting errors like
> [[10904,1],1] routed:binomial: Connection to lifeline [[10904,0],0] lost

I don't see working in this direction on plotting as being very 
profitable. We've spent effort on getting VTK output working in 
parallel, so why not just tell Viper to load the .pvtk file?

Also, plotting works from Python in parallel in the sense that things 
pop up on the screen, but it doesn't really work because one only gets a 
plot for each process with it's part of the domain. Working through the 
.pvtk file would solve this too.

Garth

> changeset:   6969:6f8c8a4229dd2a4901a91e8cc16972e198d7879d
> user:        "Johan Hake <hake@xxxxxxxxx>"
> date:        Mon Sep 07 21:32:34 2009 +0200
> files:       dolfin/swig/typemaps.i
> description:
> Removed outcommented code
>
>
> changeset:   6968:c9e4a19d28149a2e909e39abed118977afd3706c
> user:        "Johan Hake <hake@xxxxxxxxx>"
> date:        Mon Sep 07 21:31:43 2009 +0200
> files:       demo/la/block-matrix/cpp/main.cpp demo/la/block-matrix/python/demo.py demo/pde/elasticity/cpp/main.cpp demo/pde/stokes/taylor-hood/python/demo.py dolfin/la/EpetraMatrix.h dolfin/la/EpetraVector.h dolfin/la/GenericMatrix.h dolfin/la/GenericVector.h dolfin/la/MTL4Matrix.h dolfin/la/MTL4Vector.h dolfin/la/Matrix.h dolfin/la/PETScVector.cpp dolfin/la/PETScVector.h dolfin/la/STLMatrix.h dolfin/la/Vector.h dolfin/la/uBLASMatrix.h dolfin/la/uBLASVector.h
> description:
> Remove default argument to Foo.norm()
>   - Making PETScMatrix and Vector available in PyDOLFIN again
>
> ----------------------------------------------------------------------
> 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