Hi Jean, I don't think that the problem is with D3. I suspect that it is with the connectivity filter, which is not parallel-aware. Ghost levels are not enough (or necessary) for this to work in parallel. Rather, there needs to be some parallel merge algorithm to identify connected regions across partition boundaries. Unfortunately, we don't have anything like that at the moment.
-berk On Fri, Feb 22, 2013 at 10:31 AM, Favre Jean <[email protected]> wrote: > Hello > > I have an hexahedral grid, in a *vtu file. When read on a local client, the > Connectivity filter *correctly* detects that there is a single region (with > Extract All Regions). > > The same *vtu file, when read in parallel, shows multiple regions, with > *some* region boundaries matching processor boundaries. > > Adding D3 in between, makes things even worse, as some cells are completely > dropped. Yet, the cells are only hexahedra, thus with face-to-face > connectivity. Can D3 be forced to generate ghost cells which would ensure > correct region extraction? > > ----------------- > Jean/CSCS > _______________________________________________ > 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://www.paraview.org/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://www.paraview.org/mailman/listinfo/paraview
