[Dune] Question about Dune-alugrid license

[FOCHESATO Christophe 603260]

In the Grid-Manager Features page, it is indicated in the third table that ug grid is only supporting codimension 0 and dim entities and iterators. It may be a mistake in the table.

Anyway, I also tend to think it should be relatively easy to implement if needed.

Thanks,
Christophe

-----Message d'origine-----
De : Oliver Sander [mailto:oliver.sander at tu-dresden.de] 
Envoyé : mardi 15 décembre 2015 12:06
À : dune at dune-project.org; FOCHESATO Christophe 603260
Objet : Re: [Dune] Question about Dune-alugrid license

Salut Christophe,

> We saw that ug grid could be used but it does not match our needs for now since it does not provide codimension-1 entities.

what precisely do you mean by this?  UGGrid does provide codim-1 entities.  It does not provide iteration over these entities, but that should be relatively easy to implement if you really need it.

Best,
Oliver


> Our idea was the following: rely on Yaspgrid in a first  time, but we were hoping to keep the possibility to use an unstructured grid in the future, and so to minimize the dependence to Yaspgrid as much as possible if we can. We were thinking about alugrid for that.
> 
> I imagine this is still possible but there will be more work to do with ug grid since we would have to implement the missing functionalities, isn't it?
> 
> Christophe
> 
> -----Message d'origine-----
> De : dune-bounces+christophe.fochesato=cea.fr at dune-project.org 
> [mailto:dune-bounces+christophe.fochesato=cea.fr at dune-project.org] De 
> la part de Christoph Grüninger Envoyé : mardi 15 décembre 2015 10:10 À 
> : dune at dune-project.org Objet : Re: [Dune] Question about Dune-alugrid 
> license
> 
> Dear Christophe,
> licensing is such a nice topic. Everybody has an opinion. Myself included; I am not a lawyer.
> 
>> This will
>> prevent us for using this module if I understand well.
> 
> It strongly depends on what you want to do. You have to explain how you want to use Dune.
> 
> As far as I understood it:
> 1) You can do whatever you want, if you keep the software to yourself within your institute.
> 2) You can publish your codes under whatever licence you want.
> 3) You have to be careful, when you share binaries. This includes selling your software in a compiled version, offering binaries for download or packaging RPMs / DEB packages which includes binaries.
> 
> If you do not 3), you can ignore GPL/LGPL/GPL+runtime-exception 1/2/3/+.
> 
> As a consequence of 3) Debian has no alugrid package and openSuse's dune-grid package does not use the alugrid package.
> 
> So it depends on your use-case whether the differences in licensing are relevant for you. In my perception most academic users choose to do not distribute their code as binaries and are fine with that.
> 
> Bye
> Christoph
> 
> --
> Natürlich kann im Kapitalismus jeder reich werden.
> Aber doch nicht alle!            -- Volker Pispers
> 
> 
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
>