[vtkusers] Interfacing Parallel VTK with other parallel API

Berk Geveci berk.geveci at kitware.com
Wed Jun 26 11:14:17 EDT 2002


Oops. There is really no good reason why the constructor and destructor
are private. My mistake. I fixed it.
I can also add an accessor to the "opaque" communicator, if you prefer.

-Berk

On Wed, 2002-06-26 at 10:46, Moreland, Kenneth wrote:
> Hi all,
> 
> I'm having trouble interfacing the parallel VTK objects with another
> parallel API which exclusively uses MPI.  Specifically, I'm making a VTK
> object (as a wrapper over the auxiliary API) which accepts a
> vtkMPIController and must extract the MPI_Comm object from the associated
> vtkMPICommunicator.
> 
> The tricky bit is that the reference to the MPI_Comm object in the
> vtkMPICommunicator is protected.  I previously got around this problem by
> making a dummy class that inherited from vtkMPICommunicator and provided a
> public method to return the MPI_Comm object.  This has been working for
> quite a while, but yesterday I checked out the latest nightly build and
> found that the constructor and destructor for vtkMPICommunicator have been
> made private, making inheritance impossible.
> 
> Is there another way to get at the MPI_Comm object?  If not, could the
> vtkMPICommunicator constructor and destructor be made protected again?  Or
> could a public method for returning the vtkMPICommunicatorOpaqueComm be
> added?
> 
> -Ken
> 
>    ****      Kenneth Moreland
>     ***      Sandia National Laboratories
> ***********  
> *** *** ***  email: kmorel at sandia.gov
> **  ***  **  phone: (505) 844-8919
>     ***      fax:   (505) 844-9297
> 
> _______________________________________________
> This is the private VTK discussion list. 
> Please keep messages on-topic. Check the FAQ at: <http://public.kitware.com/cgi-bin/vtkfaq>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers





More information about the vtkusers mailing list