RE: blog update #2

[Marco Vassallo]

---

From: address@hidden
To: address@hidden
Subject: RE: blog update #2
Date: Tue, 18 Jun 2013 14:19:28 +0200
CC: address@hidden

> Subject: Re: blog update #2

> From: address@hidden
> Date: Tue, 18 Jun 2013 13:37:32 +0200
> CC: address@hidden
> To: address@hidden
>
>
> On 18 Jun 2013, at 13:23, Marco Vassallo <address@hidden> wrote:
> >
> >
> > I have a question about the (p,e,t) format, which seems to have a little differences between the
> > 2D and the 3D case for the "e" matrix:
> >
> > 2D: information about the number of the border is stored in the 5th row on 7.[1]
> > 3D: the same information is stored in the last row.[2]
> >
> > Is this right ?
>
> it really seems so from the documentation …
> but indeed this looks inconsistent, to double check you could look at the source code of
>
> bim3c_unknowns_on_faces
>
> and
>
> bim2c_unknowns_on_side
>
> which sure work correctly to see whether it is a documentation bug.

Hi,

thanks for the modifications you have made to the code.

I've some problem while compiling mshm_dolfin_write.cc:

mshm_dolfin_write.cc:47:38: error: ‘octave_map::const_iterator’ has no member named ‘matrix_value’

and I don't see why it is not working.

I'm testing the "mshm_dolfn_read" and "mshm_dolfin_write" functions after having added the treatment of the boundary cells/sides and I'll add them to the repository very soon.

About the mshm_dolfin_write I have some enormous "if" statement but at the moment I don't see any other possibilities.

For the mshm_dolfin_refine I've some problem while recovering the information from the refined mesh and so I'm now investigating better dolfin, which will be also useful for writing the blog post about boundaries.

Marco