<div dir="ltr"><div>FYI: I just made an MR for this -- <a href="https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/440">https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/440</a>.<br><br></div>I made it an advanced option, also called PARAVIEW_INITIALIZE_MPI_ON_<wbr>CLIENT, and only available if mpi is enabled.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 9, 2018 at 3:26 PM, Andy Bauer <span dir="ltr"><<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Joe,<br><br></div>I don't see PARAVIEW_INITIALIZE_MPI_ON_<wbr>CLIENT being set in the PV superbuild. It does make sense to me though to add that option to the superbuild though. As far as the default value for PARAVIEW_INITIALIZE_MPI_ON_<wbr>CLIENT in ParaView itself, I guess it's just a matter of opinion on whether it should be enabled or disabled by default.<br><br></div>Best,<br></div>Andy<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 9, 2018 at 3:13 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) <span dir="ltr"><<a href="mailto:joseph.g.hennessey2.ctr@mail.mil" target="_blank">joseph.g.hennessey2.ctr@mail.<wbr>mil</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Andy,<br>
<br>
Running paraview with --no-mpi remove the requirement for starting MPI with<br>
it.<br>
<br>
It seems that the superbuild is defining PARAVIEW_INITIALIZE_MPI_ON_CLI<wbr>ENT<br>
for some reason.<br>
<br>
Looking in the RC2 of ParaView 5.5.0's main CMakeLists.txt file<br>
<br>
configure_file(<br>
${ParaView_SOURCE_DIR}/<a href="http://vtkPVConfig.h.in" rel="noreferrer" target="_blank">vtkPVCo<wbr>nfig.h.in</a><br>
${ParaView_BINARY_DIR}/vtkPVCo<wbr>nfig.h<br>
@ONLY)<br>
<br>
Is now setting PARAVIEW_INITIALIZE_MPI_ON_CLI<wbr>ENT<br>
whereas with ParaView 5.4.1 it was being initialized to off.<br>
<br>
I used cmake 3.10.2 to configure the superbuild for ParaView 5.5.0-RC2,<br>
while I used cmake 3.9.1 to configure the superbuild for ParaView 5.4.1.<br>
<span><br>
Thanks,<br>
<br>
Joe<br>
<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<wbr>~~~~~<br>
Joseph G. Hennessey Ph.D., SAIC<br>
Team SAIC<br>
Army Research Lab<br>
DOD Supercomputing Resource Center<br>
Email: <a href="mailto:joseph.g.hennessey2.ctr@mail.mil" target="_blank">joseph.g.hennessey2.ctr@mail.m<wbr>il</a><br>
<br>
<br>
</span><span>-----Original Message-----<br>
From: Andy Bauer [mailto:<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a><wbr>]<br>
Sent: Wednesday, March 07, 2018 9:22 AM<br>
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)<br>
<<a href="mailto:joseph.g.hennessey2.ctr@mail.mil" target="_blank">joseph.g.hennessey2.ctr@mail.<wbr>mil</a>><br>
</span><span>Cc: ParaView Developers <<a href="mailto:paraview-developers@paraview.org" target="_blank">paraview-developers@paraview.<wbr>org</a>><br>
Subject: [Non-DoD Source] Re: [Paraview-developers] Change in mpi operation of<br>
paraview and pvpython in ParaView 5.5.0-RC1-1<br>
<br>
<br>
Hi Joe,<br>
<br>
<br>
Is it possible that you're using a different MPI for your builds? I'm<br>
wondering if the previous MPI version didn't require mpirun in order to run a<br>
single process while the current one does.<br>
<br>
What you can do though is to use the "--no-mpi" option which will skip<br>
initializing and finalizing MPI but also make the MPI required filters and<br>
readers not available. It's possible that the CMake<br>
PARAVIEW_INITIALIZE_MPI_ON_CLI<wbr>ENT option got switched from OFF to ON. It it is<br>
OFF by default but PV is still built with MPI you can do a --mpi to have the<br>
GUI or pvpython initialize and finalize MPI.<br>
<br>
<br>
Most filters (actually, I'm not aware of any) don't explicitly rely on MPI for<br>
single process runs but there are a couple of readers that use MPI IO.<br>
<br>
<br>
Best,<br>
<br>
Andy<br>
<br>
<br>
On Wed, Mar 7, 2018 at 9:02 AM, Hennessey, Joseph G CTR USARMY RDECOM ARL (US)<br>
<<a href="mailto:joseph.g.hennessey2.ctr@mail.mil" target="_blank">joseph.g.hennessey2.ctr@mail.<wbr>mil</a> <<br>
</span><div><div class="m_-7180898662979080402h5">Caution-mailto:<a href="mailto:joseph.g.hennessey2.ctr@mail.mil" target="_blank">joseph.g.hennes<wbr>sey2.ctr@mail.mil</a> > > wrote:<br>
<br>
<br>
Hello,<br>
<br>
I have noticed that when building ParaView 5.5.0-RC1-1 with an external<br>
MPI version that pvpython and paraview itself are now being built such<br>
that they can not be executed without mpirun.<br>
<br>
For example this would work with ParaView 5.4.1<br>
<br>
paraview<br>
pvpython<br>
mpirun -n 1 pvbatch<br>
<br>
While for ParaView 5.5.0-RC1-1 I have to do the following<br>
<br>
mpirun -n 1 paraview<br>
mpirun -n 1 pvpython<br>
mpirun -n 1 pvbatch<br>
<br>
as running<br>
<br>
paraview<br>
pvpython<br>
<br>
without mpirun will no longer work and complain about<br>
attempting to run an mpi required program without mpi,<br>
as has been the case with pvbatch in the past.<br>
<br>
Is this an intentional change, or is this an unintended consequence<br>
of some other change?<br>
<br>
Thanks,<br>
<br>
Joe<br>
<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<wbr>~~~~~<br>
Joseph G. Hennessey Ph.D., SAIC<br>
Team SAIC<br>
Army Research Lab<br>
DOD Supercomputing Resource Center<br>
Email: <a href="mailto:joseph.g.hennessey2.ctr@mail.mil" target="_blank">joseph.g.hennessey2.ctr@mail.m<wbr>il</a> <<br>
</div></div>Caution-mailto:<a href="mailto:joseph.g.hennessey2.ctr@mail.mil" target="_blank">joseph.g.hennes<wbr>sey2.ctr@mail.mil</a> ><br>
<br>
<br>
______________________________<wbr>_________________<br>
Powered by <a href="http://Caution-www.kitware.com" rel="noreferrer" target="_blank">Caution-www.kitware.com</a> < Caution-<a href="http://www.kitware.com" rel="noreferrer" target="_blank">http://www.kitware.com</a> ><br>
<span><br>
Visit other Kitware open-source projects at<br>
</span>Caution-<a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com<wbr>/opensource/opensource.html</a> <<br>
Caution-<a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com<wbr>/opensource/opensource.html</a> ><br>
<span><br>
Search the list archives at:<br>
</span>Caution-<a href="http://markmail.org/search/?q=Paraview-developers" rel="noreferrer" target="_blank">http://markmail.org/se<wbr>arch/?q=Paraview-developers</a> <<br>
Caution-<a href="http://markmail.org/search/?q=Paraview-developers" rel="noreferrer" target="_blank">http://markmail.org/se<wbr>arch/?q=Paraview-developers</a> ><br>
<span><br>
Follow this link to subscribe/unsubscribe:<br>
</span> Caution-<a href="https://public.kitware.com/mailman/listinfo/paraview-developers" rel="noreferrer" target="_blank">https://public.kitware<wbr>.com/mailman/listinfo/paraview<wbr>-developers</a> <<br>
Caution-<a href="https://public.kitware.com/mailman/listinfo/paraview-developers" rel="noreferrer" target="_blank">https://public.kitware<wbr>.com/mailman/listinfo/paraview<wbr>-developers</a> ><br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>