On Tue, May 03, 2011 at 11:31:22AM -0000, Garth Wells wrote:
> This works 'properly' via a VTK file, whereas Viper performs an
> interpolation which makes the output impossible to properly interpret at
> boundaries where the MeshFunction value changes. Since it is supported
> via VTK, the easiest 'fix' would be to disable plotting of MeshFunctions
> via Viper.
I don't think that's a good fix. I would prefer if plotting
MeshFunctions on facets would issue a warning.
On Tue, May 03, 2011 at 11:31:22AM -0000, Garth Wells wrote:
> This works 'properly' via a VTK file, whereas Viper performs an
> interpolation which makes the output impossible to properly interpret at
> boundaries where the MeshFunction value changes. Since it is supported
> via VTK, the easiest 'fix' would be to disable plotting of MeshFunctions
> via Viper.
I don't think that's a good fix. I would prefer if plotting
MeshFunctions on facets would issue a warning.
--
Anders