dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #20200
Re: [Branch ~dolfin-core/dolfin/main] Rev 5294: Renumber colors to start at zero and add check for contiguous coloring.
-
To:
DOLFIN Mailing List <dolfin@xxxxxxxxxxxxxxxxxxx>
-
From:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
Date:
Thu, 18 Nov 2010 11:36:05 +0000
-
In-reply-to:
<20101118110333.2360.60071.launchpad@loganberry.canonical.com>
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
On 18/11/10 11:03, noreply@xxxxxxxxxxxxx wrote:
------------------------------------------------------------
revno: 5294
committer: Anders Logg<logg@xxxxxxxxx>
branch nick: dolfin
timestamp: Thu 2010-11-18 12:00:07 +0100
message:
Renumber colors to start at zero and add check for contiguous coloring.
Something fails (segfault in coloring demo), will fix later.
I think that I've fixed the seg fault. It was related to code like
const MeshFunction<dolfin::uint>& colors_vertex = mesh.color("vertex");
const MeshFunction<dolfin::uint>& colors_edge = mesh.color("edge");
The function Mesh::color deletes the old data when asking for a new
colouring, which leave colors_vertex dangling. Could we re-use data, so
that the reference to colors_vertex remains valid? Or could we store
different colourings (vertex, edge, facet)?
Garth
modified:
dolfin/mesh/MeshColoring.cpp
--
lp:dolfin
https://code.launchpad.net/~dolfin-core/dolfin/main
Your team DOLFIN Core Team is subscribed to branch lp:dolfin.
To unsubscribe from this branch go to https://code.launchpad.net/~dolfin-core/dolfin/main/+edit-subscription
Follow ups