[Dune-devel] [GSoC2016] Proposal about the Python bindings for the DUNE grid interface

[Andreas Dedner]

Dear Michael.
Thanks for that. I had a look at the binding you wrote and they looked
good. For the final project the methods (or as many as possible) will
have to be wrapped, for the junior job just do as much as you have time
for. Getting a general idea for the code, adding test like you did and
some documentation is more important then wrapping as many methods as
possible. Or observation are right by the way, the template methods can
not be wrapped and that will present a bit of a challenge down the line
in this project.

Perhaps Martin will has some more things to say also w.r.t. to your
draft. I'll try to have a look at that tomorrow or on Tuesday morning.
Best
Andreas

On 18/03/16 04:47, Michaël Sghaïer wrote:
> Hi,
> 
> I just submitted my draft of a proposal about the Python bindings for
> the DUNE grid interface, through GSoC's official website!
> 
> You can add comments on my draft directly on Google Docs, I actually
> highlighted some points on which I would like to have some details and
> remarks.
> 
> I also have some questions that other students interested in the same
> project could have too:
> 
> - in the project description, you talk about "interface classes". What
> are specifically these "interface classes"? I assumed it was all the
> classes defined in dune-grid/dune/grid/identitygrid/ that represent the
> grid interface (and are needed in any new grid implementation), is that
> correct?
> 
> - you also talk about dune-fempy as a module which provides high level
> Python bindings to the dune-fem module but I didn't find it (nor by
> google nor by the gitlab). Is there any public git repository?
> 
> I am looking forward for your feedbacks.
> 
> Best,
> Michaël 
> 
> 
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune-devel
>