← Back to team overview

dolfin team mailing list archive

Re: plotting in all stokes demos fails (DOLFIN 1.0.x)

 

You have a viper incompatibility. The latest viper will not work with
DOLFIN 1.0.

Garth

On 24 May 2012 10:25, Andre Massing <massing@xxxxxxxxx> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi!
>
> When I try to execute the stokes python examples in
> demo/stokes-iterative or undocumented/stokes*
>
> the plotting routine always fails with (here for the taylor-hood example)
>
> Traceback (most recent call last):
>  File "demo_stokes-taylor-hood.py", line 83, in <module>
>    plot(u)
>  File
> "/home/andre/Work/software/FEniCS/install/stable/dolfin/release/lib/python2.7/site-packages/dolfin/common/plotting.py",
> line 121, in dolfin_plot
>    return viper_dolfin.plot(make_viper_object(object, mesh=mesh),
> *args, **kwargs)
>  File
> "/home/andre/Work/software/FEniCS/install/stable/lib/python2.7/site-packages/viper/viper_dolfin.py",
> line 471, in plot
>    fig = _plotter.plot(data, **kwargs)
>  File
> "/home/andre/Work/software/FEniCS/install/stable/lib/python2.7/site-packages/viper/viper_dolfin.py",
> line 413, in plot
>    return self.autoplot(plot_object, *args, **kwargs)
>  File
> "/home/andre/Work/software/FEniCS/install/stable/lib/python2.7/site-packages/viper/viper_dolfin.py",
> line 432, in autoplot
>    plotter = Viper(plot_object, *args, **kwargs)
>  File
> "/home/andre/Work/software/FEniCS/install/stable/lib/python2.7/site-packages/viper/viper_dolfin.py",
> line 65, in __init__
>    self.plot(data, *args, **kwargs)
>  File
> "/home/andre/Work/software/FEniCS/install/stable/lib/python2.7/site-packages/viper/viper_dolfin.py",
> line 90, in plot
>    plot_method(data, *args, **kwargs)
>  File
> "/home/andre/Work/software/FEniCS/install/stable/lib/python2.7/site-packages/viper/viper_dolfin.py",
> line 138, in plot_genericfunction
>    self.x = data.compute_vertex_values(self.mesh)
> TypeError: compute_vertex_values() takes exactly 3 arguments (2 given)
>
> Is that just me or is that a known bug?
>
> - --
> Andre
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJPvf6AAAoJEA79ggnbq9dmG0sH/jncgRHvRbEif3mR17YPN7CS
> +bRkzoXc3qsGQktLcdI/DatKUOnuK3qLP881FbA8a+pmicM7qMnVFbHbmPr86CHZ
> 6/4cZPZ95roT1JWNM9OwirNY6yDhgRcq7uDW3IEQ6Y028Vuk5AFJm6/NAMHHSa8i
> Bbd+V1O+ksBlDoen5wQswZfAlthHj4HD+nBg3uVjEJJbvNEgQJNjHszkPx44b49f
> 26xTBP99Hw0fW0zJtFe7xT0wZaMG6lFjeu51ebzxUe9R0gmFZKtpf2KacNsA+ALe
> m1XluGKFIMQlExAk/Fc5ZxoBamQPcY171tSvd7HQNt52700mSGtP+zO3tIn1g34=
> =E4jU
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help   : https://help.launchpad.net/ListHelp


Follow ups

References