Cannot read MeshFunctions in parallel

Bug #420755 reported by Garth Wells
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DOLFIN
Fix Released
High
Skavhaug

Bug Description

Reading MeshFunctions from file fails when running in parallel. Without a rewrite of the XMLMeshFunction, where the mapping between the mesh entities and and the vertices is stored as part of the file format, only vertex and cell valued mesh functions can be used in parallel. Hence, we only address the cases of cell and vertex entities for now.

MeshFunctions over vertices and cells are now working. A nice error is issued when trying to read facets. Closing this bug now. What we need to do is store MeshFunctions in term of the vertices to file in order to reproduce the global numbering in parallel.

description: updated
Changed in dolfin:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Anders Logg (logg) wrote :

Testing notification from launchpad to dolfin-dev

Changed in dolfin:
assignee: nobody → logg (logg)
Changed in dolfin:
assignee: logg (logg) → Skavhaug (skavhaug)
Revision history for this message
Anders Logg (logg) wrote : Re: [Bug 420755] Re: Cannot read MeshFunctions in parallel

On Thu, Sep 03, 2009 at 08:52:50PM -0000, Garth Wells wrote:
> ** Changed in: dolfin
> Assignee: logg (logg) => Skavhaug (skavhaug)

Nice. :-)

--
Anders

Skavhaug (skavhaug)
Changed in dolfin:
status: Confirmed → In Progress
Anders Logg (logg)
Changed in dolfin:
milestone: none → 0.93
Skavhaug (skavhaug)
description: updated
Revision history for this message
Garth Wells (garth-wells) wrote :

Skavhaug wrote:
> ** Description changed:
>
> - Reading MeshFunctions from file fails when running in parallel
> + Reading MeshFunctions from file fails when running in parallel. Without
> + a rewrite of the XMLMeshFunction, where the mapping between the mesh
> + entities and and the vertices is stored as part of the file format, only
> + vertex and cell valued mesh functions can be used in parallel. Hence, we
> + only address the cases of cell and vertex entities for now.
>

The key to getting a number of demos running is to read facet
MeshFunctions. How much effort will a rewrite require?

Garth

Revision history for this message
Anders Logg (logg) wrote :

On Tue, Sep 08, 2009 at 06:38:40PM -0000, Garth Wells wrote:
>
> Skavhaug wrote:
> > ** Description changed:
> >
> > - Reading MeshFunctions from file fails when running in parallel
> > + Reading MeshFunctions from file fails when running in parallel. Without
> > + a rewrite of the XMLMeshFunction, where the mapping between the mesh
> > + entities and and the vertices is stored as part of the file format, only
> > + vertex and cell valued mesh functions can be used in parallel. Hence, we
> > + only address the cases of cell and vertex entities for now.
> >
>
> The key to getting a number of demos running is to read facet
> MeshFunctions. How much effort will a rewrite require?

Quite a bit I think. It involves changing the XML format. I suggest we
move this to 0.9.4 and add a function not_implemented_in_parallel that
we can put in some key places, like in parsing of MeshFunctions. Then
all demos that fail in parallel will give a sensible message about why
they are failing.

--
Anders

Skavhaug (skavhaug)
description: updated
Changed in dolfin:
status: In Progress → Fix Committed
Changed in dolfin:
status: Fix Committed → Fix Released
Anders Logg (logg)
Changed in dolfin:
status: Fix Released → Fix Committed
Anders Logg (logg)
Changed in dolfin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.