[Paraview-developers] How to get raw MPI communicator in plugin

[Schlottke, Michael]

Hi again,

I was wondering what the “canonical” way is to get the correct MPI communicator within a parallel reader plugin (e.g. for use in a parallel I/O library)? Until now I just used  “MPI_COMM_WORLD” and hoped for the best. However, I noticed that in the CosmoTools (https://github.com/Kitware/ParaView/blob/master/ParaViewCore/VTKExtensions/CosmoTools/vtkGenericIOUtilities.cxx#L25) or the AdiosReader (https://github.com/Kitware/ParaView/blob/master/Plugins/AdiosReader/vtkAdiosInternals.h#L103) the raw MPI communicator is obtained through some calls to vtkMPICommunicator objects. Is this the right way to do it?

As a second part to this question, what is the correct way of initializing (and finalizing?) MPI from within a reader plugin if it was not initialized (e.g. because paraview was started without the —mpi flag)? Is this even possible to to “correctly” or will it always be a hack to do this from within a plugin?

Regards,

Michael


--
Michael Schlottke

Chair of Fluid Mechanics and Institute of Aerodynamics
RWTH Aachen University
Wüllnerstraße 5a
52062 Aachen
Germany

Phone: +49 (241) 80 95188
Fax: +49 (241) 80 92257
Mail: m.schlottke at aia.rwth-aachen.de<mailto:m.schlottke at aia.rwth-aachen.de>
Web: http://www.aia.rwth-aachen.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150414/058108a7/attachment.html>