octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: blog update #2


From: Marco Vassallo
Subject: RE: blog update #2
Date: Fri, 14 Jun 2013 12:31:34 +0200


> Subject: Re: blog update #2
> From: address@hidden
> Date: Fri, 14 Jun 2013 12:07:31 +0200
> CC: address@hidden
> To: address@hidden
>
>
> On 14 Jun 2013, at 11:20, c. <address@hidden> wrote:
>
> > Indeed by browsing the python source for the xml_writer I see that the dolfin format supports a field named "domains"
> > which sounds as it could possibly do what you need.
>
> This 3D maesh: http://fenicsproject.org/pub/data/meshes/aneurysm.xml.gz
> from the dolfin examples page: http://fenicsproject.org/download/data.html#data
>
> includes boundary markers.
> c.

Hi, I asked some days ago to Fenics mainteiners if:

" When I read a function from a .xml file, is there any way in which I
can know if something like boundary_markers, sub-domains, colours had been
defined on the mesh??
>
> We do not store a MeshFunction in the mesh anymore. Instead we store
> MeshDomains with MeshValueCollections. These only store values for
> entities which has a boundary value. In a MeshValueCollection are the
> mesh entity stored using the cell number and the local mesh-entity
> number. This interface has also seen some recent changes in the
> development version and it has not fully stabilized.
>
> You can check if a mesh has MeshDomains by:
>
> mesh.domains().is_empty()


"

This is what we should do? Check if the Mesh has some useful information
and eventually store them in our format?

Marco

reply via email to

[Prev in Thread] Current Thread [Next in Thread]