From: Roy S. <roy...@ic...> - 2011-02-28 23:21:24
|
On Thu, 24 Feb 2011, Roman Vetter wrote: >>> There is a third possibility, which is a compromise: >>> In the case of higher order variables, one could write each component >>> separately as scalar variables, perhaps with a suffix in the name >>> denoting the component. This way, all information is written, while >>> Paraview will still be able to recognize the first order solution as >>> scalars and display it as it does currently. >> >> [...] This actually sounds like a decent improvement, if it >> works for you. [...] > > I have implemented this, and it works fine with Paraview. Would you > like me to supply the patch so you (guys) can see what it actually > looks like? Not speaking for Derek, but for me the answer is definitely "yes"! > Getting back to the original motivation for this discussion: > Parallelism in VTK output. I have attached a patch which fixes the > issue for me. There are certainly many ways of doing it, mine attempts > to somewhat minimize the amount of modifications of the current code. > Essentially, the solution vectors are localized to one. This definitely looks like an improvement over the current code. Seems to work on my initial tests, too; I'll commit it to svn. Works on the initial tests where it's expected to work, anyway. Does the newest VTK support triquadratic hexes yet? vtk_io.C seems to think that VTK_BIQUADRATIC_QUAD is relatively new, and it would be nice if we didn't have to die with an error in the 3D case. --- Roy |