Re: [Paraview] Feasibility of and documentation on implementing a Paraview Client.

[corinna reuter]

On Mon, Aug 15, 2016 at 9:39 PM, Magnus Elden 
wrote:

> Hi,
>
>
>
> For various reasons I aim to replace the standard client of paraview and
> use the data and rendering servers as is. As such I need to implement the
> client that communicates with the servers.
>

You should elaborate on the "various reasons". All that you described is
done by the paraview application, connected to a remove pvserver. You can
extend or reduce paraview's functionality (
http://www.paraview.org/Wiki/Writing_Custom_Applications).


> I have been unable to find any documentation on this and I would
> appreciate pointers to any documentation of protocols and APIs that are
> used.
>

Apart from the wiki, you can only search the web for discussions of similar
topics or read the Paraview Guide (book).


>
>
> The reason for why I am doing this is because I am trying to utilize the
> power of Paraview and VTK inside another system. The problem is that my VTK
> program that acts as a light renderer does not work inside the system
> because it can not obtain an OpenGL context. As such I wish to remove the
> rendering from the system and instead communicate like the design already
> permits.
>

I think you should explain why you don't want to use the paraview
application as your client.

Corinna
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [EXTERNAL] Merging two datasets

[Scott, W Alan]

Not sure if this would work, but how about just moving the variables from one 
dataset to the other?  This is done with the Append Attributes filter.

Alan

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Salazar De 
Troya, Miguel
Sent: Monday, August 15, 2016 6:20 PM
To: Nasrollah Hajaliakbari via ParaView 
Subject: [EXTERNAL] [Paraview] Merging two datasets

Hello,

I have two data sets that share the same mesh and are both cell data. I want to 
put them together in a single dataset so I can extract a selection of cells 
given a criteria from one of the original datasets and then apply a filter to 
the other dataset. I tried doing GroupDataSet, but it doesn't correctly plot 
one of the datasets. In the selection of the coloring I can see "partial" next 
to the original dataset's name. How can we do this?

Thanks
Miguel

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Merging two datasets

[Salazar De Troya, Miguel]

Hello,

I have two data sets that share the same mesh and are both cell data. I want to 
put them together in a single dataset so I can extract a selection of cells 
given a criteria from one of the original datasets and then apply a filter to 
the other dataset. I tried doing GroupDataSet, but it doesn’t correctly plot 
one of the datasets. In the selection of the coloring I can see “partial” next 
to the original dataset’s name. How can we do this?

Thanks
Miguel

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Paraview with osmesa cmake issue

[Shawn Waldon]

Hi Chris,

What are you passing in for $*?  CMake, when run in a directory without a
CMakeCache file interprets the current directory as the build directory and
its last (non -ed) argument as the source directory.

HTH,
Shawn

On Mon, Aug 15, 2016 at 4:34 PM, Christopher Neal 
wrote:

> Hi,
>
> I’m trying to compile a version of Paraview that uses osmesa. I downloaded
> the ParaView soruce, and I’m following the directions from:
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>
>
>
> The tutorial gives a sample bash script for compiling with mesa. The only
> trouble that I’m having is that I don’t quite understand how to write a
> cmake shell script. I gave it a shot and it thinks my build directory is my
> source directory. I thought I passed the correct cmake variable to tell
> cmake where my source is and where my build directory are, but it can’t
> understand what I have provided. Below is the shell script that I’m trying
> to execute. Things above the space are my usual build options and things
> below are for Mesa. It can’t seem to understand those first 2 lines under
> ‘cmake’.
>
> Any thoughts on what could be causing this issue?
>
> Shell file:
>
>
> #!/bin/bash
>
>
>
> cmake \
>
>   -DCMAKE_SOURCE_DIR=/home/neal/software/ParaView_osMesa/Source \
>
>   -DCMAKE_INSTALL_PREFIX=/home/neal/software/ParaView_osMesa/build \
>
>   -DCMAKE_BUILD_TYPE:STRING=Release \
>
>   -DCMAKE_SKIP_INSTALL_RPATH:BOOL=YES \
>
>   -DBUILD_TESTING:BOOL=OFF \
>
>   -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
>
>   -DVTK_RENDERING_BACKEND=OpenGL2 \
>
>   -DPARAVIEW_USE_MPI:BOOL=ON \
>
>   -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
>
>   -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \
>
>   -DPARAVIEW_BUILD_CATALYST_ADAPTERS:BOOL=ON \
>
>   -DPARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_CDIReader:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_GeodesicMeasurement:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_MantaView:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_Moments:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_PacMan:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_RGBZView:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering:BOOL=FALSE \
>
>   -DPARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms:BOOL=OFF \
>
>   -DVTK_USE_CXX11_FEATURES:BOOL=ON \
>
>
>
>   -DPARAVIEW_BUILD_QT_GUI=OFF \
>
>   -DVTK_USE_X=OFF \
>
>   -DOPENGL_INCLUDE_DIR=/home/neal/software/Mesa/build/include \
>
>   -DOPENGL_gl_LIBRARY=/home/neal/software/Mesa/build/lib64/libOSMesa.so \
>
>   -DOPENGL_glu_LIBRARY=/home/neal/software/Mesa/build/lib64/libGLU.so \
>
>   -DVTK_OPENGL_HAS_OSMESA=ON \
>
>   -DOSMESA_INCLUDE_DIR=/home/neal/software/Mesa/build/include \
>
>   -DOSMESA_LIBRARY=/home/neal/software/Mesa/build/lib64/libOSMesa.so \
>
>   $*
>
>
>
> make -j20
>
> make -j20 install
>
>
>
> Thank you,
>
> Chris Neal
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Paraview with osmesa cmake issue

[Christopher Neal]

Hi,

I’m trying to compile a version of Paraview that uses osmesa. I downloaded the 
ParaView soruce, and I’m following the directions from: 
http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D

 

The tutorial gives a sample bash script for compiling with mesa. The only 
trouble that I’m having is that I don’t quite understand how to write a cmake 
shell script. I gave it a shot and it thinks my build directory is my source 
directory. I thought I passed the correct cmake variable to tell cmake where my 
source is and where my build directory are, but it can’t understand what I have 
provided. Below is the shell script that I’m trying to execute. Things above 
the space are my usual build options and things below are for Mesa. It can’t 
seem to understand those first 2 lines under ‘cmake’.

Any thoughts on what could be causing this issue?


Shell file:


#!/bin/bash

 

cmake \

  -DCMAKE_SOURCE_DIR=/home/neal/software/ParaView_osMesa/Source \

  -DCMAKE_INSTALL_PREFIX=/home/neal/software/ParaView_osMesa/build \

  -DCMAKE_BUILD_TYPE:STRING=Release \

  -DCMAKE_SKIP_INSTALL_RPATH:BOOL=YES \

  -DBUILD_TESTING:BOOL=OFF \

  -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \

  -DVTK_RENDERING_BACKEND=OpenGL2 \

  -DPARAVIEW_USE_MPI:BOOL=ON \

  -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \

  -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON \

  -DPARAVIEW_BUILD_CATALYST_ADAPTERS:BOOL=ON \

  -DPARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_CDIReader:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_GeodesicMeasurement:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_MantaView:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_Moments:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_PacMan:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_RGBZView:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering:BOOL=FALSE \

  -DPARAVIEW_BUILD_PLUGIN_AcceleratedAlgorithms:BOOL=OFF \

  -DVTK_USE_CXX11_FEATURES:BOOL=ON \

 

  -DPARAVIEW_BUILD_QT_GUI=OFF \

  -DVTK_USE_X=OFF \

  -DOPENGL_INCLUDE_DIR=/home/neal/software/Mesa/build/include \

  -DOPENGL_gl_LIBRARY=/home/neal/software/Mesa/build/lib64/libOSMesa.so \

  -DOPENGL_glu_LIBRARY=/home/neal/software/Mesa/build/lib64/libGLU.so \

  -DVTK_OPENGL_HAS_OSMESA=ON \

  -DOSMESA_INCLUDE_DIR=/home/neal/software/Mesa/build/include \

  -DOSMESA_LIBRARY=/home/neal/software/Mesa/build/lib64/libOSMesa.so \

  $*

 

make -j20

make -j20 install



Thank you,

Chris Neal

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Feasibility of and documentation on implementing a Paraview Client.

[Magnus Elden]

Hi,

 

For various reasons I aim to replace the standard client of paraview and use
the data and rendering servers as is. As such I need to implement the client
that communicates with the servers. I have been unable to find any
documentation on this and I would appreciate pointers to any documentation
of protocols and APIs that are used. 

 

The reason for why I am doing this is because I am trying to utilize the
power of Paraview and VTK inside another system. The problem is that my VTK
program that acts as a light renderer does not work inside the system
because it can not obtain an OpenGL context. As such I wish to remove the
rendering from the system and instead communicate like the design already
permits.

 

