← Back to team overview

dolfin team mailing list archive

Re: [HG DOLFIN] merge

 

On Sunday 14 December 2008 22:42:44 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:   5342:80da9660bd6639498aee34b430340877a017b08d
> tag:         tip
> parent:      5341:b69b68ceb0b70ec4c387c8bdf7c0a94164e07e98
> parent:      5340:8e01a163726d6ddc2d72382bf1e5ec1d4b86522c
> user:        "Johan Hake <hake@xxxxxxxxx>"
> date:        Sun Dec 14 22:42:41 2008 +0100
> files:       TODO
> description:
> merge
>
>
> changeset:   5341:b69b68ceb0b70ec4c387c8bdf7c0a94164e07e98
> parent:      5335:11eae42fc1852b3b0aca0d247ed0d2f003b05201
> user:        "Johan Hake <hake@xxxxxxxxx>"
> date:        Sun Dec 14 22:41:08 2008 +0100
> files:       TODO demo/pde/periodic/python/demo.py
> dolfin/swig/dolfin_mesh_pre.i dolfin/swig/typemaps.i
> site-packages/dolfin/compile_function.py description:
> Fixed periodic python demo.
>   - Added a director typemap for "double *y" in map

In addition to fix the typemap I also had to change

  bc0 = DirichletBC(V, u0, DirichletBoundary())

to

  dbc = DirichletBoundary()
  bc0 = DirichletBC(V, u0, dbc)

This is probably not obvious but a quite common error related to swig 
generated python classes. 

The DirichletBoundary subdomain get garbage collected killing its C++ 
equivalent. We therefore have to keep a reference in the demo, which prevents 
this.

Johan


> Fixed function eval python demo
>   - import_array() was not called in the interface file
>
>
> changeset:   5340:8e01a163726d6ddc2d72382bf1e5ec1d4b86522c
> user:        "Kristian Oelgaard <k.b.oelgaard@xxxxxxxxxx>"
> date:        Sat Dec 13 16:10:43 2008 +0000
> files:       TODO demo/pde/adaptive-poisson/python/demo.py
> description:
> Attempt at fixing pde/adaptive demo, received segmentation fault.
>
> ----------------------------------------------------------------------
> 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