I'm currently testing a workaround for the solution array fill you mentioned below. Just as a general comment, from my point of view it would be great to have a convenience method that similar to VTKIOs write_equation_systems fills the _vtk_grid - variable with mesh and solution data and makes this pointer available instead of writing it out to a file. Maybe the developers could think about adding this kind of functionality in one of the next versions of libmesh. Thanks for all the helpful comments and hints regarding my initial question..
Am 27.02.2014 um 09:21 schrieb Antonio Cervone <[email protected]>: > this is working for me > > https://gist.github.com/capitalaslash/9246262 > > after making public a couple of functions and the _vtk_grid member. > in practice, what you need is a new method that sets up the vtk > structure, as it is done in the first part of > VTKIO::write_nodal_data(). > in order to restore all the methods and members to their original > intended privateness, that section should be extracted from that > method and made public. > i can prepare a pull request for this if the developers do agree on it. > > if you need to populate also solution arrays you need to look further > in the write_nodal_data() routine and modularize it in 3 parts: vtk > mesh creation, solution array fill and print out. > cheers, ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