What I need it only for the data and rendered frames to be available on the
client and for the client to update important info such as the camera
transform and transfer functions.

 

Thank you for any help you can provide.

 

Yours,

Magnus Elden

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Catalyst example pops up render window when running

[Christopher Neal]

Hi,

 

I’m trying to run an example case for Catalyst to test my build. The case that 
I’m interested in is the ‘CxxFullExample’.  There is a SampleScripts directory 
that comes with the example. It seems to run fine. I used Paraview 5.1 to open 
the .vtu output file from the example and generated a new catalyst script that 
outputs .png images of a view that I created. 

 

When I try to run the example with my newly created script I get errors about: 
ERROR: In 
/home/neal/software/ParaView5.2/ParaView/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx,
 line 481

vtkXOpenGLRenderWindow (0x3234210): bad X server connection. 
DISPLAY=[SN-HPC-0:14212] *** Process received signal ***

Which, if I run the example in a terminal connected to the computer, I see that 
the script that Paraview created opens up a window on screen and displays my 
view. I didn’t check any boxes or options during the catalyst script creation 
process that requested an on-screen rendering. I’m at a loss for why this is 
happening. How can I request that views be saved to a file without having to be 
shown directly on the screen?

I’m using Paraview 5.2 on OpenSUSE 13.2.

Thank you,

Chris Neal

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Cannot access information from second input array in a XML custom filter

[Utkarsh Ayachit]

See the attached plugin XML. You just need to specify the array index
as default_values other it  gets initialized to 0.

On Mon, Aug 15, 2016 at 1:17 PM, Evan Kao  wrote:
> Hey guys,
>
> Just a bump in case anyone who can answer my question missed this.
> Basically, is it possible to specify two input array drop down menus in a
> Custom Filter XML file and get the array information from both?  I can get
> two drop down menus in the Properties panel, but can only get information
> from one of them.
>
> Thanks,
> Evan Kao
>
> On Fri, Aug 5, 2016 at 10:08 AM, Evan Kao  wrote:
>>
>> Hey all,
>>
>> I'm trying to create a custom filter (using vtkPythonProgrammableFilter)
>> that allows the user to specify two input arrays (the XML file is attached).
>> As a guide, I mimicked the XML specifications for the Glyphs filter in the
>> filters.xml file.  The filter appears as it should, but I can't seem to
>> access the information for the second data array:
>>
>> Request Data code:
>>
>> print 'ArrayInfo1'
>> print self.GetInputArrayInformation(0)
>> print 'ArrayInfo2'
>> print self.GetInputArrayInformation(1)
>>
>> Console output (after generating a sphere):
>>
>> ArrayInfo1
>>
>> vtkInformation (15E2FD30)
>>
>> Debug: Off
>>
>> Modified Time: 866729
>>
>> Reference Count: 2
>>
>> Registered Events: (none)
>>
>> INPUT_PORT: 0
>>
>> INPUT_CONNECTION: 0
>>
>> FIELD_ASSOCIATION: 0
>>
>> FIELD_NAME: Normals
>>
>>
>>
>> ArrayInfo2
>>
>> vtkInformation (15E47D80)
>>
>> Debug: Off
>>
>> Modified Time: 868190
>>
>> Reference Count: 2
>>
>> Registered Events: (none)
>>
>>
>> No matter how I change the second array, there is no FIELD_NAME or
>> FIELD_ASSOCIATION associated with it.  Am I accessing it incorrectly?  Did I
>> prescribe it incorrectly in the XML file?
>>
>> Thanks,
>> Evan Kao
>>
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

  


  
  


  
  


  

  

  
  


  

  

  


  

  


  


  

  

  


  

  


  




  
  
The value of this property determines the dataset type
for the output of the programmable filter.
  


  

 
   
  This property contains the text of a python program that
  the programmable source runs.
  




 

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Cannot access information from second input array in a XML custom filter

[Evan Kao]

Hey guys,

Just a bump in case anyone who can answer my question missed this.
Basically, is it possible to specify two input array drop down menus in a
Custom Filter XML file and get the array information from both?  I can get
two drop down menus in the Properties panel, but can only get information
from one of them.

Thanks,
Evan Kao

On Fri, Aug 5, 2016 at 10:08 AM, Evan Kao  wrote:

> Hey all,
>
> I'm trying to create a custom filter (using vtkPythonProgrammableFilter)
> that allows the user to specify two input arrays (the XML file is
> attached).  As a guide, I mimicked the XML specifications for the Glyphs
> filter in the filters.xml file.  The filter appears as it should, but I
> can't seem to access the information for the second data array:
>
> Request Data code:
>
> print 'ArrayInfo1'
> print self.GetInputArrayInformation(0)
> print 'ArrayInfo2'
> print self.GetInputArrayInformation(1)
>
> Console output (after generating a sphere):
>
> ArrayInfo1
>
> vtkInformation (15E2FD30)
>
> Debug: Off
>
> Modified Time: 866729
>
> Reference Count: 2
>
> Registered Events: (none)
>
> INPUT_PORT: 0
>
> INPUT_CONNECTION: 0
>
> FIELD_ASSOCIATION: 0
>
> FIELD_NAME: Normals
>
>
>
> ArrayInfo2
>
> vtkInformation (15E47D80)
>
> Debug: Off
>
> Modified Time: 868190
>
> Reference Count: 2
>
> Registered Events: (none)
>
> No matter how I change the second array, there is no FIELD_NAME or
> FIELD_ASSOCIATION associated with it.  Am I accessing it incorrectly?  Did
> I prescribe it incorrectly in the XML file?
>
> Thanks,
> Evan Kao
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Utkarsh Ayachit]

Hmm okay. I am going to report this as an issue. Clearly there are
some missing links when it comes to building examples with Catalyst
editions.

https://gitlab.kitware.com/paraview/paraview/issues/16823

On Mon, Aug 15, 2016 at 12:13 PM, Christopher Neal
 wrote:
> When I try that command I see the following after I type ‘make’:
>
> /home/neal/software/ParaView/Examples/Catalyst/CxxOverlappingAMRExample/FEAdaptor.cxx:4:23:
>  fatal error: vtkAMRBox.h: No such file or directory
>  #include 
>^
> compilation terminated.
> CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/build.make:62:
>  recipe for target 
> 'CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/FEAdaptor.cxx.o'
>  failed
> make[2]: *** 
> [CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/FEAdaptor.cxx.o]
>  Error 1
> CMakeFiles/Makefile2:124: recipe for target 
> 'CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/all' 
> failed
> make[1]: *** 
> [CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/all] 
> Error 2
> Makefile:83: recipe for target 'all' failed
> make: *** [all] Error 2
>
> It seems like it just can’t find the include directory in the Catalyst 
> edition.
>
>
> On 8/15/16, 12:06 PM, "Utkarsh Ayachit"  wrote:
>
> In that case, try the following instead from a clean directory to
> build the examples using the Catalyst edition.
>
> cmake 
> -DParaView_DIR:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
> -DBUILD_FORTRAN_EXAMPLES:BOOL=ON
> /home/neal/software/ParaView/Examples/Catalyst/
>
>
>
> On Mon, Aug 15, 2016 at 11:44 AM, Christopher Neal
>  wrote:
> > The catalyst edition was built at: 
> /home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
> >
> > /home/neal/software/ParaView_build is where I built a version of 
> Paraview with Catalyst, development files, and no gui.
> >
> > On 8/15/16, 11:41 AM, "Utkarsh Ayachit"  
> wrote:
> >
> > Chris,
> >
> > Cool. There's indeed a bug in the install rules. I'll have to it
> > fixed. BTW, I am assuming /home/neal/software/ParaView_build is the
> > direcotory where you build the Catalyst edition, is that correct?
> >
> > On Mon, Aug 15, 2016 at 11:38 AM, Christopher Neal
> >  wrote:
> > > Hi Utkarsh,
> > >
> > > I pointed to my ParaView_build directory and the examples compile 
> without any errors.
> > >
> > > cmake -DCMAKE_PREFIX_PATH=/home/neal/software/ParaView_build 
> -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> /home/neal/software/ParaView/Examples/Catalyst/
> > >
> > > Hope this helps,
> > > Chris Neal
> > >
> > > On 8/15/16, 11:19 AM, "Utkarsh Ayachit" 
>  wrote:
> > >
> > > Chris,
> > >
> > > I suspect there's a bug in the "install development files" 
> for a
> > > Catalyst edition. Can you try pointing the ParaView_DIR for 
> the
> > > Catalyst Examples to the Catalyst build directory instead? 
> Does that
> > > work?
> > >
> > > Utkarsh
> > >
> > > On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
> > >  wrote:
> > > > Hi Utkarsh,
> > > >
> > > > I have one more question related to the Catalyst edition. I 
> have compiled the ‘Essentials’ build. I used the command below(for reference) 
> to configure the edition, and everything seems to work out.
> > > >
> > > > ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
> -CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
> ../Catalyst-v5.1.0-Base-Enable-Python-Essentials
> > > >
> > > > I’m trying to compile the Catalyst examples that are 
> located in the original ParaView source tree using the Catalyst edition. I 
> used the following command to configure the examples:
> > > >
> > > > cmake 
> -DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> /home/neal/software/ParaView/Examples/Catalyst/
> > > >
> > > > cmake does not complain when I configure with the command 
> above. But when I type ‘make’ I see an error that a header file cannot be 
> located. It’s a header file that I know for a fact is located in the 
> ‘Essentials’ build directory under …/include/paraview-5.1.
> > > >
> > > > I tried 

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Christopher Neal]

