[Paraview] Is VTU File Reading Parallelized?

[Berk Geveci]

> Also...Inside UpdateInformation, the number of pieces and piece number are
> not set, inside UpdateData they are. In my view this is wrong and they
> should be set in update information too, (but you can get the mpi rank
> directly from the glocal communicator). Berk et al, can you say why the
> piece info isn't set during the information pass?

Just to make sure I understand, you are saying that
UPDATE_NUMBER_OF_PIECES() and UPDATE_PIECE_NUMBER() are set during the
RequestUpdateExtent() pass (which is true) and you are asking asking
why they are not set during RequestInformation() pass. Correct? They
cannot be set during RequestInformation() because those are requests
propagated from consumer to producer whereas the RequestInformation()
is for producers to provide information to their consumers.
MAXIMUM_NUMBER_OF_PIECES() is set during RequestInformation(). I am
guessing your use case may be that you want to provide information
specific to a piece? We have done some work with LANL folks in this
area. In that work, the pipeline passes look like:

1. RequestInformation (producers provide _static_ information about
what is available)
2. RequestUpdateExtent (consumers tell the producers what they will be asking)
3. RequestUpdateExtentInformation (producers provide _dynamic_ (per
piece, per time etc.) information
     about what is available)
4. Repeat 2 and 3 as many times as necessary
5. RequestUpdateData (pipeline executes)

-berk