[Paraview-developers] MPI_Init during standalone ParaView operation

[Fabian, Nathan]

Hi John,

I'm not familiar with Xdmf's DSM, but I remember you mentioned using that to communicate with the sim.  Are you reusing the sim's mpi_world and need to have that shared into paraview's stuff?  Or is it using something else?

Otherwise, I think the paraview client initializes the global controller with Dummy, but I think perhaps you could safely replace that when you detect the need by initializing a new MPIController and SetGlobalController().

Nathan.

On 10/28/09 2:12 AM, "Biddiscombe, John A." <biddisco at cscs.ch> wrote:

When running paraview as a stand-alone app, MPI_Init plus the initialization of communicators and suchlike is not done. Within our Xdmf/DSM plugin we make use of shared communicators to connect sim/vis. Currently everything works fine when the paraview client is connected to N pvserver instances, but not when running stand-alone.


I'd like to add in an additional set of calls to MPI_Init 'on request' i.e. when the user does something that tries to make use of the DSM - I had a quick play around with calling MPI_Init on a button click event and all was fine, but in order to get ParaView (global) communicators setup, I may need to do some digging around.

If anyone has any hints of what would need to be initialized and where to poke around in the source code, then I'd be most grateful for tips.

Thanks

JB

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20091028/6ee4018a/attachment.htm>