When I try that command I see the following after I type ‘make’:

/home/neal/software/ParaView/Examples/Catalyst/CxxOverlappingAMRExample/FEAdaptor.cxx:4:23:
 fatal error: vtkAMRBox.h: No such file or directory
 #include 
   ^
compilation terminated.
CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/build.make:62:
 recipe for target 
'CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/FEAdaptor.cxx.o'
 failed
make[2]: *** 
[CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/FEAdaptor.cxx.o]
 Error 1
CMakeFiles/Makefile2:124: recipe for target 
'CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/all' 
failed
make[1]: *** 
[CxxOverlappingAMRExample/CMakeFiles/CxxOverlappingAMRExampleAdaptor.dir/all] 
Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

It seems like it just can’t find the include directory in the Catalyst edition.


On 8/15/16, 12:06 PM, "Utkarsh Ayachit"  wrote:

In that case, try the following instead from a clean directory to
build the examples using the Catalyst edition.

cmake 
-DParaView_DIR:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
-DBUILD_FORTRAN_EXAMPLES:BOOL=ON
/home/neal/software/ParaView/Examples/Catalyst/



On Mon, Aug 15, 2016 at 11:44 AM, Christopher Neal
 wrote:
> The catalyst edition was built at: 
/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>
> /home/neal/software/ParaView_build is where I built a version of Paraview 
with Catalyst, development files, and no gui.
>
> On 8/15/16, 11:41 AM, "Utkarsh Ayachit"  
wrote:
>
> Chris,
>
> Cool. There's indeed a bug in the install rules. I'll have to it
> fixed. BTW, I am assuming /home/neal/software/ParaView_build is the
> direcotory where you build the Catalyst edition, is that correct?
>
> On Mon, Aug 15, 2016 at 11:38 AM, Christopher Neal
>  wrote:
> > Hi Utkarsh,
> >
> > I pointed to my ParaView_build directory and the examples compile 
without any errors.
> >
> > cmake -DCMAKE_PREFIX_PATH=/home/neal/software/ParaView_build 
-DBUILD_FORTRAN_EXAMPLES:BOOL=ON /home/neal/software/ParaView/Examples/Catalyst/
> >
> > Hope this helps,
> > Chris Neal
> >
> > On 8/15/16, 11:19 AM, "Utkarsh Ayachit" 
 wrote:
> >
> > Chris,
> >
> > I suspect there's a bug in the "install development files" for a
> > Catalyst edition. Can you try pointing the ParaView_DIR for the
> > Catalyst Examples to the Catalyst build directory instead? Does 
that
> > work?
> >
> > Utkarsh
> >
> > On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
> >  wrote:
> > > Hi Utkarsh,
> > >
> > > I have one more question related to the Catalyst edition. I 
have compiled the ‘Essentials’ build. I used the command below(for reference) 
to configure the edition, and everything seems to work out.
> > >
> > > ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
-CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
../Catalyst-v5.1.0-Base-Enable-Python-Essentials
> > >
> > > I’m trying to compile the Catalyst examples that are located 
in the original ParaView source tree using the Catalyst edition. I used the 
following command to configure the examples:
> > >
> > > cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
/home/neal/software/ParaView/Examples/Catalyst/
> > >
> > > cmake does not complain when I configure with the command 
above. But when I type ‘make’ I see an error that a header file cannot be 
located. It’s a header file that I know for a fact is located in the 
‘Essentials’ build directory under …/include/paraview-5.1.
> > >
> > > I tried using the -DCMAKE_INCLUDE_PATH=[path to 
…/include/paraview-5.1] , but cmake tells me that the manually specified 
variable was not used.  The full line that I’m trying to use to configure the 
examples is:
> > >
> > > cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Utkarsh Ayachit]

In that case, try the following instead from a clean directory to
build the examples using the Catalyst edition.

cmake 
-DParaView_DIR:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
-DBUILD_FORTRAN_EXAMPLES:BOOL=ON
/home/neal/software/ParaView/Examples/Catalyst/



On Mon, Aug 15, 2016 at 11:44 AM, Christopher Neal
 wrote:
