dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

Looks great.

Perhaps we could pick a common name for all visualization scripts that
we put in the demos?

We have used 'plotsolution.m' for many of the demos. Perhaps we could
use 'plotsolution.py' or 'visualize.m' for the Python demos? Or
something else, as long as we're consistent. I think it would be
helpful if a user can always expect to find a script for visualization
in each of the demo directories and know what to look for.

By the way, I get some errors when I try to generate the SWIG
interface. Something you recognize?

dolfin_wrap.cpp: In function ‘PyObject*
_wrap_new_PoissonSolver(PyObject*, PyObject*)’:
dolfin_wrap.cpp:36497: error: ‘PoissonSolver’ is not a member of
‘dolfin’
dolfin_wrap.cpp:36497: error: ‘result’ was not declared in this scope
dolfin_wrap.cpp:36529: error: ‘PoissonSolver’ is not a member of
‘dolfin’
dolfin_wrap.cpp:36529: error: expected primary-expression before ‘)’
token
dolfin_wrap.cpp:36529: error: expected `;' before ‘new’
dolfin_wrap.cpp: In function ‘PyObject*
_wrap_PoissonSolver_solve__SWIG_0(PyObject*, PyObject*)’:
dolfin_wrap.cpp:36543: error: ‘PoissonSolver’ is not a member of
‘dolfin’
dolfin_wrap.cpp:36543: error: ‘arg1’ was not declared in this scope
dolfin_wrap.cpp:36543: error: ‘PoissonSolver’ is not a member of
‘dolfin’
dolfin_wrap.cpp:36543: error: expected primary-expression before ‘)’
token
dolfin_wrap.cpp:36543: error: expected `;' before numeric constant
dolfin_wrap.cpp: In function ‘PyObject*
_wrap_PoissonSolver_solve__SWIG_1(PyObject*, PyObject*)’:
dolfin_wrap.cpp:36599: error: ‘dolfin::PoissonSolver’ has not been
declared
dolfin_wrap.cpp:36599: error: ‘solve’ was not declared in this scope

/Anders

On Tue, Nov 01, 2005 at 09:59:11PM +0100, dolfin@xxxxxxxxxx wrote:
> Commit from johanjan (2005-11-01 21:59 CET)
> --------------------
> 
> Heat:
> 
> Added new module "heat" as a demo and testbed for the PDE<->ODE solver
> interface. This also includes a Python script "visualize_heat.py"
> (requires Mayavi 1.4) for visualizing the solution on a mesh and a
> Python script "plot_heat.py" for plotting the solution as components
> over time (ODE-style).
> 
> Convdiff:
> 
> Added a Python script "visualize_convdiff.py" which does the same
> thing as above. Reduced the time step and total time to better be able
> to visualize the solution.
> 
>   dolfin  configure                                           1.225
>   dolfin  configure.ac                                        1.106
>   dolfin  src/demo/solvers/Makefile.am                        1.20
>   dolfin  src/demo/solvers/Makefile.in                        1.127
> + dolfin  src/demo/solvers/convdiff/visualize_convdiff.py     1.1
> + dolfin  src/demo/solvers/heat/Makefile                      1.3
> + dolfin  src/demo/solvers/heat/main.cpp                      1.6
> + dolfin  src/demo/solvers/heat/plot_heat.py                  1.1
> + dolfin  src/demo/solvers/heat/visualize_heat.py             1.1
>   dolfin  src/modules/Makefile.am                             1.29
>   dolfin  src/modules/Makefile.in                             1.134
>   dolfin  src/modules/convdiff/ConvectionDiffusionSolver.cpp  1.16
>   dolfin  src/modules/dolfin/dolfin_modules.h                 1.9
> + dolfin  src/modules/heat/HeatSolver.cpp                     1.8
> + dolfin  src/modules/heat/Makefile.am                        1.4
> + dolfin  src/modules/heat/Makefile.in                        1.34
> + dolfin  src/modules/heat/dolfin/Heat.form                   1.1
> + dolfin  src/modules/heat/dolfin/Heat.h                      1.1
> + dolfin  src/modules/heat/dolfin/HeatSolver.h                1.3
> + dolfin  src/modules/heat/dolfin/dolfin_heat.h               1.1
> 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/cgi-bin/mailman/listinfo/dolfin-dev
> 

-- 
Anders Logg
Research Assistant Professor
Toyota Technological Institute at Chicago
http://www.tti-c.org/logg/