dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Sun, Aug 27, 2006 at 09:39:34PM +0200, Ola Skavhaug wrote:
> Ola Skavhaug skrev den 25/08-2006 følgende:
> > Anders Logg skrev den 25/08-2006 følgende:
> > > On Fri, Aug 25, 2006 at 12:10:39PM +0200, Garth N. Wells wrote:
> > > > Does PyCC visualise without writing data to a file? This is what I would
> > > > like to be able to do. Does PyCC use the DOLFIN mesh library?
> > > 
> > > I think it writes VTK files.
> > 
> > PyCC can visualize without writing to file, if the user wishes. We utilize the
> > vtkVoidArray class for sending the contents of Numeric arrays directly to the
> > graphics card.  Additionally, plotter can write the frames to file as either
> > vtk files or png graphics.
> >  
> > > Yes, PyCC uses the DOLFIN mesh library, but I think the plotter.py script
> > > assumes a PyCC wrapper of the DOLFIN mesh. Probably, the extra wrapper layer
> > > can be removed when the new DOLFIN mesh is in place with proper Python
> > > bindinds.
> > 
> > Actually, the plotter does not depend on the DOLFIN mesh at all. We have a
> > seperate class MeshLister, that can be built from a DOLFIN mesh, that provides
> > the data needed in plotter to do runtime visualization in VTK.
> > 
> > Please, go ahead and use the code in DOLFIN if you want to. We can give you a
> > GPLed version of the file.
> 
> We can change the PyCC plotter license to open source. Can you live with LGPL?

Yes, in particular since I can change the license to GPL. :-)

Anyone is free to distribute an LGPL-licensed library under the
GPL. See section 3 of the LGPL:

    http://www.gnu.org/licenses/lgpl.html

Using GPL or LGPL is an interesting discussion, but I see four main
reasons for going with the GPL instead of the LGPL:

1. All the rest of the DOLFIN code is GPL and it's practical to have
the same license for all the code.

2. Using the LGPL is not safe; anyone can modify and relicense
LGPL-covered code under the GPL (like we may do with plotter.py) which
would prevent the modifications from being propagated back to the
original code. If I make changes under the GPL to plotter.py, you
wouldn't be able to benefit from these changes and so a main purpose
of open-sourcing plotter.py (getting benefit from user's
modifications) would be lost.

3. GPL better promotes free software than the LGPL.

4. I can't think of any example (for DOLFIN) where use of the GPL
would prevent something desirable that the LGPL would allow, which
would outweigh 1-3. But I may be missing something?

/Anders