> The catalyst edition was built at: 
> /home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>
> /home/neal/software/ParaView_build is where I built a version of Paraview 
> with Catalyst, development files, and no gui.
>
> On 8/15/16, 11:41 AM, "Utkarsh Ayachit"  wrote:
>
> Chris,
>
> Cool. There's indeed a bug in the install rules. I'll have to it
> fixed. BTW, I am assuming /home/neal/software/ParaView_build is the
> direcotory where you build the Catalyst edition, is that correct?
>
> On Mon, Aug 15, 2016 at 11:38 AM, Christopher Neal
>  wrote:
> > Hi Utkarsh,
> >
> > I pointed to my ParaView_build directory and the examples compile 
> without any errors.
> >
> > cmake -DCMAKE_PREFIX_PATH=/home/neal/software/ParaView_build 
> -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> /home/neal/software/ParaView/Examples/Catalyst/
> >
> > Hope this helps,
> > Chris Neal
> >
> > On 8/15/16, 11:19 AM, "Utkarsh Ayachit"  
> wrote:
> >
> > Chris,
> >
> > I suspect there's a bug in the "install development files" for a
> > Catalyst edition. Can you try pointing the ParaView_DIR for the
> > Catalyst Examples to the Catalyst build directory instead? Does that
> > work?
> >
> > Utkarsh
> >
> > On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
> >  wrote:
> > > Hi Utkarsh,
> > >
> > > I have one more question related to the Catalyst edition. I have 
> compiled the ‘Essentials’ build. I used the command below(for reference) to 
> configure the edition, and everything seems to work out.
> > >
> > > ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
> -CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
> ../Catalyst-v5.1.0-Base-Enable-Python-Essentials
> > >
> > > I’m trying to compile the Catalyst examples that are located in 
> the original ParaView source tree using the Catalyst edition. I used the 
> following command to configure the examples:
> > >
> > > cmake 
> -DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> /home/neal/software/ParaView/Examples/Catalyst/
> > >
> > > cmake does not complain when I configure with the command above. 
> But when I type ‘make’ I see an error that a header file cannot be located. 
> It’s a header file that I know for a fact is located in the ‘Essentials’ 
> build directory under …/include/paraview-5.1.
> > >
> > > I tried using the -DCMAKE_INCLUDE_PATH=[path to 
> …/include/paraview-5.1] , but cmake tells me that the manually specified 
> variable was not used.  The full line that I’m trying to use to configure the 
> examples is:
> > >
> > > cmake 
> -DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> -DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
>  /home/neal/software/ParaView/Examples/Catalyst/
> > >
> > > Am I not specifying the include path correctly?
> > >
> > > Thank you,
> > > Chris Neal
> > >
> > > On 8/15/16, 10:15 AM, "Utkarsh Ayachit" 
>  wrote:
> > >
> > > Chris,
> > >
> > > Some thing like this should do the trick:
> > >
> > > > [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install 
> [... path to Catalyst src ...]
> > >
> > > Utkarsh
> > >
> > >
> > >
> > >
> > > On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
> > >  wrote:
> > > > Hi All,
> > > >
> > > >
> > > >
> > > > I was wondering what the appropriate way to specify a value 
> for the cmake
> > > > variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst 
> edition.  The
> > > > editions make use of a cmake.sh script, and I’ve just been 
> manually adding
> > > > the variable to that file because I can’t quite figure out 
> how to tell the
> > 

Re: [Paraview] Private pipeline

[Moreland, Kenneth]

Wow! Thousands of objects in your pipeline browser? You must have some scripts 
to generate all those objects (or spend hours each time setting up your 
pipelines).

There is no way in to get the pipeline browser to group sections of the 
pipeline or show subsections of it. It is conceivable to create your own 
version of a pipeline browser that showed subsets of the pipeline like you want 
and put that in your own plugin, but it would be a fairly difficult programming 
project.

You might consider simpler alternatives. Rather than create thousands of 
objects in your pipeline browser, perhaps you can create custom filters that 
encapsulate (and hide) lots of filters inside it. Implementing filters in 
VTK/ParaView using several other filters internally is pretty common. It is 
much easier to create a plugin with a custom filter than to make a plugin with 
a custom pipeline browser. You could also consider using the Custom Filter 
feature (http://www.paraview.org/Wiki/ParaView/Custom_Filters). It allows you 
to create a metafilter from a collection of other filters in the ParaView GUI. 
It is easier than making a plugin, but has more limited functionality.

-Ken

From: Шагит Зиганшин [mailto:ziganshinsha...@hotmail.com]
Sent: Monday, August 15, 2016 9:38 AM
To: Moreland, Kenneth ; paraview@paraview.org
Subject: [EXTERNAL] RE: [Paraview] Private pipeline

If I'm working in multiple layouts my pipeline browser becomes a list of 
thousands of loosely coupled objects. I wish each layout had own “custom“ 
pipeline browser, is it possible to make it as part of plug-in?

Shagit Ziganshin

From: Moreland, Kenneth
Sent: Monday, August 15, 2016 6:18 PM
To: Шагит Зиганшин; 
paraview@paraview.org
Subject: RE: [Paraview] Private pipeline


I am not sure I totally understand by a “private pipeline,” but I think you 
mean that you have a pipeline that you set up in ParaView over and over again 
and you would like to add a button or something to ParaView to automatically 
create this pipeline with one click.



The short answer is, yes. There are many ways to customize ParaView. The 
easiest way is to add a macro based on a Python script. There are a pair of 
exercises in The ParaView Tutorial 
(http://www.paraview.org/Wiki/The_ParaView_Tutorial) that demonstrate how to do 
this.



-Ken



From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of ? 

Sent: Monday, August 15, 2016 7:28 AM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] Private pipeline



Hello,

I am looking for a way how to implement a private pipeline for a particular 
layout. is it possible to do this as part of third-party plug-in?



Thank you

Shagit Ziganshin
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Christopher Neal]

The catalyst edition was built at: 
/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build

/home/neal/software/ParaView_build is where I built a version of Paraview with 
Catalyst, development files, and no gui.

On 8/15/16, 11:41 AM, "Utkarsh Ayachit"  wrote:

Chris,

Cool. There's indeed a bug in the install rules. I'll have to it
fixed. BTW, I am assuming /home/neal/software/ParaView_build is the
direcotory where you build the Catalyst edition, is that correct?

On Mon, Aug 15, 2016 at 11:38 AM, Christopher Neal
 wrote:
> Hi Utkarsh,
>
> I pointed to my ParaView_build directory and the examples compile without 
any errors.
>
> cmake -DCMAKE_PREFIX_PATH=/home/neal/software/ParaView_build 
-DBUILD_FORTRAN_EXAMPLES:BOOL=ON /home/neal/software/ParaView/Examples/Catalyst/
>
> Hope this helps,
> Chris Neal
>
> On 8/15/16, 11:19 AM, "Utkarsh Ayachit"  
wrote:
>
> Chris,
>
> I suspect there's a bug in the "install development files" for a
> Catalyst edition. Can you try pointing the ParaView_DIR for the
> Catalyst Examples to the Catalyst build directory instead? Does that
> work?
>
> Utkarsh
>
> On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
>  wrote:
> > Hi Utkarsh,
> >
> > I have one more question related to the Catalyst edition. I have 
compiled the ‘Essentials’ build. I used the command below(for reference) to 
configure the edition, and everything seems to work out.
> >
> > ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
-CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
../Catalyst-v5.1.0-Base-Enable-Python-Essentials
> >
> > I’m trying to compile the Catalyst examples that are located in the 
original ParaView source tree using the Catalyst edition. I used the following 
command to configure the examples:
> >
> > cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
/home/neal/software/ParaView/Examples/Catalyst/
> >
> > cmake does not complain when I configure with the command above. 
But when I type ‘make’ I see an error that a header file cannot be located. 
It’s a header file that I know for a fact is located in the ‘Essentials’ build 
directory under …/include/paraview-5.1.
> >
> > I tried using the -DCMAKE_INCLUDE_PATH=[path to 
…/include/paraview-5.1] , but cmake tells me that the manually specified 
variable was not used.  The full line that I’m trying to use to configure the 
examples is:
> >
> > cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
-DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
 /home/neal/software/ParaView/Examples/Catalyst/
> >
> > Am I not specifying the include path correctly?
> >
> > Thank you,
> > Chris Neal
> >
> > On 8/15/16, 10:15 AM, "Utkarsh Ayachit" 
 wrote:
> >
> > Chris,
> >
> > Some thing like this should do the trick:
> >
> > > [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... 
path to Catalyst src ...]
> >
> > Utkarsh
> >
> >
> >
> >
> > On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
> >  wrote:
> > > Hi All,
> > >
> > >
> > >
> > > I was wondering what the appropriate way to specify a value 
for the cmake
> > > variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst 
edition.  The
> > > editions make use of a cmake.sh script, and I’ve just been 
manually adding
> > > the variable to that file because I can’t quite figure out 
how to tell the
> > > script to also use a value for CMAKE_INSTALL_PREFIX that I 
pass to it.
> > >
> > > Does anyone have experience with doing this? I ask because I 
always want to
> > > change the install directory to be a different location than 
the default
> > > location in the root directory that Catalyst usually tries to 
install in.
> > >
> > >
> > > Thank you,
> > >
> > > Chris Neal
> > >
> > >
> > > ___
>   

Re: [Paraview] Private pipeline

[Шагит Зиганшин]

If I'm working in multiple layouts my pipeline browser becomes a list of 
thousands of loosely coupled objects. I wish each layout had own “custom“ 
pipeline browser, is it possible to make it as part of plug-in?

Shagit Ziganshin

From: Moreland, Kenneth
Sent: Monday, August 15, 2016 6:18 PM
To: Шагит Зиганшин; 
paraview@paraview.org
Subject: RE: [Paraview] Private pipeline

I am not sure I totally understand by a “private pipeline,” but I think you 
mean that you have a pipeline that you set up in ParaView over and over again 
and you would like to add a button or something to ParaView to automatically 
create this pipeline with one click.

The short answer is, yes. There are many ways to customize ParaView. The 
easiest way is to add a macro based on a Python script. There are a pair of 
exercises in The ParaView Tutorial 
(http://www.paraview.org/Wiki/The_ParaView_Tutorial) that demonstrate how to do 
this.

-Ken

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of ? 

Sent: Monday, August 15, 2016 7:28 AM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] Private pipeline

Hello,
I am looking for a way how to implement a private pipeline for a particular 
layout. is it possible to do this as part of third-party plug-in?

Thank you
Shagit Ziganshin
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Utkarsh Ayachit]

Chris,

Cool. There's indeed a bug in the install rules. I'll have to it
fixed. BTW, I am assuming /home/neal/software/ParaView_build is the
direcotory where you build the Catalyst edition, is that correct?

On Mon, Aug 15, 2016 at 11:38 AM, Christopher Neal
 wrote:
> Hi Utkarsh,
>
> I pointed to my ParaView_build directory and the examples compile without any 
> errors.
>
> cmake -DCMAKE_PREFIX_PATH=/home/neal/software/ParaView_build 
> -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> /home/neal/software/ParaView/Examples/Catalyst/
>
> Hope this helps,
> Chris Neal
>
> On 8/15/16, 11:19 AM, "Utkarsh Ayachit"  wrote:
>
> Chris,
>
> I suspect there's a bug in the "install development files" for a
> Catalyst edition. Can you try pointing the ParaView_DIR for the
> Catalyst Examples to the Catalyst build directory instead? Does that
> work?
>
> Utkarsh
>
> On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
>  wrote:
> > Hi Utkarsh,
> >
> > I have one more question related to the Catalyst edition. I have 
> compiled the ‘Essentials’ build. I used the command below(for reference) to 
> configure the edition, and everything seems to work out.
> >
> > ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
> -CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
> ../Catalyst-v5.1.0-Base-Enable-Python-Essentials
> >
> > I’m trying to compile the Catalyst examples that are located in the 
> original ParaView source tree using the Catalyst edition. I used the 
> following command to configure the examples:
> >
> > cmake 
> -DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> /home/neal/software/ParaView/Examples/Catalyst/
> >
> > cmake does not complain when I configure with the command above. But 
> when I type ‘make’ I see an error that a header file cannot be located. It’s 
> a header file that I know for a fact is located in the ‘Essentials’ build 
> directory under …/include/paraview-5.1.
> >
> > I tried using the -DCMAKE_INCLUDE_PATH=[path to …/include/paraview-5.1] 
> , but cmake tells me that the manually specified variable was not used.  The 
> full line that I’m trying to use to configure the examples is:
> >
> > cmake 
> -DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> -DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
>  /home/neal/software/ParaView/Examples/Catalyst/
> >
> > Am I not specifying the include path correctly?
> >
> > Thank you,
> > Chris Neal
> >
> > On 8/15/16, 10:15 AM, "Utkarsh Ayachit"  
> wrote:
> >
> > Chris,
> >
> > Some thing like this should do the trick:
> >
> > > [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... path 
> to Catalyst src ...]
> >
> > Utkarsh
> >
> >
> >
> >
> > On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
> >  wrote:
> > > Hi All,
> > >
> > >
> > >
> > > I was wondering what the appropriate way to specify a value for 
> the cmake
> > > variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst 
> edition.  The
> > > editions make use of a cmake.sh script, and I’ve just been 
> manually adding
> > > the variable to that file because I can’t quite figure out how to 
> tell the
> > > script to also use a value for CMAKE_INSTALL_PREFIX that I pass 
> to it.
> > >
> > > Does anyone have experience with doing this? I ask because I 
> always want to
> > > change the install directory to be a different location than the 
> default
> > > location in the root directory that Catalyst usually tries to 
> install in.
> > >
> > >
> > > Thank you,
> > >
> > > Chris Neal
> > >
> > >
> > > ___
> > > Powered by www.kitware.com
> > >
> > > Visit other Kitware open-source projects at
> > > http://www.kitware.com/opensource/opensource.html
> > >
> > > Please keep messages on-topic and check the ParaView Wiki at:
> > > http://paraview.org/Wiki/ParaView
> > >
> > > Search the list archives at: 
> http://markmail.org/search/?q=ParaView
> > >
> > > Follow this link to subscribe/unsubscribe:
> > > http://public.kitware.com/mailman/listinfo/paraview
> > >
> >
> >
> >
>
>
>

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Christopher Neal]

