[Dune] boundary projection (Marco Cisternino)

[Dedner, Andreas]

Hi Marco.

You seem to have 2 very different problems here. The serial case should work
and (without code) I have no idea why the problem occurs.

Parallel grid creation through the factory just does not work yet correctly as far
as I know. There is a (discussed but not solved) problem with the boundary
projections: the grid obtains an instance of an abstract class and then has to communicate
that to another process during load balancing so there has to be some way
of serializing the object and to recreate it on the new process. That is not yet
sorted out. Thats my understanding of the situation, 
but perhaps somebody else has a solution or a work around?

Best
Andreas
________________________________________
From: dune-bounces+a.s.dedner=warwick.ac.uk at dune-project.org [dune-bounces+a.s.dedner=warwick.ac.uk at dune-project.org] on behalf of Marco Cisternino [marco.cisternino at optimad.it]
Sent: 13 June 2012 18:24
To: dune at dune-project.org
Subject: Re: [Dune] boundary projection (Marco Cisternino)

Hi,
I'm debugging my code trying to insert Boundary Projection in parallel.
I'm doing it on a 3D ALUCubeGrid with 729 elements (9x9x9 elements)
Two issues:

Using just one proc:
during the insertion of boundary projection everything seems good; I
insert boundary projections for each element boundary face on just one
of the six sides of the grid, which means 81 faces; the factory shows me
(using a debugger and looking at the bndVec_ attribute of the grid) that
81 boundary faces are set to be projected; but when I create the grid
only a group of these faces (42) are really set for projection. Why??

Using two procs:
I declare the factory for every procs in the communicator and I insert
vertices, elements and boundaries using zero; everything works exactly
in the same way till the grid creation, with the same result, i.e. the
grid created on proc zero has the same projection problem I have with 1
proc; then I call the loadBalance method but on proc 1 the bndVec_ and
vertexProjection_ attributes, which are anyway incorrectly (42 in place
of 81!) set for proc zero, point to 0!!!

Am I doing something wrong?? I used for BoundaryProjection the same
logic I use for Vertices and Elements.
Any help will be really appreciated.

Thanks a lot.

Marco

_______________________________________________
Dune mailing list
Dune at dune-project.org
http://lists.dune-project.org/mailman/listinfo/dune