> Ola
> 
> 
>  
> > Ola
> >  
> > > > There is also MayaVi2 on the way
> > > > (https://svn.enthought.com/enthought/wiki/MayaVi) which looks nicer than
> > > > the old MayaVi and apparently has an improved Pythin interface.
> > > >
> > > > Paraview 3 is under development and also looks at lot nicer (based on
> > > > QT) and will also have more Python support (www.vtk.org/Wiki/ParaView_III).
> > > 
> > > Both interfaces have a slightly old-fashioned feel to them (mainly
> > > because of the windowing toolkits they use). It will be nice to get
> > > hands on the new versions.
> > > 
> > > /Anders
> > >  
> > > > Garth
> > > > 
> > > > 
> > > > Anders Logg wrote:
> > > > > Ola Skavhaug has a very nice script called plotter.py (which is part
> > > > > of PyCC developed at Simula). The script does exactly this, run-time
> > > > > visualization of solutions during computations. The script works
> > > > > directly through VTK and not through Mayavi.
> > > > > 
> > > > > PyCC is not yet free software, but perhaps plotter.py could be. What
> > > > > does Ola say? Could you put a GPL license on it?
> > > > > 
> > > > > /Anders
> > > > > 
> > > > > 
> > > > > On Thu, Aug 24, 2006 at 08:13:22PM +0200, Garth N. Wells wrote:
> > > > >> mayavi looks like it could be really neat in combination with pyDOLFIN.
> > > > >> Could we pipe data directly from DOLFIN to mayavi? This would be useful
> > > > >> for sending output to the screen during lengthy nonlinear and/or time
> > > > >> dependent problems.
> > > > >>
> > > > >> Garth
> > > > >>
> > > > >>
> > > > >> DOLFIN wrote:
> > > > >>> One or more new changesets pushed to the primary DOLFIN repository.
> > > > >>> A short summary of the last three changesets is included below.
> > > > >>>
> > > > >>> changeset:   2177:3b375f83976a8a2734695060fc2a38821e7d643e
> > > > >>> tag:         tip
> > > > >>> user:        "Garth N. Wells <g.n.wells@xxxxxxxxxx>"
> > > > >>> date:        Thu Aug 24 20:07:52 2006 +0200
> > > > >>> files:       src/bench/la/sparse-matrix/main.cpp src/demo/pde/elasticity/plot.py
> > > > >>> description:
> > > > >>> Fix plot script for Poisson demo.
> > > > >>>
> > > > >>>
> > > > >>> changeset:   2176:dcfe4e70e157edfc1b124939e50f34c7a7d44e59
> > > > >>> user:        "Anders Logg <logg@xxxxxxxxx>"
> > > > >>> date:        Thu Aug 24 19:58:42 2006 +0200
> > > > >>> files:       src/demo/pde/poisson/main.cpp
> > > > >>> description:
> > > > >>> Restore original right-hand side in Poisson demo.
> > > > >>>
> > > > >>>
> > > > >>> changeset:   2175:866f7f5da06feac81188e9028e8b845787f8a7f7
> > > > >>> user:        "Anders Logg <logg@xxxxxxxxx>"
> > > > >>> date:        Thu Aug 24 19:26:22 2006 +0200
> > > > >>> files:       AUTHORS README configure.ac src/config/Makefile.am src/config/Makefile.in src/pydolfin/dolfin.py src/pydolfin/dolfin_wrap.cpp src/pydolfin/dolfin_wrap.h
> > > > >>> description:
> > > > >>> Misc cleanups:
> > > > >>>
> > > > >>> - Fix annoyingly long CFLAGS in dolfin-config. Now, dolfin-config --cflags
> > > > >>>   returns something like
> > > > >>>
> > > > >>>    -I/usr/local/include -g -O2 -DNDEBUG -pedantic -Wno-long-long -std=c++98
> > > > >>>
> > > > >>>   rather than
> > > > >>>
> > > > >>>    -I/usr/local/include -I../../src/kernel/common -I../../src/kernel/fem -I../../src/kernel/form -I../../src/kernel/function -I../../src/kernel/io -I../../src/kernel/la -I../../src/kernel/main -I../../src/kernel/math -I../../src/kernel/mesh -I../../src/kernel/mf -I../../src/kernel/nls -I../../src/kernel/ode -I../../src/kernel/pde -I../../src/kernel/quadrature -I../../src/kernel/parameter -I../../src/kernel/log -DHAVE_PETSC_H=1 -I/usr/local/lib/petsc/ -I/usr/local/lib/petsc//bmake/linux-gnu-cxx-real-debug -I/usr/local/lib/petsc//include -I/usr/local/lib/petsc/externalpackages/mpich2-1.0.3/linux-gnu-cxx-real-debug/include -I/usr/include/libxml2 -I../../src/modules/elasticity -I../../src/modules/elasticity-updated -I../../src/modules/convdiff -I../../src/modules/navierstokes -I../../src/modules/poisson -I../../src/modules/stokes -I../../src/modules/heat -I../../src/kernel/common -I../../src/kernel/fem -I../../src/kernel/form -I../../src/kernel/function -I../../src/kernel/io 
> > > > 
> > > > >  -I
> > > > >> ..
> > > > >>>  /../src/kernel/la -I../../src/kernel/main -I../../src/kernel/math -I../../src/kernel/mesh -I../../src/kernel/mf -I../../src/kernel/nls -I../../src/kernel/ode -I../../src/kernel/pde -I../../src/kernel/quadrature -I../../src/kernel/parameter -I../../src/kernel/log -DHAVE_PETSC_H=1 -I/usr/local/lib/petsc/ -I/usr/local/lib/petsc//bmake/linux-gnu-cxx-real-debug -I/usr/local/lib/petsc//include -I/usr/local/lib/petsc/externalpackages/mpich2-1.0.3/linux-gnu-cxx-real-debug/include -I/usr/include/libxml2 -I../../src/modules/ -g -O2 -DNDEBUG -pedantic -Wno-long-long -std=c++98
> > > > >>>
> > > > >>> - Update AUTHORS and README
> > > > >>>
> > > > >>>
> > > > >>> -------------------------------------------------------
> > > > >>> For more details, visit http://www.fenics.org/hg/dolfin
> > > > >>> _______________________________________________
> > > > >>> DOLFIN-dev mailing list
> > > > >>> DOLFIN-dev@xxxxxxxxxx
> > > > >>> http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > > >>>
> > > > > _______________________________________________
> > > > > DOLFIN-dev mailing list
> > > > > DOLFIN-dev@xxxxxxxxxx
> > > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > > > 
> > > > _______________________________________________
> > > > DOLFIN-dev mailing list
> > > > DOLFIN-dev@xxxxxxxxxx
> > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > 
> > _______________________________________________
> > DOLFIN-dev mailing list
> > DOLFIN-dev@xxxxxxxxxx
> > http://www.fenics.org/mailman/listinfo/dolfin-dev
>