Hi Utkarsh,

I pointed to my ParaView_build directory and the examples compile without any 
errors.

cmake -DCMAKE_PREFIX_PATH=/home/neal/software/ParaView_build 
-DBUILD_FORTRAN_EXAMPLES:BOOL=ON /home/neal/software/ParaView/Examples/Catalyst/

Hope this helps,
Chris Neal

On 8/15/16, 11:19 AM, "Utkarsh Ayachit"  wrote:

Chris,

I suspect there's a bug in the "install development files" for a
Catalyst edition. Can you try pointing the ParaView_DIR for the
Catalyst Examples to the Catalyst build directory instead? Does that
work?

Utkarsh

On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
 wrote:
> Hi Utkarsh,
>
> I have one more question related to the Catalyst edition. I have compiled 
the ‘Essentials’ build. I used the command below(for reference) to configure 
the edition, and everything seems to work out.
>
> ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
-CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
../Catalyst-v5.1.0-Base-Enable-Python-Essentials
>
> I’m trying to compile the Catalyst examples that are located in the 
original ParaView source tree using the Catalyst edition. I used the following 
command to configure the examples:
>
> cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
/home/neal/software/ParaView/Examples/Catalyst/
>
> cmake does not complain when I configure with the command above. But when 
I type ‘make’ I see an error that a header file cannot be located. It’s a 
header file that I know for a fact is located in the ‘Essentials’ build 
directory under …/include/paraview-5.1.
>
> I tried using the -DCMAKE_INCLUDE_PATH=[path to …/include/paraview-5.1] , 
but cmake tells me that the manually specified variable was not used.  The full 
line that I’m trying to use to configure the examples is:
>
> cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
-DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
 /home/neal/software/ParaView/Examples/Catalyst/
>
> Am I not specifying the include path correctly?
>
> Thank you,
> Chris Neal
>
> On 8/15/16, 10:15 AM, "Utkarsh Ayachit"  
wrote:
>
> Chris,
>
> Some thing like this should do the trick:
>
> > [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... path 
to Catalyst src ...]
>
> Utkarsh
>
>
>
>
> On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
>  wrote:
> > Hi All,
> >
> >
> >
> > I was wondering what the appropriate way to specify a value for the 
cmake
> > variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst edition. 
 The
> > editions make use of a cmake.sh script, and I’ve just been manually 
adding
> > the variable to that file because I can’t quite figure out how to 
tell the
> > script to also use a value for CMAKE_INSTALL_PREFIX that I pass to 
it.
> >
> > Does anyone have experience with doing this? I ask because I always 
want to
> > change the install directory to be a different location than the 
default
> > location in the root directory that Catalyst usually tries to 
install in.
> >
> >
> > Thank you,
> >
> > Chris Neal
> >
> >
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
>
>



___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Christopher Neal]

I’m not sure I understand 100% what you’re asking me to do. Do you want me to 
copy the Catalyst examples directory from my ParaView source tree into my 
Catalyst ‘Essentials’ edition source tree and then run the configure command?

Or do you want me to point the ParaView build for the DCMAKE_PREFIX_PATH 
variable?

On 8/15/16, 11:19 AM, "Utkarsh Ayachit"  wrote:

Chris,

I suspect there's a bug in the "install development files" for a
Catalyst edition. Can you try pointing the ParaView_DIR for the
Catalyst Examples to the Catalyst build directory instead? Does that
work?

Utkarsh

On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
 wrote:
> Hi Utkarsh,
>
> I have one more question related to the Catalyst edition. I have compiled 
the ‘Essentials’ build. I used the command below(for reference) to configure 
the edition, and everything seems to work out.
>
> ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
-CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
../Catalyst-v5.1.0-Base-Enable-Python-Essentials
>
> I’m trying to compile the Catalyst examples that are located in the 
original ParaView source tree using the Catalyst edition. I used the following 
command to configure the examples:
>
> cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
/home/neal/software/ParaView/Examples/Catalyst/
>
> cmake does not complain when I configure with the command above. But when 
I type ‘make’ I see an error that a header file cannot be located. It’s a 
header file that I know for a fact is located in the ‘Essentials’ build 
directory under …/include/paraview-5.1.
>
> I tried using the -DCMAKE_INCLUDE_PATH=[path to …/include/paraview-5.1] , 
but cmake tells me that the manually specified variable was not used.  The full 
line that I’m trying to use to configure the examples is:
>
> cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
-DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
 /home/neal/software/ParaView/Examples/Catalyst/
>
> Am I not specifying the include path correctly?
>
> Thank you,
> Chris Neal
>
> On 8/15/16, 10:15 AM, "Utkarsh Ayachit"  
wrote:
>
> Chris,
>
> Some thing like this should do the trick:
>
> > [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... path 
to Catalyst src ...]
>
> Utkarsh
>
>
>
>
> On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
>  wrote:
> > Hi All,
> >
> >
> >
> > I was wondering what the appropriate way to specify a value for the 
cmake
> > variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst edition. 
 The
> > editions make use of a cmake.sh script, and I’ve just been manually 
adding
> > the variable to that file because I can’t quite figure out how to 
tell the
> > script to also use a value for CMAKE_INSTALL_PREFIX that I pass to 
it.
> >
> > Does anyone have experience with doing this? I ask because I always 
want to
> > change the install directory to be a different location than the 
default
> > location in the root directory that Catalyst usually tries to 
install in.
> >
> >
> > Thank you,
> >
> > Chris Neal
> >
> >
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
>
>



___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Utkarsh Ayachit]

Chris,

I suspect there's a bug in the "install development files" for a
Catalyst edition. Can you try pointing the ParaView_DIR for the
Catalyst Examples to the Catalyst build directory instead? Does that
work?

Utkarsh

On Mon, Aug 15, 2016 at 11:07 AM, Christopher Neal
 wrote:
> Hi Utkarsh,
>
> I have one more question related to the Catalyst edition. I have compiled the 
> ‘Essentials’ build. I used the command below(for reference) to configure the 
> edition, and everything seems to work out.
>
> ./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
> -CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
> ../Catalyst-v5.1.0-Base-Enable-Python-Essentials
>
> I’m trying to compile the Catalyst examples that are located in the original 
> ParaView source tree using the Catalyst edition. I used the following command 
> to configure the examples:
>
> cmake 
> -DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> /home/neal/software/ParaView/Examples/Catalyst/
>
> cmake does not complain when I configure with the command above. But when I 
> type ‘make’ I see an error that a header file cannot be located. It’s a 
> header file that I know for a fact is located in the ‘Essentials’ build 
> directory under …/include/paraview-5.1.
>
> I tried using the -DCMAKE_INCLUDE_PATH=[path to …/include/paraview-5.1] , but 
> cmake tells me that the manually specified variable was not used.  The full 
> line that I’m trying to use to configure the examples is:
>
> cmake 
> -DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
>  -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
> -DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
>  /home/neal/software/ParaView/Examples/Catalyst/
>
> Am I not specifying the include path correctly?
>
> Thank you,
> Chris Neal
>
> On 8/15/16, 10:15 AM, "Utkarsh Ayachit"  wrote:
>
> Chris,
>
> Some thing like this should do the trick:
>
> > [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... path to 
> Catalyst src ...]
>
> Utkarsh
>
>
>
>
> On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
>  wrote:
> > Hi All,
> >
> >
> >
> > I was wondering what the appropriate way to specify a value for the 
> cmake
> > variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst edition.  The
> > editions make use of a cmake.sh script, and I’ve just been manually 
> adding
> > the variable to that file because I can’t quite figure out how to tell 
> the
> > script to also use a value for CMAKE_INSTALL_PREFIX that I pass to it.
> >
> > Does anyone have experience with doing this? I ask because I always 
> want to
> > change the install directory to be a different location than the default
> > location in the root directory that Catalyst usually tries to install 
> in.
> >
> >
> > Thank you,
> >
> > Chris Neal
> >
> >
> > ___
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Private pipeline

