Re: [Paraview] [EXTERNAL] Re: long animations are freezing halfway through
So far, all indicators point to a driver bug. To confirm, is everyone reporting this issue encountering it on NVIDIA GPUs with Windows? Utkarsh On Thu, Jul 6, 2017 at 8:35 PM, stephaneンドング 一信 wrote: > Hello, > > I just want to add that it's happening in both 5.3 and 5.4 > > Ndong-Mefane Stephane, Dr.Eng > Basic Design Sec. > Steam Turbine Dept. > Kawasaki Factory > > Fuji Electric Co., Ltd > 1-1, Tanabeshinden, Kawasaki-ku, > Kawasaki-city 210-9530, Japan > Phone: +81-44-329-2155 <+81%2044-329-2155> > Fax: +81-44-329-2394 <+81%2044-329-2394> > > > On Thu, Jul 6, 2017 at 11:14 PM, Utkarsh Ayachit < > utkarsh.ayac...@kitware.com> wrote: > >> Just to give an update, while I couldn't reproduce the issue with Giles >> example, I was able to do it with another customer. It's quite a curious >> thing indeed! Still figuring out where to begin to debug this -- the fact >> that it's a Windows only thing makes it even more tedious -- but will keep >> you posted. >> >> Utkarsh >> >> On Fri, Jun 23, 2017 at 12:08 PM, Utkarsh Ayachit < >> utkarsh.ayac...@kitware.com> wrote: >> >>> Alan, >>> >>> I am discussing with Giles off line. Will keep you posted. >>> >>> Utkarsh >>> >>> On Fri, Jun 23, 2017 at 12:05 PM, Scott, W Alan >>> wrote: >>> > I have another user with this complaint. I have not been able to >>> replicate it. >>> > >>> > Are you using either opacity or volume rendering? >>> > >>> > Would you be able to pass the data files to Kitware? >>> > >>> > Alan >>> > >>> >> -Original Message- >>> >> From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of >>> >> Utkarsh Ayachit >>> >> Sent: Friday, June 23, 2017 7:07 AM >>> >> To: Richardson CFD >>> >> Cc: ParaView >>> >> Subject: [EXTERNAL] Re: [Paraview] long animations are freezing >>> halfway >>> >> through >>> >> >>> >> Giles, >>> >> >>> >> What OS is this on? >>> >> >>> >> Utkarsh >>> >> >>> >> On Fri, Jun 23, 2017 at 8:59 AM, Richardson CFD >>> wrote: >>> >> > I have been having trouble creating longer animations (150 frames) >>> >> > from larger data files (1million cells). The animation works fine >>> >> > initially but then freezes up about half way through the avi file - >>> >> > displaying just a constant unchanging image. Streamlines seems to >>> work >>> >> > fine, but velocity contours (attached) is the one causing problems. >>> I >>> >> > am having to create the animation in 2 parts, creating 2 seperate >>> avi >>> >> > file and then join them after. >>> >> > >>> >> > Any suggestions or similar experience please let me know. Regards >>> Giles. >>> >> > >>> >> > -- >>> >> > Richardson CFD >>> >> > http://richardsoncfd.weebly.com >>> >> > >>> >> > ___ >>> >> > Powered by www.kitware.com >>> >> > >>> >> > Visit other Kitware open-source projects at >>> >> > http://www.kitware.com/opensource/opensource.html >>> >> > >>> >> > Please keep messages on-topic and check the ParaView Wiki at: >>> >> > http://paraview.org/Wiki/ParaView >>> >> > >>> >> > Search the list archives at: http://markmail.org/search/?q=ParaView >>> >> > >>> >> > Follow this link to subscribe/unsubscribe: >>> >> > http://public.kitware.com/mailman/listinfo/paraview >>> >> > >>> >> ___ >>> >> Powered by www.kitware.com >>> >> >>> >> Visit other Kitware open-source projects at >>> >> http://www.kitware.com/opensource/opensource.html >>> >> >>> >> Please keep messages on-topic and check the ParaView Wiki at: >>> >> http://paraview.org/Wiki/ParaView >>> >> >>> >> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >> >>> >> Follow this link to subscribe/unsubscribe: >>> >> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> ___ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on Windows
Hi Simon,
I tried with PV master (84f6e514) and couldn't replicate the crash. I was
able to get the connection between the GUI and the CatalystTest executable
though since I saw the PVTrivialProducer come up in the GUI.
Maybe you could try PV master and see if it works for you. Beyond that I
think figuring out your issue would take a non-trivial amount of effort to
figure out.
Cheers,
Andy
On Tue, Jul 11, 2017 at 8:04 AM, Simon Klarmann <
klarm...@mechanik.tu-darmstadt.de> wrote:
> Hi Andy,
>
>
>
> I want to be able to close the connection from both sides. Closing the
> connection from the Insitu side works by calling vtkLiveInsituLink::
> DropLiveInsituConnection().
>
> Closing the connection from the Live side, e.g. by closing the GUI, causes
> my application to hang in the vtkSocket::Receive() method.
>
>
>
> After enabling the Debug mode I get the following Error on the Insitu side:
>
> “ERROR: In D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line
> 572
>
> vtkClientSocket (08BFFC00): Socket error in call to send. Eine
> bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer
> abgebrochen.”
>
>
>
> „Eine bestehende Verbindung wurde softwaregesteuert durch den Hostcomputer
> abgebrochen“
>
> This seems to be a windows specific message notifying about a software
> controlled termination of the connection. So the information of the
> termination of the connection is somewhere available. The method throwing
> this error is the vtkSocket::Send() method.
>
>
>
> This error shows up as soon as I close the connection from the Live side
> (GUI) and then perform an InsituUpdate on the Insitu side. Still after this
> message, my Insitu side runs into vtkSocket::Receive() and get stuck there,
> trying to receive data.
>
>
>
>
>
> Additional Info:
>
> Performing the live visualization with the vtkCPPythonAdapter leads to the
> same error message and a crash of the Insitu application.
>
>
>
> Attached is a minimalistic working example. In both cases the error
> happens.
>
>
>
> Steps to reproduce:
>
> 1. Start Paraview ->Catalyst->Connect
>
> 2. Start the application, choose either 0 for python or 1 for cpp,
> then the PVTrivialproducer should show up in Paraview
>
> 3. Close Paraview
>
> 4. Continue the application ->crash
>
>
>
>
>
> I hope this helps a little bit to get an insight on what I did.
>
>
>
> Thanks,
>
> Simon
>
>
>
>
>
>
>
>
>
> *Von:* Andy Bauer [mailto:andy.ba...@kitware.com]
> *Gesendet:* Montag, 10. Juli 2017 22:21
>
> *An:* Simon Klarmann
> *Cc:* paraview@paraview.org
> *Betreff:* Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop
> on Windows
>
>
>
> Hi,
>
>
>
> Are you trying to close the connection from the in situ side? The design
> was for the connection to be close through the GUI.
>
>
>
> It's difficult to say what exactly is going on here without getting fairly
> deep into the problem. Theoretically though it should be possible to do the
> Live link in C++ as most of the Python routines call wrapped C++ routines.
>
>
>
> There should be some way to figure out the status of the connection on the
> PV server (the builtin server if you're not connected to a separate
> pvserver process) either the NotifyClientDisconnected() method,
> or vtkLiveInsituLink::OnConnectionClosedEvent() or
> vtkLiveInsituLink::DropLiveInsituConnection()
> member functions.
>
>
>
> Cheers,
>
> Andy
>
>
>
> On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann darmstadt.de> wrote:
>
> Sorry I think I have chosen the wrong reply method.
>
>
>
> Hi Andy,
>
>
>
> I already got rid of Python on both sides. CoProcessing with Live
> connection is working by directly using the vtkLiveInsituLink (pure C++
> implementation).
>
>
>
> Working with both Paraview 5.2 and 5.4.
>
>
>
> My problem is closing the connection on the Live side (e.g. closing
> Paraview). Doing so, my Insitu side hangs (when trying again to send data,
> m_link->InsituUpdate, see below) in the receive method of the vtkSocket
> class until at some point an integer underflow happens.
>
>
>
> Closing the connection from the Insitu side everything works as expected.
>
>
>
> Are there any methods to directly check if the connection is still alive?
>
> Or is it a Windows specific problem?
>
>
>
>
>
>
>
> Additionally the steps for the live connection in C++, for sure there may
> be more elegant ways:
>
>
>
> // Initialization
>
>
>
> vtkCPProcessor *m_proc = vtkCPProcessor::New();
>
> m_proc->Initialize();
>
>
>
> vtkLiveInsituLink *m_link = vtkLiveInsituLink::New();
>
> m_link->SetInsituPort(2);
>
> m_link->SetHostname("localhost");
>
> m_link->SetProcessType(vtkLiveInsituLink::INSITU);
>
>
>
> vtkSMProxyManager *m_spxm = vtkSMProxyManager::
> GetProxyManager()->GetActiveSessionProxyManager();
>
> vtkSMProxy *m_px = m_spxm->NewProxy("sources",
> "PVTrivialProducer");
>
>
[Paraview] Extracting actual time data
So when extracting data into a .csv file and including all time steps, is it possible to get the actual time extracted to along with the time step? In this particular "Plot over line" simulation that I am running, the time steps are dynamic and not neccesarily the same length. Any help is greatly appreciated. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Extracting actual time data
Nathan, When we export data over timesteps from an Exodus file, we run a time-plot filter first, such as Plot Global Variables Over Time. This creates a variable which contains the length of each timestep. If you then export to .csv, that time variable is included. I suppose Plot Selection Over Time would probably also work. Hope this helps. Dennis ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on Windows
Hi Andy,
I just tried my example on arch linux and it works as expected.
(ParaView 5.4.0-RC1)
Somehow I got the feeling it is an issue related to Windows. Just to be
sure, which OS did you choose to test the example code?
Thank you very much for your time and support,
Simon
Am 2017-07-11 17:02, schrieb Andy Bauer:
Hi Simon,
I tried with PV master (84f6e514) and couldn't replicate the crash. I
was able to get the connection between the GUI and the CatalystTest
executable though since I saw the PVTrivialProducer come up in the
GUI.
Maybe you could try PV master and see if it works for you. Beyond that
I think figuring out your issue would take a non-trivial amount of
effort to figure out.
Cheers,
Andy
On Tue, Jul 11, 2017 at 8:04 AM, Simon Klarmann
wrote:
Hi Andy,
I want to be able to close the connection from both sides. Closing
the connection from the Insitu side works by calling
vtkLiveInsituLink::DropLiveInsituConnection().
Closing the connection from the Live side, e.g. by closing the GUI,
causes my application to hang in the vtkSocket::Receive() method.
After enabling the Debug mode I get the following Error on the
Insitu side:
“ERROR: In
D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line 572
vtkClientSocket (08BFFC00): Socket error in call to send.
Eine bestehende Verbindung wurde softwaregesteuert durch den
Hostcomputer abgebrochen.”
„Eine bestehende Verbindung wurde softwaregesteuert durch den
Hostcomputer abgebrochen“
This seems to be a windows specific message notifying about a
software controlled termination of the connection. So the
information of the termination of the connection is somewhere
available. The method throwing this error is the vtkSocket::Send()
method.
This error shows up as soon as I close the connection from the Live
side (GUI) and then perform an InsituUpdate on the Insitu side.
Still after this message, my Insitu side runs into
vtkSocket::Receive() and get stuck there, trying to receive data.
Additional Info:
Performing the live visualization with the vtkCPPythonAdapter leads
to the same error message and a crash of the Insitu application.
Attached is a minimalistic working example. In both cases the error
happens.
Steps to reproduce:
1. Start Paraview ->Catalyst->Connect
2. Start the application, choose either 0 for python or 1 for
cpp, then the PVTrivialproducer should show up in Paraview
3. Close Paraview
4. Continue the application ->crash
I hope this helps a little bit to get an insight on what I did.
Thanks,
Simon
VON: Andy Bauer [mailto:andy.ba...@kitware.com [1]]
GESENDET: Montag, 10. Juli 2017 22:21
AN: Simon Klarmann
CC: paraview@paraview.org
BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in
loop on Windows
Hi,
Are you trying to close the connection from the in situ side? The
design was for the connection to be close through the GUI.
It's difficult to say what exactly is going on here without getting
fairly deep into the problem. Theoretically though it should be
possible to do the Live link in C++ as most of the Python routines
call wrapped C++ routines.
There should be some way to figure out the status of the connection
on the PV server (the builtin server if you're not connected to a
separate pvserver process) either the NotifyClientDisconnected()
method, or vtkLiveInsituLink::OnConnectionClosedEvent() or
vtkLiveInsituLink::DropLiveInsituConnection() member functions.
Cheers,
Andy
On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann
wrote:
Sorry I think I have chosen the wrong reply method.
Hi Andy,
I already got rid of Python on both sides. CoProcessing with Live
connection is working by directly using the vtkLiveInsituLink (pure
C++ implementation).
Working with both Paraview 5.2 and 5.4.
My problem is closing the connection on the Live side (e.g. closing
Paraview). Doing so, my Insitu side hangs (when trying again to send
data, m_link->InsituUpdate, see below) in the receive method of the
vtkSocket class until at some point an integer underflow happens.
Closing the connection from the Insitu side everything works as
expected.
Are there any methods to directly check if the connection is still
alive?
Or is it a Windows specific problem?
Additionally the steps for the live connection in C++, for sure
there may be more elegant ways:
// Initialization
vtkCPProcessor *m_proc = vtkCPProcessor::New();
m_proc->Initialize();
vtkLiveInsituLink *m_link =
vtkLiveInsituLink::New();
m_link->SetInsituPort(2);
m_link->SetHostname("localhost");
m_link->SetProcessType(vtkLiveInsituLink::INSITU);
vtkSMProxyManager *m_spxm =
vtkSMProxyManager::GetProxyManager()->GetActiveSessionProxyManager();
vtkSMProxy *m_px = m_spxm->NewProxy("sources",
"PVTrivialProducer");
vtkSMSourceProxy *m_spx =
vtkSMSourceProxy::SafeDownCast(m_px);
m_spxm->RegisterProxy("sources", m_spx);
vtkObjectBase *obase = m_spx->GetClientSideObject();
vtkPVTrivialProducer *prod =
v
Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in loop on Windows
Hi, I tested on Linux (Ubuntu 16.04). Best, Andy On Tue, Jul 11, 2017 at 1:58 PM, wrote: > Hi Andy, > > I just tried my example on arch linux and it works as expected. (ParaView > 5.4.0-RC1) > > Somehow I got the feeling it is an issue related to Windows. Just to be > sure, which OS did you choose to test the example code? > > Thank you very much for your time and support, > Simon > > > > > Am 2017-07-11 17:02, schrieb Andy Bauer: > >> Hi Simon, >> >> I tried with PV master (84f6e514) and couldn't replicate the crash. I >> was able to get the connection between the GUI and the CatalystTest >> executable though since I saw the PVTrivialProducer come up in the >> GUI. >> >> Maybe you could try PV master and see if it works for you. Beyond that >> I think figuring out your issue would take a non-trivial amount of >> effort to figure out. >> >> Cheers, >> Andy >> >> On Tue, Jul 11, 2017 at 8:04 AM, Simon Klarmann >> wrote: >> >> Hi Andy, >>> >>> I want to be able to close the connection from both sides. Closing >>> the connection from the Insitu side works by calling >>> vtkLiveInsituLink::DropLiveInsituConnection(). >>> >>> Closing the connection from the Live side, e.g. by closing the GUI, >>> causes my application to hang in the vtkSocket::Receive() method. >>> >>> After enabling the Debug mode I get the following Error on the >>> Insitu side: >>> >>> “ERROR: In >>> D:\build\ParaView-v5.4.0\VTK\Common\System\vtkSocket.cxx, line 572 >>> >>> vtkClientSocket (08BFFC00): Socket error in call to send. >>> Eine bestehende Verbindung wurde softwaregesteuert durch den >>> Hostcomputer abgebrochen.” >>> >>> „Eine bestehende Verbindung wurde softwaregesteuert durch den >>> Hostcomputer abgebrochen“ >>> >>> This seems to be a windows specific message notifying about a >>> software controlled termination of the connection. So the >>> information of the termination of the connection is somewhere >>> available. The method throwing this error is the vtkSocket::Send() >>> method. >>> >>> This error shows up as soon as I close the connection from the Live >>> side (GUI) and then perform an InsituUpdate on the Insitu side. >>> Still after this message, my Insitu side runs into >>> vtkSocket::Receive() and get stuck there, trying to receive data. >>> >>> Additional Info: >>> >>> Performing the live visualization with the vtkCPPythonAdapter leads >>> to the same error message and a crash of the Insitu application. >>> >>> Attached is a minimalistic working example. In both cases the error >>> happens. >>> >>> Steps to reproduce: >>> >>> 1. Start Paraview ->Catalyst->Connect >>> >>> 2. Start the application, choose either 0 for python or 1 for >>> cpp, then the PVTrivialproducer should show up in Paraview >>> >>> 3. Close Paraview >>> >>> 4. Continue the application ->crash >>> >>> I hope this helps a little bit to get an insight on what I did. >>> >>> Thanks, >>> >>> Simon >>> >>> VON: Andy Bauer [mailto:andy.ba...@kitware.com [1]] >>> GESENDET: Montag, 10. Juli 2017 22:21 >>> >>> AN: Simon Klarmann >>> CC: paraview@paraview.org >>> BETREFF: Re: [Paraview] C++ Catalyst vtkSocket::Receive stuck in >>> >>> loop on Windows >>> >>> Hi, >>> >>> Are you trying to close the connection from the in situ side? The >>> design was for the connection to be close through the GUI. >>> >>> It's difficult to say what exactly is going on here without getting >>> fairly deep into the problem. Theoretically though it should be >>> possible to do the Live link in C++ as most of the Python routines >>> call wrapped C++ routines. >>> >>> There should be some way to figure out the status of the connection >>> on the PV server (the builtin server if you're not connected to a >>> separate pvserver process) either the NotifyClientDisconnected() >>> method, or vtkLiveInsituLink::OnConnectionClosedEvent() or >>> vtkLiveInsituLink::DropLiveInsituConnection() member functions. >>> >>> Cheers, >>> >>> Andy >>> >>> On Mon, Jul 10, 2017 at 10:34 AM, Simon Klarmann >>> wrote: >>> >>> Sorry I think I have chosen the wrong reply method. >>> >>> Hi Andy, >>> >>> I already got rid of Python on both sides. CoProcessing with Live >>> connection is working by directly using the vtkLiveInsituLink (pure >>> C++ implementation). >>> >>> Working with both Paraview 5.2 and 5.4. >>> >>> My problem is closing the connection on the Live side (e.g. closing >>> Paraview). Doing so, my Insitu side hangs (when trying again to send >>> data, m_link->InsituUpdate, see below) in the receive method of the >>> vtkSocket class until at some point an integer underflow happens. >>> >>> Closing the connection from the Insitu side everything works as >>> expected. >>> >>> Are there any methods to directly check if the connection is still >>> alive? >>> >>> Or is it a Windows specific problem? >>> >>> Additionally the steps for the live connection in C++, for sure >>> there may be more elegant ways: >>> >>> // Initialization >>> >>> vtkCPProcessor *m
[Paraview] Running Paraview on an HPC machine with multiple processes?
Good Afternoon, I have been moving to an HDF5/XDMF system for analyzing big data from a computational fluid model. I finally got all the basic components working on my local machine but have run into problems when trying to run on an HPC system. Here is the XDMF file: http://www.w3.org/2003/XInclude"; Version="2.1"> 0 0 0 1 1 1 out.h5:/pres_group/presmag out.h5:/velo_group/x_velo out.h5:/velo_group/y_velo out.h5:/velo_group/z_velo This has worked properly on my machine. However, when I was getting an error of failing to read the pressure data when I tried this on multiple processes. The vector data for velocity was fine, but the pressure data could not be read. I narrowed the problem down to something regarding the number of processes because the pressure data worked fine on the HPC machine if I only ran it on 1 process. Is there anything that sticks out that could be causing this problem? For instance, is there a different format for these files when they are run on multiple processes? Respectfully, Jacob Gerard ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] superbuild: configure: error swr requires C++14 support
dear experts, the superbuild currently supports mpich ( http://www.paraview.org/files/dependencies/mpich-3.2.tar.gz). Did someone by chance try to use openmpi (which version can be used in this case?) and if so, is there some feedback one could benefit from ? thanks. Nabil Ghodbane (Ph. D. Habil*.*) Phone: +33 6 34 42 33 43 Mailto: nabil.ghodb...@gmail.com On Tue, Jul 4, 2017 at 3:02 PM, Nabil Ghodbane wrote: > dear experts > I am trying to compile Paraview with the latest superbuild using gcc 4.8.5 > the compilation fails with the error message that C++14 is needed... > *configure: error swr requires C++14 support* > > This raises two questions: > 1/ Can one switch to c++11 and if yes, how ? > 2/ what is the minimal configuration for gcc one needs to setup in order > to be able to compile Paraview with superbuild. > thanks > > > Nabil Ghodbane (Ph. D. Habil*.*) > Phone: +33 6 34 42 33 43 <06%2034%2042%2033%2043> > Mailto: nabil.ghodb...@gmail.com > > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] superbuild: configure: error swr requires C++14 support
Nabil, OpenMPI would work just fine too. Use can make the superbuild use an externally built MPI implementation very easily. As documented here ( https://gitlab.kitware.com/paraview/paraview-superbuild/), just set the USE_SYSTEM_xxx (in this case, USE_SYSTEM_mpi) Cmake flag to ON and then point to the MPI libs, if not in default path. Utkarsh On Tue, Jul 11, 2017 at 6:49 PM, Nabil Ghodbane wrote: > dear experts, > the superbuild currently supports mpich (http://www.paraview.org/ > files/dependencies/mpich-3.2.tar.gz). Did someone by chance try to use > openmpi (which version can be used in this case?) and if so, is there some > feedback one could benefit from ? > thanks. > > Nabil Ghodbane (Ph. D. Habil*.*) > Phone: +33 6 34 42 33 43 <+33%206%2034%2042%2033%2043> > Mailto: nabil.ghodb...@gmail.com > > > On Tue, Jul 4, 2017 at 3:02 PM, Nabil Ghodbane > wrote: > >> dear experts >> I am trying to compile Paraview with the latest superbuild using gcc 4.8.5 >> the compilation fails with the error message that C++14 is needed... >> *configure: error swr requires C++14 support* >> >> This raises two questions: >> 1/ Can one switch to c++11 and if yes, how ? >> 2/ what is the minimal configuration for gcc one needs to setup in order >> to be able to compile Paraview with superbuild. >> thanks >> >> >> Nabil Ghodbane (Ph. D. Habil*.*) >> Phone: +33 6 34 42 33 43 <06%2034%2042%2033%2043> >> Mailto: nabil.ghodb...@gmail.com >> >> > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
