Re: [Paraview] ParaView on a Retina display
Hi Robert, is there an easy to "force" the ParaView CVS to compile against qt 5 ? Thanks PO On 2012-09-05, at 3:11 PM, Pierre-Olivier Dallaire wrote: > I'm compiling QT 5 beta to see what happens, I'll see if I can get ParaView > 3.14 compiled against it. > > On 2012-09-05, at 1:27 PM, Robert Maynard wrote: > >> I do believe that is correct. I don't know what version of Qt will have >> retina support by default. >> >> On Wed, Sep 5, 2012 at 10:26 AM, Pierre-Olivier Dallaire >> wrote: >> Thanks / yes, that takes care of rendering the fonts correctly, icons are >> still blurry but overall it's better. >> My guess is that to get the full retina support, that means QT needs to be >> updated first … ? >> >> >> On 2012-09-05, at 10:15 AM, Robert Maynard >> wrote: >> >>> As a temporary workaround you can manually modify the paraview application >>> to enable retina support. >>> I haven't verified that all the icons layout properly. >>> >>> You need to edit the info.plist inside the Paraview.app/Contents/ folder >>> and add the following two lines as the >>> first items in the : >>> >>> NSPrincipalClass >>> NSApplication >>> >>> >>> On Wed, Sep 5, 2012 at 12:50 AM, Pierre-Olivier Dallaire >>> wrote: >>> Hi, >>> >>> I'm testing ParaView on a new MacBook Pro Retina and was wondering if there >>> is >>> any plan to support that hardware in a near future ? The application works >>> great >>> but the GUI is not as "sharp" as it could be in on this display. >>> >>> Regards, >>> >>> PO >>> ___ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.paraview.org/mailman/listinfo/paraview >>> >>> >>> >>> -- >>> Robert Maynard >> >> >> >> >> -- >> Robert Maynard > > ___ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView on a Retina display
Robert, I have looked into this and the QT team are making adjustments to support HiDPI: https://bugreports.qt-project.org/browse/QTBUG-23870 QT 5 beta is not "HiDPI" ready yet... I don't know how difficult it would be after to update Paraview to support the same capabilities. The temporary workaround affects only the fonts; icons and main window remain blurry. Thanks PO On 2012-09-05, at 3:11 PM, Pierre-Olivier Dallaire wrote: > I'm compiling QT 5 beta to see what happens, I'll see if I can get ParaView > 3.14 compiled against it. > > On 2012-09-05, at 1:27 PM, Robert Maynard wrote: > >> I do believe that is correct. I don't know what version of Qt will have >> retina support by default. >> >> On Wed, Sep 5, 2012 at 10:26 AM, Pierre-Olivier Dallaire >> wrote: >> Thanks / yes, that takes care of rendering the fonts correctly, icons are >> still blurry but overall it's better. >> My guess is that to get the full retina support, that means QT needs to be >> updated first … ? >> >> >> On 2012-09-05, at 10:15 AM, Robert Maynard >> wrote: >> >>> As a temporary workaround you can manually modify the paraview application >>> to enable retina support. >>> I haven't verified that all the icons layout properly. >>> >>> You need to edit the info.plist inside the Paraview.app/Contents/ folder >>> and add the following two lines as the >>> first items in the : >>> >>> NSPrincipalClass >>> NSApplication >>> >>> >>> On Wed, Sep 5, 2012 at 12:50 AM, Pierre-Olivier Dallaire >>> wrote: >>> Hi, >>> >>> I'm testing ParaView on a new MacBook Pro Retina and was wondering if there >>> is >>> any plan to support that hardware in a near future ? The application works >>> great >>> but the GUI is not as "sharp" as it could be in on this display. >>> >>> Regards, >>> >>> PO >>> ___ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.paraview.org/mailman/listinfo/paraview >>> >>> >>> >>> -- >>> Robert Maynard >> >> >> >> >> -- >> Robert Maynard > > ___ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView on a Retina display
I'm compiling QT 5 beta to see what happens, I'll see if I can get ParaView 3.14 compiled against it. On 2012-09-05, at 1:27 PM, Robert Maynard wrote: > I do believe that is correct. I don't know what version of Qt will have > retina support by default. > > On Wed, Sep 5, 2012 at 10:26 AM, Pierre-Olivier Dallaire > wrote: > Thanks / yes, that takes care of rendering the fonts correctly, icons are > still blurry but overall it's better. > My guess is that to get the full retina support, that means QT needs to be > updated first … ? > > > On 2012-09-05, at 10:15 AM, Robert Maynard wrote: > >> As a temporary workaround you can manually modify the paraview application >> to enable retina support. >> I haven't verified that all the icons layout properly. >> >> You need to edit the info.plist inside the Paraview.app/Contents/ folder and >> add the following two lines as the >> first items in the : >> >> NSPrincipalClass >> NSApplication >> >> >> On Wed, Sep 5, 2012 at 12:50 AM, Pierre-Olivier Dallaire >> wrote: >> Hi, >> >> I'm testing ParaView on a new MacBook Pro Retina and was wondering if there >> is >> any plan to support that hardware in a near future ? The application works >> great >> but the GUI is not as "sharp" as it could be in on this display. >> >> Regards, >> >> PO >> ___ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/mailman/listinfo/paraview >> >> >> >> -- >> Robert Maynard > > > > > -- > Robert Maynard ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView on a Retina display
Thanks / yes, that takes care of rendering the fonts correctly, icons are still blurry but overall it's better. My guess is that to get the full retina support, that means QT needs to be updated first … ? On 2012-09-05, at 10:15 AM, Robert Maynard wrote: > As a temporary workaround you can manually modify the paraview application to > enable retina support. > I haven't verified that all the icons layout properly. > > You need to edit the info.plist inside the Paraview.app/Contents/ folder and > add the following two lines as the > first items in the : > > NSPrincipalClass > NSApplication > > > On Wed, Sep 5, 2012 at 12:50 AM, Pierre-Olivier Dallaire > wrote: > Hi, > > I'm testing ParaView on a new MacBook Pro Retina and was wondering if there is > any plan to support that hardware in a near future ? The application works > great > but the GUI is not as "sharp" as it could be in on this display. > > Regards, > > PO > ___ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > > > -- > Robert Maynard ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] ParaView on a Retina display
Hi, I'm testing ParaView on a new MacBook Pro Retina and was wondering if there is any plan to support that hardware in a near future ? The application works great but the GUI is not as "sharp" as it could be in on this display. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Building Paraview on Mac with MPI and Python
Hi, I've been trying to build Paraview 3.14.1 from sources with options BUILD_SHARED_LIBS:BOOL=ON, PARAVIEW_ENABLE_PYTHON:BOOL=ON and PARAVIEW_USE_MPI:BOOL=ON. I have a working version of openmpi-1.6 compiled on my machine. However, it seems that the mpi/python module fails to launch during the process: [ 48%] Built target paraview_mpi_pyc Linking CXX shared module ../../../bin/MPIPython.so Undefined symbols for architecture x86_64: "_lt_dladvise_destroy", referenced from: _dlopen_mpi_lib in MPI.c.o "_lt_dladvise_ext", referenced from: _dlopen_mpi_lib in MPI.c.o "_lt_dladvise_global", referenced from: _dlopen_mpi_lib in MPI.c.o "_lt_dladvise_init", referenced from: _dlopen_mpi_lib in MPI.c.o "_lt_dlclose", referenced from: ___pyx_pf_6mpi4py_3MPI_Finalize in MPI.c.o ___pyx_f_6mpi4py_3MPI_atexit_py in MPI.c.o "_lt_dlexit", referenced from: ___pyx_pf_6mpi4py_3MPI_Finalize in MPI.c.o ___pyx_f_6mpi4py_3MPI_atexit_py in MPI.c.o "_lt_dlinit", referenced from: _dlopen_mpi_lib in MPI.c.o "_lt_dlopenadvise", referenced from: _dlopen_mpi_lib in MPI.c.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Note that I've been able to build Paraview without any problem with the parallel option disable. Any idea ? Thanks ! PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Client-server mode / data streaming problem
Good morning, I tested different scenarios using OpenFOAM cases and found out that this problem happens when a "patch" is selected / I don't have the same issue when I'm working with all the cells. Regards, PO Begin forwarded message: > From: Pierre-Olivier Dallaire > Date: January 28, 2011 12:56:28 PM EST > To: ParaView > Subject: Re: [Paraview] Latest Git - Mac OS X, error > > I see that changes were made to the code, thank you, I can compile now ! > > I have noted in the last few versions that the client/server mode has brought > back > a bad habit very similar to that : > http://www.paraview.org/pipermail/paraview/2010-January/015174.html > where the server re-stream the data as soon as the client does an action > (pan, zoom, rotate). I'm attaching the output > from the time log below. > > Regards, > > PO > > > Local Process > Interactive Render, 0.075363 seconds > OpenGL Dev Render, 0.000533 seconds > OpenGL Dev Render, 1.5e-05 seconds > Interactive Render, 0.010636 seconds > OpenGL Dev Render, 0.000527 seconds > OpenGL Dev Render, 1.5e-05 seconds > Interactive Render, 0.02397 seconds > OpenGL Dev Render, 0.000597 seconds > OpenGL Dev Render, 1.3e-05 seconds > Interactive Render, 0.01575 seconds > OpenGL Dev Render, 0.000416 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.013086 seconds > OpenGL Dev Render, 0.000416 seconds > OpenGL Dev Render, 1e-05 seconds > Interactive Render, 0.001197 seconds > OpenGL Dev Render, 0.000419 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003291 seconds > OpenGL Dev Render, 0.000426 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.00317 seconds > OpenGL Dev Render, 0.000403 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.004295 seconds > OpenGL Dev Render, 0.000401 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003245 seconds > OpenGL Dev Render, 0.000405 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.002977 seconds > OpenGL Dev Render, 0.000429 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.002985 seconds > OpenGL Dev Render, 0.000425 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003037 seconds > OpenGL Dev Render, 0.000422 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.002937 seconds > OpenGL Dev Render, 0.000428 seconds > OpenGL Dev Render, 1.2e-05 seconds > Interactive Render, 0.003271 seconds > OpenGL Dev Render, 0.000429 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003315 seconds > OpenGL Dev Render, 0.00042 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003297 seconds > OpenGL Dev Render, 0.000419 seconds > OpenGL Dev Render, 1e-05 seconds > Interactive Render, 0.003044 seconds > OpenGL Dev Render, 0.000423 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003032 seconds > OpenGL Dev Render, 0.000429 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003181 seconds > OpenGL Dev Render, 0.000403 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.002899 seconds > OpenGL Dev Render, 0.000435 seconds > OpenGL Dev Render, 1.2e-05 seconds > Interactive Render, 0.003086 seconds > OpenGL Dev Render, 0.000412 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003049 seconds > OpenGL Dev Render, 0.000421 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003163 seconds > OpenGL Dev Render, 0.000418 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003121 seconds > OpenGL Dev Render, 0.00041 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.002943 seconds > OpenGL Dev Render, 0.000412 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003178 seconds > OpenGL Dev Render, 0.00042 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.002917 seconds > OpenGL Dev Render, 0.000444 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.003071 seconds > OpenGL Dev Render, 0.00042 seconds > OpenGL Dev Render, 1.4e-05 seconds > Interactive Render, 0.002949 seconds > OpenGL Dev Render, 0.000426 seconds > OpenGL Dev Render, 1.1e-05 seconds > Interactive Render, 0.00301 se
Re: [Paraview] Latest Git - Mac OS X, error
ender, 3.9e-05 seconds Interactive Render, 3.9e-05 seconds Interactive Render, 3.8e-05 seconds Interactive Render, 4e-05 seconds Interactive Render, 5.5e-05 seconds Interactive Render, 3.9e-05 seconds Interactive Render, 4e-05 seconds Interactive Render, 6e-05 seconds Interactive Render, 3.9e-05 seconds Interactive Render, 4.6e-05 seconds Interactive Render, 4.6e-05 seconds Interactive Render, 3.9e-05 seconds Still Render, 84.5302 seconds Dataserver sending to client, 0.000291 seconds Dataserver sending to client, 79.7789 seconds On 2011-01-28, at 8:24 AM, Pierre-Olivier Dallaire wrote: > In fact, I'm getting the same error under Linux this morning : > > In file included from > /data-cfd01/software/ParaView/Git/ParaView/Servers/Filters/vtkAMRDualContour.cxx:15: > /data-cfd01/software/ParaView/Git/ParaView/Servers/Filters/vtkAMRDualContour.h:179: > error: extra qualification ‘vtkAMRDualContour::’ on member ‘CopyAttributes’ > make[2]: *** > [Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o] Error 1 > > > Begin forwarded message: > >> From: Pierre-Olivier Dallaire >> Date: January 28, 2011 8:22:05 AM EST >> To: ParaView >> Subject: Latest Git - Mac OS X, error >> >> Good day, >> >> I'm trying to build the latest git on Mac and getting this error : >> >> [ 75%] Building CXX object >> Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o >> In file included from >> /Volumes/OpenFOAM/SRC/ParaView_Git/ParaView/Servers/Filters/vtkAMRDualContour.cxx:15: >> /Volumes/OpenFOAM/SRC/ParaView_Git/ParaView/Servers/Filters/vtkAMRDualContour.h:179: >> error: extra qualification 'vtkAMRDualContour::' on member 'CopyAttributes' >> make[2]: *** >> [Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o] Error 1 >> make[1]: *** [Servers/Filters/CMakeFiles/vtkPVFilters.dir/all] Error 2 >> make: *** [all] Error 2 >> >> I never experienced that before. Note that I successfully built it under >> Linux. >> >> Regards, >> >> PO > > ___ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Latest Git - Mac OS X, error
In fact, I'm getting the same error under Linux this morning : In file included from /data-cfd01/software/ParaView/Git/ParaView/Servers/Filters/vtkAMRDualContour.cxx:15: /data-cfd01/software/ParaView/Git/ParaView/Servers/Filters/vtkAMRDualContour.h:179: error: extra qualification ‘vtkAMRDualContour::’ on member ‘CopyAttributes’ make[2]: *** [Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o] Error 1 Begin forwarded message: > From: Pierre-Olivier Dallaire > Date: January 28, 2011 8:22:05 AM EST > To: ParaView > Subject: Latest Git - Mac OS X, error > > Good day, > > I'm trying to build the latest git on Mac and getting this error : > > [ 75%] Building CXX object > Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o > In file included from > /Volumes/OpenFOAM/SRC/ParaView_Git/ParaView/Servers/Filters/vtkAMRDualContour.cxx:15: > /Volumes/OpenFOAM/SRC/ParaView_Git/ParaView/Servers/Filters/vtkAMRDualContour.h:179: > error: extra qualification 'vtkAMRDualContour::' on member 'CopyAttributes' > make[2]: *** > [Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o] Error 1 > make[1]: *** [Servers/Filters/CMakeFiles/vtkPVFilters.dir/all] Error 2 > make: *** [all] Error 2 > > I never experienced that before. Note that I successfully built it under > Linux. > > Regards, > > PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Latest Git - Mac OS X, error
Good day, I'm trying to build the latest git on Mac and getting this error : [ 75%] Building CXX object Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o In file included from /Volumes/OpenFOAM/SRC/ParaView_Git/ParaView/Servers/Filters/vtkAMRDualContour.cxx:15: /Volumes/OpenFOAM/SRC/ParaView_Git/ParaView/Servers/Filters/vtkAMRDualContour.h:179: error: extra qualification 'vtkAMRDualContour::' on member 'CopyAttributes' make[2]: *** [Servers/Filters/CMakeFiles/vtkPVFilters.dir/vtkAMRDualContour.cxx.o] Error 1 make[1]: *** [Servers/Filters/CMakeFiles/vtkPVFilters.dir/all] Error 2 make: *** [all] Error 2 I never experienced that before. Note that I successfully built it under Linux. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] paraview - client-server
Worked, thanks !
I tried different files : couple stls and openfoam cases.
Regards,
PO
On 2010-06-01, at 1:02 PM, burlen wrote:
> Hi,
>
> I have seen this error mostly relating to a plugin being loaded on the client
> side but not the server side. It looks like vtk1DTransferFunctionFilter, is
> part of a PointSprite plugin. You could check the tools->plugin manager
> dialog to see if the client and server have the same plugins loaded?
>
> It would also be helpful to know what type of file have you tried to open?
>
> good luck
> Burlen
>
>
>
> Pierre-Olivier Dallaire wrote:
>> Hi,
>>
>> I'm facing an error under the client-server mode. As soon as I try to open a
>> file, paraview crashes with this error on the
>> server side :
>>
>> ERROR: In /home/podallaire/ParaView/Servers/Common/vtkProcessModule.cxx,
>> line 1065
>> vtkProcessModule (0x851da0): Cannot create object of type
>> "vtk1DTransferFunctionFilter".
>> while processing
>> Message 0 = New
>> Argument 0 = string_value {vtk1DTransferFunctionFilter}
>> Argument 1 = id_value {387}
>>
>>
>> ERROR: In /home/podallaire/ParaView/Servers/Common/vtkProcessModule.cxx,
>> line 1066
>> vtkProcessModule (0x851da0): Aborting execution for debugging purposes.
>>
>>
>>
>>
>> Any idea what is going on ? I tried different files - same result.
>>
>> Regards,
>>
>> PO
>>
>> On 2010-04-30, at 2:49 PM, burlen wrote:
>>
>>
>>> yeah, that's a typo in the bug report. Both last night and this morning I
>>> have been unable to access mantis or the the pv web site. Page never loads.
>>> I'll try later.
>>>
>>> pat marion wrote:
>>>
>>>> Hey Burlen, on the bug report page for 10283, I think you need to fix the
>>>> command line you are testing with :
>>>>
>>>> $ ssh remote cmd1 && cm2
>>>>
>>>> will execute cmd1 on remote and cmd2 locally. It should be:
>>>>
>>>> $ ssh remote "cmd1 && cmd2"
>>>>
>>>> Pat
>>>>
>>>> On Fri, Apr 30, 2010 at 9:12 AM, pat marion >>> <mailto:pat.mar...@kitware.com>> wrote:
>>>>
>>>> I have applied your patch. I agree that paraview should explicity
>>>> close the child process. But... what I am pointing out is that
>>>> calling QProcess::close() does not help in this situation. What I
>>>> am saying is that, even when paraview does kill the process, any
>>>> commands run by ssh on the other side of the netpipe will be
>>>> orphaned by sshd. Are you sure you can't reproduce it?
>>>>
>>>>
>>>> $ ssh localhost sleep 1d
>>>> $ < press control-c >
>>>> $ pidof sleep
>>>> $ # sleep is still running
>>>>
>>>> Pat
>>>>
>>>>
>>>> On Fri, Apr 30, 2010 at 2:08 AM, burlen >>> <mailto:burlen.lor...@gmail.com>> wrote:
>>>>
>>>> Hi Pat,
>>>>
>>>> From my point of view the issue is philosophical, because
>>>> practically speaking I couldn't reproduce the orphans with out
>>>> doing something a little odd namely, ssh ... && sleep 1d.
>>>> Although the fact that a user reported suggests that it may
>>>> occur in the real world as well. The question is this: should
>>>> an application explicitly clean up resources it allocates? or
>>>> should an application rely on the user not only knowing that
>>>> there is the potential for a resource leak but also knowing
>>>> enough to do the right thing to avoid it (eg ssh -tt ...)? In
>>>> my opinion, as a matter of principle, if PV spawns a process
>>>> it should explicitly clean it up and there should be no way it
>>>> can become an orphan. In this case the fact that the orphan
>>>> can hold ports open is particularly insidious, because further
>>>> connection attempt on that port fails with no helpful error
>>>> information. Also it is not very difficult to clean up a
>>>> spawned process. What it comes down to is a little book
>>>> keeping to hang on to the qprocess handle and a few lines of
>>>> code called from pqCommandS
Re: [Paraview] paraview - client-server
Hi,
I'm facing an error under the client-server mode. As soon as I try to open a
file, paraview crashes with this error on the
server side :
ERROR: In /home/podallaire/ParaView/Servers/Common/vtkProcessModule.cxx, line
1065
vtkProcessModule (0x851da0): Cannot create object of type
"vtk1DTransferFunctionFilter".
while processing
Message 0 = New
Argument 0 = string_value {vtk1DTransferFunctionFilter}
Argument 1 = id_value {387}
ERROR: In /home/podallaire/ParaView/Servers/Common/vtkProcessModule.cxx, line
1066
vtkProcessModule (0x851da0): Aborting execution for debugging purposes.
Any idea what is going on ? I tried different files - same result.
Regards,
PO
On 2010-04-30, at 2:49 PM, burlen wrote:
> yeah, that's a typo in the bug report. Both last night and this morning I
> have been unable to access mantis or the the pv web site. Page never loads.
> I'll try later.
>
> pat marion wrote:
>> Hey Burlen, on the bug report page for 10283, I think you need to fix the
>> command line you are testing with :
>>
>> $ ssh remote cmd1 && cm2
>>
>> will execute cmd1 on remote and cmd2 locally. It should be:
>>
>> $ ssh remote "cmd1 && cmd2"
>>
>> Pat
>>
>> On Fri, Apr 30, 2010 at 9:12 AM, pat marion > > wrote:
>>
>>I have applied your patch. I agree that paraview should explicity
>>close the child process. But... what I am pointing out is that
>>calling QProcess::close() does not help in this situation. What I
>>am saying is that, even when paraview does kill the process, any
>>commands run by ssh on the other side of the netpipe will be
>>orphaned by sshd. Are you sure you can't reproduce it?
>>
>>
>>$ ssh localhost sleep 1d
>>$ < press control-c >
>>$ pidof sleep
>>$ # sleep is still running
>>
>>Pat
>>
>>
>>On Fri, Apr 30, 2010 at 2:08 AM, burlen >> wrote:
>>
>>Hi Pat,
>>
>>From my point of view the issue is philosophical, because
>>practically speaking I couldn't reproduce the orphans with out
>>doing something a little odd namely, ssh ... && sleep 1d.
>>Although the fact that a user reported suggests that it may
>>occur in the real world as well. The question is this: should
>>an application explicitly clean up resources it allocates? or
>>should an application rely on the user not only knowing that
>>there is the potential for a resource leak but also knowing
>>enough to do the right thing to avoid it (eg ssh -tt ...)? In
>>my opinion, as a matter of principle, if PV spawns a process
>>it should explicitly clean it up and there should be no way it
>>can become an orphan. In this case the fact that the orphan
>>can hold ports open is particularly insidious, because further
>>connection attempt on that port fails with no helpful error
>>information. Also it is not very difficult to clean up a
>>spawned process. What it comes down to is a little book
>>keeping to hang on to the qprocess handle and a few lines of
>>code called from pqCommandServerStartup destructor to make
>>certain it's cleaned up. This is from the patch I submitted
>>when I filed the bug report.
>>
>>+// close running process
>>+if (this->Process->state()==QProcess::Running)
>>+ {
>>+ this->Process->close();
>>+ }
>>+// free the object
>>+delete this->Process;
>>+this->Process=NULL;
>>
>>I think if the cluster admins out there new which ssh options
>>(GatewayPorts etc) are important for ParView to work
>>seamlessly, then they might be willing to open them up. It's
>>my impression that the folks that build clusters want tools
>>like PV to be easy to use, but they don't necessarily know all
>>the in's and out's of confinguring and running PV.
>>
>>Thanks for looking at this again! The -tt option to ssh is
>>indeed a good find.
>>
>>Burlen
>>
>>pat marion wrote:
>>
>>Hi all!
>>
>>I'm bringing this thread back- I have learned a couple new
>>things...
>>
>>---
>>No more orphans:
>>
>>Here is an easy way to create an orphan:
>>
>> $ ssh localhost sleep 1d
>> $
>>
>>The ssh process is cleaned up, but sshd orphans the sleep
>>process. You can avoid this by adding '-t' to ssh:
>>
>> $ ssh -t localhost sleep 1d
>>
>>Works like a charm! But then there is another problem...
>>try this command from paraview (using QProcess) and it
>>still leaves an orphan, doh! Go back and re-read ssh's
>>man page and you have the solution, use '-t' twice: ssh -tt
[Paraview] PV 3.0 - Color Legend default settings
Hi, is it possible to change the default font and size, color and others for the color legend in ~/.config/ParaView/ParaView3.9.0.ini ? This is something I have been fighting with for some time ... If not possible, where in the source code those values are hard-coded ? The "Make Default" button in the color scale editor does not work for me. Best regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] pvserver : cannot connect to X server
Well it does not solve my problem ... I never had this behaviour before / connecting with X was not necessary. This problem started this week / last week cvs was fine. Any idea why it's causing that ? Thanks PO On 2010-01-27, at 2:43 PM, Pierre-Olivier Dallaire wrote: > I never used the the -X option when connecting with ssh on the server in > order to initialize pvserver. > > I think now the solution is to use the -X but start pvserver with option "-dc" > > PO > On 2010-01-27, at 2:35 PM, Utkarsh Ayachit wrote: > >> Are you sure the display is accessible on the server machine? What >> happens when you open something like gvim? >> >> Utkarsh >> >> On Wed, Jan 27, 2010 at 10:04 AM, Pierre-Olivier Dallaire >> wrote: >>> Hi, >>> >>> when trying to start pvserver on the my ParaView server linux machine, I'm >>> getting this new >>> error with the latest cvs version, error that I never had before : >>> >>> pvserver >>> : cannot connect to X server >>> >>> Thanks! >>> >>> PO >>> ___ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.paraview.org/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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] pvserver : cannot connect to X server
I never used the the -X option when connecting with ssh on the server in order to initialize pvserver. I think now the solution is to use the -X but start pvserver with option "-dc" PO On 2010-01-27, at 2:35 PM, Utkarsh Ayachit wrote: > Are you sure the display is accessible on the server machine? What > happens when you open something like gvim? > > Utkarsh > > On Wed, Jan 27, 2010 at 10:04 AM, Pierre-Olivier Dallaire > wrote: >> Hi, >> >> when trying to start pvserver on the my ParaView server linux machine, I'm >> getting this new >> error with the latest cvs version, error that I never had before : >> >> pvserver >> : cannot connect to X server >> >> Thanks! >> >> PO >> ___ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] pvserver : cannot connect to X server
Hi, when trying to start pvserver on the my ParaView server linux machine, I'm getting this new error with the latest cvs version, error that I never had before : pvserver : cannot connect to X server Thanks! PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] vtkPOpenFOAM reader
Good afternoon, I have noticed last week that Takuya's OpenFOAM reader is now included in the cvs version, which is good ! I know that in the last versions of the reader, a "refresh" button was included in order to reload the case / is this something that could be included in the cvs version as well ? Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Latest CVS - Mac compiling problem
Works / thank you ! On 2010-01-07, at 1:37 PM, Moreland, Kenneth wrote: > Update your CVS and try again. This looks like it is from a problematic > checkin to VTK that has been reverted this morning. > > -Ken > > > On 1/7/10 10:48 AM, "Pierre-Olivier Dallaire" > wrote: > > Gents, > > I'mhaving this error when compiling today's cvs : > > [ 48%] Built target vtkWrapClientServer > Linking CXX shared library ../../../bin/libvtkCommonCS.dylib > Undefined symbols: > "vtkDataSet_Init(vtkClientServerInterpreter*)", referenced from: > vtkPlane_Init(vtkClientServerInterpreter*) in > vtkPlaneClientServer.cxx.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > make[2]: *** [bin/libvtkCommonCS.dylib] Error 1 > make[1]: *** > [Utilities/VTKClientServer/Common/CMakeFiles/vtkCommonCS.dir/all] Error 2 > make: *** [all] Error 2 > > Does not happen under Linux, only under Mac. Any idea ? > > Regards, > > PO > ___ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > > > > Kenneth Moreland > *** Sandia National Laboratories > *** > *** *** *** email: kmo...@sandia.gov > ** *** ** phone: (505) 844-8919 > *** web: http://www.cs.unm.edu/~kmorel > ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Latest CVS - Mac compiling problem
Gents, I'mhaving this error when compiling today's cvs : [ 48%] Built target vtkWrapClientServer Linking CXX shared library ../../../bin/libvtkCommonCS.dylib Undefined symbols: "vtkDataSet_Init(vtkClientServerInterpreter*)", referenced from: vtkPlane_Init(vtkClientServerInterpreter*) in vtkPlaneClientServer.cxx.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [bin/libvtkCommonCS.dylib] Error 1 make[1]: *** [Utilities/VTKClientServer/Common/CMakeFiles/vtkCommonCS.dir/all] Error 2 make: *** [all] Error 2 Does not happen under Linux, only under Mac. Any idea ? Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Client-server mode / data streaming problem
Perfect, works now, thanks ! On 2010-01-05, at 10:36 AM, Utkarsh Ayachit wrote: > That was a nasty one! Thanks for reporting it. I've committed a fix > for this bug. > > /cvsroot/ParaView3/ParaView3/Servers/ServerManager/Resources/rendering.xml,v > <-- Servers/ServerManager/Resources/rendering.xml > new revision: 1.382; previous revision: 1.381 > /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMUnstructuredDataParallelStrategy.cxx,v > <-- Servers/ServerManager/vtkSMUnstructuredDataParallelStrategy.cxx > new revision: 1.5; previous revision: 1.4 > > Utkarsh > > On Mon, Jan 4, 2010 at 3:58 PM, Pierre-Olivier Dallaire > wrote: >> Here is what I get from this test : >> >> Local Process >> Still Render, 0.057886 seconds >>Execute vtkPolyDataMapper id: 413, 1.6e-05 seconds >> Still Render, 0.070324 seconds >>Execute vtkPolyDataMapper id: 413, 1.8e-05 seconds >> Still Render, 0.045106 seconds >>Execute vtkPolyDataMapper id: 413, 2.1e-05 seconds >> Still Render, 0.038055 seconds >>Execute vtkPolyDataMapper id: 413, 2e-05 seconds >> Interactive Render, 42.5521 seconds >>Execute vtkMPIMoveData id: 621, 39.9256 seconds >>Execute vtkMPIMoveData id: 624, 2.30231 seconds >>Execute vtkPolyDataMapper id: 410, 3.5e-05 seconds >>Execute vtkPolyDataMapper id: 410, 1.4e-05 seconds >> Interactive Render, 0.002586 seconds >>Execute vtkPolyDataMapper id: 410, 2.4e-05 seconds >> Interactive Render, 0.001532 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001864 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001908 seconds >>Execute vtkPolyDataMapper id: 410, 2.2e-05 seconds >> Interactive Render, 0.001933 seconds >>Execute vtkPolyDataMapper id: 410, 2.1e-05 seconds >> Interactive Render, 0.001626 seconds >>Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds >> Interactive Render, 0.001455 seconds >>Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds >> Interactive Render, 0.00338 seconds >>Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds >> Interactive Render, 0.001561 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001537 seconds >>Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds >> Interactive Render, 0.001489 seconds >>Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds >> Interactive Render, 0.001558 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001595 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001546 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001454 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001633 seconds >>Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds >> Interactive Render, 0.001517 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001516 seconds >>Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds >> Interactive Render, 0.001481 seconds >>Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds >> Still Render, 33.0572 seconds >>Execute vtkMPIMoveData id: 621, 32.6987 seconds >>Execute vtkPolyDataMapper id: 413, 3e-05 seconds >>Execute vtkPolyDataMapper id: 413, 2.4e-05 seconds >> >> >> >> Server >> Execute vtkQuadricClustering id: 633, 0.125393 seconds >> Execute vtkMPIMoveData id: 621, 39.3476 seconds >>Dataserver sending to client, 39.3474 seconds >> Execute vtkOrderedCompositeDistributor , 7.5e-05 seconds >> Execute vtkMPIMoveData id: 624, 1.88785 seconds >>Dataserver sending to client, 1.88762 seconds >> Execute vtkOrderedCompositeDistributor , 7e-05 seconds >> Execute vtkMPIMoveData id: 621, 32.217 seconds >>Dataserver sending to client, 32.2167 seconds >> Execute vtkOrderedCompositeDistributor , 7.7e-05 seconds >> >> On 2010-01-04, at 3:47 PM, Utkarsh Ayachit wrote: >> >>> Try this: >>> * Open Tools | Timer Log. >>> * Change the "Time Threshold" to "Show All" >>> * Pan etc. then click "Refresh" >>> If there are any entires in there that say "vtkMPIMoveData" it >>> represents a data delivery to the client. >>> * I can see data-delivery happens when I change properties on the >>>
Re: [Paraview] Client-server mode / data streaming problem
Here is what I get from this test : Local Process Still Render, 0.057886 seconds Execute vtkPolyDataMapper id: 413, 1.6e-05 seconds Still Render, 0.070324 seconds Execute vtkPolyDataMapper id: 413, 1.8e-05 seconds Still Render, 0.045106 seconds Execute vtkPolyDataMapper id: 413, 2.1e-05 seconds Still Render, 0.038055 seconds Execute vtkPolyDataMapper id: 413, 2e-05 seconds Interactive Render, 42.5521 seconds Execute vtkMPIMoveData id: 621, 39.9256 seconds Execute vtkMPIMoveData id: 624, 2.30231 seconds Execute vtkPolyDataMapper id: 410, 3.5e-05 seconds Execute vtkPolyDataMapper id: 410, 1.4e-05 seconds Interactive Render, 0.002586 seconds Execute vtkPolyDataMapper id: 410, 2.4e-05 seconds Interactive Render, 0.001532 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001864 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001908 seconds Execute vtkPolyDataMapper id: 410, 2.2e-05 seconds Interactive Render, 0.001933 seconds Execute vtkPolyDataMapper id: 410, 2.1e-05 seconds Interactive Render, 0.001626 seconds Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds Interactive Render, 0.001455 seconds Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds Interactive Render, 0.00338 seconds Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds Interactive Render, 0.001561 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001537 seconds Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds Interactive Render, 0.001489 seconds Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds Interactive Render, 0.001558 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001595 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001546 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001454 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001633 seconds Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds Interactive Render, 0.001517 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001516 seconds Execute vtkPolyDataMapper id: 410, 1.6e-05 seconds Interactive Render, 0.001481 seconds Execute vtkPolyDataMapper id: 410, 1.7e-05 seconds Still Render, 33.0572 seconds Execute vtkMPIMoveData id: 621, 32.6987 seconds Execute vtkPolyDataMapper id: 413, 3e-05 seconds Execute vtkPolyDataMapper id: 413, 2.4e-05 seconds Server Execute vtkQuadricClustering id: 633, 0.125393 seconds Execute vtkMPIMoveData id: 621, 39.3476 seconds Dataserver sending to client, 39.3474 seconds Execute vtkOrderedCompositeDistributor , 7.5e-05 seconds Execute vtkMPIMoveData id: 624, 1.88785 seconds Dataserver sending to client, 1.88762 seconds Execute vtkOrderedCompositeDistributor , 7e-05 seconds Execute vtkMPIMoveData id: 621, 32.217 seconds Dataserver sending to client, 32.2167 seconds Execute vtkOrderedCompositeDistributor , 7.7e-05 seconds On 2010-01-04, at 3:47 PM, Utkarsh Ayachit wrote: > Try this: > * Open Tools | Timer Log. > * Change the "Time Threshold" to "Show All" > * Pan etc. then click "Refresh" > If there are any entires in there that say "vtkMPIMoveData" it > represents a data delivery to the client. > * I can see data-delivery happens when I change properties on the > source, but never when merely interacting with it. > > Utkarsh > > > On Mon, Jan 4, 2010 at 3:39 PM, Pierre-Olivier Dallaire > wrote: >> Hi ! >> >> yes, I'm connecting to a server machine which is running pvserver. The local >> and server machines have exactly >> the same cvs version. >> >> I tried different cases / an easy one was to open an stl file located on the >> server machine side. I'm monitoring the network >> traffic on the client machine. As soon as I try to move/rotate the stl >> geometry, I can see that the download traffic is going up >> and reach the maximum for some time. >> >> Thanks >> >> PO >> >> >> On 2010-01-04, at 3:33 PM, Utkarsh Ayachit wrote: >> >>> So, if I understand correctly, you are using local-rendering mode i.e. >>> deliver data to client and render. How are you determining that the >>> client is re-downloading the data? I just tried with a simple sphere >>> source, and could not reproduce the behavior. >>> >>> Utkarsh >>> >>> On Mon, Jan 4, 2010 at 2:22 PM, Pierre-Olivier Dallaire >>> wrote: >>>> Good afternoon, >>>> >>>> using the latest cvs version, it seems that the client-server m
Re: [Paraview] Client-server mode / data streaming problem
Hi ! yes, I'm connecting to a server machine which is running pvserver. The local and server machines have exactly the same cvs version. I tried different cases / an easy one was to open an stl file located on the server machine side. I'm monitoring the network traffic on the client machine. As soon as I try to move/rotate the stl geometry, I can see that the download traffic is going up and reach the maximum for some time. Thanks PO On 2010-01-04, at 3:33 PM, Utkarsh Ayachit wrote: > So, if I understand correctly, you are using local-rendering mode i.e. > deliver data to client and render. How are you determining that the > client is re-downloading the data? I just tried with a simple sphere > source, and could not reproduce the behavior. > > Utkarsh > > On Mon, Jan 4, 2010 at 2:22 PM, Pierre-Olivier Dallaire > wrote: >> Good afternoon, >> >> using the latest cvs version, it seems that the client-server mode does not >> work as well as before (early december). >> For some reason, every time I try to pan or rotate, the client application >> re-downloads all the data, which was not the case before. >> Using the standard view buttons work properly doe not generate a full >> re-download of the data. With this new behaviour, it's impossible >> to work under the client-server mode. >> >> Suggestions ? >> >> Thanks >> >> PO >> ___ >> 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 >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Client-server mode / data streaming problem
Good afternoon, using the latest cvs version, it seems that the client-server mode does not work as well as before (early december). For some reason, every time I try to pan or rotate, the client application re-downloads all the data, which was not the case before. Using the standard view buttons work properly doe not generate a full re-download of the data. With this new behaviour, it's impossible to work under the client-server mode. Suggestions ? Thanks PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView 3.7 from cvs on Mac OS X, x86_64, Qt 4.5.3 w/Cocoa
Hi, after doing several tests / I found out that QT-4.5.2 does not generate this problem. Everything is ok now. Michael - I tested your git version - the "make dmg" is pretty cool ! Is that something that could be included in the official cvs distribution ? Best regards, PO On 2009-11-19, at 8:22 AM, Michael Wild wrote: > Well, I did some stuff, but the only thing I can say is that I don't see this > problem. As to why this is, I have no idea... I didn't do anything > specifically to fix this. > > Sorry > > Michael > > > On 19. Nov, 2009, at 14:14 , Pierre-Olivier Dallaire wrote: > >> Ok, from this post, I thought that you added some "magic" in the ParaView >> src : >> >> http://www.paraview.org/pipermail/paraview/2009-October/014246.html >> http://github.com/themiwi/ParaView3-enhancements >> >> Have a good day >> >> PO >> >> On 2009-11-18, at 3:54 PM, Michael Wild wrote: >> >>> Uuuhm, I haven't done anything in that respect, sorry. >>> >>> >>> Michael >>> >>> On 18. Nov, 2009, at 20:19 , Pierre-Olivier Dallaire wrote: >>> >>>> Hi all, >>>> >>>> Michael - can you confirm what are the "special" enhancements that take >>>> care >>>> of the greyed out filters problem / I've been fighting with this issue >>>> recently >>>> >>>> I don't see this with the latest qt-4.6.0-rc1 but ParaView is really slow >>>> based on this qt release, >>>> prefer to rely on qt-4.5.3 for now >>>> >>>> Best regards, >>>> >>>> PO >>>> >>>> On 2009-10-30, at 12:06 PM, Chris Kees wrote: >>>> >>>>> Hi all, >>>>> >>>>> Just to add a data point, I compiled dbus and Qt 4.5.3 from source on OS >>>>> X 10.5.8(x86_64) and still have greyed out filters in PV 3.7. I'm >>>>> interested in what the enhancements do as well. >>>>> >>>>> Chris >>>>> On Oct 30, 2009, at 5:47 AM, Takuya OSHIMA wrote: >>>>> >>>>>> Hi Michael & all, >>>>>> >>>>>> With OS X 10.6.1 + Qt 4.5.3/Cocoa/x86_64 + PV 3.7 builds I've run into >>>>>> either the occasional greyed out filters when launched in-place >>>>>> without make install or crashes at startup after make install. So I >>>>>> tried your ParaView3-enhancements >>>>>> ( http://www.paraview.org/pipermail/paraview/2009-October/014246.html ) >>>>>> and indeed it works perfectly at least in builtin server mode after >>>>>> running make install (really great). I wonder what is the secret about >>>>>> your "enhancements"? >>>>>> >>>>>> Takuya >>>>>> >>>>>> Takuya OSHIMA, Ph.D. >>>>>> Faculty of Engineering, Niigata University >>>>>> 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN >>>>>> >>>>>> From: Michael Wild >>>>>> Subject: Re: [Paraview] ParaView 3.7 from cvs on Mac OS X, x86_64, Qt >>>>>> 4.5.3 w/Cocoa >>>>>> Date: Wed, 28 Oct 2009 20:47:31 +0100 >>>>>> >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I've noticed that the filters menu is greyed out after loading a valid >>>>>>>> data set on the version of paraview I built yesterday from cvs (also >>>>>>>> updated yesterday). I have the same version of paraview built on an >>>>>>>> i386 mac using the Qt SDK instead of the Cocoa 32/64 framework, and >>>>>>>> it does not have this problem. Also, the filters appear to work (e.g. >>>>>>>> if I hit the isosurface button the filter runs correctly). Any idea >>>>>>>> what is happening here? I believe somebody mentioned that the QtDBus >>>>>>>> framework is messed up in the Qt Cocoa package, maybe I just need to >>>>>>>> build Qt from source. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Chris >>>>>>> >>>>>>> >>>>>>> Hmm, I built it as a x86_64 binary with Qt-Cocoa 4.5.3 on OS X 10.6 >>
Re: [Paraview] ParaView 3.7 from cvs on Mac OS X, x86_64, Qt 4.5.3 w/Cocoa
Ok, from this post, I thought that you added some "magic" in the ParaView src : http://www.paraview.org/pipermail/paraview/2009-October/014246.html http://github.com/themiwi/ParaView3-enhancements Have a good day PO On 2009-11-18, at 3:54 PM, Michael Wild wrote: > Uuuhm, I haven't done anything in that respect, sorry. > > > Michael > > On 18. Nov, 2009, at 20:19 , Pierre-Olivier Dallaire wrote: > >> Hi all, >> >> Michael - can you confirm what are the "special" enhancements that take care >> of the greyed out filters problem / I've been fighting with this issue >> recently >> >> I don't see this with the latest qt-4.6.0-rc1 but ParaView is really slow >> based on this qt release, >> prefer to rely on qt-4.5.3 for now >> >> Best regards, >> >> PO >> >> On 2009-10-30, at 12:06 PM, Chris Kees wrote: >> >>> Hi all, >>> >>> Just to add a data point, I compiled dbus and Qt 4.5.3 from source on OS X >>> 10.5.8(x86_64) and still have greyed out filters in PV 3.7. I'm interested >>> in what the enhancements do as well. >>> >>> Chris >>> On Oct 30, 2009, at 5:47 AM, Takuya OSHIMA wrote: >>> >>>> Hi Michael & all, >>>> >>>> With OS X 10.6.1 + Qt 4.5.3/Cocoa/x86_64 + PV 3.7 builds I've run into >>>> either the occasional greyed out filters when launched in-place >>>> without make install or crashes at startup after make install. So I >>>> tried your ParaView3-enhancements >>>> ( http://www.paraview.org/pipermail/paraview/2009-October/014246.html ) >>>> and indeed it works perfectly at least in builtin server mode after >>>> running make install (really great). I wonder what is the secret about >>>> your "enhancements"? >>>> >>>> Takuya >>>> >>>> Takuya OSHIMA, Ph.D. >>>> Faculty of Engineering, Niigata University >>>> 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN >>>> >>>> From: Michael Wild >>>> Subject: Re: [Paraview] ParaView 3.7 from cvs on Mac OS X, x86_64, Qt >>>> 4.5.3 w/Cocoa >>>> Date: Wed, 28 Oct 2009 20:47:31 +0100 >>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> I've noticed that the filters menu is greyed out after loading a valid >>>>>> data set on the version of paraview I built yesterday from cvs (also >>>>>> updated yesterday). I have the same version of paraview built on an >>>>>> i386 mac using the Qt SDK instead of the Cocoa 32/64 framework, and >>>>>> it does not have this problem. Also, the filters appear to work (e.g. >>>>>> if I hit the isosurface button the filter runs correctly). Any idea >>>>>> what is happening here? I believe somebody mentioned that the QtDBus >>>>>> framework is messed up in the Qt Cocoa package, maybe I just need to >>>>>> build Qt from source. >>>>>> >>>>>> Thanks, >>>>>> Chris >>>>> >>>>> >>>>> Hmm, I built it as a x86_64 binary with Qt-Cocoa 4.5.3 on OS X 10.6 >>>>> and I don't see this issue. Also, my i386/ppc universal binary built >>>>> against the 10.5 SDK doesn't show this. >>>>> >>>>> Michael >>>>> ___ >>>>> 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 >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://www.paraview.org/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 >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://www.paraview.org/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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView 3.7 from cvs on Mac OS X, x86_64, Qt 4.5.3 w/Cocoa
Hi all, Michael - can you confirm what are the "special" enhancements that take care of the greyed out filters problem / I've been fighting with this issue recently I don't see this with the latest qt-4.6.0-rc1 but ParaView is really slow based on this qt release, prefer to rely on qt-4.5.3 for now Best regards, PO On 2009-10-30, at 12:06 PM, Chris Kees wrote: > Hi all, > > Just to add a data point, I compiled dbus and Qt 4.5.3 from source on OS X > 10.5.8(x86_64) and still have greyed out filters in PV 3.7. I'm interested in > what the enhancements do as well. > > Chris > On Oct 30, 2009, at 5:47 AM, Takuya OSHIMA wrote: > >> Hi Michael & all, >> >> With OS X 10.6.1 + Qt 4.5.3/Cocoa/x86_64 + PV 3.7 builds I've run into >> either the occasional greyed out filters when launched in-place >> without make install or crashes at startup after make install. So I >> tried your ParaView3-enhancements >> ( http://www.paraview.org/pipermail/paraview/2009-October/014246.html ) >> and indeed it works perfectly at least in builtin server mode after >> running make install (really great). I wonder what is the secret about >> your "enhancements"? >> >> Takuya >> >> Takuya OSHIMA, Ph.D. >> Faculty of Engineering, Niigata University >> 8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN >> >> From: Michael Wild >> Subject: Re: [Paraview] ParaView 3.7 from cvs on Mac OS X, x86_64, Qt 4.5.3 >> w/Cocoa >> Date: Wed, 28 Oct 2009 20:47:31 +0100 >> Hi, I've noticed that the filters menu is greyed out after loading a valid data set on the version of paraview I built yesterday from cvs (also updated yesterday). I have the same version of paraview built on an i386 mac using the Qt SDK instead of the Cocoa 32/64 framework, and it does not have this problem. Also, the filters appear to work (e.g. if I hit the isosurface button the filter runs correctly). Any idea what is happening here? I believe somebody mentioned that the QtDBus framework is messed up in the Qt Cocoa package, maybe I just need to build Qt from source. Thanks, Chris >>> >>> >>> Hmm, I built it as a x86_64 binary with Qt-Cocoa 4.5.3 on OS X 10.6 >>> and I don't see this issue. Also, my i386/ppc universal binary built >>> against the 10.5 SDK doesn't show this. >>> >>> Michael >>> ___ >>> 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 >>> >>> Follow this link to subscribe/unsubscribe: >>> http://www.paraview.org/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 >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView3 64-bit on Mac OS X 10.6.1
Good evening, guys, can you confirm if the fixes regarding the OSX bundle creation/installation were included in the current cvs version ? Regards, PO On 2009-11-03, at 7:18 AM, Michael Wild wrote: > > On 3. Nov, 2009, at 11:54 , Elvis Dowson wrote: > >> Hi Michael, >> >> On Nov 3, 2009, at 12:20 PM, Michael Wild wrote: >> >>> Yes, I also had this problem, and so did others: >>> http://markmail.org/thread/eneuve2yoemzube7 >>> >>> I had to use the patches at the end of the message. Essentially they copy >>> the qt_menu.nib to the applications resources folder and create an empty >>> qt.conf to prevent loading of image plugins by Qt. >>> >>> The reason that CMake doesn't copy the whole frameworks is space. It tries >>> very hard to only copy things that are actually required to run ParaView. >>> All the development files (e.g. header files) is just useless junk when it >>> comes to running the program. The qt_menu.nib is a recent addition >>> introduced by Qt-Cocoa and hasn't made it into the CMake scripts yet. >> >> >> Why don't you submit this patch to the cvs repository, 'cos I'm sure >> everyone else will face the same problem!! :-) Lost 5 to 6 days because of >> this one!! :-) >> >> Best regards, >> >> Elvis > > > I didn't have the time so far to clean it up, sorry. I'm doing so now, and > will then submit to the bug tracker. > > > Michael > ___ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Snow Leopard
I tried the latest svn with qt cocoa 64 bits and it compiled without any problem. I can run from the build directory but the application is broken Thanks ! PO On 2009-09-20, at 7:30 PM, Berk Geveci wrote: I did not try but I'd give it a 5% chance of working :-) Let us know if you encounter any issues. On Sat, Sep 19, 2009 at 10:16 PM, Pierre-Olivier Dallaire wrote: Nice, thanks ! Does "make install" generates a working app ? Best regards, PO On 2009-09-19, at 10:14 PM, Berk Geveci wrote: I already compiled with Qt 4.5.2, Carbon and Cocoa (32 and 64 bit), on Snow Leopard. It works fine. When compiling with Carbon, you need to set the C and CXX flags to have -m32 manually. We'll fix that in time. Make sure to use the cvs if you want the Cocoa support. I committed a patch last week. The progress bar does not work with Cocoa. We will fix that soon. -berk On Sat, Sep 19, 2009 at 7:58 PM, Pierre-Olivier Dallaire wrote: Hi guys, just curious to see what is the status of ParaView relating to Snow Leopard support. Best regards, PO On 2009-09-09, at 8:35 AM, Dave Partyka wrote: We are in the process of getting a Snow Leopard dashboard up and running as of yesterday. It seems that cmake may need some adjustments as well. On Wed, Sep 9, 2009 at 7:21 AM, Pierre-Olivier Dallaire wrote: Hi, just wanted to know if somebody tried and had success compiling ParaView on the new Snow Leopard OS X ? From my side, I have downloaded and compiled qt-4.6.0 / however, I forgot to compile it for cocoa which I will do today. Next step will be to patch the paraview source code following our previous discussions for Cocoa. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Snow Leopard
Nice, thanks ! Does "make install" generates a working app ? Best regards, PO On 2009-09-19, at 10:14 PM, Berk Geveci wrote: I already compiled with Qt 4.5.2, Carbon and Cocoa (32 and 64 bit), on Snow Leopard. It works fine. When compiling with Carbon, you need to set the C and CXX flags to have -m32 manually. We'll fix that in time. Make sure to use the cvs if you want the Cocoa support. I committed a patch last week. The progress bar does not work with Cocoa. We will fix that soon. -berk On Sat, Sep 19, 2009 at 7:58 PM, Pierre-Olivier Dallaire wrote: Hi guys, just curious to see what is the status of ParaView relating to Snow Leopard support. Best regards, PO On 2009-09-09, at 8:35 AM, Dave Partyka wrote: We are in the process of getting a Snow Leopard dashboard up and running as of yesterday. It seems that cmake may need some adjustments as well. On Wed, Sep 9, 2009 at 7:21 AM, Pierre-Olivier Dallaire wrote: Hi, just wanted to know if somebody tried and had success compiling ParaView on the new Snow Leopard OS X ? From my side, I have downloaded and compiled qt-4.6.0 / however, I forgot to compile it for cocoa which I will do today. Next step will be to patch the paraview source code following our previous discussions for Cocoa. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Snow Leopard
Hi guys, just curious to see what is the status of ParaView relating to Snow Leopard support. Best regards, PO On 2009-09-09, at 8:35 AM, Dave Partyka wrote: We are in the process of getting a Snow Leopard dashboard up and running as of yesterday. It seems that cmake may need some adjustments as well. On Wed, Sep 9, 2009 at 7:21 AM, Pierre-Olivier Dallaire > wrote: Hi, just wanted to know if somebody tried and had success compiling ParaView on the new Snow Leopard OS X ? From my side, I have downloaded and compiled qt-4.6.0 / however, I forgot to compile it for cocoa which I will do today. Next step will be to patch the paraview source code following our previous discussions for Cocoa. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Snow Leopard
Thanks for your comments ! Yesterday I have compiled QT 4.6 with cocoa and arch x86_64 using gcc 4.2 / no problem, no patch needed. After, I patched my 2-3 month old ParaView 3.7.0 source, I compiled it with this QT version and cmake 2.6.4. and it worked. The patch that I applied is basically what Mike was proposing couple months ago. However, the make install did not provide a functional application but I can run ParaView from the build directory. PO On 2009-09-10, at 10:15 AM, Berk Geveci wrote: I compiled a working ParaView on Snow Leopard using Qt 4.5.2 (Carbon, which is the default configuration). I had to set -m32 (-arch i386 should also work) for CMAKE_C_FLAGS and CMAKE_CXX_FLAGS since the latest Xcode builds 64 bit by default. There are some glitches in combo boxes but it works fine otherwise. I also built 64 bit with Qt 4.5.2 (Cocoa) but I had to apply some patches that were posted on this list before. Once I make sure that the patches work with Cocoa and Carbon, I will commit them. If anyone tried the Qt 4.6 preview, please let us know. Qt 4.5.3 is going to have Snow Leopard support also. On Wed, Sep 9, 2009 at 10:11 AM, Michael Jackson wrote: Does Qt 4.5.2 not work under Snow Leopard? I would think under Snow Leopard you just need to add some more flags to the "configure" command since 10.6 is going to make 64 bit binaries by default you probably just need to add the "-arch i386 -arch x86_64" and the -cocoa flags to the Qt configure command. There are some issues with CMake under 10.6 but nothing that can not be worked around from what I can tell. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On Sep 9, 2009, at 7:21 AM, Pierre-Olivier Dallaire wrote: Hi, just wanted to know if somebody tried and had success compiling ParaView on the new Snow Leopard OS X ? From my side, I have downloaded and compiled qt-4.6.0 / however, I forgot to compile it for cocoa which I will do today. Next step will be to patch the paraview source code following our previous discussions for Cocoa. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Snow Leopard
that is what I found yesterday on this subject : http://labs.trolltech.com/blogs/2009/08/31/qt-46-on-mac-os-106/ On 2009-09-09, at 10:11 AM, Michael Jackson wrote: Does Qt 4.5.2 not work under Snow Leopard? I would think under Snow Leopard you just need to add some more flags to the "configure" command since 10.6 is going to make 64 bit binaries by default you probably just need to add the "-arch i386 -arch x86_64" and the - cocoa flags to the Qt configure command. There are some issues with CMake under 10.6 but nothing that can not be worked around from what I can tell. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On Sep 9, 2009, at 7:21 AM, Pierre-Olivier Dallaire wrote: Hi, just wanted to know if somebody tried and had success compiling ParaView on the new Snow Leopard OS X ? From my side, I have downloaded and compiled qt-4.6.0 / however, I forgot to compile it for cocoa which I will do today. Next step will be to patch the paraview source code following our previous discussions for Cocoa. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Snow Leopard
Great ! Let us know when it's ready to test. Regards, PO On 2009-09-09, at 8:35 AM, Dave Partyka wrote: We are in the process of getting a Snow Leopard dashboard up and running as of yesterday. It seems that cmake may need some adjustments as well. On Wed, Sep 9, 2009 at 7:21 AM, Pierre-Olivier Dallaire > wrote: Hi, just wanted to know if somebody tried and had success compiling ParaView on the new Snow Leopard OS X ? From my side, I have downloaded and compiled qt-4.6.0 / however, I forgot to compile it for cocoa which I will do today. Next step will be to patch the paraview source code following our previous discussions for Cocoa. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Snow Leopard
Hi, just wanted to know if somebody tried and had success compiling ParaView on the new Snow Leopard OS X ? From my side, I have downloaded and compiled qt-4.6.0 / however, I forgot to compile it for cocoa which I will do today. Next step will be to patch the paraview source code following our previous discussions for Cocoa. Regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView Mac OS X and Cocoa ... again
I added "-framework CoreFoundation -framework CoreServices" in Servers/ Common/CMakeFiles/vtkPVServerCommon.dir/link.txt and everything compiled and I was able to run ParaView from the build directory- thanks again ! I will start to add things, i.e., python, mpi, ... However, I believe some adjustments will be needed for the bundle creation when doing "make install"; I received this error when starting ParaView with "/Applications/ParaView\ 3.7.0.app/ Contents/MacOS/paraview " : Qt internal error: qt_menu.nib could not be loaded. The .nib file should be placed in QtGui.framework/Versions/Current/Resources/ or in the resources directory of your application bundle. Abort trap PO On 2-Aug-09, at 10:12 AM, Mike Jackson wrote: Well it looks like there may be some missing libraries that are needed by the linker. The _CF* stuff is either in the Carbon library or the AppFramework so maybe the cmake files need to be updated to allow the vtkPVServerCommon to be linked against some OS X specific frameworks. Mike On Sun, Aug 2, 2009 at 8:06 AM, Pierre-Olivier Dallaire wrote: Here is what I get, thanks ! Linking CXX shared library ../../bin/libvtkPVServerCommon.dylib cd /Volumes/OpenFOAM1.6/SRC/build/Servers/Common && /opt/cmake-2.6.4/bin/cmake -E cmake_link_script CMakeFiles/vtkPVServerCommon.dir/link.txt --verbose=1 /usr/bin/g++-4.2 -arch x86_64 -isysroot /Developer/SDKs/ MacOSX10.5.sdk -Wno-deprecated -O3 -DNDEBUG -dynamiclib - headerpad_max_install_names -o ../../bin/libvtkPVServerCommon.dylib -install_name /Volumes/OpenFOAM1.6/SRC/build/bin/libvtkPVServerCommon.dylib CMakeFiles/vtkPVServerCommon.dir/vtkCacheSizeKeeper.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkCellIntegrator.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkClientConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkConnectionIterator.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkMPISelfConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkMultiProcessControllerHelper.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPriorityHelper.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkProcessModuleConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkProcessModuleConnectionManager.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkProcessModule.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkProcessModuleGUIHelper.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVAlgorithmPortsInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVArrayInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVCacheSizeInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVClassNameInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkPVClientServerIdCollectionInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVCompositeDataInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkPVCompositeDataInformationIterator.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVDataInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkPVDataSetAttributesInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVDataSizeInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVDisplayInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVEnvironmentInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkPVEnvironmentInformationHelper.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVFileInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVFileInformationHelper.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkPVGenericAttributeInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkPVOpenGLExtensionsInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVPluginLoader.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVProgressHandler.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVPythonModule.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVSelectionInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVServerInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVServerOptions.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVSILInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVTestUtilities.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVTimerInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkRemoteConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkSelectionConverter.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkSelectionSerializer.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkSelfConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkServerConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkStringList.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkSynchronousMPISelfConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkUndoElement.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkUndoSet.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkUndoStack.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkMPIMToNSocketConnection.cxx.o CMakeFiles/vtkPVServerCommon.dir/ vtkMPIMToNSocketConnectionPortInformation.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkPVServerSocket.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkCommandOptions.cxx.o CMakeFiles/vtkPVServerCommon.dir/vtkCo
Re: [Paraview] ParaView Mac OS X and Cocoa ... again
../ bin/libvtkRendering.pv3.7.dylib ../../bin/ libvtkGraphics.pv3.7.dylib ../../bin/libvtkverdict.pv3.7.dylib ../../ bin/libvtkImaging.pv3.7.dylib ../../bin/libvtkftgl.pv3.7.dylib ../../ bin/libvtkfreetype.pv3.7.dylib ../../bin/ libvtklibxml2.pv3.7.dylib ../../bin/libvtkalglib.pv3.7.dylib ../../bin/ libvtkFilteringCS.dylib ../../bin/libvtkCommonCS.dylib ../../bin/ libvtkClientServer.dylib -lm ../../bin/libvtkIO.pv3.7.dylib ../../bin/ libvtkzlib.pv3.7.dylib ../../bin/libvtkFiltering.pv3.7.dylib ../../bin/ libvtkCommon.pv3.7.dylib ../../bin/libvtksys.pv3.7.dylib ../../bin/ libvtkDICOMParser.pv3.7.dylib ../../bin/libvtkNetCDF.pv3.7.dylib ../../ bin/libvtkmetaio.pv3.7.dylib ../../bin/libvtksqlite.pv3.7.dylib ../../ bin/libvtkpng.pv3.7.dylib ../../bin/libvtkjpeg.pv3.7.dylib ../../bin/ libvtktiff.pv3.7.dylib ../../bin/libvtkexpat.pv3.7.dylib On 2-Aug-09, at 12:38 AM, Mike Jackson wrote: Run "make VERBOSE=1" and post only the final link command. I have an idea what it might be. Mike jackson Sent from my iPod On Aug 1, 2009, at 22:57, Pierre-Olivier Dallaire > wrote: Good evening, I have slightly modified the patch from http://markmail.org/thread/m2asfe3wod52k2ym and applied it on the cvs paraview. This error occurs : [ 71%] Building CXX object Servers/Common/CMakeFiles/ vtkPVServerCommon.dir/vtkPVServerCommonInstantiator.cxx.o Linking CXX shared library ../../bin/libvtkPVServerCommon.dylib Undefined symbols: "_CFStringCreateWithCharacters", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_DisposeHandle", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_kCFAllocatorDefault", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_NewHandle", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_FSResolveAlias", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFStringGetLength", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_FSGetVolumeInfo", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFStringGetTypeID", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFRelease", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFGetTypeID", referenced from: and more ... ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [bin/libvtkPVServerCommon.dylib] Error 1 make[1]: *** [Servers/Common/CMakeFiles/vtkPVServerCommon.dir/all] Error 2 make: *** [all] Error 2 any idea / is it only related to Mac OS X ? Regards, PO On 31-Jul-09, at 5:01 PM, Berk Geveci wrote: Mike, I would like to have the cvs ParaView working with Cocoa (hopefully while still preserving Carbon build functionality). Do you have patches to do this? If not, can we work together to get this working? Thanks, -berk On Fri, Jul 31, 2009 at 4:52 PM, Michael Jackson wrote: Index: CMakeLists.txt === RCS file: /cvsroot/ParaView3/ParaView3/CMakeLists.txt,v retrieving revision 1.97.2.1 diff -u -r1.97.2.1 CMakeLists.txt --- CMakeLists.txt 18 May 2009 20:34:23 - 1.97.2.1 +++ CMakeLists.txt 11 Jun 2009 18:20:48 - @@ -106,10 +106,13 @@ ENDIF (NOT qt_version4_x_tmp) ENDIF (NOT qt_version_tmp) # enforce Carbon in VTK for Qt/Mac -IF(Q_WS_MAC) +IF(Q_WS_MAC AND QT_MAC_USE_COCOA) + SET(VTK_USE_CARBON OFF CACHE BOOL "Build VTK with Carbon" FORCE) + SET(VTK_USE_COCOA ON CACHE BOOL "Build VTK with Cocoa" FORCE) +ELSE(Q_WS_MAC AND QT_MAC_USE_COCOA) SET(VTK_USE_CARBON ON CACHE BOOL "Build VTK with Carbon" FORCE) SET(VTK_USE_COCOA OFF CACHE BOOL "Build VTK with Cocoa" FORCE) -ENDIF(Q_WS_MAC) +ENDIF(Q_WS_MAC AND QT_MAC_USE_COCOA) ENDIF(NOT QT4_FOUND) ELSE (PARAVIEW_BUILD_QT_GUI) SET(VTK_USE_QT OFF CACHE BOOL "Build VTK with Qt Support&qu
Re: [Paraview] ParaView Mac OS X and Cocoa ... again
Good evening, I have slightly modified the patch from http://markmail.org/thread/m2asfe3wod52k2ym and applied it on the cvs paraview. This error occurs : [ 71%] Building CXX object Servers/Common/CMakeFiles/ vtkPVServerCommon.dir/vtkPVServerCommonInstantiator.cxx.o Linking CXX shared library ../../bin/libvtkPVServerCommon.dylib Undefined symbols: "_CFStringCreateWithCharacters", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_DisposeHandle", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_kCFAllocatorDefault", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_NewHandle", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_FSResolveAlias", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFStringGetLength", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_FSGetVolumeInfo", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFStringGetTypeID", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFRelease", referenced from: vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o vtkPVFileInformation::GetSpecialDirectories() in vtkPVFileInformation.cxx.o "_CFGetTypeID", referenced from: and more ... ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [bin/libvtkPVServerCommon.dylib] Error 1 make[1]: *** [Servers/Common/CMakeFiles/vtkPVServerCommon.dir/all] Error 2 make: *** [all] Error 2 any idea / is it only related to Mac OS X ? Regards, PO On 31-Jul-09, at 5:01 PM, Berk Geveci wrote: Mike, I would like to have the cvs ParaView working with Cocoa (hopefully while still preserving Carbon build functionality). Do you have patches to do this? If not, can we work together to get this working? Thanks, -berk On Fri, Jul 31, 2009 at 4:52 PM, Michael Jackson wrote: Index: CMakeLists.txt === RCS file: /cvsroot/ParaView3/ParaView3/CMakeLists.txt,v retrieving revision 1.97.2.1 diff -u -r1.97.2.1 CMakeLists.txt --- CMakeLists.txt 18 May 2009 20:34:23 - 1.97.2.1 +++ CMakeLists.txt 11 Jun 2009 18:20:48 - @@ -106,10 +106,13 @@ ENDIF (NOT qt_version4_x_tmp) ENDIF (NOT qt_version_tmp) # enforce Carbon in VTK for Qt/Mac -IF(Q_WS_MAC) +IF(Q_WS_MAC AND QT_MAC_USE_COCOA) + SET(VTK_USE_CARBON OFF CACHE BOOL "Build VTK with Carbon" FORCE) + SET(VTK_USE_COCOA ON CACHE BOOL "Build VTK with Cocoa" FORCE) +ELSE(Q_WS_MAC AND QT_MAC_USE_COCOA) SET(VTK_USE_CARBON ON CACHE BOOL "Build VTK with Carbon" FORCE) SET(VTK_USE_COCOA OFF CACHE BOOL "Build VTK with Cocoa" FORCE) -ENDIF(Q_WS_MAC) +ENDIF(Q_WS_MAC AND QT_MAC_USE_COCOA) ENDIF(NOT QT4_FOUND) ELSE (PARAVIEW_BUILD_QT_GUI) SET(VTK_USE_QT OFF CACHE BOOL "Build VTK with Qt Support" FORCE) Index: Qt/Widgets/pqProgressBarHelper.cxx === Here is patch (kinda crappy I know.. ) but if you can pick through it you can see what you will need to change. I think there may be some other problems but get this put in place and try the build again. I _do_ have a functioning PV 3.6 64 Bit Cocoa build running on OS X intel (Mac Pro) so I know it works. Good Luck. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Software www.bluequartz.net Principal Software Engineer Dayton, Ohio On Jul 31, 2009, at 3:27 PM, Pierre-Olivier Dallaire wrote: Good afternoon, I'm tryig to get a fully functional paraview installation based on qt cocoa 64. Here are the steps that I have followed : 0) Compile a fresh version of cmake-2.6.4 1) Compile QT with Cocoa option and arch x86_64 / this worked without problem 2) Configure paraview using BUILD_SHARED_LIBS:BOOL=ON, CMAKE_OSX_ARCHITECTURES:STRING=x86_6
Re: [Paraview] ParaView Mac OS X and Cocoa ... again
Gents, thank you very much for your support, I will try again tonight. Regards, PO On 31-Jul-09, at 5:01 PM, Berk Geveci wrote: Mike, I would like to have the cvs ParaView working with Cocoa (hopefully while still preserving Carbon build functionality). Do you have patches to do this? If not, can we work together to get this working? Thanks, -berk On Fri, Jul 31, 2009 at 4:52 PM, Michael Jackson wrote: Index: CMakeLists.txt === RCS file: /cvsroot/ParaView3/ParaView3/CMakeLists.txt,v retrieving revision 1.97.2.1 diff -u -r1.97.2.1 CMakeLists.txt --- CMakeLists.txt 18 May 2009 20:34:23 - 1.97.2.1 +++ CMakeLists.txt 11 Jun 2009 18:20:48 - @@ -106,10 +106,13 @@ ENDIF (NOT qt_version4_x_tmp) ENDIF (NOT qt_version_tmp) # enforce Carbon in VTK for Qt/Mac -IF(Q_WS_MAC) +IF(Q_WS_MAC AND QT_MAC_USE_COCOA) + SET(VTK_USE_CARBON OFF CACHE BOOL "Build VTK with Carbon" FORCE) + SET(VTK_USE_COCOA ON CACHE BOOL "Build VTK with Cocoa" FORCE) +ELSE(Q_WS_MAC AND QT_MAC_USE_COCOA) SET(VTK_USE_CARBON ON CACHE BOOL "Build VTK with Carbon" FORCE) SET(VTK_USE_COCOA OFF CACHE BOOL "Build VTK with Cocoa" FORCE) -ENDIF(Q_WS_MAC) +ENDIF(Q_WS_MAC AND QT_MAC_USE_COCOA) ENDIF(NOT QT4_FOUND) ELSE (PARAVIEW_BUILD_QT_GUI) SET(VTK_USE_QT OFF CACHE BOOL "Build VTK with Qt Support" FORCE) Index: Qt/Widgets/pqProgressBarHelper.cxx === Here is patch (kinda crappy I know.. ) but if you can pick through it you can see what you will need to change. I think there may be some other problems but get this put in place and try the build again. I _do_ have a functioning PV 3.6 64 Bit Cocoa build running on OS X intel (Mac Pro) so I know it works. Good Luck. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On Jul 31, 2009, at 3:27 PM, Pierre-Olivier Dallaire wrote: Good afternoon, I'm tryig to get a fully functional paraview installation based on qt cocoa 64. Here are the steps that I have followed : 0) Compile a fresh version of cmake-2.6.4 1) Compile QT with Cocoa option and arch x86_64 / this worked without problem 2) Configure paraview using BUILD_SHARED_LIBS:BOOL=ON, CMAKE_OSX_ARCHITECTURES:STRING=x86_64, VTK_USE_CARBON:BOOL=OFF and VTK_USE_COCOA:BOOL=ON When re-running cmake to take into account my new settings, VTK_USE_CARBON switches back to ON and VTK_USE_COCOA to OFF. However, my qt cocoa flavor is found by cmake ; -- Looking for QT_MAC_USE_COCOA -- Looking for QT_MAC_USE_COCOA - found -- Found Qt-Version 4.5.2 What is the problem here / it seems that ParaView does want to use cocoa ??? Thanks ! PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] ParaView Mac OS X and Cocoa ... again
Good afternoon, I'm tryig to get a fully functional paraview installation based on qt cocoa 64. Here are the steps that I have followed : 0) Compile a fresh version of cmake-2.6.4 1) Compile QT with Cocoa option and arch x86_64 / this worked without problem 2) Configure paraview using BUILD_SHARED_LIBS:BOOL=ON, CMAKE_OSX_ARCHITECTURES:STRING=x86_64, VTK_USE_CARBON:BOOL=OFF and VTK_USE_COCOA:BOOL=ON When re-running cmake to take into account my new settings, VTK_USE_CARBON switches back to ON and VTK_USE_COCOA to OFF. However, my qt cocoa flavor is found by cmake ; -- Looking for QT_MAC_USE_COCOA -- Looking for QT_MAC_USE_COCOA - found -- Found Qt-Version 4.5.2 What is the problem here / it seems that ParaView does want to use cocoa ??? Thanks ! PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView3 64Bit Experiment
Yes, works from the build directory ! On 12-Apr-09, at 10:32 AM, Michael Jackson wrote: I would try running ParaView from the build directory first before doing an "installation" or anything else. When a "make install" is performed there are lots of "fixups" to the frameworks and dylibs that are either produced or used by paraview. If one of these got missed then that might lead to what you are seeing. So try running from the build directory and lets see where that gets you.. --- Mike Jackson www.bluequartz.net On Apr 11, 2009, at 10:37 PM, Pierre-Olivier Dallaire wrote: Thanks guys / I forgot to change CMAKE_OSX_ARCHITECTURES ! I was able to build paraview 32 and 64 bit. However, I have this error when launching : Unimac:~ podallaire$ /Applications/ParaView\ 3.5.0.app/Contents/ MacOS/paraview objc[83608]: Class QMacSoundDelegate is implemented in both /opt/ qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaPanel is implemented in both /opt/qt-4.5.0- cocoa/lib/QtGui.framework/Versions/4/QtGui and /Applications/ ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/ Versions/4/QtGui. Using implementation from /Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/ QtGui. objc[83608]: Class QCocoaView is implemented in both /opt/qt-4.5.0- cocoa/lib/QtGui.framework/Versions/4/QtGui and /Applications/ ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/ Versions/4/QtGui. Using implementation from /Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/ QtGui. objc[83608]: Class QCocoaWindow is implemented in both /opt/ qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaWindowDelegate is implemented in both /opt/ qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaMenuLoader is implemented in both /opt/ qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaApplicationDelegate is implemented in both /opt/qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaToolBarDelegate is implemented in both / opt/qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaMenu is implemented in both /opt/qt-4.5.0- cocoa/lib/QtGui.framework/Versions/4/QtGui and /Applications/ ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/ Versions/4/QtGui. Using implementation from /Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/ QtGui. objc[83608]: Class QCocoaColorPanelDelegate is implemented in both / opt/qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QNSOpenSavePanelDelegate is implemented in both / opt/qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaFontPanelDelegate is implemented in both / opt/qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/Par
Re: [Paraview] ParaView3 64Bit Experiment
from /Applications/ParaView 3.5.0.app/ Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaPageLayoutDelegate is implemented in both / opt/qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QCocoaPrintPanelDelegate is implemented in both / opt/qt-4.5.0-cocoa/lib/QtGui.framework/Versions/4/QtGui and / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. Using implementation from / Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/ QtGui.framework/Versions/4/QtGui. objc[83608]: Class QNSMenu is implemented in both /opt/qt-4.5.0-cocoa/ lib/QtGui.framework/Versions/4/QtGui and /Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/ QtGui. Using implementation from /Applications/ParaView 3.5.0.app/ Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui. objc[83608]: Class QNSStatusItem is implemented in both /opt/qt-4.5.0- cocoa/lib/QtGui.framework/Versions/4/QtGui and /Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/ QtGui. Using implementation from /Applications/ParaView 3.5.0.app/ Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui. objc[83608]: Class QNSImageView is implemented in both /opt/qt-4.5.0- cocoa/lib/QtGui.framework/Versions/4/QtGui and /Applications/ParaView 3.5.0.app/Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/ QtGui. Using implementation from /Applications/ParaView 3.5.0.app/ Contents/MacOS/../Frameworks/QtGui.framework/Versions/4/QtGui. QApplication::qAppName: Please instantiate the QApplication object first QPixmap: Must construct a QApplication before a QPaintDeviceAbort trap Do I need to patch something else ? Regards, PO On 11-Apr-09, at 3:26 PM, Michael Jackson wrote: You need to set the CMAKE_OSX_ARCHITECTURES to x86_64. By default they build as i386 (32 bit) I would also suggest NOT building with Python at first. See if you can actually get the 64 bit to build first, then start adding things. I have already run into a number of issues with the cocoa build of Qt 4.5. QTreeViews do not respond to user clicks and there are also menu issues within applications. Drag and Drop seems pretty buggy also. I think I'll probably wait for the next few point releases in Qt 4.5 before trying again. Good luck. Keep the list posted on how things go as there are more than a few people interested in the technology. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On Apr 11, 2009, at 11:22 AM, Pierre-Olivier Dallaire wrote: 4) In the configuration process, enabled VTK_USE_64BIT_IDS, BUILD_SHARED_LIBS and PARAVIEW_ENABLE_PYTHON ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] ParaView3 64Bit Experiment
thanks for your comment Mike / am I missing a flag ??? On 11-Apr-09, at 12:36, Mike Jackson wrote: Looks like the qt libs are not 64 bit. Sent from my iPod Mike Jackson On Apr 11, 2009, at 11:22, Pierre-Olivier Dallaire > wrote: Good morning, I've been trying to compile ParaView with Cocoa 64Bit support over the last few day using the instructions from the previous posts in the thread http://www.paraview.org/pipermail/paraview/2009-March/011281.html Basically I have : 1) Compiled qt-4.5 using flags -cocoa and -arch x86_64 2) Compiled cmake-2.6.3 3) Downloaded ParaView from CVS and applied patches pv-cocoa.patch and qt-cocoa.patch 4) In the configuration process, enabled VTK_USE_64BIT_IDS, BUILD_SHARED_LIBS and PARAVIEW_ENABLE_PYTHON I have the following errors when compiling : [ 44%] Built target vtkViewsPython Linking CXX shared library ../../../../bin/libvtkQtChart.dylib ld warning: in /opt/qt-4.5.0-64/lib/QtGui.framework/QtGui, file is not of required architecture ld warning: in /opt/qt-4.5.0-64/lib/QtSql.framework/QtSql, file is not of required architecture ld warning: in /opt/qt-4.5.0-64/lib/QtCore.framework/QtCore, file is not of required architecture Undefined symbols: "QVariant::QVariant(QDate const&)", referenced from: vtkQtChartAxisDomain::mergeDateRange(QList const&) in vtkQtChartAxisDomain.o vtkQtChartAxisDomain::mergeDateRange(QList const&) in vtkQtChartAxisDomain.o vtkQtChartSeriesModelRange::computeSeriesRange(int, int)in vtkQtChartSeriesModelRange.o ... Any idea or suggestions ? Best regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] ParaView3 64Bit Experiment
Good morning, I've been trying to compile ParaView with Cocoa 64Bit support over the last few day using the instructions from the previous posts in the thread http://www.paraview.org/pipermail/paraview/2009-March/011281.html Basically I have : 1) Compiled qt-4.5 using flags -cocoa and -arch x86_64 2) Compiled cmake-2.6.3 3) Downloaded ParaView from CVS and applied patches pv-cocoa.patch and qt-cocoa.patch 4) In the configuration process, enabled VTK_USE_64BIT_IDS, BUILD_SHARED_LIBS and PARAVIEW_ENABLE_PYTHON I have the following errors when compiling : [ 44%] Built target vtkViewsPython Linking CXX shared library ../../../../bin/libvtkQtChart.dylib ld warning: in /opt/qt-4.5.0-64/lib/QtGui.framework/QtGui, file is not of required architecture ld warning: in /opt/qt-4.5.0-64/lib/QtSql.framework/QtSql, file is not of required architecture ld warning: in /opt/qt-4.5.0-64/lib/QtCore.framework/QtCore, file is not of required architecture Undefined symbols: "QVariant::QVariant(QDate const&)", referenced from: vtkQtChartAxisDomain::mergeDateRange(QList const&) in vtkQtChartAxisDomain.o vtkQtChartAxisDomain::mergeDateRange(QList const&) in vtkQtChartAxisDomain.o vtkQtChartSeriesModelRange::computeSeriesRange(int, int)in vtkQtChartSeriesModelRange.o ... Any idea or suggestions ? Best regards, PO ___ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Windows / building error on pqCommandServerStartup
Hi, I'm trying to build ParaView on Windows using MinGW - does anybody had this error in the past / not sure what to do at this point : [ 90%] Building CXX object Qt/Core/CMakeFiles/pqCore.dir/ pqCommandServerStartup.obj In file included from C:/MinGW/bin/../lib/gcc/ mingw32/3.4.5/../../../../include/windows.h:50, from C:/MinGW/bin/../lib/gcc/ mingw32/3.4.5/../../../../include/winsock2.h:22, from C:\Documents and Settings\podallaire\Desktop \ParaView3\Qt\Core\pqCommandServerStartup.cxx:39: C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1663: error: declaration of C function `LONG InterlockedCompar eExchange(volatile LONG*, LONG, LONG)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 387: error: previous declaration `long int InterlockedCompareE xchange(long int*, long int, long int)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1667: error: declaration of C function `LONG InterlockedDecrem ent(volatile LONG*)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 389: error: previous declaration `long int InterlockedDecremen t(long int*)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1668: error: declaration of C function `LONG InterlockedExchan ge(volatile LONG*, LONG)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 390: error: previous declaration `long int InterlockedExchange (long int*, long int)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1672: error: declaration of C function `LONG InterlockedExchan geAdd(volatile LONG*, LONG)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 391: error: previous declaration `long int InterlockedExchange Add(long int*, long int)' here C:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/winbase.h: 1676: error: declaration of C function `LONG InterlockedIncrem ent(volatile LONG*)' conflicts with C:/Qt/4.4.3/include/QtCore/../../src/corelib/arch/qatomic_windows.h: 388: error: previous declaration `long int InterlockedIncremen t(long int*)' here mingw32-make[2]: *** [Qt/Core/CMakeFiles/pqCore.dir/ pqCommandServerStartup.obj] Error 1 mingw32-make[1]: *** [Qt/Core/CMakeFiles/pqCore.dir/all] Error 2 mingw32-make: *** [all] Error 2 The same source code compiled fine on Linux and Mac. Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] python scripting - import cvs file
python shell, I'm using "pvpython script.py" On 15-Jan-09, at 9:20 AM, Utkarsh Ayachit wrote: Where are you typing the python script: the python shell or the "Script" parameter for the Programmable Filter/Programmable Source? On Wed, Jan 14, 2009 at 7:17 PM, Pierre-Olivier Dallaire wrote: Good evening, I'm trying to import a text file in order to superimpose the results with some OpenFOAM results. I'm using a python script to read the text file; however, the basic script provided at http://cmake.org/Wiki/Here_are_some_more_examples_of_simple_ParaView_3_python_filters fails at pdo = self.GetOutput() : Traceback (most recent call last): File "paraview_cvs.py", line 21, in pdo = self.GetOutput() NameError: name 'self' is not defined Not sure what is wrong - any idea ? Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] python scripting - import cvs file
Good evening, I'm trying to import a text file in order to superimpose the results with some OpenFOAM results. I'm using a python script to read the text file; however, the basic script provided at http://cmake.org/Wiki/Here_are_some_more_examples_of_simple_ParaView_3_python_filters fails at pdo = self.GetOutput() : Traceback (most recent call last): File "paraview_cvs.py", line 21, in pdo = self.GetOutput() NameError: name 'self' is not defined Not sure what is wrong - any idea ? Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] python scripting / calculator filter
Thanks Peter, very useful ! PO On 2-Dec-08, at 4:53 PM, Peter Brady wrote: Here's something I did recently calc = servermanager.filters.Calculator(Input=pderiv) calc.ResultArrayName = 'w' calc.AddVectorVariable = ['Vorticity', 'Vorticity', '0', '1', '2'] calc.Function = '(Vorticity).(kHat)' calc.UpdatePipeline() # w is now element 16 This gave the vorticity in the khat direction. That should get you started. Good Luck, Peter. On Tue, Dec 2, 2008 at 2:45 PM, Pierre-Olivier Dallaire <[EMAIL PROTECTED]> wrote: Good afternoon, I'm looking for an example on how to use the calculator filter in a python script. With the calculator, I want to : 1) Extract each component of a vector array (x, y, z); 2) Apply a scalar factor on each array (for unit conversion). Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] python scripting / calculator filter
Good afternoon, I'm looking for an example on how to use the calculator filter in a python script. With the calculator, I want to : 1) Extract each component of a vector array (x, y, z); 2) Apply a scalar factor on each array (for unit conversion). Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] TestParallelRandomStatistics.cxx - fails to build
Good morning, I'm experiencing some problems when building the latest cvs version : [ 48%] Building CXX object VTK/Infovis/Testing/Cxx/CMakeFiles/ TestParallelRandomStatistics.dir/TestParallelRandomStatistics.o ...ParaView3/VTK/Infovis/Testing/Cxx/TestParallelRandomStatistics.cxx: 190: error: ISO C++ says that these are ambiguous, even though the worst conversion for the first is better than the worst conversion for the second: /usr/include/c++/4.0.0/bits/basic_string.h:696: note: candidate 1: typename _Alloc::reference std::basic_string<_CharT, _Traits, _Alloc>::operator[](typename _Alloc::size_type) [with _CharT = char, _Traits = std::char_traits, _Alloc = std::allocator] ... Any idea ? Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] pvpython -> extracting timesteps
Good afternoon, I've been playing with pvpython this week and I always have this issue when using the time steps : tsteps= reader.TimestepValues #No problem here view.ViewTime = tsteps[i] #Gives me an error : Traceback (most recent call last): File "post.py", line 73, in view.ViewTime = tsteps[i] File "/data-cfd01/software/ParaView/src/build_Python2.5/Utilities/ VTKPythonWrapping/paraview/servermanager.py", line 1514, in setProperty return self.SetPropertyWithName(propName, value) File "/data-cfd01/software/ParaView/src/build_Python2.5/Utilities/ VTKPythonWrapping/paraview/servermanager.py", line 163, in SetPropertyWithName prop.SetData(arg) File "/data-cfd01/software/ParaView/src/build_Python2.5/Utilities/ VTKPythonWrapping/paraview/servermanager.py", line 394, in SetData self.SMProperty.SetElement(i, self.ConvertValue(values[i])) TypeError: a float is required It's impossible to extract each number from the array tsteps - any idea ? Thanks ! PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Mac OS X - Standalone bundle
Thanks David ! yes, the make install works / I did not know that invoking the make install was required to build the standalone app / this changed over the last month. Since I'm building Paraview and OpenFOAM from a sensitive-case disk image, ParavIew could not launch yesterday from /Applications since the disk image was not mounted. Now everything is good - the standalone applications weigths 185 M as before. Best regards, PO On 31-Oct-08, at 9:58 AM, David Cole wrote: You need to do a "make install" to produce the standalone bundle. I recommend using...: DESTDIR=pvinst make install ...and then getting the standalone bundle out of the pvinst directory... Why do you say the build directory is needed to launch it? What happens if you move/rename the build directory and try to launch the standalone bundle? On Fri, Oct 31, 2008 at 7:00 AM, Pierre-Olivier Dallaire <[EMAIL PROTECTED] > wrote: Good morning, with the latest version of Paraview (3.5.0), I understand that there is a new script (paraview_OSX_MakeStandAloneBundle.sh) to create the Mac OS X application bundle. However, the application only weights now 15 M and in fact is not standalone as before -> the build directory is needed to launch it. Any thoughts on how to solve this problem ? Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Mac OS X - Standalone bundle
Good morning, with the latest version of Paraview (3.5.0), I understand that there is a new script (paraview_OSX_MakeStandAloneBundle.sh) to create the Mac OS X application bundle. However, the application only weights now 15 M and in fact is not standalone as before -> the build directory is needed to launch it. Any thoughts on how to solve this problem ? Best regards, PO ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
