[EMAIL PROTECTED] wrote:
>> One or more new changesets pushed to the primary dolfin repository.
>> A short summary of the last three changesets is included below.
>>
>> changeset:   4730:6548c25c33352492c9279c035509a139caab323b
>> tag:         tip
>> user:        "Garth N. Wells <[EMAIL PROTECTED]>"
>> date:        Tue Sep 09 13:08:58 2008 +0100
>> files:       dolfin/fem/Assembler.cpp dolfin/pde/LinearPDE.cpp
>> description:
>> Revert to old assembly in LinearPDE due to bug in symmetric assembly.
>>
>> There is a problem with exterior facets in the symmetric assembly. The
>> code needs to be broken up to make debugging easier.
>>
> 
> Agree that it should be broken up. But it will take some effort.
> Do you have an example where the bug is apparent ?
>

I was using a RT0 element (not one of the demos).  It should be 
reproducible by adding a non-zero Dirichlet bc (given be a Function) to 
the mixed-poisson demo.

I had a quick look, but I couldn't find the problem, so I thought it 
better to wait until the code is broken up.

Garth


> Kent
> 
> 
>> changeset:   4729:a84cf2b5cda6170367b30e1c6bcffa00bc4f36d1
>> parent:      4727:04152c9160962363af3a996773ced092caed339d
>> parent:      4728:a5ad46cb91f08dac998bd2a506f6c7e6aa4d0da1
>> user:        Anders Logg <[EMAIL PROTECTED]>
>> date:        Mon Sep 08 00:03:12 2008 +0200
>> files:
>> description:
>> Merge patch from Shawn Walker
>>
>>
>> changeset:   4728:a5ad46cb91f08dac998bd2a506f6c7e6aa4d0da1
>> parent:      4703:0e3198c7a287f5d7e8604f0f26fa8cc958fbc5b4
>> user:        Shawn Walker <[EMAIL PROTECTED]>
>> date:        Wed Sep 03 10:56:23 2008 -0400
>> files:       dolfin/function/DiscreteFunction.h
>> dolfin/function/Function.cpp dolfin/function/Function.h
>> dolfin/io/XMLMesh.cpp dolfin/io/XMLMesh.h dolfin/io/XMLObject.cpp
>> dolfin/io/XMLObject.h dolfin/io/XMLVector.h dolfin/mesh/MeshEditor.cpp
>> dolfin/mesh/MeshEditor.h dolfin/mesh/MeshGeometry.cpp
>> dolfin/mesh/MeshGeometry.h
>> description:
>> This patch adds in support for reading in an additional 'coordinates' tag
>> in the mesh.xml file, and uses this information to create a Function*
>> called mesh_coordinates that is contained in the MeshGeometry class.  This
>> function stores higher order mesh coordinate data that comes from assuming
>> the mesh elements are mapped using a finite element function higher order
>> than linear.  Another boolean array is created inside MeshGeometry that
>> indicates which elements are ACTUALLY curved, and which are just straight
>> (standard).  This is completely backwards compatible with previous mesh
>> formats.
>>
>> ----------------------------------------------------------------------
>> For more details, visit http://www.fenics.org/hg/dolfin
>> _______________________________________________
>> DOLFIN-dev mailing list
>> [email protected]
>> http://www.fenics.org/mailman/listinfo/dolfin-dev
>>
> 
> 
> _______________________________________________
> DOLFIN-dev mailing list
> [email protected]
> http://www.fenics.org/mailman/listinfo/dolfin-dev


_______________________________________________
DOLFIN-dev mailing list
[email protected]
http://www.fenics.org/mailman/listinfo/dolfin-dev

Reply via email to