[Moreland, Kenneth]

I am not sure I totally understand by a “private pipeline,” but I think you 
mean that you have a pipeline that you set up in ParaView over and over again 
and you would like to add a button or something to ParaView to automatically 
create this pipeline with one click.

The short answer is, yes. There are many ways to customize ParaView. The 
easiest way is to add a macro based on a Python script. There are a pair of 
exercises in The ParaView Tutorial 
(http://www.paraview.org/Wiki/The_ParaView_Tutorial) that demonstrate how to do 
this.

-Ken

From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of ? 

Sent: Monday, August 15, 2016 7:28 AM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] Private pipeline

Hello,
I am looking for a way how to implement a private pipeline for a particular 
layout. is it possible to do this as part of third-party plug-in?

Thank you
Shagit Ziganshin
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] ParaviewWeb security

[Sebastien Jourdain]

Hi Sven,

We do take security seriously.  Several actions have been made to make the
exposed protocols more secured.
It is true, that legacy protocol like ParaViewWebPipelineManager does not
check for code injection. But that protocol is deprecated and will be
removed for the next ParaView release (5.2).

In the current ParaViewWebProxyManager we do check that the user is allowed
to create the given requested proxy.

@exportRpc("pv.proxy.manager.create")
def create(self, functionName, parentId):
"""
Creates a new filter/source proxy as a child of the specified
parent proxy.  Returns the proxy state for the newly created
proxy as a JSON object.
"""
name = self.validate(functionName)

if not name:
return { 'success': False,
 'reason': '"' + functionName + '" was not valid and
could not be evaluated' }

   [...]

Regarding the access outside of the --data-dir we are preventing the user
from listing any file outside of that directory

if not currentPath.startswith(normBase):
print "### CAUTION =="
print " Attempt to get to another root path ###"
print "  => Requested:", relativeDir
print "  => BaseDir:", normBase
print "  => Computed path:", currentPath
print "### CAUTION =="
currentPath = normBase

Although, it is true that we are not guarding the "open" function which is
a mistake and it will be address right away.

Regarding your question, ParaViewWeb tend to be deployed on secured
environments (intranet and/or behind firewalls) but could be deployed on
the internet if specific actions are taking care. The authentication should
be delegated to your infrastructure and your infrastructure should be
responsible of launching the ParaView process under the user privilege. Our
Python launcher is provided as an example and for quick demos in a secured
environment but can not be considered secured. Since we delegate the
launching and the authentication to your infrastructure, you should also
provide a mechanism to share in a secure way the secret key that was used
to launch your application. The goal of that secret key is to prevent any
user that could have guessed your session ID (endpoint URL) to connect to
your dedicated WebSocket.

Then, after that, we are assuming some kind of user responsibility as we
seems to trust them enough to use server side resources. Specially as they
can still bring down the machine by filling up the memory and/or using all
the CPU via complex geometry/pipeline processing. In which case, it will be
fairly hard to prevent such behavior.

Regarding your last question, we do not provide any commercial alternative
but we provide support which could be used to improve our current Open
source solutions to match your expectations or create new products which
will be your property.

Seb



On Sat, Aug 13, 2016 at 4:53 AM, Sven Kramer  wrote:

> I was wondering, if ParaviewWeb takes security concerns serious. Studying
> the server code, I found no measures against access to files outside of the
> specified --data-dir, against XSS or injection of arbitrary code in analogy
> to SQL injection.
>
> Would you consider ParaviewWeb secure when the server is open to anybody
> in the internet, or is its purpose only to be run within intranets behind a
> firewall? Assuming that ParaviewWeb has not undergone any security audits,
> are there any commercial alternatives?
>
> Thank you
> Sven
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Christopher Neal]

Hi Utkarsh,

I have one more question related to the Catalyst edition. I have compiled the 
‘Essentials’ build. I used the command below(for reference) to configure the 
edition, and everything seems to work out.

./../Catalyst-v5.1.0-Base-Enable-Python-Essentials/cmake.sh 
-CMAKE_INSTALL_PREFIX:PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DPARAVIEW_INSTALL_DEVELOPMENT_FILES:BOOL=ON 
../Catalyst-v5.1.0-Base-Enable-Python-Essentials

I’m trying to compile the Catalyst examples that are located in the original 
ParaView source tree using the Catalyst edition. I used the following command 
to configure the examples:

cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
/home/neal/software/ParaView/Examples/Catalyst/

cmake does not complain when I configure with the command above. But when I 
type ‘make’ I see an error that a header file cannot be located. It’s a header 
file that I know for a fact is located in the ‘Essentials’ build directory 
under …/include/paraview-5.1. 

I tried using the -DCMAKE_INCLUDE_PATH=[path to …/include/paraview-5.1] , but 
cmake tells me that the manually specified variable was not used.  The full 
line that I’m trying to use to configure the examples is:

cmake 
-DCMAKE_PREFIX_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build
 -DBUILD_FORTRAN_EXAMPLES:BOOL=ON 
-DCMAKE_INCLUDE_PATH=/home/neal/software/Catalyst/Catalyst-v5.1.0-Base-Enable-Python-Essentials_build/include/paraview-5.1
 /home/neal/software/ParaView/Examples/Catalyst/

Am I not specifying the include path correctly?

Thank you,
Chris Neal

On 8/15/16, 10:15 AM, "Utkarsh Ayachit"  wrote:

Chris,

Some thing like this should do the trick:

> [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... path to 
Catalyst src ...]

Utkarsh




On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
 wrote:
> Hi All,
>
>
>
> I was wondering what the appropriate way to specify a value for the cmake
> variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst edition.  The
> editions make use of a cmake.sh script, and I’ve just been manually adding
> the variable to that file because I can’t quite figure out how to tell the
> script to also use a value for CMAKE_INSTALL_PREFIX that I pass to it.
>
> Does anyone have experience with doing this? I ask because I always want 
to
> change the install directory to be a different location than the default
> location in the root directory that Catalyst usually tries to install in.
>
>
> Thank you,
>
> Chris Neal
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 'make install'

[Christopher Neal]

Hey guys,

 

I don’t know if it helps, but the way that I’ve been able to get around the 
issue is to:

1.) Make a directory in the ParaView build directory called ‘tempbin’
2.) Copy all binaries from the ParaView ‘bin’ directory into ‘tempbin’

3.) Delete all files in ‘bin’
4.) Create symbolic links to all files in the ‘tempbin’ directory so that the 
‘bin’ directory is full of symbolic links
5.) Re-do ‘make’   ( it’s just what I had to do in order to get it to work)
6.) do ‘make install’

Now all of the header files and things are moved to the correct locations and 
the make install process doesn’t result in binaries being removed from the 
‘bin’ directory.  It’s a bit of a headscratcher, but I guess this fix results 
in that IF block that checks for symbolic links status not being executed in 
file: VTK/Utilities/HashSource/cmake_install.cmake:46

Best regards,
Chris Neal

 

From: Christopher Neal 
Date: Friday, August 5, 2016 at 1:25 PM
To: Andy Bauer , Utkarsh Ayachit 

Cc: Ben Boeckel , "paraview@paraview.org" 

Subject: Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 
'make install'

 

For the case outlined in this email chain, it is the ParaView source. I’m 
currently using Paraview5.2.  I have also had the same trouble with: 
Catalyst-v5.1.0-Base-Enable-Python-Essentials, with the symbolic link ad-hoc 
solution working with this case as well.

 

From: Andy Bauer 
Date: Friday, August 5, 2016 at 1:19 PM
To: Utkarsh Ayachit 
Cc: Christopher Neal , Ben Boeckel 
, "paraview@paraview.org" 
Subject: Re: [Paraview] vtkHashSource-pv5.1 binary disappearing during ParaView 
'make install'

 

Hi Chris,

Are you trying to build from a Catalyst edition or directly from the full 
ParaView source? I want to make sure that we're going in the proper direction 
when trying to fix this problem.

Thanks,

Andy

 

On Fri, Aug 5, 2016 at 1:15 PM, Utkarsh Ayachit  
wrote:

Ben,

Can you take a look please?  Thanks.

On Fri, Aug 5, 2016 at 1:03 PM, Christopher Neal
 wrote:
