Re: [Paraview] Customize filter toolbar
Hi David, thank you for your answer. The procedure you proposed did not work for me - clicking on the eye has no effect. What does work is the following: 1. Create selection manually 2. Play trace 3. Click on Apply 4. Open a new view 5. Check Display- Visible However, selecting the PlotSelectionOverTime filter from the menu and clicking Apply makes the plot appear in two steps. I was thinking that a PlotSelectionOverTime button could save me two clicks, as I often have to process many datasets in a row. But it seems that the two clicks saved here have to be done elsewhere for making the plot appear... I should perhaps think about learning how to program a macro in order to automate the whole thing - the procedure I do all the time is: 1. Open the dataset 2. Change the displayed variable, edit the color map 3. Select a point (always the same) 4. Plot selection over time 5. Save data in a csv file Steps 2 and 3 are optional - I think steps 1,4,5 must be easy to do automatically if I know how... ;) Is there a good starting point, a tutorial or something for macro programming apart from the ParaView Manual? Thank you for your help, Matthias -Ursprüngliche Nachricht- Von: David E DeMarle [mailto:dave.dema...@kitware.com] Gesendet: Dienstag, 27. März 2012 12:35 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Customize filter toolbar I missed that you were using a selection related filter. You could record the action of making the selection too in that case. But that is problematic because you don't have as much control over what to plot. Otherwise, for when you make the selection manually and then apply the macro you've already got, it seems that ParaView isn't creating the plot view for you like it normally does for some reason. To work around, open up a line chart view and then replay your trace. Select the plot view and then click the eye icon in the pipeline browser next to the plot filter to show the result. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Mar 26, 2012 at 10:34 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi David, thank you for the hints. Unfortunately it doesn't work for me that way. The macro I get is - try: paraview.simple except: from paraview.simple import * paraview.simple._DisableFirstRenderCameraReset() my_file_pvd = GetActiveSource() PlotSelectionOverTime8 = PlotSelectionOverTime() Render() I must admit that I don't know Python at all. It's not the same language as in Life of Brian... ;-)) I have had a look in the ParaView Manual which did not enlighten me for this specific problem. When I execute the macro above, ParaView creates a Plot SelectionOverTime object, but when I hit Apply, nothing happens. Also it seems to me that the Macro expects a specific name for the dataset. How can I generalize it, once it works? Thanks for some more hints... Matthias -Ursprüngliche Nachricht- Von: David E DeMarle [mailto:dave.dema...@kitware.com] Gesendet: Montag, 26. März 2012 16:00 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Customize filter toolbar You can record a trace in which you just apply that filter, and then save the trace as a macro. It won't be in the common filters toolbar, but it will be in the macros toolbar which is by default right next to it. If you are building from source you can add the filter to the Common group in Applications/ParaView/ParaViewFilters.xml. You could also write a plugin that does it. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Mar 26, 2012 at 9:27 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, is there an easy way to customize the filter toolbar? For example, the Plot selection over time I filter is the one I use all the time. I would like to have a button on the toolbar, like there are buttons for the calculator, contour plot, clip, ... How do I do it? Thanks, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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 _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede
[Paraview] Split plot window vertically by default
Hi, since ParaView 3.14, the plot window seems to be split horizontally by default when a new plot is generated, e.g. by the PlotSelectionOverTime filter. In ParaView 3.12, it was split vertically, which I prefer. Can this be set somewhere in the preferences or in the initialization file? Thank you, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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] Customize filter toolbar
Hi again, I have succeeded making a trace which essentially does what I want, i.e. automatically performing steps from my message 1,4,5 below. Thanks, Matthias -Ursprüngliche Nachricht- Von: Zenker, Dr. Matthias Gesendet: Dienstag, 27. März 2012 13:45 An: 'David E DeMarle' Cc: paraview@paraview.org Betreff: AW: [Paraview] Customize filter toolbar Hi David, thank you for your answer. The procedure you proposed did not work for me - clicking on the eye has no effect. What does work is the following: 1. Create selection manually 2. Play trace 3. Click on Apply 4. Open a new view 5. Check Display- Visible However, selecting the PlotSelectionOverTime filter from the menu and clicking Apply makes the plot appear in two steps. I was thinking that a PlotSelectionOverTime button could save me two clicks, as I often have to process many datasets in a row. But it seems that the two clicks saved here have to be done elsewhere for making the plot appear... I should perhaps think about learning how to program a macro in order to automate the whole thing - the procedure I do all the time is: 1. Open the dataset 2. Change the displayed variable, edit the color map 3. Select a point (always the same) 4. Plot selection over time 5. Save data in a csv file Steps 2 and 3 are optional - I think steps 1,4,5 must be easy to do automatically if I know how... ;) Is there a good starting point, a tutorial or something for macro programming apart from the ParaView Manual? Thank you for your help, Matthias -Ursprüngliche Nachricht- Von: David E DeMarle [mailto:dave.dema...@kitware.com] Gesendet: Dienstag, 27. März 2012 12:35 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Customize filter toolbar I missed that you were using a selection related filter. You could record the action of making the selection too in that case. But that is problematic because you don't have as much control over what to plot. Otherwise, for when you make the selection manually and then apply the macro you've already got, it seems that ParaView isn't creating the plot view for you like it normally does for some reason. To work around, open up a line chart view and then replay your trace. Select the plot view and then click the eye icon in the pipeline browser next to the plot filter to show the result. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Mar 26, 2012 at 10:34 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi David, thank you for the hints. Unfortunately it doesn't work for me that way. The macro I get is - try: paraview.simple except: from paraview.simple import * paraview.simple._DisableFirstRenderCameraReset() my_file_pvd = GetActiveSource() PlotSelectionOverTime8 = PlotSelectionOverTime() Render() I must admit that I don't know Python at all. It's not the same language as in Life of Brian... ;-)) I have had a look in the ParaView Manual which did not enlighten me for this specific problem. When I execute the macro above, ParaView creates a Plot SelectionOverTime object, but when I hit Apply, nothing happens. Also it seems to me that the Macro expects a specific name for the dataset. How can I generalize it, once it works? Thanks for some more hints... Matthias -Ursprüngliche Nachricht- Von: David E DeMarle [mailto:dave.dema...@kitware.com] Gesendet: Montag, 26. März 2012 16:00 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Customize filter toolbar You can record a trace in which you just apply that filter, and then save the trace as a macro. It won't be in the common filters toolbar, but it will be in the macros toolbar which is by default right next to it. If you are building from source you can add the filter to the Common group in Applications/ParaView/ParaViewFilters.xml. You could also write a plugin that does it. David E DeMarle Kitware, Inc. RD Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Mar 26, 2012 at 9:27 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, is there an easy way to customize the filter toolbar? For example, the Plot selection over time I filter is the one I use all the time. I would like to have a button on the toolbar, like there are buttons for the calculator, contour plot, clip, ... How do I do it? Thanks, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages
Re: [Paraview] Split plot window vertically by default
Not currently. Feel free to add a feature request to the bug tracker. On Tue, Mar 27, 2012 at 8:12 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, since ParaView 3.14, the plot window seems to be split horizontally by default when a new plot is generated, e.g. by the PlotSelectionOverTime filter. In ParaView 3.12, it was split vertically, which I prefer. Can this be set somewhere in the preferences or in the initialization file? Thank you, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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] Split plot window vertically by default
But it has changed from 3.12 to 3.14 - was this on purpose, or is it a feature? ;) -Ursprüngliche Nachricht- Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] Gesendet: Dienstag, 27. März 2012 15:17 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Split plot window vertically by default Not currently. Feel free to add a feature request to the bug tracker. On Tue, Mar 27, 2012 at 8:12 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, since ParaView 3.14, the plot window seems to be split horizontally by default when a new plot is generated, e.g. by the PlotSelectionOverTime filter. In ParaView 3.12, it was split vertically, which I prefer. Can this be set somewhere in the preferences or in the initialization file? Thank you, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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 _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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] Split plot window vertically by default
The purpose was that random swicthing of which direction to split causes failures in the testing framework which led to unreliable test playback. On Tue, Mar 27, 2012 at 9:19 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: But it has changed from 3.12 to 3.14 - was this on purpose, or is it a feature? ;) -Ursprüngliche Nachricht- Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] Gesendet: Dienstag, 27. März 2012 15:17 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Split plot window vertically by default Not currently. Feel free to add a feature request to the bug tracker. On Tue, Mar 27, 2012 at 8:12 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, since ParaView 3.14, the plot window seems to be split horizontally by default when a new plot is generated, e.g. by the PlotSelectionOverTime filter. In ParaView 3.12, it was split vertically, which I prefer. Can this be set somewhere in the preferences or in the initialization file? Thank you, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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 _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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] Split plot window vertically by default
In ParaView 3.12 an earlier, the split was determined by the aspect ratio of the view. If the view was taller than wide, it split vertically by default. If the view was wider than tall, it split horizontally by default. It now seems to always split horizontally. Why the change? -Ken On 3/27/12 7:17 AM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: Not currently. Feel free to add a feature request to the bug tracker. On Tue, Mar 27, 2012 at 8:12 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, since ParaView 3.14, the plot window seems to be split horizontally by default when a new plot is generated, e.g. by the PlotSelectionOverTime filter. In ParaView 3.12, it was split vertically, which I prefer. Can this be set somewhere in the preferences or in the initialization file? Thank you, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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] Split plot window vertically by default
Thank you for the clarification - I will try to add the request to the bug tracker. Matthias -Ursprüngliche Nachricht- Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] Gesendet: Dienstag, 27. März 2012 15:21 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Split plot window vertically by default The purpose was that random swicthing of which direction to split causes failures in the testing framework which led to unreliable test playback. On Tue, Mar 27, 2012 at 9:19 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: But it has changed from 3.12 to 3.14 - was this on purpose, or is it a feature? ;) -Ursprüngliche Nachricht- Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] Gesendet: Dienstag, 27. März 2012 15:17 An: Zenker, Dr. Matthias Cc: paraview@paraview.org Betreff: Re: [Paraview] Split plot window vertically by default Not currently. Feel free to add a feature request to the bug tracker. On Tue, Mar 27, 2012 at 8:12 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, since ParaView 3.14, the plot window seems to be split horizontally by default when a new plot is generated, e.g. by the PlotSelectionOverTime filter. In ParaView 3.12, it was split vertically, which I prefer. Can this be set somewhere in the preferences or in the initialization file? Thank you, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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 _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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] Surface Development on ParaView
Thank you, Ken. I tried Calculation filter and got a good result! I used acos() function, so I couldn't extract whole cylindrical surface. But fortunately, my source data is quarter or half one. So it wasn't a problem for me. At first, I thought the Calculator just as a calculating tool with Scalar or Vector values. But on your advice, I believed that is one of the typical post-processing tool of ParaView. Magician On 2012/03/26, at 22:38, Moreland, Kenneth wrote: In the past I have used the calculator filter to convert polar coordinates to cartesian or vice versa. -Ken On 3/26/12 7:08 AM, Magician f_magic...@mac.com wrote: Hi. I'm considering to generate developed surface view on ParaView. My VTK data contains cylindrical surfaces (defined on theta-z spaces), and I want to convert them to flat planes (defined on x-y planes). One idea is re-writing VTK file, but it's pretty troublesome. Are there any ideas to do it easily? Magician ___ 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] build error with boost and additional questions
Rob and Aashish: Ok so boost 1.45.0 worked fine with Paraview 3.14 Can someone confirm that Paraview client and server (remote) do not require same sets of plugin on either end. Is there a required minimal plugin set? Thanks --Amit On Mar 23, 2012, at 1:48 PM, Robert Maynard wrote: Hi, The ParaView Binary page ( http://www.paraview.org/Wiki/ParaView_Binaries ) which version of each library ParaView is built against. ParaView 3.14 used Boost 1.45.0. On Fri, Mar 23, 2012 at 2:44 PM, Chourasia, Amit a...@sdsc.edumailto:a...@sdsc.edu wrote: Yes, I found the bug report by a web search as well. I tried boost_1_47_0 with same error Since the build take quite some time, I would like to know if there is a known version of boost which works Paraview3.14 On Mar 23, 2012, at 1:29 PM, Aashish Chaudhary wrote: There is already a bug report for this: http://www.vtk.org/Bug/bug_relationship_graph.php?bug_id=12988graph=dependency I believe that boost_1_49_0 won't work, Can you try earlier versions? On Fri, Mar 23, 2012 at 2:16 PM, Chourasia, Amit a...@sdsc.edumailto:a...@sdsc.edu wrote: Hello, I have tried building Paraview3.14 with boost_1_49_0 and boost_1_47_0 versions. I get the following error, is there a fix or workaround besides disabling boost altogether. Please see ERROR below Since I am doing this build for general purpose use on one of the big cluster what are canonical plugins which should be built? I am using the options as listed at the end of the message Burlen mentioned sometime back that in the new version of Paraview the client and server will not require same plugins on both ends. Is this now possible? Please also point me to documentation on how to create a Paraview profile for end users to easily use it remotely with client-server interface Thanks --Amit ERROR * [ 49%] Building CXX object VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o /usr/include/c++/4.1.2/backward/backward_warning.h(32): warning #1224: #warning directive: This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the X header for the X.h header for C++ includes, or iostream instead of the deprecated header iostream.h. To disable this warning use -Wno-deprecated. #warning This file includes at least one deprecated or antiquated header. \ ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1304): warning #279: controlling expression is constant assert(pre: valid_range range[0]=range[1]); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1334): warning #279: controlling expression is constant assert(post: valid_result result=0.0 result=1.0); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx(56): error: class boost::detail::reverse_graph_edge_descriptorvtkEdgeType has no member underlying_desc return e.underlying_desc.Idhttp://e.underlying_desc.Id/; ^ compilation aborted for /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx (code 2) make[2]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o] Error 2 make[1]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/all] Error 2 make: *** [all] Error 2 BUILD OPTIONS cmake \ -DCMAKE_BUILD_TYPE=Debug \ -DBUILD_SHARED_LIBS=ON \ -DBUILD_TESTING=OFF \ -DPARAVIEW_DISABLE_VTK_TESTING=ON \ -DPARAVIEW_TESTING_WITH_PYTHON=OFF \ -DVTK_USE_BOOST=ON \ -DPARAVIEW_BUILD_QT_GUI=OFF \ -DPARAVIEW_ENABLE_PYTHON=ON \ -DPARAVIEW_USE_MPI=ON \ -DPARAVIEW_BUILD_PLUGIN=EyeDomeLighting \ -DPARAVIEW_USE_VISITBRIDGE=OFF \ -DVISIT_BUILD_READER_CGNS=OFF \ -DVISIT_BUILD_READER_Silo=OFF \ -DBUILD_DOCUMENTATION=ON \ -DPARAVIEW_GENERATE_PROXY_DOCUMENTATION=ON \ -DGENERATE_FILTERS_DOCUMENTATION=ON \ -DDOCUMENTATION_HTML_HELP=ON \ -DCMAKE_C_COMPILER=icc \ -DCMAKE_CXX_COMPILER=icpc \ -DCMAKE_INSTALL_PREFIX=/oasis/scratch/amit/temp_project/paraview_build \ -DVTK_OPENGL_HAS_OSMESA=ON \ -DVTK_USE_X=OFF \ -DOSMESA_INCLUDE_DIR=/oasis/scratch/amit/temp_project/mesa_build/include \ -DOPENGL_INCLUDE_DIR=/oasis/scratch/amit/temp_project/mesa_build/include \ -DOPENGL_gl_LIBRARY= \ -DOPENGL_glu_LIBRARY=/oasis/scratch/amit/temp_project/mesa_build/lib/libGLU.so \ -DOSMESA_LIBRARY=/oasis/scratch/amit/temp_project/mesa_build/lib/libOSMesa32.so \ -DMPI_COMPILER=/opt/mvapich2/intel/ib/bin/mpicxx \ -DMPI_LIBRARY=/opt/mvapich2/intel/ib/lib \ -DBOOST_ROOT=/oasis/scratch/amit/temp_project/boost_1_49_0 ___ Powered by www.kitware.comhttp://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:
Re: [Paraview] build error with boost and additional questions
All plugins are indeed optional. If you build your server statically, it will include all plugins that were enabled at build time so you may get a warning message when a client connects to the server to load the missing plugins on the client as well, at which point they can be loaded on cleint. Utkarsh On Tue, Mar 27, 2012 at 12:16 PM, Chourasia, Amit a...@sdsc.edu wrote: Rob and Aashish: Ok so boost 1.45.0 worked fine with Paraview 3.14 Can someone confirm that Paraview client and server (remote) do not require same sets of plugin on either end. Is there a required minimal plugin set? Thanks --Amit On Mar 23, 2012, at 1:48 PM, Robert Maynard wrote: Hi, The ParaView Binary page ( http://www.paraview.org/Wiki/ParaView_Binaries ) which version of each library ParaView is built against. ParaView 3.14 used Boost 1.45.0. On Fri, Mar 23, 2012 at 2:44 PM, Chourasia, Amit a...@sdsc.edu wrote: Yes, I found the bug report by a web search as well. I tried boost_1_47_0 with same error Since the build take quite some time, I would like to know if there is a known version of boost which works Paraview3.14 On Mar 23, 2012, at 1:29 PM, Aashish Chaudhary wrote: There is already a bug report for this: http://www.vtk.org/Bug/bug_relationship_graph.php?bug_id=12988graph=dependency I believe that boost_1_49_0 won't work, Can you try earlier versions? On Fri, Mar 23, 2012 at 2:16 PM, Chourasia, Amit a...@sdsc.edu wrote: Hello, I have tried building Paraview3.14 with boost_1_49_0 and boost_1_47_0 versions. I get the following error, is there a fix or workaround besides disabling boost altogether. Please see ERROR below Since I am doing this build for general purpose use on one of the big cluster what are canonical plugins which should be built? I am using the options as listed at the end of the message Burlen mentioned sometime back that in the new version of Paraview the client and server will not require same plugins on both ends. Is this now possible? Please also point me to documentation on how to create a Paraview profile for end users to easily use it remotely with client-server interface Thanks --Amit ERROR * [ 49%] Building CXX object VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o /usr/include/c++/4.1.2/backward/backward_warning.h(32): warning #1224: #warning directive: This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the X header for the X.h header for C++ includes, or iostream instead of the deprecated header iostream.h. To disable this warning use -Wno-deprecated. #warning This file includes at least one deprecated or antiquated header. \ ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1304): warning #279: controlling expression is constant assert(pre: valid_range range[0]=range[1]); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1334): warning #279: controlling expression is constant assert(post: valid_result result=0.0 result=1.0); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx(56): error: class boost::detail::reverse_graph_edge_descriptorvtkEdgeType has no member underlying_desc return e.underlying_desc.Id; ^ compilation aborted for /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx (code 2) make[2]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o] Error 2 make[1]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/all] Error 2 make: *** [all] Error 2 BUILD OPTIONS cmake \ -DCMAKE_BUILD_TYPE=Debug \ -DBUILD_SHARED_LIBS=ON \ -DBUILD_TESTING=OFF \ -DPARAVIEW_DISABLE_VTK_TESTING=ON \ -DPARAVIEW_TESTING_WITH_PYTHON=OFF \ -DVTK_USE_BOOST=ON \ -DPARAVIEW_BUILD_QT_GUI=OFF \ -DPARAVIEW_ENABLE_PYTHON=ON \ -DPARAVIEW_USE_MPI=ON \ -DPARAVIEW_BUILD_PLUGIN=EyeDomeLighting \ -DPARAVIEW_USE_VISITBRIDGE=OFF \ -DVISIT_BUILD_READER_CGNS=OFF \ -DVISIT_BUILD_READER_Silo=OFF \ -DBUILD_DOCUMENTATION=ON \ -DPARAVIEW_GENERATE_PROXY_DOCUMENTATION=ON \ -DGENERATE_FILTERS_DOCUMENTATION=ON \ -DDOCUMENTATION_HTML_HELP=ON \ -DCMAKE_C_COMPILER=icc \ -DCMAKE_CXX_COMPILER=icpc \ -DCMAKE_INSTALL_PREFIX=/oasis/scratch/amit/temp_project/paraview_build \ -DVTK_OPENGL_HAS_OSMESA=ON \ -DVTK_USE_X=OFF \ -DOSMESA_INCLUDE_DIR=/oasis/scratch/amit/temp_project/mesa_build/include \ -DOPENGL_INCLUDE_DIR=/oasis/scratch/amit/temp_project/mesa_build/include \ -DOPENGL_gl_LIBRARY= \ -DOPENGL_glu_LIBRARY=/oasis/scratch/amit/temp_project/mesa_build/lib/libGLU.so \ -DOSMESA_LIBRARY=/oasis/scratch/amit/temp_project/mesa_build/lib/libOSMesa32.so \
Re: [Paraview] Split plot window vertically by default
Mostly testing. As panels size started changing on different platforms, it was not uncommon to end up with the views being split differently during different runs. On Tue, Mar 27, 2012 at 9:22 AM, Moreland, Kenneth kmo...@sandia.gov wrote: In ParaView 3.12 an earlier, the split was determined by the aspect ratio of the view. If the view was taller than wide, it split vertically by default. If the view was wider than tall, it split horizontally by default. It now seems to always split horizontally. Why the change? -Ken On 3/27/12 7:17 AM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: Not currently. Feel free to add a feature request to the bug tracker. On Tue, Mar 27, 2012 at 8:12 AM, Zenker, Dr. Matthias matthias.zen...@erbe-med.com wrote: Hi, since ParaView 3.14, the plot window seems to be split horizontally by default when a new plot is generated, e.g. by the PlotSelectionOverTime filter. In ParaView 3.12, it was split vertically, which I prefer. Can this be set somewhere in the preferences or in the initialization file? Thank you, Matthias _ ERBE Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137 ___ 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] build error with boost and additional questions
Hey, Amit, FWIW, I know that in the past (pv3.10 and pv3.12) I have run into issues when client/server plugins don't match. This was a problem when using a binary distribution of the client, which included many (all?) of the reader plugins, against a pvserver that I built which did not include the same reader plugins. Specifically, it failed if I tried to open a file for which there was not a default choice of reader. If I understand correctly, the client would go down the list of readers that it knew about, and tell the server to try it. But if the server did not know about that reader, it would case ParaView to fail. I believe this has been addressed in PV3.14, but I have not had a chance to confirm. joe. On Mar 27, 2012, at 11:16 AM, Chourasia, Amit wrote: Rob and Aashish: Ok so boost 1.45.0 worked fine with Paraview 3.14 Can someone confirm that Paraview client and server (remote) do not require same sets of plugin on either end. Is there a required minimal plugin set? Thanks --Amit On Mar 23, 2012, at 1:48 PM, Robert Maynard wrote: Hi, The ParaView Binary page ( http://www.paraview.org/Wiki/ParaView_Binaries ) which version of each library ParaView is built against. ParaView 3.14 used Boost 1.45.0. On Fri, Mar 23, 2012 at 2:44 PM, Chourasia, Amit a...@sdsc.edu wrote: Yes, I found the bug report by a web search as well. I tried boost_1_47_0 with same error Since the build take quite some time, I would like to know if there is a known version of boost which works Paraview3.14 On Mar 23, 2012, at 1:29 PM, Aashish Chaudhary wrote: There is already a bug report for this: http://www.vtk.org/Bug/bug_relationship_graph.php?bug_id=12988graph=dependency I believe that boost_1_49_0 won't work, Can you try earlier versions? On Fri, Mar 23, 2012 at 2:16 PM, Chourasia, Amit a...@sdsc.edu wrote: Hello, I have tried building Paraview3.14 with boost_1_49_0 and boost_1_47_0 versions. I get the following error, is there a fix or workaround besides disabling boost altogether. Please see ERROR below Since I am doing this build for general purpose use on one of the big cluster what are canonical plugins which should be built? I am using the options as listed at the end of the message Burlen mentioned sometime back that in the new version of Paraview the client and server will not require same plugins on both ends. Is this now possible? Please also point me to documentation on how to create a Paraview profile for end users to easily use it remotely with client-server interface Thanks --Amit ERROR * [ 49%] Building CXX object VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o /usr/include/c++/4.1.2/backward/backward_warning.h(32): warning #1224: #warning directive: This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the X header for the X.h header for C++ includes, or iostream instead of the deprecated header iostream.h. To disable this warning use -Wno-deprecated. #warning This file includes at least one deprecated or antiquated header. \ ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1304): warning #279: controlling expression is constant assert(pre: valid_range range[0]=range[1]); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1334): warning #279: controlling expression is constant assert(post: valid_result result=0.0 result=1.0); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx(56): error: class boost::detail::reverse_graph_edge_descriptorvtkEdgeType has no member underlying_desc return e.underlying_desc.Id; ^ compilation aborted for /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx (code 2) make[2]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o] Error 2 make[1]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/all] Error 2 make: *** [all] Error 2 BUILD OPTIONS cmake \ -DCMAKE_BUILD_TYPE=Debug \ -DBUILD_SHARED_LIBS=ON \ -DBUILD_TESTING=OFF \ -DPARAVIEW_DISABLE_VTK_TESTING=ON \ -DPARAVIEW_TESTING_WITH_PYTHON=OFF \ -DVTK_USE_BOOST=ON \ -DPARAVIEW_BUILD_QT_GUI=OFF \ -DPARAVIEW_ENABLE_PYTHON=ON \ -DPARAVIEW_USE_MPI=ON \ -DPARAVIEW_BUILD_PLUGIN=EyeDomeLighting \ -DPARAVIEW_USE_VISITBRIDGE=OFF \ -DVISIT_BUILD_READER_CGNS=OFF \ -DVISIT_BUILD_READER_Silo=OFF \ -DBUILD_DOCUMENTATION=ON \ -DPARAVIEW_GENERATE_PROXY_DOCUMENTATION=ON \ -DGENERATE_FILTERS_DOCUMENTATION=ON \ -DDOCUMENTATION_HTML_HELP=ON \ -DCMAKE_C_COMPILER=icc \ -DCMAKE_CXX_COMPILER=icpc \
Re: [Paraview] build error with boost and additional questions
Hi Utkarsh, If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Burlen On 03/27/2012 09:44 AM, Utkarsh Ayachit wrote: All plugins are indeed optional. If you build your server statically, it will include all plugins that were enabled at build time so you may get a warning message when a client connects to the server to load the missing plugins on the client as well, at which point they can be loaded on cleint. Utkarsh On Tue, Mar 27, 2012 at 12:16 PM, Chourasia, Amita...@sdsc.edu wrote: Rob and Aashish: Ok so boost 1.45.0 worked fine with Paraview 3.14 Can someone confirm that Paraview client and server (remote) do not require same sets of plugin on either end. Is there a required minimal plugin set? Thanks --Amit On Mar 23, 2012, at 1:48 PM, Robert Maynard wrote: Hi, The ParaView Binary page ( http://www.paraview.org/Wiki/ParaView_Binaries ) which version of each library ParaView is built against. ParaView 3.14 used Boost 1.45.0. On Fri, Mar 23, 2012 at 2:44 PM, Chourasia, Amita...@sdsc.edu wrote: Yes, I found the bug report by a web search as well. I tried boost_1_47_0 with same error Since the build take quite some time, I would like to know if there is a known version of boost which works Paraview3.14 On Mar 23, 2012, at 1:29 PM, Aashish Chaudhary wrote: There is already a bug report for this: http://www.vtk.org/Bug/bug_relationship_graph.php?bug_id=12988graph=dependency I believe that boost_1_49_0 won't work, Can you try earlier versions? On Fri, Mar 23, 2012 at 2:16 PM, Chourasia, Amita...@sdsc.edu wrote: Hello, I have tried building Paraview3.14 with boost_1_49_0 and boost_1_47_0 versions. I get the following error, is there a fix or workaround besides disabling boost altogether. Please see ERROR below Since I am doing this build for general purpose use on one of the big cluster what are canonical plugins which should be built? I am using the options as listed at the end of the message Burlen mentioned sometime back that in the new version of Paraview the client and server will not require same plugins on both ends. Is this now possible? Please also point me to documentation on how to create a Paraview profile for end users to easily use it remotely with client-server interface Thanks --Amit ERROR * [ 49%] Building CXX object VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o /usr/include/c++/4.1.2/backward/backward_warning.h(32): warning #1224: #warning directive: This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting theX header for theX.h header for C++ includes, oriostream instead of the deprecated headeriostream.h. To disable this warning use -Wno-deprecated. #warning This file includes at least one deprecated or antiquated header. \ ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1304): warning #279: controlling expression is constant assert(pre: valid_range range[0]=range[1]); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Common/vtkMath.h(1334): warning #279: controlling expression is constant assert(post: valid_result result=0.0 result=1.0); ^ /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx(56): error: class boost::detail::reverse_graph_edge_descriptorvtkEdgeType has no member underlying_desc return e.underlying_desc.Id; ^ compilation aborted for /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/VTK/Infovis/vtkBoostBreadthFirstSearchTree.cxx (code 2) make[2]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/vtkBoostBreadthFirstSearchTree.cxx.o] Error 2 make[1]: *** [VTK/Infovis/CMakeFiles/vtkInfovis.dir/all] Error 2 make: *** [all] Error 2 BUILD OPTIONS cmake \ -DCMAKE_BUILD_TYPE=Debug \ -DBUILD_SHARED_LIBS=ON \ -DBUILD_TESTING=OFF \ -DPARAVIEW_DISABLE_VTK_TESTING=ON \ -DPARAVIEW_TESTING_WITH_PYTHON=OFF \ -DVTK_USE_BOOST=ON \ -DPARAVIEW_BUILD_QT_GUI=OFF \ -DPARAVIEW_ENABLE_PYTHON=ON \ -DPARAVIEW_USE_MPI=ON \ -DPARAVIEW_BUILD_PLUGIN=EyeDomeLighting \ -DPARAVIEW_USE_VISITBRIDGE=OFF \ -DVISIT_BUILD_READER_CGNS=OFF \ -DVISIT_BUILD_READER_Silo=OFF \ -DBUILD_DOCUMENTATION=ON \ -DPARAVIEW_GENERATE_PROXY_DOCUMENTATION=ON \ -DGENERATE_FILTERS_DOCUMENTATION=ON \ -DDOCUMENTATION_HTML_HELP=ON \ -DCMAKE_C_COMPILER=icc \ -DCMAKE_CXX_COMPILER=icpc \ -DCMAKE_INSTALL_PREFIX=/oasis/scratch/amit/temp_project/paraview_build \ -DVTK_OPENGL_HAS_OSMESA=ON \ -DVTK_USE_X=OFF \
Re: [Paraview] build error with boost and additional questions
If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? No it won't, starting 3.14. With 3.14 the client fetches the list of available proxies from the server, so if the server doesn't have the VisIt bridge enabled, the readers simply won't be available for the client. do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Not sure what you mean exactly. Are you saying the default cmake values should be the ones that we use to build PV binaries? I think the superbuild proposal will address this issue. Using the superbuild it would be easier to build binaries using similar settings. Utkarsh ___ 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] vtkImageMarchingCubes as PlugIn XML-File: Problem with SetValue(int i, double value)
Unfortunately that doesn't work for me. I do not get a window where I could enter my contour value. Is there a documentation available regarding the XML syntax used for ParaView plugins? So I could look it up. Thanks - Peter -Ursprüngliche Nachricht- Von: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] Gesendet: Dienstag, 27. März 2012 22:50 An: Boettcher, Prof. Dr. Peter Cc: paraview@paraview.org Betreff: Re: [Paraview] vtkImageMarchingCubes as PlugIn XML-File: Problem with SetValue(int i, double value) You need something list this: DoubleVectorProperty name=ContourValues command=SetValue repeat_command=1 set_number_command=SetNumberOfContours number_of_elements_per_command=1 use_index=1 label=Slice Offset Values The key attributes you're missing are repeat_command, set_number_command, and use_index. Utkarsh On Tue, Mar 27, 2012 at 4:26 PM, Boettcher, Prof. Dr. Peter boettc...@kleintierklinik.uni-leipzig.de wrote: Dear All I would like to make the vtkImageMarchingCubes filter visible in ParaView. However I struggle when writing the GUI XML-File implementing the SetValue() parameter. I didn't find an example of an XML-File showing the syntax of a composed command: SetValue(int i, double value). DoubleVectorProperty name=Value label=Value for Isosurface command=SetValue number_of_elements=1 animateable=1 default_values=1500.5 /DoubleVectorProperty Any help would be highly appreciated. Peter. ___ 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] build error with boost and additional questions
My server side Paraview build was built without visit bridge. On client side I used binaries for OS X 64 bit I established a cs session and when I tired to open a .bov file both client and server crashed. Utkarsh this behaviour seems buggy as per your explanation. On Mar 27, 2012, at 3:45 PM, Utkarsh Ayachit wrote: If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? No it won't, starting 3.14. With 3.14 the client fetches the list of available proxies from the server, so if the server doesn't have the VisIt bridge enabled, the readers simply won't be available for the client. do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Not sure what you mean exactly. Are you saying the default cmake values should be the ones that we use to build PV binaries? I think the superbuild proposal will address this issue. Using the superbuild it would be easier to build binaries using similar settings. Utkarsh ___ 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] build error with boost and additional questions
What version of ParaView was this? On Tue, Mar 27, 2012 at 5:39 PM, Chourasia, Amit a...@sdsc.edu wrote: My server side Paraview build was built without visit bridge. On client side I used binaries for OS X 64 bit I established a cs session and when I tired to open a .bov file both client and server crashed. Utkarsh this behaviour seems buggy as per your explanation. On Mar 27, 2012, at 3:45 PM, Utkarsh Ayachit wrote: If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? No it won't, starting 3.14. With 3.14 the client fetches the list of available proxies from the server, so if the server doesn't have the VisIt bridge enabled, the readers simply won't be available for the client. do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Not sure what you mean exactly. Are you saying the default cmake values should be the ones that we use to build PV binaries? I think the superbuild proposal will address this issue. Using the superbuild it would be easier to build binaries using similar settings. Utkarsh ___ 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] build error with boost and additional questions
all server client are at version 3.14 On Mar 27, 2012, at 4:49 PM, Utkarsh Ayachit wrote: What version of ParaView was this? On Tue, Mar 27, 2012 at 5:39 PM, Chourasia, Amit a...@sdsc.edu wrote: My server side Paraview build was built without visit bridge. On client side I used binaries for OS X 64 bit I established a cs session and when I tired to open a .bov file both client and server crashed. Utkarsh this behaviour seems buggy as per your explanation. On Mar 27, 2012, at 3:45 PM, Utkarsh Ayachit wrote: If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? No it won't, starting 3.14. With 3.14 the client fetches the list of available proxies from the server, so if the server doesn't have the VisIt bridge enabled, the readers simply won't be available for the client. do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Not sure what you mean exactly. Are you saying the default cmake values should be the ones that we use to build PV binaries? I think the superbuild proposal will address this issue. Using the superbuild it would be easier to build binaries using similar settings. Utkarsh ___ 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] build error with boost and additional questions
This was the error reported when I loaded a .bov file Connection URL: cs://gcn-13-47.sdsc.edu:1 Accepting connection(s): gcn-13-47.sdsc.edu:1 Client connected. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x753c60): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0xab9000): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3404 location: 2 On Mar 27, 2012, at 4:49 PM, Utkarsh Ayachit wrote: What version of ParaView was this? On Tue, Mar 27, 2012 at 5:39 PM, Chourasia, Amit a...@sdsc.edu wrote: My server side Paraview build was built without visit bridge. On client side I used binaries for OS X 64 bit I established a cs session and when I tired to open a .bov file both client and server crashed. Utkarsh this behaviour seems buggy as per your explanation. On Mar 27, 2012, at 3:45 PM, Utkarsh Ayachit wrote: If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? No it won't, starting 3.14. With 3.14 the client fetches the list of available proxies from the server, so if the server doesn't have the VisIt bridge enabled, the readers simply won't be available for the client. do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Not sure what you mean exactly. Are you saying the default cmake values should be the ones that we use to build PV binaries? I think the superbuild proposal will address this issue. Using the superbuild it would be easier to build binaries using similar settings. Utkarsh ___ 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] build error with boost and additional questions
Pardon me the previous message did not include entire error Connection URL: cs://gcn-13-47.sdsc.edu:1 Accepting connection(s): gcn-13-47.sdsc.edu:1 Client connected. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x753c60): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0xab9000): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3404 location: 2 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ClientServerCore/vtkPVAlgorithmPortsInformation.cxx, line 57 vtkPVAlgorithmPortsInformation (0x223d070): Could not downcast vtkAlgorithm. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x753c60): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0xab9000): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3415 location: 2 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ClientServerCore/vtkPVAlgorithmPortsInformation.cxx, line 57 vtkPVAlgorithmPortsInformation (0x1fba0e0): Could not downcast vtkAlgorithm. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x753c60): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0xab9000): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3426 location: 1 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ClientServerCore/vtkPVAlgorithmPortsInformation.cxx, line 57 vtkPVAlgorithmPortsInformation (0x223c460): Could not downcast vtkAlgorithm. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x748fe0): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x748fe0): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x748fe0): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0x1d37fe0): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3426 location: 1 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0x1d382f0): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3426 location: 1 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In
Re: [Paraview] build error with boost and additional questions
Doh! That sounds like a bug to me. Let me track that down. Maybe we can fix it in time for 3.14.1. Utkarsh On Tue, Mar 27, 2012 at 7:15 PM, Chourasia, Amit a...@sdsc.edu wrote: Pardon me the previous message did not include entire error Connection URL: cs://gcn-13-47.sdsc.edu:1 Accepting connection(s): gcn-13-47.sdsc.edu:1 Client connected. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x753c60): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0xab9000): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3404 location: 2 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ClientServerCore/vtkPVAlgorithmPortsInformation.cxx, line 57 vtkPVAlgorithmPortsInformation (0x223d070): Could not downcast vtkAlgorithm. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x753c60): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0xab9000): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3415 location: 2 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ClientServerCore/vtkPVAlgorithmPortsInformation.cxx, line 57 vtkPVAlgorithmPortsInformation (0x1fba0e0): Could not downcast vtkAlgorithm. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x753c60): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0xab9000): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3426 location: 1 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ClientServerCore/vtkPVAlgorithmPortsInformation.cxx, line 57 vtkPVAlgorithmPortsInformation (0x223c460): Could not downcast vtkAlgorithm. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x748fe0): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x748fe0): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxyDefinitionManager.cxx, line 543 vtkSIProxyDefinitionManager (0x748fe0): No proxy that matches: group=sources and proxy=VisItBOVReader were found. ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0x1d37fe0): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3426 location: 1 [paraview_protobuf.DefinitionHeader.client_class]: vtkSMSourceProxy [paraview_protobuf.DefinitionHeader.server_class]: vtkSISourceProxy [paraview_protobuf.ProxyState.xml_group]: sources [paraview_protobuf.ProxyState.xml_name]: VisItBOVReader ERROR: In /oasis/scratch/amit/temp_project/ParaView-3.14.0-Source/ParaViewCore/ServerImplementation/vtkSIProxy.cxx, line 292 vtkSISourceProxy (0x1d382f0): Definition not found for xml_group: sources and xml_name: VisItBOVReader global_id: 3426 location: 1 [paraview_protobuf.DefinitionHeader.client_class]:
Re: [Paraview] build error with boost and additional questions
Amit, you may want to enable the visit bridge as it dramatically expands the number of file formats pv can open, and would very likely work around the bug you found. On 03/27/2012 02:39 PM, Chourasia, Amit wrote: My server side Paraview build was built without visit bridge. On client side I used binaries for OS X 64 bit I established a cs session and when I tired to open a .bov file both client and server crashed. Utkarsh this behaviour seems buggy as per your explanation. On Mar 27, 2012, at 3:45 PM, Utkarsh Ayachit wrote: If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? No it won't, starting 3.14. With 3.14 the client fetches the list of available proxies from the server, so if the server doesn't have the VisIt bridge enabled, the readers simply won't be available for the client. do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Not sure what you mean exactly. Are you saying the default cmake values should be the ones that we use to build PV binaries? I think the superbuild proposal will address this issue. Using the superbuild it would be easier to build binaries using similar settings. Utkarsh ___ 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] build error with boost and additional questions
I agree having visit bridge will be useful. I just finished building silo and cgns to go along with it. I am about to fire a fresh build right now. Cheers --Amit On Mar 27, 2012, at 11:13 PM, burlen wrote: Amit, you may want to enable the visit bridge as it dramatically expands the number of file formats pv can open, and would very likely work around the bug you found. On 03/27/2012 02:39 PM, Chourasia, Amit wrote: My server side Paraview build was built without visit bridge. On client side I used binaries for OS X 64 bit I established a cs session and when I tired to open a .bov file both client and server crashed. Utkarsh this behaviour seems buggy as per your explanation. On Mar 27, 2012, at 3:45 PM, Utkarsh Ayachit wrote: If we don't explicitly enable the bridge on the server side, and user is making use of client from the KW binaries, will it crash if a file type associated to the bridge is opened? No it won't, starting 3.14. With 3.14 the client fetches the list of available proxies from the server, so if the server doesn't have the VisIt bridge enabled, the readers simply won't be available for the client. do you think that the PV binaries c/should be built with the default build options, to reduce incompatibilities? but also maybe to improve the cmake coverage? Not sure what you mean exactly. Are you saying the default cmake values should be the ones that we use to build PV binaries? I think the superbuild proposal will address this issue. Using the superbuild it would be easier to build binaries using similar settings. Utkarsh ___ 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
