I faced some weeks ago essentially the same problem. I can just
recommend you to write separate files for each grid (if somehow
possible), it will save you a lot of trouble in many perspectives.
-Armin
P.S.: With ParaView state files you can still "load" several files, i.e.
grids, at the same time - a very handy feature. ;)
On 06/25/2014 08:20 PM, Truman Ellis wrote:
I essentially have two grids with different solution variables defined
on each one. I am using the XDMF format to output the data. When I
create a spatial collection of the two grids, the solution variables
show up as "partial" data in Paraview. Say solution variable u lives on
grid 1 while f lives on grid 2. If I color by u, grid 2 shows up as some
solid color that doesn't go away unless I turn off the block that
corresponds to grid 2. And vice versa for f.
I read that XDMF supports multiple domains, which sounded like it might
be the right solution for this problem. But when I load such a mesh into
Paraview, it only picks up on the last defined domain. It seems like
having different solution variables on different grids is a common
problem, so I'm wondering if anyone has a cleaner solution than
selectively turning on and off the blocks corresponding to the solution
variable I am currently considering.
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
