<HTML>
<HEAD>
<TITLE>Re: [Paraview-developers] MPI_Init during standalone ParaView operation</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi John,<BR>
<BR>
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?<BR>
<BR>
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().<BR>
<BR>
Nathan.<BR>
<BR>
On 10/28/09 2:12 AM, "Biddiscombe, John A." <<a href="biddisco@cscs.ch">biddisco@cscs.ch</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>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.<BR>
<BR>
<BR>
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.<BR>
<BR>
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.<BR>
<BR>
Thanks<BR>
<BR>
JB<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>