[Paraview-developers] [Non-DoD Source] Re: Problems with mpi4py and SGI's mpt 2.14 version of MPI

[Hennessey, Joseph G CTR USARMY RDECOM ARL (US)]

Ben,

The idea of reruning the Cython code generator so that it works with an 
arbitrary MPI,
sounds like a good idea to me. I compile and install ParaView across a wide 
range of HPC systems,
with many variations of MPI across all of them.

Do you know what would be involved in implementing this?

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005


-----Original Message-----
From: Ben Boeckel [mailto:ben.boeckel at kitware.com]
Sent: Monday, April 03, 2017 11:30 AM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) 
<joseph.g.hennessey2.ctr at mail.mil>
Cc: ParaView Developers <paraview-developers at paraview.org>
Subject: [Non-DoD Source] Re: [Paraview-developers] Problems with mpi4py and 
SGI's mpt 2.14 version of MPI

All active links contained in this email were disabled.  Please verify the 
identity of the sender, and confirm the authenticity of all links contained 
within the message prior to copying and pasting the address to a Web browser.




----

On Mon, Apr 03, 2017 at 14:15:49 +0000, Hennessey, Joseph G CTR USARMY RDECOM 
ARL (US) wrote:
> I have been running into problems with mpi4py and SGI's mpt 2.14
> version of MPI while compiling ParaView 5.3.0 on HPC systems.
>
> mpi4py cannot find MPI_CONVERSION_FN_NULL when compiling mpi4py.MPI.c
>
> MPI_CONVERSION_FN_NULL was not used by the version of mpi4py that came
> with ParaView 5.2.0 and when I swap the ParaView 5.2.0 version of
> mpi4py in place of the ParaView 5.3.0 version of mpi4py then ParaView
> 5.3.0 (with the 5.2.0 version of mpi4py) compiles just fine.
>
> Is this a known problem? Is there a minimum version of mpt that is
> required for ParaView 5.3.0? What will break if use the ParaView 5.2.0
> version of mpi4py instead with ParaView 5.3.0?

We updated from mpi4py from 1.3.0 to 2.0.0. You can see upstream-documented 
differences here:

    Caution-https://gitlab.kitware.com/vtk/vtk/blob/master/ThirdParty/mpi4py/vtkmpi4py/CHANGES.rst

It doesn't appear that VTK cares about the backwards-incompat changes listed 
there (we use it to allow MPI Controllers to be shared between VTK's C++ code 
and other Python code).

It seems that the MPI_CONVERSION_FN_NULL is used because the 
upstream-generated Cython code says it exists. Maybe the module could be 
updated to optionally rerun the Cython code generator so that it works with an 
arbitrary MPI?

--Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170403/2610d6ca/attachment.bin>