> I tried it again with cmake 3.5.1 and I see the same error.
>
> -- Up-to-date: 
> /home/neal/software/ParaView5.2/build/lib/cmake/paraview-5.1/Modules/vtkUtilitiesHashSource.cmake
> CMake Error at VTK/Utilities/HashSource/cmake_install.cmake:46 (file):
>   file INSTALL cannot find
>   "/home/neal/software/ParaView5.2/build/bin/vtkHashSource-pv5.1".
> Call Stack (most recent call first):
>   VTK/cmake_install.cmake:148 (include)
>   cmake_install.cmake:117 (include)
>
> I did find a way around the issue by creating a ‘tempbin’ directory and 
> copying the binaries into that directory and then making a symbolic link from 
> the ‘bin’ to the binaries in the ‘tempbin’.
>
> The code that the make install is failing 
> on(VTK/Utilities/HashSource/cmake_install.cmake:46 ) has the following part 
> that is leading to the error:
>
> if(NOT CMAKE_INSTALL_COMPONENT OR "${CMAKE_INSTALL_COMPONENT}" STREQUAL 
> "RuntimeLibraries")
>   if(EXISTS "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1" AND
>  NOT IS_SYMLINK 
> "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1")
> file(RPATH_CHECK
>  FILE "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1"
>  RPATH "")
>   endif()
>   file(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/bin" TYPE EXECUTABLE 
> FILES "/home/neal/software/ParaView5.2/build/bin/vtkHashSource-pv5.1")
>   if(EXISTS "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1" AND
>  NOT IS_SYMLINK 
> "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1")
> file(RPATH_CHANGE
>  FILE "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1"
>  OLD_RPATH "/home/neal/software/ParaView5.2/build/lib:"
>  NEW_RPATH "")
> if(CMAKE_INSTALL_DO_STRIP)
>   execute_process(COMMAND "/usr/bin/strip" 
> "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1")
> endif()
>   endif()
> endif()
>
>
> There’s a if statement that checks to see if the executable is symbolic, and 
> if it is it skips the following operation, which I believe is the source of 
> my issue:
>
> file(RPATH_CHANGE
>  FILE "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/vtkHashSource-pv5.1"
>  OLD_RPATH "/home/neal/software/ParaView5.2/build/lib:"
>  NEW_RPATH "")
>
> -Chris
>
>
> On 8/5/16, 11:40 AM, "ParaView on behalf of Christopher Neal" 
>  wrote:
>
> Thank you Utkarsh,
>
> I will try cmake 3.5.1 to see if that has any effect on the issue that 
> I’m having.
>
> Output from: cmake –version
> cmake version 3.6.20160722-g8842a
>
>
> 

Re: [Paraview] Specify value for CMAKE_INSTALL_PREFIX when compiling Catalyst?

[Utkarsh Ayachit]

Chris,

Some thing like this should do the trick:

> [...]/cmake.sh -DCMAKE_INSTALL_PREFIX:PATH=/tmp/install [... path to Catalyst 
> src ...]

Utkarsh




On Fri, Aug 12, 2016 at 5:49 PM, Christopher Neal
 wrote:
> Hi All,
>
>
>
> I was wondering what the appropriate way to specify a value for the cmake
> variable CMAKE_INSTALL_PREFIX is when compiling a Catalyst edition.  The
> editions make use of a cmake.sh script, and I’ve just been manually adding
> the variable to that file because I can’t quite figure out how to tell the
> script to also use a value for CMAKE_INSTALL_PREFIX that I pass to it.
>
> Does anyone have experience with doing this? I ask because I always want to
> change the install directory to be a different location than the default
> location in the root directory that Catalyst usually tries to install in.
>
>
> Thank you,
>
> Chris Neal
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [Non-DoD Source] Re: Qt version support update 2016

[michal wozniak]

Hi,
I'm currently using qt 5.6 with vs 2015 and python 2.7 and everything is 
building correctly. I still didn't try QT 5.7.  On Windows, you need to make 
sure your PATH are set correctly. Verify that your CMake PATH isn't set before 
your qt or else your ParaView executable will find some qt dll in the CMake 
folder. 
DLL not found - > http://www.dependencywalker.com/  This will help you track 
down your problems. 
From: shawn.wal...@kitware.com
Date: Mon, 15 Aug 2016 09:06:27 -0400
To: simon.m.su@mail.mil
CC: paraview@paraview.org
Subject: Re: [Paraview] [Non-DoD Source] Re: Qt version support update 2016

Mega Mind,

I have a project that is using ParaView with Qt 5.7 on Windows.  Of course we 
use VS 2013 still, so that may be the difference.  It still sounds like you 
forgot to set the PARAVIEW_QT_VERSION to 5.  If this is 4 (the default), the 
CMake scripts will ignore Qt5.  I think it may be smart enough to default to 5 
when there is no Qt4 preset which may be why that build worked.  Our build 
machine has both Qt4 and Qt5 installed and it works fine.  Still, I don't know 
if anyone has tried Qt5 + VS 2015  Anyway, your runtime error with the dll 
not found?  That is a Windows thing.  Not found means it is not in the PATH 
environment variable's list of folders.  Windows doesn't bake into the 
executable the paths to its runtime dependencies.  Linux and OSX do, which is 
why you can typically run things from a build tree there without any problems.  
But to run it from Windows, you will need to add the Qt5 dll's directory to 
your PATH or move it to the same directory as the executable which needs it.

Simon,

The ParaView Superbuild uses a precompiled python 2.7 that was built with VS 
2008.  Python 2.x doesn't support any newer versions (maybe 2010, but we've 
never used that version of python).  Since the API we link against is pure C, 
there are no ABI issues with using this prebuilt version.  You should be able 
to look in the superbuild and find the path for the zip file with the prebuilt 
python and download/use that one.  I know Python 3 is supported in VTK, but I'm 
not sure it is fully supported in ParaView yet.

HTH,
Shawn

On Sat, Aug 13, 2016 at 6:30 PM, Su, Simon M CIV USARMY RDECOM ARL (US) 
 wrote:







you need python in the path for QT 5 to build for windows. specifically python 
with bz2 module both running configure and nmake 



the next problem you will encounter after getting past the QT 5 which I am 
still stuck is to build python. Python 3 will compile with vs2015 express, 
python 2.x will not. c++ time zone related variables changes. But I am not able 
to compile pv with python 3.
  I even tried to fix the time zone related compile but end up with linking 
error at the very end. 



because of this, i think win7 or win10 pv will only work with vs2013 
express.




hth
-s






From: ParaView [paraview-boun...@paraview.org] on behalf of Mega Mind 
[123megam...@gmail.com]

Sent: Saturday, August 13, 2016 5:00 PM

To: Shawn Waldon

Cc: ParaView list

Subject: [Non-DoD Source] Re: [Paraview] Qt version support update 2016





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









Have you or anyone successfully built and installed on Win7 64 with Visual 
Studio 2015? I always get errors when building or opening the paraview.exe. For 
Qt the 4.x versions seem to have only x86 installs but I installed 4.8 anyway. 
When trying
 Qt 5.7 I get a failed build with 3 errors and over 350 warnings. Also noted 
that in Cmake configure it would still reference Qt 4 even after setting 
Qt5_DIR Qt5Core_DIR Qt5Widgets_DIR  etc and changing all paths to proper 
reference directories. The only fix
 was to uninstall Qt 4 but I was able to get a build with no errors when it was 
using both Qt 4 & 5 strangely but when opening paraview,exe the 'system error' 
message was Qt5Widgets.dll does not exist. It does though and is in "C:\Program 
Files (x86)\Qt\5.7\msvc2015_64\bin\"
 so I tried to manually change that in any Cmake config file I could find but 
nothing worked out. I've tried hundreds of things over the past three days and 
read and followed the wiki many times and I'm coming to the conclusion no one 
is using Win 64 which
 seems strange to me but I guess everyone is using Unix.




On Fri, Aug 12, 2016 at 5:18 AM, Shawn Waldon 
 > wrote:



To use Qt5, you have to set the PARAVIEW_QT_VERSION variable to 5 (it still 
defaults to 4, which is why cmake is complaining).  Note that some things may 
be buggy when building against Qt5, I don't know the full list of current 
issues, just that there
 are some.  Also note that you have to specify the location of Qt5 differently 
to CMake.  CMake 

Re: [Paraview] Plot3D Function Files

[Berk Geveci]

Dear Michael,

Even though this doesn't exist, it would be relatively easy to add. This
would be through this reader:

http://www.vtk.org/doc/nightly/html/classvtkPlot3DMetaReader.html

I suggest that you create a feature request on the VTK issue tracker:

https://gitlab.kitware.com/vtk/vtk/issues

Hopefully, someone will pick it up during the next VTK or ParaView
hackathon.

Best,
-berk

On Sat, Aug 13, 2016 at 9:15 PM, Michael Nucci 
wrote:

