dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #10623
[HG DOLFIN] Move mesh.order() call in Stokes demo to after MeshFunction input. Results look good.
One or more new changesets pushed to the primary dolfin repository.
A short summary of the last three changesets is included below.
changeset: 5111:7c62552a138352c0a35ef8863898f18b85e827f3
tag: tip
user: "Garth N. Wells <gnw20@xxxxxxxxx>"
date: Tue Nov 04 22:34:33 2008 +0000
files: demo/pde/stokes/stabilized/cpp/main.cpp demo/pde/stokes/taylor-hood/cpp/main.cpp
description:
Move mesh.order() call in Stokes demo to after MeshFunction input. Results look good.
The use of mesh.order() is an issue with MeshFunctions. Any idea how to make it robust?
changeset: 5110:b0c23f3ea88431a7471d2546a73bd443f3abb2d8
user: "Garth N. Wells <gnw20@xxxxxxxxx>"
date: Tue Nov 04 22:26:57 2008 +0000
files: demo/pde/convection-diffusion/cpp/main.cpp demo/pde/stokes/taylor-hood/cpp/main.cpp
description:
Get convection-diffusion demo working (using a very nasty trick).
changeset: 5109:b68fe65f0aeda2b9997fe7713c9b6ceca9beb7eb
user: "Garth N. Wells <gnw20@xxxxxxxxx>"
date: Tue Nov 04 14:52:27 2008 +0000
files: demo/pde/convection-diffusion/cpp/main.cpp dolfin/function/Function.cpp dolfin/io/XMLFile.cpp
description:
Work on convection-diffusion demo.
We need to figure out what to do about the mesh for Functions read from a file. We have multiple instances of the 'same' mesh but FunctionSpace doesn't know this.
----------------------------------------------------------------------
For more details, visit http://www.fenics.org/hg/dolfin