[Paraview] parellel processing problem

[Andy Bauer]

You can use the Process Id Scalars to examine the data distribution and
maybe see if something funky is going on there. In parallel there's also a
helper array which you can pseudo-color by to see the partitioning but I
don't remember the name of that array.

You could also try doing something like a Wavelet source in parallel and
pseudo-color that by process id to see if the partitioning is working
properly for that..

On Tue, Nov 1, 2016 at 9:37 AM, spectm2 <spectm2 at rpi.edu> wrote:

> Hello,
>
> I am brand new to Paraview and I an having a serious parallel processing
> problem when using a pvserver client/server connection, Paraview 4.4.0, and
> mvapitch2-2.0a-gcc44. The server and the client run linux.
>
> Attached is my .pvd file and a photo of what the model should look like
> (ie. when I am using 1 processor) and what the model looks like when I am
> using more than one processor.
>
> When I ran this FEM simulation I used 16 processors. So, for each time
> step folder (for ex. DRPTransientN_13, which is for the 13th time step)
> there is a folder inside named '0' that contains 16 .vtu files.
>
> Also, when using multiple processors in Paraview I can 'scrub' through
> time with this one chunk of the model.
>
>
> It seems like Paraview isnt reading the .pvd file correctly, or
> something....
>
>
> Do you have any idea what the issue is? Any fixes that I can implement?
>
>
> I would be most grateful for any help you can provide.
> _______________________________________________
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20161109/e22fd8f1/attachment.html>