> When I read in Plot3D function files my variables are named Function0,
> Function1, etc. I can rename them with the calculator filter, but doing
> this each time gets tedious. I was wondering if there was a way to point
> paraview to a text file containing the correct names during the read so
> that they would automatically come in with the correct names.
>
> Thanks,
> Michael Nucci
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Private pipeline

[Шагит Зиганшин]

Hello,
I am looking for a way how to implement a private pipeline for a particular 
layout. is it possible to do this as part of third-party plug-in?

Thank you
Shagit Ziganshin
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [Non-DoD Source] Re: Qt version support update 2016

[Shawn Waldon]

Mega Mind,

I have a project that is using ParaView with Qt 5.7 on Windows.  Of course
we use VS 2013 still, so that may be the difference.  It still sounds like
you forgot to set the PARAVIEW_QT_VERSION to 5.  If this is 4 (the
default), the CMake scripts will ignore Qt5.  I think it may be smart
enough to default to 5 when there is no Qt4 preset which may be why that
build worked.  Our build machine has both Qt4 and Qt5 installed and it
works fine.  Still, I don't know if anyone has tried Qt5 + VS 2015
Anyway, your runtime error with the dll not found?  That is a Windows
thing.  Not found means it is not in the PATH environment variable's list
of folders.  Windows doesn't bake into the executable the paths to its
runtime dependencies.  Linux and OSX do, which is why you can typically run
things from a build tree there without any problems.  But to run it from
Windows, you will need to add the Qt5 dll's directory to your PATH or move
it to the same directory as the executable which needs it.

Simon,

The ParaView Superbuild uses a precompiled python 2.7 that was built with
VS 2008.  Python 2.x doesn't support any newer versions (maybe 2010, but
we've never used that version of python).  Since the API we link against is
pure C, there are no ABI issues with using this prebuilt version.  You
should be able to look in the superbuild and find the path for the zip file
with the prebuilt python and download/use that one.  I know Python 3 is
supported in VTK, but I'm not sure it is fully supported in ParaView yet.

HTH,
Shawn

On Sat, Aug 13, 2016 at 6:30 PM, Su, Simon M CIV USARMY RDECOM ARL (US) <
simon.m.su@mail.mil> wrote:

> you need python in the path for QT 5 to build for windows. specifically
> python with bz2 module both running configure and nmake
>
> the next problem you will encounter after getting past the QT 5 which I am
> still stuck is to build python. Python 3 will compile with vs2015 express,
> python 2.x will not. c++ time zone related variables changes. But I am not
> able to compile pv with python 3.  I even tried to fix the time zone
> related compile but end up with linking error at the very end.
>
> because of this, i think win7 or win10 pv will only work with vs2013
> express.
>
> hth
> -s
>
> --
> *From:* ParaView [paraview-boun...@paraview.org] on behalf of Mega Mind [
> 123megam...@gmail.com]
> *Sent:* Saturday, August 13, 2016 5:00 PM
> *To:* Shawn Waldon
> *Cc:* ParaView list
> *Subject:* [Non-DoD Source] Re: [Paraview] Qt version support update 2016
>
> All active links contained in this email were disabled. Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
> --
>
>
> Have you or anyone successfully built and installed on Win7 64 with Visual
> Studio 2015? I always get errors when building or opening the paraview.exe.
> For Qt the 4.x versions seem to have only x86 installs but I installed 4.8
> anyway. When trying Qt 5.7 I get a failed build with 3 errors and over 350
> warnings. Also noted that in Cmake configure it would still reference Qt 4
> even after setting Qt5_DIR Qt5Core_DIR Qt5Widgets_DIR  etc and changing all
> paths to proper reference directories. The only fix was to uninstall Qt 4
> but I was able to get a build with no errors when it was using both Qt 4 &
> 5 strangely but when opening paraview,exe the 'system error' message was
> Qt5Widgets.dll does not exist. It does though and is in "C:\Program Files
> (x86)\Qt\5.7\msvc2015_64\bin\" so I tried to manually change that in any
> Cmake config file I could find but nothing worked out. I've tried hundreds
> of things over the past three days and read and followed the wiki many
> times and I'm coming to the conclusion no one is using Win 64 which seems
> strange to me but I guess everyone is using Unix.
>
> On Fri, Aug 12, 2016 at 5:18 AM, Shawn Waldon  Caution-mailto:shawn.wal...@kitware.com > > wrote:
>
>> To use Qt5, you have to set the PARAVIEW_QT_VERSION variable to 5 (it
>> still defaults to 4, which is why cmake is complaining).  Note that some
>> things may be buggy when building against Qt5, I don't know the full list
>> of current issues, just that there are some.  Also note that you have to
>> specify the location of Qt5 differently to CMake.  CMake doesn't use the
>> QT_QMAKE_EXECUTABLE variable for Qt5, instead it uses Qt5_DIR.  This should
>> point to .../lib/cmake/Qt5 inside your Qt5 install.
>>
>> HTH,
>> Shawn
>>
>> On Fri, Aug 12, 2016 at 5:09 AM, Mega Mind <123megam...@gmail.com <
>> Caution-mailto:123megam...@gmail.com > > wrote:
>>
>>> Has the Qt version support advanced close to 5.7 yet?
>>> Cmake throws error that Qt 4.x required but read on mailing list some
>>> guys are using Qt 5.x.
>>> I'm installing Qt 4.8.1 but the only option seems to be x86 and for
>>> Visual 

Re: [Paraview] Paraview Build python dependency

[Utkarsh Ayachit]

With superbuild, I'd strongly recommend using Ninja instead of the VS
IDE. Ninja should also ensure that CPU utilization is maximum.

Utkarsh

On Thu, Aug 11, 2016 at 5:35 PM, michal wozniak  wrote:
> thanks
>
>
>
> I am currently trying the superbuild process. I usually pass pass /m:4 to my
> msbuild to get 4 msbuild instance. When I used to build paraview (not
> superbuild), the cpu utilization during the build was always at maximum but
> with superbuild it is always around 20%.
>
>
>
> Do I also need to pass /MP parameter to enable multi-processor build ?
>
>
>
>
>
>
>
> From: Utkarsh Ayachit
> Sent: Thursday, August 11, 2016 1:42 PM
> To: michal wozniak
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] Paraview Build python dependency
>
>
>
> I'd suggest using ParaView Superbuild to build redistributables
> (https://gitlab.kitware.com/paraview/paraview-superbuild).
>
> Utkarsh
>
> On Tue, Aug 9, 2016 at 3:23 PM, michal wozniak 
> wrote:
>> Hi,
>>
>> I am building ParaView from source. When we test my release version on a
>> different system, we can't use any feature that uses python : trace,
>> python
>> shell ...
>>
>> I installed your binary version and I saw that you provided the
>> python27.DLL
>> and a Lib folder which seem to be the one from python27 installation
>> directory. So I copy pasted python27.dll  and Lib folder into my release
>> folder. When I use this release folder on a different computer, Paraview
>> is
>> still crashing when we try to use  the trace feature which use python.
>>
>> Could someone tell me what's the correct way of deploying python with
>> ParaView.  If only there was some python tool like windeployqt.exe which
>> is
>> provided by qt.
>>
>> thanks
>>
>> Michal Wozniak
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Parallel rendering in the cave

[Max Reimann]

I am trying to get parallel rendering to work in ParaView 5.1 in a 
multi-display environment (cave) and keep getting this error when connecting 
from a client to a single or multiple render servers.


""

ERROR: In 
/da/sw/paraview/ParaView-5.1.0-source/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx,
 line 1404
vtkPVRenderView (0x1497060): In Cave mode and Display cannot be opened on 
server-side! Ensure the environment is set correctly in the pvx file.
""


I have followed the steps on the wiki and now trying to get a single rendering 
display to work. My cave.pvx looks like this:




 
  
  
  
 




And I start it with


mpirun -d   --report-bindings -H da-dev1 -np 2 
/paraview/install-5.1/bin/pvserver -sp=2052 /paraview/tvs.pvx



I have disabled all firewalls and set xhost to disable access control, but to 
no avail.
Starting paraview with x-forwarding works, however this can't work on multiple 
rendering displays, I assume.

Specs are:

- linux gentoo x64

- paraview 5.1 with vrplugin, openmpi, vrpn




UTS CRICOS Provider Code: 00099F
DISCLAIMER: This email message and any accompanying attachments may contain 
confidential information.
If you are not the intended recipient, do not read, use, disseminate, 
distribute or copy this message or
attachments. If you have received this message in error, please notify the 
sender immediately and delete
this message. Any views expressed in this message are those of the individual 
sender, except where the
sender expressly, and with authority, states them to be the views of the 
University of Technology Sydney.
Before opening any attachments, please check them for viruses and defects.

Think. Green. Do.

Please consider the environment before printing this email.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview