← Back to team overview

dolfin team mailing list archive

Re: Parallel MeshFunction IO

 

On Tuesday September 20 2011 08:45:01 Garth N. Wells wrote:
> On 20 September 2011 16:37, Johan Hake <johan.hake@xxxxxxxxx> wrote:
> > Ok, sounds promising!
> > 
> > Just to get it straight:
> > 
> >  1) The old MeshFunction file format will not be supported in parallel
> 
> Even better - your old file won't work in serial! The MeshFunction
> output is flawed (for edges and faces) because the edge and facet
> numbering is not specified by the mesh file. Edge and face numbering
> is determined by the library that constructs a mesh. The new format
> will be the same in serial and parallel.

Well, if you use the library (DOLFIN) to generate your MeshFunction you are 
safe. 

> >  2) To read a MeshFunction from file in parallel I need to convert
> >     all my MeshFunctions to MeshValueCollections and store them. Then I
> > use that file to initiate a MeshFunction in parallel?
> 
> I'll add something so if you read and old-style MeshFunction, and then
> write it to file, it will be written in the new  format.

So the file format of MeshValueCollection and MeshFunction will now be the 
same?

Johan

> Garth
> 
> > Doable!
> > 
> > Johan
> > 
> > On Tuesday September 20 2011 01:17:25 Garth N. Wells wrote:
> >> On 20 September 2011 07:10, Anders Logg <logg@xxxxxxxxx> wrote:
> >> > MeshFunctions? I think MeshValueCollection works but not yet
> >> > MeshFunctions.
> >> > 
> >> > My suggestion is to either store MeshFunctions as
> >> > MeshValueCollections:
> >> > 
> >> >  <mesh_function>
> >> >    <mesh_value_collection>
> >> >    </mesh_value_collection>
> >> >  </mesh_function>
> >> > 
> >> > (when dim is not 0 or D) or to say that parallel I/O for MeshFunction
> >> > is not supported and make the conversion between MeshFunction and
> >> > MeshValueCollection easy (constructors).
> >> 
> >> I think that the suggestion to store MeshFunctions as
> >> MeshValueCollections is the best solution. To keep it simple, I would
> >> use MeshValueCollection for entities of any dimension with a tweak of
> >> the tags for vertices.
> >> 
> >> The tools are in place to read MeshValueCollections from a separate
> >> file. Just a few small additions are required to make it
> >> work (right now the domain data needs to be in the mesh file). Once
> >> this is in place reading MeshFunctions should be easy. I'll add the
> >> code today.
> >> 
> >> Garth
> >> 
> >> > --
> >> > Anders
> >> > 
> >> > On Tue, Sep 20, 2011 at 07:58:31AM +0200, Kent-Andre Mardal wrote:
> >> >> It seems to work now!
> >> >> 
> >> >> Kent
> >> >> 
> >> >> On 20 September 2011 01:06, Johan Hake <johan.hake@xxxxxxxxx> wrote:
> >> >>      How far are we from a functional reading of MeshFunctions in
> >> >>      parallel?
> >> >> 
> >> >>      Johan
> >> >> 
> >> >>      _______________________________________________
> >> >>      Mailing list: https://launchpad.net/~dolfin
> >> >>      Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> >> >>      Unsubscribe : https://launchpad.net/~dolfin
> >> >>      More help   : https://help.launchpad.net/ListHelp
> >> >> 
> >> >> 
> >> >> _______________________________________________
> >> >> Mailing list: https://launchpad.net/~dolfin
> >> >> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> >> >> Unsubscribe : https://launchpad.net/~dolfin
> >> >> More help   : https://help.launchpad.net/ListHelp
> >> > 
> >> > _______________________________________________
> >> > Mailing list: https://launchpad.net/~dolfin
> >> > Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> >> > Unsubscribe : https://launchpad.net/~dolfin
> >> > More help   : https://help.launchpad.net/ListHelp
> >> 
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~dolfin
> >> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~dolfin
> >> More help   : https://help.launchpad.net/ListHelp


Follow ups

References