[Dune-devel] YaspGrid project status update

[Dominic Kempf]

Dear Dune developers,

I want to inform you that I am working on the next phase of the
YaspGrid overhaul - the entities of arbitrary codimension.

You find the latest version of my work in the branch
p/dominic/all-entities-yaspgrid on dune-project.

A first step has been taken, where the fundamental structure of a
ygridlevel has been given generic data structures (see
http://cgit.dune-project.org/repositories/dune-grid/commit/?h=p/dominic/all-entities-yaspgrid&id=430b7ec8cd875b284b660aa8d4579eb87631ef4e)
The next steps will be about step by step replacing specialized
implementations with their generic counterparts (without tackling the
actual entities by now).

I am open to any suggestions you have on the project and will be at
the developer meeting in Berlin in september, too.

Best,
Dominic

On Fri, Jul 11, 2014 at 5:32 PM, Oliver Sander
<sander at igpm.rwth-aachen.de> wrote:
> Hi Dominic,
> many thanks for the tensor-product stuff.  I had a quick look, and it seems
> good to me.  I am all for merging it to master.
> Cheers,
> Oliver
>
> Am 09.07.2014 15:33, schrieb Dominic Kempf:
>> Dear Dune community,
>>
>> I am back at working on YaspGrid and would like to share the current
>> project status and plan with you.
>>
>> The tensorproduct feature is fully implemented. It will be merged into
>> master within the following days if nobody objects. You find the code
>> on my branch feature/yaspgrid-tensorproduct (on the dune-project
>> server). Some Remarks:
>> - Yasp now handles coordinates through a coordinate container
>> (technically this is a policy for storing and handling coordinates) -
>> which now is its second template parameter. It is defaulted to
>> EquidistantCoordinateContainer (see dune/grid/yaspgrid/coordinates.hh)
>> which makes this change fully backwards compatible.
>> - Tensorproduct grids can be used via the container
>> TensorproductCoordinateContainer. A Dune::array<std::vector<ctype>> is
>> used for coordinates.
>> - The YaspGrid class offers constructors to allow the construction of
>> a grid without explicitly constructing the coordinate container.
>> - The "backend file" dune/grid/yaspgrid/grids.hh is deleted. Its
>> content is instead split into several files: torus.hh contains the
>> communication infrastructure, ygrid.hh contains the definition of a
>> Ygrid - the cornerstone of yasps implementation of a structured grid.
>> ygrid.hh also got a lot of cleanup like the removal of an entire layer
>> of dynamic polymorphism and documentation was added.
>> - If you ever fancy to do so, you can change Yasps ctype by changing
>> the template parameter of the coordinate container.
>>
>> While this is an important step for YaspGrid, its not the end. As
>> talked about on the Dune developer meeting in Aachen, Yasp will get
>> entities of all codimensions and communication on these. I will start
>> working on that now. Although this will result in a lot more changes,
>> we decided to merge the tensorproduct feature now, since its been a
>> long waiting period since the first announcement of the feature.
>> Additionally, a clean cut will make development easier for the second
>> project.
>>
>> I look forward to all your test reports and feedbacks,
>> Dominic
>>
>> _______________________________________________
>> Dune-devel mailing list
>> Dune-devel at dune-project.org
>> http://lists.dune-project.org/mailman/listinfo/dune-devel
>>
>
>
>
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel
>