#676 SubsamplingVTKWriter.addVertexData for std::vector shows unexpected result
Metadata
| Property | Value |
|---|---|
| Reported by | Andreas Dedner (A.S.Dedner@warwick.ac.uk) |
| Reported at | Dec 1, 2009 16:33 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Last edited at | Mar 9, 2015 16:47 |
| Closed by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Closed at | Mar 9, 2015 16:47 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment | Removing the addVertexData method fixes the issue. The implementation of P1VTKFunction is still wrong, but nobody should ever notice. Better subsampling support is coming to dune-functions. |
Description
When calling addVertexData using a std::vector like container on the SubsamplingVTKWriter one would expect to get the same result as when calling the method without sub sampling. Instead a ''piecwise'' constant function on the dual cells is generated - at least for sub sampling -> infinity. Test: dgfparser/test/tester with examplegrid2e.dgf (change VTKWriter to SubsamplingVTKWriter in main.cc)
