From jeremy.santina at gmail.com  Tue Jul  1 04:31:51 2014
From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=)
Date: Tue, 1 Jul 2014 10:31:51 +0200
Subject: [Paraview] Rendering in parallel
In-Reply-To: <CFD6CDF4.193FA%kmorel@sandia.gov>
References: <CAAPOYrGifEeTFy3-=Fm-nfzhmyjPRDkT48iM3fLnGKcsNqC=6w@mail.gmail.com>
 <CFD6CDF4.193FA%kmorel@sandia.gov>
Message-ID: <CAAPOYrF8LnNZ9UOxXeoiDyqKaKmqqv80+rPiLEwPfERCq1hSyg@mail.gmail.com>

Actually, I did try the D3 filter but I didn't really see any better
results. Maybe it is because I don't know how to configure it. How does D3
filter work ?



2014-06-30 16:21 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:

>   Jeremy,
>
>  Like the other parallel processing in ParaView, the efficiency is
> dictated by the distribution of the data. If your data distribution is
> highly imbalanced such as when all the data is on one process as in your
> case, then all the processing will happen where the data is and the rest of
> the processors will remain idle.
>
>  You could try running the D3 filter. That should redistribute the point
> data more evenly.
>
>  -Ken
>
>   From: J?r?my Santina <jeremy.santina at gmail.com>
> Date: Monday, June 30, 2014 2:55 AM
> To: "paraview at paraview.org" <paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] Rendering in parallel
>
>    Good morning,
>
>  I am a novice user of Paraview and there are some aspects which I am not
> familiar with. Here is one of the issues I am having :
>
> I run Paraview in Client-Server mode, performing the data processing and
> the rendering on the remote server, and I read a Tecplot Binary File (.plt)
> composed of more than 30 millions of points. This take a lot of time. An
> idea to speed up the calculation is to launch the server in parallel. I
> know that many readers can not read in parallel (it is the case of
> TecplotBinaryFileReader I think) so I don't expect any improvment in this
> way.
>
> But, examining the Timer Log, I noticed that it doesn't speed up the
> rendering either. I tested many times displaying the points and both
> experiment with parallelism and without gave the same results (about 40-50
> sec). I don't understand why.
>
>  Do I misinterpret the Timer Log ? Is the time of rendering long enough
> to conclude ? Do I have to set specific parameters to make it works ?
>
>  I thank you in advance for your help.
>
>  J?r?my
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/7fd39312/attachment.html>

From jfavre at cscs.ch  Tue Jul  1 04:32:16 2014
From: jfavre at cscs.ch (Favre  Jean)
Date: Tue, 1 Jul 2014 08:32:16 +0000
Subject: [Paraview] CRAY building with cray-mpich2
In-Reply-To: <CFD701C2.11D38%bak@lanl.gov>
References: <CFD701C2.11D38%bak@lanl.gov>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F681AA1389A@MBX21.d.ethz.ch>

We're running ParaView on our Cray XC30, with GPU rendering

here's my cmake line:

cmake -DMPI_C_COMPILER=/opt/cray/craype/2.1.0/bin/cc -DMPI_CXX_COMPILER=/opt/cray/craype/2.1.0/bin/CC -DMPI_CXX_LIBRARIES="/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib/libmpichcxx.so" -DMPI_C_LIBRARIES="/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib/libmpich.so" -DMPI_C_LINK_FLAGS="-L/opt/cray/libsci/12.2.0/GNU/48/sandybridge/lib -L/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib -L/opt/cray/atp/1.7.1/lib" -DMPI_CXX_LINK_FLAGS="-L/opt/cray/libsci/12.2.0/GNU/48/sandybridge/lib -L/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib -L/opt/cray/atp/1.7.1/lib" -DMPI_C_INCLUDE_PATH=/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/include -DMPI_CXX_INCLUDE_PATH=/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/include -DCMAKE_C_COMPILER=/opt/gcc/4.8.2/bin/gcc -DCMAKE_CXX_COMPILER=/opt/gcc/4.8.2/bin/g++ -DBUILD_TESTING=OFF -DPARAVIEW_ENABLE_CATALYST=OFF -DVTK_COSMO_USE_MPI=OFF -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools=OFF -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering=OFF -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit=OFF -DPARAVIEW_BUILD_PLUGIN_QuadView=OFF -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXE_LINKER_FLAGS_RELEASE=-Wl,-rpath,/opt/cray/nvidia/default/lib64 -L/opt/cray/nvidia/default/lib64 -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DCMAKE_INSTALL_PREFIX=/apps/santis/ParaView/4.1 -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DBUILD_SHARED_LIBS=ON -DOPENGL_INCLUDE_DIR=/opt/cray/nvidia/default/include -DOPENGL_gl_LIBRARY=/opt/cray/nvidia/default/lib64/libGL.so -DQT_QMAKE_EXECUTABLE=/apps/santis/Qt/4.8.5_gcc482/bin/qmake /apps/santis/ParaView/src/ParaView-v4.1.0

hope this helps.

-----------------
Jean M. Favre
Swiss National Supercomputing Center
CH-6900 Lugano
Switzerland



From mailinglists at xgm.de  Tue Jul  1 04:43:54 2014
From: mailinglists at xgm.de (Florian Lindner)
Date: Tue, 01 Jul 2014 10:43:54 +0200
Subject: [Paraview] Can't display/plot simple VTK
Message-ID: <lotsca$js8$1@ger.gmane.org>

Hello,

I have a VTK I want to plot/analyze in paraview. It does not really contain 
valid geometry information as far as I can tell, so I try to plot it using 
the Line Chart View.

I can watch the data using the SpreadSheet View but as soon as I change the 
tab to the Line Chart non of the sources in the pipeline browser is 
activatable (making the eye appear left to it)

Paraview is 4.1.0 on linux.
The small (17 KB) VTK is available at http://pastebin.com/HycUEmWB and I 
want to plot the SCALARS CrossSectionalArea float and the SCALARS Pressure 
float sections.

What is the problem there?

Thanks,
Florian


From simon.m.su.ctr at mail.mil  Tue Jul  1 08:37:31 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Tue, 1 Jul 2014 12:37:31 +0000
Subject: [Paraview] calculate total sum of a variable in CTH data
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED7F@umechp9h.easf.csd.disa.mil>

Hello,

I am trying to simply add up all the values of a variable in the dataset using programmable filter with the python code at the end of this email..



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/f6c1bbc9/attachment.html>

From simon.m.su.ctr at mail.mil  Tue Jul  1 08:40:23 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Tue, 1 Jul 2014 12:40:23 +0000
Subject: [Paraview] calculate total sum of a variable in CTH data
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED7F@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED7F@umechp9h.easf.csd.disa.mil>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED8F@umechp9h.easf.csd.disa.mil>


Hello,

I am trying to simply add up all the values of a variable in the CTH dataset using programmable filter with the python code at the end of this email..

The code seems to be working for the other dataset that I worked in the past. But for CTH dataset, it is giving me an error with GetCellData


Traceback (most recent call last):

File "<string>", line 22, in <module>

File "<string>", line 43, in RequestData

File "<string>", line 8, in calculateSum

AttributeError: GetCellData

When I printed the output for CTH dataset it is giving me


vtkNonOverlappingAMR (0x7f96ca7675c0)

Debug: Off

Modified Time: 860345754

Reference Count: 2

Registered Events: (none)

Information: 0x7f96ca767040

Data Released: False

Global Release Data: Off

UpdateTime: 856914636

Field Data:

Debug: Off

Modified Time: 855459763

Reference Count: 1

Registered Events: (none)

Number Of Arrays: 4

Array 0 name = GlobalBounds

Array 1 name = GlobalBoxSize

Array 2 name = MinLevel

Array 3 name = MinLevelSpacing

Number Of Components: 4

Number Of Tuples: 6

Any help is in adding a variable in a CTH dataset is much appreciated.

thank you
-simon

p/s: sorry for the other unfinished email sent....



=========================================
def calculateSum(input, output):
    # Copy the cells etc.
    output.ShallowCopy(input)

    # Get the array to calculate the coefficient
    toSum = output.GetPointData().GetArray("MOMENT_X")

    # for each of the elements, calculate the three roots and store the real and imaginary output in separate arrays
    numPoints = toSum.GetSize()

    # create the output arrays
    sum = vtk.vtkDoubleArray()
    sum.SetNumberOfValues(numPoints)
    sum.SetName("sum")
    tsum = 0

    for i in range(0, numPoints):
        tsum = tsum + toSum.GetValue(i)

    for j in range(0, numPoints):
        sum.SetValue(j, tsum)

    output.GetPointData().AddArray(sum)

input = self.GetInputDataObject(0, 0)
output = self.GetOutputDataObject(0)

if input.IsA("vtkMultiBlockDataSet"):
    output.CopyStructure(input)
    iter = input.NewIterator()
    iter.UnRegister(None)
    iter.InitTraversal()
    while not iter.IsDoneWithTraversal():
        curInput = iter.GetCurrentDataObject()
        curOutput = curInput.NewInstance()
        curOutput.UnRegister(None)
        output.SetDataSet(iter, curOutput)
        calculateSum(curInput, curOutput)
        iter.GoToNextItem();
else:
    calculateSum(input, output)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/e7f6f66e/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Tue Jul  1 08:56:31 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 1 Jul 2014 08:56:31 -0400
Subject: [Paraview] CRAY building with cray-mpich2
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F681AA1389A@MBX21.d.ethz.ch>
References: <CFD701C2.11D38%bak@lanl.gov>
 <0EB9B6375711A04B820E6B6F5CCA9F681AA1389A@MBX21.d.ethz.ch>
Message-ID: <CADHSJjDriu1T=xQuzRyPYqTHfEu577A_j_VztgQ53CU1ROKG5g@mail.gmail.com>

Bucky,

Like Jean, suggests, FindMPI can be tricky. It's easier to just
manually specify allt he MPI_<LANG>_<TYPE> flags explicitly. Let's
start there. If FindMPI still ends up messing up the variables you
set, can you force FindMPI to not do "interrogation" by adding the
following variables.

-D MPI_C_NO_INTERROGATE:STRING=<same value as MPI_C_COMPILER>
-D MPI_CXX_NO_INTERROGATE:STRING=<same value as MPI_CXX_COMPILER>
-D MPI_Fortran_NO_INTERROGATE:STRING=<same value as MPI_Fortran_COMPILER>

Utkarsh

On Tue, Jul 1, 2014 at 4:32 AM, Favre  Jean <jfavre at cscs.ch> wrote:
> We're running ParaView on our Cray XC30, with GPU rendering
>
> here's my cmake line:
>
> cmake -DMPI_C_COMPILER=/opt/cray/craype/2.1.0/bin/cc -DMPI_CXX_COMPILER=/opt/cray/craype/2.1.0/bin/CC -DMPI_CXX_LIBRARIES="/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib/libmpichcxx.so" -DMPI_C_LIBRARIES="/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib/libmpich.so" -DMPI_C_LINK_FLAGS="-L/opt/cray/libsci/12.2.0/GNU/48/sandybridge/lib -L/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib -L/opt/cray/atp/1.7.1/lib" -DMPI_CXX_LINK_FLAGS="-L/opt/cray/libsci/12.2.0/GNU/48/sandybridge/lib -L/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib -L/opt/cray/atp/1.7.1/lib" -DMPI_C_INCLUDE_PATH=/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/include -DMPI_CXX_INCLUDE_PATH=/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/include -DCMAKE_C_COMPILER=/opt/gcc/4.8.2/bin/gcc -DCMAKE_CXX_COMPILER=/opt/gcc/4.8.2/bin/g++ -DBUILD_TESTING=OFF -DPARAVIEW_ENABLE_CATALYST=OFF -DVTK_COSMO_USE_MPI=OFF -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools=OFF -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering=OFF -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit=OFF -DPARAVIEW_BUILD_PLUGIN_
>  QuadView=OFF -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXE_LINKER_FLAGS_RELEASE=-Wl,-rpath,/opt/cray/nvidia/default/lib64 -L/opt/cray/nvidia/default/lib64 -DPARAVIEW_ENABLE_PYTHON=ON -DPARAVIEW_USE_MPI=ON -DCMAKE_INSTALL_PREFIX=/apps/santis/ParaView/4.1 -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON -DBUILD_SHARED_LIBS=ON -DOPENGL_INCLUDE_DIR=/opt/cray/nvidia/default/include -DOPENGL_gl_LIBRARY=/opt/cray/nvidia/default/lib64/libGL.so -DQT_QMAKE_EXECUTABLE=/apps/santis/Qt/4.8.5_gcc482/bin/qmake /apps/santis/ParaView/src/ParaView-v4.1.0
>
> hope this helps.
>
> -----------------
> Jean M. Favre
> Swiss National Supercomputing Center
> CH-6900 Lugano
> Switzerland
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview

From andy.bauer at kitware.com  Tue Jul  1 08:58:53 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 1 Jul 2014 08:58:53 -0400
Subject: [Paraview] CRAY building with cray-mpich2
In-Reply-To: <CADHSJjDriu1T=xQuzRyPYqTHfEu577A_j_VztgQ53CU1ROKG5g@mail.gmail.com>
References: <CFD701C2.11D38%bak@lanl.gov>
 <0EB9B6375711A04B820E6B6F5CCA9F681AA1389A@MBX21.d.ethz.ch>
 <CADHSJjDriu1T=xQuzRyPYqTHfEu577A_j_VztgQ53CU1ROKG5g@mail.gmail.com>
Message-ID: <CAMaOp+HC8anXV_iKb8Nd9=rDhv5ipOSQijTBST3OCWkefGDNWA@mail.gmail.com>

Hi Bucky,

Attached is a CMakeCache.txt for Hopper at NERSC. It may be a bit outdated but
I know it worked at one point. You can check it out for the MPI library
specifications which can be quite hard to figure out on your own.

Regards,
Andy


On Tue, Jul 1, 2014 at 8:56 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com
> wrote:

> Bucky,
>
> Like Jean, suggests, FindMPI can be tricky. It's easier to just
> manually specify allt he MPI_<LANG>_<TYPE> flags explicitly. Let's
> start there. If FindMPI still ends up messing up the variables you
> set, can you force FindMPI to not do "interrogation" by adding the
> following variables.
>
> -D MPI_C_NO_INTERROGATE:STRING=<same value as MPI_C_COMPILER>
> -D MPI_CXX_NO_INTERROGATE:STRING=<same value as MPI_CXX_COMPILER>
> -D MPI_Fortran_NO_INTERROGATE:STRING=<same value as MPI_Fortran_COMPILER>
>
> Utkarsh
>
> On Tue, Jul 1, 2014 at 4:32 AM, Favre  Jean <jfavre at cscs.ch> wrote:
> > We're running ParaView on our Cray XC30, with GPU rendering
> >
> > here's my cmake line:
> >
> > cmake -DMPI_C_COMPILER=/opt/cray/craype/2.1.0/bin/cc
> -DMPI_CXX_COMPILER=/opt/cray/craype/2.1.0/bin/CC
> -DMPI_CXX_LIBRARIES="/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib/libmpichcxx.so"
> -DMPI_C_LIBRARIES="/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib/libmpich.so"
> -DMPI_C_LINK_FLAGS="-L/opt/cray/libsci/12.2.0/GNU/48/sandybridge/lib
> -L/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib -L/opt/cray/atp/1.7.1/lib"
> -DMPI_CXX_LINK_FLAGS="-L/opt/cray/libsci/12.2.0/GNU/48/sandybridge/lib
> -L/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/lib -L/opt/cray/atp/1.7.1/lib"
> -DMPI_C_INCLUDE_PATH=/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/include
> -DMPI_CXX_INCLUDE_PATH=/opt/cray/mpt/6.3.0/gni/mpich2-gnu/48/include
> -DCMAKE_C_COMPILER=/opt/gcc/4.8.2/bin/gcc
> -DCMAKE_CXX_COMPILER=/opt/gcc/4.8.2/bin/g++ -DBUILD_TESTING=OFF
> -DPARAVIEW_ENABLE_CATALYST=OFF -DVTK_COSMO_USE_MPI=OFF
> -DPARAVIEW_BUILD_PLUGIN_SierraPlotTools=OFF
> -DPARAVIEW_BUILD_PLUGIN_UncertaintyRendering=OFF
> -DPARAVIEW_BUILD_PLUGIN_SciberQuestToolKit=OFF -DPARAVIEW_BUILD_PLUGI
>  N_
> >  QuadView=OFF -DCMAKE_BUILD_TYPE=Release
> -DCMAKE_EXE_LINKER_FLAGS_RELEASE=-Wl,-rpath,/opt/cray/nvidia/default/lib64
> -L/opt/cray/nvidia/default/lib64 -DPARAVIEW_ENABLE_PYTHON=ON
> -DPARAVIEW_USE_MPI=ON -DCMAKE_INSTALL_PREFIX=/apps/santis/ParaView/4.1
> -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON
> -DBUILD_SHARED_LIBS=ON
> -DOPENGL_INCLUDE_DIR=/opt/cray/nvidia/default/include
> -DOPENGL_gl_LIBRARY=/opt/cray/nvidia/default/lib64/libGL.so
> -DQT_QMAKE_EXECUTABLE=/apps/santis/Qt/4.8.5_gcc482/bin/qmake
> /apps/santis/ParaView/src/ParaView-v4.1.0
> >
> > hope this helps.
> >
> > -----------------
> > Jean M. Favre
> > Swiss National Supercomputing Center
> > CH-6900 Lugano
> > Switzerland
> >
> >
> > _______________________________________________
> > 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://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
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/25c75dcc/attachment-0001.html>
-------------- next part --------------
# This is the CMakeCache file.
# For build in directory: /scratch/scratchdirs/acbauer/paraview-build
# It was generated by CMake: /global/common/hopper2/usg/cmake/2.8.10.1/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUI's for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//Dependencies for the target
AnalyzeReader_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Dependencies for the target
AnalyzeWriter_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Build the documentation (Doxygen).
BUILD_DOCUMENTATION:BOOL=OFF

//Build ParaView examples.
BUILD_EXAMPLES:BOOL=OFF

//Build IceT with shared libraries.
BUILD_SHARED_LIBS:BOOL=ON

//Build the testing tree.
BUILD_TESTING:BOOL=OFF

//Path to a program.
BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND

//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar

//For backwards compatibility, what version of CMake commands and
// syntax should this version of CMake try to support.
CMAKE_BACKWARDS_COMPATIBILITY:STRING=2.4

//Choose the type of build.
CMAKE_BUILD_TYPE:STRING=Release

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler.
CMAKE_CXX_COMPILER:FILEPATH=/opt/gcc/4.7.1/bin/g++

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release minsize builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during Release with Debug Info builds.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//C compiler.
CMAKE_C_COMPILER:FILEPATH=/opt/gcc/4.7.1/bin/gcc

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release minsize builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during Release with Debug Info builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=' '

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF

//Use HP pthreads.
CMAKE_HP_PTHREADS:BOOL=

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=/usr/local

//Path to a program.
CMAKE_LINKER:FILEPATH=/usr/common/usg/altd/1.0/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=' '

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Path to a program.
CMAKE_NM:FILEPATH=/usr/bin/nm

//Path to a program.
CMAKE_OBJCOPY:FILEPATH=/usr/bin/objcopy

//Path to a program.
CMAKE_OBJDUMP:FILEPATH=/usr/bin/objdump

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=ParaView

//Path to a program.
CMAKE_RANLIB:FILEPATH=/usr/bin/ranlib

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=' '

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Path to a program.
CMAKE_STRIP:FILEPATH=/usr/bin/strip

//Thread library used.
CMAKE_THREAD_LIBS:STRING=-lpthread

//Use the pthreads library.
CMAKE_USE_PTHREADS:BOOL=1

//If true, cmake will use relative paths in makefiles and projects.
CMAKE_USE_RELATIVE_PATHS:BOOL=OFF

//Use sproc libs.
CMAKE_USE_SPROC:BOOL=

//Use the win32 thread library.
CMAKE_USE_WIN32_THREADS:BOOL=

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=FALSE

//X11 extra flags.
CMAKE_X_CFLAGS:STRING=

//Libraries and options used in X11 programs.
CMAKE_X_LIBS:STRING=/usr/lib64/libSM.so;/usr/lib64/libICE.so;/usr/lib64/libX11.so;/usr/lib64/libXext.so

//Path to program used to compress files for transfer to the dart
// server
COMPRESSIONCOMMAND:FILEPATH=/usr/bin/gzip

//Path to the coverage program that CTest uses for performing coverage
// inspection
COVERAGE_COMMAND:FILEPATH=/opt/gcc/4.7.1/bin/gcov

//Extra command line flags to pass to the coverage tool
COVERAGE_EXTRA_FLAGS:STRING=-l

//Enable to build Debian packages
CPACK_BINARY_DEB:BOOL=OFF

//Enable to build NSIS packages
CPACK_BINARY_NSIS:BOOL=OFF

//Enable to build RPM packages
CPACK_BINARY_RPM:BOOL=OFF

//Enable to build STGZ packages
CPACK_BINARY_STGZ:BOOL=ON

//Enable to build TBZ2 packages
CPACK_BINARY_TBZ2:BOOL=OFF

//Enable to build TGZ packages
CPACK_BINARY_TGZ:BOOL=ON

//Enable to build TZ packages
CPACK_BINARY_TZ:BOOL=ON

//Enable to build TBZ2 source packages
CPACK_SOURCE_TBZ2:BOOL=ON

//Enable to build TGZ source packages
CPACK_SOURCE_TGZ:BOOL=ON

//Enable to build TZ source packages
CPACK_SOURCE_TZ:BOOL=ON

//Enable to build ZIP source packages
CPACK_SOURCE_ZIP:BOOL=OFF

//How many times to retry timed-out CTest submissions.
CTEST_SUBMIT_RETRY_COUNT:STRING=3

//How long to wait between timed-out CTest submissions.
CTEST_SUBMIT_RETRY_DELAY:STRING=5

//Path to a program.
CVSCOMMAND:FILEPATH=/usr/bin/cvs

//Options passed to the cvs update command.
CVS_UPDATE_OPTIONS:STRING=-d -A -P

//Value Computed by CMake
Cosmo_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/Cosmo

//Dependencies for the target
Cosmo_LIB_DEPENDS:STATIC=general;vtksys;general;vtkCommon;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;

//Value Computed by CMake
Cosmo_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/Cosmo

//Limit of reported errors, -1 reports all.
DART_BUILD_ERROR_REPORT_LIMIT:BOOL=OFF

//Limit of reported warnings, -1 reports all.
DART_BUILD_WARNING_REPORT_LIMIT:BOOL=OFF

//If you have Dart installed, where is it located?
DART_ROOT:PATH=DART_ROOT-NOTFOUND

//Maximum time allowed before CTest will kill the test.
DART_TESTING_TIMEOUT:STRING=1500

//Show the actual output of the build, or if off show a . for each
// 1024 bytes.
DART_VERBOSE_BUILD:BOOL=OFF

//Should Dart server send email when build errors are found in
// Continuous builds?
DELIVER_CONTINUOUS_EMAIL:BOOL=Off

//Value Computed by CMake
DICOMParser_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/DICOMParser

//Value Computed by CMake
DICOMParser_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/DICOMParser

//Build mpi4py support to allow python filters to use mpi calls
ENABLE_MPI4PY:BOOL=ON

//Path to a program.
GITCOMMAND:FILEPATH=/usr/common/usg/bin/git

//git command line client
GIT_EXECUTABLE:FILEPATH=/usr/common/usg/bin/git

//Path to gunzip executable
GUNZIPCOMMAND:FILEPATH=/usr/bin/gunzip

//Dependencies for the target
H5PartReader_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Value Computed by CMake
HDF5_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkhdf5

//Build HDF5 C++ Library
HDF5_BUILD_CPP_LIB:BOOL=OFF

//Build HIGH Level HDF5 Library
HDF5_BUILD_HL_LIB:BOOL=OFF

//Disable compiler warnings
HDF5_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Enable datasets larger than memory
HDF5_ENABLE_HSIZET:BOOL=ON

//Enable support for large (64-bit) files on Linux.
HDF5_ENABLE_LARGE_FILE:BOOL=ON

//Enable parallel build (requires MPI)
HDF5_ENABLE_PARALLEL:BOOL=OFF

//Use SZip Filter
HDF5_ENABLE_SZIP_SUPPORT:BOOL=OFF

//Enable Zlib Filters
HDF5_ENABLE_Z_LIB_SUPPORT:BOOL=ON

//Securely clear file buffers before writing to file
HDF5_Enable_Clear_File_Buffers:BOOL=ON

//Instrument The library
HDF5_Enable_Instrument:BOOL=OFF

//Enable metadata trace file collection
HDF5_METADATA_TRACE_FILE:BOOL=OFF

//Value Computed by CMake
HDF5_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkhdf5

//Value Computed by CMake
HDF5_SRC_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkhdf5/src

//Value Computed by CMake
HDF5_SRC_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkhdf5/src

//Whether to perform strict file format checks
HDF5_STRICT_FORMAT_CHECKS:BOOL=OFF

//Use the HDF5 1.6.x API by default
HDF5_USE_16_API_DEFAULT:BOOL=OFF

//Use the FLETCHER32 Filter
HDF5_USE_FILTER_FLETCHER32:BOOL=ON

//Use the NBIT Filter
HDF5_USE_FILTER_NBIT:BOOL=ON

//Use the SCALEOFFSET Filter
HDF5_USE_FILTER_SCALEOFFSET:BOOL=ON

//Use the SHUFFLE Filter
HDF5_USE_FILTER_SHUFFLE:BOOL=ON

//Use the PACKED BITS feature in h5dump
HDF5_USE_H5DUMP_PACKED_BITS:BOOL=ON

//IF data accuracy is guaranteed during data conversions
HDF5_WANT_DATA_ACCURACY:BOOL=ON

//exception handling functions is checked during data conversions
HDF5_WANT_DCONV_EXCEPTION:BOOL=ON

//Path to a program.
HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND

//Value Computed by CMake
ICET_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Utilities/IceT

//Sets the preferred `k' value for the radix-k algorithm.  This
// is the amount of simultaneous messages each process receives.
//  A value of 8 is generally good on most architectures, but in
// others that have slower computation with respect to network
// (such as BlueGene), a larger value may give better performance.
ICET_MAGIC_K:STRING=8

//Sets the preferred number of times an image may be split.  Some
// image compositing algorithms prefer to partition the images
// such that each process gets a piece.  Too many partitions, though,
// and you end up spending more time collecting them than you save
// balancing the compositing.
ICET_MAX_IMAGE_SPLIT:STRING=512

//This is set from VTK_MPIRUN_EXE.
ICET_MPIRUN_EXE:FILEPATH=ICET_MPIRUN_EXE-NOTFOUND

//Flag used by MPI start program.  Used to specify the number of
// processes.
ICET_MPI_NUMPROC_FLAG:STRING=-np

//Value Computed by CMake
ICET_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Utilities/IceT

//Use MPE to trace MPI communications.  This is helpful for developers
// trying to measure the performance of parallel compositing algorithms.
ICET_USE_MPE:BOOL=OFF

//Build MPI communication layer for IceT.
ICET_USE_MPI:BOOL=ON

//Build OpenGL support layer for IceT.
ICET_USE_OPENGL:BOOL=ON

//Value Computed by CMake
ICE_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Utilities/Xdmf2/Ice

//Path to a file.
ICE_HAVE_FCNTL:PATH=/usr/include

//Path to a file.
ICE_HAVE_MMAN:PATH=/usr/include/sys

//Path to a file.
ICE_HAVE_NETINET:PATH=/usr/include/netinet

//Value Computed by CMake
ICE_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Utilities/Xdmf2/Ice

//Dependencies for the target
IceTCore_LIB_DEPENDS:STATIC=general;m;general;m;

//Dependencies for the target
IceTGL_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;

//Dependencies for the target
IceTMPI_LIB_DEPENDS:STATIC=general;m;general;IceTCore;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;

//Path to java command, used by the Dart server to create html.
JAVACOMMAND:FILEPATH=/usr/bin/java

//Value Computed by CMake
KWCommon_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Common/KWCommon

//Enable testing in KWCommon (if BUILD_TESTING is ON as well).
KWCommon_BUILD_TESTING:BOOL=ON

//Dependencies for the target
KWCommon_LIB_DEPENDS:STATIC=general;vtkCommon;general;vtksys;

//Value Computed by CMake
KWCommon_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Common/KWCommon

//Command to build the project
MAKECOMMAND:STRING=/usr/bin/gmake -i

//Value Computed by CMake
MAPREDUCE_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/mrmpi

//Value Computed by CMake
MAPREDUCE_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/mrmpi

//Path to the memory checking command, used for memory error detection.
MEMORYCHECK_COMMAND:FILEPATH=MEMORYCHECK_COMMAND-NOTFOUND

//File that contains suppressions for the memory checker
MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH=

//Executable for running MPI programs.
MPIEXEC:FILEPATH=MPIEXEC-NOTFOUND

//Maximum number of processors available to run MPI applications.
MPIEXEC_MAX_NUMPROCS:STRING=2

//Flag used by MPI to specify the number of processes for MPIEXEC;
// the next option will be the number of processes.
MPIEXEC_NUMPROC_FLAG:STRING=-np

//These flags will come after all flags given to MPIEXEC.
MPIEXEC_POSTFLAGS:STRING=

//These flags will be directly before the executable that is being
// run by MPIEXEC.
MPIEXEC_PREFLAGS:STRING=

//Dependencies for the target
MPIPython_LIB_DEPENDS:STATIC=general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;/usr/common/usg/python/2.7.1/lib/libpython2.7.so.1.0;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;

//Path to a program.
MPI_CXX_COMPILER:FILEPATH=MPI_CXX_COMPILER-NOTFOUND

//MPI CXX compilation flags
MPI_CXX_COMPILE_FLAGS:STRING=

//MPI CXX include path
MPI_CXX_INCLUDE_PATH:STRING=/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/include

//MPI CXX libraries to link against
MPI_CXX_LIBRARIES:STRING=MPI_CXX_LIBRARIES-NOTFOUND

//MPI CXX linking flags
MPI_CXX_LINK_FLAGS:STRING=

//Path to a program.
MPI_C_COMPILER:FILEPATH=MPI_C_COMPILER-NOTFOUND

//MPI C compilation flags
MPI_C_COMPILE_FLAGS:STRING=

//MPI C include path
MPI_C_INCLUDE_PATH:STRING=/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/include

//MPI C libraries to link against
MPI_C_LIBRARIES:STRING=MPI_C_LIBRARIES-NOTFOUND

//MPI C linking flags
MPI_C_LINK_FLAGS:STRING=

//Extra MPI libraries to link against
MPI_EXTRA_LIBRARY:STRING=/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;/usr/lib64/librt.so;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;/usr/lib/alps/libalpslli.so;/usr/lib/alps/libalpsutil.so;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;/usr/lib64/libpthread.so

//MPI library to link against
MPI_LIBRARY:FILEPATH=/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so

//Dependencies for the target
MapReduceMPI_LIB_DEPENDS:STATIC=general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;

//Value Computed by CMake
MaterialLibrary_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/MaterialLibrary

//Value Computed by CMake
MaterialLibrary_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/MaterialLibrary

//Dependencies for the target
Moments_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Disable compiler warnings
NETCDF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Dependencies for the target
NIfTIReader_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Dependencies for the target
NIfTIWriter_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Path to a file.
OPENGL_INCLUDE_DIR:PATH=/usr/common/graphics/ParaView/Mesa-7.10.1/include

//Path to a library.
OPENGL_gl_LIBRARY:FILEPATH=

//Path to a library.
OPENGL_glu_LIBRARY:FILEPATH=/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libGLU.so

//Path to a file.
OPENGL_xmesa_INCLUDE_DIR:PATH=OPENGL_xmesa_INCLUDE_DIR-NOTFOUND

//Path to a file.
OSMESA_INCLUDE_DIR:PATH=/usr/common/graphics/ParaView/Mesa-7.10.1/include

//Path to a library.
OSMESA_LIBRARY:FILEPATH=/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so

//Build ParaView with enforced secure connection (--connect-id)
PARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=OFF

//Build Reader for *.bp files based on Adios
PARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=OFF

//Build Reader/Writer for Analyze and NIfTI.
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIReaderWriter:BOOL=ON

//Build EyeDomeLighting
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=OFF

//Build Override time requests
PARAVIEW_BUILD_PLUGIN_ForceTime:BOOL=OFF

//Build Reader for *.h5part files
PARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=ON

//Build Manta ray traced rendering
PARAVIEW_BUILD_PLUGIN_Manta:BOOL=OFF

//Build Filters for Flux and Circulation Fields
PARAVIEW_BUILD_PLUGIN_Moments:BOOL=ON

//Build Testing plugin
PARAVIEW_BUILD_PLUGIN_PacMan:BOOL=ON

//Build Point Sprites
PARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=ON

//Build Prism
PARAVIEW_BUILD_PLUGIN_Prism:BOOL=ON

//Build SLACTools
PARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON

//Build SciberQuest SciViz Toolkit
PARAVIEW_BUILD_PLUGIN_SQToolkit:BOOL=OFF

//Build SierraPlotTools
PARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=ON

//Build Streaming View
PARAVIEW_BUILD_PLUGIN_StreamingView:BOOL=ON

//Build SurfaceLIC
PARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=ON

//Build Plugin to read NCAR VDF files
PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=OFF

//Build pvblot
PARAVIEW_BUILD_PLUGIN_pvblot:BOOL=ON

//Build ParaView Qt Client. This requires Qt.
PARAVIEW_BUILD_QT_GUI:BOOL=OFF

//Path to a file.
PARAVIEW_DATA_ROOT:PATH=PARAVIEW_DATA_ROOT-NOTFOUND

//Disable VTK Testing
PARAVIEW_DISABLE_VTK_TESTING:BOOL=OFF

//Enable/Disable the CoProcessing library.
PARAVIEW_ENABLE_COPROCESSING:BOOL=OFF

//Build ParaView with Floating Point Exceptions turned on
PARAVIEW_ENABLE_FPE:BOOL=OFF

//Enable/Disable Python scripting support.
PARAVIEW_ENABLE_PYTHON:BOOL=ON

//Enable Python calculator and programmable filters.
PARAVIEW_ENABLE_PYTHON_FILTERS:BOOL=ON

//Path to a cmake file containing calls to build additional plugins
// external to ParaView.
PARAVIEW_EXTERNAL_PLUGINS_FILE:FILEPATH=

//';' separated paths to additional plugin directories to be included
// in build process.
PARAVIEW_EXTERNAL_PLUGIN_DIRS:STRING=

//Extra modules that ParaView will try to import. The modules have
// to provide ParaViewImport.cmake file.
PARAVIEW_EXTRA_EXTERNAL_MODULES:STRING=

//Install ParaView plugin development files.
PARAVIEW_INSTALL_DEVELOPMENT:BOOL=OFF

//Enable installation of third party libraries such as Qt and FFMPEG.
PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES:BOOL=ON

//Compile paraview for minimum image
PARAVIEW_MINIMAL_BUILD:BOOL=OFF

//Build Python Testing support if PARAVIEW_ENABLE_PYTHON is ON
PARAVIEW_TESTING_WITH_PYTHON:BOOL=ON

//Build ParaView with R support
PARAVIEW_USE_GNU_R:BOOL=OFF

//Use IceT multi display manager
PARAVIEW_USE_ICE_T:BOOL=ON

//Build ParaView with MPI support
PARAVIEW_USE_MPI:BOOL=ON

//Use MPI synchronous-send commands for communication
PARAVIEW_USE_MPI_SSEND:BOOL=OFF

//Use VisIt Bridge
PARAVIEW_USE_VISITBRIDGE:BOOL=OFF

//Does an external project define proj_list or should libproj4
// define it?
PROJ_LIST_EXTERNAL:BOOL=OFF

//Should libproj4 include projection code that relies on GSL?
PROJ_USE_GSL:BOOL=OFF

//Should libproj4 be built as a thread-friendly library?
PROJ_USE_PTHREADS:BOOL=OFF

//Disable compiler warnings
PROTOBUF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Value Computed by CMake
PVClientServerCore_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/ParaViewCore/ClientServerCore

//Value Computed by CMake
PVClientServerCore_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/ParaViewCore/ClientServerCore

//Value Computed by CMake
PVCommmandLineExecutables_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/CommandLineExecutables

//Value Computed by CMake
PVCommmandLineExecutables_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/CommandLineExecutables

//Value Computed by CMake
PVCommon_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/ParaViewCore/Common

//Value Computed by CMake
PVCommon_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/ParaViewCore/Common

//Value Computed by CMake
PVServerImplementation_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/ParaViewCore/ServerImplementation

//Value Computed by CMake
PVServerImplementation_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/ParaViewCore/ServerImplementation

//Value Computed by CMake
PVServerManager_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/ParaViewCore/ServerManager

//Value Computed by CMake
PVServerManager_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/ParaViewCore/ServerManager

//Value Computed by CMake
PVVTKExtensions_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/ParaViewCore/VTKExtensions

//Value Computed by CMake
PVVTKExtensions_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/ParaViewCore/VTKExtensions

//Command to run after a failed test to cleanup processes.  Example:
// "killall -9 rsh paraview"
PV_TEST_CLEAN_COMMAND:STRING=

//Node which serves as the client node, used to connect from the
// server side in reverse connection mode.
PV_TEST_CLIENT:STRING=localhost

//Command to run before a test begins. Multiple commands are separated
// by ';'.
PV_TEST_INIT_COMMAND:STRING=

//Add module MPIPython
PYTHON_ENABLE_MODULE_MPIPython:BOOL=ON

//Add module vtkChartsPython
PYTHON_ENABLE_MODULE_vtkChartsPython:BOOL=ON

//Add module vtkCommonPython
PYTHON_ENABLE_MODULE_vtkCommonPython:BOOL=ON

//Add module vtkFilteringPython
PYTHON_ENABLE_MODULE_vtkFilteringPython:BOOL=ON

//Add module vtkGenericFilteringPython
PYTHON_ENABLE_MODULE_vtkGenericFilteringPython:BOOL=ON

//Add module vtkGeovisPython
PYTHON_ENABLE_MODULE_vtkGeovisPython:BOOL=ON

//Add module vtkGraphicsPython
PYTHON_ENABLE_MODULE_vtkGraphicsPython:BOOL=ON

//Add module vtkHybridPython
PYTHON_ENABLE_MODULE_vtkHybridPython:BOOL=ON

//Add module vtkIOPython
PYTHON_ENABLE_MODULE_vtkIOPython:BOOL=ON

//Add module vtkImagingPython
PYTHON_ENABLE_MODULE_vtkImagingPython:BOOL=ON

//Add module vtkInfovisPython
PYTHON_ENABLE_MODULE_vtkInfovisPython:BOOL=ON

//Add module vtkPVClientServerCorePython
PYTHON_ENABLE_MODULE_vtkPVClientServerCorePython:BOOL=ON

//Add module vtkPVCommonPython
PYTHON_ENABLE_MODULE_vtkPVCommonPython:BOOL=ON

//Add module vtkPVServerImplementationPython
PYTHON_ENABLE_MODULE_vtkPVServerImplementationPython:BOOL=ON

//Add module vtkPVServerManagerPython
PYTHON_ENABLE_MODULE_vtkPVServerManagerPython:BOOL=ON

//Add module vtkPVVTKExtensionsPython
PYTHON_ENABLE_MODULE_vtkPVVTKExtensionsPython:BOOL=ON

//Add module vtkParallelPython
PYTHON_ENABLE_MODULE_vtkParallelPython:BOOL=ON

//Add module vtkRenderingPython
PYTHON_ENABLE_MODULE_vtkRenderingPython:BOOL=ON

//Add module vtkViewsPython
PYTHON_ENABLE_MODULE_vtkViewsPython:BOOL=ON

//Add module vtkVolumeRenderingPython
PYTHON_ENABLE_MODULE_vtkVolumeRenderingPython:BOOL=ON

//Add module vtkWidgetsPython
PYTHON_ENABLE_MODULE_vtkWidgetsPython:BOOL=ON

//Path to a program.
PYTHON_EXECUTABLE:FILEPATH=/usr/common/usg/python/2.7.1/bin/python

//Extra libraries to link when linking to python (such as "z" for
// zlib).  Separate multiple libraries with semicolons.
PYTHON_EXTRA_LIBS:STRING=

//Path to a file.
PYTHON_INCLUDE_DIR:PATH=/usr/common/usg/python/2.7.1/include/python2.7

//Path to a library.
PYTHON_LIBRARY:FILEPATH=/usr/common/usg/python/2.7.1/lib/libpython2.7.so.1.0

//Add module MPIPython shared
PYTHON_MODULE_MPIPython_BUILD_SHARED:BOOL=ON

//Add module vtkChartsPython shared
PYTHON_MODULE_vtkChartsPython_BUILD_SHARED:BOOL=ON

//Add module vtkCommonPython shared
PYTHON_MODULE_vtkCommonPython_BUILD_SHARED:BOOL=ON

//Add module vtkFilteringPython shared
PYTHON_MODULE_vtkFilteringPython_BUILD_SHARED:BOOL=ON

//Add module vtkGenericFilteringPython shared
PYTHON_MODULE_vtkGenericFilteringPython_BUILD_SHARED:BOOL=ON

//Add module vtkGeovisPython shared
PYTHON_MODULE_vtkGeovisPython_BUILD_SHARED:BOOL=ON

//Add module vtkGraphicsPython shared
PYTHON_MODULE_vtkGraphicsPython_BUILD_SHARED:BOOL=ON

//Add module vtkHybridPython shared
PYTHON_MODULE_vtkHybridPython_BUILD_SHARED:BOOL=ON

//Add module vtkIOPython shared
PYTHON_MODULE_vtkIOPython_BUILD_SHARED:BOOL=ON

//Add module vtkImagingPython shared
PYTHON_MODULE_vtkImagingPython_BUILD_SHARED:BOOL=ON

//Add module vtkInfovisPython shared
PYTHON_MODULE_vtkInfovisPython_BUILD_SHARED:BOOL=ON

//Add module vtkPVClientServerCorePython shared
PYTHON_MODULE_vtkPVClientServerCorePython_BUILD_SHARED:BOOL=ON

//Add module vtkPVCommonPython shared
PYTHON_MODULE_vtkPVCommonPython_BUILD_SHARED:BOOL=ON

//Add module vtkPVServerImplementationPython shared
PYTHON_MODULE_vtkPVServerImplementationPython_BUILD_SHARED:BOOL=ON

//Add module vtkPVServerManagerPython shared
PYTHON_MODULE_vtkPVServerManagerPython_BUILD_SHARED:BOOL=ON

//Add module vtkPVVTKExtensionsPython shared
PYTHON_MODULE_vtkPVVTKExtensionsPython_BUILD_SHARED:BOOL=ON

//Add module vtkParallelPython shared
PYTHON_MODULE_vtkParallelPython_BUILD_SHARED:BOOL=ON

//Add module vtkRenderingPython shared
PYTHON_MODULE_vtkRenderingPython_BUILD_SHARED:BOOL=ON

//Add module vtkViewsPython shared
PYTHON_MODULE_vtkViewsPython_BUILD_SHARED:BOOL=ON

//Add module vtkVolumeRenderingPython shared
PYTHON_MODULE_vtkVolumeRenderingPython_BUILD_SHARED:BOOL=ON

//Add module vtkWidgetsPython shared
PYTHON_MODULE_vtkWidgetsPython_BUILD_SHARED:BOOL=ON

//Utility library needed for vtkpython
PYTHON_UTIL_LIBRARY:FILEPATH=/usr/lib64/libutil.so

//Dependencies for the target
PacMan_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Value Computed by CMake
ParaViewCore_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/ParaViewCore

//Value Computed by CMake
ParaViewCore_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/ParaViewCore

//Value Computed by CMake
ParaView_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build

//Value Computed by CMake
ParaView_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1

//Value Computed by CMake
PointSpritePlugin_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Plugins/PointSprite

//Value Computed by CMake
PointSpritePlugin_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Plugins/PointSprite

//Dependencies for the target
PointSprite_Graphics_LIB_DEPENDS:STATIC=general;vtkGraphics;

//Dependencies for the target
PointSprite_Plugin_LIB_DEPENDS:STATIC=general;vtkPVServerManager;general;PointSprite_Rendering;general;PointSprite_Graphics;

//Dependencies for the target
PointSprite_Rendering_LIB_DEPENDS:STATIC=general;vtkHybrid;general;vtkRendering;general;vtkImaging;general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;

//Dependencies for the target
PrismServerPlugin_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//The qmake executable for the Qt installation to use
QT_QMAKE_EXECUTABLE:FILEPATH=QT_QMAKE_EXECUTABLE-NOTFOUND

//Path to scp command, used by CTest for submitting results to
// a Dart server
SCPCOMMAND:FILEPATH=/usr/bin/scp

//Name of the computer/site where compile is being run
SITE:STRING=hopper12

//Dependencies for the target
SLACTools_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Path to the SLURM sbatch executable
SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND

//Path to the SLURM srun executable
SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND

//Path to a program.
SVNCOMMAND:FILEPATH=/usr/common/usg/bin/svn

//Dependencies for the target
StreamingView_LIB_DEPENDS:STATIC=general;vtkPVServerManager;general;vtkStreamingCS;

//Location of Tcl library imported from VTK.  This may mean your
// project is depending on VTK to get this setting.  Consider using
// FindTCL.cmake.
TCL_LIBRARY:FILEPATH=

//Location of Tk library imported from VTK.  This may mean your
// project is depending on VTK to get this setting.  Consider using
// FindTCL.cmake.
TK_LIBRARY:FILEPATH=

//Build the 2007 Verdict User Manual
VERDICT_BUILD_DOC:BOOL=OFF

//Should tests of the VERDICT library be built?
VERDICT_ENABLE_TESTING:BOOL=OFF

//Mangle verdict names for inclusion in a larger library?
VERDICT_MANGLE:BOOL=ON

//VTK requires the verdict prefix to be vtk
VERDICT_MANGLE_PREFIX:STRING=vtk

//VTK requires doubles
VERDICT_USE_FLOAT:BOOL=OFF

//Path to a library.
VLI_LIBRARY_FOR_VP1000:FILEPATH=VLI_LIBRARY_FOR_VP1000-NOTFOUND

//Value Computed by CMake
VPIC_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/VPIC

//Dependencies for the target
VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;

//Value Computed by CMake
VPIC_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/VPIC

//Value Computed by CMake
VTKCS_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Utilities/VTKClientServer

//Value Computed by CMake
VTKCS_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Utilities/VTKClientServer

//Value Computed by CMake
VTKEXPAT_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkexpat

//Value Computed by CMake
VTKEXPAT_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkexpat

//Value Computed by CMake
VTKFREETYPE_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkfreetype

//Value Computed by CMake
VTKFREETYPE_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkfreetype

//Value Computed by CMake
VTKFTGL_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/ftgl

//Value Computed by CMake
VTKFTGL_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/ftgl

//Value Computed by CMake
VTKJPEG_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkjpeg

//Value Computed by CMake
VTKJPEG_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkjpeg

//Value Computed by CMake
VTKNETCDF_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtknetcdf

//Value Computed by CMake
VTKNETCDF_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtknetcdf

//Value Computed by CMake
VTKPNG_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkpng

//Value Computed by CMake
VTKPNG_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkpng

//Value Computed by CMake
VTKPythonWrapping_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Utilities/VTKPythonWrapping

//Value Computed by CMake
VTKPythonWrapping_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Utilities/VTKPythonWrapping

//Value Computed by CMake
VTKSQLite_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtksqlite

//Value Computed by CMake
VTKSQLite_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtksqlite

//Value Computed by CMake
VTKTIFF_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtktiff

//Value Computed by CMake
VTKTIFF_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtktiff

//Value Computed by CMake
VTKZLIB_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkzlib

//Value Computed by CMake
VTKZLIB_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkzlib

//Value Computed by CMake
VTK_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK

//Build forwarding executables for vtk, vtkpython, etc.
VTK_BUILD_FORWARDING_EXECUTABLES:BOOL=OFF

//Path to a file.
VTK_DATA_ROOT:PATH=VTK_DATA_ROOT-NOTFOUND

//Build leak checking support into VTK.
VTK_DEBUG_LEAKS:BOOL=OFF

//Add compiler flags to do stricter checking when building debug.
VTK_EXTRA_COMPILER_WARNINGS:BOOL=OFF

//Location of the OpenGL extensions header file (glext.h).
VTK_GLEXT_FILE:FILEPATH=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/ParseOGLExt/headers/glext.h

//Location of the GLX extensions header file (glxext.h).
VTK_GLXEXT_FILE:FILEPATH=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/ParseOGLExt/headers/glxext.h

//Ignore BTX and ETX in header files.
VTK_IGNORE_BTX:BOOL=ON

//Use fixup bundle to install vtk and vtkpython dependencies.
VTK_INSTALL_THIRD_PARTY_LIBRARIES:BOOL=OFF

//Path to a file.
VTK_LARGE_DATA_ROOT:PATH=VTK_LARGE_DATA_ROOT-NOTFOUND

//Remove all legacy code completely.
VTK_LEGACY_REMOVE:BOOL=OFF

//Silence all legacy code messages.
VTK_LEGACY_SILENT:BOOL=OFF

//; separated directories to search for materials/shaders
VTK_MATERIALS_DIRS:STRING=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/MaterialLibrary/Repository

//Max number of threads vktMultiThreader will allocate.
VTK_MAX_THREADS:STRING=64

//Path to a program.
VTK_MPIRUN_EXE:FILEPATH=VTK_MPIRUN_EXE-NOTFOUND

//Maximum number of processors available to run parallel applications.
// (see /global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/CMakeLists.txt
// for more info.)
VTK_MPI_MAX_NUMPROCS:STRING=2

//Flag used by mpi to specify the number of processes, the next
// option will be the number of processes. (see /global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/CMakeLists.txt
// for more info.)
VTK_MPI_NUMPROC_FLAG:STRING=-np

//These flags will come after all flags given to MPIRun.(see /global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/CMakeLists.txt
// for more info.)
VTK_MPI_POSTFLAGS:STRING=

//These flags will be directly before the executable that is being
// run by VTK_MPIRUN_EXE. (see /global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/CMakeLists.txt
// for more info.)
VTK_MPI_PREFLAGS:STRING=

//These flags will be directly before the number of processess
// flag (see /global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/CMakeLists.txt
// for more info.)
VTK_MPI_PRENUMPROC_FLAGS:STRING=

//Forced to ON since neither OPEN_gl_LIBRARY nor MangledMesa were
// found
VTK_OPENGL_HAS_OSMESA:BOOL=ON

//Value Computed by CMake
VTK_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK

//Locale for VTK C++ tests. Example fr_FR.utf8, empty string for
// env variable.
VTK_TESTING_LOCALE:STRING=

//VTK tests call vtkFloatingPointExceptions::Enable()
VTK_TESTING_USE_FPE:BOOL=ON

//VTK c++ tests will start with specified locale.
VTK_TESTING_USE_LOCALE:BOOL=OFF

//Build VTK with 64 bit ids
VTK_USE_64BIT_IDS:BOOL=ON

//Use Boost libraries for graph algorithms - www.boost.org.
VTK_USE_BOOST:BOOL=OFF

//Build pixel and vertex shader support for Cg.
VTK_USE_CG_SHADERS:BOOL=OFF

//Build VTK chart support (OpenGL based)
VTK_USE_CHARTS:BOOL=ON

//Turn this option off and tests and warning/error macros will
// not popup windows
VTK_USE_DISPLAY:BOOL=ON

//If the FFMPEG library is available, should VTK use it for saving
// .avi animation files?
VTK_USE_FFMPEG_ENCODER:BOOL=OFF

//Use GCC visibility support if available.
VTK_USE_GCC_VISIBILITY:BOOL=ON

//Build the vtkGeovis kit.  Needed for performing geographic visualization.
VTK_USE_GEOVIS:BOOL=ON

//Build VTK with gl2ps support.
VTK_USE_GL2PS:BOOL=OFF

//Build pixel and vertex shader support for GLSL.
VTK_USE_GLSL_SHADERS:BOOL=ON

//Build VTK with GUI Support
VTK_USE_GUISUPPORT:BOOL=1

//Build the vtkInfovis kit.  Needed for performing information
// visualization.
VTK_USE_INFOVIS:BOOL=ON

//Use mangled Mesa with OpenGL.
VTK_USE_MANGLED_MESA:BOOL=OFF

//Use Matlab Engine and Matlab Mex files.  Requires valid Matlab
// installation.
VTK_USE_MATLAB_MEX:BOOL=OFF

//Build metaio
VTK_USE_METAIO:BOOL=ON

//Enable use of the patented mpeg2 library. You are solely responsible
// for any legal issues associated with using patented code in
// your software.
VTK_USE_MPEG2_ENCODER:BOOL=OFF

//Build the MySQL driver for vtkSQLDatabase.
VTK_USE_MYSQL:BOOL=OFF

//Use NVIDIAs X server extension NVCONTROL.
VTK_USE_NVCONTROL:BOOL=OFF

//Add support for arbitrary-dimension sparse and dense arrays.
VTK_USE_N_WAY_ARRAYS:BOOL=ON

//Build the ODBC database interface
VTK_USE_ODBC:BOOL=OFF

//Use off screen calls by default.
VTK_USE_OFFSCREEN:BOOL=ON

//Build experimental Ogg/Theora support
VTK_USE_OGGTHEORA_ENCODER:BOOL=OFF

//Build the PostgreSQL driver for vtkSQLDatabase.
VTK_USE_POSTGRES:BOOL=OFF

//Build Qt support
VTK_USE_QT:BOOL=OFF

//Build Qt based charts - DEPRECATED
VTK_USE_QTCHARTS:BOOL=OFF

//Use the system's expat library.
VTK_USE_SYSTEM_EXPAT:BOOL=OFF

//Use the system's freetype library.
VTK_USE_SYSTEM_FREETYPE:BOOL=OFF

//Use the system's hdf5 library.
VTK_USE_SYSTEM_HDF5:BOOL=OFF

//Use the system's jpeg library.
VTK_USE_SYSTEM_JPEG:BOOL=OFF

//Use the system's proj4 library.
VTK_USE_SYSTEM_LIBPROJ4:BOOL=OFF

//Use the system's libxml2 library.
VTK_USE_SYSTEM_LIBXML2:BOOL=OFF

//Use the system's png library.
VTK_USE_SYSTEM_PNG:BOOL=OFF

//Use the system's tiff library.
VTK_USE_SYSTEM_TIFF:BOOL=OFF

//Use the system's zlib library.
VTK_USE_SYSTEM_ZLIB:BOOL=OFF

//Use 3Dconnexion device
VTK_USE_TDX:BOOL=OFF

//Build the vtkTextAnalysis kit.  Needed for performing text analysis.
VTK_USE_TEXT_ANALYSIS:BOOL=OFF

//Build VTK with Tk support
VTK_USE_TK:BOOL=OFF

//Build the vtkViews kit.  Needed for creating packaged and linked
// views.
VTK_USE_VIEWS:BOOL=ON

//Enable support for VolumePro 1000.
VTK_USE_VOLUMEPRO_1000:BOOL=OFF

//Build classes for the X11 window system.
VTK_USE_X:BOOL=OFF

//Location of the WGL extensions header file (wglext.h).
VTK_WGLEXT_FILE:FILEPATH=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/ParseOGLExt/headers/wglext.h

//Path to a file.
VTK_WRAP_HINTS:FILEPATH=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Wrapping/hints

//Wrap VTK classes into the Java language.
VTK_WRAP_JAVA:BOOL=OFF

//Make python wrapped classes available to SIP/PyQt.
VTK_WRAP_PYTHON_SIP:BOOL=OFF

//Path to a file.
X11_ICE_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_ICE_LIB:FILEPATH=/usr/lib64/libICE.so

//Path to a file.
X11_SM_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_SM_LIB:FILEPATH=/usr/lib64/libSM.so

//Path to a file.
X11_X11_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_X11_LIB:FILEPATH=/usr/lib64/libX11.so

//Path to a file.
X11_XRes_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_XRes_LIB:FILEPATH=/usr/lib64/libXRes.so

//Path to a file.
X11_XShm_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_XSync_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_XTest_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_XTest_LIB:FILEPATH=/usr/lib64/libXtst.so

//Path to a file.
X11_Xaccessrules_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xaccessstr_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xau_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xau_LIB:FILEPATH=/usr/lib64/libXau.so

//Path to a file.
X11_Xcomposite_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xcomposite_LIB:FILEPATH=/usr/lib64/libXcomposite.so

//Path to a file.
X11_Xcursor_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xcursor_LIB:FILEPATH=/usr/lib64/libXcursor.so

//Path to a file.
X11_Xdamage_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xdamage_LIB:FILEPATH=/usr/lib64/libXdamage.so

//Path to a file.
X11_Xdmcp_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xdmcp_LIB:FILEPATH=/usr/lib64/libXdmcp.so

//Path to a library.
X11_Xext_LIB:FILEPATH=/usr/lib64/libXext.so

//Path to a file.
X11_Xfixes_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xfixes_LIB:FILEPATH=/usr/lib64/libXfixes.so

//Path to a file.
X11_Xft_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xft_LIB:FILEPATH=/usr/lib64/libXft.so

//Path to a file.
X11_Xi_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xi_LIB:FILEPATH=/usr/lib64/libXi.so

//Path to a file.
X11_Xinerama_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xinerama_LIB:FILEPATH=/usr/lib64/libXinerama.so

//Path to a file.
X11_Xinput_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xinput_LIB:FILEPATH=/usr/lib64/libXi.so

//Path to a file.
X11_Xkb_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xkbfile_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xkbfile_LIB:FILEPATH=/usr/lib64/libxkbfile.so

//Path to a file.
X11_Xkblib_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xlib_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xmu_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xmu_LIB:FILEPATH=/usr/lib64/libXmu.so

//Path to a file.
X11_Xpm_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xpm_LIB:FILEPATH=/usr/lib64/libXpm.so

//Path to a file.
X11_Xrandr_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xrandr_LIB:FILEPATH=/usr/lib64/libXrandr.so

//Path to a file.
X11_Xrender_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xrender_LIB:FILEPATH=/usr/lib64/libXrender.so

//Path to a file.
X11_Xscreensaver_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xscreensaver_LIB:FILEPATH=/usr/lib64/libXss.so

//Path to a file.
X11_Xshape_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xt_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xt_LIB:FILEPATH=/usr/lib64/libXt.so

//Path to a file.
X11_Xutil_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_Xv_INCLUDE_PATH:PATH=/usr/include

//Path to a library.
X11_Xv_LIB:FILEPATH=/usr/lib64/libXv.so

//Path to a library.
X11_Xxf86misc_LIB:FILEPATH=/usr/lib64/libXxf86misc.so

//Path to a library.
X11_Xxf86vm_LIB:FILEPATH=/usr/lib64/libXxf86vm.so

//Path to a file.
X11_dpms_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_xf86misc_INCLUDE_PATH:PATH=/usr/include

//Path to a file.
X11_xf86vmode_INCLUDE_PATH:PATH=/usr/include

//Build Xdmf Utilities
XDMF_BUILD_UTILS:BOOL=OFF

//XDMF has Network Distributed Global Memory (NDGM)
XDMF_HAS_NDGM:BOOL=OFF

//Path to a file.
XDMF_HAVE_FCNTL:PATH=/usr/include

//Path to a file.
XDMF_HAVE_MMAN:PATH=/usr/include/sys

//Path to a file.
XDMF_HAVE_NETINET:PATH=/usr/include/netinet

//Use bzip2
XDMF_USE_BZIP2:BOOL=OFF

//Build GZip Compression
XDMF_USE_GZIP:BOOL=OFF

//Build Support for MySQL DataItems
XDMF_USE_MYSQL:BOOL=OFF

//Build a C# wrapping interface
XDMF_WRAP_CSHARP:BOOL=OFF

//Value Computed by CMake
Xdmf_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Utilities/Xdmf2

//Dependencies for the target
Xdmf_LIB_DEPENDS:STATIC=general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;vtkhdf5;general;vtklibxml2;

//Value Computed by CMake
Xdmf_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Utilities/Xdmf2

//Path to a file.
ZLIB_INCLUDE_DIR:PATH=/usr/include

//Path to a library.
ZLIB_LIBRARY:FILEPATH=/usr/lib64/libz.so

//Value Computed by CMake
alglib_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkalglib

//Value Computed by CMake
alglib_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkalglib

//Value Computed by CMake
libproj4_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtklibproj4

//Value Computed by CMake
libproj4_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtklibproj4

//Value Computed by CMake
mpi4py_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Utilities/mpi4py

//Value Computed by CMake
mpi4py_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Utilities/mpi4py

//Dependencies for the target
mpistubs_LIB_DEPENDS:STATIC=general;vtksys;

//Dependencies for the target
protobuf-lite_LIB_DEPENDS:STATIC=general;-lpthread;

//Value Computed by CMake
protobuf_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Utilities/protobuf

//Enable and build protobuf tests
protobuf_ENABLE_TESTING:BOOL=OFF

//Dependencies for the target
protobuf_LIB_DEPENDS:STATIC=general;-lpthread;general;/usr/lib64/libz.so;

//Value Computed by CMake
protobuf_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Utilities/protobuf

//Dependencies for the target
protoc_LIB_DEPENDS:STATIC=general;-lpthread;general;protobuf;

//Dependencies for the target
pvblot_LIB_DEPENDS:STATIC=general;vtkPVServerManager;

//Value Computed by CMake
verdict_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/verdict

//Value Computed by CMake
verdict_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/verdict

//Dependencies for the target
vtkChartsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCharts;general;vtkViewsCS;general;vtkRenderingCS;

//Dependencies for the target
vtkChartsPythonD_LIB_DEPENDS:STATIC=general;vtkCharts;general;vtkPythonCore;general;vtkViewsPythonD;

//Dependencies for the target
vtkChartsPython_LIB_DEPENDS:STATIC=general;vtkChartsPythonD;

//Dependencies for the target
vtkCharts_LIB_DEPENDS:STATIC=general;vtkViews;general;vtkftgl;

//Dependencies for the target
vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommon;

//Dependencies for the target
vtkCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommon;

//Dependencies for the target
vtkCommonPythonD_LIB_DEPENDS:STATIC=general;vtkCommon;general;vtkPythonCore;

//Dependencies for the target
vtkCommonPython_LIB_DEPENDS:STATIC=general;vtkCommonPythonD;

//Dependencies for the target
vtkCommon_LIB_DEPENDS:STATIC=general;vtksys;general;-lm;general;-lpthread;general;dl;

//Dependencies for target
vtkDICOMParser_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtkExodus2_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkexodus2

//Value Computed by CMake
vtkExodus2_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkexodus2

//Dependencies for the target
vtkFilteringCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltering;general;vtkCommonCS;

//Dependencies for the target
vtkFilteringPythonD_LIB_DEPENDS:STATIC=general;vtkFiltering;general;vtkPythonCore;general;vtkCommonPythonD;

//Dependencies for the target
vtkFilteringPython_LIB_DEPENDS:STATIC=general;vtkFilteringPythonD;

//Dependencies for the target
vtkFiltering_LIB_DEPENDS:STATIC=general;vtkCommon;

//Dependencies for the target
vtkGenericFilteringCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkGenericFiltering;general;vtkFilteringCS;

//Dependencies for the target
vtkGenericFilteringPythonD_LIB_DEPENDS:STATIC=general;vtkGenericFiltering;general;vtkPythonCore;general;vtkFilteringPythonD;general;vtkGraphicsPythonD;

//Dependencies for the target
vtkGenericFilteringPython_LIB_DEPENDS:STATIC=general;vtkGenericFilteringPythonD;

//Dependencies for the target
vtkGenericFiltering_LIB_DEPENDS:STATIC=general;vtkFiltering;general;vtkGraphics;

//Dependencies for the target
vtkGeovisPythonD_LIB_DEPENDS:STATIC=general;vtkGeovis;general;vtkPythonCore;general;vtkWidgetsPythonD;general;vtkViewsPythonD;

//Dependencies for the target
vtkGeovisPython_LIB_DEPENDS:STATIC=general;vtkGeovisPythonD;

//Dependencies for the target
vtkGeovis_LIB_DEPENDS:STATIC=general;vtkWidgets;general;vtkViews;general;vtkproj4;

//Dependencies for the target
vtkGraphicsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkGraphics;general;vtkFilteringCS;general;vtkIOCS;

//Dependencies for the target
vtkGraphicsPythonD_LIB_DEPENDS:STATIC=general;vtkGraphics;general;vtkPythonCore;general;vtkFilteringPythonD;

//Dependencies for the target
vtkGraphicsPython_LIB_DEPENDS:STATIC=general;vtkGraphicsPythonD;

//Dependencies for the target
vtkGraphics_LIB_DEPENDS:STATIC=general;vtkFiltering;general;vtkverdict;

//Dependencies for the target
vtkHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkHybrid;general;vtkRenderingCS;general;vtkParallelCS;

//Dependencies for the target
vtkHybridPythonD_LIB_DEPENDS:STATIC=general;vtkHybrid;general;vtkPythonCore;general;vtkRenderingPythonD;general;vtkIOPythonD;

//Dependencies for the target
vtkHybridPython_LIB_DEPENDS:STATIC=general;vtkHybridPythonD;

//Dependencies for the target
vtkHybrid_LIB_DEPENDS:STATIC=general;vtkRendering;general;vtkIO;general;vtkParallel;general;vtkexoIIc;general;vtkftgl;

//Dependencies for the target
vtkIOCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIO;general;vtkFilteringCS;

//Dependencies for the target
vtkIOPythonD_LIB_DEPENDS:STATIC=general;vtkIO;general;vtkPythonCore;general;vtkFilteringPythonD;

//Dependencies for the target
vtkIOPython_LIB_DEPENDS:STATIC=general;vtkIOPythonD;

//Dependencies for the target
vtkIO_LIB_DEPENDS:STATIC=general;vtkFiltering;general;vtkDICOMParser;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtkmetaio;general;vtksqlite;general;vtkpng;general;vtkzlib;general;vtkjpeg;general;vtktiff;general;vtkexpat;general;vtksys;

//Dependencies for the target
vtkImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImaging;general;vtkFilteringCS;

//Dependencies for the target
vtkImagingPythonD_LIB_DEPENDS:STATIC=general;vtkImaging;general;vtkPythonCore;general;vtkFilteringPythonD;

//Dependencies for the target
vtkImagingPython_LIB_DEPENDS:STATIC=general;vtkImagingPythonD;

//Dependencies for the target
vtkImaging_LIB_DEPENDS:STATIC=general;vtkFiltering;

//Dependencies for the target
vtkInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInfovis;general;vtkFilteringCS;general;vtkRenderingCS;general;vtkParallelCS;

//Dependencies for the target
vtkInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkInfovis;general;vtkPythonCore;general;vtkWidgetsPythonD;

//Dependencies for the target
vtkInfovisPython_LIB_DEPENDS:STATIC=general;vtkInfovisPythonD;

//Dependencies for the target
vtkInfovis_LIB_DEPENDS:STATIC=general;vtkWidgets;general;vtkParallel;general;vtklibxml2;general;vtkalglib;

//Dependencies for target
vtkNetCDF_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkNetCDF_cxx_LIB_DEPENDS:STATIC=general;vtkNetCDF;

//Dependencies for the target
vtkPVClientServerCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCore;general;vtkPVVTKExtensionsCS;

//Dependencies for the target
vtkPVClientServerCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCore;general;vtkPythonCore;general;vtkViewsPythonD;general;vtkPVVTKExtensionsPythonD;

//Dependencies for the target
vtkPVClientServerCorePython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCorePythonD;

//Dependencies for the target
vtkPVClientServerCore_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensions;general;vtkPVVTKExtensionsCS;general;IceTCore;general;IceTMPI;general;IceTGL;general;/usr/common/usg/python/2.7.1/lib/libpython2.7.so.1.0;general;vtkPVPythonInterpretor;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;

//Dependencies for the target
vtkPVCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCommon;general;vtkIOCS;

//Dependencies for the target
vtkPVCommonPythonD_LIB_DEPENDS:STATIC=general;vtkPVCommon;general;vtkPythonCore;general;vtkCommonPythonD;general;vtkIOPythonD;general;vtkPVCommon;

//Dependencies for the target
vtkPVCommonPython_LIB_DEPENDS:STATIC=general;vtkPVCommonPythonD;

//Dependencies for the target
vtkPVCommon_LIB_DEPENDS:STATIC=general;vtkIOCS;general;vtksys;general;vtkClientServer;

//Dependencies for the target
vtkPVPythonInterpretor_LIB_DEPENDS:STATIC=general;vtkCommon;general;/usr/common/usg/python/2.7.1/lib/libpython2.7.so.1.0;general;/usr/lib64/libutil.so;

//Dependencies for the target
vtkPVPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerPythonD;general;vtkCommon;general;vtkFiltering;general;vtkIO;general;vtkGraphics;general;vtkImaging;general;vtkPVPythonInterpretor;general;/usr/common/usg/python/2.7.1/lib/libpython2.7.so.1.0;general;/usr/lib64/libutil.so;

//Dependencies for the target
vtkPVServerImplementationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementation;general;vtkPVClientServerCoreCS;

//Dependencies for the target
vtkPVServerImplementationPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerImplementation;general;vtkPythonCore;general;vtkPVClientServerCorePythonD;

//Dependencies for the target
vtkPVServerImplementationPython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationPythonD;

//Dependencies for the target
vtkPVServerImplementation_LIB_DEPENDS:STATIC=general;vtkPVClientServerCore;general;vtkPVClientServerCoreCS;general;protobuf;

//Dependencies for the target
vtkPVServerManagerPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManager;general;vtkPythonCore;general;vtkPVServerImplementationPythonD;

//Dependencies for the target
vtkPVServerManagerPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerPythonD;

//Dependencies for the target
vtkPVServerManager_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCS;general;vtkPVServerImplementation;

//Dependencies for the target
vtkPVVTKExtensionsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensions;general;vtkPVCommonCS;general;vtkParallelCS;general;vtkHybridCS;general;vtkRenderingCS;general;vtkVolumeRenderingCS;general;vtkWidgetsCS;

//Dependencies for the target
vtkPVVTKExtensionsPythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensions;general;vtkPythonCore;general;vtkPVCommonPythonD;general;vtkHybridPythonD;general;vtkWidgetsPythonD;general;vtkParallelPythonD;

//Dependencies for the target
vtkPVVTKExtensionsPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsPythonD;

//Dependencies for the target
vtkPVVTKExtensions_LIB_DEPENDS:STATIC=general;vtkPVCommon;general;vtkPVCommonCS;general;vtkXdmfCS;general;vtkHybridCS;general;vtkParallelCS;general;vtkVolumeRenderingCS;general;vtkWidgetsCS;general;vtkViews;general;vtkViewsCS;general;vtkCharts;general;vtkChartsCS;general;KWCommon;general;vtkNetCDF;general;vtksys;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkhdf5;

//Dependencies for the target
vtkParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallel;general;vtkRenderingCS;

//Dependencies for the target
vtkParallelPythonD_LIB_DEPENDS:STATIC=general;vtkParallel;general;vtkPythonCore;general;vtkRenderingPythonD;general;vtkIOPythonD;

//Dependencies for the target
vtkParallelPython_LIB_DEPENDS:STATIC=general;vtkParallelPythonD;

//Dependencies for the target
vtkParallel_LIB_DEPENDS:STATIC=general;vtkRendering;general;vtkIO;general;VPIC;general;Cosmo;general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;general;vtkexoIIc;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;general;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;general;/usr/lib64/librt.so;general;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;general;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;general;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;general;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;general;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;general;/usr/lib/alps/libalpslli.so;general;/usr/lib/alps/libalpsutil.so;general;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;general;/usr/lib64/libpthread.so;

//Dependencies for the target
vtkPythonCore_LIB_DEPENDS:STATIC=general;vtkCommon;

//Dependencies for the target
vtkRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRendering;general;vtkGenericFilteringCS;general;vtkGraphicsCS;general;vtkImagingCS;general;vtkIOCS;

//Dependencies for the target
vtkRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkRendering;general;vtkPythonCore;general;vtkGraphicsPythonD;general;vtkImagingPythonD;

//Dependencies for the target
vtkRenderingPython_LIB_DEPENDS:STATIC=general;vtkRenderingPythonD;

//Dependencies for the target
vtkRendering_LIB_DEPENDS:STATIC=general;vtkGraphics;general;vtkImaging;general;vtkIO;general;vtkftgl;general;vtkfreetype;general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;

//Dependencies for the target
vtkStreamingCS_LIB_DEPENDS:STATIC=general;vtkStreaming;general;vtkClientServer;general;vtkPVServerManager;

//Value Computed by CMake
vtkStreaming_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/Plugins/StreamingView/VTK

//Dependencies for the target
vtkStreaming_LIB_DEPENDS:STATIC=general;vtkRendering;general;vtkGraphics;general;vtkFiltering;general;vtkCommon;general;vtkIO;general;vtkImaging;general;vtkNetCDF;

//Value Computed by CMake
vtkStreaming_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Plugins/StreamingView/VTK

//Dependencies for the target
vtkViewsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViews;general;vtkInfovisCS;general;vtkFilteringCS;

//Dependencies for the target
vtkViewsPythonD_LIB_DEPENDS:STATIC=general;vtkViews;general;vtkPythonCore;general;vtkInfovisPythonD;

//Dependencies for the target
vtkViewsPython_LIB_DEPENDS:STATIC=general;vtkViewsPythonD;

//Dependencies for the target
vtkViews_LIB_DEPENDS:STATIC=general;vtkInfovis;

//Dependencies for the target
vtkVolumeRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkVolumeRendering;general;vtkRenderingCS;

//Dependencies for the target
vtkVolumeRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkVolumeRendering;general;vtkPythonCore;general;vtkRenderingPythonD;general;vtkIOPythonD;

//Dependencies for the target
vtkVolumeRenderingPython_LIB_DEPENDS:STATIC=general;vtkVolumeRenderingPythonD;

//Dependencies for the target
vtkVolumeRendering_LIB_DEPENDS:STATIC=general;vtkRendering;general;vtkIO;general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;

//Dependencies for the target
vtkWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWidgets;general;vtkRenderingCS;general;vtkHybridCS;

//Dependencies for the target
vtkWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkWidgets;general;vtkPythonCore;general;vtkRenderingPythonD;general;vtkHybridPythonD;

//Dependencies for the target
vtkWidgetsPython_LIB_DEPENDS:STATIC=general;vtkWidgetsPythonD;

//Dependencies for the target
vtkWidgets_LIB_DEPENDS:STATIC=general;vtkRendering;general;vtkHybrid;general;vtkVolumeRendering;general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;

//Dependencies for the target
vtkXdmfCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkXdmf;general;vtkRenderingCS;

//Dependencies for the target
vtkXdmfPython_LIB_DEPENDS:STATIC=general;vtkIOPythonD;general;vtkRenderingPythonD;general;Xdmf;

//Dependencies for the target
vtkXdmf_LIB_DEPENDS:STATIC=general;vtkIO;general;Xdmf;general;vtkRendering;

//Dependencies for target
vtkalglib_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkexoIIc_LIB_DEPENDS:STATIC=general;vtkNetCDF;

//Dependencies for target
vtkexpat_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkfreetype_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkftgl_LIB_DEPENDS:STATIC=general;/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so;general;vtkfreetype;

//Dependencies for the target
vtkhdf5_LIB_DEPENDS:STATIC=general;m;general;vtkzlib;

//Dependencies for target
vtkjpeg_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtklibxml2_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtklibxml2

//Dependencies for the target
vtklibxml2_LIB_DEPENDS:STATIC=general;vtkzlib;general;dl;general;-lpthread;general;dl;general;m;

//Value Computed by CMake
vtklibxml2_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtklibxml2

//Value Computed by CMake
vtkmetaio_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/vtkmetaio

//Dependencies for the target
vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib;

//Value Computed by CMake
vtkmetaio_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/vtkmetaio

//Dependencies for the target
vtkpng_LIB_DEPENDS:STATIC=general;vtkzlib;general;-lm;

//Dependencies for the target
vtkproj4_LIB_DEPENDS:STATIC=general;m;

//Dependencies for the target
vtksqlite_LIB_DEPENDS:STATIC=general;-lpthread;

//Value Computed by CMake
vtksys_BINARY_DIR:STATIC=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/kwsys

//Dependencies for the target
vtksys_LIB_DEPENDS:STATIC=general;dl;

//Value Computed by CMake
vtksys_SOURCE_DIR:STATIC=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/Utilities/kwsys

//Dependencies for the target
vtktiff_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkjpeg;general;-lm;

//Dependencies for target
vtkverdict_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkzlib_LIB_DEPENDS:STATIC=


########################
# INTERNAL cache entries
########################

ALGLIB_SHARED_LIB:INTERNAL=ON
//Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN
ARCH_TO_BUILD:INTERNAL=Linux
//ADVANCED property for variable: BUILD_DOCUMENTATION
BUILD_DOCUMENTATION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: BUILD_EXAMPLES
BUILD_EXAMPLES-ADVANCED:INTERNAL=1
//MODIFIED property for variable: BUILD_SHARED_LIBS
BUILD_SHARED_LIBS-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: BUILD_TESTING
BUILD_TESTING-ADVANCED:INTERNAL=1
//MODIFIED property for variable: BUILD_TESTING
BUILD_TESTING-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: BZRCOMMAND
BZRCOMMAND-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_ANSI_FOR_SCOPE:INTERNAL=TRUE
//Have include iostream
CMAKE_ANSI_STREAM_HEADERS:INTERNAL=1
//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_BACKWARDS_COMPATIBILITY
CMAKE_BACKWARDS_COMPATIBILITY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_BUILD_TOOL
CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=1
//What is the target build tool cmake is generating for.
CMAKE_BUILD_TOOL:INTERNAL=/usr/bin/gmake
//MODIFIED property for variable: CMAKE_BUILD_TYPE
CMAKE_BUILD_TYPE-MODIFIED:INTERNAL=ON
//STRINGS property for variable: CMAKE_BUILD_TYPE
CMAKE_BUILD_TYPE-STRINGS:INTERNAL=Debug;Release;MinSizeRel;RelWithDebInfo
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=2
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=8
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=10
//ADVANCED property for variable: CMAKE_COLOR_MAKEFILE
CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=/global/common/hopper2/usg/cmake/2.8.10.1/bin/cmake
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=/global/common/hopper2/usg/cmake/2.8.10.1/bin/cpack
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=/global/common/hopper2/usg/cmake/2.8.10.1/bin/ctest
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=/global/common/hopper2/usg/cmake/2.8.10.1/bin/ccmake
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=ELF
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Unix Makefiles
//Result of TRY_COMPILE
CMAKE_HAS_ANSI_STRING_STREAM:INTERNAL=TRUE
//Is X11 around.
CMAKE_HAS_X:INTERNAL=1
//Have function connect
CMAKE_HAVE_CONNECT:INTERNAL=1
//Have function gethostbyname
CMAKE_HAVE_GETHOSTBYNAME:INTERNAL=1
//Have symbol pthread_create
CMAKE_HAVE_LIBC_CREATE:INTERNAL=
//Have include limits.h
CMAKE_HAVE_LIMITS_H:INTERNAL=1
//Have library pthreads
CMAKE_HAVE_PTHREADS_CREATE:INTERNAL=
//Have library pthread
CMAKE_HAVE_PTHREAD_CREATE:INTERNAL=1
//Have include pthread.h
CMAKE_HAVE_PTHREAD_H:INTERNAL=1
//Have function remove
CMAKE_HAVE_REMOVE:INTERNAL=1
//Have function shmat
CMAKE_HAVE_SHMAT:INTERNAL=1
//Have include sys/types.h;sys/prctl.h
CMAKE_HAVE_SYS_PRCTL_H:INTERNAL=1
//Have include unistd.h
CMAKE_HAVE_UNISTD_H:INTERNAL=1
//Start directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1
//ADVANCED property for variable: CMAKE_HP_PTHREADS
CMAKE_HP_PTHREADS-ADVANCED:INTERNAL=1
//Install .so files without execute permission.
CMAKE_INSTALL_SO_NO_EXE:INTERNAL=0
//Have library ICE
CMAKE_LIB_ICE_HAS_ICECONNECTIONNUMBER:INTERNAL=1
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_NM
CMAKE_NM-ADVANCED:INTERNAL=1
//Does the compiler support ansi for scope.
CMAKE_NO_ANSI_FOR_SCOPE:INTERNAL=0
//ADVANCED property for variable: CMAKE_NO_ANSI_STREAM_HEADERS
CMAKE_NO_ANSI_STREAM_HEADERS-ADVANCED:INTERNAL=1
//Does the compiler support headers like iostream.
CMAKE_NO_ANSI_STREAM_HEADERS:INTERNAL=0
//Does the compiler support sstream
CMAKE_NO_ANSI_STRING_STREAM:INTERNAL=0
//Does the compiler support std::.
CMAKE_NO_STD_NAMESPACE:INTERNAL=0
//number of local generators
CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=113
//ADVANCED property for variable: CMAKE_OBJCOPY
CMAKE_OBJCOPY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_OBJDUMP
CMAKE_OBJDUMP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RANLIB
CMAKE_RANLIB-ADVANCED:INTERNAL=1
//Test Support for 64 bit file systems
CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=/global/common/hopper2/usg/cmake/2.8.10.1/share/cmake-2.8
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(char)
CMAKE_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
CMAKE_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
CMAKE_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
CMAKE_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
CMAKE_SIZEOF_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
CMAKE_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(unsigned short)
CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(void*)
CMAKE_SIZEOF_VOID_P:INTERNAL=8
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_STD_NAMESPACE:INTERNAL=TRUE
//ADVANCED property for variable: CMAKE_STRIP
CMAKE_STRIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_THREAD_LIBS
CMAKE_THREAD_LIBS-ADVANCED:INTERNAL=1
//uname command
CMAKE_UNAME:INTERNAL=/bin/uname
//ADVANCED property for variable: CMAKE_USE_PTHREADS
CMAKE_USE_PTHREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS
CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_USE_SPROC
CMAKE_USE_SPROC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_USE_WIN32_THREADS
CMAKE_USE_WIN32_THREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Result of TEST_BIG_ENDIAN
CMAKE_WORDS_BIGENDIAN:INTERNAL=0
//ADVANCED property for variable: CMAKE_X_CFLAGS
CMAKE_X_CFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_X_LIBS
CMAKE_X_LIBS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COMPRESSIONCOMMAND
COMPRESSIONCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COVERAGE_COMMAND
COVERAGE_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COVERAGE_EXTRA_FLAGS
COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_DEB
CPACK_BINARY_DEB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_NSIS
CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_RPM
CPACK_BINARY_RPM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_STGZ
CPACK_BINARY_STGZ-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_TBZ2
CPACK_BINARY_TBZ2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_TGZ
CPACK_BINARY_TGZ-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_TZ
CPACK_BINARY_TZ-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_TBZ2
CPACK_SOURCE_TBZ2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_TGZ
CPACK_SOURCE_TGZ-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_TZ
CPACK_SOURCE_TZ-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_ZIP
CPACK_SOURCE_ZIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT
CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY
CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVSCOMMAND
CVSCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVS_UPDATE_OPTIONS
CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CXX_HAVE_OFFSETOF:INTERNAL=TRUE
//ADVANCED property for variable: DART_BUILD_ERROR_REPORT_LIMIT
DART_BUILD_ERROR_REPORT_LIMIT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_BUILD_WARNING_REPORT_LIMIT
DART_BUILD_WARNING_REPORT_LIMIT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_ROOT
DART_ROOT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_TESTING_TIMEOUT
DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_VERBOSE_BUILD
DART_VERBOSE_BUILD-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DELIVER_CONTINUOUS_EMAIL
DELIVER_CONTINUOUS_EMAIL-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
DEV_T_IS_SCALAR:INTERNAL=FALSE
//ADVANCED property for variable: EXECUTABLE_OUTPUT_PATH
EXECUTABLE_OUTPUT_PATH-ADVANCED:INTERNAL=1
//Single output directory for building all executables.
EXECUTABLE_OUTPUT_PATH:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/bin
//Have include malloc.h
EX_HAVE_MALLOC_H:INTERNAL=1
//Details about finding Git
FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[/usr/common/usg/bin/git][v1.7.7.4()]
//Details about finding MPI_C
FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;/usr/lib64/librt.so;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;/usr/lib/alps/libalpslli.so;/usr/lib/alps/libalpsutil.so;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;/usr/lib64/libpthread.so][/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/include][v()]
//Details about finding MPI_CXX
FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpich_gnu_47.so;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpichcxx_gnu_47.so;/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/lib/libmpl.so;/usr/lib64/librt.so;/opt/cray/mpt/5.5.2/gni/sma/lib64/libsma.so;/opt/cray/xpmem/0.1-2.0400.31280.3.1.gem/lib64/libxpmem.so;/opt/cray/dmapp/3.2.1-1.0400.4255.2.159.gem/lib64/libdmapp.so;/opt/cray/ugni/2.3-1.0400.4374.4.88.gem/lib64/libugni.so;/opt/cray/pmi/3.0.1-1.0000.9101.2.26.gem/lib64/libpmi.so;/usr/lib/alps/libalpslli.so;/usr/lib/alps/libalpsutil.so;/opt/cray/udreg/2.3.1-1.0400.4264.3.1.gem/lib64/libudreg.so;/usr/lib64/libpthread.so][/opt/cray/mpt/5.5.2/gni/mpich2-gnu/47/include][v()]
//Details about finding OSMesa
FIND_PACKAGE_MESSAGE_DETAILS_OSMesa:INTERNAL=[/usr/common/graphics/ParaView/Mesa-7.10.1/lib/libOSMesa32.so][/usr/common/graphics/ParaView/Mesa-7.10.1/include][v()]
//Details about finding OpenGL
FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[/usr/lib64/libGL.so][v()]
//Details about finding PythonLibs
FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[/usr/common/usg/python/2.7.1/lib/libpython2.7.so.1.0][/usr/common/usg/python/2.7.1/include/python2.7][v()]
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
//Details about finding X11
FIND_PACKAGE_MESSAGE_DETAILS_X11:INTERNAL=[/usr/lib64/libX11.so][/usr/include]
//Details about finding ZLIB
FIND_PACKAGE_MESSAGE_DETAILS_ZLIB:INTERNAL=[/usr/lib64/libz.so][/usr/include][v1.2.3()]
//Result of TRY_COMPILE
GETTIMEOFDAY_GIVES_TZ:INTERNAL=FALSE
//ADVANCED property for variable: GITCOMMAND
GITCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GIT_EXECUTABLE
GIT_EXECUTABLE-ADVANCED:INTERNAL=1
//Test GLX_DECLARES_FUNCTION_glXGetProcAddress
GLX_DECLARES_FUNCTION_glXGetProcAddress:INTERNAL=1
//Test GLX_DECLARES_FUNCTION_glXGetProcAddressARB
GLX_DECLARES_FUNCTION_glXGetProcAddressARB:INTERNAL=1
//Test GLX_DECLARES_FUNCTION_glXGetProcAddressARB_AS_EMPTY
GLX_DECLARES_FUNCTION_glXGetProcAddressARB_AS_EMPTY:INTERNAL=
//Test GLX_DECLARES_FUNCTION_glXGetProcAddress_AS_EMPTY
GLX_DECLARES_FUNCTION_glXGetProcAddress_AS_EMPTY:INTERNAL=
//Test GLX_DEFINES_MACRO_GLX_ARB_get_proc_address
GLX_DEFINES_MACRO_GLX_ARB_get_proc_address:INTERNAL=1
//Test GLX_DEFINES_MACRO_GLX_VERSION_1_1
GLX_DEFINES_MACRO_GLX_VERSION_1_1:INTERNAL=1
//Test GLX_DEFINES_MACRO_GLX_VERSION_1_2
GLX_DEFINES_MACRO_GLX_VERSION_1_2:INTERNAL=1
//Test GLX_DEFINES_MACRO_GLX_VERSION_1_3
GLX_DEFINES_MACRO_GLX_VERSION_1_3:INTERNAL=1
//Test GLX_DEFINES_MACRO_GLX_VERSION_1_4
GLX_DEFINES_MACRO_GLX_VERSION_1_4:INTERNAL=1
//Test GLX_DEFINES_TYPE_GLXFBConfig
GLX_DEFINES_TYPE_GLXFBConfig:INTERNAL=1
//Test GLX_DEFINES_TYPE_GLXextFuncPtr
GLX_DEFINES_TYPE_GLXextFuncPtr:INTERNAL=1
//Test GLX_DEFINES_TYPE_GLXextFuncPtr_AS_EMPTY
GLX_DEFINES_TYPE_GLXextFuncPtr_AS_EMPTY:INTERNAL=
//Test GLX_INCLUDES_GLXEXT
GLX_INCLUDES_GLXEXT:INTERNAL=1
GLX_USES_MACRO_GLX_GLXEXT_LEGACY:INTERNAL=TRUE
//ADVANCED property for variable: GUNZIPCOMMAND
GUNZIPCOMMAND-ADVANCED:INTERNAL=1
//Other test 
H5_CXX_HAVE_OFFSETOF:INTERNAL=1
//Other test 
H5_DEV_T_IS_SCALAR:INTERNAL=
//Checking IF overflows normally converting floating-point to integer
// values
H5_FP_TO_INTEGER_OVERFLOW_WORKS:INTERNAL=1
//Result of TRY_COMPILE
H5_FP_TO_INTEGER_OVERFLOW_WORKS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_INTEGER_OVERFLOW_WORKS_RUN:INTERNAL=0
//Checking IF accurately roundup converting floating-point to unsigned
// long long values
H5_FP_TO_ULLONG_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_FP_TO_ULLONG_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_ULLONG_ACCURATE_RUN:INTERNAL=0
//Checking IF right maximum converting floating-point to unsigned
// long long values
H5_FP_TO_ULLONG_RIGHT_MAXIMUM:INTERNAL=
//Result of TRY_COMPILE
H5_FP_TO_ULLONG_RIGHT_MAXIMUM_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_ULLONG_RIGHT_MAXIMUM_RUN:INTERNAL=1
//Other test 
H5_GETTIMEOFDAY_GIVES_TZ:INTERNAL=
//Have function alarm
H5_HAVE_ALARM:INTERNAL=1
//Other test 
H5_HAVE_ATTRIBUTE:INTERNAL=1
//Other test 
H5_HAVE_C99_DESIGNATED_INITIALIZER:INTERNAL=1
//Other test 
H5_HAVE_C99_FUNC:INTERNAL=1
//Have symbol tzname
H5_HAVE_DECL_TZNAME:INTERNAL=1
//Have function difftime
H5_HAVE_DIFFTIME:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h;stdlib.h;memory.h;dlfcn.h
H5_HAVE_DLFCN_H:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h;stdlib.h;memory.h;dlfcn.h;features.h
H5_HAVE_FEATURES_H:INTERNAL=1
//Have function fork
H5_HAVE_FORK:INTERNAL=1
//Have function frexpf
H5_HAVE_FREXPF:INTERNAL=1
//Have function frexpl
H5_HAVE_FREXPL:INTERNAL=1
//Have function fseeko
H5_HAVE_FSEEKO:INTERNAL=1
//Have function fstat64
H5_HAVE_FSTAT64:INTERNAL=1
//Have function ftello
H5_HAVE_FTELLO:INTERNAL=1
//Other test 
H5_HAVE_FUNCTION:INTERNAL=1
//Have function gethostname
H5_HAVE_GETHOSTNAME:INTERNAL=1
//Have function getpwuid
H5_HAVE_GETPWUID:INTERNAL=1
//Have function getrusage
H5_HAVE_GETRUSAGE:INTERNAL=1
//Have includes ;globus/common.h
H5_HAVE_GLOBUS_COMMON_H:INTERNAL=
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h;stdlib.h;memory.h;dlfcn.h;features.h;inttypes.h
H5_HAVE_INTTYPES_H:INTERNAL=1
//Have function ioctl
H5_HAVE_IOCTL:INTERNAL=1
//Have includes ;io.h
H5_HAVE_IO_H:INTERNAL=
//Have library m;
H5_HAVE_LIBM:INTERNAL=1
//Have library socket;m
H5_HAVE_LIBSOCKET:INTERNAL=
//Have library ucb;m
H5_HAVE_LIBUCB:INTERNAL=
//Have library ws2_32;m
H5_HAVE_LIBWS2_32:INTERNAL=
//Have library wsock32;m
H5_HAVE_LIBWSOCK32:INTERNAL=
//Have function longjmp
H5_HAVE_LONGJMP:INTERNAL=1
//Have function lstat
H5_HAVE_LSTAT:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h;stdlib.h;memory.h
H5_HAVE_MEMORY_H:INTERNAL=1
//Have includes ;mfhdf.h
H5_HAVE_MFHDF_H:INTERNAL=
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h;stdlib.h;memory.h;dlfcn.h;features.h;inttypes.h;netinet/in.h
H5_HAVE_NETINET_IN_H:INTERNAL=1
//Other test 
H5_HAVE_OFF64_T:INTERNAL=
//Have includes ;pdb.h
H5_HAVE_PDB_H:INTERNAL=
//Have include ;pthread.h
H5_HAVE_PTHREAD_H:INTERNAL=1
//Have function random
H5_HAVE_RANDOM:INTERNAL=1
//Have function rand_r
H5_HAVE_RAND_R:INTERNAL=1
//Have function setjmp
H5_HAVE_SETJMP:INTERNAL=1
//Have include pthread.h;setjmp.h
H5_HAVE_SETJMP_H:INTERNAL=1
//Have function setsysinfo
H5_HAVE_SETSYSINFO:INTERNAL=
//Have function sigaction
H5_HAVE_SIGACTION:INTERNAL=1
//Have function siglongjmp
H5_HAVE_SIGLONGJMP:INTERNAL=1
//Have function signal
H5_HAVE_SIGNAL:INTERNAL=1
//Have function sigprocmask
H5_HAVE_SIGPROCMASK:INTERNAL=1
//Have function sigsetjmp
H5_HAVE_SIGSETJMP:INTERNAL=
//Have function snprintf
H5_HAVE_SNPRINTF:INTERNAL=1
//Other test 
H5_HAVE_SOCKLEN_T:INTERNAL=
//Have function srandom
H5_HAVE_SRANDOM:INTERNAL=1
//Have includes pthread.h;setjmp.h;srbclient.h
H5_HAVE_SRBCLIENT_H:INTERNAL=
//Have function stat64
H5_HAVE_STAT64:INTERNAL=1
//Other test 
H5_HAVE_STAT_ST_BLOCKS:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h
H5_HAVE_STDDEF_H:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h
H5_HAVE_STDINT_H:INTERNAL=1
//Have include stdint.h
H5_HAVE_STDINT_H_CXX:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h;stdlib.h
H5_HAVE_STDLIB_H:INTERNAL=1
//Have function strdup
H5_HAVE_STRDUP:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h
H5_HAVE_STRINGS_H:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h
H5_HAVE_STRING_H:INTERNAL=1
//Other test 
H5_HAVE_STRUCT_TIMEZONE:INTERNAL=
//Other test 
H5_HAVE_STRUCT_TM_TM_ZONE:INTERNAL=1
//Have function symlink
H5_HAVE_SYMLINK:INTERNAL=1
//Have function system
H5_HAVE_SYSTEM:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h
H5_HAVE_SYS_IOCTL_H:INTERNAL=1
//Have includes pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/proc.h
H5_HAVE_SYS_PROC_H:INTERNAL=
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h
H5_HAVE_SYS_RESOURCE_H:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h
H5_HAVE_SYS_SOCKET_H:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h
H5_HAVE_SYS_STAT_H:INTERNAL=1
H5_HAVE_SYS_SYSINFO_H:INTERNAL=
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h
H5_HAVE_SYS_TIMEB_H:INTERNAL=1
//H5_HAVE_SYS_TIME_GETTIMEOFDAY
H5_HAVE_SYS_TIME_GETTIMEOFDAY:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h
H5_HAVE_SYS_TIME_H:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h
H5_HAVE_SYS_TYPES_H:INTERNAL=1
//Other test 
H5_HAVE_TIMEZONE:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h
H5_HAVE_TIME_H:INTERNAL=1
//Have symbol TIOCGETD
H5_HAVE_TIOCGETD:INTERNAL=1
//Have symbol TIOCGWINSZ
H5_HAVE_TIOCGWINSZ:INTERNAL=1
//Other test 
H5_HAVE_TM_GMTOFF:INTERNAL=1
//Other test 
H5_HAVE_TM_ZONE:INTERNAL=1
//Have include pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h
H5_HAVE_UNISTD_H:INTERNAL=1
//Have function vasprintf
H5_HAVE_VASPRINTF:INTERNAL=1
//Have function vsnprintf
H5_HAVE_VSNPRINTF:INTERNAL=1
//Have function waitpid
H5_HAVE_WAITPID:INTERNAL=1
//Have includes pthread.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h;sys/ioctl.h;sys/resource.h;sys/socket.h;sys/stat.h;sys/time.h;time.h;sys/timeb.h;sys/types.h;unistd.h;stdlib.h;memory.h;dlfcn.h;features.h;inttypes.h;winsock.h
H5_HAVE_WINSOCK_H:INTERNAL=
//Other test 
H5_INLINE_TEST___inline:INTERNAL=1
//Other test 
H5_INLINE_TEST___inline__:INTERNAL=1
//Other test 
H5_INLINE_TEST_inline:INTERNAL=1
//checking IF accurately converting from integers to long double
H5_INTEGER_TO_LDOUBLE_ACCURATE:INTERNAL=1
//checking IF converting from long double to integers is accurate
H5_LDOUBLE_TO_INTEGER_ACCURATE:INTERNAL=1
//Checking IF converting from long double to integers works
H5_LDOUBLE_TO_INTEGER_WORKS:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_INTEGER_WORKS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_INTEGER_WORKS_RUN:INTERNAL=0
//Checking IF correctly converting long double to (unsigned) long
// long values
H5_LDOUBLE_TO_LLONG_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_LLONG_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_LLONG_ACCURATE_RUN:INTERNAL=0
//Checking IF correctly converting long double to unsigned int
// values
H5_LDOUBLE_TO_UINT_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_UINT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_UINT_ACCURATE_RUN:INTERNAL=0
//Checking IF compiling long long to floating-point typecasts work
H5_LLONG_TO_FP_CAST_WORKS:INTERNAL=1
//Checking IF correctly converting (unsigned) long long to long
// double values
H5_LLONG_TO_LDOUBLE_CORRECT:INTERNAL=1
//Result of TRY_COMPILE
H5_LLONG_TO_LDOUBLE_CORRECT_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LLONG_TO_LDOUBLE_CORRECT_RUN:INTERNAL=0
//Checking IF alignment restrictions are strictly enforced
H5_NO_ALIGNMENT_RESTRICTIONS:INTERNAL=1
//Result of TRY_COMPILE
H5_NO_ALIGNMENT_RESTRICTIONS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_NO_ALIGNMENT_RESTRICTIONS_RUN:INTERNAL=0
//Width for printf for type `long long' or `__int64', us. `ll
H5_PRINTF_LL_WIDTH:INTERNAL="ll"
//CHECK_TYPE_SIZE: sizeof(char)
H5_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
H5_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
H5_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
H5_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int16_t)
H5_SIZEOF_INT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int32_t)
H5_SIZEOF_INT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int64_t)
H5_SIZEOF_INT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int8_t)
H5_SIZEOF_INT8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int_fast16_t)
H5_SIZEOF_INT_FAST16_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_fast32_t)
H5_SIZEOF_INT_FAST32_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_fast64_t)
H5_SIZEOF_INT_FAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_fast8_t)
H5_SIZEOF_INT_FAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int_least16_t)
H5_SIZEOF_INT_LEAST16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int_least32_t)
H5_SIZEOF_INT_LEAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int_least64_t)
H5_SIZEOF_INT_LEAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_least8_t)
H5_SIZEOF_INT_LEAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(long)
H5_SIZEOF_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long double)
H5_SIZEOF_LONG_DOUBLE:INTERNAL=16
//CHECK_TYPE_SIZE: sizeof(long long)
H5_SIZEOF_LONG_LONG:INTERNAL=8
//SizeOf for off64_t
H5_SIZEOF_OFF64_T:INTERNAL=0
//CHECK_TYPE_SIZE: sizeof(off_t)
H5_SIZEOF_OFF_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
H5_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(size_t)
H5_SIZEOF_SIZE_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(ssize_t)
H5_SIZEOF_SSIZE_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint16_t)
H5_SIZEOF_UINT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint32_t)
H5_SIZEOF_UINT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint64_t)
H5_SIZEOF_UINT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint8_t)
H5_SIZEOF_UINT8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(uint_fast16_t)
H5_SIZEOF_UINT_FAST16_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_fast32_t)
H5_SIZEOF_UINT_FAST32_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_fast64_t)
H5_SIZEOF_UINT_FAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_fast8_t)
H5_SIZEOF_UINT_FAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(uint_least16_t)
H5_SIZEOF_UINT_LEAST16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint_least32_t)
H5_SIZEOF_UINT_LEAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint_least64_t)
H5_SIZEOF_UINT_LEAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_least8_t)
H5_SIZEOF_UINT_LEAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(unsigned)
H5_SIZEOF_UNSIGNED:INTERNAL=4
//SizeOf for __int64
H5_SIZEOF___INT64:INTERNAL=0
//Other test 
H5_STDC_HEADERS:INTERNAL=1
//Other test 
H5_SYSTEM_SCOPE_THREADS:INTERNAL=1
//Other test 
H5_TIME_WITH_SYS_TIME:INTERNAL=1
//Checking IF compiling unsigned long long to floating-point typecasts
// work
H5_ULLONG_TO_FP_CAST_WORKS:INTERNAL=1
//Checking IF converting unsigned long long to long double with
// precision
H5_ULLONG_TO_LDOUBLE_PRECISION:INTERNAL=1
//Result of TRY_COMPILE
H5_ULLONG_TO_LDOUBLE_PRECISION_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_ULLONG_TO_LDOUBLE_PRECISION_RUN:INTERNAL=0
//Checking IF accurately converting unsigned long to float values
H5_ULONG_TO_FLOAT_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_ULONG_TO_FLOAT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_ULONG_TO_FLOAT_ACCURATE_RUN:INTERNAL=0
//Checking IF accurately converting unsigned long long to floating-point
// values
H5_ULONG_TO_FP_BOTTOM_BIT_ACCURATE:INTERNAL=
//Result of TRY_COMPILE
H5_ULONG_TO_FP_BOTTOM_BIT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_ULONG_TO_FP_BOTTOM_BIT_ACCURATE_RUN:INTERNAL=1
//Other test 
H5_VSNPRINTF_WORKS:INTERNAL=1
//Have symbol alloca
HAVE_ALLOCA:INTERNAL=1
//Have include ;alloca.h
HAVE_ALLOCA_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h
HAVE_ANSIDECL_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h
HAVE_ARPA_INET_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h
HAVE_ARPA_NAMESER_H:INTERNAL=1
//Have include assert.h
HAVE_ASSERT_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_ATTRIBUTE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_C99_DESIGNATED_INITIALIZER:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_C99_FUNC:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_VOID_P:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_WORDS_BIGENDIAN:INTERNAL=TRUE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h
HAVE_CTYPE_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h
HAVE_DIRENT_H:INTERNAL=1
//Have include dlfcn.h
HAVE_DLFCN_H:INTERNAL=1
//Have library dl;-lpthread;dl;m
HAVE_DLOPEN:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;dl.h
HAVE_DL_H:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h
HAVE_ERRNO_H:INTERNAL=1
//Have include fcntl.h
HAVE_FCNTL_H:INTERNAL=1
//Have include fenv.h
HAVE_FENV_H:INTERNAL=1
//Have symbol finite
HAVE_FINITE:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h
HAVE_FLOAT_H:INTERNAL=1
//Have function floor
HAVE_FLOOR:INTERNAL=
//Have symbol fpclass
HAVE_FPCLASS:INTERNAL=
//Have symbol fprintf
HAVE_FPRINTF:INTERNAL=1
//Have symbol fp_class
HAVE_FP_CLASS:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;fp_class.h
HAVE_FP_CLASS_H:INTERNAL=
//Have symbol ftime
HAVE_FTIME:INTERNAL=1
//NetCDF test 
HAVE_FTRUNCATE:INTERNAL=1
//Result of TRY_COMPILE
HAVE_FUNCTION:INTERNAL=TRUE
//Test HAVE_GCC_ERROR_RETURN_TYPE
HAVE_GCC_ERROR_RETURN_TYPE:INTERNAL=1
//Test HAVE_GCC_VISIBILITY
HAVE_GCC_VISIBILITY:INTERNAL=1
//Result of TRY_COMPILE
HAVE_GETADDRINFO_COMPILED:INTERNAL=TRUE
//Have function getopt
HAVE_GETOPT:INTERNAL=1
//Have symbol gettimeofday
HAVE_GETTIMEOFDAY:INTERNAL=1
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_OFF64_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_OFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SSIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UNSIGNED:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF___INT64:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_VOID_P:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF___INT64:INTERNAL=FALSE
//Have includes ieeefp.h
HAVE_IEEEFP_H:INTERNAL=
//Test HAVE_INLINE_FUNCTIONS
HAVE_INLINE_FUNCTIONS:INTERNAL=1
//Have include inttypes.h
HAVE_INTTYPES_H:INTERNAL=1
//Have function isascii
HAVE_ISASCII:INTERNAL=1
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF___INT64:INTERNAL=FALSE
//Have library dl;
HAVE_LIBDL:INTERNAL=1
//Have include limits.h
HAVE_LIMITS_H:INTERNAL=1
//Have symbol localtime
HAVE_LOCALTIME:INTERNAL=1
//Have include malloc.h
HAVE_MALLOC_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h
HAVE_MATH_H:INTERNAL=1
//Have function memmove
HAVE_MEMMOVE:INTERNAL=1
//Have include memory.h
HAVE_MEMORY_H:INTERNAL=1
//Have function memset
HAVE_MEMSET:INTERNAL=1
//Have function mmap
HAVE_MMAP:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;nan.h
HAVE_NAN_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;ndir.h
HAVE_NDIR_H:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h
HAVE_NETDB_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h
HAVE_NETINET_IN_H:INTERNAL=1
//Test HAVE_NO_COMMON
HAVE_NO_COMMON:INTERNAL=1
//Result of TRY_COMPILE
HAVE_OFF64_T:INTERNAL=FALSE
//Test HAVE_OMIT_FRAME_POINTER
HAVE_OMIT_FRAME_POINTER:INTERNAL=1
//Have function pow
HAVE_POW:INTERNAL=
//Have symbol printf
HAVE_PRINTF:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h
HAVE_PTHREAD_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h
HAVE_RESOLV_H:INTERNAL=1
//Have library dld;dl
HAVE_SHLLOAD:INTERNAL=
//Have symbol signal
HAVE_SIGNAL:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h
HAVE_SIGNAL_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_OFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_PTRDIFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SSIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_UCHAR:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF__BOOL:INTERNAL=TRUE
//Have symbol snprintf
HAVE_SNPRINTF:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SOCKLEN_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SOCKLEN_T_COMPILED:INTERNAL=TRUE
//Have symbol sprintf
HAVE_SPRINTF:INTERNAL=1
//Have function sqrt
HAVE_SQRT:INTERNAL=
//Have symbol sscanf
HAVE_SSCANF:INTERNAL=1
//Have symbol stat
HAVE_STAT:INTERNAL=1
//Result of TRY_COMPILE
HAVE_STAT_ST_BLOCKS:INTERNAL=TRUE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h
HAVE_STDARG_H:INTERNAL=1
//Have include alloca.h;stdlib.h;sys/types.h;sys/stat.h;unistd.h;fcntl.h;stdio.h;string.h;stddef.h;stdint.h;inttypes.h;stdbool.h
HAVE_STDBOOL_H:INTERNAL=1
//Have include stddef.h
HAVE_STDDEF_H:INTERNAL=1
//Have include stdint.h
HAVE_STDINT_H:INTERNAL=1
//Have include ;stdio.h
HAVE_STDIO_H:INTERNAL=1
//Have include stdlib.h
HAVE_STDLIB_H:INTERNAL=1
//Test HAVE_STD_C99
HAVE_STD_C99:INTERNAL=1
//Have function strcasecmp
HAVE_STRCASECMP:INTERNAL=1
//Have function strchr
HAVE_STRCHR:INTERNAL=1
//Have symbol strdup
HAVE_STRDUP:INTERNAL=1
//Have symbol strerror
HAVE_STRERROR:INTERNAL=1
//Have symbol strftime
HAVE_STRFTIME:INTERNAL=1
//Have include strings.h
HAVE_STRINGS_H:INTERNAL=1
//Have include string.h
HAVE_STRING_H:INTERNAL=1
//Have symbol strndup
HAVE_STRNDUP:INTERNAL=1
//Have function strrchr
HAVE_STRRCHR:INTERNAL=1
//Have function strstr
HAVE_STRSTR:INTERNAL=1
//Have function strtol
HAVE_STRTOL:INTERNAL=1
//Have function strtoll
HAVE_STRTOLL:INTERNAL=1
//Have function areroul
HAVE_STRTOUL:INTERNAL=
//Result of TRY_COMPILE
HAVE_STRUCT_TIMEZONE:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_STRUCT_TM_TM_ZONE:INTERNAL=TRUE
//NetCDF test 
HAVE_ST_BLKSIZE:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SYS_DIR_H_COMPILED:INTERNAL=TRUE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h
HAVE_SYS_MMAN_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SYS_NDIR_H_COMPILED:INTERNAL=FALSE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h
HAVE_SYS_SELECT_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h
HAVE_SYS_SOCKET_H:INTERNAL=1
//Have include sys/stat.h
HAVE_SYS_STAT_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h;unistd.h;signal.h;errno.h;ansidecl.h;arpa/inet.h;arpa/nameser.h;ctype.h;dirent.h;float.h;math.h;pthread.h;resolv.h;stdarg.h;sys/mman.h;sys/timeb.h
HAVE_SYS_TIMEB_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SYS_TIME_GETTIMEOFDAY:INTERNAL=TRUE
//Have include sys/time.h
HAVE_SYS_TIME_H:INTERNAL=1
//Have include sys/types.h
HAVE_SYS_TYPES_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_TIMEZONE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_TIME_GETTIMEOFDAY:INTERNAL=FALSE
//Have include stdio.h;stddef.h;sys/types.h;inttypes.h;dlfcn.h;fcntl.h;malloc.h;memory.h;netdb.h;limits.h;sys/socket.h;netinet/in.h;sys/select.h;stdint.h;stdlib.h;string.h;strings.h;sys/stat.h;sys/time.h;time.h
HAVE_TIME_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_TM_GMTOFF:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_TM_ZONE:INTERNAL=TRUE
//Have include unistd.h
HAVE_UNISTD_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_VA_COPY_COMPILED:INTERNAL=TRUE
//Have symbol vfprintf
HAVE_VFPRINTF:INTERNAL=1
//Have symbol vsnprintf
HAVE_VSNPRINTF:INTERNAL=1
//Have symbol vsprintf
HAVE_VSPRINTF:INTERNAL=1
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF___INT64:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_VTK_UINTPTR_T:INTERNAL=TRUE
//Have includes windows.h
HAVE_WINDOWS_H:INTERNAL=
//Have symbol _stat
HAVE__STAT:INTERNAL=
//Result of TRY_COMPILE
HAVE___VA_COPY_COMPILED:INTERNAL=TRUE
//ADVANCED property for variable: HDF5_BUILD_CPP_LIB
HDF5_BUILD_CPP_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_BUILD_HL_LIB
HDF5_BUILD_HL_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_DISABLE_COMPILER_WARNINGS
HDF5_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_HSIZET
HDF5_ENABLE_HSIZET-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_LARGE_FILE
HDF5_ENABLE_LARGE_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_PARALLEL
HDF5_ENABLE_PARALLEL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_SZIP_SUPPORT
HDF5_ENABLE_SZIP_SUPPORT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_ENABLE_Z_LIB_SUPPORT
HDF5_ENABLE_Z_LIB_SUPPORT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_Enable_Clear_File_Buffers
HDF5_Enable_Clear_File_Buffers-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_Enable_Instrument
HDF5_Enable_Instrument-ADVANCED:INTERNAL=1
//Used to pass variables between directories
HDF5_LIBRARIES_TO_EXPORT:INTERNAL=vtkhdf5
//ADVANCED property for variable: HDF5_METADATA_TRACE_FILE
HDF5_METADATA_TRACE_FILE-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
HDF5_PRINTF_LL_TEST_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
HDF5_PRINTF_LL_TEST_RUN:INTERNAL=0
//ADVANCED property for variable: HDF5_STRICT_FORMAT_CHECKS
HDF5_STRICT_FORMAT_CHECKS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_USE_16_API_DEFAULT
HDF5_USE_16_API_DEFAULT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_USE_FILTER_FLETCHER32
HDF5_USE_FILTER_FLETCHER32-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_USE_FILTER_NBIT
HDF5_USE_FILTER_NBIT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_USE_FILTER_SCALEOFFSET
HDF5_USE_FILTER_SCALEOFFSET-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_USE_FILTER_SHUFFLE
HDF5_USE_FILTER_SHUFFLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_USE_H5DUMP_PACKED_BITS
HDF5_USE_H5DUMP_PACKED_BITS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_WANT_DATA_ACCURACY
HDF5_WANT_DATA_ACCURACY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HDF5_WANT_DCONV_EXCEPTION
HDF5_WANT_DCONV_EXCEPTION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: HGCOMMAND
HGCOMMAND-ADVANCED:INTERNAL=1
//HTMLDocumentation files generated from ServerManager
HTMLDocumentation_FILES:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/Documentation/ParaViewSources.html;/scratch/scratchdirs/acbauer/paraview-build/Documentation/ParaViewFilters.html;/scratch/scratchdirs/acbauer/paraview-build/Documentation/ParaViewReaders.html;/scratch/scratchdirs/acbauer/paraview-build/Documentation/ParaViewWriters.html
//ADVANCED property for variable: ICET_MPIRUN_EXE
ICET_MPIRUN_EXE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_MPI_MAX_NUMPROCS
ICET_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//This is set from VTK_MPI_MAX_NUMPROCS.
ICET_MPI_MAX_NUMPROCS:INTERNAL=2
//ADVANCED property for variable: ICET_MPI_NUMPROC_FLAG
ICET_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_MPI_POSTFLAGS
ICET_MPI_POSTFLAGS-ADVANCED:INTERNAL=1
//This is set from VTK_MPI_POSTFLAGS.
ICET_MPI_POSTFLAGS:INTERNAL=
//ADVANCED property for variable: ICET_MPI_PREFLAGS
ICET_MPI_PREFLAGS-ADVANCED:INTERNAL=1
//This is set from a combination of VTK_MPI_PREFLAGS VTK_MPI_NUMPROC_FLAG
// VTK_MPI_MAX_NUMPROCS VTK_MPI_PREFLAGS.
ICET_MPI_PREFLAGS:INTERNAL=;-np;2;
//CHECK_TYPE_SIZE: sizeof(char)
ICET_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
ICET_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
ICET_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
ICET_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
ICET_SIZEOF_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long long)
ICET_SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
ICET_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(void*)
ICET_SIZEOF_VOID_P:INTERNAL=8
//CHECK_TYPE_SIZE: __int64 unknown
ICET_SIZEOF___INT64:INTERNAL=
//ADVANCED property for variable: ICET_USE_MPE
ICET_USE_MPE-ADVANCED:INTERNAL=1
//Whether streams support 64-bit types
ICE_HAVE_64BIT_STREAMS:INTERNAL=1
//ADVANCED property for variable: ICE_HAVE_FCNTL
ICE_HAVE_FCNTL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICE_HAVE_MMAN
ICE_HAVE_MMAN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICE_HAVE_NETINET
ICE_HAVE_NETINET-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
INLINE_TEST___inline:INTERNAL=TRUE
//Result of TRY_COMPILE
INLINE_TEST___inline__:INTERNAL=TRUE
//Result of TRY_COMPILE
INLINE_TEST_inline:INTERNAL=TRUE
//ADVANCED property for variable: JAVACOMMAND
JAVACOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: KWCommon_BUILD_TESTING
KWCommon_BUILD_TESTING-ADVANCED:INTERNAL=1
//include paths for KWCommon
KWCommon_INCLUDE_PATH:INTERNAL=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/Common/KWCommon
//libraries for KWCommon
KWCommon_LIBRARIES:INTERNAL=KWCommon
//Result of TRY_RUN
KWSYS_CHAR_IS_SIGNED:INTERNAL=0
//Result of TRY_COMPILE
KWSYS_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ARGUMENT_DEPENDENT_LOOKUP_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CSTDDEF_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CSTDIO_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_FULL_SPECIALIZATION_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_MEMBER_TEMPLATES_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_NULL_TEMPLATE_ARGS_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_C_HAS_PTRDIFF_T_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_C_HAS_SSIZE_T_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_C_TYPE_MACROS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_HAVE_BINARY_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_HAVE_STD_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_USE_ANSI_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_USE_SSTREAM_COMPILED:INTERNAL=TRUE
//Result of TRY_RUN
KWSYS_LFS_WORKS:INTERNAL=0
//Result of TRY_COMPILE
KWSYS_LFS_WORKS_COMPILED:INTERNAL=TRUE
//CHECK_TYPE_SIZE: sizeof(char)
KWSYS_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: __int64 unknown
KWSYS_SIZEOF___INT64:INTERNAL=
//Result of TRY_COMPILE
KWSYS_STAT_HAS_ST_MTIM_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_MAX_SIZE_ARGUMENT_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_OBJECTS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_REBIND_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_TEMPLATE_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ITERATOR_TRAITS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAVE_STD_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_STRING_HAVE_NEQ_CHAR_COMPILED:INTERNAL=TRUE
//ADVANCED property for variable: LIBRARY_OUTPUT_PATH
LIBRARY_OUTPUT_PATH-ADVANCED:INTERNAL=1
//Single output directory for building all libraries.
LIBRARY_OUTPUT_PATH:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/bin
//ADVANCED property for variable: MAKECOMMAND
MAKECOMMAND-ADVANCED:INTERNAL=1
//Path to vtkMaterialLibraryMacro.h
MATERIAL_LIBRARY_MATERIAL_MACRO_HEADER:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/MaterialLibrary/vtkMaterialLibraryMacro.h
//Path to vtkShaderCodeLibraryMacro.h
MATERIAL_LIBRARY_SHADER_MACRO_HEADER:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/MaterialLibrary/vtkShaderCodeLibraryMacro.h
//ADVANCED property for variable: MEMORYCHECK_COMMAND
MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE
MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC
MPIEXEC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS
MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG
MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_POSTFLAGS
MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_PREFLAGS
MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILER
MPI_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS
MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_INCLUDE_PATH
MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1
//MODIFIED property for variable: MPI_CXX_INCLUDE_PATH
MPI_CXX_INCLUDE_PATH-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: MPI_CXX_LIBRARIES
MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_LINK_FLAGS
MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILER
MPI_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILE_FLAGS
MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_INCLUDE_PATH
MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=1
//MODIFIED property for variable: MPI_C_INCLUDE_PATH
MPI_C_INCLUDE_PATH-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: MPI_C_LIBRARIES
MPI_C_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_LINK_FLAGS
MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_EXTRA_LIBRARY
MPI_EXTRA_LIBRARY-ADVANCED:INTERNAL=0
//MODIFIED property for variable: MPI_EXTRA_LIBRARY
MPI_EXTRA_LIBRARY-MODIFIED:INTERNAL=ON
//Scratch variable for MPI header detection
MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND
//Scratch variable for MPI lib detection
MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND
//ADVANCED property for variable: MPI_LIBRARY
MPI_LIBRARY-ADVANCED:INTERNAL=0
//MODIFIED property for variable: MPI_LIBRARY
MPI_LIBRARY-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: NETCDF_DISABLE_COMPILER_WARNINGS
NETCDF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//Have library c
NOT_NEED_LIBNSL:INTERNAL=1
//ADVANCED property for variable: OPENGL_INCLUDE_DIR
OPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OPENGL_INCLUDE_DIR
OPENGL_INCLUDE_DIR-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: OPENGL_gl_LIBRARY
OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OPENGL_gl_LIBRARY
OPENGL_gl_LIBRARY-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: OPENGL_glu_LIBRARY
OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OPENGL_glu_LIBRARY
OPENGL_glu_LIBRARY-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: OPENGL_xmesa_INCLUDE_DIR
OPENGL_xmesa_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSMESA_INCLUDE_DIR
OSMESA_INCLUDE_DIR-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OSMESA_INCLUDE_DIR
OSMESA_INCLUDE_DIR-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: OSMESA_LIBRARY
OSMESA_LIBRARY-ADVANCED:INTERNAL=1
//MODIFIED property for variable: OSMESA_LIBRARY
OSMESA_LIBRARY-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PARAVIEW_ALWAYS_SECURE_CONNECTION
PARAVIEW_ALWAYS_SECURE_CONNECTION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AdiosReader
PARAVIEW_BUILD_PLUGIN_AdiosReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIReaderWriter
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIReaderWriter-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_EyeDomeLighting
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ForceTime
PARAVIEW_BUILD_PLUGIN_ForceTime-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_H5PartReader
PARAVIEW_BUILD_PLUGIN_H5PartReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Manta
PARAVIEW_BUILD_PLUGIN_Manta-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Moments
PARAVIEW_BUILD_PLUGIN_Moments-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PacMan
PARAVIEW_BUILD_PLUGIN_PacMan-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PointSprite
PARAVIEW_BUILD_PLUGIN_PointSprite-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Prism
PARAVIEW_BUILD_PLUGIN_Prism-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SLACTools
PARAVIEW_BUILD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SQToolkit
PARAVIEW_BUILD_PLUGIN_SQToolkit-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SierraPlotTools
PARAVIEW_BUILD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamingView
PARAVIEW_BUILD_PLUGIN_StreamingView-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SurfaceLIC
PARAVIEW_BUILD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin
PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_pvblot
PARAVIEW_BUILD_PLUGIN_pvblot-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PARAVIEW_BUILD_QT_GUI
PARAVIEW_BUILD_QT_GUI-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PARAVIEW_DISABLE_VTK_TESTING
PARAVIEW_DISABLE_VTK_TESTING-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_COPROCESSING
PARAVIEW_ENABLE_COPROCESSING-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_FPE
PARAVIEW_ENABLE_FPE-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PARAVIEW_ENABLE_PYTHON
PARAVIEW_ENABLE_PYTHON-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PARAVIEW_EXTERNAL_PLUGINS_FILE
PARAVIEW_EXTERNAL_PLUGINS_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_EXTERNAL_PLUGIN_DIRS
PARAVIEW_EXTERNAL_PLUGIN_DIRS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_EXTRA_EXTERNAL_MODULES
PARAVIEW_EXTRA_EXTERNAL_MODULES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_INSTALL_DEVELOPMENT
PARAVIEW_INSTALL_DEVELOPMENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES
PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_MINIMAL_BUILD
PARAVIEW_MINIMAL_BUILD-ADVANCED:INTERNAL=1
//List of configured plugins
PARAVIEW_PLUGINLIST:INTERNAL=Moments;PrismServerPlugin;PacMan;PointSprite_Plugin;pvblot;SLACTools;StreamingView;H5PartReader;AnalyzeReader;AnalyzeWriter;NIfTIReader;NIfTIWriter
//ADVANCED property for variable: PARAVIEW_TESTING_WITH_PYTHON
PARAVIEW_TESTING_WITH_PYTHON-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_ICE_T
PARAVIEW_USE_ICE_T-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PARAVIEW_USE_MPI
PARAVIEW_USE_MPI-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PARAVIEW_USE_MPI_SSEND
PARAVIEW_USE_MPI_SSEND-ADVANCED:INTERNAL=1
//Have symbol atanh
PROJ_HAVE_ATANH:INTERNAL=1
//Have symbol csin
PROJ_HAVE_COMPLEX:INTERNAL=1
//ADVANCED property for variable: PROJ_LIST_EXTERNAL
PROJ_LIST_EXTERNAL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PROJ_USE_GSL
PROJ_USE_GSL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PROJ_USE_PTHREADS
PROJ_USE_PTHREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PROTOBUF_DISABLE_COMPILER_WARNINGS
PROTOBUF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//Path to paraview module.
PV_PYTHON_MODULE_DIR:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/Utilities/VTKPythonWrapping
//ADVANCED property for variable: PV_TEST_CLEAN_COMMAND
PV_TEST_CLEAN_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_CLIENT
PV_TEST_CLIENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_INIT_COMMAND
PV_TEST_INIT_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_MPIPython
PYTHON_ENABLE_MODULE_MPIPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkChartsPython
PYTHON_ENABLE_MODULE_vtkChartsPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkCommonPython
PYTHON_ENABLE_MODULE_vtkCommonPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkFilteringPython
PYTHON_ENABLE_MODULE_vtkFilteringPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkGenericFilteringPython
PYTHON_ENABLE_MODULE_vtkGenericFilteringPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkGeovisPython
PYTHON_ENABLE_MODULE_vtkGeovisPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkGraphicsPython
PYTHON_ENABLE_MODULE_vtkGraphicsPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkHybridPython
PYTHON_ENABLE_MODULE_vtkHybridPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkIOPython
PYTHON_ENABLE_MODULE_vtkIOPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkImagingPython
PYTHON_ENABLE_MODULE_vtkImagingPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkInfovisPython
PYTHON_ENABLE_MODULE_vtkInfovisPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkPVClientServerCorePython
PYTHON_ENABLE_MODULE_vtkPVClientServerCorePython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkPVCommonPython
PYTHON_ENABLE_MODULE_vtkPVCommonPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkPVServerImplementationPython
PYTHON_ENABLE_MODULE_vtkPVServerImplementationPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkPVServerManagerPython
PYTHON_ENABLE_MODULE_vtkPVServerManagerPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkPVVTKExtensionsPython
PYTHON_ENABLE_MODULE_vtkPVVTKExtensionsPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkParallelPython
PYTHON_ENABLE_MODULE_vtkParallelPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkRenderingPython
PYTHON_ENABLE_MODULE_vtkRenderingPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkViewsPython
PYTHON_ENABLE_MODULE_vtkViewsPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkVolumeRenderingPython
PYTHON_ENABLE_MODULE_vtkVolumeRenderingPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_ENABLE_MODULE_vtkWidgetsPython
PYTHON_ENABLE_MODULE_vtkWidgetsPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PYTHON_EXTRA_LIBS
PYTHON_EXTRA_LIBS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_INCLUDE_DIR
PYTHON_INCLUDE_DIR-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PYTHON_INCLUDE_DIR
PYTHON_INCLUDE_DIR-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PYTHON_INCLUDE_PATH
PYTHON_INCLUDE_PATH-ADVANCED:INTERNAL=1
//Path to where Python.h is found (deprecated)
PYTHON_INCLUDE_PATH:INTERNAL=/usr/common/usg/python/2.7.1/include/python2.7
//ADVANCED property for variable: PYTHON_LIBRARY
PYTHON_LIBRARY-ADVANCED:INTERNAL=1
//MODIFIED property for variable: PYTHON_LIBRARY
PYTHON_LIBRARY-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: PYTHON_MODULE_MPIPython_BUILD_SHARED
PYTHON_MODULE_MPIPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkChartsPython_BUILD_SHARED
PYTHON_MODULE_vtkChartsPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkCommonPython_BUILD_SHARED
PYTHON_MODULE_vtkCommonPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkFilteringPython_BUILD_SHARED
PYTHON_MODULE_vtkFilteringPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkGenericFilteringPython_BUILD_SHARED
PYTHON_MODULE_vtkGenericFilteringPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkGeovisPython_BUILD_SHARED
PYTHON_MODULE_vtkGeovisPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkGraphicsPython_BUILD_SHARED
PYTHON_MODULE_vtkGraphicsPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkHybridPython_BUILD_SHARED
PYTHON_MODULE_vtkHybridPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkIOPython_BUILD_SHARED
PYTHON_MODULE_vtkIOPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkImagingPython_BUILD_SHARED
PYTHON_MODULE_vtkImagingPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkInfovisPython_BUILD_SHARED
PYTHON_MODULE_vtkInfovisPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkPVClientServerCorePython_BUILD_SHARED
PYTHON_MODULE_vtkPVClientServerCorePython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkPVCommonPython_BUILD_SHARED
PYTHON_MODULE_vtkPVCommonPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkPVServerImplementationPython_BUILD_SHARED
PYTHON_MODULE_vtkPVServerImplementationPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkPVServerManagerPython_BUILD_SHARED
PYTHON_MODULE_vtkPVServerManagerPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkPVVTKExtensionsPython_BUILD_SHARED
PYTHON_MODULE_vtkPVVTKExtensionsPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkParallelPython_BUILD_SHARED
PYTHON_MODULE_vtkParallelPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkRenderingPython_BUILD_SHARED
PYTHON_MODULE_vtkRenderingPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkViewsPython_BUILD_SHARED
PYTHON_MODULE_vtkViewsPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkVolumeRenderingPython_BUILD_SHARED
PYTHON_MODULE_vtkVolumeRenderingPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_MODULE_vtkWidgetsPython_BUILD_SHARED
PYTHON_MODULE_vtkWidgetsPython_BUILD_SHARED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_UTIL_LIBRARY
PYTHON_UTIL_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SCPCOMMAND
SCPCOMMAND-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
SHARED_LIBRARY_PATH_INFO_COMPILED:INTERNAL=TRUE
//Result of TRY_RUN
SHARED_LIBRARY_PATH_TYPE:INTERNAL=0
//runtime library path variable name.
SHARED_LIBRARY_PATH_VAR_NAME:INTERNAL=LD_LIBRARY_PATH
//ADVANCED property for variable: SITE
SITE-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
SIZEOF_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long long)
SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(off_t)
SIZEOF_OFF_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(ptrdiff_t)
SIZEOF_PTRDIFF_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(size_t)
SIZEOF_SIZE_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(ssize_t)
SIZEOF_SSIZE_T:INTERNAL=8
//CHECK_TYPE_SIZE: uchar unknown
SIZEOF_UCHAR:INTERNAL=
//CHECK_TYPE_SIZE: sizeof(_Bool)
SIZEOF__BOOL:INTERNAL=1
//ADVANCED property for variable: SLURM_SBATCH_COMMAND
SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SLURM_SRUN_COMMAND
SLURM_SRUN_COMMAND-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
STDC_HEADERS:INTERNAL=TRUE
//Result of TRY_COMPILE
SUCCEED:INTERNAL=TRUE
//Result of TRY_COMPILE
SUCCEED_MAP:INTERNAL=TRUE
//Result of TRY_COMPILE
SUCCEED_SET:INTERNAL=TRUE
//Result of TRY_COMPILE
SUPPORT_IP6_COMPILED:INTERNAL=TRUE
//ADVANCED property for variable: SVNCOMMAND
SVNCOMMAND-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
SYSTEM_SCOPE_THREADS:INTERNAL=TRUE
//ADVANCED property for variable: TCL_LIBRARY
TCL_LIBRARY-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
TIME_WITH_SYS_TIME:INTERNAL=TRUE
//ADVANCED property for variable: TK_LIBRARY
TK_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_BUILD_DOC
VERDICT_BUILD_DOC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_ENABLE_TESTING
VERDICT_ENABLE_TESTING-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_MANGLE
VERDICT_MANGLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_MANGLE_PREFIX
VERDICT_MANGLE_PREFIX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_USE_FLOAT
VERDICT_USE_FLOAT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VLI_LIBRARY_FOR_VP1000
VLI_LIBRARY_FOR_VP1000-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
VSNPRINTF_WORKS:INTERNAL=TRUE
//Result of TRY_COMPILE
VTK_ANSI_STREAM_EOF_COMPILED:INTERNAL=TRUE
//Result of TRY_RUN
VTK_ANSI_STREAM_EOF_RESULT:INTERNAL=1
//ADVANCED property for variable: VTK_BUILD_FORWARDING_EXECUTABLES
VTK_BUILD_FORWARDING_EXECUTABLES-ADVANCED:INTERNAL=1
VTK_CMAKE_DIR:INTERNAL=/global/homes/a/acbauer/CODE/ParaView/paraview-climate-3.11.1/VTK/CMake
//Support for C++ type bool
VTK_COMPILER_HAS_BOOL:INTERNAL=1
//Support for full template specialization syntax
VTK_COMPILER_HAS_FULL_SPECIALIZATION:INTERNAL=1
//Test VTK_CONST_REVERSE_ITERATOR_COMPARISON
VTK_CONST_REVERSE_ITERATOR_COMPARISON:INTERNAL=1
//ADVANCED property for variable: VTK_DATA_ROOT
VTK_DATA_ROOT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_DEBUG_LEAKS
VTK_DEBUG_LEAKS-ADVANCED:INTERNAL=1
//The directory in which code for Shaders is provided.
VTK_DEFAULT_SHADERS_DIR:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/VTK/Utilities/MaterialLibrary/Repository
VTK_DIR:INTERNAL=/scratch/scratchdirs/acbauer/paraview-build/VTK
//Support for C++ explict templates
VTK_EXPLICIT_TEMPLATES:INTERNAL=1
//ADVANCED property for variable: VTK_GLEXT_FILE
VTK_GLEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_GLXEXT_FILE
VTK_GLXEXT_FILE-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS:INTERNAL=TRUE
//OpenGL includes used to test glXGetProcAddressARB prototype.
VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS_INCLUDES:INTERNAL=/usr/include
//Already set VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS
VTK_GLX_GET_PROC_ADDRESS_ARB_PROTOTYPE_EXISTS_TESTED:INTERNAL=1
//Have symbol feenableexcept
VTK_HAS_FEENABLEEXCEPT:INTERNAL=1
//Have symbol isinf
VTK_HAS_ISINF:INTERNAL=
//Have symbol isnan
VTK_HAS_ISNAN:INTERNAL=
//Have symbol _isnan
VTK_HAS__ISNAN:INTERNAL=
//Have include iosfwd
VTK_HAVE_ANSI_STREAMS:INTERNAL=1
//Support for getsockname with socklen_t
VTK_HAVE_GETSOCKNAME_WITH_SOCKLEN_T:INTERNAL=1
//Have library socket
VTK_HAVE_LIBSOCKET:INTERNAL=
//Have include iostream.h
VTK_HAVE_OLD_STREAMS:INTERNAL=
//Have symbol SO_REUSEADDR
VTK_HAVE_SO_REUSEADDR:INTERNAL=1
//For __sync atomic builtins.
VTK_HAVE_SYNC_BUILTINS:INTERNAL=1
//ADVANCED property for variable: VTK_IGNORE_BTX
VTK_IGNORE_BTX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_INSTALL_THIRD_PARTY_LIBRARIES
VTK_INSTALL_THIRD_PARTY_LIBRARIES-ADVANCED:INTERNAL=1
//Whether istream supports long long
VTK_ISTREAM_SUPPORTS_LONG_LONG:INTERNAL=1
//ADVANCED property for variable: VTK_LARGE_DATA_ROOT
VTK_LARGE_DATA_ROOT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_REMOVE
VTK_LEGACY_REMOVE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_SILENT
VTK_LEGACY_SILENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MATERIALS_DIRS
VTK_MATERIALS_DIRS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MAX_THREADS
VTK_MAX_THREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPIRUN_EXE
VTK_MPIRUN_EXE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_MAX_NUMPROCS
VTK_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_NUMPROC_FLAG
VTK_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_POSTFLAGS
VTK_MPI_POSTFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_PREFLAGS
VTK_MPI_PREFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_PRENUMPROC_FLAGS
VTK_MPI_PRENUMPROC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_NO_PYTHON_THREADS
VTK_NO_PYTHON_THREADS-ADVANCED:INTERNAL=1
//Disable multithreading support in the Python bindings
VTK_NO_PYTHON_THREADS:INTERNAL=1
//ADVANCED property for variable: VTK_OPENGL_HAS_OSMESA
VTK_OPENGL_HAS_OSMESA-ADVANCED:INTERNAL=1
//MODIFIED property for variable: VTK_OPENGL_HAS_OSMESA
VTK_OPENGL_HAS_OSMESA-MODIFIED:INTERNAL=ON
//Whether ostream supports long long
VTK_OSTREAM_SUPPORTS_LONG_LONG:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(long long)
VTK_SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: __int64 unknown
VTK_SIZEOF___INT64:INTERNAL=
VTK_TCL_TK_STATIC:INTERNAL=ON
//ADVANCED property for variable: VTK_TESTING_LOCALE
VTK_TESTING_LOCALE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_TESTING_USE_FPE
VTK_TESTING_USE_FPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_TESTING_USE_LOCALE
VTK_TESTING_USE_LOCALE-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
VTK_TEST_SYNC_BUILTINS_COMPILED:INTERNAL=TRUE
//Whether char is signed.
VTK_TYPE_CHAR_IS_SIGNED:INTERNAL=1
//Result of TRY_COMPILE
VTK_TYPE_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE
//CHECK_TYPE_SIZE: sizeof(uintptr_t)
VTK_UINTPTR_T:INTERNAL=8
//ADVANCED property for variable: VTK_USE_64BIT_IDS
VTK_USE_64BIT_IDS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_BOOST
VTK_USE_BOOST-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_CG_SHADERS
VTK_USE_CG_SHADERS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_CHARTS
VTK_USE_CHARTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_DISPLAY
VTK_USE_DISPLAY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_FFMPEG_ENCODER
VTK_USE_FFMPEG_ENCODER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_GCC_VISIBILITY
VTK_USE_GCC_VISIBILITY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_GEOVIS
VTK_USE_GEOVIS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_GL2PS
VTK_USE_GL2PS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_GLSL_SHADERS
VTK_USE_GLSL_SHADERS-ADVANCED:INTERNAL=1
//Have function glXGetProcAddressARB
VTK_USE_GLX_GET_PROC_ADDRESS_ARB:INTERNAL=1
//ADVANCED property for variable: VTK_USE_GNU_R
VTK_USE_GNU_R-ADVANCED:INTERNAL=1
//Use Gnu R interface for VTK.  Requires Gnu R installation.
VTK_USE_GNU_R:INTERNAL=OFF
//ADVANCED property for variable: VTK_USE_GUISUPPORT
VTK_USE_GUISUPPORT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_INFOVIS
VTK_USE_INFOVIS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_MANGLED_MESA
VTK_USE_MANGLED_MESA-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_MATLAB_MEX
VTK_USE_MATLAB_MEX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_MATROX_IMAGING
VTK_USE_MATROX_IMAGING-ADVANCED:INTERNAL=1
//Use Matrox Imaging Library for video input.
VTK_USE_MATROX_IMAGING:INTERNAL=OFF
//ADVANCED property for variable: VTK_USE_METAIO
VTK_USE_METAIO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_MPEG2_ENCODER
VTK_USE_MPEG2_ENCODER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_MPI
VTK_USE_MPI-ADVANCED:INTERNAL=0
//Build VTK with MPI support
VTK_USE_MPI:INTERNAL=ON
//ADVANCED property for variable: VTK_USE_MYSQL
VTK_USE_MYSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_NVCONTROL
VTK_USE_NVCONTROL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_N_WAY_ARRAYS
VTK_USE_N_WAY_ARRAYS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_ODBC
VTK_USE_ODBC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_OFFSCREEN
VTK_USE_OFFSCREEN-ADVANCED:INTERNAL=1
//MODIFIED property for variable: VTK_USE_OFFSCREEN
VTK_USE_OFFSCREEN-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: VTK_USE_OGGTHEORA_ENCODER
VTK_USE_OGGTHEORA_ENCODER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_POSTGRES
VTK_USE_POSTGRES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_QT
VTK_USE_QT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_QTCHARTS
VTK_USE_QTCHARTS-ADVANCED:INTERNAL=1
//Build QVTK widget and plugin for Qt
VTK_USE_QVTK:INTERNAL=OFF
//ADVANCED property for variable: VTK_USE_QVTK_QTOPENGL
VTK_USE_QVTK_QTOPENGL-ADVANCED:INTERNAL=1
//Use QtOpenGL in QVTK
VTK_USE_QVTK_QTOPENGL:INTERNAL=OFF
//Build the vtkRendering kit.  Needed for displaying data or using
// widgets.
VTK_USE_RENDERING:INTERNAL=ON
//ADVANCED property for variable: VTK_USE_SYSTEM_EXPAT
VTK_USE_SYSTEM_EXPAT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_FREETYPE
VTK_USE_SYSTEM_FREETYPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_HDF5
VTK_USE_SYSTEM_HDF5-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_JPEG
VTK_USE_SYSTEM_JPEG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBPROJ4
VTK_USE_SYSTEM_LIBPROJ4-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBXML2
VTK_USE_SYSTEM_LIBXML2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PNG
VTK_USE_SYSTEM_PNG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_TIFF
VTK_USE_SYSTEM_TIFF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_ZLIB
VTK_USE_SYSTEM_ZLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TDX
VTK_USE_TDX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TEXT_ANALYSIS
VTK_USE_TEXT_ANALYSIS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TK
VTK_USE_TK-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_VIEWS
VTK_USE_VIEWS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_VOLUMEPRO_1000
VTK_USE_VOLUMEPRO_1000-ADVANCED:INTERNAL=1
//MODIFIED property for variable: VTK_USE_X
VTK_USE_X-MODIFIED:INTERNAL=ON
//ADVANCED property for variable: VTK_WGLEXT_FILE
VTK_WGLEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_HINTS
VTK_WRAP_HINTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_JAVA
VTK_WRAP_JAVA-ADVANCED:INTERNAL=1
//Wrap VTK classes into the Python language.
VTK_WRAP_PYTHON:INTERNAL=ON
//Wrap VTK classes into the TCL language.
VTK_WRAP_TCL:INTERNAL=OFF
//ADVANCED property for variable: X11_ICE_INCLUDE_PATH
X11_ICE_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_ICE_LIB
X11_ICE_LIB-ADVANCED:INTERNAL=1
//Have library /usr/lib64/libX11.so;/usr/lib64/libXext.so
X11_LIB_X11_SOLO:INTERNAL=1
//ADVANCED property for variable: X11_SM_INCLUDE_PATH
X11_SM_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_SM_LIB
X11_SM_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_X11_INCLUDE_PATH
X11_X11_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_X11_LIB
X11_X11_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XRes_INCLUDE_PATH
X11_XRes_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XRes_LIB
X11_XRes_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XShm_INCLUDE_PATH
X11_XShm_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XSync_INCLUDE_PATH
X11_XSync_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XTest_INCLUDE_PATH
X11_XTest_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_XTest_LIB
X11_XTest_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xaccessrules_INCLUDE_PATH
X11_Xaccessrules_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xaccessstr_INCLUDE_PATH
X11_Xaccessstr_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xau_INCLUDE_PATH
X11_Xau_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xau_LIB
X11_Xau_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcomposite_INCLUDE_PATH
X11_Xcomposite_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcomposite_LIB
X11_Xcomposite_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcursor_INCLUDE_PATH
X11_Xcursor_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xcursor_LIB
X11_Xcursor_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdamage_INCLUDE_PATH
X11_Xdamage_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdamage_LIB
X11_Xdamage_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdmcp_INCLUDE_PATH
X11_Xdmcp_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xdmcp_LIB
X11_Xdmcp_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xext_LIB
X11_Xext_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xfixes_INCLUDE_PATH
X11_Xfixes_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xfixes_LIB
X11_Xfixes_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xft_INCLUDE_PATH
X11_Xft_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xft_LIB
X11_Xft_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xi_INCLUDE_PATH
X11_Xi_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xi_LIB
X11_Xi_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinerama_INCLUDE_PATH
X11_Xinerama_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinerama_LIB
X11_Xinerama_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinput_INCLUDE_PATH
X11_Xinput_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xinput_LIB
X11_Xinput_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkb_INCLUDE_PATH
X11_Xkb_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkbfile_INCLUDE_PATH
X11_Xkbfile_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkbfile_LIB
X11_Xkbfile_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xkblib_INCLUDE_PATH
X11_Xkblib_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xlib_INCLUDE_PATH
X11_Xlib_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xmu_INCLUDE_PATH
X11_Xmu_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xmu_LIB
X11_Xmu_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xpm_INCLUDE_PATH
X11_Xpm_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xpm_LIB
X11_Xpm_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrandr_INCLUDE_PATH
X11_Xrandr_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrandr_LIB
X11_Xrandr_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrender_INCLUDE_PATH
X11_Xrender_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xrender_LIB
X11_Xrender_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xscreensaver_INCLUDE_PATH
X11_Xscreensaver_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xscreensaver_LIB
X11_Xscreensaver_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xshape_INCLUDE_PATH
X11_Xshape_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xt_INCLUDE_PATH
X11_Xt_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xt_LIB
X11_Xt_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xutil_INCLUDE_PATH
X11_Xutil_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xv_INCLUDE_PATH
X11_Xv_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xv_LIB
X11_Xv_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xxf86misc_LIB
X11_Xxf86misc_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_Xxf86vm_LIB
X11_Xxf86vm_LIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_dpms_INCLUDE_PATH
X11_dpms_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_xf86misc_INCLUDE_PATH
X11_xf86misc_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: X11_xf86vmode_INCLUDE_PATH
X11_xf86vmode_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_BUILD_UTILS
XDMF_BUILD_UTILS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAS_NDGM
XDMF_HAS_NDGM-ADVANCED:INTERNAL=1
//Whether streams support 64-bit types
XDMF_HAVE_64BIT_STREAMS:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_FCNTL
XDMF_HAVE_FCNTL-ADVANCED:INTERNAL=1
//Have include malloc.h
XDMF_HAVE_MALLOC_H:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_MMAN
XDMF_HAVE_MMAN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_NETINET
XDMF_HAVE_NETINET-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_REGENERATE_WRAPPERS
XDMF_REGENERATE_WRAPPERS-ADVANCED:INTERNAL=1
//Regenerate XdmfPython.cxx
XDMF_REGENERATE_WRAPPERS:INTERNAL=OFF
//ADVANCED property for variable: XDMF_REGENERATE_YACCLEX
XDMF_REGENERATE_YACCLEX-ADVANCED:INTERNAL=1
//Regenerate XdmfExprYacc.cxx and XdmfExprLex.cxx
XDMF_REGENERATE_YACCLEX:INTERNAL=OFF
//ADVANCED property for variable: XDMF_USE_BZIP2
XDMF_USE_BZIP2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_USE_GZIP
XDMF_USE_GZIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_USE_MYSQL
XDMF_USE_MYSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_WRAP_CSHARP
XDMF_WRAP_CSHARP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_WRAP_PYTHON
XDMF_WRAP_PYTHON-ADVANCED:INTERNAL=1
//Build a Python wrapping interface
XDMF_WRAP_PYTHON:INTERNAL=OFF
XDMF_WRAP_TCL:INTERNAL=OFF
//ADVANCED property for variable: ZLIB_INCLUDE_DIR
ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ZLIB_LIBRARY
ZLIB_LIBRARY-ADVANCED:INTERNAL=1
//Have function _isinf
float.h:INTERNAL=


From utkarsh.ayachit at kitware.com  Tue Jul  1 09:14:02 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 1 Jul 2014 09:14:02 -0400
Subject: [Paraview] calculate total sum of a variable in CTH data
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED8F@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED7F@umechp9h.easf.csd.disa.mil>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED8F@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjD7DzxS3GBPHOiOx3_3z+TtceviJMuWcxw1NQgTggkiEQ@mail.gmail.com>

Simon,

Use the following for your main body. Also note, for AMR datasets, the
scalars are available cell data, not point data.


-----------------------------------------------------------------------------------
if input.IsA("vtkUniformGridAMR"):
    # This initializes AMR properly. It will share the dataset instances
    # but we will clone those later.
    output.ShallowCopy(input)

    iter = input.NewIterator()
    iter.UnRegister(None)
    iter.InitTraversal()
    while not iter.IsDoneWithTraversal():
        curInput = iter.GetCurrentDataObject()
        curOutput = curInput.NewInstance()
        calculateSum(curInput, curOutput)
        output.SetDataSet(iter, curOutput)
        curOutput.UnRegister(None)
        iter.GoToNextItem();
else:
    calculateSum(input, output)
-----------------------------------------------------------------------------------

On Tue, Jul 1, 2014 at 8:40 AM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
>
> Hello,
>
> I am trying to simply add up all the values of a variable in the CTH dataset
> using programmable filter with the python code at the end of this email..
>
> The code seems to be working for the other dataset that I worked in the
> past. But for CTH dataset, it is giving me an error with GetCellData
>
> Traceback (most recent call last):
>
> File "<string>", line 22, in <module>
>
> File "<string>", line 43, in RequestData
>
> File "<string>", line 8, in calculateSum
>
> AttributeError: GetCellData
>
>
> When I printed the output for CTH dataset it is giving me
>
> vtkNonOverlappingAMR (0x7f96ca7675c0)
>
> Debug: Off
>
> Modified Time: 860345754
>
> Reference Count: 2
>
> Registered Events: (none)
>
> Information: 0x7f96ca767040
>
> Data Released: False
>
> Global Release Data: Off
>
> UpdateTime: 856914636
>
> Field Data:
>
> Debug: Off
>
> Modified Time: 855459763
>
> Reference Count: 1
>
> Registered Events: (none)
>
> Number Of Arrays: 4
>
> Array 0 name = GlobalBounds
>
> Array 1 name = GlobalBoxSize
>
> Array 2 name = MinLevel
>
> Array 3 name = MinLevelSpacing
>
> Number Of Components: 4
>
> Number Of Tuples: 6
>
>
> Any help is in adding a variable in a CTH dataset is much appreciated.
>
> thank you
> -simon
>
> p/s: sorry for the other unfinished email sent....
>
>
>
> =========================================
> def calculateSum(input, output):
>     # Copy the cells etc.
>     output.ShallowCopy(input)
>
>     # Get the array to calculate the coefficient
>     toSum = output.GetPointData().GetArray("MOMENT_X")
>
>     # for each of the elements, calculate the three roots and store the real
> and imaginary output in separate arrays
>     numPoints = toSum.GetSize()
>
>     # create the output arrays
>     sum = vtk.vtkDoubleArray()
>     sum.SetNumberOfValues(numPoints)
>     sum.SetName("sum")
>     tsum = 0
>
>     for i in range(0, numPoints):
>         tsum = tsum + toSum.GetValue(i)
>
>     for j in range(0, numPoints):
>         sum.SetValue(j, tsum)
>
>     output.GetPointData().AddArray(sum)
>
> input = self.GetInputDataObject(0, 0)
> output = self.GetOutputDataObject(0)
>
> if input.IsA("vtkMultiBlockDataSet"):
>     output.CopyStructure(input)
>     iter = input.NewIterator()
>     iter.UnRegister(None)
>     iter.InitTraversal()
>     while not iter.IsDoneWithTraversal():
>         curInput = iter.GetCurrentDataObject()
>         curOutput = curInput.NewInstance()
>         curOutput.UnRegister(None)
>         output.SetDataSet(iter, curOutput)
>         calculateSum(curInput, curOutput)
>         iter.GoToNextItem();
> else:
>     calculateSum(input, output)
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

From simon.m.su.ctr at mail.mil  Tue Jul  1 09:24:17 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Tue, 1 Jul 2014 13:24:17 +0000
Subject: [Paraview] calculate total sum of a variable in CTH data
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjD7DzxS3GBPHOiOx3_3z+TtceviJMuWcxw1NQgTggkiEQ@mail.gmail.com>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED7F@umechp9h.easf.csd.disa.mil>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101ED8F@umechp9h.easf.csd.disa.mil>
 <CADHSJjD7DzxS3GBPHOiOx3_3z+TtceviJMuWcxw1NQgTggkiEQ@mail.gmail.com>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101EDD3@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hi Utkrash,

Thanks
-simon

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Tuesday, July 01, 2014 9:14 AM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] calculate total sum of a variable in CTH data

Simon,

Use the following for your main body. Also note, for AMR datasets, the scalars 
are available cell data, not point data.


-----------------------------------------------------------------------------------
if input.IsA("vtkUniformGridAMR"):
    # This initializes AMR properly. It will share the dataset instances
    # but we will clone those later.
    output.ShallowCopy(input)

    iter = input.NewIterator()
    iter.UnRegister(None)
    iter.InitTraversal()
    while not iter.IsDoneWithTraversal():
        curInput = iter.GetCurrentDataObject()
        curOutput = curInput.NewInstance()
        calculateSum(curInput, curOutput)
        output.SetDataSet(iter, curOutput)
        curOutput.UnRegister(None)
        iter.GoToNextItem();
else:
    calculateSum(input, output)
-----------------------------------------------------------------------------------

On Tue, Jul 1, 2014 at 8:40 AM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:
>
> Hello,
>
> I am trying to simply add up all the values of a variable in the CTH
> dataset using programmable filter with the python code at the end of this 
> email..
>
> The code seems to be working for the other dataset that I worked in
> the past. But for CTH dataset, it is giving me an error with
> GetCellData
>
> Traceback (most recent call last):
>
> File "<string>", line 22, in <module>
>
> File "<string>", line 43, in RequestData
>
> File "<string>", line 8, in calculateSum
>
> AttributeError: GetCellData
>
>
> When I printed the output for CTH dataset it is giving me
>
> vtkNonOverlappingAMR (0x7f96ca7675c0)
>
> Debug: Off
>
> Modified Time: 860345754
>
> Reference Count: 2
>
> Registered Events: (none)
>
> Information: 0x7f96ca767040
>
> Data Released: False
>
> Global Release Data: Off
>
> UpdateTime: 856914636
>
> Field Data:
>
> Debug: Off
>
> Modified Time: 855459763
>
> Reference Count: 1
>
> Registered Events: (none)
>
> Number Of Arrays: 4
>
> Array 0 name = GlobalBounds
>
> Array 1 name = GlobalBoxSize
>
> Array 2 name = MinLevel
>
> Array 3 name = MinLevelSpacing
>
> Number Of Components: 4
>
> Number Of Tuples: 6
>
>
> Any help is in adding a variable in a CTH dataset is much appreciated.
>
> thank you
> -simon
>
> p/s: sorry for the other unfinished email sent....
>
>
>
> =========================================
> def calculateSum(input, output):
>     # Copy the cells etc.
>     output.ShallowCopy(input)
>
>     # Get the array to calculate the coefficient
>     toSum = output.GetPointData().GetArray("MOMENT_X")
>
>     # for each of the elements, calculate the three roots and store
> the real and imaginary output in separate arrays
>     numPoints = toSum.GetSize()
>
>     # create the output arrays
>     sum = vtk.vtkDoubleArray()
>     sum.SetNumberOfValues(numPoints)
>     sum.SetName("sum")
>     tsum = 0
>
>     for i in range(0, numPoints):
>         tsum = tsum + toSum.GetValue(i)
>
>     for j in range(0, numPoints):
>         sum.SetValue(j, tsum)
>
>     output.GetPointData().AddArray(sum)
>
> input = self.GetInputDataObject(0, 0)
> output = self.GetOutputDataObject(0)
>
> if input.IsA("vtkMultiBlockDataSet"):
>     output.CopyStructure(input)
>     iter = input.NewIterator()
>     iter.UnRegister(None)
>     iter.InitTraversal()
>     while not iter.IsDoneWithTraversal():
>         curInput = iter.GetCurrentDataObject()
>         curOutput = curInput.NewInstance()
>         curOutput.UnRegister(None)
>         output.SetDataSet(iter, curOutput)
>         calculateSum(curInput, curOutput)
>         iter.GoToNextItem();
> else:
>     calculateSum(input, output)
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/0f99ea4e/attachment.bin>

From berk.geveci at kitware.com  Tue Jul  1 10:46:35 2014
From: berk.geveci at kitware.com (Berk Geveci)
Date: Tue, 1 Jul 2014 10:46:35 -0400
Subject: [Paraview] TemporalParticlesToPathlines filter missing scalar
In-Reply-To: <53B22F78.7060505@indiana.edu>
References: <53B22F78.7060505@indiana.edu>
Message-ID: <CAE32kpWHkHd9oL4qgJPS97X8p5019Y+ZhEuM6Hz4=4CXc2_CNA@mail.gmail.com>

Sounds like a bug. Do you have data/pipeline to reproduce it?

-berk


On Mon, Jun 30, 2014 at 11:48 PM, Bill Sherman <shermanw at indiana.edu> wrote:

> Hello,
>
> I am confused by something that the TemporalParticlesToPathlines
> filter seems to be doing.  It seems to be deleting or replacing
> one of the scalar fields in the "Pathlines" output.
>
> I have a rather simple pipeline:
>
>    Data
>    TemporalInterpolator
>    TemporalParticlesToPathlines
>       Pathlines
>         Tube
>       Particles
>         Glyph
>
> So the data has a handful of scalar values:
>    * density
>    * id
>    * mass
>    * type
>    * velocity (okay, not a scalar)
>    * vphi
>
> And all the filters offer these as available to color the data
> by -- except!  Except under the Pathlines (and Tube), the "mass"
> data is replaced by "TrailId".
>
> Of course, I'm trying to color the pathlines by the value of the
> particle "mass", so this is a problem for me.
>
> And I'm using the "id" field to make sure the particles are properly
> associated with their past selves in the "TemporalParticlesToPathlines"
> filter.
>
> Any thoughts?  Didn't find anything via Google (though I limited the
> search to the past year).
>
> Oh, and I tried this both with ParaView versions 4.0.1 and 4.1.0.
>
>         Thank you,
>         Bill
>
> --
> Bill Sherman
> Sr. Technology Advisor
> Advanced Visualization Lab
> Pervasive Technology Inst
> Indiana University
> shermanw at indiana.edu
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/a1374d00/attachment.html>

From michael.tum.92 at gmail.com  Tue Jul  1 11:19:31 2014
From: michael.tum.92 at gmail.com (Mich Aelo)
Date: Tue, 1 Jul 2014 17:19:31 +0200
Subject: [Paraview] adding components to existing array using Phython
	Programable Filter
Message-ID: <CAFSM0o9=9XMmZ1WVeiDGeyZFkA2r7LQfR4V7QoBJjEwL6ZJymA@mail.gmail.com>

Hello,

I am new to Paraview as well as Phython.
Currently I am working on some tensor representation issues.

Right now, I am dealing with a symetric tensor dataset. As the the tensor
is symetric only 6 values are stored in the data array.
Some filters I would like to apply, however, demand input arrays with 9
components.
So my guess was, it would be easiest to use "Phyton Programmabe Filter" and
add the missing entries.

Here is what i tried after viewing some examples on the paraview-wiki:

//////////////////////////////////////////////////////////////////////////////////
from paraview import numpy_support as NS
import numpy as N
pdi = self.GetInputDataObject(0,0)
pdo = self.GetOutputDataObject(0)
pdo.ShallowCopy(pdi)

import math

m = pdi.GetPointData().GetArray('tensor6_array')
m2 = N.mat([[m.GetValue(0), m.GetValue(1), m.GetValue(2)], [m.GetValue(1),
m.GetValue(3), m.GetValue(4)], [m.GetValue(2), m.GetValue(4),
m.GetValue(5)]])


m3 = NS.numpy_to_vtk(m2)
m3.SetName('tensor9_array')
pdo.GetPointData().AddArray(m3)
//////////////////////////////////////////////////////////////////////////////////

This however results in a 3 component array, with only zeros in it.

Its quite clear to me, that there must be some fundamental mistake in it,
and would be very gratefull if someone could point it out to me!

Regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/739e40e2/attachment-0001.html>

From kmorel at sandia.gov  Tue Jul  1 12:08:51 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 1 Jul 2014 16:08:51 +0000
Subject: [Paraview] Rendering in parallel
In-Reply-To: <CAAPOYrF8LnNZ9UOxXeoiDyqKaKmqqv80+rPiLEwPfERCq1hSyg@mail.gmail.com>
Message-ID: <CFD837C8.19494%kmorel@sandia.gov>

To check the distribution of the data, use the Process Id Scalars filters. That should color the data based on which processor it is located.

It might help if you described your system more completely. What kind of data are you loading? Is it image data? Polygon data? AMR? An unstructured grid? Are you applying any filters? How are you rendering it? Is it surface or volume rendering? Is there any transparency? Can you send a picture? What kind of parallel computer are you using? Are you running ParaView on your desktop in multi-core mode (I think rendering actually serializes in that case because you still have only one GPU.), or are you connecting to a cluster? How many nodes on your cluster and how are they configured?

-Ken

From: J?r?my Santina <jeremy.santina at gmail.com<mailto:jeremy.santina at gmail.com>>
Date: Tuesday, July 1, 2014 2:31 AM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel

Actually, I did try the D3 filter but I didn't really see any better results. Maybe it is because I don't know how to configure it. How does D3 filter work ?



2014-06-30 16:21 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>:
Jeremy,

Like the other parallel processing in ParaView, the efficiency is dictated by the distribution of the data. If your data distribution is highly imbalanced such as when all the data is on one process as in your case, then all the processing will happen where the data is and the rest of the processors will remain idle.

You could try running the D3 filter. That should redistribute the point data more evenly.

-Ken

From: J?r?my Santina <jeremy.santina at gmail.com<mailto:jeremy.santina at gmail.com>>
Date: Monday, June 30, 2014 2:55 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Rendering in parallel

Good morning,

I am a novice user of Paraview and there are some aspects which I am not familiar with. Here is one of the issues I am having :

I run Paraview in Client-Server mode, performing the data processing and the rendering on the remote server, and I read a Tecplot Binary File (.plt) composed of more than 30 millions of points. This take a lot of time. An idea to speed up the calculation is to launch the server in parallel. I know that many readers can not read in parallel (it is the case of TecplotBinaryFileReader I think) so I don't expect any improvment in this way.

But, examining the Timer Log, I noticed that it doesn't speed up the rendering either. I tested many times displaying the points and both experiment with parallelism and without gave the same results (about 40-50 sec). I don't understand why.

Do I misinterpret the Timer Log ? Is the time of rendering long enough to conclude ? Do I have to set specific parameters to make it works ?

I thank you in advance for your help.

J?r?my

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/fc4110e1/attachment.html>

From shermanw at indiana.edu  Tue Jul  1 12:54:11 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Tue, 01 Jul 2014 12:54:11 -0400
Subject: [Paraview] TemporalParticlesToPathlines filter missing scalar
In-Reply-To: <CAE32kpWHkHd9oL4qgJPS97X8p5019Y+ZhEuM6Hz4=4CXc2_CNA@mail.gmail.com>
References: <53B22F78.7060505@indiana.edu>
 <CAE32kpWHkHd9oL4qgJPS97X8p5019Y+ZhEuM6Hz4=4CXc2_CNA@mail.gmail.com>
Message-ID: <53B2E7B3.5090300@indiana.edu>

On 07/01/2014 10:46 AM, Berk Geveci wrote:
> Sounds like a bug. Do you have data/pipeline to reproduce it?

Sure.  I put a tar file at:
	http://iq-station.org/downloads/Part2Path_debug.tar.gz

I included the first 9 steps of the data.

> -berk

	Thanks,
	Bill

>
>
> On Mon, Jun 30, 2014 at 11:48 PM, Bill Sherman <shermanw at indiana.edu
> <mailto:shermanw at indiana.edu>> wrote:
>
>     Hello,
>
>     I am confused by something that the TemporalParticlesToPathlines
>     filter seems to be doing. It seems to be deleting or replacing
>     one of the scalar fields in the "Pathlines" output.
>
>     I have a rather simple pipeline:
>
>     Data
>     TemporalInterpolator
>     TemporalParticlesToPathlines
>     Pathlines
>     Tube
>     Particles
>     Glyph
>
>     So the data has a handful of scalar values:
>     * density
>     * id
>     * mass
>     * type
>     * velocity (okay, not a scalar)
>     * vphi
>
>     And all the filters offer these as available to color the data
>     by -- except! Except under the Pathlines (and Tube), the "mass"
>     data is replaced by "TrailId".
>
>     Of course, I'm trying to color the pathlines by the value of the
>     particle "mass", so this is a problem for me.
>
>     And I'm using the "id" field to make sure the particles are properly
>     associated with their past selves in the "TemporalParticlesToPathlines"
>     filter.
>
>     Any thoughts? Didn't find anything via Google (though I limited the
>     search to the past year).
>
>     Oh, and I tried this both with ParaView versions 4.0.1 and 4.1.0.
>
>     Thank you,
>     Bill
>
>     --
>     Bill Sherman
>     Sr. Technology Advisor
>     Advanced Visualization Lab
>     Pervasive Technology Inst
>     Indiana University
>     shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>     _________________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/__opensource/opensource.html
>     <http://www.kitware.com/opensource/opensource.html>
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/__ParaView <http://paraview.org/Wiki/ParaView>
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/__mailman/listinfo/paraview
>     <http://public.kitware.com/mailman/listinfo/paraview>
>
>


From wascott at sandia.gov  Tue Jul  1 13:09:44 2014
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 1 Jul 2014 17:09:44 +0000
Subject: [Paraview] Color legend and log scaling
Message-ID: <9047EE0D4D3C8E43B93980DA10A073809C30DC12@EXMB04.srn.sandia.gov>

I would like to propose a few changes in our log scaling algorithm for painting a dataset by a variable.   I discussed this with Utkarsh, and he asked that I bounce it off the e-mail list.  So, here goes.

Currently, when a user log scales a variable, if all data is positive, ParaView just uses the normal min and max.  There are times when this is not proper - for instance when looking at the temperature or density of material in a supernova, or velocity of outbound gas.  Another example is large data, with noise around zero.  I would like to propose that we have a user selectable option to set the minimum at maximum*10^-q, where q is user defined but defaults to 4.  In other words, the minimum would be set to 1*10^-4 of what the maximum is.

If all of the user's data is negative, ParaView grumbles, and then seg faults using a current master git pull - not optimal behavior.  In PV 4.1, it just sets min and max to 0.  I would like to propose that ParaView calculate the log of the data, as follows:  Index= -(log(abs(Var))).  Then, just draw the color legend as normal - for instance, red at top, white in the middle and blue at bottom.  Tick marks will be the reverse of positive log scaling - with the dense numbers, more negative numbers at the bottom and less dense, less negative numbers at the top.

The problem arises with data that spans positive and negative numbers.  Since the log of 0 is infinity, we have to deal with very small numbers in a special way.  I propose that we find maxVal = max(maximum, abs(minimum)).  Then, we set the color bar to run from maxVal to -maxVal.  We log scale the top half of the color legend, running from maxVal to maxVal*10^-4, and we reverse log scale the bottom half of the color legend, running from -maxVal*10^-4 to -maxVal.  We calculate this negative range the same as the all negative data section above.  All data between maxVal*10^-4 and -maxVal*10^-4 would remain white by default, or user selectable black.

User selectable functionality would be as follows:
*       to allow/ not allow negative numbers (default allow)
*       to be able to change the q exponent (i.e., 4 above) (default 4)
*       to be able to change the painting color that is too small (default white)
*       to clamp minimum to some number (such as q == 4 above).  (default on).

Thoughts?

Alan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/021ecf10/attachment.html>

From samuelkey at bresnan.net  Tue Jul  1 15:51:56 2014
From: samuelkey at bresnan.net (Samuel Key)
Date: Tue, 01 Jul 2014 13:51:56 -0600
Subject: [Paraview] Color legend and log scaling
In-Reply-To: <9047EE0D4D3C8E43B93980DA10A073809C30DC12@EXMB04.srn.sandia.gov>
References: <9047EE0D4D3C8E43B93980DA10A073809C30DC12@EXMB04.srn.sandia.gov>
Message-ID: <53B3115C.7010308@bresnan.net>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140701/70f6b3e4/attachment-0001.html>

From david.thompson at kitware.com  Tue Jul  1 17:44:06 2014
From: david.thompson at kitware.com (David Thompson)
Date: Tue, 1 Jul 2014 17:44:06 -0400
Subject: [Paraview] Color legend and log scaling
In-Reply-To: <9047EE0D4D3C8E43B93980DA10A073809C30DC12@EXMB04.srn.sandia.gov>
References: <9047EE0D4D3C8E43B93980DA10A073809C30DC12@EXMB04.srn.sandia.gov>
Message-ID: <3938F2CD-CE84-4DAA-B8DC-856194627805@kitware.com>

Hi Alan,

> I would like to propose a few changes in our log scaling algorithm for painting a dataset by a variable.   I discussed this with Utkarsh, and he asked that I bounce it off the e-mail list.  So, here goes.
>  
> Currently, when a user log scales a variable, if all data is positive, ParaView just uses the normal min and max.  There are times when this is not proper ? for instance when looking at the temperature or density of material in a supernova, or velocity of outbound gas.  Another example is large data, with noise around zero.  I would like to propose that we have a user selectable option to set the minimum at maximum*10^-q, where q is user defined but defaults to 4.  In other words, the minimum would be set to 1*10^-4 of what the maximum is.

Avoiding a "window" around 0 in the initial view sounds good to me. However, I can imagine some cases where the data spans more than 4 orders of magnitude. One thing I've seen (debatably bad, but something ParaView must deal with) are simulations/datasets that use large numbers (i.e., 1e+38) to mark invalid values. (The LDAV climate data does this.) Showing a plot with the initial view set to [1e34,1e38] would not be useful, since it would only show invalid values. Another is chemical reaction simulations where concentrations span much more than 4 orders of magnitude (I've seen some span 11 or 12 orders of magnitude, but 5 or 6 can be common).

What choosing q to ensure that a significant fraction (say 90%?) of the data is actually on-screen? It not terribly hard (even in parallel) to extract a fixed-size sample that approximates a histogram to within a few percent. We could use that to determine where the bulk of the data resided and ensure that the q-value does not leave more than 10% offscreen.

> If all of the user?s data is negative, ParaView grumbles, and then seg faults using a current master git pull ? not optimal behavior.  In PV 4.1, it just sets min and max to 0.  I would like to propose that ParaView calculate the log of the data, as follows:  Index= -(log(abs(Var))).  Then, just draw the color legend as normal ? for instance, red at top, white in the middle and blue at bottom.  Tick marks will be the reverse of positive log scaling ? with the dense numbers, more negative numbers at the bottom and less dense, less negative numbers at the top.

I'm not sure I understand this, especially your use of "dense". It sounds like you have a particular dataset in mind where the probability density is low near zero. Are you saying you want the color scale to be different in the case of data that is all negative numbers? Or that log plots in general should have colors reversed?

> The problem arises with data that spans positive and negative numbers.  Since the log of 0 is infinity, we have to deal with very small numbers in a special way.  I propose that we find maxVal = max(maximum, abs(minimum)).  Then, we set the color bar to run from maxVal to ?maxVal.  We log scale the top half of the color legend, running from maxVal to maxVal*10^-4, and we reverse log scale the bottom half of the color legend, running from ?maxVal*10^-4 to ?maxVal.  We calculate this negative range the same as the all negative data section above.  All data between maxVal*10^-4 and -maxVal*10^-4 would remain white by default, or user selectable black.

I like the idea of having a custom color for the range [-10^q,10^q] and I think I understand and agree with the simplified bounds/ticks for the case where the data crosses zero -- at least when it firmly crosses the origin. However, whose chemistry simulations I mentioned above would occasionally have very slightly negative concentrations. Physically they can never be negative but floating-point precision meant that some were. In this case, we might have a distribution of concentrations that went from -1e-16 to 1 with the bulk in the range [1e-10,1]. Using the algorithm above for the axes would assign half of the color palette to the range [-1,-1e-4], half to [1e-4,1] and draw a significant fraction of the data as "black". If instead the histogram was used to choose q, then we might be able to decide that all of the "naughty" data were outliers and select a log color-scale of [1e-10,1].

	David

> User selectable functionality would be as follows:
> 	? to allow/ not allow negative numbers (default allow)
> 	? to be able to change the q exponent (i.e., 4 above) (default 4)
> 	? to be able to change the painting color that is too small (default white)
> 	? to clamp minimum to some number (such as q == 4 above).  (default on).
>  
> Thoughts?
>  
> Alan
>  
>  
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects athttp://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://public.kitware.com/mailman/listinfo/paraview


From wascott at sandia.gov  Tue Jul  1 18:23:29 2014
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 1 Jul 2014 22:23:29 +0000
Subject: [Paraview] [EXTERNAL] Re:  Color legend and log scaling
In-Reply-To: <3938F2CD-CE84-4DAA-B8DC-856194627805@kitware.com>
References: <9047EE0D4D3C8E43B93980DA10A073809C30DC12@EXMB04.srn.sandia.gov>
 <3938F2CD-CE84-4DAA-B8DC-856194627805@kitware.com>
Message-ID: <9047EE0D4D3C8E43B93980DA10A073809C30DD70@EXMB04.srn.sandia.gov>

With regards to data spanning more than 4 orders of magnitude, this is dealt with by having this value user selectable.

With regards to setting q to include most data, using a q at all is user selectable.  If you turn it off, Rescale to Data Range would just set min and max to include all data.  If data included 0, which is illegal, you have to do something.  Setting the min to be q orders of magnitude smaller than max is better than setting it to 1!  Then, if that wasn't what you wanted, you could always reset it manually.  My goal is to create a smarter way of automatically dealing with min and max for log scaling.

With regards to data that is an "invalid value", this is an orthogonal problem.  Dealing with invalid data is already dealt with (i.e., nans), and maybe we should expand this to include huge positive and negative numbers (1e38 and -1e38).  I believe it is still outside of this discussion.

Regarding negative values, my bad - I was not clear.  A vertical normal log scale bar, going from a 1e8 to 1e4 may have minor labels (working down) of 1e8, 1e7, 1e6, 1e5, and 1e4.  I.e., each tick towards the top representing a change of 10 million units, each tick towards the top representing a change of a thousand units.  Now, for the negative case, this would be reversed.  The color bar remains colored as before (for default color map, red on top, blue on bottom).  Since more positive numbers are always on top, we would run as follows (working down the minor labels): -1e4, -1e5, -1e6, -1e7 and -1e8.  Units change by the thousands at the top of the color legend, and millions towards the bottom.

Once again, you could always manually set your min and max.  But, I am arguing that what we currently do - set min to 1, is arbitrary, crude and wrong.

Alan



-----Original Message-----
From: David Thompson [mailto:david.thompson at kitware.com] 
Sent: Tuesday, July 01, 2014 3:44 PM
To: Scott, W Alan
Cc: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Color legend and log scaling

Hi Alan,

> I would like to propose a few changes in our log scaling algorithm for painting a dataset by a variable.   I discussed this with Utkarsh, and he asked that I bounce it off the e-mail list.  So, here goes.
>  
> Currently, when a user log scales a variable, if all data is positive, ParaView just uses the normal min and max.  There are times when this is not proper - for instance when looking at the temperature or density of material in a supernova, or velocity of outbound gas.  Another example is large data, with noise around zero.  I would like to propose that we have a user selectable option to set the minimum at maximum*10^-q, where q is user defined but defaults to 4.  In other words, the minimum would be set to 1*10^-4 of what the maximum is.

Avoiding a "window" around 0 in the initial view sounds good to me. However, I can imagine some cases where the data spans more than 4 orders of magnitude. One thing I've seen (debatably bad, but something ParaView must deal with) are simulations/datasets that use large numbers (i.e., 1e+38) to mark invalid values. (The LDAV climate data does this.) Showing a plot with the initial view set to [1e34,1e38] would not be useful, since it would only show invalid values. Another is chemical reaction simulations where concentrations span much more than 4 orders of magnitude (I've seen some span 11 or 12 orders of magnitude, but 5 or 6 can be common).

What choosing q to ensure that a significant fraction (say 90%?) of the data is actually on-screen? It not terribly hard (even in parallel) to extract a fixed-size sample that approximates a histogram to within a few percent. We could use that to determine where the bulk of the data resided and ensure that the q-value does not leave more than 10% offscreen.

> If all of the user's data is negative, ParaView grumbles, and then seg faults using a current master git pull - not optimal behavior.  In PV 4.1, it just sets min and max to 0.  I would like to propose that ParaView calculate the log of the data, as follows:  Index= -(log(abs(Var))).  Then, just draw the color legend as normal - for instance, red at top, white in the middle and blue at bottom.  Tick marks will be the reverse of positive log scaling - with the dense numbers, more negative numbers at the bottom and less dense, less negative numbers at the top.

I'm not sure I understand this, especially your use of "dense". It sounds like you have a particular dataset in mind where the probability density is low near zero. Are you saying you want the color scale to be different in the case of data that is all negative numbers? Or that log plots in general should have colors reversed?

> The problem arises with data that spans positive and negative numbers.  Since the log of 0 is infinity, we have to deal with very small numbers in a special way.  I propose that we find maxVal = max(maximum, abs(minimum)).  Then, we set the color bar to run from maxVal to -maxVal.  We log scale the top half of the color legend, running from maxVal to maxVal*10^-4, and we reverse log scale the bottom half of the color legend, running from -maxVal*10^-4 to -maxVal.  We calculate this negative range the same as the all negative data section above.  All data between maxVal*10^-4 and -maxVal*10^-4 would remain white by default, or user selectable black.

I like the idea of having a custom color for the range [-10^q,10^q] and I think I understand and agree with the simplified bounds/ticks for the case where the data crosses zero -- at least when it firmly crosses the origin. However, whose chemistry simulations I mentioned above would occasionally have very slightly negative concentrations. Physically they can never be negative but floating-point precision meant that some were. In this case, we might have a distribution of concentrations that went from -1e-16 to 1 with the bulk in the range [1e-10,1]. Using the algorithm above for the axes would assign half of the color palette to the range [-1,-1e-4], half to [1e-4,1] and draw a significant fraction of the data as "black". If instead the histogram was used to choose q, then we might be able to decide that all of the "naughty" data were outliers and select a log color-scale of [1e-10,1].

	David

> User selectable functionality would be as follows:
> 	* to allow/ not allow negative numbers (default allow)
> 	* to be able to change the q exponent (i.e., 4 above) (default 4)
> 	* to be able to change the painting color that is too small (default white)
> 	* to clamp minimum to some number (such as q == 4 above).  (default on).
>  
> Thoughts?
>  
> Alan
>  
>  
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects athttp://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://public.kitware.com/mailman/listinfo/paraview


From shermanw at indiana.edu  Wed Jul  2 10:22:11 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Wed, 02 Jul 2014 10:22:11 -0400
Subject: [Paraview] TemporalParticlesToPathlines filter missing scalar
In-Reply-To: <53B2E7B3.5090300@indiana.edu>
References: <53B22F78.7060505@indiana.edu>
 <CAE32kpWHkHd9oL4qgJPS97X8p5019Y+ZhEuM6Hz4=4CXc2_CNA@mail.gmail.com>
 <53B2E7B3.5090300@indiana.edu>
Message-ID: <53B41593.7070100@indiana.edu>

A followup to my question.

Presuming this is a bug, which means it might require some time to
fix, I went ahead and figured out a work-around.

I just bring up a "Calculator" filter and duplicate the problematic
field ("mass") as "massdup", and then put that through the
TemporalParticlesToPathlines filter.  And now I have access to
the data of interest.

Curiously, it's the "massdup" field that is now replaced by "TrailId".

	Bill


On 07/01/2014 12:54 PM, Bill Sherman wrote:
> On 07/01/2014 10:46 AM, Berk Geveci wrote:
>> Sounds like a bug. Do you have data/pipeline to reproduce it?
>
> Sure. I put a tar file at:
> http://iq-station.org/downloads/Part2Path_debug.tar.gz
>
> I included the first 9 steps of the data.
>
>> -berk
>
> Thanks,
> Bill
>
>>
>>
>> On Mon, Jun 30, 2014 at 11:48 PM, Bill Sherman <shermanw at indiana.edu
>> <mailto:shermanw at indiana.edu>> wrote:
>>
>> Hello,
>>
>> I am confused by something that the TemporalParticlesToPathlines
>> filter seems to be doing. It seems to be deleting or replacing
>> one of the scalar fields in the "Pathlines" output.
>>
>> I have a rather simple pipeline:
>>
>> Data
>> TemporalInterpolator
>> TemporalParticlesToPathlines
>> Pathlines
>> Tube
>> Particles
>> Glyph
>>
>> So the data has a handful of scalar values:
>> * density
>> * id
>> * mass
>> * type
>> * velocity (okay, not a scalar)
>> * vphi
>>
>> And all the filters offer these as available to color the data
>> by -- except! Except under the Pathlines (and Tube), the "mass"
>> data is replaced by "TrailId".
>>
>> Of course, I'm trying to color the pathlines by the value of the
>> particle "mass", so this is a problem for me.
>>
>> And I'm using the "id" field to make sure the particles are properly
>> associated with their past selves in the "TemporalParticlesToPathlines"
>> filter.
>>
>> Any thoughts? Didn't find anything via Google (though I limited the
>> search to the past year).
>>
>> Oh, and I tried this both with ParaView versions 4.0.1 and 4.1.0.
>>
>> Thank you,
>> Bill
>>
>> --
>> Bill Sherman
>> Sr. Technology Advisor
>> Advanced Visualization Lab
>> Pervasive Technology Inst
>> Indiana University
>> shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>> _________________________________________________
>> Powered by www.kitware.com <http://www.kitware.com>
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/__opensource/opensource.html
>> <http://www.kitware.com/opensource/opensource.html>
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/__ParaView <http://paraview.org/Wiki/ParaView>
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/__mailman/listinfo/paraview
>> <http://public.kitware.com/mailman/listinfo/paraview>
>>
>>
>


From kmorel at sandia.gov  Wed Jul  2 16:34:13 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 2 Jul 2014 20:34:13 +0000
Subject: [Paraview] Rendering in parallel
In-Reply-To: <CAAPOYrFoAbruAWoqtxv9TLEvd2WLik=aRUw0gfy2SEHGVvtheA@mail.gmail.com>
Message-ID: <CFD9C074.19528%kmorel@sandia.gov>

OK, I can see where things are going majorly wrong here. Let's start with the worst of the problems.

I notice on the bottom of your screenshot that your desktop has 4 windows named ParaView Server #0, ParaView Server #1, etc. Those are X windows that the server is opening up on your desktop. You really don't want the server to do that. Those windows are used for OpenGL rendering. If they are opened on your desktop, that means that all four of those processes on your server are sending all the geometry to your desktop, your desktop renders all the geometry, and then the images get shipped to the server. The server then composites those images together and sends the result back to your desktop.

I'm sure that when you are running the server, your DISPLAY environment variable is pointing back to your desktop, which is causing the problem. You need to make sure the server is run with display set to localhost:0. More information is on the ParaView wiki at:

http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#X_Connections

That said, I'm not sure using your server is going to give you a big rendering performance boost over your desktop. The parallel rendering is really designed for large clusters with many GPUs. The rendering should work OK on your desktop as long as you're not thrashing your virtual memory (which is possible).

-Ken

From: J?r?my Santina <jeremy.santina at gmail.com<mailto:jeremy.santina at gmail.com>>
Date: Wednesday, July 2, 2014 4:17 AM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel

Sorry for my poor description. I will try to give more information.

I am loading a Multi-block Dataset without applying any filters and the rendering is surface rendering. In order to understand how it works, I am just running a pvserver in parallel on another computer (with a better GPU) connected via SSH. The graphics card is an NVIDIA Quadro FX 4600 and you have to know that I am not alone using this machine.  Server and client both work on Linux. So would the problem be because there is only one GPU ?

I join a picture with this message.

I would have another question. When I launch the rendering in parallel, a variable called vtkProcessId is generated. What is it ? Does it do the same thing if I apply Process Id Scalars filter ? Or are they two different things ?

J?r?my


2014-07-01 18:08 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>:
To check the distribution of the data, use the Process Id Scalars filters. That should color the data based on which processor it is located.

It might help if you described your system more completely. What kind of data are you loading? Is it image data? Polygon data? AMR? An unstructured grid? Are you applying any filters? How are you rendering it? Is it surface or volume rendering? Is there any transparency? Can you send a picture? What kind of parallel computer are you using? Are you running ParaView on your desktop in multi-core mode (I think rendering actually serializes in that case because you still have only one GPU.), or are you connecting to a cluster? How many nodes on your cluster and how are they configured?

-Ken

From: J?r?my Santina <jeremy.santina at gmail.com<mailto:jeremy.santina at gmail.com>>
Date: Tuesday, July 1, 2014 2:31 AM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel

Actually, I did try the D3 filter but I didn't really see any better results. Maybe it is because I don't know how to configure it. How does D3 filter work ?



2014-06-30 16:21 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>:
Jeremy,

Like the other parallel processing in ParaView, the efficiency is dictated by the distribution of the data. If your data distribution is highly imbalanced such as when all the data is on one process as in your case, then all the processing will happen where the data is and the rest of the processors will remain idle.

You could try running the D3 filter. That should redistribute the point data more evenly.

-Ken

From: J?r?my Santina <jeremy.santina at gmail.com<mailto:jeremy.santina at gmail.com>>
Date: Monday, June 30, 2014 2:55 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Rendering in parallel

Good morning,

I am a novice user of Paraview and there are some aspects which I am not familiar with. Here is one of the issues I am having :

I run Paraview in Client-Server mode, performing the data processing and the rendering on the remote server, and I read a Tecplot Binary File (.plt) composed of more than 30 millions of points. This take a lot of time. An idea to speed up the calculation is to launch the server in parallel. I know that many readers can not read in parallel (it is the case of TecplotBinaryFileReader I think) so I don't expect any improvment in this way.

But, examining the Timer Log, I noticed that it doesn't speed up the rendering either. I tested many times displaying the points and both experiment with parallelism and without gave the same results (about 40-50 sec). I don't understand why.

Do I misinterpret the Timer Log ? Is the time of rendering long enough to conclude ? Do I have to set specific parameters to make it works ?

I thank you in advance for your help.

J?r?my


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140702/7ad5fa71/attachment-0001.html>

From jeremy.santina at gmail.com  Thu Jul  3 04:20:35 2014
From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=)
Date: Thu, 3 Jul 2014 10:20:35 +0200
Subject: [Paraview] Rendering in parallel
In-Reply-To: <CFD9C074.19528%kmorel@sandia.gov>
References: <CAAPOYrFoAbruAWoqtxv9TLEvd2WLik=aRUw0gfy2SEHGVvtheA@mail.gmail.com>
 <CFD9C074.19528%kmorel@sandia.gov>
Message-ID: <CAAPOYrEuF=AyU9UtzhhD3ALBDqh3X9rz1-z33uJgjkHjJmMbhA@mail.gmail.com>

Thank you very much for your help.

As you said, my DISPLAY environment variable is pointing back to my desktop.
The problem now is that I have tried using the option -display for the
command pvserver but apparently it is unknown. Is it normal ? Is there
another way to make sure that the display is set correctly ? I didn't
mention it but my version of Paraview is 4.1.0-RC1-Linux-64bits. I don't
know if it might help.

J?r?my.


2014-07-02 22:34 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:

>  OK, I can see where things are going majorly wrong here. Let's start
> with the worst of the problems.
>
>  I notice on the bottom of your screenshot that your desktop has 4
> windows named ParaView Server #0, ParaView Server #1, etc. Those are X
> windows that the server is opening up on your desktop. You really don't
> want the server to do that. Those windows are used for OpenGL rendering. If
> they are opened on your desktop, that means that all four of those
> processes on your server are sending *all* the geometry to your desktop,
> your desktop renders *all* the geometry, and then the images get shipped
> to the server. The server then composites those images together and sends
> the result *back* to your desktop.
>
>  I'm sure that when you are running the server, your DISPLAY environment
> variable is pointing back to your desktop, which is causing the problem.
> You need to make sure the server is run with display set to localhost:0.
> More information is on the ParaView wiki at:
>
>  http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#X_Connections
>
>  That said, I'm not sure using your server is going to give you a big
> rendering performance boost over your desktop. The parallel rendering is
> really designed for large clusters with many GPUs. The rendering should
> work OK on your desktop as long as you're not thrashing your virtual memory
> (which is possible).
>
>  -Ken
>
>   From: J?r?my Santina <jeremy.santina at gmail.com>
> Date: Wednesday, July 2, 2014 4:17 AM
>
> To: Kenneth Moreland <kmorel at sandia.gov>
> Cc: "paraview at paraview.org" <paraview at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel
>
>   Sorry for my poor description. I will try to give more information.
>
> I am loading a Multi-block Dataset without applying any filters and the
> rendering is surface rendering. In order to understand how it works, I am
> just running a pvserver in parallel on another computer (with a better GPU)
> connected via SSH. The graphics card is an NVIDIA Quadro FX 4600 and you
> have to know that I am not alone using this machine.  Server and client
> both work on Linux. So would the problem be because there is only one GPU ?
>
>  I join a picture with this message.
>
>  I would have another question. When I launch the rendering in parallel,
> a variable called vtkProcessId is generated. What is it ? Does it do the
> same thing if I apply Process Id Scalars filter ? Or are they two different
> things ?
>
>  J?r?my
>
>
> 2014-07-01 18:08 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>
>>  To check the distribution of the data, use the Process Id Scalars
>> filters. That should color the data based on which processor it is located.
>>
>>  It might help if you described your system more completely. What kind
>> of data are you loading? Is it image data? Polygon data? AMR? An
>> unstructured grid? Are you applying any filters? How are you rendering it?
>> Is it surface or volume rendering? Is there any transparency? Can you send
>> a picture? What kind of parallel computer are you using? Are you running
>> ParaView on your desktop in multi-core mode (I think rendering actually
>> serializes in that case because you still have only one GPU.), or are you
>> connecting to a cluster? How many nodes on your cluster and how are they
>> configured?
>>
>>  -Ken
>>
>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>> Date: Tuesday, July 1, 2014 2:31 AM
>> To: Kenneth Moreland <kmorel at sandia.gov>
>> Cc: "paraview at paraview.org" <paraview at paraview.org>
>> Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel
>>
>>   Actually, I did try the D3 filter but I didn't really see any better
>> results. Maybe it is because I don't know how to configure it. How does D3
>> filter work ?
>>
>>
>>
>> 2014-06-30 16:21 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>>
>>>   Jeremy,
>>>
>>>  Like the other parallel processing in ParaView, the efficiency is
>>> dictated by the distribution of the data. If your data distribution is
>>> highly imbalanced such as when all the data is on one process as in your
>>> case, then all the processing will happen where the data is and the rest of
>>> the processors will remain idle.
>>>
>>>  You could try running the D3 filter. That should redistribute the
>>> point data more evenly.
>>>
>>>  -Ken
>>>
>>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>>> Date: Monday, June 30, 2014 2:55 AM
>>> To: "paraview at paraview.org" <paraview at paraview.org>
>>> Subject: [EXTERNAL] [Paraview] Rendering in parallel
>>>
>>>    Good morning,
>>>
>>>  I am a novice user of Paraview and there are some aspects which I am
>>> not familiar with. Here is one of the issues I am having :
>>>
>>> I run Paraview in Client-Server mode, performing the data processing and
>>> the rendering on the remote server, and I read a Tecplot Binary File (.plt)
>>> composed of more than 30 millions of points. This take a lot of time. An
>>> idea to speed up the calculation is to launch the server in parallel. I
>>> know that many readers can not read in parallel (it is the case of
>>> TecplotBinaryFileReader I think) so I don't expect any improvment in this
>>> way.
>>>
>>> But, examining the Timer Log, I noticed that it doesn't speed up the
>>> rendering either. I tested many times displaying the points and both
>>> experiment with parallelism and without gave the same results (about 40-50
>>> sec). I don't understand why.
>>>
>>>  Do I misinterpret the Timer Log ? Is the time of rendering long enough
>>> to conclude ? Do I have to set specific parameters to make it works ?
>>>
>>>  I thank you in advance for your help.
>>>
>>>  J?r?my
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/92596cf2/attachment.html>

From jeremy.santina at gmail.com  Thu Jul  3 06:05:16 2014
From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=)
Date: Thu, 3 Jul 2014 12:05:16 +0200
Subject: [Paraview] Rendering in parallel
In-Reply-To: <CAAPOYrEuF=AyU9UtzhhD3ALBDqh3X9rz1-z33uJgjkHjJmMbhA@mail.gmail.com>
References: <CAAPOYrFoAbruAWoqtxv9TLEvd2WLik=aRUw0gfy2SEHGVvtheA@mail.gmail.com>
 <CFD9C074.19528%kmorel@sandia.gov>
 <CAAPOYrEuF=AyU9UtzhhD3ALBDqh3X9rz1-z33uJgjkHjJmMbhA@mail.gmail.com>
Message-ID: <CAAPOYrErQF9QoAtgqdgyYfVEGLFeNfqrqvVdgBvvZMb9Q2sApA@mail.gmail.com>

Actually, I don't use mpirun to launch pvserver but mpiexec in
ParaView-4.1.0-RC1-Linux-64bit/lib/paraview-4.1/ and it is why the option
is not recognized.

J?r?my


2014-07-03 10:20 GMT+02:00 J?r?my Santina <jeremy.santina at gmail.com>:

> Thank you very much for your help.
>
> As you said, my DISPLAY environment variable is pointing back to my
> desktop.
> The problem now is that I have tried using the option -display for the
> command pvserver but apparently it is unknown. Is it normal ? Is there
> another way to make sure that the display is set correctly ? I didn't
> mention it but my version of Paraview is 4.1.0-RC1-Linux-64bits. I don't
> know if it might help.
>
> J?r?my.
>
>
> 2014-07-02 22:34 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>
>  OK, I can see where things are going majorly wrong here. Let's start
>> with the worst of the problems.
>>
>>  I notice on the bottom of your screenshot that your desktop has 4
>> windows named ParaView Server #0, ParaView Server #1, etc. Those are X
>> windows that the server is opening up on your desktop. You really don't
>> want the server to do that. Those windows are used for OpenGL rendering. If
>> they are opened on your desktop, that means that all four of those
>> processes on your server are sending *all* the geometry to your desktop,
>> your desktop renders *all* the geometry, and then the images get shipped
>> to the server. The server then composites those images together and sends
>> the result *back* to your desktop.
>>
>>  I'm sure that when you are running the server, your DISPLAY environment
>> variable is pointing back to your desktop, which is causing the problem.
>> You need to make sure the server is run with display set to localhost:0.
>> More information is on the ParaView wiki at:
>>
>>  http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#X_Connections
>>
>>  That said, I'm not sure using your server is going to give you a big
>> rendering performance boost over your desktop. The parallel rendering is
>> really designed for large clusters with many GPUs. The rendering should
>> work OK on your desktop as long as you're not thrashing your virtual memory
>> (which is possible).
>>
>>  -Ken
>>
>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>> Date: Wednesday, July 2, 2014 4:17 AM
>>
>> To: Kenneth Moreland <kmorel at sandia.gov>
>> Cc: "paraview at paraview.org" <paraview at paraview.org>
>> Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel
>>
>>   Sorry for my poor description. I will try to give more information.
>>
>> I am loading a Multi-block Dataset without applying any filters and the
>> rendering is surface rendering. In order to understand how it works, I am
>> just running a pvserver in parallel on another computer (with a better GPU)
>> connected via SSH. The graphics card is an NVIDIA Quadro FX 4600 and you
>> have to know that I am not alone using this machine.  Server and client
>> both work on Linux. So would the problem be because there is only one GPU ?
>>
>>  I join a picture with this message.
>>
>>  I would have another question. When I launch the rendering in parallel,
>> a variable called vtkProcessId is generated. What is it ? Does it do the
>> same thing if I apply Process Id Scalars filter ? Or are they two different
>> things ?
>>
>>  J?r?my
>>
>>
>> 2014-07-01 18:08 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>>
>>>  To check the distribution of the data, use the Process Id Scalars
>>> filters. That should color the data based on which processor it is located.
>>>
>>>  It might help if you described your system more completely. What kind
>>> of data are you loading? Is it image data? Polygon data? AMR? An
>>> unstructured grid? Are you applying any filters? How are you rendering it?
>>> Is it surface or volume rendering? Is there any transparency? Can you send
>>> a picture? What kind of parallel computer are you using? Are you running
>>> ParaView on your desktop in multi-core mode (I think rendering actually
>>> serializes in that case because you still have only one GPU.), or are you
>>> connecting to a cluster? How many nodes on your cluster and how are they
>>> configured?
>>>
>>>  -Ken
>>>
>>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>>> Date: Tuesday, July 1, 2014 2:31 AM
>>> To: Kenneth Moreland <kmorel at sandia.gov>
>>> Cc: "paraview at paraview.org" <paraview at paraview.org>
>>> Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel
>>>
>>>   Actually, I did try the D3 filter but I didn't really see any better
>>> results. Maybe it is because I don't know how to configure it. How does D3
>>> filter work ?
>>>
>>>
>>>
>>> 2014-06-30 16:21 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>>>
>>>>   Jeremy,
>>>>
>>>>  Like the other parallel processing in ParaView, the efficiency is
>>>> dictated by the distribution of the data. If your data distribution is
>>>> highly imbalanced such as when all the data is on one process as in your
>>>> case, then all the processing will happen where the data is and the rest of
>>>> the processors will remain idle.
>>>>
>>>>  You could try running the D3 filter. That should redistribute the
>>>> point data more evenly.
>>>>
>>>>  -Ken
>>>>
>>>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>>>> Date: Monday, June 30, 2014 2:55 AM
>>>> To: "paraview at paraview.org" <paraview at paraview.org>
>>>> Subject: [EXTERNAL] [Paraview] Rendering in parallel
>>>>
>>>>    Good morning,
>>>>
>>>>  I am a novice user of Paraview and there are some aspects which I am
>>>> not familiar with. Here is one of the issues I am having :
>>>>
>>>> I run Paraview in Client-Server mode, performing the data processing
>>>> and the rendering on the remote server, and I read a Tecplot Binary File
>>>> (.plt) composed of more than 30 millions of points. This take a lot of
>>>> time. An idea to speed up the calculation is to launch the server in
>>>> parallel. I know that many readers can not read in parallel (it is the case
>>>> of TecplotBinaryFileReader I think) so I don't expect any improvment in
>>>> this way.
>>>>
>>>> But, examining the Timer Log, I noticed that it doesn't speed up the
>>>> rendering either. I tested many times displaying the points and both
>>>> experiment with parallelism and without gave the same results (about 40-50
>>>> sec). I don't understand why.
>>>>
>>>>  Do I misinterpret the Timer Log ? Is the time of rendering long
>>>> enough to conclude ? Do I have to set specific parameters to make it works ?
>>>>
>>>>  I thank you in advance for your help.
>>>>
>>>>  J?r?my
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/d2ac3b8e/attachment-0001.html>

From jeremy.santina at gmail.com  Thu Jul  3 09:13:23 2014
From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=)
Date: Thu, 3 Jul 2014 15:13:23 +0200
Subject: [Paraview] Rendering in parallel
In-Reply-To: <CAAPOYrErQF9QoAtgqdgyYfVEGLFeNfqrqvVdgBvvZMb9Q2sApA@mail.gmail.com>
References: <CAAPOYrFoAbruAWoqtxv9TLEvd2WLik=aRUw0gfy2SEHGVvtheA@mail.gmail.com>
 <CFD9C074.19528%kmorel@sandia.gov>
 <CAAPOYrEuF=AyU9UtzhhD3ALBDqh3X9rz1-z33uJgjkHjJmMbhA@mail.gmail.com>
 <CAAPOYrErQF9QoAtgqdgyYfVEGLFeNfqrqvVdgBvvZMb9Q2sApA@mail.gmail.com>
Message-ID: <CAAPOYrHuPUemBX7R90kbSbp+tMDL7sB2M3BZS7U68kBqpPQVJA@mail.gmail.com>

Ok, I have just set the environment variable DISPLAY to ":0" and it works.
I don't have these windows anymore so I guess the server renders the
geometry now.

Thank you again for your help.

J?r?my


2014-07-03 12:05 GMT+02:00 J?r?my Santina <jeremy.santina at gmail.com>:

> Actually, I don't use mpirun to launch pvserver but mpiexec in
> ParaView-4.1.0-RC1-Linux-64bit/lib/paraview-4.1/ and it is why the option
> is not recognized.
>
> J?r?my
>
>
> 2014-07-03 10:20 GMT+02:00 J?r?my Santina <jeremy.santina at gmail.com>:
>
> Thank you very much for your help.
>>
>> As you said, my DISPLAY environment variable is pointing back to my
>> desktop.
>> The problem now is that I have tried using the option -display for the
>> command pvserver but apparently it is unknown. Is it normal ? Is there
>> another way to make sure that the display is set correctly ? I didn't
>> mention it but my version of Paraview is 4.1.0-RC1-Linux-64bits. I don't
>> know if it might help.
>>
>> J?r?my.
>>
>>
>> 2014-07-02 22:34 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>>
>>  OK, I can see where things are going majorly wrong here. Let's start
>>> with the worst of the problems.
>>>
>>>  I notice on the bottom of your screenshot that your desktop has 4
>>> windows named ParaView Server #0, ParaView Server #1, etc. Those are X
>>> windows that the server is opening up on your desktop. You really don't
>>> want the server to do that. Those windows are used for OpenGL rendering. If
>>> they are opened on your desktop, that means that all four of those
>>> processes on your server are sending *all* the geometry to your
>>> desktop, your desktop renders *all* the geometry, and then the images
>>> get shipped to the server. The server then composites those images together
>>> and sends the result *back* to your desktop.
>>>
>>>  I'm sure that when you are running the server, your DISPLAY
>>> environment variable is pointing back to your desktop, which is causing the
>>> problem. You need to make sure the server is run with display set to
>>> localhost:0. More information is on the ParaView wiki at:
>>>
>>>  http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#X_Connections
>>>
>>>  That said, I'm not sure using your server is going to give you a big
>>> rendering performance boost over your desktop. The parallel rendering is
>>> really designed for large clusters with many GPUs. The rendering should
>>> work OK on your desktop as long as you're not thrashing your virtual memory
>>> (which is possible).
>>>
>>>  -Ken
>>>
>>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>>> Date: Wednesday, July 2, 2014 4:17 AM
>>>
>>> To: Kenneth Moreland <kmorel at sandia.gov>
>>> Cc: "paraview at paraview.org" <paraview at paraview.org>
>>> Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel
>>>
>>>   Sorry for my poor description. I will try to give more information.
>>>
>>> I am loading a Multi-block Dataset without applying any filters and the
>>> rendering is surface rendering. In order to understand how it works, I am
>>> just running a pvserver in parallel on another computer (with a better GPU)
>>> connected via SSH. The graphics card is an NVIDIA Quadro FX 4600 and you
>>> have to know that I am not alone using this machine.  Server and client
>>> both work on Linux. So would the problem be because there is only one GPU ?
>>>
>>>  I join a picture with this message.
>>>
>>>  I would have another question. When I launch the rendering in
>>> parallel, a variable called vtkProcessId is generated. What is it ? Does it
>>> do the same thing if I apply Process Id Scalars filter ? Or are they two
>>> different things ?
>>>
>>>  J?r?my
>>>
>>>
>>> 2014-07-01 18:08 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>>>
>>>>  To check the distribution of the data, use the Process Id Scalars
>>>> filters. That should color the data based on which processor it is located.
>>>>
>>>>  It might help if you described your system more completely. What kind
>>>> of data are you loading? Is it image data? Polygon data? AMR? An
>>>> unstructured grid? Are you applying any filters? How are you rendering it?
>>>> Is it surface or volume rendering? Is there any transparency? Can you send
>>>> a picture? What kind of parallel computer are you using? Are you running
>>>> ParaView on your desktop in multi-core mode (I think rendering actually
>>>> serializes in that case because you still have only one GPU.), or are you
>>>> connecting to a cluster? How many nodes on your cluster and how are they
>>>> configured?
>>>>
>>>>  -Ken
>>>>
>>>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>>>> Date: Tuesday, July 1, 2014 2:31 AM
>>>> To: Kenneth Moreland <kmorel at sandia.gov>
>>>> Cc: "paraview at paraview.org" <paraview at paraview.org>
>>>> Subject: [EXTERNAL] Re: [Paraview] Rendering in parallel
>>>>
>>>>   Actually, I did try the D3 filter but I didn't really see any better
>>>> results. Maybe it is because I don't know how to configure it. How does D3
>>>> filter work ?
>>>>
>>>>
>>>>
>>>> 2014-06-30 16:21 GMT+02:00 Moreland, Kenneth <kmorel at sandia.gov>:
>>>>
>>>>>   Jeremy,
>>>>>
>>>>>  Like the other parallel processing in ParaView, the efficiency is
>>>>> dictated by the distribution of the data. If your data distribution is
>>>>> highly imbalanced such as when all the data is on one process as in your
>>>>> case, then all the processing will happen where the data is and the rest of
>>>>> the processors will remain idle.
>>>>>
>>>>>  You could try running the D3 filter. That should redistribute the
>>>>> point data more evenly.
>>>>>
>>>>>  -Ken
>>>>>
>>>>>   From: J?r?my Santina <jeremy.santina at gmail.com>
>>>>> Date: Monday, June 30, 2014 2:55 AM
>>>>> To: "paraview at paraview.org" <paraview at paraview.org>
>>>>> Subject: [EXTERNAL] [Paraview] Rendering in parallel
>>>>>
>>>>>    Good morning,
>>>>>
>>>>>  I am a novice user of Paraview and there are some aspects which I am
>>>>> not familiar with. Here is one of the issues I am having :
>>>>>
>>>>> I run Paraview in Client-Server mode, performing the data processing
>>>>> and the rendering on the remote server, and I read a Tecplot Binary File
>>>>> (.plt) composed of more than 30 millions of points. This take a lot of
>>>>> time. An idea to speed up the calculation is to launch the server in
>>>>> parallel. I know that many readers can not read in parallel (it is the case
>>>>> of TecplotBinaryFileReader I think) so I don't expect any improvment in
>>>>> this way.
>>>>>
>>>>> But, examining the Timer Log, I noticed that it doesn't speed up the
>>>>> rendering either. I tested many times displaying the points and both
>>>>> experiment with parallelism and without gave the same results (about 40-50
>>>>> sec). I don't understand why.
>>>>>
>>>>>  Do I misinterpret the Timer Log ? Is the time of rendering long
>>>>> enough to conclude ? Do I have to set specific parameters to make it works ?
>>>>>
>>>>>  I thank you in advance for your help.
>>>>>
>>>>>  J?r?my
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/b9542f59/attachment.html>

From jfavre at cscs.ch  Thu Jul  3 09:42:05 2014
From: jfavre at cscs.ch (Favre  Jean)
Date: Thu, 3 Jul 2014 13:42:05 +0000
Subject: [Paraview] PointSprite seg faulting in client-server mode
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F681AA1430F@MBX21.d.ethz.ch>

Hi there

I am using PV4.1 on a GPU-based machine, in client-server mode (remote render threshold=0).

LIC, as another example of a GPU-enabled representation, works fine. But when I try the PointSprite plugin, I get a seg fault. I even tried a single task pvserver, and it always seg faults. my driver (server-side) is libGL.so.319.62. i have tried to turn Immediate Rendering ON/OFF.

I have also tried a second cluster. Same result.

I don't actually remember ever having done PointSprite on the remote side. Is this something which works?

-----------------
Jean 
CSCS

From minh.cfd at gmail.com  Thu Jul  3 12:39:06 2014
From: minh.cfd at gmail.com (minh hien)
Date: Thu, 3 Jul 2014 12:39:06 -0400
Subject: [Paraview] Line Chart view - Legend font
Message-ID: <CANhRpYF8D7Fcj2rGtsaoFbZd95Udg3vcS9zX2e+RJ3_tqqnq3g@mail.gmail.com>

Hi,

Can I change font of Legend in Line Chart view plot? I am using Paraview ,
Ubuntu version 4.0.1.

Thank you.
Minh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/1f170952/attachment.html>

From berk.geveci at kitware.com  Thu Jul  3 12:57:35 2014
From: berk.geveci at kitware.com (Berk Geveci)
Date: Thu, 3 Jul 2014 12:57:35 -0400
Subject: [Paraview] TemporalParticlesToPathlines filter missing scalar
In-Reply-To: <53B41593.7070100@indiana.edu>
References: <53B22F78.7060505@indiana.edu>
 <CAE32kpWHkHd9oL4qgJPS97X8p5019Y+ZhEuM6Hz4=4CXc2_CNA@mail.gmail.com>
 <53B2E7B3.5090300@indiana.edu> <53B41593.7070100@indiana.edu>
Message-ID: <CAE32kpWaA-Ex+oSJ3kbUYjpsoiz+TqMZ_kOd_yw_HYLuapDd1g@mail.gmail.com>

It was indeed a bug. Thanks for reporting it Bill. A fix is in the
pipeline. It will probably take until next week for it to make into
ParaView master.

Best,
-berk


On Wed, Jul 2, 2014 at 10:22 AM, Bill Sherman <shermanw at indiana.edu> wrote:

> A followup to my question.
>
> Presuming this is a bug, which means it might require some time to
> fix, I went ahead and figured out a work-around.
>
> I just bring up a "Calculator" filter and duplicate the problematic
> field ("mass") as "massdup", and then put that through the
> TemporalParticlesToPathlines filter.  And now I have access to
> the data of interest.
>
> Curiously, it's the "massdup" field that is now replaced by "TrailId".
>
>         Bill
>
>
>
> On 07/01/2014 12:54 PM, Bill Sherman wrote:
>
>> On 07/01/2014 10:46 AM, Berk Geveci wrote:
>>
>>> Sounds like a bug. Do you have data/pipeline to reproduce it?
>>>
>>
>> Sure. I put a tar file at:
>> http://iq-station.org/downloads/Part2Path_debug.tar.gz
>>
>> I included the first 9 steps of the data.
>>
>>  -berk
>>>
>>
>> Thanks,
>> Bill
>>
>>
>>>
>>> On Mon, Jun 30, 2014 at 11:48 PM, Bill Sherman <shermanw at indiana.edu
>>> <mailto:shermanw at indiana.edu>> wrote:
>>>
>>> Hello,
>>>
>>> I am confused by something that the TemporalParticlesToPathlines
>>> filter seems to be doing. It seems to be deleting or replacing
>>> one of the scalar fields in the "Pathlines" output.
>>>
>>> I have a rather simple pipeline:
>>>
>>> Data
>>> TemporalInterpolator
>>> TemporalParticlesToPathlines
>>> Pathlines
>>> Tube
>>> Particles
>>> Glyph
>>>
>>> So the data has a handful of scalar values:
>>> * density
>>> * id
>>> * mass
>>> * type
>>> * velocity (okay, not a scalar)
>>> * vphi
>>>
>>> And all the filters offer these as available to color the data
>>> by -- except! Except under the Pathlines (and Tube), the "mass"
>>> data is replaced by "TrailId".
>>>
>>> Of course, I'm trying to color the pathlines by the value of the
>>> particle "mass", so this is a problem for me.
>>>
>>> And I'm using the "id" field to make sure the particles are properly
>>> associated with their past selves in the "TemporalParticlesToPathlines"
>>> filter.
>>>
>>> Any thoughts? Didn't find anything via Google (though I limited the
>>> search to the past year).
>>>
>>> Oh, and I tried this both with ParaView versions 4.0.1 and 4.1.0.
>>>
>>> Thank you,
>>> Bill
>>>
>>> --
>>> Bill Sherman
>>> Sr. Technology Advisor
>>> Advanced Visualization Lab
>>> Pervasive Technology Inst
>>> Indiana University
>>> shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>>> _________________________________________________
>>> Powered by www.kitware.com <http://www.kitware.com>
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/__opensource/opensource.html
>>> <http://www.kitware.com/opensource/opensource.html>
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/__ParaView <http://paraview.org/Wiki/ParaView>
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/__mailman/listinfo/paraview
>>> <http://public.kitware.com/mailman/listinfo/paraview>
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/9b4d2067/attachment-0001.html>

From shermanw at indiana.edu  Thu Jul  3 13:44:32 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Thu, 03 Jul 2014 13:44:32 -0400
Subject: [Paraview] TemporalParticlesToPathlines filter missing scalar
In-Reply-To: <CAE32kpWaA-Ex+oSJ3kbUYjpsoiz+TqMZ_kOd_yw_HYLuapDd1g@mail.gmail.com>
References: <53B22F78.7060505@indiana.edu>
 <CAE32kpWHkHd9oL4qgJPS97X8p5019Y+ZhEuM6Hz4=4CXc2_CNA@mail.gmail.com>
 <53B2E7B3.5090300@indiana.edu> <53B41593.7070100@indiana.edu>
 <CAE32kpWaA-Ex+oSJ3kbUYjpsoiz+TqMZ_kOd_yw_HYLuapDd1g@mail.gmail.com>
Message-ID: <53B59680.6070606@indiana.edu>

On 07/03/2014 12:57 PM, Berk Geveci wrote:
> It was indeed a bug. Thanks for reporting it Bill. A fix is in the
> pipeline. It will probably take until next week for it to make into
> ParaView master.

Sounds good, thanks Berk.

And if, while that's in the pipeline, can I also request an agumentation
to the documentation -- what is the "TrailId" data that is added to
the pathlines output?  And also, I noticed that the particles output
also has an added data value ("GlyphVector") -- what does that do?

(And there's a typo in the beginning of the documentation -- "much"
should be "must".  Trivial, I know.)

> Best,
> -berk

	Bill

>
>
> On Wed, Jul 2, 2014 at 10:22 AM, Bill Sherman <shermanw at indiana.edu
> <mailto:shermanw at indiana.edu>> wrote:
>
>     A followup to my question.
>
>     Presuming this is a bug, which means it might require some time to
>     fix, I went ahead and figured out a work-around.
>
>     I just bring up a "Calculator" filter and duplicate the problematic
>     field ("mass") as "massdup", and then put that through the
>     TemporalParticlesToPathlines filter. And now I have access to
>     the data of interest.
>
>     Curiously, it's the "massdup" field that is now replaced by "TrailId".
>
>     Bill
>
>
>
>     On 07/01/2014 12:54 PM, Bill Sherman wrote:
>
>         On 07/01/2014 10:46 AM, Berk Geveci wrote:
>
>             Sounds like a bug. Do you have data/pipeline to reproduce it?
>
>
>         Sure. I put a tar file at:
>         http://iq-station.org/__downloads/Part2Path_debug.tar.__gz
>         <http://iq-station.org/downloads/Part2Path_debug.tar.gz>
>
>         I included the first 9 steps of the data.
>
>             -berk
>
>
>         Thanks,
>         Bill
>
>
>
>             On Mon, Jun 30, 2014 at 11:48 PM, Bill Sherman
>             <shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>             <mailto:shermanw at indiana.edu <mailto:shermanw at indiana.edu>>>
>             wrote:
>
>             Hello,
>
>             I am confused by something that the TemporalParticlesToPathlines
>             filter seems to be doing. It seems to be deleting or replacing
>             one of the scalar fields in the "Pathlines" output.
>
>             I have a rather simple pipeline:
>
>             Data
>             TemporalInterpolator
>             TemporalParticlesToPathlines
>             Pathlines
>             Tube
>             Particles
>             Glyph
>
>             So the data has a handful of scalar values:
>             * density
>             * id
>             * mass
>             * type
>             * velocity (okay, not a scalar)
>             * vphi
>
>             And all the filters offer these as available to color the data
>             by -- except! Except under the Pathlines (and Tube), the "mass"
>             data is replaced by "TrailId".
>
>             Of course, I'm trying to color the pathlines by the value of the
>             particle "mass", so this is a problem for me.
>
>             And I'm using the "id" field to make sure the particles are
>             properly
>             associated with their past selves in the
>             "TemporalParticlesToPathlines"
>             filter.
>
>             Any thoughts? Didn't find anything via Google (though I
>             limited the
>             search to the past year).
>
>             Oh, and I tried this both with ParaView versions 4.0.1 and
>             4.1.0.
>
>             Thank you,
>             Bill
>
>             --
>             Bill Sherman
>             Sr. Technology Advisor
>             Advanced Visualization Lab
>             Pervasive Technology Inst
>             Indiana University
>             shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>             <mailto:shermanw at indiana.edu <mailto:shermanw at indiana.edu>>
>             ___________________________________________________
>             Powered by www.kitware.com <http://www.kitware.com>
>             <http://www.kitware.com>
>
>             Visit other Kitware open-source projects at
>             http://www.kitware.com/____opensource/opensource.html
>             <http://www.kitware.com/__opensource/opensource.html>
>             <http://www.kitware.com/__opensource/opensource.html
>             <http://www.kitware.com/opensource/opensource.html>>
>
>             Please keep messages on-topic and check the ParaView Wiki at:
>             http://paraview.org/Wiki/____ParaView
>             <http://paraview.org/Wiki/__ParaView>
>             <http://paraview.org/Wiki/__ParaView
>             <http://paraview.org/Wiki/ParaView>>
>
>             Follow this link to subscribe/unsubscribe:
>             http://public.kitware.com/____mailman/listinfo/paraview
>             <http://public.kitware.com/__mailman/listinfo/paraview>
>             <http://public.kitware.com/__mailman/listinfo/paraview
>             <http://public.kitware.com/mailman/listinfo/paraview>>
>
>
>
>
>


From berk.geveci at kitware.com  Thu Jul  3 13:53:35 2014
From: berk.geveci at kitware.com (Berk Geveci)
Date: Thu, 3 Jul 2014 13:53:35 -0400
Subject: [Paraview] TemporalParticlesToPathlines filter missing scalar
In-Reply-To: <53B59680.6070606@indiana.edu>
References: <53B22F78.7060505@indiana.edu>
 <CAE32kpWHkHd9oL4qgJPS97X8p5019Y+ZhEuM6Hz4=4CXc2_CNA@mail.gmail.com>
 <53B2E7B3.5090300@indiana.edu> <53B41593.7070100@indiana.edu>
 <CAE32kpWaA-Ex+oSJ3kbUYjpsoiz+TqMZ_kOd_yw_HYLuapDd1g@mail.gmail.com>
 <53B59680.6070606@indiana.edu>
Message-ID: <CAE32kpX4nuo974d_ZbFRAKQSyU4jfgGP5gX=_jXZFOdPF9+0yA@mail.gmail.com>

You can always ask :-)

It's not my class though so I have no idea what those arrays are. Feel free
to dig into the code (VTK/Filters/General/vtkTemporalPathLineFilter.cxx) to
figure it out and contribute updated doc. Or you may want to go to the VTK
developers list. Or bug John Biddiscombe directly (the original author).

Best,
-berk


On Thu, Jul 3, 2014 at 1:44 PM, Bill Sherman <shermanw at indiana.edu> wrote:

> On 07/03/2014 12:57 PM, Berk Geveci wrote:
>
>> It was indeed a bug. Thanks for reporting it Bill. A fix is in the
>> pipeline. It will probably take until next week for it to make into
>> ParaView master.
>>
>
> Sounds good, thanks Berk.
>
> And if, while that's in the pipeline, can I also request an agumentation
> to the documentation -- what is the "TrailId" data that is added to
> the pathlines output?  And also, I noticed that the particles output
> also has an added data value ("GlyphVector") -- what does that do?
>
> (And there's a typo in the beginning of the documentation -- "much"
> should be "must".  Trivial, I know.)
>
>  Best,
>> -berk
>>
>
>         Bill
>
>
>>
>> On Wed, Jul 2, 2014 at 10:22 AM, Bill Sherman <shermanw at indiana.edu
>> <mailto:shermanw at indiana.edu>> wrote:
>>
>>     A followup to my question.
>>
>>     Presuming this is a bug, which means it might require some time to
>>     fix, I went ahead and figured out a work-around.
>>
>>     I just bring up a "Calculator" filter and duplicate the problematic
>>     field ("mass") as "massdup", and then put that through the
>>     TemporalParticlesToPathlines filter. And now I have access to
>>     the data of interest.
>>
>>     Curiously, it's the "massdup" field that is now replaced by "TrailId".
>>
>>     Bill
>>
>>
>>
>>     On 07/01/2014 12:54 PM, Bill Sherman wrote:
>>
>>         On 07/01/2014 10:46 AM, Berk Geveci wrote:
>>
>>             Sounds like a bug. Do you have data/pipeline to reproduce it?
>>
>>
>>         Sure. I put a tar file at:
>>         http://iq-station.org/__downloads/Part2Path_debug.tar.__gz
>>
>>         <http://iq-station.org/downloads/Part2Path_debug.tar.gz>
>>
>>         I included the first 9 steps of the data.
>>
>>             -berk
>>
>>
>>         Thanks,
>>         Bill
>>
>>
>>
>>             On Mon, Jun 30, 2014 at 11:48 PM, Bill Sherman
>>             <shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>>             <mailto:shermanw at indiana.edu <mailto:shermanw at indiana.edu>>>
>>
>>             wrote:
>>
>>             Hello,
>>
>>             I am confused by something that the
>> TemporalParticlesToPathlines
>>             filter seems to be doing. It seems to be deleting or replacing
>>             one of the scalar fields in the "Pathlines" output.
>>
>>             I have a rather simple pipeline:
>>
>>             Data
>>             TemporalInterpolator
>>             TemporalParticlesToPathlines
>>             Pathlines
>>             Tube
>>             Particles
>>             Glyph
>>
>>             So the data has a handful of scalar values:
>>             * density
>>             * id
>>             * mass
>>             * type
>>             * velocity (okay, not a scalar)
>>             * vphi
>>
>>             And all the filters offer these as available to color the data
>>             by -- except! Except under the Pathlines (and Tube), the
>> "mass"
>>             data is replaced by "TrailId".
>>
>>             Of course, I'm trying to color the pathlines by the value of
>> the
>>             particle "mass", so this is a problem for me.
>>
>>             And I'm using the "id" field to make sure the particles are
>>             properly
>>             associated with their past selves in the
>>             "TemporalParticlesToPathlines"
>>             filter.
>>
>>             Any thoughts? Didn't find anything via Google (though I
>>             limited the
>>             search to the past year).
>>
>>             Oh, and I tried this both with ParaView versions 4.0.1 and
>>             4.1.0.
>>
>>             Thank you,
>>             Bill
>>
>>             --
>>             Bill Sherman
>>             Sr. Technology Advisor
>>             Advanced Visualization Lab
>>             Pervasive Technology Inst
>>             Indiana University
>>             shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>>             <mailto:shermanw at indiana.edu <mailto:shermanw at indiana.edu>>
>>             ___________________________________________________
>>
>>             Powered by www.kitware.com <http://www.kitware.com>
>>             <http://www.kitware.com>
>>
>>             Visit other Kitware open-source projects at
>>             http://www.kitware.com/____opensource/opensource.html
>>             <http://www.kitware.com/__opensource/opensource.html>
>>
>>             <http://www.kitware.com/__opensource/opensource.html
>>             <http://www.kitware.com/opensource/opensource.html>>
>>
>>             Please keep messages on-topic and check the ParaView Wiki at:
>>             http://paraview.org/Wiki/____ParaView
>>             <http://paraview.org/Wiki/__ParaView>
>>
>>             <http://paraview.org/Wiki/__ParaView
>>             <http://paraview.org/Wiki/ParaView>>
>>
>>             Follow this link to subscribe/unsubscribe:
>>             http://public.kitware.com/____mailman/listinfo/paraview
>>             <http://public.kitware.com/__mailman/listinfo/paraview>
>>             <http://public.kitware.com/__mailman/listinfo/paraview
>>             <http://public.kitware.com/mailman/listinfo/paraview>>
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/92f91590/attachment.html>

From dave.demarle at kitware.com  Thu Jul  3 14:13:47 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 3 Jul 2014 14:13:47 -0400
Subject: [Paraview] announce: Kitware is hiring - now with more web!
Message-ID: <CANjZAi8bMPX5FqpBnuYJkNB37LW6yz93cvvcuEQ0NSn-xJ_d8g@mail.gmail.com>

Howdy,

If you are talented researcher and developer with strong C++ and/or web
services development skills, please consider applying to Kitware. We are
particularly interested now in developers who have significant web service
development talent to help us expand the frontiers of visualization and
analytics delivered over the web. At Kitware you will join a fun and
talented team and work on many interesting and challenging technical
problems - always aiming to deliver robust and widely used software
solutions.

Specifically, the scientific visualization and medical groups at Kitware is
looking for these people:
* Scientific Visualization Web Developer (see below)
* GUI and Application Software Developer
* Informatics Researcher
* Informatics Software Developer
* HPC Visualization and Data Analysis Software Developer
* Scientific Visualization Developer
* Research and Development Involving Machine Learning and Medical Image
Analysis
* Technical Lead in Biomedical Image Analysis and Visualization
* Biomechanical Modeling and Surgical Simulation Software Developer

Go to http://jobs.kitware.com/opportunities.html for more details and to
apply.

SCIENTIFIC VISUALIZATION WEB DEVELOPER

Job Description:

By joining our team you will participate in a dynamic work environment with
exceptionally talented coworkers who are committed to high-quality
development practices.

You will collaborate with esteemed researchers from around the world to
create next-generation, open-source software for web applications for data
management, analysis, and visualization; design and produce full-featured,
modern web interfaces for cutting-edge applications; and will deploy
software applications and infrastructure that are used by people, every
day, around the world, to improve the world.

Work will be performed in the context of an open-source and highly
collaborative development model.

Qualifications:

An ideal candidate should have at least four years of experience in HTML,
CSS, and JavaScript, with an undergraduate or higher degree in Computer
Science or a related field. Strong software development skills are a must,
and familiarity with website UI/UX aesthetics and design as well as
JavaScript libraries such as JQuery, Underscore, Backbone, and/or Angular
is highly desirable.

Candidates should be familiar with tools for good software practice such as
git and web testing frameworks. Also desirable is experience with server
scripting languages like Python, and server components such as Apache,
Node.js, Django, and CherryPy. Strong candidates will also have experience
with web visualization libraries such as D3, WebGL, and HTML5 Canvas. C++
experience is a plus.

thanks and good luck!

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/7fbe1fb8/attachment-0001.html>

From saeed.mazrouei at gmail.com  Thu Jul  3 16:34:57 2014
From: saeed.mazrouei at gmail.com (Saeed Mazrouei)
Date: Thu, 3 Jul 2014 16:34:57 -0400
Subject: [Paraview] (no subject)
Message-ID: <CAO6K9GVoUVhNXG6GPUBtnKiDkZGuyfY9ft4yapN2Q-P=Fdns2g@mail.gmail.com>

Hi

Does anyone has a vtk file in cylindrical coordinate. I have data and I
need to write them in vtk file for cylindrical coordinate. I just started
to learn. please help me
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/388b17d4/attachment.html>

From dave.demarle at kitware.com  Thu Jul  3 17:25:39 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 3 Jul 2014 17:25:39 -0400
Subject: [Paraview] Data Displayed Incorrectly
In-Reply-To: <CAE=GJrZng7D-xWOjzPROTGcKURjtEFTYBQGfZoV03aKCqRGV0w@mail.gmail.com>
References: <CAE=GJra_a2sS8nqwzsOsPJXmMFaNZuYzQyyvnkEKqC4To5tqdg@mail.gmail.com>
 <CAE=GJrY8NrGksVQ-kWUQJB3SD0axiBuZtgVf2v8dz8iFMY9vug@mail.gmail.com>
 <CAE=GJrZng7D-xWOjzPROTGcKURjtEFTYBQGfZoV03aKCqRGV0w@mail.gmail.com>
Message-ID: <CANjZAi-F_ZrhZMMonmFnENVFPgVA=UOMU1BuvpEZv_uO_HK0Cg@mail.gmail.com>

The problem is that GL itself (almost always) has 4 byte floating point
precision. Thus anything VTK draws that needs more ends up loosing
precision. You see with really large and really small numbers. The latest
incarnation of VTK's charts do not have the same problem.

In any case, thanks Leo for tracking the issue down and posting the
solution to the list.







David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Mon, Jun 30, 2014 at 9:22 AM, L?o Pessanha <leonardopessanha74 at gmail.com>
wrote:

> After a lot of attempts,  I found the problem
>
> The coordinates of my points were too big
>
> I was using the full  geographic coordinate
>
> So,  the coordinates were really big numbers and for some reason that I
> don't know they were not being displayed  correctly
>
> I've fixed this,  and now everything looks great
>
> Att,
>
> Leonardo Pessanha
> UFRJ -  Federal University of Rio de Janeiro
> El jun 23, 2014 9:22 a.m., "L?o Pessanha" <leonardopessanha74 at gmail.com>
> escribi?:
>
>  It seems like this only happens when I try to load big datasets
>>
>> How could i solve this problem?
>>
>> Maybe trying another type of data,  different from vtk or maybe clip the
>> data
>>
>> Can someone give me a hint??
>> El jun 16, 2014 3:49 p.m., "L?o Pessanha" <leonardopessanha74 at gmail.com>
>> escribi?:
>>
>>> Hi,
>>>
>>> I am using Windows 7 64-bit - Paraview 4.0.1 - 16Mb RAM - QuadroPlex(2
>>> NVIDIA Quadro FX 5800)
>>>
>>> I set up a server with 2 processes and a pvx config file with 2 machines
>>> each one showing half of the visualization
>>>
>>> The problem is when i load a 400mb VTK file of a structured dataset
>>> with 9675000 points and 1 scalar
>>>
>>> I am getting a flicked image of the data, the data is not displayed
>>> completely
>>>
>>> There`s a image attached
>>>
>>> Can someone help me?
>>>
>>> Another question, how can i use advantage of GPU on Windows?
>>>
>>> Att,
>>> Leonardo Pessanha
>>>
>>>
>>>
>>>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/778ccb00/attachment.html>

From cchukw1 at tigers.lsu.edu  Fri Jul  4 01:06:38 2014
From: cchukw1 at tigers.lsu.edu (Chukwudi Chukwudozie)
Date: Fri, 4 Jul 2014 00:06:38 -0500
Subject: [Paraview] Extracting result from IntegrateVariables
Message-ID: <CANPyyBJym9T5aEHDuFS8Ao3ChF=Ptu8RrPqvsuYxu_vR0+u4aQ@mail.gmail.com>

Hi,

I'm pretty new in paraview python scripting and I'm trying my hand on an
example to IntegrateVariables along a slice (plane). However, I don't know
how to extract the results of the Integrate pipeline as when I ask to
print, all I get is a memory address. Below is a snapshot of my s=python
script. Basically, after calling, IntegrateVariables0 = IntegrateVariables(
Calculator0 ), I want to be able to use the result of the integration for
other operations. How do I access it, or the syntax to use.



Slice0 = Slice()

Slice0.SliceType = "Plane"

Slice0 = GetActiveSource()

Slice0.SliceType.Origin = [0.5, 0.005, 0.5]

Slice0.SliceType.Normal = [1.0, 0.0, 0.0]

Calculator0 = Calculator( Slice0 )

Calculator0.Function = 'Volumetric Crack Opening'

IntegrateVariables0 = IntegrateVariables( Calculator0 )

print IntegrateVariables0





Chuks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140704/c0ea8f7b/attachment.html>

From jfavre at cscs.ch  Fri Jul  4 05:52:27 2014
From: jfavre at cscs.ch (Favre  Jean)
Date: Fri, 4 Jul 2014 09:52:27 +0000
Subject: [Paraview] PointSprite seg faulting in client-server mode
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F681AA1430F@MBX21.d.ethz.ch>
References: <0EB9B6375711A04B820E6B6F5CCA9F681AA1430F@MBX21.d.ethz.ch>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F681AA1587B@MBX21.d.ethz.ch>


here is a follow-up.  I installed the latest git checkout on our Cray, and I can now do Point Sprite rendering. I tested with 8.5 billion particles on 128 GPUs.

I still see some error message, but it is not breaking and not stopping me. That error message comes from the client on my desktop.

ERROR: In /local/apps/ParaView/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 710
vtkCompositeDataPipeline (0xa2518b0): Input port 0 of algorithm vtkAppendPolyData(0x9a04f90) has 0 connections but is not optional.
-----------------

Jean
CSCS

From a.huebl at hzdr.de  Sat Jul  5 07:47:01 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Sat, 05 Jul 2014 13:47:01 +0200
Subject: [Paraview] Config OSMesa Software Rendering
Message-ID: <53B7E5B5.6070702@hzdr.de>

Hi ParaView list,


I am trying to set up a offscreen rendering setup with the current
ParaView master (g5493984) and OSMesa.

The target platform is a CPU-only cluster with several nodes, each
containing four sockels with AMD Bulldozer CPUs (64 physical cores per
node).

I get everything up and running in parallel, connections via rc work
perfectly and I can load my data.

But the problems start with rendering the data. Do you have any
recommendations which versions of OSMesa and llvmpipe are tested and stable?

The recommendations in the wiki


http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D#OSMesa.2C_Mesa_without_graphics_hardware

  http://www.paraview.org/Wiki/ParaView/Users_Guide/Parallel_Rendering

Look a bit outdated to me.


E.g.
 - Mesa 9.2.5 (and newer versions) already split libgl and libglu
   which versions are recommended?
 - does OSMesa Gallium llvmpipe run with llvm X.Y (e.g. 3.3) ?
 - what do I have to set for the DISPLAY environment with OSMesa ?
 - is it necessary/forbidden to have a X11 server running in that setup
   (on the server nodes)?
 - I am confused if the mentioned "SOFTWARE_DEPTH_BITS=31" bug is
   already fixed in mesa
 - are some of my dependencies (OpenMPI, gcc, python) too new/old ?

I configured the server side with a whole bunch of flags now:

cmake -DCMAKE_INSTALL_PREFIX=$HOME/bin/paraview-4.1.0-1008-g5493984   \
   -DPARAVIEW_BUILD_QT_GUI=OFF   -DBUILD_TESTING=OFF \
   -DCMAKE_BUILD_TYPE=Debug   -DPARAVIEW_ENABLE_CATALYST=OFF \
   -DPARAVIEW_ENABLE_PYTHON=ON   -DPARAVIEW_USE_MPI=ON \
   -DPARAVIEW_USE_SYSTEM_MPI4PY=ON   -DVTK_USE_X=OFF \
   -DOPENGL_INCLUDE_DIR=$MESA_ROOT/include  \
   -DOSMESA_INCLUDE_DIR=$MESA_ROOT/include -DVTK_OPENGL_HAS_OSMESA=ON  \
   -DOPENGL_gl_LIBRARY=IS-NOTFOUND \
   -DOPENGL_glu_LIBRARY=$MESA_ROOT/lib/libGLU.so \
   -DOSMESA_LIBRARY=$MESA_ROOT/lib/libOSMesa.so -DVTK_USE_OFFSCREEN=ON \
   -DPARAVIEW_BUILD_PLUGIN_AdiosReader=ON \
   -DVTK_Group_MPI=ON -DVTK_Group_Imaging=ON -DVTK_Group_Rendering=ON \
   -DVTK_XDMF_USE_MPI=ON -DXDMF_BUILD_MPI=ON \
   -GNinja ~/src/ParaView

and I am starting my servers with

mpiexec -npernode 8 -n 32 `which pvserver` --use-offscreen-rendering \
  -sp=$NUM_PORT -rc -ch=$HEAD_NODE

and used the following separately compiled dependencies:
  - python 2.7.5
  - icet 2.1.1 (probably compiled again by paraview)
  - gcc 4.8.2
  - OpenMPI 1.7.4 (with infiniband support)
  - cmake 2.8.10

I tried a couple of flags for more than two weeks, three different
OSMesa versions, environment tweaks, ... but never ended up with a
stable setup (as soon as server side rendering kicks in).

I can trigger that by loading a sphere, setting the remote/local
rendering threshold to 0MB.

and usually end up with an error in OpenGLInit (see attached).


Do you have any ideas?


Best regards,
Axel Huebl


-- 

Axel Huebl
Diploma Student
Phone +49 351 260 3582
https://www.hzdr.de/crp
Computational Radiation Physics
Laser Particle Acceleration Division
Helmholtz-Zentrum Dresden - Rossendorf e.V.

Bautzner Landstrasse 400, 01328 Dresden
POB 510119, D-01314 Dresden
Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey
          Prof. Dr.Dr.h.c. P. Joehnk
VR 1693 beim Amtsgericht Dresden
-------------- next part --------------
pvserver:14882 terminated with signal 11 at PC=7ffa825f2b1f SP=7fff658441b8.  Backtrace:
/lib/x86_64-linux-gnu/libc.so.6(+0x92b1f)[0x7ffa825f2b1f]
/lib/x86_64-linux-gnu/libc.so.6(+0x7d700)[0x7ffa825dd700]
/lib/x86_64-linux-gnu/libc.so.6(vsscanf+0x60)[0x7ffa825d18c0]
/lib/x86_64-linux-gnu/libc.so.6(_IO_sscanf+0x87)[0x7ffa825bd3f7]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so.1(_ZN25vtkOpenGLExtensionManager20ReadOpenGLExtensionsEv+0x200)[0x7ffa77166ec0]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so.1(_ZN25vtkOpenGLExtensionManager6UpdateEv+0x4b)[0x7ffa7716611b]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so.1(_ZN25vtkOpenGLExtensionManager18ExtensionSupportedEPKc+0x17)[0x7ffa77160f47]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so.1(_ZN21vtkOpenGLRenderWindow17OpenGLInitContextEv+0x4a)[0x7ffa771aacaa]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so.1(_ZN21vtkOpenGLRenderWindow10OpenGLInitEv+0xd)[0x7ffa771a96bd]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so.1(_ZN23vtkOSOpenGLRenderWindow5StartEv+0xd)[0x7ffa7726835d]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingCore-pv4.1.so.1(_ZN15vtkRenderWindow14DoStereoRenderEv+0x10)[0x7ffa890bd690]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingCore-pv4.1.so.1(_ZN15vtkRenderWindow10DoFDRenderEv+0x6c7)[0x7ffa890bea77]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingCore-pv4.1.so.1(_ZN15vtkRenderWindow10DoAARenderEv+0x80d)[0x7ffa890be35d]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkRenderingCore-pv4.1.so.1(_ZN15vtkRenderWindow6RenderEv+0xdf)[0x7ffa890bf90f]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkPVClientServerCoreRendering-pv4.1.so.1(_ZN15vtkPVRenderView6RenderEbb+0x5e6)[0x7ffa7da7c136]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkPVClientServerCoreRendering-pv4.1.so.1(_ZN15vtkPVRenderView11StillRenderEv+0x3c)[0x7ffa7da791fc]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkPVServerManagerApplication-pv4.1.so.1(_Z22vtkPVRenderViewCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x13e7)[0x7ffa8abbc457]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x14b)[0x7ffa86cae97b]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x14a)[0x7ffa86caec7a]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x3e6)[0x7ffa86caf6d6]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkClientServer-pv4.1.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1d)[0x7ffa86cafabd]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore21ExecuteStreamInternalERK21vtkClientServerStreamb+0xf9)[0x7ffa89bd1c39]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkPVServerImplementationCore-pv4.1.so.1(_ZN16vtkPVSessionCore30ExecuteStreamSatelliteCallbackEv+0xa5)[0x7ffa89bd2265]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkParallelCore-pv4.1.so.1(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x150)[0x7ffa860884b0]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkParallelCore-pv4.1.so.1(_ZN25vtkMultiProcessController20BroadcastProcessRMIsEii+0x79)[0x7ffa860886b9]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/libvtkParallelCore-pv4.1.so.1(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x2b5)[0x7ffa86088d85]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/pvserver(main+0x209)[0x4018e9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7ffa8258176d]
/home/huebl/bin/paraview-4.1.0-1008-g5493984/lib/paraview-4.1/pvserver[0x401951]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140705/87a78200/attachment-0001.bin>

From a.huebl at hzdr.de  Sun Jul  6 05:59:39 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Sun, 06 Jul 2014 11:59:39 +0200
Subject: [Paraview] Config OSMesa Software Rendering
In-Reply-To: <53B7E5B5.6070702@hzdr.de>
References: <53B7E5B5.6070702@hzdr.de>
Message-ID: <53B91E0B.4040603@hzdr.de>

Interesting but somehow it helps to write all the problems and steps up
again.

I fixed the issue(s) now as follows:

- tried a pvbatch example (parallelSphere.py) and fixed the python
install first, by setting:

  -DPYTHON_INCLUDE_DIR=$PYTHON_ROOT/include/python2.7
  -DPYTHON_LIBRARY=$PYTHON_ROOT/lib/libpython2.7.so

for CMake's FindPythonLib module (our system has several parallel
installed python versions, some in system paths -.- ).

- one has to set a bunch of entries in LD_LIBRARY_PATH and PYTHONPATH,
  that were:

  export LD_LIBRARY_PATH=
   $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1
  export LD_LIBRARY_PATH=
   $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1/site-packages/paraview/
  export LD_LIBRARY_PATH=
   $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1/site-packages/paraview/vtk/
  export LD_LIBRARY_PATH=
   $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1/site-packages/vtk

  export PYTHONPATH=
   $PVHOME/lib/paraview-4.1/site-packages:$PYTHONPATH
  export PYTHONPATH=
   $PVHOME/lib/paraview-4.1/site-packages/paraview:$PYTHONPATH
  export PYTHONPATH=
   $PVHOME/lib/paraview-4.1/site-packages/paraview/vtk:$PYTHONPATH
  export PYTHONPATH=
   $PVHOME/lib/paraview-4.1/site-packages/vtk:$PYTHONPATH

- realized libgl and x11 libs were still linked, e.g. in:
    ldd $BUILD/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so \
      | grep -i "gl"

  changing the CMake flags to
    -DOPENGL_gl_LIBRARY:PATH=

  helped
  (with my old setting it auto-set the systems libgl.so during config).


My full CMake flags are now (with the same dependencies as below):

  cmake \
  -DCMAKE_INSTALL_PREFIX=$HOME/bin/paraview-4.1.0-1008-g5493984  \
  -DPARAVIEW_BUILD_QT_GUI=OFF   -DBUILD_TESTING=OFF  \
  -DCMAKE_BUILD_TYPE=Debug   -DPARAVIEW_ENABLE_CATALYST=OFF  \
  -DPARAVIEW_ENABLE_PYTHON=ON \
  -DPYTHON_INCLUDE_DIR=$PYTHON_ROOT/include /python2.7 \
  -DPYTHON_LIBRARY=$PYTHON_ROOT/lib/libpython2.7.so  \
  -DPARAVIEW_USE_MPI=ON    -DPARAVIEW_USE_SYSTEM_MPI4PY=ON   \
  -DVTK_USE_X=OFF    -DOPENGL_INCLUDE_DIR=$MESA_ROOT/include   \
  -DOSMESA_INCLUDE_DIR=$MESA_ROOT/include \
  -DVTK_OPENGL_HAS_OSMESA=ON     -DOPENGL_gl_LIBRARY:PATH=  \
  -DOPENGL_glu_LIBRARY=$MESA_ROOT/lib/libGLU.so    \
  -DOSMESA_LIBRARY=$MESA_ROOT/lib/libOSMesa.so \
  -DVTK_USE_OFFSCREEN=ON    -DPARAVIEW_BUILD_PLUGIN_AdiosReader=ON  \
  -DVTK_Group_MPI=ON -DVTK_Group_Imaging=ON -DVTK_Group_Rendering=ON  \
  -DVTK_XDMF_USE_MPI=ON -DXDMF_BUILD_MPI=ON  \
  -GNinja ~/src/ParaView



Finally it's one issue left that prevents me from rendering my data in
Paraview itself.

Paraview -> Source "Sphere" -> Filter -> "Clean to Grid" and Volume
Rendering gives me a

  "ERROR: src/ParaView/VTK/Filters/Parallel/vtkPKdTree.cxx, line 295
  vtkPKdTree (0x6022160) (process 0) NumberOfDatasets = 0, cannot
  determine volume bounds."

 (same for my xdmf/hdf5 data sets).


Best regards,
Axel Huebl
On 05.07.2014 13:47, Huebl, Axel wrote:
> Hi ParaView list,
> 
> 
> I am trying to set up a offscreen rendering setup with the current
> ParaView master (g5493984) and OSMesa.
> 
> The target platform is a CPU-only cluster with several nodes, each
> containing four sockels with AMD Bulldozer CPUs (64 physical cores per
> node).
> 
> I get everything up and running in parallel, connections via rc work
> perfectly and I can load my data.
> 
> But the problems start with rendering the data. Do you have any
> recommendations which versions of OSMesa and llvmpipe are tested and stable?
> 
> The recommendations in the wiki
> 
> 
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D#OSMesa.2C_Mesa_without_graphics_hardware
> 
>   http://www.paraview.org/Wiki/ParaView/Users_Guide/Parallel_Rendering
> 
> Look a bit outdated to me.
> 
> 
> E.g.
>  - Mesa 9.2.5 (and newer versions) already split libgl and libglu
>    which versions are recommended?
>  - does OSMesa Gallium llvmpipe run with llvm X.Y (e.g. 3.3) ?
>  - what do I have to set for the DISPLAY environment with OSMesa ?
>  - is it necessary/forbidden to have a X11 server running in that setup
>    (on the server nodes)?
>  - I am confused if the mentioned "SOFTWARE_DEPTH_BITS=31" bug is
>    already fixed in mesa
>  - are some of my dependencies (OpenMPI, gcc, python) too new/old ?
> 
> I configured the server side with a whole bunch of flags now:
> 
> cmake -DCMAKE_INSTALL_PREFIX=$HOME/bin/paraview-4.1.0-1008-g5493984   \
>    -DPARAVIEW_BUILD_QT_GUI=OFF   -DBUILD_TESTING=OFF \
>    -DCMAKE_BUILD_TYPE=Debug   -DPARAVIEW_ENABLE_CATALYST=OFF \
>    -DPARAVIEW_ENABLE_PYTHON=ON   -DPARAVIEW_USE_MPI=ON \
>    -DPARAVIEW_USE_SYSTEM_MPI4PY=ON   -DVTK_USE_X=OFF \
>    -DOPENGL_INCLUDE_DIR=$MESA_ROOT/include  \
>    -DOSMESA_INCLUDE_DIR=$MESA_ROOT/include -DVTK_OPENGL_HAS_OSMESA=ON  \
>    -DOPENGL_gl_LIBRARY=IS-NOTFOUND \
>    -DOPENGL_glu_LIBRARY=$MESA_ROOT/lib/libGLU.so \
>    -DOSMESA_LIBRARY=$MESA_ROOT/lib/libOSMesa.so -DVTK_USE_OFFSCREEN=ON \
>    -DPARAVIEW_BUILD_PLUGIN_AdiosReader=ON \
>    -DVTK_Group_MPI=ON -DVTK_Group_Imaging=ON -DVTK_Group_Rendering=ON \
>    -DVTK_XDMF_USE_MPI=ON -DXDMF_BUILD_MPI=ON \
>    -GNinja ~/src/ParaView
> 
> and I am starting my servers with
> 
> mpiexec -npernode 8 -n 32 `which pvserver` --use-offscreen-rendering \
>   -sp=$NUM_PORT -rc -ch=$HEAD_NODE
> 
> and used the following separately compiled dependencies:
>   - python 2.7.5
>   - icet 2.1.1 (probably compiled again by paraview)
>   - gcc 4.8.2
>   - OpenMPI 1.7.4 (with infiniband support)
>   - cmake 2.8.10
> 
> I tried a couple of flags for more than two weeks, three different
> OSMesa versions, environment tweaks, ... but never ended up with a
> stable setup (as soon as server side rendering kicks in).
> 
> I can trigger that by loading a sphere, setting the remote/local
> rendering threshold to 0MB.
> 
> and usually end up with an error in OpenGLInit (see attached).
> 
> 
> Do you have any ideas?
> 
> 
> Best regards,
> Axel Huebl
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140706/7647f149/attachment.bin>

From a.huebl at hzdr.de  Mon Jul  7 05:01:36 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Mon, 07 Jul 2014 11:01:36 +0200
Subject: [Paraview] XDMF Join Strided: Memory Footprint
Message-ID: <53BA61F0.9020503@hzdr.de>

Hi,


I am experiencing a huge temporal memory usage by loading xdmf/hdf5 data
strided with "join" (see attached file).

While loading the "join-ed" data set, the memory usage pops up to very
high levels and when it is finished (the gui starts to react again) it
shrinks down to around few percent of it.

I am loading the "Function=JOIN(...)" set with striding "8 8 8" with
paraview which makes me wonder if the striding might get ignored for the
initial load period?

I tested the same by loading the individual components of the vector
field, each with striding, and using the "Calculator" filter to generate
the vector field.
By that the memory usage stays at a low footprint all the time.


Best regards,
Axel Huebl
-- 

Axel Huebl
Diploma Student
Phone +49 351 260 3582
https://www.hzdr.de/crp
Computational Radiation Physics
Laser Particle Acceleration Division
Helmholtz-Zentrum Dresden - Rossendorf e.V.

Bautzner Landstrasse 400, 01328 Dresden
POB 510119, D-01314 Dresden
Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey
          Prof. Dr.Dr.h.c. P. Joehnk
VR 1693 beim Amtsgericht Dresden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: join.xmf
Type: audio/x-xmf
Size: 2725 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140707/1c268a07/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140707/1c268a07/attachment-0001.bin>

From a.huebl at hzdr.de  Mon Jul  7 07:51:00 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Mon, 07 Jul 2014 13:51:00 +0200
Subject: [Paraview] Config OSMesa Software Rendering
In-Reply-To: <53B91E0B.4040603@hzdr.de>
References: <53B7E5B5.6070702@hzdr.de> <53B91E0B.4040603@hzdr.de>
Message-ID: <53BA89A4.9000904@hzdr.de>

Ok the

  NumberOfDatasets = 0, cannot determine volume bounds

can be circumvented by a "CleanToGrid" filter or any other filter that
projects the Image data to an UnstructuredGrid.

Paraview can still not render non-cubic cells / ImageData /
XDMF-3DCoRectMesh naively?


Best regards,
Axel Huebl

On 06.07.2014 11:59, Huebl, Axel wrote:
> Interesting but somehow it helps to write all the problems and steps up
> again.
> 
> I fixed the issue(s) now as follows:
> 
> - tried a pvbatch example (parallelSphere.py) and fixed the python
> install first, by setting:
> 
>   -DPYTHON_INCLUDE_DIR=$PYTHON_ROOT/include/python2.7
>   -DPYTHON_LIBRARY=$PYTHON_ROOT/lib/libpython2.7.so
> 
> for CMake's FindPythonLib module (our system has several parallel
> installed python versions, some in system paths -.- ).
> 
> - one has to set a bunch of entries in LD_LIBRARY_PATH and PYTHONPATH,
>   that were:
> 
>   export LD_LIBRARY_PATH=
>    $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1
>   export LD_LIBRARY_PATH=
>    $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1/site-packages/paraview/
>   export LD_LIBRARY_PATH=
>    $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1/site-packages/paraview/vtk/
>   export LD_LIBRARY_PATH=
>    $LD_LIBRARY_PATH:$PVHOME/lib/paraview-4.1/site-packages/vtk
> 
>   export PYTHONPATH=
>    $PVHOME/lib/paraview-4.1/site-packages:$PYTHONPATH
>   export PYTHONPATH=
>    $PVHOME/lib/paraview-4.1/site-packages/paraview:$PYTHONPATH
>   export PYTHONPATH=
>    $PVHOME/lib/paraview-4.1/site-packages/paraview/vtk:$PYTHONPATH
>   export PYTHONPATH=
>    $PVHOME/lib/paraview-4.1/site-packages/vtk:$PYTHONPATH
> 
> - realized libgl and x11 libs were still linked, e.g. in:
>     ldd $BUILD/lib/paraview-4.1/libvtkRenderingOpenGL-pv4.1.so \
>       | grep -i "gl"
> 
>   changing the CMake flags to
>     -DOPENGL_gl_LIBRARY:PATH=
> 
>   helped
>   (with my old setting it auto-set the systems libgl.so during config).
> 
> 
> My full CMake flags are now (with the same dependencies as below):
> 
>   cmake \
>   -DCMAKE_INSTALL_PREFIX=$HOME/bin/paraview-4.1.0-1008-g5493984  \
>   -DPARAVIEW_BUILD_QT_GUI=OFF   -DBUILD_TESTING=OFF  \
>   -DCMAKE_BUILD_TYPE=Debug   -DPARAVIEW_ENABLE_CATALYST=OFF  \
>   -DPARAVIEW_ENABLE_PYTHON=ON \
>   -DPYTHON_INCLUDE_DIR=$PYTHON_ROOT/include /python2.7 \
>   -DPYTHON_LIBRARY=$PYTHON_ROOT/lib/libpython2.7.so  \
>   -DPARAVIEW_USE_MPI=ON    -DPARAVIEW_USE_SYSTEM_MPI4PY=ON   \
>   -DVTK_USE_X=OFF    -DOPENGL_INCLUDE_DIR=$MESA_ROOT/include   \
>   -DOSMESA_INCLUDE_DIR=$MESA_ROOT/include \
>   -DVTK_OPENGL_HAS_OSMESA=ON     -DOPENGL_gl_LIBRARY:PATH=  \
>   -DOPENGL_glu_LIBRARY=$MESA_ROOT/lib/libGLU.so    \
>   -DOSMESA_LIBRARY=$MESA_ROOT/lib/libOSMesa.so \
>   -DVTK_USE_OFFSCREEN=ON    -DPARAVIEW_BUILD_PLUGIN_AdiosReader=ON  \
>   -DVTK_Group_MPI=ON -DVTK_Group_Imaging=ON -DVTK_Group_Rendering=ON  \
>   -DVTK_XDMF_USE_MPI=ON -DXDMF_BUILD_MPI=ON  \
>   -GNinja ~/src/ParaView
> 
> 
> 
> Finally it's one issue left that prevents me from rendering my data in
> Paraview itself.
> 
> Paraview -> Source "Sphere" -> Filter -> "Clean to Grid" and Volume
> Rendering gives me a
> 
>   "ERROR: src/ParaView/VTK/Filters/Parallel/vtkPKdTree.cxx, line 295
>   vtkPKdTree (0x6022160) (process 0) NumberOfDatasets = 0, cannot
>   determine volume bounds."
> 
>  (same for my xdmf/hdf5 data sets).
> 
> 
> Best regards,
> Axel Huebl
> On 05.07.2014 13:47, Huebl, Axel wrote:
>> Hi ParaView list,
>>
>>
>> I am trying to set up a offscreen rendering setup with the current
>> ParaView master (g5493984) and OSMesa.
>>
>> The target platform is a CPU-only cluster with several nodes, each
>> containing four sockels with AMD Bulldozer CPUs (64 physical cores per
>> node).
>>
>> I get everything up and running in parallel, connections via rc work
>> perfectly and I can load my data.
>>
>> But the problems start with rendering the data. Do you have any
>> recommendations which versions of OSMesa and llvmpipe are tested and stable?
>>
>> The recommendations in the wiki
>>
>>
>> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D#OSMesa.2C_Mesa_without_graphics_hardware
>>
>>   http://www.paraview.org/Wiki/ParaView/Users_Guide/Parallel_Rendering
>>
>> Look a bit outdated to me.
>>
>>
>> E.g.
>>  - Mesa 9.2.5 (and newer versions) already split libgl and libglu
>>    which versions are recommended?
>>  - does OSMesa Gallium llvmpipe run with llvm X.Y (e.g. 3.3) ?
>>  - what do I have to set for the DISPLAY environment with OSMesa ?
>>  - is it necessary/forbidden to have a X11 server running in that setup
>>    (on the server nodes)?
>>  - I am confused if the mentioned "SOFTWARE_DEPTH_BITS=31" bug is
>>    already fixed in mesa
>>  - are some of my dependencies (OpenMPI, gcc, python) too new/old ?
>>
>> I configured the server side with a whole bunch of flags now:
>>
>> cmake -DCMAKE_INSTALL_PREFIX=$HOME/bin/paraview-4.1.0-1008-g5493984   \
>>    -DPARAVIEW_BUILD_QT_GUI=OFF   -DBUILD_TESTING=OFF \
>>    -DCMAKE_BUILD_TYPE=Debug   -DPARAVIEW_ENABLE_CATALYST=OFF \
>>    -DPARAVIEW_ENABLE_PYTHON=ON   -DPARAVIEW_USE_MPI=ON \
>>    -DPARAVIEW_USE_SYSTEM_MPI4PY=ON   -DVTK_USE_X=OFF \
>>    -DOPENGL_INCLUDE_DIR=$MESA_ROOT/include  \
>>    -DOSMESA_INCLUDE_DIR=$MESA_ROOT/include -DVTK_OPENGL_HAS_OSMESA=ON  \
>>    -DOPENGL_gl_LIBRARY=IS-NOTFOUND \
>>    -DOPENGL_glu_LIBRARY=$MESA_ROOT/lib/libGLU.so \
>>    -DOSMESA_LIBRARY=$MESA_ROOT/lib/libOSMesa.so -DVTK_USE_OFFSCREEN=ON \
>>    -DPARAVIEW_BUILD_PLUGIN_AdiosReader=ON \
>>    -DVTK_Group_MPI=ON -DVTK_Group_Imaging=ON -DVTK_Group_Rendering=ON \
>>    -DVTK_XDMF_USE_MPI=ON -DXDMF_BUILD_MPI=ON \
>>    -GNinja ~/src/ParaView
>>
>> and I am starting my servers with
>>
>> mpiexec -npernode 8 -n 32 `which pvserver` --use-offscreen-rendering \
>>   -sp=$NUM_PORT -rc -ch=$HEAD_NODE
>>
>> and used the following separately compiled dependencies:
>>   - python 2.7.5
>>   - icet 2.1.1 (probably compiled again by paraview)
>>   - gcc 4.8.2
>>   - OpenMPI 1.7.4 (with infiniband support)
>>   - cmake 2.8.10
>>
>> I tried a couple of flags for more than two weeks, three different
>> OSMesa versions, environment tweaks, ... but never ended up with a
>> stable setup (as soon as server side rendering kicks in).
>>
>> I can trigger that by loading a sphere, setting the remote/local
>> rendering threshold to 0MB.
>>
>> and usually end up with an error in OpenGLInit (see attached).
>>
>>
>> Do you have any ideas?
>>
>>
>> Best regards,
>> Axel Huebl
>>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140707/62add743/attachment-0001.bin>

From felipe.bordeu at ec-nantes.fr  Mon Jul  7 10:36:53 2014
From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu)
Date: Mon, 07 Jul 2014 16:36:53 +0200
Subject: [Paraview] Nvidia K20x on cluster
Message-ID: <53BAB085.6010305@ec-nantes.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

We have a computer (node in a cluster) with 2 Nvidia K20x GPUs (plus a
chipset for low-end visu). Is It possible to use these GPUs to
accelerate ParaView visualization even if theses cards don't have a
video output??? I know how to use the pvserver/paraview. But my problem
is about the X11 configuration.


If I put a  'Section "Screen"' for these cards in the xorg.conf, nvidia
complains that these cards don't have outputs. and if I eliminate the
'Screen' section, the card are not available. (tried display :0, 0:0 1:0...)


Any Ideas??

Thanks
Felipe

- -- 
Felipe Bordeu Weldt
Ing?nieur de Recherche
- -------------------------------------
T?l. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
Felipe.Bordeu at ec-nantes.fr
Institut GeM - UMR CNRS 6183
?cole Centrale Nantes
1 Rue de La No?, 44321 Nantes, FRANCE
- -------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTurB+AAoJEE/fMfNgU9/DVdcH/1IYsRVTtl94L+PYqYOIgkAz
7Yx4rAFBdRVWAV8lUkFqnW/vyFNxqGcp2kuRKu/iH7cIWsEojETVbv2xcEbYaE0d
Zo/UKE1HfkAX9LFb/94igJDmgNJQXSL+QfABo+bmtpfbx+e6i63aKk+9VxRwB7t+
XEi+GKOJ0q+oQ8Rpa1J+uYWfgMQ6uPAisPQdXQWDa9sLPP4UFYi0YW60f5hzMopO
XyMHOFUVdu0NiF+Y+oqKmS44KpQt6BJHU+uHqq0Sn16DUvIuDFgdUXnFOlZM/nJU
Cya7ae2aHF+3umX7PMNeDdXjWC3NrevuZBilv9Off09XtGACyDXIG8SpnJDnd9Q=
=EaqR
-----END PGP SIGNATURE-----

From a.huebl at hzdr.de  Mon Jul  7 10:50:14 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Mon, 07 Jul 2014 16:50:14 +0200
Subject: [Paraview] Nvidia K20x on cluster
In-Reply-To: <53BAB085.6010305@ec-nantes.fr>
References: <53BAB085.6010305@ec-nantes.fr>
Message-ID: <53BAB3A6.7090604@hzdr.de>

To add to that question:

is the PISTON / Dax support in Paraview already a stable alternative to
avoid X11 at all?


Thanks,
Axel

On 07.07.2014 16:36, Felipe Bordeu wrote:
> Hello,
> 
> We have a computer (node in a cluster) with 2 Nvidia K20x GPUs (plus a
> chipset for low-end visu). Is It possible to use these GPUs to
> accelerate ParaView visualization even if theses cards don't have a
> video output??? I know how to use the pvserver/paraview. But my problem
> is about the X11 configuration.
> 
> 
> If I put a  'Section "Screen"' for these cards in the xorg.conf, nvidia
> complains that these cards don't have outputs. and if I eliminate the
> 'Screen' section, the card are not available. (tried display :0, 0:0 1:0...)
> 
> 
> Any Ideas??
> 
> Thanks
> Felipe

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140707/392ffd65/attachment.bin>

From simon.m.su.ctr at mail.mil  Mon Jul  7 11:30:37 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Mon, 7 Jul 2014 15:30:37 +0000
Subject: [Paraview] storing output calculated by python running in parallel
 - write to a file? (UNCLASSIFIED)
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7ABF@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hello,

In my python script (ran using pvbatch mypythonscript.py in parallel
environment), how do I save out the data I calculated to a file? How will be
parallel execution affect the writing of the output to a file (which process
will be doing the writing)? 

In a none parallel mode, this is what I want to do which write the output to
out.txt file.

f = open('out.txt', 'w')
print >> f, 'Filename:', filename  # or f.write('...\n')
f.close()

what is the parallel equivalent of that?

Any help is much appreciated.

Thanks
-simon




Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140707/4af3c0be/attachment.bin>

From utkarsh.ayachit at kitware.com  Mon Jul  7 11:36:14 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 7 Jul 2014 11:36:14 -0400
Subject: [Paraview] storing output calculated by python running in
 parallel - write to a file? (UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7ABF@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7ABF@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjB6eb1qoGMAWXeoc7rb87mOjCMPt+pqp4Ed5Zxoh5oE3Q@mail.gmail.com>

Simon,

If you're saving out data generated by a pipeline (which can include
Programmable filter or Python calculator), then you should use
CreateWriter(http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.simple.html#paraview.simple.CreateWriter)
to create a writer and then write the data out -- akin to "Save Data"
in ParaView.

Utkarsh

On Mon, Jul 7, 2014 at 11:30 AM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hello,
>
> In my python script (ran using pvbatch mypythonscript.py in parallel
> environment), how do I save out the data I calculated to a file? How will be
> parallel execution affect the writing of the output to a file (which process
> will be doing the writing)?
>
> In a none parallel mode, this is what I want to do which write the output to
> out.txt file.
>
> f = open('out.txt', 'w')
> print >> f, 'Filename:', filename  # or f.write('...\n')
> f.close()
>
> what is the parallel equivalent of that?
>
> Any help is much appreciated.
>
> Thanks
> -simon
>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

From simon.m.su.ctr at mail.mil  Mon Jul  7 11:52:17 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Mon, 7 Jul 2014 15:52:17 +0000
Subject: [Paraview] storing output calculated by python running in
 parallel - write to a file? (UNCLASSIFIED)
In-Reply-To: <CADHSJjB6eb1qoGMAWXeoc7rb87mOjCMPt+pqp4Ed5Zxoh5oE3Q@mail.gmail.com>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7ABF@umechp9h.easf.csd.disa.mil>
 <CADHSJjB6eb1qoGMAWXeoc7rb87mOjCMPt+pqp4Ed5Zxoh5oE3Q@mail.gmail.com>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7AF1@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hi Utkarsh,

Yes that is exactly what I wanted to do. I am using the programmable filter to 
add up all the values for a cell/point variable by iterating through the 
number of cells/points using python loop and write out the sum. Is there an 
example on how to do this? How will I format the output before writing it to 
the file? In my script below which you helped with last week, how would you 
have the paraview.simple.CreateWriter() class to write out just the sum 
variable?

Thank you very much
-simon




def calculateSum(input, output):
    # Copy the cells etc.
    output.ShallowCopy(input)

    # Get the array to calculate the coefficient
    toSum = output.GetPointData().GetArray("MOMENT_X")

    # for each of the elements, calculate the three roots and store the real 
and imaginary output in separate arrays
    numPoints = toSum.GetSize()

    tsum = 0

    for i in range(0, numPoints):
        tsum = tsum + toSum.GetValue(i)
    return tsum


input = self.GetInputDataObject(0, 0)
output = self.GetOutputDataObject(0)
sum = 0

print sum
if input.IsA("vtkUniformGridAMR"):
    # This initializes AMR properly. It will share the dataset instances
    # but we will clone those later.
    output.ShallowCopy(input)

    iter = input.NewIterator()
    iter.UnRegister(None)
    iter.InitTraversal()
    while not iter.IsDoneWithTraversal():
        curInput = iter.GetCurrentDataObject()
        curOutput = curInput.NewInstance()
        sum = sum + calculateSum(curInput, curOutput)
        output.SetDataSet(iter, curOutput)
        curOutput.UnRegister(None)
        iter.GoToNextItem();
else:
    sum = sum + calculateSum(input, output)

# write sum to file
writer = CreateWriter('foo.csv')
......







-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Monday, July 07, 2014 11:36 AM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] storing output calculated by python running in 
parallel - write to a file? (UNCLASSIFIED)

Simon,

If you're saving out data generated by a pipeline (which can include 
Programmable filter or Python calculator), then you should use
CreateWriter(http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.simple.html#paraview.simple.CreateWriter)
to create a writer and then write the data out -- akin to "Save Data"
in ParaView.

Utkarsh

On Mon, Jul 7, 2014 at 11:30 AM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hello,
>
> In my python script (ran using pvbatch mypythonscript.py in parallel
> environment), how do I save out the data I calculated to a file? How
> will be parallel execution affect the writing of the output to a file
> (which process will be doing the writing)?
>
> In a none parallel mode, this is what I want to do which write the
> output to out.txt file.
>
> f = open('out.txt', 'w')
> print >> f, 'Filename:', filename  # or f.write('...\n')
> f.close()
>
> what is the parallel equivalent of that?
>
> Any help is much appreciated.
>
> Thanks
> -simon
>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140707/f7ffcaf3/attachment-0001.bin>

From john.mangeri at uconn.edu  Mon Jul  7 14:00:00 2014
From: john.mangeri at uconn.edu (John Mangeri)
Date: Mon, 7 Jul 2014 14:00:00 -0400
Subject: [Paraview] Issue with ParaView rendering
Message-ID: <CAJC7CwaWm3cP_tcgTdx7-9VHQrZZuYtwa8SRtZ_LqCc=gPdBKA@mail.gmail.com>

I'm currently trying to compare two different mesh solution output files in
ParaView 4.1.0 Linux64bit(Ubuntu 12.04 LTS). I'm getting an strange error
that doesn't make much sense and I think may have something to do with my
settings.

I have a data range for the following variables to be rendered.

File_1:

disp_Magnitude: [0,.100]
disp_x: [-0.001,0.001]
disp_y: [-2e-5, 2e-5]
disp_z: [-0.10, 2e-6]

File_2:

disp_Magnitude: [0,.100]
disp_x: [-0.002,0.002]
disp_y: [-8e-6,0.001]
disp_z: [-0.10,0.0110]

File_2 seems to be able to be rendered fine in ParaView but File_1 is
giving me troubles. It says "Data range too small to render" in the corner
Mapping Data section. I have another program(a simple gui with my solver)
that can open these types of files(Exodus II .e format) and all is fine(no
errors, the data is there) for both File_1 and File_2. Does anyone know
what might be going on here?

A couple things I've tried

-For File_1 I tried to set a log scale for the color map transfer function
and got this error:

" Warning: Range [0,0.100038] invalid for log scaling. Changing to
[0.0100038,0.100038]."

So I know that the program sees the correct data range or does it?

-I've also looked in the information tab for my exodus object in ParaView.
It says my data ranges for all of the variables are type double [0,0] but
this is absolutely wrong since I can open the same file in my gui and view
the mesh with the correct data ranges for each of these variables. I also
think the error for log scale conflicts this statement. Why does the
information tab say [0,0] but log scale reads a range of [0,0.1]?

-If I open File_1 and then open File_2 in this order I get the same error
for File_2 that I get for File_1. Then if I change my disp_Mag variable to
disp_X the problem ceases for File_2

-Other unrelated files are giving me the same error but the data type data
range is listed as double [.05,.05]

Also I'm sure all of my settings are set to DEFAULT since I haven't changed
them at all.

Thanks for the help
John M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140707/c685461c/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jul  7 16:21:44 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 7 Jul 2014 16:21:44 -0400
Subject: [Paraview] ParaView Python problem
In-Reply-To: <CADHSJjCro4NptTuJTcFbaR0pAh+XXuVkSMv1zBDEmyFtaJn+yg@mail.gmail.com>
References: <53ABF64F.50307@tu-braunschweig.de>
 <CADHSJjBvtg_W6C_pfoLUGJWW8U2z1LtqZF=duNb1t3K+MjOSKg@mail.gmail.com>
 <CADHSJjCro4NptTuJTcFbaR0pAh+XXuVkSMv1zBDEmyFtaJn+yg@mail.gmail.com>
Message-ID: <CADHSJjDbXJCTBDQuX1XjEJG8G6rCW0EN6SG26HSujXJbAP8Raw@mail.gmail.com>

BTW, this issue has been resolved in the development version of
ParaView and the fix will be included in the next release.

Utkarsh

On Thu, Jun 26, 2014 at 7:48 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> I should have read the full email :)...ok..so this fails only with
> pvpython. I'll take a look.
>
> On Thu, Jun 26, 2014 at 7:47 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>> Ah! I think the Python calculator is corrupting the global context
>> since both, the filter and the main script run within the same Python
>> interpreter. Is this using pvpython or Python shell in the UI?
>>
>> On Thu, Jun 26, 2014 at 6:30 AM, Ian Krukow <i.krukow at tu-braunschweig.de> wrote:
>>> Hi all,
>>>
>>> I like to keep different modules apart in python, therefore I use
>>>     import paraview.simple as pv
>>> instead of
>>>     from paraview.simple import *
>>>
>>> I never had problems with this, until I included the Python Calculator in my
>>> script. Whenever I call "pv.Show()" on the Python Calculator, "pv" (my
>>> ParaView module) is overwritten with some strange function object, and with
>>> the next call of pv, I get an error. An example script is given below. I am
>>> using ParaView 4.1.0, Windows binaries.
>>>
>>> Now, there are, of course, several possibilities to prevent this from
>>> happening, but I do not see any reason for this behaviour. Any ideas?
>>>
>>> Kind regards
>>> Ian
>>>
>>>
>>> Example script:
>>>
>>> import paraview.simple as pv
>>>
>>> sphere = pv.Sphere()
>>> pv.GetRenderView()
>>> pv.Show()
>>>
>>> pycalc = pv.PythonCalculator()
>>> pycalc.Expression = 'Normals'
>>> pycalc.ArrayName = 'Deformation'
>>> pv.Show()
>>>
>>> clip = pv.Clip()
>>> pv.Show()
>>> pv.Render()
>>>
>>> On the "pv.Clip" call, I get
>>> AttributeError: 'function' object has no attribute 'Clip'
>>> It works fine in the GUI's Python Shell
>>>
>>>
>>> --
>>> Dipl.-Ing. Ian Krukow
>>> Tel +49 531 391-3673
>>>
>>> Technische Universit?t Braunschweig
>>> Institut f?r Statik/SFB 880
>>> Beethovenstr. 51
>>> 38106 Braunschweig
>>> Deutschland
>>>
>>> www.statik.tu-braunschweig.de
>>> sfb880.tu-braunschweig.de
>>> _______________________________________________
>>> 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://public.kitware.com/mailman/listinfo/paraview

From d.froning at fz-juelich.de  Tue Jul  8 02:34:39 2014
From: d.froning at fz-juelich.de (Dieter Froning)
Date: Tue, 8 Jul 2014 08:34:39 +0200
Subject: [Paraview] Issue with ParaView rendering
In-Reply-To: <CAJC7CwaWm3cP_tcgTdx7-9VHQrZZuYtwa8SRtZ_LqCc=gPdBKA@mail.gmail.com>
References: <CAJC7CwaWm3cP_tcgTdx7-9VHQrZZuYtwa8SRtZ_LqCc=gPdBKA@mail.gmail.com>
Message-ID: <1404801279.22537.11.camel@iek3102.iek.kfa-juelich.de>

dear John,

from the mathematical point of view:

a) File 1 has a very small extent in y direction. That makes it
different from File 2.

b) The disp_Magnitude looks correct, the max value  0.1 comes from the
lower disp_z value (|-0.1|=0.1). Both files.

c) The error message from log scale is correct because log(0)=-infinity.
(log(disp_Magnitude)). It needs only one hidden position with its
|value| being 0 (i.e. value=(0,0,0)).

In such cases sometimes I pick the table view (get it with "integrate
variables"), pick the column where I want to look at and sort it
ascending by clicking at the column header. In that way you may find the
data with the lowest |value|.

Good luck!
--
mit freundlichen Gruessen / best regards

D i e t e r   F r o n i n g

Institute of Energy and Climate Research (IEK)
IEK-3: Electrochemical Process Engineering
tel.: +49 2461 61-6676
fax:  +49 2461 61-6695
e-mail: d.froning at fz-juelich.de


On Mon, 2014-07-07 at 14:00 -0400, John Mangeri wrote:
> I'm currently trying to compare two different mesh solution output
> files in ParaView 4.1.0 Linux64bit(Ubuntu 12.04 LTS). I'm getting an
> strange error that doesn't make much sense and I think may have
> something to do with my settings.
>
> I have a data range for the following variables to be rendered.
>
> File_1:
>
> disp_Magnitude: [0,.100]
> disp_x: [-0.001,0.001]
> disp_y: [-2e-5, 2e-5]
> disp_z: [-0.10, 2e-6]
>
> File_2:
>
> disp_Magnitude: [0,.100]
> disp_x: [-0.002,0.002]
> disp_y: [-8e-6,0.001]
> disp_z: [-0.10,0.0110]
>
> File_2 seems to be able to be rendered fine in ParaView but File_1 is
> giving me troubles. It says "Data range too small to render" in the
> corner Mapping Data section. I have another program(a simple gui with
> my solver) that can open these types of files(Exodus II .e format) and
> all is fine(no errors, the data is there) for both File_1 and File_2.
> Does anyone know what might be going on here?
>
> A couple things I've tried
>
> -For File_1 I tried to set a log scale for the color map transfer
> function and got this error:
>
> " Warning: Range [0,0.100038] invalid for log scaling. Changing to
> [0.0100038,0.100038]."
>
> So I know that the program sees the correct data range or does it?
>
> -I've also looked in the information tab for my exodus object in
> ParaView. It says my data ranges for all of the variables are type
> double [0,0] but this is absolutely wrong since I can open the same
> file in my gui and view the mesh with the correct data ranges for each
> of these variables. I also think the error for log scale conflicts
> this statement. Why does the information tab say [0,0] but log scale
> reads a range of [0,0.1]?
>
> -If I open File_1 and then open File_2 in this order I get the same
> error for File_2 that I get for File_1. Then if I change my disp_Mag
> variable to disp_X the problem ceases for File_2
>
> -Other unrelated files are giving me the same error but the data type
> data range is listed as double [.05,.05]
>
>
> Also I'm sure all of my settings are set to DEFAULT since I haven't
> changed them at all.
>
>
> Thanks for the help
>
> John M
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview



------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------


From frank.albina at sauber-motorsport.com  Tue Jul  8 02:37:30 2014
From: frank.albina at sauber-motorsport.com (Albina, Frank)
Date: Tue, 8 Jul 2014 08:37:30 +0200
Subject: [Paraview] Nvidia K20x on cluster
In-Reply-To: <53BAB085.6010305@ec-nantes.fr>
References: <53BAB085.6010305@ec-nantes.fr>
Message-ID: <589CEB614006334D93C1A48C1B1964C9020010D102C7@srvmes03.spe-ch-md9.net>

IMHO, the issue is that you need to tell the NVIDIA driver that a screen will be connected at any time to the GPU, but you need to supply the driver with the screen data via a custom EDID file, like so in your xorg.conf file:

Section "Device"
    Identifier     "Device0"
    [...]
    Option       "CustomEDID" "DFP-0:/etc/X11/edid-DELL_P2212H.bin" 
    Option       "ConnectedMonitor" "DFP-0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    [...]
EndSection

Hope this helps.

Frank.
-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Felipe Bordeu
Sent: Montag, 7. Juli 2014 16:37
To: Paraview Mailing list (to use with ec-nantes)
Subject: [Paraview] Nvidia K20x on cluster

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

We have a computer (node in a cluster) with 2 Nvidia K20x GPUs (plus a chipset for low-end visu). Is It possible to use these GPUs to accelerate ParaView visualization even if theses cards don't have a video output??? I know how to use the pvserver/paraview. But my problem is about the X11 configuration.


If I put a  'Section "Screen"' for these cards in the xorg.conf, nvidia complains that these cards don't have outputs. and if I eliminate the 'Screen' section, the card are not available. (tried display :0, 0:0 1:0...)


Any Ideas??

Thanks
Felipe

- --
Felipe Bordeu Weldt
Ing?nieur de Recherche
- -------------------------------------
T?l. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
Felipe.Bordeu at ec-nantes.fr
Institut GeM - UMR CNRS 6183
?cole Centrale Nantes
1 Rue de La No?, 44321 Nantes, FRANCE
- -------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTurB+AAoJEE/fMfNgU9/DVdcH/1IYsRVTtl94L+PYqYOIgkAz
7Yx4rAFBdRVWAV8lUkFqnW/vyFNxqGcp2kuRKu/iH7cIWsEojETVbv2xcEbYaE0d
Zo/UKE1HfkAX9LFb/94igJDmgNJQXSL+QfABo+bmtpfbx+e6i63aKk+9VxRwB7t+
XEi+GKOJ0q+oQ8Rpa1J+uYWfgMQ6uPAisPQdXQWDa9sLPP4UFYi0YW60f5hzMopO
XyMHOFUVdu0NiF+Y+oqKmS44KpQt6BJHU+uHqq0Sn16DUvIuDFgdUXnFOlZM/nJU
Cya7ae2aHF+3umX7PMNeDdXjWC3NrevuZBilv9Off09XtGACyDXIG8SpnJDnd9Q=
=EaqR
-----END PGP SIGNATURE-----
_______________________________________________
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://public.kitware.com/mailman/listinfo/paraview

From felipe.bordeu at ec-nantes.fr  Tue Jul  8 05:33:53 2014
From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu)
Date: Tue, 08 Jul 2014 11:33:53 +0200
Subject: [Paraview] Nvidia K20x on cluster
In-Reply-To: <589CEB614006334D93C1A48C1B1964C9020010D102C7@srvmes03.spe-ch-md9.net>
References: <53BAB085.6010305@ec-nantes.fr>
 <589CEB614006334D93C1A48C1B1964C9020010D102C7@srvmes03.spe-ch-md9.net>
Message-ID: <53BBBB01.4080900@ec-nantes.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks but... K20x are only a cuda card, no graphics support.

info from :

http://comments.gmane.org/gmane.comp.video.opengl.virtualgl.user/1003


End of History

Felipe



Le 08/07/2014 08:37, Albina, Frank a ?crit :
> IMHO, the issue is that you need to tell the NVIDIA driver that a screen will be connected at any time to the GPU, but you need to supply the driver with the screen data via a custom EDID file, like so in your xorg.conf file:
> 
> Section "Device"
>     Identifier     "Device0"
>     [...]
>     Option       "CustomEDID" "DFP-0:/etc/X11/edid-DELL_P2212H.bin" 
>     Option       "ConnectedMonitor" "DFP-0"
> EndSection
> 
> Section "Screen"
>     Identifier     "Screen0"
>     Device         "Device0"
>     Monitor        "Monitor0"
>     DefaultDepth    24
>     [...]
> EndSection
> 
> Hope this helps.
> 
> Frank.
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Felipe Bordeu
> Sent: Montag, 7. Juli 2014 16:37
> To: Paraview Mailing list (to use with ec-nantes)
> Subject: [Paraview] Nvidia K20x on cluster
> 
> Hello,
> 
> We have a computer (node in a cluster) with 2 Nvidia K20x GPUs (plus a chipset for low-end visu). Is It possible to use these GPUs to accelerate ParaView visualization even if theses cards don't have a video output??? I know how to use the pvserver/paraview. But my problem is about the X11 configuration.
> 
> 
> If I put a  'Section "Screen"' for these cards in the xorg.conf, nvidia complains that these cards don't have outputs. and if I eliminate the 'Screen' section, the card are not available. (tried display :0, 0:0 1:0...)
> 
> 
> Any Ideas??
> 
> Thanks
> Felipe
> 
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
> 

- -- 
Felipe Bordeu Weldt
Ing?nieur de Recherche
- -------------------------------------
T?l. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
Felipe.Bordeu at ec-nantes.fr
Institut GeM - UMR CNRS 6183
?cole Centrale Nantes
1 Rue de La No?, 44321 Nantes, FRANCE
- -------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTu7r7AAoJEE/fMfNgU9/D3lcIAK6ky96rFngkJdwhqlyBK9LA
aOLiq80cs378HLwmqulSE4idYNXGPTBtX2KZKY5Zd6mXRq5i1LOMmCgZKHoPLy0l
66crlpd5tuqiFab796Nxqjv+hem/sXlFcaJkn2lbGAdY16FxAZYgssEipcKfIw2R
G+VOSsHYk9klAOvzy/VCC5JTxZCL+Sc34CbPRwS0Spi6Du2tdzZcr6NfMX7/7IEN
OB6Uw6yQmXVr58LlmVGXpzT5suXRpai2jeWdOe/9fDuI9AStyL4MSLbMifcT9sl7
M86UAaO9EOXkDg/IBxWeALPMADRtIGsAlHPyLFZMYQgneG6vhiACZJl7DLnsFpw=
=HG7F
-----END PGP SIGNATURE-----

From a.huebl at hzdr.de  Tue Jul  8 06:55:51 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Tue, 08 Jul 2014 12:55:51 +0200
Subject: [Paraview] Nvidia K20x on cluster
In-Reply-To: <53BBBB01.4080900@ec-nantes.fr>
References: <53BAB085.6010305@ec-nantes.fr>
 <589CEB614006334D93C1A48C1B1964C9020010D102C7@srvmes03.spe-ch-md9.net>
 <53BBBB01.4080900@ec-nantes.fr>
Message-ID: <53BBCE37.8050405@hzdr.de>

I think that is true for most cards, but K20 series should still support
to switch the "GPU Operation Mode" (GOM) via nvidia-settings:


http://blogs.fau.de/zeiser/2013/09/09/xserver-virtualgl-on-nvidia-k20m-gpgpus/

  nvidia-smi --gom=0 [...]

  (0 = ALL_ON)


Best,
Axel

On 08.07.2014 11:33, Felipe Bordeu wrote:
> Thanks but... K20x are only a cuda card, no graphics support.
> 
> info from :
> 
> http://comments.gmane.org/gmane.comp.video.opengl.virtualgl.user/1003
> 
> 
> End of History
> 
> Felipe
> 
> 
> 
> Le 08/07/2014 08:37, Albina, Frank a ?crit :
>> IMHO, the issue is that you need to tell the NVIDIA driver that a screen will be connected at any time to the GPU, but you need to supply the driver with the screen data via a custom EDID file, like so in your xorg.conf file:
> 
>> Section "Device"
>>     Identifier     "Device0"
>>     [...]
>>     Option       "CustomEDID" "DFP-0:/etc/X11/edid-DELL_P2212H.bin"
>>     Option       "ConnectedMonitor" "DFP-0"
>> EndSection
> 
>> Section "Screen"
>>     Identifier     "Screen0"
>>     Device         "Device0"
>>     Monitor        "Monitor0"
>>     DefaultDepth    24
>>     [...]
>> EndSection
> 
>> Hope this helps.
> 
>> Frank.
>> -----Original Message-----
>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Felipe Bordeu
>> Sent: Montag, 7. Juli 2014 16:37
>> To: Paraview Mailing list (to use with ec-nantes)
>> Subject: [Paraview] Nvidia K20x on cluster
> 
>> Hello,
> 
>> We have a computer (node in a cluster) with 2 Nvidia K20x GPUs (plus a chipset for low-end visu). Is It possible to use these GPUs to accelerate ParaView visualization even if theses cards don't have a video output??? I know how to use the pvserver/paraview. But my problem is about the X11 configuration.
> 
> 
>> If I put a  'Section "Screen"' for these cards in the xorg.conf, nvidia complains that these cards don't have outputs. and if I eliminate the 'Screen' section, the card are not available. (tried display :0, 0:0 1:0...)
> 
> 
>> Any Ideas??
> 
>> Thanks
>> Felipe
> 
>> _______________________________________________
>> 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://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
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
> 
> 

-- 

Axel Huebl
Diploma Student
Phone +49 351 260 3582
https://www.hzdr.de/crp
Computational Radiation Physics
Laser Particle Acceleration Division
Helmholtz-Zentrum Dresden - Rossendorf e.V.

Bautzner Landstrasse 400, 01328 Dresden
POB 510119, D-01314 Dresden
Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey
          Prof. Dr.Dr.h.c. P. Joehnk
VR 1693 beim Amtsgericht Dresden

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/1ab6460d/attachment-0001.bin>

From a.huebl at hzdr.de  Tue Jul  8 07:03:06 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Tue, 08 Jul 2014 13:03:06 +0200
Subject: [Paraview] Nvidia K20x on cluster
In-Reply-To: <53BBCE37.8050405@hzdr.de>
References: <53BAB085.6010305@ec-nantes.fr>
 <589CEB614006334D93C1A48C1B1964C9020010D102C7@srvmes03.spe-ch-md9.net>
 <53BBBB01.4080900@ec-nantes.fr> <53BBCE37.8050405@hzdr.de>
Message-ID: <53BBCFEA.6030706@hzdr.de>

Oh that's actually not true for the full k20 series.

the k20m (server modules) should support switching, the k20c
(workstations) might not.


https://devtalk.nvidia.com/default/topic/528048/k20-gpu-operation-mode-support/
  https://devtalk.nvidia.com/default/topic/534299/tesla-k20c-or-k20m-/

Probably the K20Xm should still allow to set it to ALL_ON - can you
confirm that?


Good luck!
Axel

On 08.07.2014 12:55, Huebl, Axel wrote:
> I think that is true for most cards, but K20 series should still support
> to switch the "GPU Operation Mode" (GOM) via nvidia-settings:
> 
> 
> http://blogs.fau.de/zeiser/2013/09/09/xserver-virtualgl-on-nvidia-k20m-gpgpus/
> 
>   nvidia-smi --gom=0 [...]
> 
>   (0 = ALL_ON)
> 
> 
> Best,
> Axel
> 
> On 08.07.2014 11:33, Felipe Bordeu wrote:
>> Thanks but... K20x are only a cuda card, no graphics support.
>>
>> info from :
>>
>> http://comments.gmane.org/gmane.comp.video.opengl.virtualgl.user/1003
>>
>>
>> End of History
>>
>> Felipe
>>
>>
>>
>> Le 08/07/2014 08:37, Albina, Frank a ?crit :
>>> IMHO, the issue is that you need to tell the NVIDIA driver that a screen will be connected at any time to the GPU, but you need to supply the driver with the screen data via a custom EDID file, like so in your xorg.conf file:
>>
>>> Section "Device"
>>>     Identifier     "Device0"
>>>     [...]
>>>     Option       "CustomEDID" "DFP-0:/etc/X11/edid-DELL_P2212H.bin"
>>>     Option       "ConnectedMonitor" "DFP-0"
>>> EndSection
>>
>>> Section "Screen"
>>>     Identifier     "Screen0"
>>>     Device         "Device0"
>>>     Monitor        "Monitor0"
>>>     DefaultDepth    24
>>>     [...]
>>> EndSection
>>
>>> Hope this helps.
>>
>>> Frank.
>>> -----Original Message-----
>>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Felipe Bordeu
>>> Sent: Montag, 7. Juli 2014 16:37
>>> To: Paraview Mailing list (to use with ec-nantes)
>>> Subject: [Paraview] Nvidia K20x on cluster
>>
>>> Hello,
>>
>>> We have a computer (node in a cluster) with 2 Nvidia K20x GPUs (plus a chipset for low-end visu). Is It possible to use these GPUs to accelerate ParaView visualization even if theses cards don't have a video output??? I know how to use the pvserver/paraview. But my problem is about the X11 configuration.
>>
>>
>>> If I put a  'Section "Screen"' for these cards in the xorg.conf, nvidia complains that these cards don't have outputs. and if I eliminate the 'Screen' section, the card are not available. (tried display :0, 0:0 1:0...)
>>
>>
>>> Any Ideas??
>>
>>> Thanks
>>> Felipe
>>
>>> _______________________________________________
>>> 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://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
>>
>> 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
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
> 

-- 

Axel Huebl
Diploma Student
Phone +49 351 260 3582
https://www.hzdr.de/crp
Computational Radiation Physics
Laser Particle Acceleration Division
Helmholtz-Zentrum Dresden - Rossendorf e.V.

Bautzner Landstrasse 400, 01328 Dresden
POB 510119, D-01314 Dresden
Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey
          Prof. Dr.Dr.h.c. P. Joehnk
VR 1693 beim Amtsgericht Dresden

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/92c1aad9/attachment.bin>

From a.huebl at hzdr.de  Tue Jul  8 09:56:58 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Tue, 08 Jul 2014 15:56:58 +0200
Subject: [Paraview] Render View: Edit View Options Gone?
Message-ID: <53BBF8AA.6000501@hzdr.de>

Hi,


is the Button for changing lightning, "Edit View Options", in the
"Render View" gone in the current master (g5493984) ?

The 4.1 release still has that option.

Best,
Axel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/c0b25148/attachment.bin>

From utkarsh.ayachit at kitware.com  Tue Jul  8 11:01:12 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 8 Jul 2014 11:01:12 -0400
Subject: [Paraview] Render View: Edit View Options Gone?
In-Reply-To: <53BBF8AA.6000501@hzdr.de>
References: <53BBF8AA.6000501@hzdr.de>
Message-ID: <CADHSJjDMQqFLcc7PKKpafh2a98WkMo3bFc1ABON9j7-GtYQGuA@mail.gmail.com>

Yes, "Edit View Options" is gone. You can still change the lights from
the "Properties Panel". It's an advanced property, so make sure you
have the "gear" toggled.
Check these posts out:

http://www.kitware.com/blog/home/post/621
http://www.kitware.com/blog/home/post/673
http://www.kitware.com/blog/home/post/491

Utkarsh

On Tue, Jul 8, 2014 at 9:56 AM, Huebl, Axel <a.huebl at hzdr.de> wrote:
> Hi,
>
>
> is the Button for changing lightning, "Edit View Options", in the
> "Render View" gone in the current master (g5493984) ?
>
> The 4.1 release still has that option.
>
> Best,
> Axel
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

From john.mangeri at uconn.edu  Tue Jul  8 13:42:14 2014
From: john.mangeri at uconn.edu (John Mangeri)
Date: Tue, 8 Jul 2014 13:42:14 -0400
Subject: [Paraview] Issue with ParaView rendering
In-Reply-To: <1404801279.22537.11.camel@iek3102.iek.kfa-juelich.de>
References: <CAJC7CwaWm3cP_tcgTdx7-9VHQrZZuYtwa8SRtZ_LqCc=gPdBKA@mail.gmail.com>
 <1404801279.22537.11.camel@iek3102.iek.kfa-juelich.de>
Message-ID: <CAJC7CwZCs+idX=SWd6XrPrHiAGsp+afAbC9O1+MAbnY9mqNuVQ@mail.gmail.com>

Thanks Dieter for your quick response.

Quite literally about a minute after I sent out the email to paraview.org,
I figured out what was going wrong. This was after about a week of fiddling
with it. The problem was actually not within ParaView but I had set an
option in my time independent mesh to show an initial condition which gave
time stamps of 0 AND 1. I was looking at 0 instead of 1 without realizing
the solution was on the other time stamp. I'd like to close this thread.
How do I go about doing so?

John


On Tue, Jul 8, 2014 at 2:34 AM, Dieter Froning <d.froning at fz-juelich.de>
wrote:

> dear John,
>
> from the mathematical point of view:
>
> a) File 1 has a very small extent in y direction. That makes it
> different from File 2.
>
> b) The disp_Magnitude looks correct, the max value  0.1 comes from the
> lower disp_z value (|-0.1|=0.1). Both files.
>
> c) The error message from log scale is correct because log(0)=-infinity.
> (log(disp_Magnitude)). It needs only one hidden position with its
> |value| being 0 (i.e. value=(0,0,0)).
>
> In such cases sometimes I pick the table view (get it with "integrate
> variables"), pick the column where I want to look at and sort it
> ascending by clicking at the column header. In that way you may find the
> data with the lowest |value|.
>
> Good luck!
> --
> mit freundlichen Gruessen / best regards
>
> D i e t e r   F r o n i n g
>
> Institute of Energy and Climate Research (IEK)
> IEK-3: Electrochemical Process Engineering
> tel.: +49 2461 61-6676
> fax:  +49 2461 61-6695
> e-mail: d.froning at fz-juelich.de
>
>
> On Mon, 2014-07-07 at 14:00 -0400, John Mangeri wrote:
> > I'm currently trying to compare two different mesh solution output
> > files in ParaView 4.1.0 Linux64bit(Ubuntu 12.04 LTS). I'm getting an
> > strange error that doesn't make much sense and I think may have
> > something to do with my settings.
> >
> > I have a data range for the following variables to be rendered.
> >
> > File_1:
> >
> > disp_Magnitude: [0,.100]
> > disp_x: [-0.001,0.001]
> > disp_y: [-2e-5, 2e-5]
> > disp_z: [-0.10, 2e-6]
> >
> > File_2:
> >
> > disp_Magnitude: [0,.100]
> > disp_x: [-0.002,0.002]
> > disp_y: [-8e-6,0.001]
> > disp_z: [-0.10,0.0110]
> >
> > File_2 seems to be able to be rendered fine in ParaView but File_1 is
> > giving me troubles. It says "Data range too small to render" in the
> > corner Mapping Data section. I have another program(a simple gui with
> > my solver) that can open these types of files(Exodus II .e format) and
> > all is fine(no errors, the data is there) for both File_1 and File_2.
> > Does anyone know what might be going on here?
> >
> > A couple things I've tried
> >
> > -For File_1 I tried to set a log scale for the color map transfer
> > function and got this error:
> >
> > " Warning: Range [0,0.100038] invalid for log scaling. Changing to
> > [0.0100038,0.100038]."
> >
> > So I know that the program sees the correct data range or does it?
> >
> > -I've also looked in the information tab for my exodus object in
> > ParaView. It says my data ranges for all of the variables are type
> > double [0,0] but this is absolutely wrong since I can open the same
> > file in my gui and view the mesh with the correct data ranges for each
> > of these variables. I also think the error for log scale conflicts
> > this statement. Why does the information tab say [0,0] but log scale
> > reads a range of [0,0.1]?
> >
> > -If I open File_1 and then open File_2 in this order I get the same
> > error for File_2 that I get for File_1. Then if I change my disp_Mag
> > variable to disp_X the problem ceases for File_2
> >
> > -Other unrelated files are giving me the same error but the data type
> > data range is listed as double [.05,.05]
> >
> >
> > Also I'm sure all of my settings are set to DEFAULT since I haven't
> > changed them at all.
> >
> >
> > Thanks for the help
> >
> > John M
> > _______________________________________________
> > 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://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
> ------------------------------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------------------------
> Forschungszentrum Juelich GmbH
> 52425 Juelich
> Sitz der Gesellschaft: Juelich
> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
> Prof. Dr. Sebastian M. Schmidt
>
> ------------------------------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------------------------
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/202ed261/attachment-0001.html>

From wascott at sandia.gov  Tue Jul  8 17:45:11 2014
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 8 Jul 2014 21:45:11 +0000
Subject: [Paraview] Rotational velocities
Message-ID: <9047EE0D4D3C8E43B93980DA10A073809C314CD1@EXMB04.srn.sandia.gov>

Two questions from a user.  I don't yet know if the user is using ParaView remote server.  I know that we have number 1) being implemented, but is there any other way to do it?  Any ideas on 2)?

Thanks,

Alan



1)      I want to calculate the average nodal velocity for nodes in a particular element block. How do I do that? The documentation for paraview discussing how one might do that is very confusing and not all that helpful.



2)      I want to calculate the rotational velocities of a component (block of elements) in paraview using the nodal translational velocities. How do I do that?


Thanks for your help.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/df35856a/attachment.html>

From berk.geveci at kitware.com  Tue Jul  8 19:10:11 2014
From: berk.geveci at kitware.com (Berk Geveci)
Date: Tue, 8 Jul 2014 19:10:11 -0400
Subject: [Paraview] Rotational velocities
In-Reply-To: <9047EE0D4D3C8E43B93980DA10A073809C314CD1@EXMB04.srn.sandia.gov>
References: <9047EE0D4D3C8E43B93980DA10A073809C314CD1@EXMB04.srn.sandia.gov>
Message-ID: <CAE32kpUuJQsa4ZAmQ65X_zYiE1wrhCr5dCkNX_rycjCT=8jJFw@mail.gmail.com>

It would be good to have some more clear mathematical definition of (2). I
am assuming it involves some sort of integration but it is not clear.


On Tue, Jul 8, 2014 at 5:45 PM, Scott, W Alan <wascott at sandia.gov> wrote:

>  Two questions from a user.  I don?t yet know if the user is using
> ParaView remote server.  I know that we have number 1) being implemented,
> but is there any other way to do it?  Any ideas on 2)?
>
>
>
> Thanks,
>
>
>
> Alan
>
>
>
>
>
> 1)      I want to calculate the average nodal velocity for nodes in a
> particular element block. How do I do that? The documentation for paraview
> discussing how one might do that is very confusing and not all that helpful.
>
>
>
> 2)      I want to calculate the rotational velocities of a component
> (block of elements) in paraview using the nodal translational velocities.
> How do I do that?
>
>
>
> Thanks for your help.
>
>
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/27fd1ead/attachment.html>

From wascott at sandia.gov  Tue Jul  8 19:25:02 2014
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 8 Jul 2014 23:25:02 +0000
Subject: [Paraview] [EXTERNAL] Re:  Rotational velocities
In-Reply-To: <CAE32kpUuJQsa4ZAmQ65X_zYiE1wrhCr5dCkNX_rycjCT=8jJFw@mail.gmail.com>
References: <9047EE0D4D3C8E43B93980DA10A073809C314CD1@EXMB04.srn.sandia.gov>
 <CAE32kpUuJQsa4ZAmQ65X_zYiE1wrhCr5dCkNX_rycjCT=8jJFw@mail.gmail.com>
Message-ID: <9047EE0D4D3C8E43B93980DA10A073809C314D9E@EXMB04.srn.sandia.gov>

From my user:

Alan,

I am not sure I have a good answer. Let?s say we have a block of elements moving through space that represent some component. That component is translating and rotating as a rigid body (or flexible/deformable body). I want to be able to calculate in paraview the rigid body translation and rotation of the body based on the nodal displacement or coordinate information. The nodes only include translation information since they are from hexahedral elements. I am not aware of the algorithm for performing that calculation, but I am pretty sure one exists for a rigid body (maybe even for a deformable body as well ? although in the latter case, I would guess the algorithm is not exact). Digital image correlation techniques come to mind. The DIC people perform these calculations all the time somehow. Anyway, that is what I want to be able to do. Say something like ?calculate motion of block 100? and plot the six degree of freedom translation and rotations versus time. And then save the information to an ASCII file for plotting in an external program, such as excel.

John

From: Berk Geveci [mailto:berk.geveci at kitware.com]
Sent: Tuesday, July 08, 2014 5:10 PM
To: Scott, W Alan
Cc: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Rotational velocities

It would be good to have some more clear mathematical definition of (2). I am assuming it involves some sort of integration but it is not clear.

On Tue, Jul 8, 2014 at 5:45 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
Two questions from a user.  I don?t yet know if the user is using ParaView remote server.  I know that we have number 1) being implemented, but is there any other way to do it?  Any ideas on 2)?

Thanks,

Alan



1)      I want to calculate the average nodal velocity for nodes in a particular element block. How do I do that? The documentation for paraview discussing how one might do that is very confusing and not all that helpful.



2)      I want to calculate the rotational velocities of a component (block of elements) in paraview using the nodal translational velocities. How do I do that?


Thanks for your help.



_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/68dbd46c/attachment-0001.html>

From david.thompson at kitware.com  Tue Jul  8 20:04:30 2014
From: david.thompson at kitware.com (David Thompson)
Date: Tue, 8 Jul 2014 20:04:30 -0400
Subject: [Paraview] Rotational velocities
In-Reply-To: <CAE32kpUuJQsa4ZAmQ65X_zYiE1wrhCr5dCkNX_rycjCT=8jJFw@mail.gmail.com>
References: <9047EE0D4D3C8E43B93980DA10A073809C314CD1@EXMB04.srn.sandia.gov>
 <CAE32kpUuJQsa4ZAmQ65X_zYiE1wrhCr5dCkNX_rycjCT=8jJFw@mail.gmail.com>
Message-ID: <C19FE384-2370-446E-8508-11FF696E2C36@kitware.com>

>> 2)      I want to calculate the rotational velocities of a component (block of elements) in paraview using the nodal translational velocities. How do I do that?

> It would be good to have some more clear mathematical definition of (2). I am assuming it involves some sort of integration but it is not clear.

Assuming that the elements are (mostly) undergoing rigid-body motion, you could estimate the instant center of rotation and decompose the velocity into rotational and linear components. It should only take 3 points and their velocities (in 3-D, or 2 pts in 2-D) to estimate the instant center. For the 2-D case, see

  http://emweb.unl.edu/NEGAHBAN/EM373/note16/note.htm

In 3-D, you get an axis, not a point. Having more than 3 (or 2 in 2-D) points generates a distribution of instant centers. For a deformable body, the distribution might not be anything like a point/line in space. You can imagine a pancake being flipped and see that the instantaneous angular velocity at the edges (far from the "axis of flip") would oscillate above and below that of the portion nearest the "axis of flip" -- because pancakes can curl (taco?) a good deal while flipping. How should ParaView report that? As a single angular velocity for the pancake, averaged over the entire cake? What if there are multiple pancakes? One average for each connected component? One for the full stack? :-)

For each set of nodes N_i you want to use in an estimate, you could deflect nodal coordinates by their velocity N_i' = N_i + delta_t * V_i and then compute the optimal rotation matrix using the Kabsch algorithm:

  http://en.wikipedia.org/wiki/Kabsch_algorithm

From the optimal rotation matrix, you can choose the eigenvector with the largest eigenvalue and use it as an estimate of the instant center of rotation. With the instant center, you can then decompose each nodal velocity into an angular velocity magnitude and linear velocity magnitude -- and average over all the nodes in a connected component/block/full stack.

	David

From kmorel at sandia.gov  Tue Jul  8 20:04:42 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 9 Jul 2014 00:04:42 +0000
Subject: [Paraview] [EXTERNAL] Re:  Rotational velocities
In-Reply-To: <9047EE0D4D3C8E43B93980DA10A073809C314D9E@EXMB04.srn.sandia.gov>
Message-ID: <CFE1DF55.19701%kmorel@sandia.gov>

I've never done this, and maybe there is an existing established way to do it, but a simple Google search did not reveal it. Here is what I think from my understanding of the movement of rigid bodies.

First, the rotation only makes sense around some fixed point. For example, OpenGL defines all rotations around the origin of the coordinate system, but I'm sure that is not what John is after. I'm guessing that he would probably be interested in rotations around the center of mass. An average of all the point coordinates might be a close enough approximation to the center of mass.

Next, find the translation of the rigid body by looking at the displacement at the center of mass. That displacement is the translation. Now subtract that translation vector from all the displacements to get what I will call the rotation displacement (a term I just made up).

Now you can use any of these rotation displacements to find the rotation. Technically any one displacement will give you the rotation (because it is a rigid body), but you should pick one far away from the axis of rotation. Just find one with a large rotation displacement and that would be fine. Consider the vector from the center of mass to the original point and the vector from the center of mass to the point moved by the rotation displacement. The cross product of those two vectors should be in the direction of the axis of rotation and its length is equal to the product of the lengths of those two vectors times the sine of the angle of rotation.

-Ken

From: <Scott>, Walter Scott <wascott at sandia.gov<mailto:wascott at sandia.gov>>
Date: Tuesday, July 8, 2014 5:25 PM
To: Berk Geveci <berk.geveci at kitware.com<mailto:berk.geveci at kitware.com>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: Re: [Paraview] [EXTERNAL] Re: Rotational velocities

>From my user:

Alan,

I am not sure I have a good answer. Let?s say we have a block of elements moving through space that represent some component. That component is translating and rotating as a rigid body (or flexible/deformable body). I want to be able to calculate in paraview the rigid body translation and rotation of the body based on the nodal displacement or coordinate information. The nodes only include translation information since they are from hexahedral elements. I am not aware of the algorithm for performing that calculation, but I am pretty sure one exists for a rigid body (maybe even for a deformable body as well ? although in the latter case, I would guess the algorithm is not exact). Digital image correlation techniques come to mind. The DIC people perform these calculations all the time somehow. Anyway, that is what I want to be able to do. Say something like ?calculate motion of block 100? and plot the six degree of freedom translation and rotations versus time. And then save the information to an ASCII file for plotting in an external program, such as excel.

John

From: Berk Geveci [mailto:berk.geveci at kitware.com]
Sent: Tuesday, July 08, 2014 5:10 PM
To: Scott, W Alan
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] Rotational velocities

It would be good to have some more clear mathematical definition of (2). I am assuming it involves some sort of integration but it is not clear.

On Tue, Jul 8, 2014 at 5:45 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
Two questions from a user.  I don?t yet know if the user is using ParaView remote server.  I know that we have number 1) being implemented, but is there any other way to do it?  Any ideas on 2)?

Thanks,

Alan



1)      I want to calculate the average nodal velocity for nodes in a particular element block. How do I do that? The documentation for paraview discussing how one might do that is very confusing and not all that helpful.



2)      I want to calculate the rotational velocities of a component (block of elements) in paraview using the nodal translational velocities. How do I do that?


Thanks for your help.



_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/067f1ad3/attachment.html>

From david.thompson at kitware.com  Tue Jul  8 20:52:37 2014
From: david.thompson at kitware.com (David Thompson)
Date: Tue, 8 Jul 2014 20:52:37 -0400
Subject: [Paraview] [EXTERNAL] Re:  Rotational velocities
In-Reply-To: <CFE1DF55.19701%kmorel@sandia.gov>
References: <CFE1DF55.19701%kmorel@sandia.gov>
Message-ID: <039957D0-2FE0-4442-AB65-0A776C6E6049@kitware.com>

> I've never done this, and maybe there is an existing established way to do it, but a simple Google search did not reveal it.

The proper Google search phrase to find mechanical engineering sites is "instant center of rotation". Most of them deal with 2-D though, as that's what's covered in undergraduate mechanics. If you find an advanced mechanics book (or an aerospace mechanics book), you should find the 3-D case.

> ... I'm guessing that he would probably be interested in rotations around the center of mass.

I think it's more likely for someone to be interested in the rotation about the instant center than the center of mass, but the angular velocity about the center of mass is also a useful thing to know. (It is also nice to know the moment of inertia about whatever axis you are dealing with because then you can estimate rotational kinetic energy as I\omega^2 and the linear kinetic energy as m*v^2 and compare the two.)

> An average of all the point coordinates might be a close enough approximation to the center of mass.

I would be nervous about using that approximation in a general-purpose tool because the angular velocities that result can vary significantly for small changes in the position of the center of mass when velocity is large.

You could use the mesh quality filter and cell-center filters to avoid bias from the mesh. Or do a least squares fit to the instant center of rotation and the angular velocity all at once.

> Next, find the translation of the rigid body by looking at the displacement at the center of mass. That displacement is the translation. Now subtract that translation vector from all the displacements to get what I will call the rotation displacement (a term I just made up).

If the body is deforming (or the element block contains independently-moving disjoint bodies), both the estimated displacement and your "rotation displacement" include variations due to non-rigid deflections.

> Now you can use any of these rotation displacements to find the rotation. Technically any one displacement will give you the rotation (because it is a rigid body), but you should pick one far away from the axis of rotation.

The problem I have with this is that -- assuming non-rigid deflections are significant -- the ones far from the axis of rotation are likely the ones most affected by non-rigid-body deflections.

	David


From cchukw1 at tigers.lsu.edu  Wed Jul  9 00:01:04 2014
From: cchukw1 at tigers.lsu.edu (Chukwudi Chukwudozie)
Date: Tue, 8 Jul 2014 23:01:04 -0500
Subject: [Paraview] Extracting results from python
Message-ID: <CANPyyBLAdDYSabpiJqvsqsAqp37Ob1kJFWiGM88_EEiajWqXMw@mail.gmail.com>

Hi,

I'm pretty new in paraview python scripting and I'm trying my hand on an
example to IntegrateVariables along a slice (plane). However, I don't know
how to extract the results of the Integrate pipeline as when I ask to
print, all I get is a memory address. Below is a snapshot of my s=python
script. Basically, after calling, IntegrateVariables0 = IntegrateVariables(
Calculator0 ), I want to be able to use the result of the integration for
other operations. How do I access it, or the syntax to use.

Slice0 = Slice()

Slice0.SliceType = "Plane"

Slice0 = GetActiveSource()

Slice0.SliceType.Origin = [0.5, 0.005, 0.5]

Slice0.SliceType.Normal = [1.0, 0.0, 0.0]

Calculator0 = Calculator( Slice0 )

Calculator0.Function = 'Volumetric Crack Opening'

IntegrateVariables0 = IntegrateVariables( Calculator0 )

print IntegrateVariables0




Chuks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140708/a405ce9a/attachment-0001.html>

From a.huebl at hzdr.de  Wed Jul  9 07:01:14 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Wed, 09 Jul 2014 13:01:14 +0200
Subject: [Paraview] Render View: Edit View Options Gone?
In-Reply-To: <CADHSJjDMQqFLcc7PKKpafh2a98WkMo3bFc1ABON9j7-GtYQGuA@mail.gmail.com>
References: <53BBF8AA.6000501@hzdr.de>
 <CADHSJjDMQqFLcc7PKKpafh2a98WkMo3bFc1ABON9j7-GtYQGuA@mail.gmail.com>
Message-ID: <53BD20FA.4020001@hzdr.de>

Ah, there it is!
  Left Panel "Properties" -> "Advanced (gear)".

Thank you,
Axel

On 08.07.2014 17:01, Utkarsh Ayachit wrote:
> Yes, "Edit View Options" is gone. You can still change the lights from
> the "Properties Panel". It's an advanced property, so make sure you
> have the "gear" toggled.
> Check these posts out:
> 
> http://www.kitware.com/blog/home/post/621
> http://www.kitware.com/blog/home/post/673
> http://www.kitware.com/blog/home/post/491
> 
> Utkarsh
> 
> On Tue, Jul 8, 2014 at 9:56 AM, Huebl, Axel <a.huebl at hzdr.de> wrote:
>> Hi,
>>
>>
>> is the Button for changing lightning, "Edit View Options", in the
>> "Render View" gone in the current master (g5493984) ?
>>
>> The 4.1 release still has that option.
>>
>> Best,
>> Axel
>>
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
> 
> 

-- 

Axel Huebl
Diploma Student
Phone +49 351 260 3582
https://www.hzdr.de/crp
Computational Radiation Physics
Laser Particle Acceleration Division
Helmholtz-Zentrum Dresden - Rossendorf e.V.

Bautzner Landstrasse 400, 01328 Dresden
POB 510119, D-01314 Dresden
Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey
          Prof. Dr.Dr.h.c. P. Joehnk
VR 1693 beim Amtsgericht Dresden

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4921 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/a588fa01/attachment.bin>

From louie.cardone-noott at linacre.ox.ac.uk  Wed Jul  9 08:18:13 2014
From: louie.cardone-noott at linacre.ox.ac.uk (Louie Cardone-Noott)
Date: Wed, 9 Jul 2014 13:18:13 +0100
Subject: [Paraview] Changing displayed dataset in python interface
Message-ID: <CAOCDKs8rVYVq=+O3kM83e5PpmHLYLGOVtLYkATFBeB4JrL995Q@mail.gmail.com>

Hi paraview list,

First post here - hope I'm doing it right!

I've been fighting with the python interface to generate images from
several views (rotated around) of a number of datasets. I'm stuck on the
latter point. The outline of my script is as follows:

# Start pseudo-code
# Load
RenderView1 = CreateRenderView()
results_pvtu = XMLPartitionedUnstructuredGridReader( ... )

# Make two lookup tables and scalar bars
UpstrokeLookupTable = GetLookupTableForArray( "UpstrokeTimeMap_0_000000",
... )
UpstrokeBarRep = CreateScalarBar( ... )
UpstrokeBarRep.LookupTable = UpstrokeLookupTable
ApdLookupTable = GetLookupTableForArray( "Apd_90_0_Map_000000", ... )
ApdBarRep = CreateScalarBar( ... )
ApdBarRep.LookupTable = ApdLookupTable

# Threshold results first
Threshold1 = Threshold()
Show()
ResetCamera() # To get the zoom roughly right

# Display first dataset
threshold_rep.ColorArrayName = 'UpstrokeTimeMap_0_000000'
threshold_rep.LookupTable = UpstrokeLookupTable
RenderView1.Representations.append(UpstrokeBarRep)

# Rotate camera and save a series of images
RenderView1.CameraViewUp = [...]
RenderView1.CameraClippingRange = [...]
RenderView1.CameraPosition = [...]
Render()
WriteImage(...)

# Delete first scalar bar and change dataset
Delete(RenderView1.Representations[1]) # 0 is the results, 1 is the scalar
bar
threshold_rep.ColorArrayName = 'Apd_90_0_Map_000000'
threshold_rep.LookupTable = ApdLookupTable
RenderView1.Representations.append(ApdBarRep)

# Rotate camera and save a series of images
RenderView1.CameraViewUp ... etc.

# End pseudo-code

The images from the first dataset ('UpstrokeTimeMap_0_000000') look normal,
but in the second set ('Apd_90_0_Map_000000') the colours are all weird and
jaggy with similarities to both datasets, a bit like it's trying to display
them both.

The python trace doesn't help as it generates similar code to the above.

I was wondering if there might be a smarter way to do this. The
"representations and views" bit of the python guide looks promising but I
don't quite see how.
http://www.paraview.org/Wiki/ParaView/Python_Scripting#Representations_and_Views

Thanks for assistance.

Louie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/37952576/attachment.html>

From jeremy.santina at gmail.com  Wed Jul  9 08:26:19 2014
From: jeremy.santina at gmail.com (=?UTF-8?B?SsOpcsOpbXkgU2FudGluYQ==?=)
Date: Wed, 9 Jul 2014 14:26:19 +0200
Subject: [Paraview] How to speed up data reading
Message-ID: <CAAPOYrFkOUvuJLy27BdVOFfk6d=8_YWO8BfArHM3m2kwn+-npA@mail.gmail.com>

Good afternoon,

I am working with ParaView in parallel and I am trying to vizualise a big
data as efficiently as possible. I am reading Tecplot Binary Files (.plt).
For now, I am simply using a computer as a pvserver and my data is stored
via NFS.

When I am launching the vizualisation, I notice that it is very slow.
Looking at the Timer Log, I understood that is because the reading is
taking a lot of time. I think it is mainly because the reader used is not
implemented to work in parallel and only one process can read the data.

So here are my questions :
  - Considering the Tecplot Binary File Format, is it possible to write a
parallel reader ?
  - Does NFS considerably slow down the reading ?
  - Is there any other issues that could cause a slow reading ? In that
case, how could I fix it ?

Thank you in advance for your help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/cb287547/attachment.html>

From richard.c.angelini.civ at mail.mil  Wed Jul  9 09:02:11 2014
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US))
Date: Wed, 9 Jul 2014 13:02:11 +0000
Subject: [Paraview] connectivity errors
Message-ID: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>

I?m setting up Paraview client/server  on a new Cray XC30 system.   I have
a totally clean build on Paraview on the Cray side, but I can?t get the
client-server connection to work, and I?m seeing a strange error.   It
looks like the client-server connection is being established, and then the
client crashes with this error:

Accepting connection(s): my-client-host:53484
ERROR: In 
/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/
paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefi
nitionManager.cxx, line 565
vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
group=misc and proxy=StrictLoadBalancing were found.


Segmentation fault



On the server side,  I?m getting a more standard connectivity error:

Client connected.
ERROR: In 
/p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/C
ore/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0xe2b930): Could not receive tag. 1


I know that the communication path from the compute nodes to the client
workstation is valid because VisIt and Ensight both work on this system.

Any ideas?



________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266



From utkarsh.ayachit at kitware.com  Wed Jul  9 09:18:24 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 9 Jul 2014 09:18:24 -0400
Subject: [Paraview] connectivity errors
In-Reply-To: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>
References: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjADLiZrDw971c-fSGUDkBnZx5rHA0Ja=mYq=hBDnRdKvA@mail.gmail.com>

Looks like you're using git/master client with 4.1 server or
vice-versa. Is that the case?

Utkarsh

On Wed, Jul 9, 2014 at 9:02 AM, Angelini, Richard C (Rick) CIV USARMY
ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> I?m setting up Paraview client/server  on a new Cray XC30 system.   I have
> a totally clean build on Paraview on the Cray side, but I can?t get the
> client-server connection to work, and I?m seeing a strange error.   It
> looks like the client-server connection is being established, and then the
> client crashes with this error:
>
> Accepting connection(s): my-client-host:53484
> ERROR: In
> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/
> paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefi
> nitionManager.cxx, line 565
> vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
> group=misc and proxy=StrictLoadBalancing were found.
>
>
> Segmentation fault
>
>
>
> On the server side,  I?m getting a more standard connectivity error:
>
> Client connected.
> ERROR: In
> /p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/C
> ore/vtkSocketCommunicator.cxx, line 812
> vtkSocketCommunicator (0xe2b930): Could not receive tag. 1
>
>
> I know that the communication path from the compute nodes to the client
> workstation is valid because VisIt and Ensight both work on this system.
>
> Any ideas?
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview

From richard.c.angelini.civ at mail.mil  Wed Jul  9 09:15:00 2014
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US))
Date: Wed, 9 Jul 2014 13:15:00 +0000
Subject: [Paraview] connectivity errors
In-Reply-To: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>
References: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CFE2B7FE.DA58%Richard.C.Angelini.CIV@mail.mil>

I forgot to include that I get the same behavior on both an OSX and Linux
ParaView client - so I don?t think that it?s a client-side software issue.
  But, what I don?t understand is what could happen on the server side to
crash the client?

I think that my cmake/build command is pretty straight forward an
essentially identical to the cmake command I?ve used on other Cray systems:

cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
-DParaView_FROM_GIT=ON \
-DENABLE_boost=ON \
-DENABLE_cgns=OFF \
-DENABLE_ffmpeg=ON \
-DENABLE_fontconfig=ON \
-DENABLE_freetype=ON \
-DENABLE_hdf5=ON \
-DENABLE_libxml2=ON \
-DENABLE_matplotlib=OFF \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_osmesa=ON \
-DENABLE_paraview=ON \
-DENABLE_png=ON \
-DENABLE_python=ON \
-DENABLE_qhull=ON \
-DENABLE_qt=OFF \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-DENABLE_visitbridge=ON \
-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
ichcxx.so" \
-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
h.so" \
-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc
xx.so" \
-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
e/" \
-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/
" \
-DUSE_SYSTEM_mpi=ON \
-DUSE_SYSTEM_python=ON \
-DUSE_SYSTEM_zlib=ON \
../Source



________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




On 7/9/14, 9:02 AM, "Angelini, Richard C (Rick) CIV USARMY ARL (US)"
<richard.c.angelini.civ at mail.mil> wrote:

>I?m setting up Paraview client/server  on a new Cray XC30 system.   I have
>a totally clean build on Paraview on the Cray side, but I can?t get the
>client-server connection to work, and I?m seeing a strange error.   It
>looks like the client-server connection is being established, and then the
>client crashes with this error:
>
>Accepting connection(s): my-client-host:53484
>ERROR: In 
>/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release
>/
>paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDef
>i
>nitionManager.cxx, line 565
>vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
>group=misc and proxy=StrictLoadBalancing were found.
>
>
>Segmentation fault
>
>
>
>On the server side,  I?m getting a more standard connectivity error:
>
>Client connected.
>ERROR: In 
>/p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/
>C
>ore/vtkSocketCommunicator.cxx, line 812
>vtkSocketCommunicator (0xe2b930): Could not receive tag. 1
>
>
>I know that the communication path from the compute nodes to the client
>workstation is valid because VisIt and Ensight both work on this system.
>
>Any ideas?
>
>
>
>________________________________
>Rick Angelini
>USArmy Research Laboratory
>CISD/HPC Architectures Team
>Phone:  410-278-6266
>
>


From jfavre at cscs.ch  Wed Jul  9 10:28:07 2014
From: jfavre at cscs.ch (Favre  Jean)
Date: Wed, 9 Jul 2014 14:28:07 +0000
Subject: [Paraview] connectivity errors
In-Reply-To: <CFE2B7FE.DA58%Richard.C.Angelini.CIV@mail.mil>
References: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>,
 <CFE2B7FE.DA58%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F681AA16E13@MBX21.d.ethz.ch>


I had the same crash yesterday on our Cray XC30 while connecting a 4.1 client with a 4.2 server. Everything worked fine (i.e. I am now using the latest git checkout) after I updated both sides.

-----------------
Jean 
CSCS

From bloring at lbl.gov  Wed Jul  9 11:32:33 2014
From: bloring at lbl.gov (Burlen Loring)
Date: Wed, 09 Jul 2014 08:32:33 -0700
Subject: [Paraview] How to speed up data reading
In-Reply-To: <CAAPOYrFkOUvuJLy27BdVOFfk6d=8_YWO8BfArHM3m2kwn+-npA@mail.gmail.com>
References: <CAAPOYrFkOUvuJLy27BdVOFfk6d=8_YWO8BfArHM3m2kwn+-npA@mail.gmail.com>
Message-ID: <53BD6091.6050305@lbl.gov>


>   - Considering the Tecplot Binary File Format, is it possible to 
> write a parallel reader ?
yes
>   - Does NFS considerably slow down the reading ?
yes


On 07/09/2014 05:26 AM, J?r?my Santina wrote:
> Good afternoon,
>
> I am working with ParaView in parallel and I am trying to vizualise a 
> big data as efficiently as possible. I am reading Tecplot Binary Files 
> (.plt). For now, I am simply using a computer as a pvserver and my 
> data is stored via NFS.
>
> When I am launching the vizualisation, I notice that it is very slow. 
> Looking at the Timer Log, I understood that is because the reading is 
> taking a lot of time. I think it is mainly because the reader used is 
> not implemented to work in parallel and only one process can read the 
> data.
>
> So here are my questions :
>   - Considering the Tecplot Binary File Format, is it possible to 
> write a parallel reader ?
>   - Does NFS considerably slow down the reading ?
>   - Is there any other issues that could cause a slow reading ? In 
> that case, how could I fix it ?
>
> Thank you in advance for your help.
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/f4d07667/attachment.html>

From simon.m.su.ctr at mail.mil  Wed Jul  9 14:06:15 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Wed, 9 Jul 2014 18:06:15 +0000
Subject: [Paraview] python script to rotate a view (UNCLASSIFIED)
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CD5842@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hello,

If I open up ParaView and Source->Box, I will get a box in the view. Is
there an example python script that will allow me to rotate my view around
the box? I will eventually add this to animation rendering of a more
complicated dataset. 

Any help is much appreciated... 

Thanks
-simon

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/ea7be8ba/attachment.bin>

From utkarsh.ayachit at kitware.com  Wed Jul  9 15:21:28 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 9 Jul 2014 15:21:28 -0400
Subject: [Paraview] python script to rotate a view (UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CD5842@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CD5842@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjBo_WLVqyjGyXk-1=ZWB6CwdCaguRDKUX5Kj6KX+PZ3aQ@mail.gmail.com>

Attached is a sample. For the most part it was obtained by using the
"tracing" capabilities and adding a camera orbit animation. There's a
bug in the tracing code that is missed the adding of KeyFrames to the
CameraAnimationCue1 proxy as indicated in the script.

BTW, we are working on revamping the Python tracing entirely to better
trace the user actions as well as produce more readable scripts.

Utkarsh

On Wed, Jul 9, 2014 at 2:06 PM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hello,
>
> If I open up ParaView and Source->Box, I will get a box in the view. Is
> there an example python script that will allow me to rotate my view around
> the box? I will eventually add this to animation rendering of a more
> complicated dataset.
>
> Any help is much appreciated...
>
> Thanks
> -simon
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foo.py
Type: text/x-python
Size: 1182 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/fd16b061/attachment-0001.py>

From simon.m.su.ctr at mail.mil  Wed Jul  9 15:38:04 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Wed, 9 Jul 2014 19:38:04 +0000
Subject: [Paraview] python script to rotate a view (UNCLASSIFIED)
In-Reply-To: <CADHSJjBo_WLVqyjGyXk-1=ZWB6CwdCaguRDKUX5Kj6KX+PZ3aQ@mail.gmail.com>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CD5842@umechp9h.easf.csd.disa.mil>
 <CADHSJjBo_WLVqyjGyXk-1=ZWB6CwdCaguRDKUX5Kj6KX+PZ3aQ@mail.gmail.com>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CD5910@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hi Utkarsh,

Thank you.... it worked.....

Great... I am looking forward to the improved python tracing...

Thanks
-simon

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Wednesday, July 09, 2014 3:21 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] python script to rotate a view (UNCLASSIFIED)

Attached is a sample. For the most part it was obtained by using the "tracing" 
capabilities and adding a camera orbit animation. There's a bug in the tracing 
code that is missed the adding of KeyFrames to the
CameraAnimationCue1 proxy as indicated in the script.

BTW, we are working on revamping the Python tracing entirely to better trace 
the user actions as well as produce more readable scripts.

Utkarsh

On Wed, Jul 9, 2014 at 2:06 PM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hello,
>
> If I open up ParaView and Source->Box, I will get a box in the view.
> Is there an example python script that will allow me to rotate my view
> around the box? I will eventually add this to animation rendering of a
> more complicated dataset.
>
> Any help is much appreciated...
>
> Thanks
> -simon
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/d2fd1fd9/attachment.bin>

From berk.geveci at kitware.com  Wed Jul  9 16:02:24 2014
From: berk.geveci at kitware.com (Berk Geveci)
Date: Wed, 9 Jul 2014 16:02:24 -0400
Subject: [Paraview] Extracting results from python
In-Reply-To: <CANPyyBLAdDYSabpiJqvsqsAqp37Ob1kJFWiGM88_EEiajWqXMw@mail.gmail.com>
References: <CANPyyBLAdDYSabpiJqvsqsAqp37Ob1kJFWiGM88_EEiajWqXMw@mail.gmail.com>
Message-ID: <CAE32kpXuzEuXHzEJSK83OepkUKCuyM3Ya1D2f3qLjcDOFNpL2g@mail.gmail.com>

You need something like this:

print IntegrateVariables0.PointData['xxx'].GetRange()

where xxx is the name of the array you are integrating.

Best,
-berk


On Wed, Jul 9, 2014 at 12:01 AM, Chukwudi Chukwudozie <
cchukw1 at tigers.lsu.edu> wrote:

> Hi,
>
> I'm pretty new in paraview python scripting and I'm trying my hand on an
> example to IntegrateVariables along a slice (plane). However, I don't know
> how to extract the results of the Integrate pipeline as when I ask to
> print, all I get is a memory address. Below is a snapshot of my s=python
> script. Basically, after calling, IntegrateVariables0 = IntegrateVariables(
> Calculator0 ), I want to be able to use the result of the integration for
> other operations. How do I access it, or the syntax to use.
>
> Slice0 = Slice()
>
> Slice0.SliceType = "Plane"
>
> Slice0 = GetActiveSource()
>
> Slice0.SliceType.Origin = [0.5, 0.005, 0.5]
>
> Slice0.SliceType.Normal = [1.0, 0.0, 0.0]
>
> Calculator0 = Calculator( Slice0 )
>
> Calculator0.Function = 'Volumetric Crack Opening'
>
> IntegrateVariables0 = IntegrateVariables( Calculator0 )
>
> print IntegrateVariables0
>
>
>
>
> Chuks
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/c6d8b30c/attachment.html>

From rjk at lanl.gov  Wed Jul  9 18:06:32 2014
From: rjk at lanl.gov (Kares, Robert J)
Date: Wed, 9 Jul 2014 22:06:32 +0000
Subject: [Paraview] Resampling to a uniform grid
In-Reply-To: <887FEBB138D1F24695067B7E85A6A4F645A66634@ECS-EXG-P-MB03.win.lanl.gov>
References: <887FEBB138D1F24695067B7E85A6A4F645A66634@ECS-EXG-P-MB03.win.lanl.gov>
Message-ID: <887FEBB138D1F24695067B7E85A6A4F645A6667C@ECS-EXG-P-MB03.win.lanl.gov>

Folks,

I would like to resample a scalar field defined on an unstructured
grid in 3D onto a uniform rectangular 3D grid with specified logical and
physical dimensions.

It seems from the ParaView filters documentation that this can
somehow be done using the Resample With Dataset filter. It appears
to me that the procedure involves generating a uniform rectangular
grid in some fashion and then feeding it to the Resample With Dataset
filter along with the unstructured grid containing the scalar to be
resampled.

However, I am confused about just how to make the rectangular grid of
specified size in the first place and about how to use it with the Resample With Dataset
filter.

Could someone explain to me how to do this ?

Thanks,

                                       --Bob


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140709/0c439aa6/attachment.html>

From joachim.pouderoux at kitware.com  Thu Jul 10 04:00:15 2014
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Thu, 10 Jul 2014 10:00:15 +0200
Subject: [Paraview] ANN: VTK/ParaView Training Course in Lyon, France,
 September 30th & October 1st, 2014
Message-ID: <CACJ=gTjO8+-D7=9-1+q6MjLk6yWagTMVm1zj_QF_iERY7tX9BA@mail.gmail.com>

Kitware will be holding a 2-day VTK and ParaView course on September 30th
and October 1st,
2014 in Lyon, France.

Please visit our web site for more information and registration details at
either:

http://training.kitware.fr/browse/24 <http://training.kitware.fr/browse/48>
(in English)
or
http://formations.kitware.fr/browse/24
<http://formations.kitware.fr/browse/48>(in French)

Note that the course will be taught in English. If you have any question,
please contact us at formations at http://www.kitware.fr

Thank you,

*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/d31aada4/attachment-0001.html>

From dave.demarle at kitware.com  Thu Jul 10 09:17:23 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 10 Jul 2014 09:17:23 -0400
Subject: [Paraview] Resampling to a uniform grid
In-Reply-To: <887FEBB138D1F24695067B7E85A6A4F645A6667C@ECS-EXG-P-MB03.win.lanl.gov>
References: <887FEBB138D1F24695067B7E85A6A4F645A66634@ECS-EXG-P-MB03.win.lanl.gov>
 <887FEBB138D1F24695067B7E85A6A4F645A6667C@ECS-EXG-P-MB03.win.lanl.gov>
Message-ID: <CANjZAi8PcPULbG-8UkcDCXCv5CHgC0ctM9ixEsyWNaUb9p0edg@mail.gmail.com>

You could start with Sources->Wavelet and reposition it as needed, but I'ld
use a python programmable source. Attached is a state file to demonstrate.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jul 9, 2014 at 6:06 PM, Kares, Robert J <rjk at lanl.gov> wrote:

>  Folks,
>
>
>
> I would like to resample a scalar field defined on an unstructured
>
> grid in 3D onto a uniform rectangular 3D grid with specified logical and
>
> physical dimensions.
>
>
>
> It seems from the ParaView filters documentation that this can
>
> somehow be done using the Resample With Dataset filter. It appears
>
> to me that the procedure involves generating a uniform rectangular
>
> grid in some fashion and then feeding it to the Resample With Dataset
>
> filter along with the unstructured grid containing the scalar to be
>
> resampled.
>
>
>
> However, I am confused about just how to make the rectangular grid of
>
> specified size in the first place and about how to use it with the
> Resample With Dataset
>
> filter.
>
>
>
> Could someone explain to me how to do this ?
>
>
>
> Thanks,
>
>
>
>                                        --Bob
>
>
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/68aac984/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ResampleWithData.pvsm
Type: application/octet-stream
Size: 177626 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/68aac984/attachment-0001.obj>

From cgomez0000 at yahoo.com  Thu Jul 10 10:33:09 2014
From: cgomez0000 at yahoo.com (Carla Gomez)
Date: Thu, 10 Jul 2014 07:33:09 -0700
Subject: [Paraview] velocity arrows and stream lines from Fluent .cas and
	.dat file
Message-ID: <1405002789.56621.YahooMailNeo@web125203.mail.ne1.yahoo.com>

I have cas and dat files from Fluent that I have opened via the .cas file in ParaView.? I converted the velocity data to vector form via the calculator, since it comes in in scalar form.? My goal is to get velocity arrows (glyph) and stream lines.? What I get instead are random arrow that do not make since to what is seen in Fluent.? The stream lines are non-existent.? Has anyone had success with this?? If so, can you help guide me in the process to achieve arrow and streamlines, if it is possible?

Thank you,
Carla Gomez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/fba055df/attachment.html>

From d.froning at fz-juelich.de  Thu Jul 10 10:48:17 2014
From: d.froning at fz-juelich.de (Dieter Froning)
Date: Thu, 10 Jul 2014 16:48:17 +0200
Subject: [Paraview] velocity arrows and stream lines from Fluent .cas
 and .dat file
In-Reply-To: <1405002789.56621.YahooMailNeo@web125203.mail.ne1.yahoo.com>
References: <1405002789.56621.YahooMailNeo@web125203.mail.ne1.yahoo.com>
Message-ID: <1405003697.15494.11.camel@iek3102.iek.kfa-juelich.de>

dear Carla,

we exported the data from Fluent in "Ensight Gold" data format.
Paraviews expects the suffix *.case.encas.
I admit that it were not the streamlines what we looked at.
You have to take care to write binary Ensight files, the other types
cannot be read by Paraview (situation from 2012).

The data should be recognized as multi block structures, i.e. the
geometric structures is kept. The blocks of the multi block structure
are the zones and surfaces from the Fluent case.

It may become confusing for very complex structures because the blocks
are not ordered alphabetically but maybe according to the
Fluent-internal data structure.

Good luck!

Dieter Froning

On Thu, 2014-07-10 at 07:33 -0700, Carla Gomez via ParaView wrote:
> I have cas and dat files from Fluent that I have opened via the .cas
> file in ParaView.  I converted the velocity data to vector form via
> the calculator, since it comes in in scalar form.  My goal is to get
> velocity arrows (glyph) and stream lines.  What I get instead are
> random arrow that do not make since to what is seen in Fluent.  The
> stream lines are non-existent.  Has anyone had success with this?  If
> so, can you help guide me in the process to achieve arrow and
> streamlines, if it is possible?
>
>
> Thank you,
> Carla Gomez
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview



------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------


From kmorel at sandia.gov  Thu Jul 10 11:31:22 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 10 Jul 2014 15:31:22 +0000
Subject: [Paraview] Resampling to a uniform grid
In-Reply-To: <CANjZAi8PcPULbG-8UkcDCXCv5CHgC0ctM9ixEsyWNaUb9p0edg@mail.gmail.com>
Message-ID: <CFE40C86.197DF%kmorel@sandia.gov>

Note that this will only work when running in serial. I'm sure that in parallel this will not sample correctly. That would require communication to resolve uneven distributions in the unstructured grid. I don't think anyone has written something like that yet.

-Ken

From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 10, 2014 7:17 AM
To: "Kares, Robert J. (LANL)" <rjk at lanl.gov<mailto:rjk at lanl.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Resampling to a uniform grid

You could start with Sources->Wavelet and reposition it as needed, but I'ld use a python programmable source. Attached is a state file to demonstrate.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jul 9, 2014 at 6:06 PM, Kares, Robert J <rjk at lanl.gov<mailto:rjk at lanl.gov>> wrote:
Folks,

I would like to resample a scalar field defined on an unstructured
grid in 3D onto a uniform rectangular 3D grid with specified logical and
physical dimensions.

It seems from the ParaView filters documentation that this can
somehow be done using the Resample With Dataset filter. It appears
to me that the procedure involves generating a uniform rectangular
grid in some fashion and then feeding it to the Resample With Dataset
filter along with the unstructured grid containing the scalar to be
resampled.

However, I am confused about just how to make the rectangular grid of
specified size in the first place and about how to use it with the Resample With Dataset
filter.

Could someone explain to me how to do this ?

Thanks,

                                       --Bob



_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/21a19238/attachment.html>

From burlen.loring at gmail.com  Thu Jul 10 12:16:35 2014
From: burlen.loring at gmail.com (Burlen Loring)
Date: Thu, 10 Jul 2014 09:16:35 -0700
Subject: [Paraview] connectivity errors
In-Reply-To: <CFE2B7FE.DA58%Richard.C.Angelini.CIV@mail.mil>
References: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>
 <CFE2B7FE.DA58%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <53BEBC63.904@gmail.com>

Hi Rich,

Did you get it to work? You should be using the same version on both
sides. If you are setting this up for multiple people it's simpler to
use the official releases, and do version check in your server side
scripts, print a nice error message when someone connects with an
unsupported version. The scripts
<https://github.com/burlen/pvserver-configs> I wrote for NERSC Edison
have this check.

Burlen

On 07/09/2014 06:15 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US)
wrote:
> I forgot to include that I get the same behavior on both an OSX and Linux
> ParaView client - so I don?t think that it?s a client-side software issue.
>   But, what I don?t understand is what could happen on the server side to
> crash the client?
>
> I think that my cmake/build command is pretty straight forward an
> essentially identical to the cmake command I?ve used on other Cray systems:
>
> cmake \
> -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
> -DCMAKE_BUILD_TYPE=Release \
> -DParaView_FROM_GIT=ON \
> -DENABLE_boost=ON \
> -DENABLE_cgns=OFF \
> -DENABLE_ffmpeg=ON \
> -DENABLE_fontconfig=ON \
> -DENABLE_freetype=ON \
> -DENABLE_hdf5=ON \
> -DENABLE_libxml2=ON \
> -DENABLE_matplotlib=OFF \
> -DENABLE_mesa=OFF \
> -DENABLE_mpi=ON \
> -DENABLE_numpy=ON \
> -DENABLE_osmesa=ON \
> -DENABLE_paraview=ON \
> -DENABLE_png=ON \
> -DENABLE_python=ON \
> -DENABLE_qhull=ON \
> -DENABLE_qt=OFF \
> -DENABLE_silo=ON \
> -DENABLE_szip=ON \
> -DENABLE_visitbridge=ON \
> -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
> ichcxx.so" \
> -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
> h.so" \
> -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc
> xx.so" \
> -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
> e/" \
> -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/
> " \
> -DUSE_SYSTEM_mpi=ON \
> -DUSE_SYSTEM_python=ON \
> -DUSE_SYSTEM_zlib=ON \
> ../Source
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> On 7/9/14, 9:02 AM, "Angelini, Richard C (Rick) CIV USARMY ARL (US)"
> <richard.c.angelini.civ at mail.mil> wrote:
>
>> I?m setting up Paraview client/server  on a new Cray XC30 system.   I have
>> a totally clean build on Paraview on the Cray side, but I can?t get the
>> client-server connection to work, and I?m seeing a strange error.   It
>> looks like the client-server connection is being established, and then the
>> client crashes with this error:
>>
>> Accepting connection(s): my-client-host:53484
>> ERROR: In 
>> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release
>> /
>> paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDef
>> i
>> nitionManager.cxx, line 565
>> vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
>> group=misc and proxy=StrictLoadBalancing were found.
>>
>>
>> Segmentation fault
>>
>>
>>
>> On the server side,  I?m getting a more standard connectivity error:
>>
>> Client connected.
>> ERROR: In 
>> /p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/
>> C
>> ore/vtkSocketCommunicator.cxx, line 812
>> vtkSocketCommunicator (0xe2b930): Could not receive tag. 1
>>
>>
>> I know that the communication path from the compute nodes to the client
>> workstation is valid because VisIt and Ensight both work on this system.
>>
>> Any ideas?
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/a029f027/attachment-0001.html>

From richard.c.angelini.civ at mail.mil  Thu Jul 10 12:20:50 2014
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US))
Date: Thu, 10 Jul 2014 16:20:50 +0000
Subject: [Paraview] connectivity errors
In-Reply-To: <53BEBC63.904@gmail.com>
References: <CFE2B58E.DA56%Richard.C.Angelini.CIV@mail.mil>
 <CFE2B7FE.DA58%Richard.C.Angelini.CIV@mail.mil> <53BEBC63.904@gmail.com>
Message-ID: <CFE43516.DB55%Richard.C.Angelini.CIV@mail.mil>

Yes ? it was a versions issue.    I ?borrowed? someone else?s build script and didn?t look closely enough to see that it wasn?t picking up the production release.     8-)



________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: Burlen Loring <burlen.loring at gmail.com<mailto:burlen.loring at gmail.com>>
Date: Thursday, July 10, 2014 at 12:16 PM
To: "U.S. ARL" <Richard.C.Angelini.CIV at mail.mil<mailto:Richard.C.Angelini.CIV at mail.mil>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: Re: [Paraview] connectivity errors

Hi Rich,

Did you get it to work? You should be using the same version on both sides. If you are setting this up for multiple people it's simpler to use the official releases, and do version check in your server side scripts, print a nice error message when someone connects with an unsupported version. The scripts<https://github.com/burlen/pvserver-configs> I wrote for NERSC Edison  have this check.

Burlen

On 07/09/2014 06:15 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote:

I forgot to include that I get the same behavior on both an OSX and Linux
ParaView client - so I don?t think that it?s a client-side software issue.
  But, what I don?t understand is what could happen on the server side to
crash the client?

I think that my cmake/build command is pretty straight forward an
essentially identical to the cmake command I?ve used on other Cray systems:

cmake \
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa \
-DCMAKE_BUILD_TYPE=Release \
-DParaView_FROM_GIT=ON \
-DENABLE_boost=ON \
-DENABLE_cgns=OFF \
-DENABLE_ffmpeg=ON \
-DENABLE_fontconfig=ON \
-DENABLE_freetype=ON \
-DENABLE_hdf5=ON \
-DENABLE_libxml2=ON \
-DENABLE_matplotlib=OFF \
-DENABLE_mesa=OFF \
-DENABLE_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_osmesa=ON \
-DENABLE_paraview=ON \
-DENABLE_png=ON \
-DENABLE_python=ON \
-DENABLE_qhull=ON \
-DENABLE_qt=OFF \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-DENABLE_visitbridge=ON \
-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp
ichcxx.so" \
-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic
h.so" \
-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc
xx.so" \
-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ
e/" \
-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/
" \
-DUSE_SYSTEM_mpi=ON \
-DUSE_SYSTEM_python=ON \
-DUSE_SYSTEM_zlib=ON \
../Source



________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




On 7/9/14, 9:02 AM, "Angelini, Richard C (Rick) CIV USARMY ARL (US)"
<richard.c.angelini.civ at mail.mil><mailto:richard.c.angelini.civ at mail.mil> wrote:



I?m setting up Paraview client/server  on a new Cray XC30 system.   I have
a totally clean build on Paraview on the Cray side, but I can?t get the
client-server connection to work, and I?m seeing a strange error.   It
looks like the client-server connection is being established, and then the
client crashes with this error:

Accepting connection(s): my-client-host:53484
ERROR: In
/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release
/
paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDef
i
nitionManager.cxx, line 565
vtkSIProxyDefinitionManager (0x113fe5fc0): No proxy that matches:
group=misc and proxy=StrictLoadBalancing were found.


Segmentation fault



On the server side,  I?m getting a more standard connectivity error:

Client connected.
ERROR: In
/p/home/angelini/PV/Build_4.1.0_osmesa/paraview/src/paraview/VTK/Parallel/
C
ore/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0xe2b930): Could not receive tag. 1


I know that the communication path from the compute nodes to the client
workstation is valid because VisIt and Ensight both work on this system.

Any ideas?



________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/3b8d925e/attachment.html>

From andy.bauer at kitware.com  Thu Jul 10 12:43:26 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 10 Jul 2014 12:43:26 -0400
Subject: [Paraview] Resampling to a uniform grid
In-Reply-To: <CFE40C86.197DF%kmorel@sandia.gov>
References: <CANjZAi8PcPULbG-8UkcDCXCv5CHgC0ctM9ixEsyWNaUb9p0edg@mail.gmail.com>
 <CFE40C86.197DF%kmorel@sandia.gov>
Message-ID: <CAMaOp+FsnS+Snm2ibJhnm3JGVNtxdCP9_9iMZR2cTLGNzCN06Q@mail.gmail.com>

The resample to data set filter does work in parallel but the result will
only be on process 0. Each process sends its values to process 0 so this is
not an algorithm that will scale well.

Regards,
Andy


On Thu, Jul 10, 2014 at 11:31 AM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

>   Note that this will only work when running in serial. I'm sure that in
> parallel this will not sample correctly. That would require communication
> to resolve uneven distributions in the unstructured grid. I don't think
> anyone has written something like that yet.
>
>  -Ken
>
>   From: David E DeMarle <dave.demarle at kitware.com>
> Date: Thursday, July 10, 2014 7:17 AM
> To: "Kares, Robert J. (LANL)" <rjk at lanl.gov>
> Cc: "paraview at paraview.org" <paraview at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview] Resampling to a uniform grid
>
>   You could start with Sources->Wavelet and reposition it as needed, but
> I'ld use a python programmable source. Attached is a state file to
> demonstrate.
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
> On Wed, Jul 9, 2014 at 6:06 PM, Kares, Robert J <rjk at lanl.gov> wrote:
>
>>  Folks,
>>
>>
>>
>> I would like to resample a scalar field defined on an unstructured
>>
>> grid in 3D onto a uniform rectangular 3D grid with specified logical and
>>
>> physical dimensions.
>>
>>
>>
>> It seems from the ParaView filters documentation that this can
>>
>> somehow be done using the Resample With Dataset filter. It appears
>>
>> to me that the procedure involves generating a uniform rectangular
>>
>> grid in some fashion and then feeding it to the Resample With Dataset
>>
>> filter along with the unstructured grid containing the scalar to be
>>
>> resampled.
>>
>>
>>
>> However, I am confused about just how to make the rectangular grid of
>>
>> specified size in the first place and about how to use it with the
>> Resample With Dataset
>>
>> filter.
>>
>>
>>
>> Could someone explain to me how to do this ?
>>
>>
>>
>> Thanks,
>>
>>
>>
>>                                        --Bob
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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://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
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/bcc0ba94/attachment.html>

From nmiri127 at gmail.com  Thu Jul 10 12:48:07 2014
From: nmiri127 at gmail.com (Nabil Miri)
Date: Thu, 10 Jul 2014 14:18:07 -0230
Subject: [Paraview] Texture Mapping in Paraview 4.1
Message-ID: <CACBt9+r1B=3o=rxWddKfoOfLJiDNQGEPh3H3CfacpHbCDRUpnA@mail.gmail.com>

HI all,

I have been puzzling over how to map textures to sources in Paraview 4.1. I
know it involves the "Map texture to sphere/plane/cylinder" filter but
where do I go after applying that to the applicable object??

Thanks.

-Nabil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/117aeb86/attachment.html>

From kmorel at sandia.gov  Thu Jul 10 12:49:16 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 10 Jul 2014 16:49:16 +0000
Subject: [Paraview] Resampling to a uniform grid
In-Reply-To: <CAMaOp+FsnS+Snm2ibJhnm3JGVNtxdCP9_9iMZR2cTLGNzCN06Q@mail.gmail.com>
Message-ID: <CFE42010.19807%kmorel@sandia.gov>

I stand corrected then.

From: Andy Bauer <andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>>
Date: Thursday, July 10, 2014 10:43 AM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>, "Kares, Robert J. (LANL)" <rjk at lanl.gov<mailto:rjk at lanl.gov>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Resampling to a uniform grid

The resample to data set filter does work in parallel but the result will only be on process 0. Each process sends its values to process 0 so this is not an algorithm that will scale well.

Regards,
Andy


On Thu, Jul 10, 2014 at 11:31 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Note that this will only work when running in serial. I'm sure that in parallel this will not sample correctly. That would require communication to resolve uneven distributions in the unstructured grid. I don't think anyone has written something like that yet.

-Ken

From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 10, 2014 7:17 AM
To: "Kares, Robert J. (LANL)" <rjk at lanl.gov<mailto:rjk at lanl.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Resampling to a uniform grid

You could start with Sources->Wavelet and reposition it as needed, but I'ld use a python programmable source. Attached is a state file to demonstrate.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>


On Wed, Jul 9, 2014 at 6:06 PM, Kares, Robert J <rjk at lanl.gov<mailto:rjk at lanl.gov>> wrote:
Folks,

I would like to resample a scalar field defined on an unstructured
grid in 3D onto a uniform rectangular 3D grid with specified logical and
physical dimensions.

It seems from the ParaView filters documentation that this can
somehow be done using the Resample With Dataset filter. It appears
to me that the procedure involves generating a uniform rectangular
grid in some fashion and then feeding it to the Resample With Dataset
filter along with the unstructured grid containing the scalar to be
resampled.

However, I am confused about just how to make the rectangular grid of
specified size in the first place and about how to use it with the Resample With Dataset
filter.

Could someone explain to me how to do this ?

Thanks,

                                       --Bob



_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview



_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/78c6a4ce/attachment-0001.html>

From kmorel at sandia.gov  Thu Jul 10 12:52:27 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 10 Jul 2014 16:52:27 +0000
Subject: [Paraview] Texture Mapping in Paraview 4.1
In-Reply-To: <CACBt9+r1B=3o=rxWddKfoOfLJiDNQGEPh3H3CfacpHbCDRUpnA@mail.gmail.com>
Message-ID: <CFE42093.1980C%kmorel@sandia.gov>

One of the advanced options in the properties panel under Display is Texture. By default it is set to None, but you can load an image file to use as a texture.

Try typing "texture" in the search box at the top of the properties panel.

-Ken

From: Nabil Miri <nmiri127 at gmail.com<mailto:nmiri127 at gmail.com>>
Date: Thursday, July 10, 2014 10:48 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Texture Mapping in Paraview 4.1

HI all,

I have been puzzling over how to map textures to sources in Paraview 4.1. I know it involves the "Map texture to sphere/plane/cylinder" filter but where do I go after applying that to the applicable object??

Thanks.

-Nabil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/60c6f8e3/attachment.html>

From nmiri127 at gmail.com  Thu Jul 10 12:59:39 2014
From: nmiri127 at gmail.com (Nabil Miri)
Date: Thu, 10 Jul 2014 14:29:39 -0230
Subject: [Paraview] Texture Mapping in Paraview 4.1
In-Reply-To: <CFE42093.1980C%kmorel@sandia.gov>
References: <CACBt9+r1B=3o=rxWddKfoOfLJiDNQGEPh3H3CfacpHbCDRUpnA@mail.gmail.com>
 <CFE42093.1980C%kmorel@sandia.gov>
Message-ID: <CACBt9+qbN77CjB8e7hmueiXSZ2=h1rpfYH9KDRaHsLcCN70oTg@mail.gmail.com>

Found it (I am not very good at looking :). Thanks very much!

-Nabil


On Thu, Jul 10, 2014 at 2:22 PM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

>   One of the advanced options in the properties panel under Display is
> Texture. By default it is set to None, but you can load an image file to
> use as a texture.
>
>  Try typing "texture" in the search box at the top of the properties
> panel.
>
>  -Ken
>
>    From: Nabil Miri <nmiri127 at gmail.com>
> Date: Thursday, July 10, 2014 10:48 AM
> To: "paraview at paraview.org" <paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] Texture Mapping in Paraview 4.1
>
>   HI all,
>
>  I have been puzzling over how to map textures to sources in Paraview
> 4.1. I know it involves the "Map texture to sphere/plane/cylinder" filter
> but where do I go after applying that to the applicable object??
>
>  Thanks.
>
>  -Nabil
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/cadc894f/attachment.html>

From simon.m.su.ctr at mail.mil  Thu Jul 10 16:48:29 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Thu, 10 Jul 2014 20:48:29 +0000
Subject: [Paraview] python script to rotate geometry object from Extract CTH
 Parts filter (UNCLASSIFIED)
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CD5D4D@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hello,

After loading CTH data set and apply the Extract CTH parts filter, I will
get some geometry/objects (depending on how many volume fraction you
selected). When animated over time, the objects will move based on your
modeling/simulation. 

What I would like to do next is to rotate one of the moving object (but not
changing the simulation trajectory path) independent of other objects from
the extract cth parts filter. Can this be done? Is there sample python
script out there that can accomplish this rotation?

Thanks in advance..

Thanks
-simon

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140710/4ca1a4d8/attachment.bin>

From victor.major at gmail.com  Fri Jul 11 03:31:06 2014
From: victor.major at gmail.com (Victor)
Date: Fri, 11 Jul 2014 15:31:06 +0800
Subject: [Paraview] How to run ParaView in parallel
In-Reply-To: <CAJTHAufEtSsokyWr6kXzO2tXdLApMNFUs85qd-tx7czT=NjVuQ@mail.gmail.com>
References: <CAJTHAufEtSsokyWr6kXzO2tXdLApMNFUs85qd-tx7czT=NjVuQ@mail.gmail.com>
Message-ID: <CAJTHAuf0vfnG57tgXEkpenPzh6oiwTpU3m32JgtrOw2Jc=0rdw@mail.gmail.com>

Can anyone offer any insights for my problem? Each data set is from 6gb to
13gb in size and we have a compute cluster on site, and even my own
workstation is a 12 physical core machine so I am looking for a way to
utilise these resources to increase the otherwise very slow data post
processing.


On 23 June 2014 09:55, Victor <victor.major at gmail.com> wrote:

> I have compiled ParaView with MPI support, searched the internet, looked
> at examples and I cannot get it to work.
>
> I tried to run it with the following methods:
>
> 1. "Use multicore" setting within the GUI. I set it at 6 and got this
> during startup
>
> AutoMPI: SUCCESS: command is:
>  "/opt/openmpi-1.8.1/bin/mpiexec" "-np" "6"
> "/usr/local/lib/paraview-4.1/pvserver" "--server-port=45024"
> AutoMPI: starting process server
> -------------- server output --------------
> Waiting for client...
> AutoMPI: server successfully started.
>
>
> It looks normal.
>
> 2. Start pvserver with "mpirun -np 6 pvserver" and connect the client
> manually:
>
> Waiting for client...
> Connection URL: cs://consilience-ssd:11111
> Accepting connection(s): consilience-ssd:11111
> Client connected.
>
>
> It looks normal.
>
>
> The problem is that the output does not look normal. I am trying to
> display CFD external flow simulation data using a Slice filter and instead
> of a correct visualization of the flow I get a spotty field as per the
> image attached. I am also attaching the PV ProcessID screenshot.
>
> What do I need to do to make ParaView render in parallel and deliver
> correct visualization results?
>
> Thanks,
>
> Victor
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140711/0de9b647/attachment.html>

From biddisco at cscs.ch  Fri Jul 11 10:47:05 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Fri, 11 Jul 2014 14:47:05 +0000
Subject: [Paraview] Resampling to a uniform grid
In-Reply-To: <CFE42010.19807%kmorel@sandia.gov>
References: <CAMaOp+FsnS+Snm2ibJhnm3JGVNtxdCP9_9iMZR2cTLGNzCN06Q@mail.gmail.com>
 <CFE42010.19807%kmorel@sandia.gov>
Message-ID: <50320452A334BD42A5EC72BAD21450991077F767@MBX110.d.ethz.ch>

I do this by using the pv-zoltan plugin mesh redistribution filter, which distributes meshes in parallel, adds ghost cells as needed and also (and importantly here) bounding box information to the extent translator (vtkBoundsExtentTranslator). Then in the pv-meshless plugin I have a resampling grid generator which takes the bounding box info and a resolution and generates grids in parallel - one for each process - using the bounds. The SPH resample filter then takes these inputs and does a resampling using an SPH kernel - this is probably more than the OP wants, but in principle it would be easy to switch out the SPH resampler and just use a standard probe filter to get a parallel resample which scales well.

Unfortunately, I'm on vacation and the code is not documented well and may not work currently as I have not been using It much recently.

JB

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Moreland, Kenneth
Sent: 10 July 2014 18:49
To: Andy Bauer
Cc: paraview at paraview.org
Subject: Re: [Paraview] Resampling to a uniform grid

I stand corrected then.

From: Andy Bauer <andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>>
Date: Thursday, July 10, 2014 10:43 AM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Cc: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>, "Kares, Robert J. (LANL)" <rjk at lanl.gov<mailto:rjk at lanl.gov>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Resampling to a uniform grid

The resample to data set filter does work in parallel but the result will only be on process 0. Each process sends its values to process 0 so this is not an algorithm that will scale well.

Regards,
Andy

On Thu, Jul 10, 2014 at 11:31 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Note that this will only work when running in serial. I'm sure that in parallel this will not sample correctly. That would require communication to resolve uneven distributions in the unstructured grid. I don't think anyone has written something like that yet.

-Ken

From: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Date: Thursday, July 10, 2014 7:17 AM
To: "Kares, Robert J. (LANL)" <rjk at lanl.gov<mailto:rjk at lanl.gov>>
Cc: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Resampling to a uniform grid

You could start with Sources->Wavelet and reposition it as needed, but I'ld use a python programmable source. Attached is a state file to demonstrate.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>

On Wed, Jul 9, 2014 at 6:06 PM, Kares, Robert J <rjk at lanl.gov<mailto:rjk at lanl.gov>> wrote:
Folks,

I would like to resample a scalar field defined on an unstructured
grid in 3D onto a uniform rectangular 3D grid with specified logical and
physical dimensions.

It seems from the ParaView filters documentation that this can
somehow be done using the Resample With Dataset filter. It appears
to me that the procedure involves generating a uniform rectangular
grid in some fashion and then feeding it to the Resample With Dataset
filter along with the unstructured grid containing the scalar to be
resampled.

However, I am confused about just how to make the rectangular grid of
specified size in the first place and about how to use it with the Resample With Dataset
filter.

Could someone explain to me how to do this ?

Thanks,

                                       --Bob



_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview


_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140711/2dad4fdb/attachment-0001.html>

From JPHammonds at anl.gov  Fri Jul 11 10:51:44 2014
From: JPHammonds at anl.gov (John Hammonds)
Date: Fri, 11 Jul 2014 09:51:44 -0500
Subject: [Paraview] Using JOIN to load images from Many HDF files.
Message-ID: <53BFFA00.9040605@anl.gov>

I tried posting this to the XDMF mailing list and have received no 
response.  Hoping someone here can help...

I have a number of images(a few hundred) , each collected in an 
individual HDF file, that I am trying to read into Paraview using a XDMF 
file.  I have found that I can use JOIN to do this but it seems that I 
need to nest the JOINs.  The nesting seems to be due to some limit on 
the number of things that can be referenced in the JOIN.  I seem to be 
limited to ten items in the join list.  All of this has me building some 
odd Join files due to the way things are joined at each level.  I am 
wondering if I am missing something that would make this a lot simpler.  
Esp since I seem to have trouble when large sets are not the same size.  
I am including a working XDMF file an example of one of the HDF files 
for reference.

John Hammonds

-- 
--------------------------------------------
John Hammonds
Software Services Group
Advanced Photon Source
Argonne National Laboratory
JPHammonds at anl.gov

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PartialSet_working.xmf
Type: text/xml
Size: 37420 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140711/132d4bce/attachment-0001.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 015Escan_1.h5
Type: application/octet-stream
Size: 56810 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140711/132d4bce/attachment-0001.obj>

From nmiri127 at gmail.com  Fri Jul 11 11:43:52 2014
From: nmiri127 at gmail.com (Nabil Miri)
Date: Fri, 11 Jul 2014 13:13:52 -0230
Subject: [Paraview] Paraview 4.1 to Blender 2.71 via *.x3d
Message-ID: <CACBt9+qM2=417bSjxxMPz53TdY-mXvdxZnMohqtjN-zQ=i0KpA@mail.gmail.com>

Hi all,

I have a paraview animation that I want to import into blender to do some
advanced post-processing and export as an animation. I have the
"VTKBlender.py" module but I have do idea what values I have to put into my
system's environment variables. All the documentation I found is for Unix,
and nothing for Windows x64. :( Here is where I got the script:
http://www.ualberta.ca/CNS/RESEARCH/Vis/VTKBlender/.

Thanks again!

-Nabil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140711/ae2fe9c1/attachment.html>

From dave.demarle at kitware.com  Fri Jul 11 11:50:27 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 11 Jul 2014 11:50:27 -0400
Subject: [Paraview] Multiple Domains with XDMF
In-Reply-To: <53AB04CD.7090703@ices.utexas.edu>
References: <53AB04CD.7090703@ices.utexas.edu>
Message-ID: <CANjZAi9ibxuEb+NmZF+KBOpx=e=9Wm5J5-GYJbdWDqUc9wjxpA@mail.gmail.com>

ParaView hasn't handled multiple XDMF Domains well in a _long_ while or
maybe ever (Two.4 might have). This is because ParaView doesn't like it
when the high level structure of the data changes. This could happen when
you pick a different domain and suddenly the reader has to switch from
producing a single structured grid to a multi block containing tens of
unstructured grids for example.

I can think of two alternatives:
* After you read in the data you have, use the extract block filter to
choose which of the two grids you want to work with.
* Write two separate files and read each one in turn.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jun 25, 2014 at 1:20 PM, Truman Ellis <truman at ices.utexas.edu>
wrote:

> I essentially have two grids with different solution variables defined on
> each one. I am using the XDMF format to output the data. When I create a
> spatial collection of the two grids, the solution variables show up as
> "partial" data in Paraview. Say solution variable u lives on grid 1 while f
> lives on grid 2. If I color by u, grid 2 shows up as some solid color that
> doesn't go away unless I turn off the block that corresponds to grid 2. And
> vice versa for f.
>
> I read that XDMF supports multiple domains, which sounded like it might be
> the right solution for this problem. But when I load such a mesh into
> Paraview, it only picks up on the last defined domain. It seems like having
> different solution variables on different grids is a common problem, so I'm
> wondering if anyone has a cleaner solution than selectively turning on and
> off the blocks corresponding to the solution variable I am currently
> considering.
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140711/0545ef40/attachment.html>

From dave.demarle at kitware.com  Fri Jul 11 12:03:30 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 11 Jul 2014 12:03:30 -0400
Subject: [Paraview] Using JOIN to load images from Many HDF files.
In-Reply-To: <53BFFA00.9040605@anl.gov>
References: <53BFFA00.9040605@anl.gov>
Message-ID: <CANjZAi-veYThG06rAcJrsFH0L0QziT4ozW+MnE28fRiGy1UOOA@mail.gmail.com>

Just responded on the xdmf list.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Fri, Jul 11, 2014 at 10:51 AM, John Hammonds <JPHammonds at anl.gov> wrote:

> I tried posting this to the XDMF mailing list and have received no
> response.  Hoping someone here can help...
>
> I have a number of images(a few hundred) , each collected in an individual
> HDF file, that I am trying to read into Paraview using a XDMF file.  I have
> found that I can use JOIN to do this but it seems that I need to nest the
> JOINs.  The nesting seems to be due to some limit on the number of things
> that can be referenced in the JOIN.  I seem to be limited to ten items in
> the join list.  All of this has me building some odd Join files due to the
> way things are joined at each level.  I am wondering if I am missing
> something that would make this a lot simpler.  Esp since I seem to have
> trouble when large sets are not the same size.  I am including a working
> XDMF file an example of one of the HDF files for reference.
>
> John Hammonds
>
> --
> --------------------------------------------
> John Hammonds
> Software Services Group
> Advanced Photon Source
> Argonne National Laboratory
> JPHammonds at anl.gov
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140711/feb16dd0/attachment.html>

From marcus.hanwell at kitware.com  Fri Jul 11 15:42:53 2014
From: marcus.hanwell at kitware.com (Marcus D. Hanwell)
Date: Fri, 11 Jul 2014 15:42:53 -0400
Subject: [Paraview] Using JOIN to load images from Many HDF files.
In-Reply-To: <53BFFA00.9040605@anl.gov>
References: <53BFFA00.9040605@anl.gov>
Message-ID: <CAMkPkZVK9mOXTf2e3f_uU5reo3gCuYVSiJ7LvSBiK+yW=SfoPQ@mail.gmail.com>

On Fri, Jul 11, 2014 at 10:51 AM, John Hammonds <JPHammonds at anl.gov> wrote:
> I tried posting this to the XDMF mailing list and have received no response.
> Hoping someone here can help...
>
> I have a number of images(a few hundred) , each collected in an individual
> HDF file, that I am trying to read into Paraview using a XDMF file.  I have
> found that I can use JOIN to do this but it seems that I need to nest the
> JOINs.  The nesting seems to be due to some limit on the number of things
> that can be referenced in the JOIN.  I seem to be limited to ten items in
> the join list.  All of this has me building some odd Join files due to the
> way things are joined at each level.  I am wondering if I am missing
> something that would make this a lot simpler.  Esp since I seem to have
> trouble when large sets are not the same size.  I am including a working
> XDMF file an example of one of the HDF files for reference.
>
How is your data produced? We are developing a custom ParaView
application, and as part of that we are adding some new readers to VTK
to support S/TEM tomography using an HDF5-based format. The spec is
here,

http://emdatasets.lbl.gov/spec/

It would be great to understand your needs, and whether some of this
development work could be tweaked in order to address a wider range of
experimental data that might help your user community. If XDMF is one
path, then we should also look more closely at supporting that too.

Thanks,

Marcus

From JPHammonds at anl.gov  Fri Jul 11 17:40:08 2014
From: JPHammonds at anl.gov (John Hammonds)
Date: Fri, 11 Jul 2014 16:40:08 -0500
Subject: [Paraview] Using JOIN to load images from Many HDF files.
In-Reply-To: <CAMkPkZVK9mOXTf2e3f_uU5reo3gCuYVSiJ7LvSBiK+yW=SfoPQ@mail.gmail.com>
References: <53BFFA00.9040605@anl.gov>
 <CAMkPkZVK9mOXTf2e3f_uU5reo3gCuYVSiJ7LvSBiK+yW=SfoPQ@mail.gmail.com>
Message-ID: <53C059B8.9050504@anl.gov>

Marcus,

The HDF data that I am working with is currently collected using the 
NeXus data format (http://www.nexusformat.org/).  Some of the data that 
is collected has all of the data in one big file and others have the 
data in separate files.  For the case that all of the data is in one big 
file, XDMF actually works pretty smoothly once you get over the initial 
hurdles.  For the case that the data is in different files, I had the 
issues that I described.  Note that I have also looked the last couple 
of days on loading Tiff images (for another beamline here 
www.aps.anl.gov) using Binary instead of HDF. This went pretty smoothly 
except that the XDMF pages do not mention that you can use Short as the 
NumberType for 16 bit data. Eventually I tried it and it fixed my 
loading issues.

Note that we also have some Tomography beamlines here.  Their data is 
captured in a similar but different HDF format (can't see to find the 
link at the moment).

John
On 7/11/2014 2:42 PM, Marcus D. Hanwell wrote:
> On Fri, Jul 11, 2014 at 10:51 AM, John Hammonds <JPHammonds at anl.gov> wrote:
>> I tried posting this to the XDMF mailing list and have received no response.
>> Hoping someone here can help...
>>
>> I have a number of images(a few hundred) , each collected in an individual
>> HDF file, that I am trying to read into Paraview using a XDMF file.  I have
>> found that I can use JOIN to do this but it seems that I need to nest the
>> JOINs.  The nesting seems to be due to some limit on the number of things
>> that can be referenced in the JOIN.  I seem to be limited to ten items in
>> the join list.  All of this has me building some odd Join files due to the
>> way things are joined at each level.  I am wondering if I am missing
>> something that would make this a lot simpler.  Esp since I seem to have
>> trouble when large sets are not the same size.  I am including a working
>> XDMF file an example of one of the HDF files for reference.
>>
> How is your data produced? We are developing a custom ParaView
> application, and as part of that we are adding some new readers to VTK
> to support S/TEM tomography using an HDF5-based format. The spec is
> here,
>
> http://emdatasets.lbl.gov/spec/
>
> It would be great to understand your needs, and whether some of this
> development work could be tweaked in order to address a wider range of
> experimental data that might help your user community. If XDMF is one
> path, then we should also look more closely at supporting that too.
>
> Thanks,
>
> Marcus

-- 
--------------------------------------------
John Hammonds
Software Services Group
Advanced Photon Source
Argonne National Laboratory
JPHammonds at anl.gov


From shermanw at indiana.edu  Mon Jul 14 02:14:14 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Mon, 14 Jul 2014 02:14:14 -0400
Subject: [Paraview] Attempting to start an animation in the middle
Message-ID: <53C37536.5070307@indiana.edu>

Hello PVer's,

I'm trying to start a batch animation in the middle of the animation
track, but I have not yet figured out how to make it work.

I've tried lots of things that looked promising, but none work.

So in my ParaView batch script (which starts out loading a statefile
created by the GUI client), I create a Python animation cue, based
on some code I found a while back, and that has been working fine.
But now I need to be able to start animations in the middle, and
at first I thought it was working, but it was really always starting
from the beginning.

So my script has the lines:
	scene.StartTime = 1200
...
	view.UseOffscreenRendering = 1
	WriteAnimation("file.png")

and my Python cue has this in the "tick()" method:
    i = int(scene.TimeKeeper.Time)
    print "time is " + str(i) + " / " + str(self.GetAnimationTime())
    view.ViewTime = i
    scene.AnimationTime = i

So the value of "i" is correct, it starts at "1200", but when I print
"GetAnimationTime()", it starts at time 0.0 (which is normalized from 0.0
to 1.0).

The "scene.AnimationTime = i" seems to have no effect.


So some documentation for the "WriteAnimation" says that there are a
few parameters, but the two parameters I thought might work, aren't
actually implemented in "simple.py", so I guess that's a bug:
     WriteAnimation("file.png", StartFileCount=1200, 
PlaybackTimeWindow=[1200,1600])

that doesn't work either.


So looking in the "simple.py" code, I repalced the wall to WriteAnimation()
with this:
     iw = servermanager.vtkSMAnimationSceneImageWriter()
     iw.SetAnimationScene(scene.SMProxy)
     iw.SetFileName("file.png")
     iw.SetStartFileCount(1200)
     iw.SetPlaybackTimeWindow(.7, 1.0)
     iw.Save()
     WriteAnimation("file.png")

And that doesn't work either.

I should note that it fails in two ways:

1) It doesn't start the file numbering at 1200

2) It doesn't render the scene at time 1200

I should not though that the "Annotate Time" source actually reports
the time as though it starts at 1200.  But the camera moves and other
aspects of the scene all start at time 0.


Thoughts/suggestions would be greatly appreciated.

	Thanks in advance,
	Bill

--
Bill Sherman
Sr. Technology Advisor
Advanced Visualization Lab
Pervasive Technology Inst
Indiana University
shermanw at indiana.edu



From praveenn at nvidia.com  Mon Jul 14 18:34:40 2014
From: praveenn at nvidia.com (Praveen Narayanan)
Date: Mon, 14 Jul 2014 15:34:40 -0700
Subject: [Paraview] Building Piston
Message-ID: <1B75FE20F814944EA42F9A3A76476C253C4A76C358@HQMAIL03.nvidia.com>

Hi

I have been trying to build piston from the paraview source (on website), and standalone piston from the lanl website.

I run into this error:

urces
[ 32%] Built target vtkRenderingCore
[ 32%] Built target vtkParseOGLExt
[ 32%] Built target vtkEncodeString
[ 32%] Built target vtkEncodeString-launcher
[ 32%] Built target vtkRenderingOpenGL
[ 32%] Building NVCC (Device) object VTK/Accelerators/Piston/CMakeFiles/cuda_compile.dir//./cuda_compile_generated_vtkPistonThreshold.cu.o
nvcc warning : The 'compute_10' and 'sm_10' architectures are deprecated, and may be removed in a future release.
nvcc warning : The 'compute_10' and 'sm_10' architectures are deprecated, and may be removed in a future release.
/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(13): error: invalid redeclaration of type name "float3"
/usr/local/cuda/include/vector_types.h(394): here

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(18): error: invalid redeclaration of type name "float4"
/usr/local/cuda/include/vector_types.h(395): here

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(23): error: invalid redeclaration of type name "uint3"
/usr/local/cuda/include/vector_types.h(381): here

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(29): error: cannot overload functions distinguished by return type alone

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(34): error: cannot overload functions distinguished by return type alone

....


Several such errors appear. Float2, float3 etc are cuda specific things, so I am not sure what is happening here.

Ideas?
Thanks
Praveen

Applied Engineer
NVIDIA

http://devblogs.nvidia.com/parallelforall/


-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140714/2226d325/attachment.html>

From menonon at port.kobe-u.ac.jp  Tue Jul 15 00:22:02 2014
From: menonon at port.kobe-u.ac.jp (Daisuke Meno)
Date: Tue, 15 Jul 2014 13:22:02 +0900
Subject: [Paraview] VR plugin cannot be built.
Message-ID: <CAA+mDZg5TL+98jKh7hd4b_76treKV8uA5f6GZ70NprHupM0Cmg@mail.gmail.com>

Hi,

VR plugin cannot be built on Windows7.
I have followed this page.
http://www.paraview.org/Wiki/ParaView/VRPN_with_MS-MPI

But I got errors.
Sorry, text files include some Japanese characters.

Would you give me any solution ?

Thanks
Daisuke

-- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Kobe University
Education Center on Computational Science and Engineering

                Daisuke MENO
    (Limited-term Assistant Professor)

 Integrated Research Center @ Port Island
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-------------- next part --------------
[2/2] Linking CXX shared library bin\VRPlugin.dll
FAILED: cmd.exe /c cd . && "c:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E vs_link_dll C:\PROGRA~2\MICROS~2.0\VC\bin\link.exe /nologo 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRAddConnectionDialog.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRAddStyleDialog.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRDockPanel.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRStarter.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRAddConnectionDialog.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRAddStyleDialog.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRConnectionManager.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRDockPanel.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRQueueHandler.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRStarter.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRPNConnection.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRPNEventListener.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRControlSliceOrientationStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRControlSlicePositionStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRGrabWorldStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRInteractorStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRInteractorStyleFactory.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRQueue.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRTrackStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRConnectionManager.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRQueueHandler.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRPNConnection.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRPNEventListener.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRPNCallBackHandlers.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRControlSliceOrientationStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRControlSlicePositionStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRGrabWorldStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRInteractorStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRInteractorStyleFactory.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRQueue.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRTrackStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRSpaceNavigatorGrabWorldStyle.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRStarterImplementation.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRStarterImplementation.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRDockPanelImplementation.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRDockPanelImplementation.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\VRPlugin_Plugin.obj 
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_VRPlugin_Plugin.obj  
/out:bin\VRPlugin.dll 
/implib:lib\VRPlugin.lib 
/pdb:bin\VRPlugin.pdb 
/dll /version:1.0 /machine:X86  /INCREMENTAL:NO /MANIFEST:NO  
lib\vtkpqComponents-pv4.1.lib 
E:\immersiveParaview\vrpn-bin\vrpn.lib 
lib\vtkpqApplicationComponents-pv4.1.lib 
lib\vtkpqComponents-pv4.1.lib 
lib\vtkpqPython-pv4.1.lib 
lib\vtkpqCore-pv4.1.lib 
lib\vtkpqWidgets-pv4.1.lib 
lib\QtTesting.lib 
C:\Qt\4.8.6\lib\QtHelp4.lib 
C:\Qt\4.8.6\lib\QtSql4.lib 
C:\Qt\4.8.6\lib\QtUiTools.lib 
C:\Qt\4.8.6\lib\QtXml4.lib 
lib\vtkPVServerManagerCore-pv4.1.lib 
lib\vtkPVServerImplementationCore-pv4.1.lib 
lib\protobuf.lib 
lib\vtkPVClientServerCoreCore-pv4.1.lib 
lib\vtkFiltersProgrammable-pv4.1.lib 
lib\vtkGUISupportQt-pv4.1.lib 
C:\Qt\4.8.6\lib\QtGui4.lib 
C:\Qt\4.8.6\lib\QtNetwork4.lib 
C:\Qt\4.8.6\lib\QtCore4.lib 
lib\vtkPVVTKExtensionsCore-pv4.1.lib 
lib\vtkPVCommon-pv4.1.lib 
lib\vtkClientServer-pv4.1.lib 
lib\vtkPythonInterpreter-pv4.1.lib 
lib\vtkWrappingPython27Core-pv4.1.lib 
C:\Python27\libs\python27.lib 
lib\vtkFiltersParallel-pv4.1.lib 
lib\vtkParallelMPI-pv4.1.lib 
lib\vtkIOXMLParser-pv4.1.lib 
lib\vtkParallelCore-pv4.1.lib 
lib\vtkIOLegacy-pv4.1.lib 
lib\vtkInteractionStyle-pv4.1.lib 
lib\vtkFiltersModeling-pv4.1.lib 
lib\vtkRenderingOpenGL-pv4.1.lib 
glu32.lib 
opengl32.lib 
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\d3d9.lib" 
wbemuuid.lib 
lib\vtkIOCore-pv4.1.lib 
lib\vtkRenderingCore-pv4.1.lib 
lib\vtkFiltersExtraction-pv4.1.lib 
lib\vtkFiltersStatistics-pv4.1.lib 
lib\vtkImagingFourier-pv4.1.lib 
lib\vtkImagingCore-pv4.1.lib 
lib\vtkalglib-pv4.1.lib 
lib\vtkFiltersGeometry-pv4.1.lib 
lib\vtkFiltersSources-pv4.1.lib 
lib\vtkFiltersGeneral-pv4.1.lib 
lib\vtkFiltersCore-pv4.1.lib 
lib\vtkCommonExecutionModel-pv4.1.lib 
lib\vtkCommonComputationalGeometry-pv4.1.lib 
lib\vtkCommonDataModel-pv4.1.lib 
lib\vtkCommonTransforms-pv4.1.lib 
lib\vtkCommonMisc-pv4.1.lib 
lib\vtkCommonMath-pv4.1.lib 
lib\vtkCommonSystem-pv4.1.lib 
lib\vtkCommonCore-pv4.1.lib 
lib\vtksys-pv4.1.lib 
ws2_32.lib 
Psapi.lib 
kernel32.lib 
user32.lib 
gdi32.lib 
winspool.lib 
shell32.lib 
ole32.lib 
oleaut32.lib 
uuid.lib 
comdlg32.lib 
advapi32.lib
  && cd .



   ???C?u???? lib\VRPlugin.lib ???I?u?W?F?N?g lib\VRPlugin.exp ????????
pqVRDockPanel.obj : error LNK2019: ?????????O???V???{?? "__declspec(dllimport) public: class vtkCamera * __thiscall vtkSMRenderViewProxy::GetActiveCamera(void)" (__imp_?GetActiveCamera at vtkSMRenderViewProxy@@QAEPAVvtkCamera@@XZ) ?????? "private: void __thiscall pqVRDockPanel::setActiveView(class pqView *)" (?setActiveView at pqVRDockPanel@@AAEXPAVpqView@@@Z) ???Q?????????????B
vtkVRGrabWorldStyle.obj : error LNK2001: ?O???V???{?? ""__declspec(dllimport) public: class vtkCamera * __thiscall vtkSMRenderViewProxy::GetActiveCamera(void)"(__imp_?GetActiveCamera at vtkSMRenderViewProxy@@QAEPAVvtkCamera@@XZ)" ?????????????B
vtkVRSpaceNavigatorGrabWorldStyle.obj : error LNK2001: ?O???V???{?? ""__declspec(dllimport) public: class vtkCamera * __thiscall vtkSMRenderViewProxy::GetActiveCamera(void)" (__imp_?GetActiveCamera at vtkSMRenderViewProxy@@QAEPAVvtkCamera@@XZ)" ?????????????B
vtkVRSpaceNavigatorGrabWorldStyle.obj : error LNK2001: ?O???V???{?? ""__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)" (__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)" ?????????????B
pqVRQueueHandler.obj : error LNK2019: ?????????O???V???{?? "__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)" (__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z) ?????? "private: void __thiscall pqVRQueueHandler::render(void)" (?render at pqVRQueueHandler@@AAEXXZ) ???Q?????????????B
vtkVRControlSliceOrientationStyle.obj : error LNK2001: ?O???V???{?? ""__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)" (__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)" ?????????????B
vtkVRControlSlicePositionStyle.obj : error LNK2001: ?O???V???{?? ""__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)" (__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)" ?????????????B
vtkVRGrabWorldStyle.obj : error LNK2001: ?O???V???{?? ""__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)" (__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)" ?????????????B
bin\VRPlugin.dll : fatal error LNK1120: ?O???Q?? 2 ?????????????B
LINK failed. with 1120
ninja: build stopped: subcommand failed.

-------------- next part --------------
# This is the CMakeCache file.
# For build in directory: e:/immersiveParaview/ParaView-build
# It was generated by CMake: c:/Program Files (x86)/CMake 2.8/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//Dependencies for the target
AnalyzeNIfTIIO_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkzlib;

//Dependencies for the target
ArrowGlyph_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Build the VTK documentation
BUILD_DOCUMENTATION:BOOL=OFF

BUILD_EXAMPLES:BOOL=OFF

//Build Verdict with shared libraries.
BUILD_SHARED_LIBS:BOOL=ON

//Build the testing tree.
BUILD_TESTING:BOOL=ON

//Path to a program.
BZRCOMMAND:FILEPATH=BZRCOMMAND-NOTFOUND

//For backwards compatibility, what version of CMake commands and
// syntax should this version of CMake try to support.
CMAKE_BACKWARDS_COMPATIBILITY:STRING=2.4

//Choose the type of build, options are: None(CMAKE_CXX_FLAGS or
// CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel.
CMAKE_BUILD_TYPE:STRING=Release

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING= /DWIN32 /D_WINDOWS /W3 /GR /EHsc

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1

//Flags used by the compiler during release minsize builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG

//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG

//Flags used by the compiler during Release with Debug Info builds.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG

//Build with /MP flag enabled
CMAKE_CXX_MP_FLAG:BOOL=OFF

//The maximum number of processes for the /MP flag
CMAKE_CXX_MP_NUM_PROCESSORS:STRING=

//Libraries linked by defalut with all C++ applications.
CMAKE_CXX_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/cl.exe

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING= /DWIN32 /D_WINDOWS /W3

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1

//Flags used by the compiler during release minsize builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG

//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_C_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG

//Flags used by the compiler during Release with Debug Info builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG

//Libraries linked by defalut with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=' /machine:X86 '

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=C:/Program Files (x86)/ParaView

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/bin/link.exe

//Program used to build from build.ninja files.
CMAKE_MAKE_PROGRAM:FILEPATH=E:/immersiveParaview/ninja/ninja.exe

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=' /machine:X86 '

//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=ParaView

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Bin/RC.Exe

//Flags for Fortran compiler.
CMAKE_RC_FLAGS:STRING=' '

//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING=' /machine:X86 '

//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL

//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO

//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=OFF

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=OFF

//Flags used by the linker during the creation of static libraries.
CMAKE_STATIC_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Thread library used.
CMAKE_THREAD_LIBS:STRING=

//If true, cmake will use relative paths in makefiles and projects.
CMAKE_USE_RELATIVE_PATHS:BOOL=OFF

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=OFF

//Path to program used to compress files for transfer to the dart
// server
COMPRESSIONCOMMAND:FILEPATH=COMPRESSIONCOMMAND-NOTFOUND

//Path to the coverage program that CTest uses for performing coverage
// inspection
COVERAGE_COMMAND:FILEPATH=COVERAGE_COMMAND-NOTFOUND

//Extra command line flags to pass to the coverage tool
COVERAGE_EXTRA_FLAGS:STRING=-l

//Enable to build NSIS packages
CPACK_BINARY_NSIS:BOOL=ON

//Enable to build WiX packages
CPACK_BINARY_WIX:BOOL=OFF

//Enable to build ZIP packages
CPACK_BINARY_ZIP:BOOL=OFF

//Enable to build ZIP source packages
CPACK_SOURCE_ZIP:BOOL=ON

//How many times to retry timed-out CTest submissions.
CTEST_SUBMIT_RETRY_COUNT:STRING=3

//How long to wait between timed-out CTest submissions.
CTEST_SUBMIT_RETRY_DELAY:STRING=5

//Path to a program.
CVSCOMMAND:FILEPATH=CVSCOMMAND-NOTFOUND

//Options passed to the cvs update command.
CVS_UPDATE_OPTIONS:STRING=-d -A -P

//Dependencies for the target
CoProcessingPlugin_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Value Computed by CMake
CoProcessingScriptGeneratorPlugin_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/Plugins/CoProcessingScriptGenerator

//Value Computed by CMake
CoProcessingScriptGeneratorPlugin_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/Plugins/CoProcessingScriptGenerator

//Limit of reported errors, -1 reports all.
DART_BUILD_ERROR_REPORT_LIMIT:BOOL=OFF

//Limit of reported warnings, -1 reports all.
DART_BUILD_WARNING_REPORT_LIMIT:BOOL=OFF

//If you have Dart installed, where is it located?
DART_ROOT:PATH=DART_ROOT-NOTFOUND

//Maximum time allowed before CTest will kill the test.
DART_TESTING_TIMEOUT:STRING=1500

//Show the actual output of the build, or if off show a . for each
// 1024 bytes.
DART_VERBOSE_BUILD:BOOL=OFF

//Should Dart server send email when build errors are found in
// Continuous builds?
DELIVER_CONTINUOUS_EMAIL:BOOL=OFF

//Value Computed by CMake
DICOMParser_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/Utilities/DICOMParser

//Value Computed by CMake
DICOMParser_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/Utilities/DICOMParser

//Path to a file.
DirectX_INCLUDE_DIR:PATH=C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Include

//Path to a library.
DirectX_LIBRARY:FILEPATH=C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/d3d9.lib

//Disable compiler warnings
EXODUSII_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Path to Eigen install.
Eigen_DIR:FILEPATH=E:/immersiveParaview/ParaView/Plugins/SciberQuestToolKit/eigen-3.0.3/eigen-eigen-3.0.3

//Additional URL templates for the ExternalData CMake script to
// look for testing data. E.g.
//\nfile:///var/bigharddrive/%(algo)/%(hash)
ExternalData_URL_TEMPLATES:STRING=

//Dependencies for the target
EyeDomeLightingView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkEyeDomeLighting;general;vtkEyeDomeLightingCS;general;vtkEyeDomeLighting;

//Value Computed by CMake
EyeDomeLighting_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/Plugins/EyeDomeLighting

//Value Computed by CMake
EyeDomeLighting_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/Plugins/EyeDomeLighting

//Path to a program.
GITCOMMAND:FILEPATH=C:/Program Files (x86)/Git/cmd/git.exe

//git command line client
GIT_EXECUTABLE:FILEPATH=C:/Program Files (x86)/Git/cmd/git.exe

//Path to a file.
GLUT_INCLUDE_DIR:PATH=C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Include

//Path to a library.
GLUT_glut_LIBRARY:FILEPATH=C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/glut32.lib

//The directory containing gmvread.c, gmvread.h and gmvrayread.h
GMVReader_GMVREAD_LIB_DIR:PATH=E:/immersiveParaview/ParaView/Utilities/VisItBridge/databases/GMV

//Dependencies for the target
GMVReader_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Calculate minimum and maximum of data arrays in RequestInformation
// calls.
//\n   A feature inherited from AVSucdReader, but it seems this
// information is
//\n   never queried by ParaView.
GMVReader_SKIP_DATARANGE_CALCULATIONS_IN_REQUEST_INFORMATION_CALLS:BOOL=OFF

//Path to gunzip executable
GUNZIPCOMMAND:FILEPATH=GUNZIPCOMMAND-NOTFOUND

//Dependencies for the target
H5PartReader_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkhdf5_hl;general;vtkhdf5;general;vtksys;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Value Computed by CMake
HDF5_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5

//Value Computed by CMake
HDF5_HL_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5/hl

//Value Computed by CMake
HDF5_HL_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/hl

//Value Computed by CMake
HDF5_HL_SRC_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5/hl/src

//Value Computed by CMake
HDF5_HL_SRC_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/hl/src

//Value Computed by CMake
HDF5_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/hdf5/vtkhdf5

//Value Computed by CMake
HDF5_SRC_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/hdf5/vtkhdf5/src

//Value Computed by CMake
HDF5_SRC_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/hdf5/vtkhdf5/src

//Path to a program.
HGCOMMAND:FILEPATH=HGCOMMAND-NOTFOUND

//Value Computed by CMake
ICET_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/ThirdParty/IceT/vtkicet

//Build and run the IceT tests.
ICET_BUILD_TESTING:BOOL=ON

//Sets the preferred `k' value for the radix-k algorithm.  This
// is the amount of simultaneous messages each process receives.
//  A value of 8 is generally good on most architectures, but in
// others that have slower computation with respect to network
// (such as BlueGene), a larger value may give better performance.
ICET_MAGIC_K:STRING=8

//Sets the preferred number of times an image may be split.  Some
// image compositing algorithms prefer to partition the images
// such that each process gets a piece.  Too many partitions, though,
// and you end up spending more time collecting them than you save
// balancing the compositing.
ICET_MAX_IMAGE_SPLIT:STRING=512

//Value Computed by CMake
ICET_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/ThirdParty/IceT/vtkicet

//Arguments given to the test program.  These are given between
// the test executable and the name of the test.  Run the test
// executable with the -h flag to see what is available.
ICET_TEST_FLAGS:STRING=

//Use MPE to trace MPI communications.  This is helpful for developers
// trying to measure the performance of parallel compositing algorithms.
ICET_USE_MPE:BOOL=OFF

//Build MPI communication layer for IceT.
ICET_USE_MPI:BOOL=ON

//Build OpenGL support layer for IceT.
ICET_USE_OPENGL:BOOL=ON

//Dependencies for target
IceTCore_LIB_DEPENDS:STATIC=

//Dependencies for the target
IceTGL_LIB_DEPENDS:STATIC=general;IceTCore;general;glu32;general;opengl32;

//Dependencies for the target
IceTMPI_LIB_DEPENDS:STATIC=general;IceTCore;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Path to java command, used by the Dart server to create html.
JAVACOMMAND:FILEPATH=JAVACOMMAND-NOTFOUND

//Value Computed by CMake
JsonCpp_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/jsoncpp/vtkjsoncpp

//Value Computed by CMake
JsonCpp_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/jsoncpp/vtkjsoncpp

//Command to build the project
MAKECOMMAND:STRING=E:/immersiveParaview/ninja/ninja.exe

//Path to the memory checking command, used for memory error detection.
MEMORYCHECK_COMMAND:FILEPATH=MEMORYCHECK_COMMAND-NOTFOUND

//File that contains suppressions for the memory checker
MEMORYCHECK_SUPPRESSIONS_FILE:FILEPATH=

//Executable for running MPI programs.
MPIEXEC:FILEPATH=C:/Program Files/Microsoft HPC Pack 2008 R2/Bin/mpiexec.exe

//Maximum number of processors available to run MPI applications.
MPIEXEC_MAX_NUMPROCS:STRING=2

//Flag used by MPI to specify the number of processes for MPIEXEC;
// the next option will be the number of processes.
MPIEXEC_NUMPROC_FLAG:STRING=-np

//These flags will come after all flags given to MPIEXEC.
MPIEXEC_POSTFLAGS:STRING=

//These flags will be directly before the executable that is being
// run by MPIEXEC.
MPIEXEC_PREFLAGS:STRING=

//Path to a program.
MPI_CXX_COMPILER:FILEPATH=MPI_CXX_COMPILER-NOTFOUND

//MPI CXX compilation flags
MPI_CXX_COMPILE_FLAGS:STRING=

//MPI CXX include path
MPI_CXX_INCLUDE_PATH:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/Inc

//MPI CXX libraries to link against
MPI_CXX_LIBRARIES:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib

//MPI CXX linking flags
MPI_CXX_LINK_FLAGS:STRING=

//Path to a program.
MPI_C_COMPILER:FILEPATH=MPI_C_COMPILER-NOTFOUND

//MPI C compilation flags
MPI_C_COMPILE_FLAGS:STRING=

//MPI C include path
MPI_C_INCLUDE_PATH:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/Inc

//MPI C libraries to link against
MPI_C_LIBRARIES:STRING=C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib

//MPI C linking flags
MPI_C_LINK_FLAGS:STRING=

//Extra MPI libraries to link against
MPI_EXTRA_LIBRARY:STRING=MPI_EXTRA_LIBRARY-NOTFOUND

//MPI library to link against
MPI_LIBRARY:FILEPATH=C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib

//Dependencies for the target
MobileRemoteControl_LIB_DEPENDS:STATIC=general;pqComponents;general;pqApplicationComponents;general;vtkPVClientServerCoreRendering;general;vtkPVServerManagerRendering;

//Request building AutobahnPython
Module_AutobahnPython:BOOL=OFF

//Request building SixPython
Module_SixPython:BOOL=OFF

//Request building Twisted
Module_Twisted:BOOL=OFF

//Request building VisItLib
Module_VisItLib:BOOL=OFF

//Request building ZopeInterface
Module_ZopeInterface:BOOL=OFF

//Request building pqDeprecated
Module_pqDeprecated:BOOL=OFF

//Request building vtkAcceleratorsDax
Module_vtkAcceleratorsDax:BOOL=OFF

//Request building vtkAcceleratorsPiston
Module_vtkAcceleratorsPiston:BOOL=OFF

//Request building vtkFiltersReebGraph
Module_vtkFiltersReebGraph:BOOL=OFF

//Request building vtkFiltersSMP
Module_vtkFiltersSMP:BOOL=OFF

//Request building vtkFiltersSelection
Module_vtkFiltersSelection:BOOL=OFF

//Request building vtkFiltersStatisticsGnuR
Module_vtkFiltersStatisticsGnuR:BOOL=OFF

//Request building vtkGUISupportMFC
Module_vtkGUISupportMFC:BOOL=OFF

//Request building vtkGUISupportQtOpenGL
Module_vtkGUISupportQtOpenGL:BOOL=ON

//Request building vtkIOFFMPEG
Module_vtkIOFFMPEG:BOOL=OFF

//Request building vtkIOGDAL
Module_vtkIOGDAL:BOOL=OFF

//Request building vtkIOGeoJSON
Module_vtkIOGeoJSON:BOOL=OFF

//Request building vtkIOMINC
Module_vtkIOMINC:BOOL=OFF

//Request building vtkIOMySQL
Module_vtkIOMySQL:BOOL=OFF

//Request building vtkIOODBC
Module_vtkIOODBC:BOOL=OFF

//Request building vtkIOPostgreSQL
Module_vtkIOPostgreSQL:BOOL=OFF

//Request building vtkIOVideo
Module_vtkIOVideo:BOOL=OFF

//Request building vtkIOVisItBridge
Module_vtkIOVisItBridge:BOOL=OFF

//Request building vtkImagingMath
Module_vtkImagingMath:BOOL=OFF

//Request building vtkImagingStatistics
Module_vtkImagingStatistics:BOOL=OFF

//Request building vtkImagingStencil
Module_vtkImagingStencil:BOOL=OFF

//Request building vtkInfovisBoost
Module_vtkInfovisBoost:BOOL=OFF

//Request building vtkInfovisBoostGraphAlgorithms
Module_vtkInfovisBoostGraphAlgorithms:BOOL=OFF

//Request building vtkInfovisParallel
Module_vtkInfovisParallel:BOOL=OFF

//Request building vtkPVVTKExtensionsCosmoTools
Module_vtkPVVTKExtensionsCosmoTools:BOOL=OFF

//Request building vtkRenderingContextOpenGL2
Module_vtkRenderingContextOpenGL2:BOOL=OFF

//Request building vtkRenderingFreeTypeFontConfig
Module_vtkRenderingFreeTypeFontConfig:BOOL=OFF

//Request building vtkRenderingImage
Module_vtkRenderingImage:BOOL=OFF

//Request building vtkRenderingMatplotlib
Module_vtkRenderingMatplotlib:BOOL=OFF

//Request building vtkRenderingOpenGL2
Module_vtkRenderingOpenGL2:BOOL=OFF

//Request building vtkRenderingTk
Module_vtkRenderingTk:BOOL=OFF

//Request building vtkTclTk
Module_vtkTclTk:BOOL=OFF

//Request building vtkUtilitiesColorSeriesToXML
Module_vtkUtilitiesColorSeriesToXML:BOOL=OFF

//Request building vtkWebApplications
Module_vtkWebApplications:BOOL=OFF

//Request building vtkWebCore
Module_vtkWebCore:BOOL=OFF

//Request building vtkWebInstall
Module_vtkWebInstall:BOOL=OFF

//Request building vtkWebJavaScript
Module_vtkWebJavaScript:BOOL=OFF

//Request building vtkWebPython
Module_vtkWebPython:BOOL=OFF

//Request building vtkWrappingJava
Module_vtkWrappingJava:BOOL=OFF

//Request building vtkWrappingPythonCore
Module_vtkWrappingPythonCore:BOOL=ON

//Request building vtkWrappingTcl
Module_vtkWrappingTcl:BOOL=OFF

//Request building vtkmrmpi
Module_vtkmrmpi:BOOL=OFF

//Dependencies for the target
Moments_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Specify default maximum number of elements in the file chunk
// cache chunk for HDF5 files (should be prime number).
NETCDF4_CHUNK_CACHE_NELEMS:STRING=1009

//Specify default file chunk cache preemption policy for HDF5 files
// (a number between 0 and 1, inclusive).
NETCDF4_CHUNK_CACHE_PREEMPTION:STRING=0.75

//Specify default file cache chunk size for HDF5 files in bytes.
NETCDF4_CHUNK_CACHE_SIZE:STRING=4194304

//Specify the number of chunks to store in default per-variable
// cache.
NETCDF4_DEFAULT_CHUNKS_IN_CACHE:STRING=10

//Specify default size of chunks in bytes.
NETCDF4_DEFAULT_CHUNK_SIZE:STRING=4194304

//Specify maximum size (in bytes) for the default per-var chunk
// cache.
NETCDF4_MAX_DEFAULT_CACHE_SIZE:STRING=67108864

//Disable compiler warnings
NETCDF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Build netcdf C++ API
NETCDF_ENABLE_CXX:BOOL=ON

//Dependencies for the target
NonOrthogonalSource_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//OpenGL library for win32
OPENGL_gl_LIBRARY:STRING=opengl32

//GLU library for win32
OPENGL_glu_LIBRARY:STRING=glu32

//Build Adaptors for various simulation codes
PARAVIEW_BUILD_CATALYST_ADAPTORS:BOOL=OFF

//Build AdiosReader Plugin
PARAVIEW_BUILD_PLUGIN_AdiosReader:BOOL=OFF

//Build AnalyzeNIfTIIO Plugin
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO:BOOL=ON

//Build ArrowGlyph Plugin
PARAVIEW_BUILD_PLUGIN_ArrowGlyph:BOOL=ON

//Build CoProcessingScriptGenerator Plugin
PARAVIEW_BUILD_PLUGIN_CoProcessingScriptGenerator:BOOL=ON

//Build EyeDomeLighting Plugin
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting:BOOL=ON

//Build ForceTime Plugin
PARAVIEW_BUILD_PLUGIN_ForceTime:BOOL=OFF

//Build GMVReader Plugin
PARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=ON

//Build H5PartReader Plugin
PARAVIEW_BUILD_PLUGIN_H5PartReader:BOOL=ON

//Build InSituExodus Plugin
PARAVIEW_BUILD_PLUGIN_InSituExodus:BOOL=OFF

//Build MantaView Plugin
PARAVIEW_BUILD_PLUGIN_MantaView:BOOL=OFF

//Build MobileRemoteControl Plugin
PARAVIEW_BUILD_PLUGIN_MobileRemoteControl:BOOL=ON

//Build Moments Plugin
PARAVIEW_BUILD_PLUGIN_Moments:BOOL=ON

//Build NonOrthogonalSource Plugin
PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource:BOOL=ON

//Build PacMan Plugin
PARAVIEW_BUILD_PLUGIN_PacMan:BOOL=ON

//Build PointSprite Plugin
PARAVIEW_BUILD_PLUGIN_PointSprite:BOOL=ON

//Build PythonQtPlugin Plugin
PARAVIEW_BUILD_PLUGIN_PythonQtPlugin:BOOL=OFF

//Build QuadView Plugin
PARAVIEW_BUILD_PLUGIN_QuadView:BOOL=ON

//Build RGBZView Plugin
PARAVIEW_BUILD_PLUGIN_RGBZView:BOOL=ON

//Build SLACTools Plugin
PARAVIEW_BUILD_PLUGIN_SLACTools:BOOL=ON

//Build SciberQuestToolKit Plugin
PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit:BOOL=ON

//Build SierraPlotTools Plugin
PARAVIEW_BUILD_PLUGIN_SierraPlotTools:BOOL=ON

//Build StreamingParticles Plugin
PARAVIEW_BUILD_PLUGIN_StreamingParticles:BOOL=ON

//Build SurfaceLIC Plugin
PARAVIEW_BUILD_PLUGIN_SurfaceLIC:BOOL=ON

//Build TemporalParallelismScriptGenerator Plugin
PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator:BOOL=OFF

//Build UncertaintyRendering Plugin
PARAVIEW_BUILD_PLUGIN_UncertaintyRendering:BOOL=ON

//Build VRPlugin Plugin
PARAVIEW_BUILD_PLUGIN_VRPlugin:BOOL=ON

//Build VaporPlugin Plugin
PARAVIEW_BUILD_PLUGIN_VaporPlugin:BOOL=OFF

//Enable ParaView Qt-based client
PARAVIEW_BUILD_QT_GUI:BOOL=ON

//Enable/Disable web documentation
PARAVIEW_BUILD_WEB_DOCUMENTATION:BOOL=OFF

//Turn on/off client tests that involve separate data and render
// servers.
PARAVIEW_CLIENT_RENDER_SERVER_TESTS:BOOL=ON

//Add Collaboration testing
PARAVIEW_COLLABORATION_TESTING:BOOL=ON

//Exclude test data download from default 'all' target.
PARAVIEW_DATA_EXCLUDE_FROM_ALL:BOOL=OFF

//Local directory holding ExternalData objects in the layout %(algo)/%(hash).
PARAVIEW_DATA_STORE:PATH=

//Enable Catalyst CoProcessing modules
PARAVIEW_ENABLE_CATALYST:BOOL=ON

//Enable/Disable Python scripting support
PARAVIEW_ENABLE_PYTHON:BOOL=ON

//Enables markers in the spyplot reader
PARAVIEW_ENABLE_SPYPLOT_MARKERS:BOOL=ON

//Turn off to avoid ParaView depending on all used VTK modules.
PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED:BOOL=ON

PARAVIEW_ENABLE_WEB:BOOL=OFF

//Semi-colon seperated paths to extrenal plugin directories.
PARAVIEW_EXTERNAL_PLUGIN_DIRS:STRING=

//Initialize MPI on client-processes by default. Can be overridden
// using command line arguments
PARAVIEW_INITIALIZE_MPI_ON_CLIENT:BOOL=OFF

//Expected Qt version
PARAVIEW_QT_VERSION:STRING=4

//Enable IceT (needed for parallel rendering)
PARAVIEW_USE_ICE_T:BOOL=ON

//Enable MPI support for parallel computing
PARAVIEW_USE_MPI:BOOL=ON

//Use MPI synchronous-send commands for communication
PARAVIEW_USE_MPI_SSEND:BOOL=OFF

//Build ParaView with Piston GPGPU filters
PARAVIEW_USE_PISTON:BOOL=OFF

//Use system 'mpi4py' Python package
PARAVIEW_USE_SYSTEM_MPI4PY:BOOL=OFF

//If enabled, Python bindings will back the ClientServer wrapping
// implementation
PARAVIEW_USE_UNIFIED_BINDINGS:BOOL=OFF

//Build ParaView with VisIt readers.
PARAVIEW_USE_VISITBRIDGE:BOOL=OFF

//Build ParaView with VRPN support
PARAVIEW_USE_VRPN:BOOL=ON

//Build ParaView with VRUI support
PARAVIEW_USE_VRUI:BOOL=OFF

//Does an external project define proj_list or should libproj4
// define it?
PROJ_LIST_EXTERNAL:BOOL=OFF

//Should libproj4 include projection code that relies on GSL?
PROJ_USE_GSL:BOOL=OFF

//Should libproj4 be built as a thread-friendly library?
PROJ_USE_PTHREADS:BOOL=OFF

//Disable compiler warnings
PROTOBUF_DISABLE_COMPILER_WARNINGS:BOOL=ON

//Command to run after a failed test to cleanup processes.  Example:
// "killall -9 rsh paraview"
PV_TEST_CLEAN_COMMAND:STRING=

//Node which serves as the client node, used to connect from the
// server side in reverse connection mode.
PV_TEST_CLIENT:STRING=localhost

//Command to run before a test begins. Multiple commands are separated
// by ';'.
PV_TEST_INIT_COMMAND:STRING=

//Use random port numbers when testing client-server configurations.
PV_TEST_USE_RANDOM_PORTS:BOOL=ON

//Path to a library.
PYTHON_DEBUG_LIBRARY:FILEPATH=PYTHON_DEBUG_LIBRARY-NOTFOUND

//Path to a program.
PYTHON_EXECUTABLE:FILEPATH=C:/Python27/python.exe

//Path to a file.
PYTHON_INCLUDE_DIR:PATH=C:/Python27/include

//Path to a library.
PYTHON_LIBRARY:FILEPATH=C:/Python27/libs/python27.lib

//Dependencies for the target
PacMan_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Value Computed by CMake
ParaView_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build

//Value Computed by CMake
ParaView_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView

//Value Computed by CMake
PointSpritePlugin_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/Plugins/PointSprite

//Value Computed by CMake
PointSpritePlugin_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/Plugins/PointSprite

//Dependencies for the target
PointSprite_Plugin_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkPointSpriteGraphics;general;vtkPointSpriteGraphicsCS;general;vtkPointSpriteRendering;general;vtkPointSpriteRenderingCS;general;vtkQvis;general;vtkPointSpriteGraphics;general;vtkPointSpriteRendering;

//Path to a library.
QT_ARTHURPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_ARTHURPLUGIN_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_ARTHURPLUGIN_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/arthurplugin.dll

//Path to a library.
QT_CONTAINEREXTENSION_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/designer/containerextensiond.dll

//Path to a library.
QT_CONTAINEREXTENSION_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/containerextension.dll

//Path to a library.
QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/customwidgetplugin.dll

//Path to a program.
QT_DBUSCPP2XML_EXECUTABLE:FILEPATH=QT_DBUSCPP2XML_EXECUTABLE-NOTFOUND

//Path to a program.
QT_DBUSXML2CPP_EXECUTABLE:FILEPATH=QT_DBUSXML2CPP_EXECUTABLE-NOTFOUND

//Path to a program.
QT_DESIGNER_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/designer.exe

//The location of the Qt docs
QT_DOC_DIR:PATH=C:/Qt/4.8.6/doc

//qhelpgenerator used to compile Qt help project files
QT_HELP_GENERATOR:FILEPATH=C:/Qt/4.8.6/bin/qhelpgenerator.exe

//The location of the Qt imports
QT_IMPORTS_DIR:PATH=C:/Qt/4.8.6/imports

//Path to a program.
QT_LINGUIST_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/linguist.exe

//Path to a program.
QT_LRELEASE_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/lrelease.exe

//Path to a program.
QT_LUPDATE_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/lupdate.exe

//The location of the Qt mkspecs containing qconfig.pri
QT_MKSPECS_DIR:PATH=C:/Qt/4.8.6/mkspecs

//Path to a program.
QT_MOC_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/moc.exe

//Path to a library.
QT_PHONONWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_PHONONWIDGETS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_PHONONWIDGETS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/phononwidgets.dll

//Path to a library.
QT_PHONON_DS9_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/phonon_backend/phonon_ds9d4.dll

//Path to a library.
QT_PHONON_DS9_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/phonon_backend/phonon_ds94.dll

//Path to a file.
QT_PHONON_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/phonon

//The Qt PHONON library
QT_PHONON_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/phonon4.lib;debug;C:/Qt/4.8.6/lib/phonond4.lib

//Path to a library.
QT_PHONON_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/phonond4.lib

//Path to a library.
QT_PHONON_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/phonon4.lib

//The location of the Qt plugins
QT_PLUGINS_DIR:PATH=C:/Qt/4.8.6/plugins

//Path to a file.
QT_QAXCONTAINER_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/ActiveQt

//The Qt QAXCONTAINER library
QT_QAXCONTAINER_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QAxContainer.lib;debug;C:/Qt/4.8.6/lib/QAxContainerd.lib

//Path to a library.
QT_QAXCONTAINER_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QAxContainerd.lib

//Path to a library.
QT_QAXCONTAINER_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QAxContainer.lib

//Path to a file.
QT_QAXSERVER_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/ActiveQt

//The Qt QAXSERVER library
QT_QAXSERVER_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QAxServer.lib;debug;C:/Qt/4.8.6/lib/QAxServerd.lib

//Path to a library.
QT_QAXSERVER_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QAxServerd.lib

//Path to a library.
QT_QAXSERVER_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QAxServer.lib

//Path to a library.
QT_QCNCODECS_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qcncodecsd4.dll

//Path to a library.
QT_QCNCODECS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qcncodecs4.dll

//Path to a program.
QT_QCOLLECTIONGENERATOR_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/qcollectiongenerator.exe

//Path to a library.
QT_QCOREWLANBEARER_PLUGIN_DEBUG:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QCOREWLANBEARER_PLUGIN_RELEASE:FILEPATH=QT_QCOREWLANBEARER_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QDECLARATIVEVIEW_PLUGIN_DEBUG:FILEPATH=QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QDECLARATIVEVIEW_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/qdeclarativeview.dll

//Path to a library.
QT_QDECORATIONDEFAULT_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QDECORATIONDEFAULT_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QDECORATIONWINDOWS_PLUGIN_DEBUG:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QDECORATIONWINDOWS_PLUGIN_RELEASE:FILEPATH=QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QGENERICBEARER_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/bearer/qgenericbearerd4.dll

//Path to a library.
QT_QGENERICBEARER_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/bearer/qgenericbearer4.dll

//Path to a library.
QT_QGIF_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qgifd4.dll

//Path to a library.
QT_QGIF_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qgif4.dll

//Path to a library.
QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/graphicssystems/qglgraphicssystemd4.dll

//Path to a library.
QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/graphicssystems/qglgraphicssystem4.dll

//Path to a library.
QT_QICO_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qicod4.dll

//Path to a library.
QT_QICO_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qico4.dll

//Path to a library.
QT_QIMSW_MULTI_PLUGIN_DEBUG:FILEPATH=QT_QIMSW_MULTI_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QIMSW_MULTI_PLUGIN_RELEASE:FILEPATH=QT_QIMSW_MULTI_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QJPCODECS_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qjpcodecsd4.dll

//Path to a library.
QT_QJPCODECS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qjpcodecs4.dll

//Path to a library.
QT_QJPEG_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qjpegd4.dll

//Path to a library.
QT_QJPEG_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qjpeg4.dll

//Path to a library.
QT_QKRCODECS_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qkrcodecsd4.dll

//Path to a library.
QT_QKRCODECS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qkrcodecs4.dll

//The qmake executable for the Qt installation to use
QT_QMAKE_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/qmake.exe

//Path to a library.
QT_QMNG_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qmngd4.dll

//Path to a library.
QT_QMNG_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qmng4.dll

//Path to a library.
QT_QSQLDB2_PLUGIN_DEBUG:FILEPATH=QT_QSQLDB2_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLDB2_PLUGIN_RELEASE:FILEPATH=QT_QSQLDB2_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLIBASE_PLUGIN_DEBUG:FILEPATH=QT_QSQLIBASE_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLIBASE_PLUGIN_RELEASE:FILEPATH=QT_QSQLIBASE_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLITE2_PLUGIN_DEBUG:FILEPATH=QT_QSQLITE2_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLITE2_PLUGIN_RELEASE:FILEPATH=QT_QSQLITE2_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLITE_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/sqldrivers/qsqlited4.dll

//Path to a library.
QT_QSQLITE_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/sqldrivers/qsqlite4.dll

//Path to a library.
QT_QSQLMYSQL_PLUGIN_DEBUG:FILEPATH=QT_QSQLMYSQL_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLMYSQL_PLUGIN_RELEASE:FILEPATH=QT_QSQLMYSQL_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLOCI_PLUGIN_DEBUG:FILEPATH=QT_QSQLOCI_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLOCI_PLUGIN_RELEASE:FILEPATH=QT_QSQLOCI_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSQLODBC_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/sqldrivers/qsqlodbcd4.dll

//Path to a library.
QT_QSQLODBC_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/sqldrivers/qsqlodbc4.dll

//Path to a library.
QT_QSQLPSQL_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/sqldrivers/qsqlpsqld4.dll

//Path to a library.
QT_QSQLPSQL_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/sqldrivers/qsqlpsql4.dll

//Path to a library.
QT_QSQLTDS_PLUGIN_DEBUG:FILEPATH=QT_QSQLTDS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QSQLTDS_PLUGIN_RELEASE:FILEPATH=QT_QSQLTDS_PLUGIN_RELEASE-NOTFOUND

//Path to a library.
QT_QSVGICON_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/iconengines/qsvgicond4.dll

//Path to a library.
QT_QSVGICON_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/iconengines/qsvgicon4.dll

//Path to a library.
QT_QSVG_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qsvgd4.dll

//Path to a library.
QT_QSVG_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qsvg4.dll

//Path to a library.
QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG:FILEPATH=QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/qt3supportwidgets.dll

//Path to a file.
QT_QT3SUPPORT_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/Qt3Support

//The Qt QT3SUPPORT library
QT_QT3SUPPORT_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/Qt3Support4.lib;debug;C:/Qt/4.8.6/lib/Qt3Supportd4.lib

//Path to a library.
QT_QT3SUPPORT_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/Qt3Supportd4.lib

//Path to a library.
QT_QT3SUPPORT_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/Qt3Support4.lib

//Path to a library.
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/accessible/qtaccessiblecompatwidgetsd4.dll

//Path to a library.
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/accessible/qtaccessiblecompatwidgets4.dll

//Path to a library.
QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/accessible/qtaccessiblewidgetsd4.dll

//Path to a library.
QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/accessible/qtaccessiblewidgets4.dll

//Path to a file.
QT_QTASSISTANTCLIENT_INCLUDE_DIR:PATH=QT_QTASSISTANTCLIENT_INCLUDE_DIR-NOTFOUND

//The Qt QTASSISTANTCLIENT library
QT_QTASSISTANTCLIENT_LIBRARY:STRING=

//Path to a library.
QT_QTASSISTANTCLIENT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTASSISTANTCLIENT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-NOTFOUND

//Path to a file.
QT_QTASSISTANT_INCLUDE_DIR:PATH=QT_QTASSISTANT_INCLUDE_DIR-NOTFOUND

//The Qt QTASSISTANT library
QT_QTASSISTANT_LIBRARY:STRING=

//Path to a library.
QT_QTASSISTANT_LIBRARY_DEBUG:FILEPATH=QT_QTASSISTANT_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTASSISTANT_LIBRARY_RELEASE:FILEPATH=QT_QTASSISTANT_LIBRARY_RELEASE-NOTFOUND

//The Qt QTCLUCENE library
QT_QTCLUCENE_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtCLucene4.lib;debug;C:/Qt/4.8.6/lib/QtCLucened4.lib

//Path to a library.
QT_QTCLUCENE_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtCLucened4.lib

//Path to a library.
QT_QTCLUCENE_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtCLucene4.lib

//Path to a file.
QT_QTCORE_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtCore

//The Qt QTCORE library
QT_QTCORE_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib

//Path to a library.
QT_QTCORE_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtCored4.lib

//Path to a library.
QT_QTCORE_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtCore4.lib

//Path to a file.
QT_QTDBUS_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtDBus

//The Qt QTDBUS library
QT_QTDBUS_LIBRARY:STRING=

//Path to a library.
QT_QTDBUS_LIBRARY_DEBUG:FILEPATH=QT_QTDBUS_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTDBUS_LIBRARY_RELEASE:FILEPATH=QT_QTDBUS_LIBRARY_RELEASE-NOTFOUND

//Path to a file.
QT_QTDECLARATIVE_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtDeclarative

//The Qt QTDECLARATIVE library
QT_QTDECLARATIVE_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtDeclarative4.lib;debug;C:/Qt/4.8.6/lib/QtDeclaratived4.lib

//Path to a library.
QT_QTDECLARATIVE_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtDeclaratived4.lib

//Path to a library.
QT_QTDECLARATIVE_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtDeclarative4.lib

//Path to a file.
QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtDesigner

//The Qt QTDESIGNERCOMPONENTS library
QT_QTDESIGNERCOMPONENTS_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtDesignerComponents4.lib;debug;C:/Qt/4.8.6/lib/QtDesignerComponentsd4.lib

//Path to a library.
QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtDesignerComponentsd4.lib

//Path to a library.
QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtDesignerComponents4.lib

//Path to a file.
QT_QTDESIGNER_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtDesigner

//The Qt QTDESIGNER library
QT_QTDESIGNER_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtDesigner4.lib;debug;C:/Qt/4.8.6/lib/QtDesignerd4.lib

//Path to a library.
QT_QTDESIGNER_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtDesignerd4.lib

//Path to a library.
QT_QTDESIGNER_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtDesigner4.lib

//Path to a file.
QT_QTGUI_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtGui

//The Qt QTGUI library
QT_QTGUI_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib

//Path to a library.
QT_QTGUI_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtGuid4.lib

//Path to a library.
QT_QTGUI_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtGui4.lib

//Path to a file.
QT_QTHELP_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtHelp

//The Qt QTHELP library
QT_QTHELP_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtHelp4.lib;debug;C:/Qt/4.8.6/lib/QtHelpd4.lib

//Path to a library.
QT_QTHELP_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtHelpd4.lib

//Path to a library.
QT_QTHELP_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtHelp4.lib

//Path to a library.
QT_QTIFF_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qtiffd4.dll

//Path to a library.
QT_QTIFF_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/imageformats/qtiff4.dll

//The Qt QTMAIN library
QT_QTMAIN_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/qtmain.lib;debug;C:/Qt/4.8.6/lib/qtmaind.lib

//Path to a library.
QT_QTMAIN_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/qtmaind.lib

//Path to a library.
QT_QTMAIN_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/qtmain.lib

//Path to a file.
QT_QTMULTIMEDIA_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtMultimedia

//The Qt QTMULTIMEDIA library
QT_QTMULTIMEDIA_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtMultimedia4.lib;debug;C:/Qt/4.8.6/lib/QtMultimediad4.lib

//Path to a library.
QT_QTMULTIMEDIA_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtMultimediad4.lib

//Path to a library.
QT_QTMULTIMEDIA_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtMultimedia4.lib

//Path to a file.
QT_QTNETWORK_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtNetwork

//The Qt QTNETWORK library
QT_QTNETWORK_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtNetwork4.lib;debug;C:/Qt/4.8.6/lib/QtNetworkd4.lib

//Path to a library.
QT_QTNETWORK_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtNetworkd4.lib

//Path to a library.
QT_QTNETWORK_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtNetwork4.lib

//Path to a file.
QT_QTNSPLUGIN_INCLUDE_DIR:PATH=QT_QTNSPLUGIN_INCLUDE_DIR-NOTFOUND

//The Qt QTNSPLUGIN library
QT_QTNSPLUGIN_LIBRARY:STRING=

//Path to a library.
QT_QTNSPLUGIN_LIBRARY_DEBUG:FILEPATH=QT_QTNSPLUGIN_LIBRARY_DEBUG-NOTFOUND

//Path to a library.
QT_QTNSPLUGIN_LIBRARY_RELEASE:FILEPATH=QT_QTNSPLUGIN_LIBRARY_RELEASE-NOTFOUND

//Path to a file.
QT_QTOPENGL_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtOpenGL

//The Qt QTOPENGL library
QT_QTOPENGL_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtOpenGL4.lib;debug;C:/Qt/4.8.6/lib/QtOpenGLd4.lib

//Path to a library.
QT_QTOPENGL_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtOpenGLd4.lib

//Path to a library.
QT_QTOPENGL_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtOpenGL4.lib

//Path to a library.
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/graphicssystems/qtracegraphicssystemd4.dll

//Path to a library.
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/graphicssystems/qtracegraphicssystem4.dll

//Path to a library.
QT_QTSCRIPTDBUS_PLUGIN_DEBUG:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QTSCRIPTDBUS_PLUGIN_RELEASE:FILEPATH=QT_QTSCRIPTDBUS_PLUGIN_RELEASE-NOTFOUND

//Path to a file.
QT_QTSCRIPTTOOLS_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtScriptTools

//The Qt QTSCRIPTTOOLS library
QT_QTSCRIPTTOOLS_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtScriptTools4.lib;debug;C:/Qt/4.8.6/lib/QtScriptToolsd4.lib

//Path to a library.
QT_QTSCRIPTTOOLS_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtScriptToolsd4.lib

//Path to a library.
QT_QTSCRIPTTOOLS_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtScriptTools4.lib

//Path to a file.
QT_QTSCRIPT_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtScript

//The Qt QTSCRIPT library
QT_QTSCRIPT_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtScript4.lib;debug;C:/Qt/4.8.6/lib/QtScriptd4.lib

//Path to a library.
QT_QTSCRIPT_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtScriptd4.lib

//Path to a library.
QT_QTSCRIPT_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtScript4.lib

//Path to a file.
QT_QTSQL_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtSql

//The Qt QTSQL library
QT_QTSQL_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtSql4.lib;debug;C:/Qt/4.8.6/lib/QtSqld4.lib

//Path to a library.
QT_QTSQL_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtSqld4.lib

//Path to a library.
QT_QTSQL_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtSql4.lib

//Path to a file.
QT_QTSVG_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtSvg

//The Qt QTSVG library
QT_QTSVG_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtSvg4.lib;debug;C:/Qt/4.8.6/lib/QtSvgd4.lib

//Path to a library.
QT_QTSVG_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtSvgd4.lib

//Path to a library.
QT_QTSVG_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtSvg4.lib

//Path to a file.
QT_QTTEST_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtTest

//The Qt QTTEST library
QT_QTTEST_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtTest4.lib;debug;C:/Qt/4.8.6/lib/QtTestd4.lib

//Path to a library.
QT_QTTEST_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtTestd4.lib

//Path to a library.
QT_QTTEST_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtTest4.lib

//Path to a file.
QT_QTUITOOLS_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtUiTools

//The Qt QTUITOOLS library
QT_QTUITOOLS_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtUiTools.lib;debug;C:/Qt/4.8.6/lib/QtUiToolsd.lib

//Path to a library.
QT_QTUITOOLS_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtUiToolsd.lib

//Path to a library.
QT_QTUITOOLS_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtUiTools.lib

//Path to a library.
QT_QTWCODECS_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qtwcodecsd4.dll

//Path to a library.
QT_QTWCODECS_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/codecs/qtwcodecs4.dll

//Path to a file.
QT_QTWEBKIT_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtWebKit

//The Qt QTWEBKIT library
QT_QTWEBKIT_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtWebKit4.lib;debug;C:/Qt/4.8.6/lib/QtWebKitd4.lib

//Path to a library.
QT_QTWEBKIT_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtWebKitd4.lib

//Path to a library.
QT_QTWEBKIT_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtWebKit4.lib

//Path to a file.
QT_QTXMLPATTERNS_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtXmlPatterns

//The Qt QTXMLPATTERNS library
QT_QTXMLPATTERNS_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtXmlPatterns4.lib;debug;C:/Qt/4.8.6/lib/QtXmlPatternsd4.lib

//Path to a library.
QT_QTXMLPATTERNS_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtXmlPatternsd4.lib

//Path to a library.
QT_QTXMLPATTERNS_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtXmlPatterns4.lib

//Path to a file.
QT_QTXML_INCLUDE_DIR:PATH=C:/Qt/4.8.6/include/QtXml

//The Qt QTXML library
QT_QTXML_LIBRARY:STRING=optimized;C:/Qt/4.8.6/lib/QtXml4.lib;debug;C:/Qt/4.8.6/lib/QtXmld4.lib

//Path to a library.
QT_QTXML_LIBRARY_DEBUG:FILEPATH=C:/Qt/4.8.6/lib/QtXmld4.lib

//Path to a library.
QT_QTXML_LIBRARY_RELEASE:FILEPATH=C:/Qt/4.8.6/lib/QtXml4.lib

//Path to a library.
QT_QWEBVIEW_PLUGIN_DEBUG:FILEPATH=QT_QWEBVIEW_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QWEBVIEW_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/qwebview.dll

//Path to a library.
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE:FILEPATH=QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-NOTFOUND

//Path to a program.
QT_RCC_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/rcc.exe

//Path to a library.
QT_TASKMENUEXTENSION_PLUGIN_DEBUG:FILEPATH=C:/Qt/4.8.6/plugins/designer/taskmenuextensiond.dll

//Path to a library.
QT_TASKMENUEXTENSION_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/taskmenuextension.dll

//Delay between invocation of each testing event.
QT_TESTING_EVENT_PLAYBACK_DELAY:STRING=100

//The location of the Qt translations
QT_TRANSLATIONS_DIR:PATH=C:/Qt/4.8.6/translations

//Path to a program.
QT_UIC3_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/uic3.exe

//Path to a program.
QT_UIC_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/uic.exe

//Path to a library.
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG:FILEPATH=QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-NOTFOUND

//Path to a library.
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE:FILEPATH=C:/Qt/4.8.6/plugins/designer/worldtimeclockplugin.dll

//xmlpatterns used to generate html from Proxy documentation.
QT_XMLPATTERNS_EXECUTABLE:FILEPATH=C:/Qt/4.8.6/bin/xmlpatterns.exe

//Dependencies for the target
QVTKWidgetPlugin_LIB_DEPENDS:STATIC=optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Value Computed by CMake
QtTesting_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/ThirdParty/QtTesting/vtkqttesting

//Dependencies for the target
QtTesting_LIB_DEPENDS:STATIC=optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Value Computed by CMake
QtTesting_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/ThirdParty/QtTesting/vtkqttesting

//Dependencies for the target
QuadView_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Value Computed by CMake
RGBZView_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/Plugins/RGBZView

//Dependencies for the target
RGBZView_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Value Computed by CMake
RGBZView_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/Plugins/RGBZView

//Path to scp command, used by CTest for submitting results to
// a Dart server
SCPCOMMAND:FILEPATH=SCPCOMMAND-NOTFOUND

//Name of the computer/site where compile is being run
SITE:STRING=VRCC_02

//Dependencies for the target
SLACTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Path to the SLURM sbatch executable
SLURM_SBATCH_COMMAND:FILEPATH=SLURM_SBATCH_COMMAND-NOTFOUND

//Path to the SLURM srun executable
SLURM_SRUN_COMMAND:FILEPATH=SLURM_SRUN_COMMAND-NOTFOUND

//Enable CUDA accelerated filters.
SQTK_CUDA:BOOL=OFF

//Enable debug output to stderr.
SQTK_DEBUG:BOOL=OFF

//Explicitly disable SurfaceLIC plugin ctests
SURFACELIC_PLUGIN_TESTING:BOOL=ON

//Path to a program.
SVNCOMMAND:FILEPATH=C:/Program Files/SlikSvn/bin/svn.exe

//Value Computed by CMake
SciberQuestToolKit_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/Plugins/SciberQuestToolKit

//Dependencies for the target
SciberQuestToolKit_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkSciberQuest;general;vtkSciberQuestCS;general;vtkFiltersFlowPaths;general;vtkSciberQuest;general;vtkPVServerManagerDefault;general;vtksys;general;pqComponents;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Value Computed by CMake
SciberQuestToolKit_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/Plugins/SciberQuestToolKit

//Dependencies for the target
SierraPlotTools_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkPVVTKExtensionsDefault;

//Dependencies for the target
StreamingParticles_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;

//Dependencies for the target
SurfaceLIC_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkRenderingLIC;general;vtkRenderingParallelLIC;

//Dependencies for the target
UncertaintyRendering_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerApplicationCS;general;vtkRenderingParallel;

//Value Computed by CMake
VPIC_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/VPIC

//Dependencies for the target
VPIC_LIB_DEPENDS:STATIC=general;vtksys;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Value Computed by CMake
VPIC_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/VPIC

//Path to a file.
VRPN_INCLUDE_DIR:PATH=E:\immersiveParaview\vrpn

//Path to a library.
VRPN_LIBRARY:FILEPATH=E:/immersiveParaview/vrpn-bin/vrpn.lib

//Dependencies for the target
VRPlugin_LIB_DEPENDS:STATIC=general;pqComponents;general;E:/immersiveParaview/vrpn-bin/vrpn.lib;general;pqApplicationComponents;

//Value Computed by CMake
VTKEXPAT_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/expat/vtkexpat

//Value Computed by CMake
VTKEXPAT_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/expat/vtkexpat

//Value Computed by CMake
VTKFREETYPE_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/freetype/vtkfreetype

//Value Computed by CMake
VTKFREETYPE_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/freetype/vtkfreetype

//Value Computed by CMake
VTKFTGL_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/ftgl

//Value Computed by CMake
VTKFTGL_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/ftgl

//Value Computed by CMake
VTKGL2PS_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/gl2ps/vtkgl2ps

//Value Computed by CMake
VTKGL2PS_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/gl2ps/vtkgl2ps

//Value Computed by CMake
VTKJPEG_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/jpeg/vtkjpeg

//Value Computed by CMake
VTKJPEG_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/jpeg/vtkjpeg

//Value Computed by CMake
VTKNETCDF_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf

//Value Computed by CMake
VTKNETCDF_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf

//Value Computed by CMake
VTKOGGTHEORA_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/oggtheora/vtkoggtheora

//Disable assemby optimizations
VTKOGGTHEORA_DISABLE_ASM:BOOL=OFF

//Disable the use of floating point code in theora
VTKOGGTHEORA_DISABLE_FLOAT:BOOL=OFF

//Additional linker flags for vtkoggtheora when building as a shared
// library
VTKOGGTHEORA_SHARED_LINKER_FLAGS:STRING=

//Value Computed by CMake
VTKOGGTHEORA_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/oggtheora/vtkoggtheora

//Value Computed by CMake
VTKPNG_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/png/vtkpng

//Value Computed by CMake
VTKPNG_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/png/vtkpng

//Value Computed by CMake
VTKSQLite_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/sqlite/vtksqlite

//Value Computed by CMake
VTKSQLite_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/sqlite/vtksqlite

//Value Computed by CMake
VTKTIFF_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/tiff/vtktiff

//Value Computed by CMake
VTKTIFF_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/tiff/vtktiff

//Value Computed by CMake
VTKZLIB_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/zlib/vtkzlib

//Value Computed by CMake
VTKZLIB_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/zlib/vtkzlib

//Build all vtkObject derived classes with object factory new methods.
VTK_ALL_NEW_OBJECT_FACTORY:BOOL=OFF

//Value Computed by CMake
VTK_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK

//Request to build all modules
VTK_BUILD_ALL_MODULES:BOOL=OFF

//Enable modules as needed for testing all the enabled modules
VTK_BUILD_ALL_MODULES_FOR_TESTS:BOOL=OFF

//Local directory holding ExternalData objects in the layout %(algo)/%(hash).
VTK_DATA_STORE:PATH=

//Build leak checking support into VTK.
VTK_DEBUG_LEAKS:BOOL=OFF

//Path to a program.
VTK_GHOSTSCRIPT_EXECUTABLE:FILEPATH=VTK_GHOSTSCRIPT_EXECUTABLE-NOTFOUND

//Location of the OpenGL extensions header file (glext.h).
VTK_GLEXT_FILE:FILEPATH=E:/immersiveParaview/ParaView/VTK/Utilities/ParseOGLExt/headers/glext.h

//Location of the GLX extensions header file (glxext.h).
VTK_GLXEXT_FILE:FILEPATH=E:/immersiveParaview/ParaView/VTK/Utilities/ParseOGLExt/headers/glxext.h

//Request building Imaging modules
VTK_Group_Imaging:BOOL=OFF

//Request building MPI modules
VTK_Group_MPI:BOOL=ON

//Request building ParaViewCore modules
VTK_Group_ParaViewCore:BOOL=ON

//Request building ParaViewQt modules
VTK_Group_ParaViewQt:BOOL=ON

//Request building ParaViewRendering modules
VTK_Group_ParaViewRendering:BOOL=ON

//Request building Qt modules
VTK_Group_Qt:BOOL=ON

//Request building Rendering modules
VTK_Group_Rendering:BOOL=OFF

//Request building of all stand alone modules (no external dependencies
// required)
VTK_Group_StandAlone:BOOL=OFF

//Request building Tk modules
VTK_Group_Tk:BOOL=OFF

//Request building Views modules
VTK_Group_Views:BOOL=ON

//Request building Web modules
VTK_Group_Web:BOOL=OFF

//Enable buggy OpenGL drivers for testing.
VTK_IGNORE_GLDRIVER_BUGS:BOOL=OFF

//Remove all legacy code completely.
VTK_LEGACY_REMOVE:BOOL=OFF

//Silence all legacy code messages.
VTK_LEGACY_SILENT:BOOL=OFF

//Should all modules build instantiators
VTK_MAKE_INSTANTIATORS:BOOL=OFF

//Max number of threads vktMultiThreader will allocate.
VTK_MAX_THREADS:STRING=64

//The full path to mpirun command
VTK_MPIRUN_EXE:FILEPATH=C:/Program Files/Microsoft HPC Pack 2008 R2/Bin/mpiexec.exe

//Maximum number of processors available to run parallel applications.
// (see E:/immersiveParaview/ParaView/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_MAX_NUMPROCS:STRING=2

//Flag used by mpi to specify the number of processes, the next
// option will be the number of processes. (see E:/immersiveParaview/ParaView/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_NUMPROC_FLAG:STRING=-np

//These flags will come after all flags given to MPIRun.(see E:/immersiveParaview/ParaView/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_POSTFLAGS:STRING=

//These flags will be directly before the executable that is being
// run by VTK_MPIRUN_EXE. (see E:/immersiveParaview/ParaView/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_PREFLAGS:STRING=

//These flags will be directly before the number of processess
// flag (see E:/immersiveParaview/ParaView/VTK/Parallel/MPI/CMakeLists.txt
// for more info.)
VTK_MPI_PRENUMPROC_FLAGS:STRING=

//The OpenGL library being used supports off screen Mesa calls
VTK_OPENGL_HAS_OSMESA:BOOL=OFF

VTK_QT_VERSION:STRING=4

//enable parallel timers for the 2d line integral convolution
VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER:BOOL=OFF

//enable parallel timers for the surface lic painter
VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER:BOOL=OFF

//Choose the rendering backend.
VTK_RENDERING_BACKEND:STRING=OpenGL

//Enable OpenGL error check and report
VTK_REPORT_OPENGL_ERRORS:BOOL=ON

//Which multi-threaded parallelism implementation to use. Options
// are Sequential, Simple, Kaapi or TBB
VTK_SMP_IMPLEMENTATION_TYPE:STRING=Sequential

//Value Computed by CMake
VTK_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK

//Build VTK with 64 bit ids
VTK_USE_64BIT_IDS:BOOL=OFF

//Enable tests requiring "large" data
VTK_USE_LARGE_DATA:BOOL=OFF

//Use off screen calls by default
VTK_USE_OFFSCREEN:BOOL=OFF

//Use system-installed EXPAT
VTK_USE_SYSTEM_EXPAT:BOOL=OFF

//Use system-installed Freetype
VTK_USE_SYSTEM_FREETYPE:BOOL=OFF

//Use system-installed GL2PS
VTK_USE_SYSTEM_GL2PS:BOOL=OFF

//Use system-installed HDF5
VTK_USE_SYSTEM_HDF5:BOOL=OFF

//Use system-installed icet
VTK_USE_SYSTEM_ICET:BOOL=OFF

//Use system-installed JPEG
VTK_USE_SYSTEM_JPEG:BOOL=OFF

//Use system-installed JsonCpp
VTK_USE_SYSTEM_JSONCPP:BOOL=OFF

//Use system-installed LIBPROJ4
VTK_USE_SYSTEM_LIBPROJ4:BOOL=OFF

//Use system-installed LibXml2
VTK_USE_SYSTEM_LIBXML2:BOOL=OFF

//Use system-installed NetCDF
VTK_USE_SYSTEM_NETCDF:BOOL=OFF

//Use system-installed OGGTHEORA
VTK_USE_SYSTEM_OGGTHEORA:BOOL=OFF

//Use system-installed PNG
VTK_USE_SYSTEM_PNG:BOOL=OFF

//Use system-installed protobuf
VTK_USE_SYSTEM_PROTOBUF:BOOL=OFF

//Use system-installed pugixml
VTK_USE_SYSTEM_PUGIXML:BOOL=OFF

//Use system-installed qttesting
VTK_USE_SYSTEM_QTTESTING:BOOL=OFF

//Use system-installed TIFF
VTK_USE_SYSTEM_TIFF:BOOL=OFF

//Use system-installed xdmf2
VTK_USE_SYSTEM_XDMF2:BOOL=OFF

//Use system-installed ZLIB
VTK_USE_SYSTEM_ZLIB:BOOL=OFF

//Use TDx interaction devices
VTK_USE_TDX:BOOL=OFF

//Build VTK with Tk support
VTK_USE_TK:BOOL=OFF

//Enable using Video for Windows (vfw32) for video input and output.
VTK_USE_VIDEO_FOR_WINDOWS:BOOL=ON

//Use X for VTK render windows
VTK_USE_X:BOOL=OFF

//Build VPIC with MPI
VTK_VPIC_USE_MPI:BOOL=ON

//Location of the WGL extensions header file (wglext.h).
VTK_WGLEXT_FILE:FILEPATH=E:/immersiveParaview/ParaView/VTK/Utilities/ParseOGLExt/headers/wglext.h

//Path to a file.
VTK_WRAP_HINTS:FILEPATH=E:/immersiveParaview/ParaView/VTK/Wrapping/Tools/hints

//Should VTK Java wrapping be built?
VTK_WRAP_JAVA:BOOL=OFF

//Should VTK Tcl wrapping be built?
VTK_WRAP_TCL:BOOL=OFF

//Build Xdmf with MPI
VTK_XDMF_USE_MPI:BOOL=OFF

//XDMF should use MPI
XDMF_BUILD_MPI:BOOL=OFF

//XDMF has Network Distributed Global Memory (NDGM)
XDMF_HAS_NDGM:BOOL=OFF

//Path to a file.
XDMF_HAVE_FCNTL:PATH=C:/Program Files (x86)/Microsoft Visual Studio 10.0/VC/include

//Path to a file.
XDMF_HAVE_MMAN:PATH=XDMF_HAVE_MMAN-NOTFOUND

//Path to a file.
XDMF_HAVE_NETINET:PATH=XDMF_HAVE_NETINET-NOTFOUND

//Use bzip2
XDMF_USE_BZIP2:BOOL=OFF

//Build GZip Compression
XDMF_USE_GZIP:BOOL=OFF

//Build Support for MySQL DataItems
XDMF_USE_MYSQL:BOOL=OFF

//Path to a file.
ZLIB_INCLUDE_DIR:PATH=ZLIB_INCLUDE_DIR-NOTFOUND

//Path to a library.
ZLIB_LIBRARY:FILEPATH=ZLIB_LIBRARY-NOTFOUND

//Value Computed by CMake
alglib_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/alglib

//Value Computed by CMake
alglib_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/alglib

//Value Computed by CMake
libproj4_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/libproj4/vtklibproj4

//Value Computed by CMake
libproj4_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/libproj4/vtklibproj4

//Value Computed by CMake
netcdf_cxx_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/cxx

//Value Computed by CMake
netcdf_cxx_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/cxx

//Value Computed by CMake
netcdf_libdispatch_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch

//Value Computed by CMake
netcdf_libdispatch_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch

//Value Computed by CMake
netcdf_liblib_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/liblib

//Value Computed by CMake
netcdf_liblib_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/liblib

//Value Computed by CMake
netcdf_libsrc4_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4

//Value Computed by CMake
netcdf_libsrc4_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4

//Value Computed by CMake
netcdf_libsrc_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/netcdf/vtknetcdf/libsrc

//Value Computed by CMake
netcdf_libsrc_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc

//Dependencies for the target
pqApplicationComponents_LIB_DEPENDS:STATIC=general;pqComponents;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;

//Dependencies for the target
pqComponents_LIB_DEPENDS:STATIC=general;pqCore;general;pqPython;general;vtkChartsCore;general;vtkIOImage;general;vtkPVAnimation;general;vtkPVServerManagerDefault;general;vtkPVServerManagerRendering;general;vtksys;

//Dependencies for the target
pqCore_LIB_DEPENDS:STATIC=general;pqWidgets;general;vtkGUISupportQt;general;vtkPVAnimation;general;vtkPVClientServerCoreDefault;general;vtkPVServerManagerApplication;general;vtkPVServerManagerDefault;general;vtksys;general;vtkTestingRendering;optimized;C:/Qt/4.8.6/lib/QtUiTools.lib;debug;C:/Qt/4.8.6/lib/QtUiToolsd.lib;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtXml4.lib;debug;C:/Qt/4.8.6/lib/QtXmld4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
pqDeprecated_LIB_DEPENDS:STATIC=general;pqApplicationComponents;general;vtkChartsCore;general;vtkViewsContext2D;

//Dependencies for the target
pqPython_LIB_DEPENDS:STATIC=general;pqCore;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;

//Dependencies for the target
pqWidgets_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkPVServerManagerCore;general;QtTesting;optimized;C:/Qt/4.8.6/lib/QtHelp4.lib;debug;C:/Qt/4.8.6/lib/QtHelpd4.lib;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtXml4.lib;debug;C:/Qt/4.8.6/lib/QtXmld4.lib;optimized;C:/Qt/4.8.6/lib/QtSql4.lib;debug;C:/Qt/4.8.6/lib/QtSqld4.lib;optimized;C:/Qt/4.8.6/lib/QtNetwork4.lib;debug;C:/Qt/4.8.6/lib/QtNetworkd4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for target
protobuf-lite_LIB_DEPENDS:STATIC=

//Value Computed by CMake
protobuf_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/ThirdParty/protobuf/vtkprotobuf

//Dependencies for target
protobuf_LIB_DEPENDS:STATIC=

//Value Computed by CMake
protobuf_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/ThirdParty/protobuf/vtkprotobuf

//Path to smooth.flash data file.
smooth_flash:FILEPATH=smooth_flash-NOTFOUND

//Value Computed by CMake
verdict_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/verdict/vtkverdict

//Dependencies for target
verdict_LIB_DEPENDS:STATIC=

//Value Computed by CMake
verdict_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/verdict/vtkverdict

//Dependencies for the target
vtkChartsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkChartsCore;

//Dependencies for the target
vtkChartsCorePythonD_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkInfovisCorePythonD;general;vtkRenderingContext2DPythonD;

//Dependencies for the target
vtkChartsCorePython_LIB_DEPENDS:STATIC=general;vtkChartsCorePythonD;

//Dependencies for the target
vtkChartsCore_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkCommonColor;general;vtkInfovisCore;

//Dependencies for the target
vtkClientServer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;C:/Python27/libs/python27.lib;general;vtkPythonInterpreter;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkCommonColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonColor;

//Dependencies for the target
vtkCommonColorPythonD_LIB_DEPENDS:STATIC=general;vtkCommonColor;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;

//Dependencies for the target
vtkCommonColorPython_LIB_DEPENDS:STATIC=general;vtkCommonColorPythonD;

//Dependencies for the target
vtkCommonColor_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonComputationalGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonComputationalGeometry;

//Dependencies for the target
vtkCommonComputationalGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;

//Dependencies for the target
vtkCommonComputationalGeometryPython_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometryPythonD;

//Dependencies for the target
vtkCommonComputationalGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;

//Dependencies for the target
vtkCommonCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;

//Dependencies for the target
vtkCommonCorePythonD_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkCommonCorePython_LIB_DEPENDS:STATIC=general;vtkCommonCorePythonD;

//Dependencies for the target
vtkCommonCore_LIB_DEPENDS:STATIC=general;vtksys;

//Dependencies for the target
vtkCommonDataModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonDataModelPythonD_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkWrappingPythonCore;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkCommonDataModelPython_LIB_DEPENDS:STATIC=general;vtkCommonDataModelPythonD;

//Dependencies for the target
vtkCommonDataModel_LIB_DEPENDS:STATIC=general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtksys;

//Dependencies for the target
vtkCommonExecutionModelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonExecutionModel;

//Dependencies for the target
vtkCommonExecutionModelPythonD_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;

//Dependencies for the target
vtkCommonExecutionModelPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkCommonExecutionModel_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;

//Dependencies for the target
vtkCommonMathCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMath;

//Dependencies for the target
vtkCommonMathPythonD_LIB_DEPENDS:STATIC=general;vtkCommonMath;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;

//Dependencies for the target
vtkCommonMathPython_LIB_DEPENDS:STATIC=general;vtkCommonMathPythonD;

//Dependencies for the target
vtkCommonMath_LIB_DEPENDS:STATIC=general;vtkCommonCore;

//Dependencies for the target
vtkCommonMiscCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonMisc;

//Dependencies for the target
vtkCommonMiscPythonD_LIB_DEPENDS:STATIC=general;vtkCommonMisc;general;vtkWrappingPythonCore;general;vtkCommonMathPythonD;

//Dependencies for the target
vtkCommonMiscPython_LIB_DEPENDS:STATIC=general;vtkCommonMiscPythonD;

//Dependencies for the target
vtkCommonMisc_LIB_DEPENDS:STATIC=general;vtkCommonMath;

//Dependencies for the target
vtkCommonSystemCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonSystem;

//Dependencies for the target
vtkCommonSystemPythonD_LIB_DEPENDS:STATIC=general;vtkCommonSystem;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;

//Dependencies for the target
vtkCommonSystemPython_LIB_DEPENDS:STATIC=general;vtkCommonSystemPythonD;

//Dependencies for the target
vtkCommonSystem_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtksys;

//Dependencies for the target
vtkCommonTransformsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonTransforms;

//Dependencies for the target
vtkCommonTransformsPythonD_LIB_DEPENDS:STATIC=general;vtkCommonTransforms;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonMathPythonD;

//Dependencies for the target
vtkCommonTransformsPython_LIB_DEPENDS:STATIC=general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkCommonTransforms_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonMath;

//Dependencies for target
vtkDICOMParser_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkDomainsChemistryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkDomainsChemistry;

//Dependencies for the target
vtkDomainsChemistryPythonD_LIB_DEPENDS:STATIC=general;vtkDomainsChemistry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOXMLPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkDomainsChemistryPython_LIB_DEPENDS:STATIC=general;vtkDomainsChemistryPythonD;

//Dependencies for the target
vtkDomainsChemistry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkRenderingCore;general;vtkIOXML;general;vtkFiltersSources;

//Value Computed by CMake
vtkExodus2_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/exodusII/vtkexodusII

//Value Computed by CMake
vtkExodus2_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/exodusII/vtkexodusII

//Dependencies for the target
vtkEyeDomeLightingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkEyeDomeLighting;

//Dependencies for the target
vtkEyeDomeLighting_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;

//Dependencies for the target
vtkFiltersAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersAMR;

//Dependencies for the target
vtkFiltersAMRPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkFiltersAMRPython_LIB_DEPENDS:STATIC=general;vtkFiltersAMRPythonD;

//Dependencies for the target
vtkFiltersAMR_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkParallelCore;

//Dependencies for the target
vtkFiltersCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersCorePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkFiltersCorePython_LIB_DEPENDS:STATIC=general;vtkFiltersCorePythonD;

//Dependencies for the target
vtkFiltersCore_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;

//Dependencies for the target
vtkFiltersExtractionCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersExtraction;

//Dependencies for the target
vtkFiltersExtractionPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersStatisticsPythonD;

//Dependencies for the target
vtkFiltersExtractionPython_LIB_DEPENDS:STATIC=general;vtkFiltersExtractionPythonD;

//Dependencies for the target
vtkFiltersExtraction_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersCore;general;vtkFiltersGeneral;general;vtkFiltersStatistics;

//Dependencies for the target
vtkFiltersFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersFlowPaths;

//Dependencies for the target
vtkFiltersFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPaths;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkFiltersFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPathsPythonD;

//Dependencies for the target
vtkFiltersFlowPaths_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersGeneral;general;vtkFiltersSources;general;vtkIOCore;

//Dependencies for the target
vtkFiltersGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersCorePythonD;

//Dependencies for the target
vtkFiltersGeneralPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersGeneral_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersGenericCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeneric;

//Dependencies for the target
vtkFiltersGenericPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersGeneric;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkFiltersGenericPython_LIB_DEPENDS:STATIC=general;vtkFiltersGenericPythonD;

//Dependencies for the target
vtkFiltersGeneric_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersGeometry;

//Dependencies for the target
vtkFiltersGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersGeometry;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;

//Dependencies for the target
vtkFiltersGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersGeometryPythonD;

//Dependencies for the target
vtkFiltersGeometry_LIB_DEPENDS:STATIC=general;vtkFiltersCore;

//Dependencies for the target
vtkFiltersHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHybrid;

//Dependencies for the target
vtkFiltersHybridPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkFiltersHybridPython_LIB_DEPENDS:STATIC=general;vtkFiltersHybridPythonD;

//Dependencies for the target
vtkFiltersHybrid_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkImagingSources;general;vtkRenderingCore;

//Dependencies for the target
vtkFiltersHyperTreeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersHyperTree;

//Dependencies for the target
vtkFiltersHyperTreePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTree;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersHyperTreePython_LIB_DEPENDS:STATIC=general;vtkFiltersHyperTreePythonD;

//Dependencies for the target
vtkFiltersHyperTree_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersImaging;

//Dependencies for the target
vtkFiltersImagingPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersImaging;general;vtkWrappingPythonCore;general;vtkFiltersStatisticsPythonD;general;vtkImagingGeneralPythonD;general;vtkImagingSourcesPythonD;

//Dependencies for the target
vtkFiltersImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersImagingPythonD;

//Dependencies for the target
vtkFiltersImaging_LIB_DEPENDS:STATIC=general;vtkFiltersStatistics;general;vtkImagingGeneral;general;vtkImagingSources;

//Dependencies for the target
vtkFiltersModelingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersModeling;

//Dependencies for the target
vtkFiltersModelingPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersModeling;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkFiltersModelingPython_LIB_DEPENDS:STATIC=general;vtkFiltersModelingPythonD;

//Dependencies for the target
vtkFiltersModeling_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallel;

//Dependencies for the target
vtkFiltersParallelFlowPathsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelFlowPaths;

//Dependencies for the target
vtkFiltersParallelFlowPathsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelFlowPaths;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkFiltersParallelFlowPathsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelFlowPathsPythonD;

//Dependencies for the target
vtkFiltersParallelFlowPaths_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersFlowPaths;general;vtkParallelCore;general;vtkParallelMPI;

//Dependencies for the target
vtkFiltersParallelGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelGeometry;

//Dependencies for the target
vtkFiltersParallelGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelGeometry;general;vtkWrappingPythonCore;general;vtkFiltersGeometryPythonD;general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkFiltersParallelGeometryPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelGeometryPythonD;

//Dependencies for the target
vtkFiltersParallelGeometry_LIB_DEPENDS:STATIC=general;vtkFiltersGeometry;general;vtkParallelMPI;

//Dependencies for the target
vtkFiltersParallelImagingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelImaging;

//Dependencies for the target
vtkFiltersParallelImagingPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImaging;general;vtkWrappingPythonCore;general;vtkFiltersImagingPythonD;general;vtkFiltersParallelPythonD;general;vtkIOLegacyPythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkFiltersParallelImagingPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelImagingPythonD;

//Dependencies for the target
vtkFiltersParallelImaging_LIB_DEPENDS:STATIC=general;vtkFiltersImaging;general;vtkFiltersParallel;general;vtkIOLegacy;general;vtkImagingCore;general;vtkParallelCore;

//Dependencies for the target
vtkFiltersParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelMPI;

//Dependencies for the target
vtkFiltersParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelMPI;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersParallelPythonD;general;vtkImagingCorePythonD;general;vtkParallelCorePythonD;general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkFiltersParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelMPIPythonD;

//Dependencies for the target
vtkFiltersParallelMPI_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersGeneral;general;vtkFiltersParallel;general;vtkImagingCore;general;vtkParallelCore;general;vtkParallelMPI;

//Dependencies for the target
vtkFiltersParallelPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersModelingPythonD;general;vtkParallelCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkFiltersParallelPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelPythonD;

//Dependencies for the target
vtkFiltersParallelStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersParallelStatistics;

//Dependencies for the target
vtkFiltersParallelStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersParallelStatistics;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersStatisticsPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkFiltersParallelStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersParallelStatisticsPythonD;

//Dependencies for the target
vtkFiltersParallelStatistics_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkFiltersStatistics;general;vtkParallelCore;general;vtkalglib;

//Dependencies for the target
vtkFiltersParallel_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersGeometry;general;vtkFiltersModeling;general;vtkParallelCore;general;vtkRenderingCore;

//Dependencies for the target
vtkFiltersProgrammableCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersProgrammable;

//Dependencies for the target
vtkFiltersProgrammablePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammable;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkFiltersProgrammablePython_LIB_DEPENDS:STATIC=general;vtkFiltersProgrammablePythonD;

//Dependencies for the target
vtkFiltersProgrammable_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;

//Dependencies for the target
vtkFiltersPythonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersPython;

//Dependencies for the target
vtkFiltersPythonPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersPython;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkFiltersPythonPython_LIB_DEPENDS:STATIC=general;vtkFiltersPythonPythonD;

//Dependencies for the target
vtkFiltersPython_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;C:/Python27/libs/python27.lib;general;vtkWrappingPythonCore;

//Dependencies for the target
vtkFiltersSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersSources;

//Dependencies for the target
vtkFiltersSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersSources;general;vtkWrappingPythonCore;general;vtkCommonComputationalGeometryPythonD;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersSourcesPython_LIB_DEPENDS:STATIC=general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkFiltersSources_LIB_DEPENDS:STATIC=general;vtkCommonComputationalGeometry;general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersStatisticsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersStatistics;

//Dependencies for the target
vtkFiltersStatisticsPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersStatistics;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonTransformsPythonD;general;vtkImagingFourierPythonD;

//Dependencies for the target
vtkFiltersStatisticsPython_LIB_DEPENDS:STATIC=general;vtkFiltersStatisticsPythonD;

//Dependencies for the target
vtkFiltersStatistics_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonTransforms;general;vtkImagingFourier;general;vtkalglib;

//Dependencies for the target
vtkFiltersTextureCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersTexture;

//Dependencies for the target
vtkFiltersTexturePythonD_LIB_DEPENDS:STATIC=general;vtkFiltersTexture;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkFiltersTexturePython_LIB_DEPENDS:STATIC=general;vtkFiltersTexturePythonD;

//Dependencies for the target
vtkFiltersTexture_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;

//Dependencies for the target
vtkFiltersVerdictCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkFiltersVerdict;

//Dependencies for the target
vtkFiltersVerdictPythonD_LIB_DEPENDS:STATIC=general;vtkFiltersVerdict;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkFiltersVerdictPython_LIB_DEPENDS:STATIC=general;vtkFiltersVerdictPythonD;

//Dependencies for the target
vtkFiltersVerdict_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;verdict;

//Dependencies for the target
vtkGUISupportQtOpenGL_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkRenderingOpenGL;optimized;C:/Qt/4.8.6/lib/QtOpenGL4.lib;debug;C:/Qt/4.8.6/lib/QtOpenGLd4.lib;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkGUISupportQtSQL_LIB_DEPENDS:STATIC=general;vtkIOSQL;general;vtksys;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtSql4.lib;debug;C:/Qt/4.8.6/lib/QtSqld4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkGUISupportQtWebkit_LIB_DEPENDS:STATIC=general;vtkViewsQt;optimized;C:/Qt/4.8.6/lib/QtWebKit4.lib;debug;C:/Qt/4.8.6/lib/QtWebKitd4.lib;optimized;C:/Qt/4.8.6/lib/QtXmlPatterns4.lib;debug;C:/Qt/4.8.6/lib/QtXmlPatternsd4.lib;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtNetwork4.lib;debug;C:/Qt/4.8.6/lib/QtNetworkd4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkGUISupportQt_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkRenderingOpenGL;general;vtkFiltersExtraction;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtNetwork4.lib;debug;C:/Qt/4.8.6/lib/QtNetworkd4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkGeovisCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkGeovisCore;

//Dependencies for the target
vtkGeovisCorePythonD_LIB_DEPENDS:STATIC=general;vtkGeovisCore;general;vtkWrappingPythonCore;general;vtkIOXMLPythonD;general;vtkInfovisLayoutPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkViewsCorePythonD;

//Dependencies for the target
vtkGeovisCorePython_LIB_DEPENDS:STATIC=general;vtkGeovisCorePythonD;

//Dependencies for the target
vtkGeovisCore_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkInfovisLayout;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkRenderingCore;general;vtkViewsCore;general;vtkproj4;

//Dependencies for the target
vtkIOAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOAMR;

//Dependencies for the target
vtkIOAMRPythonD_LIB_DEPENDS:STATIC=general;vtkIOAMR;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOAMRPython_LIB_DEPENDS:STATIC=general;vtkIOAMRPythonD;

//Dependencies for the target
vtkIOAMR_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkParallelCore;general;vtkhdf5_hl;general;vtkhdf5;general;vtksys;

//Dependencies for the target
vtkIOCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOCore;

//Dependencies for the target
vtkIOCorePythonD_LIB_DEPENDS:STATIC=general;vtkIOCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;

//Dependencies for the target
vtkIOCorePython_LIB_DEPENDS:STATIC=general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkzlib;general;vtksys;

//Dependencies for the target
vtkIOEnSightCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOEnSight;

//Dependencies for the target
vtkIOEnSightPythonD_LIB_DEPENDS:STATIC=general;vtkIOEnSight;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;

//Dependencies for the target
vtkIOEnSightPython_LIB_DEPENDS:STATIC=general;vtkIOEnSightPythonD;

//Dependencies for the target
vtkIOEnSight_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;

//Dependencies for the target
vtkIOExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExodus;

//Dependencies for the target
vtkIOExodusPythonD_LIB_DEPENDS:STATIC=general;vtkIOExodus;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOExodusPython_LIB_DEPENDS:STATIC=general;vtkIOExodusPythonD;

//Dependencies for the target
vtkIOExodus_LIB_DEPENDS:STATIC=general;vtkFiltersGeneral;general;vtkIOXML;general;vtkexoIIc;general;vtksys;

//Dependencies for the target
vtkIOExportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOExport;

//Dependencies for the target
vtkIOExportPythonD_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersGeometryPythonD;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingGL2PSPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkIOExportPython_LIB_DEPENDS:STATIC=general;vtkIOExportPythonD;

//Dependencies for the target
vtkIOExport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkImagingCore;general;vtkRenderingAnnotation;general;vtkRenderingContext2D;general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingGL2PS;general;vtkRenderingLabel;general;vtkRenderingOpenGL;general;vtkIOImage;general;vtkFiltersGeometry;general;vtkgl2ps;

//Dependencies for the target
vtkIOGeometryCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOGeometry;

//Dependencies for the target
vtkIOGeometryPythonD_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOGeometryPython_LIB_DEPENDS:STATIC=general;vtkIOGeometryPythonD;

//Dependencies for the target
vtkIOGeometry_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkzlib;general;vtkjsoncpp;general;vtksys;

//Dependencies for the target
vtkIOImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImage;

//Dependencies for the target
vtkIOImagePythonD_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOImagePython_LIB_DEPENDS:STATIC=general;vtkIOImagePythonD;

//Dependencies for the target
vtkIOImage_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkCommonTransforms;general;vtkIOCore;general;vtkjpeg;general;vtkpng;general;vtktiff;general;vtkmetaio;general;vtkDICOMParser;general;vtkzlib;general;vtksys;

//Dependencies for the target
vtkIOImportCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOImport;

//Dependencies for the target
vtkIOImportPythonD_LIB_DEPENDS:STATIC=general;vtkIOImport;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkIOImportPython_LIB_DEPENDS:STATIC=general;vtkIOImportPythonD;

//Dependencies for the target
vtkIOImport_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkRenderingCore;general;vtkFiltersSources;

//Dependencies for the target
vtkIOInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOInfovis;

//Dependencies for the target
vtkIOInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkIOInfovis;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkInfovisCorePythonD;

//Dependencies for the target
vtkIOInfovisPython_LIB_DEPENDS:STATIC=general;vtkIOInfovisPythonD;

//Dependencies for the target
vtkIOInfovis_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkIOLegacy;general;vtkIOXML;general;vtkInfovisCore;general;vtklibxml2;general;vtksys;

//Dependencies for the target
vtkIOLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLSDyna;

//Dependencies for the target
vtkIOLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkIOLSDyna;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOLSDynaPythonD;

//Dependencies for the target
vtkIOLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkIOXML;general;vtksys;

//Dependencies for the target
vtkIOLegacyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOLegacy;

//Dependencies for the target
vtkIOLegacyPythonD_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOLegacyPython_LIB_DEPENDS:STATIC=general;vtkIOLegacyPythonD;

//Dependencies for the target
vtkIOLegacy_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtksys;

//Dependencies for the target
vtkIOMPIImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIImage;

//Dependencies for the target
vtkIOMPIImagePythonD_LIB_DEPENDS:STATIC=general;vtkIOMPIImage;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkIOMPIImagePython_LIB_DEPENDS:STATIC=general;vtkIOMPIImagePythonD;

//Dependencies for the target
vtkIOMPIImage_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkIOImage;general;vtkParallelMPI;general;vtksys;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkIOMPIParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMPIParallel;

//Dependencies for the target
vtkIOMPIParallelPythonD_LIB_DEPENDS:STATIC=general;vtkIOMPIParallel;general;vtkWrappingPythonCore;general;vtkIOGeometryPythonD;general;vtkIOGeometryPythonD;general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkIOMPIParallelPython_LIB_DEPENDS:STATIC=general;vtkIOMPIParallelPythonD;

//Dependencies for the target
vtkIOMPIParallel_LIB_DEPENDS:STATIC=general;vtkIOGeometry;general;vtkIOGeometry;general;vtkParallelMPI;general;vtksys;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkIOMovieCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOMovie;

//Dependencies for the target
vtkIOMoviePythonD_LIB_DEPENDS:STATIC=general;vtkIOMovie;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOMoviePython_LIB_DEPENDS:STATIC=general;vtkIOMoviePythonD;

//Dependencies for the target
vtkIOMovie_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonSystem;general;vtkIOCore;general;vtkoggtheora;general;vfw32;

//Dependencies for the target
vtkIONetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIONetCDF;

//Dependencies for the target
vtkIONetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkIONetCDF;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIONetCDFPython_LIB_DEPENDS:STATIC=general;vtkIONetCDFPythonD;

//Dependencies for the target
vtkIONetCDF_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkIOCore;general;vtksys;general;vtkNetCDF;general;vtkNetCDF_cxx;

//Dependencies for the target
vtkIOPLYCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOPLY;

//Dependencies for the target
vtkIOPLYPythonD_LIB_DEPENDS:STATIC=general;vtkIOPLY;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonMiscPythonD;general;vtkIOGeometryPythonD;

//Dependencies for the target
vtkIOPLYPython_LIB_DEPENDS:STATIC=general;vtkIOPLYPythonD;

//Dependencies for the target
vtkIOPLY_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonMisc;general;vtkIOGeometry;

//Dependencies for the target
vtkIOParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallel;

//Dependencies for the target
vtkIOParallelExodusCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelExodus;

//Dependencies for the target
vtkIOParallelExodusPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelExodus;general;vtkWrappingPythonCore;general;vtkIOExodusPythonD;general;vtkIOExodusPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelExodusPython_LIB_DEPENDS:STATIC=general;vtkIOParallelExodusPythonD;

//Dependencies for the target
vtkIOParallelExodus_LIB_DEPENDS:STATIC=general;vtkIOExodus;general;vtkIOExodus;general;vtkParallelCore;general;vtksys;general;vtkexoIIc;

//Dependencies for the target
vtkIOParallelLSDynaCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelLSDyna;

//Dependencies for the target
vtkIOParallelLSDynaPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelLSDyna;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkIOLSDynaPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelLSDynaPython_LIB_DEPENDS:STATIC=general;vtkIOParallelLSDynaPythonD;

//Dependencies for the target
vtkIOParallelLSDyna_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkIOLSDyna;general;vtkParallelCore;

//Dependencies for the target
vtkIOParallelNetCDFCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelNetCDF;

//Dependencies for the target
vtkIOParallelNetCDFPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDF;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkIOParallelNetCDFPython_LIB_DEPENDS:STATIC=general;vtkIOParallelNetCDFPythonD;

//Dependencies for the target
vtkIOParallelNetCDF_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkParallelMPI;general;vtkNetCDF;general;vtkNetCDF_cxx;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkIOParallelPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallel;general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkIONetCDFPythonD;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelPython_LIB_DEPENDS:STATIC=general;vtkIOParallelPythonD;

//Dependencies for the target
vtkIOParallelXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOParallelXML;

//Dependencies for the target
vtkIOParallelXMLPythonD_LIB_DEPENDS:STATIC=general;vtkIOParallelXML;general;vtkWrappingPythonCore;general;vtkIOXMLPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOParallelXMLPython_LIB_DEPENDS:STATIC=general;vtkIOParallelXMLPythonD;

//Dependencies for the target
vtkIOParallelXML_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkParallelCore;general;vtksys;

//Dependencies for the target
vtkIOParallel_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkIOImage;general;vtkIONetCDF;general;vtkIOXML;general;vtkParallelCore;general;vtkexoIIc;general;vtkNetCDF;general;vtkNetCDF_cxx;

//Dependencies for the target
vtkIOSQLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOSQL;

//Dependencies for the target
vtkIOSQLPythonD_LIB_DEPENDS:STATIC=general;vtkIOSQL;general;vtkWrappingPythonCore;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOSQLPython_LIB_DEPENDS:STATIC=general;vtkIOSQLPythonD;

//Dependencies for the target
vtkIOSQL_LIB_DEPENDS:STATIC=general;vtkIOCore;general;vtksys;general;vtksqlite;

//Dependencies for the target
vtkIOVPICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOVPIC;

//Dependencies for the target
vtkIOVPICPythonD_LIB_DEPENDS:STATIC=general;vtkIOVPIC;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkIOVPICPython_LIB_DEPENDS:STATIC=general;vtkIOVPICPythonD;

//Dependencies for the target
vtkIOVPIC_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkParallelCore;general;VPIC;

//Dependencies for the target
vtkIOXMLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXML;

//Dependencies for the target
vtkIOXMLParserCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXMLParser;

//Dependencies for the target
vtkIOXMLParserPythonD_LIB_DEPENDS:STATIC=general;vtkIOXMLParser;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMiscPythonD;general;vtkCommonSystemPythonD;general;vtkIOCorePythonD;

//Dependencies for the target
vtkIOXMLParserPython_LIB_DEPENDS:STATIC=general;vtkIOXMLParserPythonD;

//Dependencies for the target
vtkIOXMLParser_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonMisc;general;vtkCommonSystem;general;vtkIOCore;general;vtkexpat;

//Dependencies for the target
vtkIOXMLPythonD_LIB_DEPENDS:STATIC=general;vtkIOXML;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkIOGeometryPythonD;general;vtkIOXMLParserPythonD;

//Dependencies for the target
vtkIOXMLPython_LIB_DEPENDS:STATIC=general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOXML_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkIOGeometry;general;vtkIOXMLParser;general;vtksys;

//Dependencies for the target
vtkIOXdmf2CS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkIOXdmf2;

//Dependencies for the target
vtkIOXdmf2PythonD_LIB_DEPENDS:STATIC=general;vtkIOXdmf2;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkFiltersExtractionPythonD;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;

//Dependencies for the target
vtkIOXdmf2Python_LIB_DEPENDS:STATIC=general;vtkIOXdmf2PythonD;

//Dependencies for the target
vtkIOXdmf2_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkFiltersExtraction;general;vtkIOLegacy;general;vtkIOXML;general;vtksys;general;vtkxdmf2;

//Dependencies for the target
vtkImagingColorCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingColor;

//Dependencies for the target
vtkImagingColorPythonD_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingColorPython_LIB_DEPENDS:STATIC=general;vtkImagingColorPythonD;

//Dependencies for the target
vtkImagingColor_LIB_DEPENDS:STATIC=general;vtkImagingCore;

//Dependencies for the target
vtkImagingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingCore;

//Dependencies for the target
vtkImagingCorePythonD_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonExecutionModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonSystemPythonD;general;vtkCommonTransformsPythonD;

//Dependencies for the target
vtkImagingCorePython_LIB_DEPENDS:STATIC=general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonExecutionModel;general;vtkCommonMath;general;vtkCommonSystem;general;vtkCommonTransforms;

//Dependencies for the target
vtkImagingFourierCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingFourier;

//Dependencies for the target
vtkImagingFourierPythonD_LIB_DEPENDS:STATIC=general;vtkImagingFourier;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingFourierPython_LIB_DEPENDS:STATIC=general;vtkImagingFourierPythonD;

//Dependencies for the target
vtkImagingFourier_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtksys;

//Dependencies for the target
vtkImagingGeneralCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingGeneral;

//Dependencies for the target
vtkImagingGeneralPythonD_LIB_DEPENDS:STATIC=general;vtkImagingGeneral;general;vtkWrappingPythonCore;general;vtkImagingSourcesPythonD;

//Dependencies for the target
vtkImagingGeneralPython_LIB_DEPENDS:STATIC=general;vtkImagingGeneralPythonD;

//Dependencies for the target
vtkImagingGeneral_LIB_DEPENDS:STATIC=general;vtkImagingSources;

//Dependencies for the target
vtkImagingHybridCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingHybrid;

//Dependencies for the target
vtkImagingHybridPythonD_LIB_DEPENDS:STATIC=general;vtkImagingHybrid;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingHybridPython_LIB_DEPENDS:STATIC=general;vtkImagingHybridPythonD;

//Dependencies for the target
vtkImagingHybrid_LIB_DEPENDS:STATIC=general;vtkIOImage;general;vtkImagingCore;

//Dependencies for the target
vtkImagingMorphologicalCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingMorphological;

//Dependencies for the target
vtkImagingMorphologicalPythonD_LIB_DEPENDS:STATIC=general;vtkImagingMorphological;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkImagingGeneralPythonD;

//Dependencies for the target
vtkImagingMorphologicalPython_LIB_DEPENDS:STATIC=general;vtkImagingMorphologicalPythonD;

//Dependencies for the target
vtkImagingMorphological_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkImagingGeneral;

//Dependencies for the target
vtkImagingSourcesCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkImagingSources;

//Dependencies for the target
vtkImagingSourcesPythonD_LIB_DEPENDS:STATIC=general;vtkImagingSources;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;

//Dependencies for the target
vtkImagingSourcesPython_LIB_DEPENDS:STATIC=general;vtkImagingSourcesPythonD;

//Dependencies for the target
vtkImagingSources_LIB_DEPENDS:STATIC=general;vtkImagingCore;

//Dependencies for the target
vtkInfovisCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInfovisCore;

//Dependencies for the target
vtkInfovisCorePythonD_LIB_DEPENDS:STATIC=general;vtkInfovisCore;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonSystemPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeneralPythonD;

//Dependencies for the target
vtkInfovisCorePython_LIB_DEPENDS:STATIC=general;vtkInfovisCorePythonD;

//Dependencies for the target
vtkInfovisCore_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;general;vtkCommonSystem;general;vtkFiltersExtraction;general;vtkFiltersGeneral;

//Dependencies for the target
vtkInfovisLayoutCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInfovisLayout;

//Dependencies for the target
vtkInfovisLayoutPythonD_LIB_DEPENDS:STATIC=general;vtkInfovisLayout;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkFiltersModelingPythonD;general;vtkImagingHybridPythonD;general;vtkInfovisCorePythonD;

//Dependencies for the target
vtkInfovisLayoutPython_LIB_DEPENDS:STATIC=general;vtkInfovisLayoutPythonD;

//Dependencies for the target
vtkInfovisLayout_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkFiltersModeling;general;vtkImagingHybrid;general;vtkInfovisCore;

//Dependencies for the target
vtkInteractionImageCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionImage;

//Dependencies for the target
vtkInteractionImagePythonD_LIB_DEPENDS:STATIC=general;vtkInteractionImage;general;vtkWrappingPythonCore;general;vtkImagingColorPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkInteractionImagePython_LIB_DEPENDS:STATIC=general;vtkInteractionImagePythonD;

//Dependencies for the target
vtkInteractionImage_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkRenderingCore;general;vtkRenderingFreeType;

//Dependencies for the target
vtkInteractionStyleCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionStyle;

//Dependencies for the target
vtkInteractionStylePythonD_LIB_DEPENDS:STATIC=general;vtkInteractionStyle;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkInteractionStylePython_LIB_DEPENDS:STATIC=general;vtkInteractionStylePythonD;

//Dependencies for the target
vtkInteractionStyle_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkFiltersSources;general;vtkFiltersExtraction;

//Dependencies for the target
vtkInteractionWidgetsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkInteractionWidgets;

//Dependencies for the target
vtkInteractionWidgetsPythonD_LIB_DEPENDS:STATIC=general;vtkInteractionWidgets;general;vtkWrappingPythonCore;general;vtkFiltersHybridPythonD;general;vtkFiltersModelingPythonD;general;vtkImagingGeneralPythonD;general;vtkImagingHybridPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkInteractionWidgetsPython_LIB_DEPENDS:STATIC=general;vtkInteractionWidgetsPythonD;

//Dependencies for the target
vtkInteractionWidgets_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkFiltersModeling;general;vtkImagingGeneral;general;vtkImagingHybrid;general;vtkInteractionStyle;general;vtkRenderingAnnotation;general;vtkRenderingFreeType;general;vtkRenderingVolume;

//Dependencies for the target
vtkNetCDF_LIB_DEPENDS:STATIC=general;vtkhdf5_hl;general;vtkhdf5;

//Dependencies for the target
vtkNetCDF_cxx_LIB_DEPENDS:STATIC=general;vtkNetCDF;

//Dependencies for the target
vtkPVAnimationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVAnimation;

//Dependencies for the target
vtkPVAnimationPythonD_LIB_DEPENDS:STATIC=general;vtkPVAnimation;general;vtkWrappingPythonCore;general;vtkIOMoviePythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerDefaultPythonD;

//Dependencies for the target
vtkPVAnimationPython_LIB_DEPENDS:STATIC=general;vtkPVAnimationPythonD;

//Dependencies for the target
vtkPVAnimation_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtksys;general;vtkIOMovie;general;vtkPVServerManagerDefault;

//Dependencies for the target
vtkPVCatalystCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalyst;

//Dependencies for the target
vtkPVCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;general;vtkWrappingPythonCore;general;vtkPVServerManagerApplicationPythonD;

//Dependencies for the target
vtkPVCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystPythonD;

//Dependencies for the target
vtkPVCatalystTestDriverCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCatalystTestDriver;

//Dependencies for the target
vtkPVCatalystTestDriverPythonD_LIB_DEPENDS:STATIC=general;vtkPVCatalystTestDriver;general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;

//Dependencies for the target
vtkPVCatalystTestDriverPython_LIB_DEPENDS:STATIC=general;vtkPVCatalystTestDriverPythonD;

//Dependencies for the target
vtkPVCatalystTestDriver_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;

//Dependencies for the target
vtkPVCatalyst_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtksys;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkPVClientServerCoreCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreCore;

//Dependencies for the target
vtkPVClientServerCoreCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersProgrammablePythonD;general;vtkPVCommonPythonD;general;vtkPVCommonPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkParallelMPIPythonD;general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPVClientServerCoreCorePython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCorePythonD;

//Dependencies for the target
vtkPVClientServerCoreCore_LIB_DEPENDS:STATIC=general;vtkFiltersExtraction;general;vtkFiltersParallel;general;vtkFiltersProgrammable;general;vtkPVCommon;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelMPI;general;vtkPythonInterpreter;general;vtksys;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkPVClientServerCoreDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreDefault;

//Dependencies for the target
vtkPVClientServerCoreDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefault;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVVTKExtensionsDefaultPythonD;

//Dependencies for the target
vtkPVClientServerCoreDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreDefaultPythonD;

//Dependencies for the target
vtkPVClientServerCoreDefault_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVVTKExtensionsDefault;general;vtksys;general;mpr;

//Dependencies for the target
vtkPVClientServerCoreRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVClientServerCoreRendering;

//Dependencies for the target
vtkPVClientServerCoreRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkWrappingPythonCore;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkPVClientServerCoreCorePythonD;general;vtkPVVTKExtensionsDefaultPythonD;general;vtkPVVTKExtensionsRenderingPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingVolumeAMRPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkViewsContext2DPythonD;general;vtkViewsCorePythonD;general;vtkWebGLExporterPythonD;

//Dependencies for the target
vtkPVClientServerCoreRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRenderingPythonD;

//Dependencies for the target
vtkPVClientServerCoreRendering_LIB_DEPENDS:STATIC=general;vtkDomainsChemistry;general;vtkFiltersAMR;general;vtkPVClientServerCoreCore;general;vtkPVVTKExtensionsDefault;general;vtkPVVTKExtensionsRendering;general;vtkRenderingLabel;general;vtkRenderingVolumeAMR;general;vtkRenderingVolumeOpenGL;general;vtkViewsContext2D;general;vtkViewsCore;general;vtkWebGLExporter;general;vtksys;general;vtkzlib;

//Dependencies for the target
vtkPVCommonCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVCommon;

//Dependencies for the target
vtkPVCommonPythonD_LIB_DEPENDS:STATIC=general;vtkPVCommon;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOXMLParserPythonD;

//Dependencies for the target
vtkPVCommonPython_LIB_DEPENDS:STATIC=general;vtkPVCommonPythonD;

//Dependencies for the target
vtkPVCommon_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkCommonCore;general;vtkIOXMLParser;general;vtksys;

//Dependencies for the target
vtkPVPythonCatalystPythonD_LIB_DEPENDS:STATIC=general;vtkPVPythonCatalyst;general;vtkWrappingPythonCore;general;vtkPVCatalystPythonD;general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPVPythonCatalystPython_LIB_DEPENDS:STATIC=general;vtkPVPythonCatalystPythonD;

//Dependencies for the target
vtkPVPythonCatalyst_LIB_DEPENDS:STATIC=general;vtkPVCatalyst;general;vtkPythonInterpreter;general;vtkUtilitiesPythonInitializer;

//Dependencies for the target
vtkPVServerImplementationCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationCore;

//Dependencies for the target
vtkPVServerImplementationCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCore;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreCorePythonD;

//Dependencies for the target
vtkPVServerImplementationCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationCorePythonD;

//Dependencies for the target
vtkPVServerImplementationCore_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreCore;general;protobuf;general;vtksys;

//Dependencies for the target
vtkPVServerImplementationRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerImplementationRendering;

//Dependencies for the target
vtkPVServerImplementationRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRendering;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreRenderingPythonD;general;vtkPVServerImplementationCorePythonD;

//Dependencies for the target
vtkPVServerImplementationRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRenderingPythonD;

//Dependencies for the target
vtkPVServerImplementationRendering_LIB_DEPENDS:STATIC=general;vtkPVClientServerCoreRendering;general;vtkPVServerImplementationCore;

//Dependencies for the target
vtkPVServerManagerApplicationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerApplication;

//Dependencies for the target
vtkPVServerManagerApplicationPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplication;general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonExecutionModelPythonD;general;vtkDomainsChemistryPythonD;general;vtkFiltersAMRPythonD;general;vtkFiltersCorePythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersFlowPathsPythonD;general;vtkFiltersGeneralPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersHybridPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersModelingPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelFlowPathsPythonD;general;vtkFiltersParallelImagingPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkFiltersProgrammablePythonD;general;vtkFiltersPythonPythonD;general;vtkFiltersSourcesPythonD;general;vtkFiltersStatisticsPythonD;general;vtkFiltersTexturePythonD;general;vtkFiltersVerdictPythonD;general;vtkIOAMRPythonD;general;vtkIOEnSightPythonD;general;vtkIOExodusPythonD;general;vtkIOExportPythonD;general;vtkIOGeometryPythonD;general;vtkIOGeometryPythonD;general;vtkIOImagePythonD;general;vtkIOImagePythonD;general;vtkIOImportPythonD;general;vtkIOInfovisPythonD;general;vtkIOLegacyPythonD;general;vtkIOMPIImagePythonD;general;vtkIOMoviePythonD;general;vtkIONetCDFPythonD;general;vtkIOPLYPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelLSDynaPythonD;general;vtkIOParallelNetCDFPythonD;general;vtkIOVPICPythonD;general;vtkIOXMLPythonD;general;vtkIOXMLPythonD;general;vtkIOXdmf2PythonD;general;vtkImagingCorePythonD;general;vtkImagingFourierPythonD;general;vtkImagingHybridPythonD;general;vtkImagingMorphologicalPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionImagePythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVAnimationPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerDefaultPythonD;general;vtkParallelMPIPythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingLODPythonD;general;vtkRenderingLabelPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD;general;vtkRenderingVolumePythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD;general;vtkViewsContext2DPythonD;

//Dependencies for the target
vtkPVServerManagerApplicationPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerApplicationPythonD;

//Dependencies for the target
vtkPVServerManagerApplication_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtksys;general;vtkCommonCoreCS;general;vtkCommonMathCS;general;vtkCommonMiscCS;general;vtkCommonSystemCS;general;vtkCommonTransformsCS;general;vtkCommonDataModelCS;general;vtkCommonExecutionModelCS;general;vtkFiltersCoreCS;general;vtkCommonComputationalGeometryCS;general;vtkFiltersGeneralCS;general;vtkImagingCoreCS;general;vtkImagingFourierCS;general;vtkFiltersStatisticsCS;general;vtkFiltersExtractionCS;general;vtkFiltersSourcesCS;general;vtkFiltersGeometryCS;general;vtkRenderingCoreCS;general;vtkInteractionStyleCS;general;vtkIOCoreCS;general;vtkIOImageCS;general;vtkImagingHybridCS;general;vtkRenderingOpenGLCS;general;vtkFiltersModelingCS;general;vtkIOLegacyCS;general;vtkParallelCoreCS;general;vtkFiltersParallelCS;general;vtkFiltersProgrammableCS;general;vtkPythonInterpreterCS;general;vtkIOXMLParserCS;general;vtkPVCommonCS;general;vtkPVVTKExtensionsCoreCS;general;vtkParallelMPICS;general;vtkPVClientServerCoreCoreCS;general;vtkPVServerImplementationCoreCS;general;vtkPVServerManagerCoreCS;general;vtkIOMovieCS;general;vtkFiltersAMRCS;general;vtkIOGeometryCS;general;vtkIOXMLCS;general;vtkDomainsChemistryCS;general;vtkFiltersParallelStatisticsCS;general;vtkIOEnSightCS;general;vtkIOImportCS;general;vtkInfovisCoreCS;general;vtkIOInfovisCS;general;vtkIOMPIImageCS;general;vtkIONetCDFCS;general;vtkIOParallelCS;general;vtkIOExodusCS;general;vtkIOParallelExodusCS;general;vtkIOParallelXMLCS;general;vtkImagingSourcesCS;general;vtkFiltersHybridCS;general;vtkImagingGeneralCS;general;vtkImagingColorCS;general;vtkRenderingFreeTypeCS;general;vtkRenderingAnnotationCS;general;vtkRenderingVolumeCS;general;vtkInteractionWidgetsCS;general;vtkCommonColorCS;general;vtkRenderingContext2DCS;general;vtkChartsCoreCS;general;vtkFiltersGenericCS;general;vtkFiltersHyperTreeCS;general;vtkFiltersParallelMPICS;general;vtkRenderingContextOpenGLCS;general;vtkRenderingGL2PSCS;general;vtkRenderingLabelCS;general;vtkIOExportCS;general;vtkRenderingFreeTypeOpenGLCS;general;vtkRenderingLICCS;general;vtkRenderingParallelCS;general;vtkRenderingParallelLICCS;general;vtkPVVTKExtensionsRenderingCS;general;vtkPVVTKExtensionsDefaultCS;general;vtkRenderingVolumeAMRCS;general;vtkRenderingVolumeOpenGLCS;general;vtkViewsCoreCS;general;vtkViewsContext2DCS;general;vtkWebGLExporterCS;general;vtkPVClientServerCoreRenderingCS;general;vtkPVClientServerCoreDefaultCS;general;vtkPVServerImplementationRenderingCS;general;vtkPVServerManagerRenderingCS;general;vtkTestingRenderingCS;general;vtkPVServerManagerDefaultCS;general;vtkPVAnimationCS;general;vtkFiltersFlowPathsCS;general;vtkFiltersParallelFlowPathsCS;general;vtkFiltersImagingCS;general;vtkFiltersParallelImagingCS;general;vtkFiltersPythonCS;general;vtkFiltersTextureCS;general;vtkFiltersVerdictCS;general;vtkIOAMRCS;general;vtkIOPLYCS;general;vtkIOLSDynaCS;general;vtkIOParallelLSDynaCS;general;vtkIOParallelNetCDFCS;general;vtkIOVPICCS;general;vtkIOXdmf2CS;general;vtkImagingMorphologicalCS;general;vtkInteractionImageCS;general;vtkRenderingLODCS;general;vtkFiltersParallelGeometryCS;general;vtkIOSQLCS;general;vtkInfovisLayoutCS;general;vtkViewsInfovisCS;general;vtkGeovisCoreCS;general;vtkViewsGeovisCS;general;vtkIOMPIParallelCS;general;vtkParallelMPI4PyCS;general;vtkRenderingQtCS;general;vtkPVServerManagerCore;

//Dependencies for the target
vtkPVServerManagerCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerCore;

//Dependencies for the target
vtkPVServerManagerCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkPVServerImplementationCorePythonD;

//Dependencies for the target
vtkPVServerManagerCorePython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerCorePythonD;

//Dependencies for the target
vtkPVServerManagerCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkPVServerImplementationCore;general;vtksys;general;vtkjsoncpp;general;vtkpugixml;

//Dependencies for the target
vtkPVServerManagerDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerDefault;

//Dependencies for the target
vtkPVServerManagerDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefault;general;vtkWrappingPythonCore;general;vtkPVClientServerCoreDefaultPythonD;general;vtkPVServerManagerRenderingPythonD;general;vtkRenderingVolumeOpenGLPythonD;general;vtkTestingRenderingPythonD;

//Dependencies for the target
vtkPVServerManagerDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerDefaultPythonD;

//Dependencies for the target
vtkPVServerManagerDefault_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRendering;general;vtksys;general;vtkRenderingVolumeOpenGL;general;vtkTestingRendering;general;vtkPVClientServerCoreDefault;

//Dependencies for the target
vtkPVServerManagerRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVServerManagerRendering;

//Dependencies for the target
vtkPVServerManagerRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRendering;general;vtkWrappingPythonCore;general;vtkCommonColorPythonD;general;vtkPVServerImplementationRenderingPythonD;general;vtkPVServerManagerCorePythonD;general;vtkPVServerManagerCorePythonD;

//Dependencies for the target
vtkPVServerManagerRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVServerManagerRenderingPythonD;

//Dependencies for the target
vtkPVServerManagerRendering_LIB_DEPENDS:STATIC=general;vtkPVServerImplementationRendering;general;vtkPVServerManagerCore;general;vtkPVServerManagerCore;general;vtksys;general;vtkCommonColor;

//Dependencies for the target
vtkPVVTKExtensionsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsCore;

//Dependencies for the target
vtkPVVTKExtensionsCorePythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCore;general;vtkWrappingPythonCore;general;vtkFiltersCorePythonD;general;vtkPVCommonPythonD;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkPVVTKExtensionsCorePython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsCorePythonD;

//Dependencies for the target
vtkPVVTKExtensionsCore_LIB_DEPENDS:STATIC=general;vtkFiltersCore;general;vtkPVCommon;general;vtkParallelCore;general;vtksys;

//Dependencies for the target
vtkPVVTKExtensionsDefaultCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsDefault;

//Dependencies for the target
vtkPVVTKExtensionsDefaultPythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefault;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkFiltersParallelStatisticsPythonD;general;vtkIOEnSightPythonD;general;vtkIOImportPythonD;general;vtkIOInfovisPythonD;general;vtkIOMPIImagePythonD;general;vtkIOParallelPythonD;general;vtkIOParallelExodusPythonD;general;vtkIOParallelXMLPythonD;general;vtkImagingFourierPythonD;general;vtkImagingSourcesPythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkPVVTKExtensionsRenderingPythonD;

//Dependencies for the target
vtkPVVTKExtensionsDefaultPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsDefaultPythonD;

//Dependencies for the target
vtkPVVTKExtensionsDefault_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkFiltersParallelStatistics;general;vtkIOEnSight;general;vtkIOImport;general;vtkIOMPIImage;general;vtkIOParallel;general;vtkIOParallelExodus;general;vtkIOParallelXML;general;vtkImagingFourier;general;vtkImagingSources;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkPVVTKExtensionsRendering;general;vtkIOInfovis;general;vtkNetCDF;general;vtkNetCDF_cxx;general;vtksys;

//Dependencies for the target
vtkPVVTKExtensionsRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPVVTKExtensionsRendering;

//Dependencies for the target
vtkPVVTKExtensionsRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRendering;general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonColorPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGenericPythonD;general;vtkFiltersHyperTreePythonD;general;vtkFiltersParallelPythonD;general;vtkFiltersParallelMPIPythonD;general;vtkIOExportPythonD;general;vtkIOXMLPythonD;general;vtkInteractionStylePythonD;general;vtkInteractionWidgetsPythonD;general;vtkPVVTKExtensionsCorePythonD;general;vtkRenderingAnnotationPythonD;general;vtkRenderingFreeTypeOpenGLPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingParallelPythonD;general;vtkRenderingParallelLICPythonD;

//Dependencies for the target
vtkPVVTKExtensionsRenderingPython_LIB_DEPENDS:STATIC=general;vtkPVVTKExtensionsRenderingPythonD;

//Dependencies for the target
vtkPVVTKExtensionsRendering_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkFiltersExtraction;general;vtkFiltersGeneric;general;vtkFiltersHyperTree;general;vtkFiltersParallel;general;vtkFiltersParallelMPI;general;vtkGUISupportQt;general;vtkIOExport;general;vtkIOXML;general;vtkInteractionStyle;general;vtkInteractionWidgets;general;vtkPVVTKExtensionsCore;general;vtkRenderingAnnotation;general;vtkRenderingFreeTypeOpenGL;general;vtkRenderingLIC;general;vtkRenderingOpenGL;general;vtkRenderingParallel;general;vtkRenderingParallelLIC;general;IceTCore;general;IceTMPI;general;IceTGL;general;vtkCommonColor;general;vtkzlib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkParaViewDocumentation_LIB_DEPENDS:STATIC=optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtNetwork4.lib;debug;C:/Qt/4.8.6/lib/QtNetworkd4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkParallelCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelCore;

//Dependencies for the target
vtkParallelCorePythonD_LIB_DEPENDS:STATIC=general;vtkParallelCore;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;general;vtkIOLegacyPythonD;

//Dependencies for the target
vtkParallelCorePython_LIB_DEPENDS:STATIC=general;vtkParallelCorePythonD;

//Dependencies for the target
vtkParallelCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkIOLegacy;general;vtksys;

//Dependencies for the target
vtkParallelMPI4PyCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI4Py;

//Dependencies for the target
vtkParallelMPI4PyPythonD_LIB_DEPENDS:STATIC=general;vtkParallelMPI4Py;general;vtkWrappingPythonCore;general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkParallelMPI4PyPython_LIB_DEPENDS:STATIC=general;vtkParallelMPI4PyPythonD;

//Dependencies for the target
vtkParallelMPI4Py_LIB_DEPENDS:STATIC=general;vtkParallelMPI;general;C:/Python27/libs/python27.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkParallelMPICS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkParallelMPI;

//Dependencies for the target
vtkParallelMPIPythonD_LIB_DEPENDS:STATIC=general;vtkParallelMPI;general;vtkWrappingPythonCore;general;vtkParallelCorePythonD;

//Dependencies for the target
vtkParallelMPIPython_LIB_DEPENDS:STATIC=general;vtkParallelMPIPythonD;

//Dependencies for the target
vtkParallelMPI_LIB_DEPENDS:STATIC=general;vtkParallelCore;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkPointSpriteGraphicsCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPointSpriteGraphics;

//Dependencies for the target
vtkPointSpriteGraphics_LIB_DEPENDS:STATIC=general;vtkFiltersCore;

//Dependencies for the target
vtkPointSpriteRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPointSpriteRendering;

//Dependencies for the target
vtkPointSpriteRendering_LIB_DEPENDS:STATIC=general;vtkFiltersHybrid;general;vtkImagingCore;general;vtkInteractionStyle;general;vtkRenderingFreeTypeOpenGL;general;vtkRenderingOpenGL;

//Dependencies for the target
vtkPythonInterpreterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkPythonInterpreter;

//Dependencies for the target
vtkPythonInterpreterPythonD_LIB_DEPENDS:STATIC=general;vtkPythonInterpreter;general;vtkWrappingPythonCore;general;vtkCommonCorePythonD;

//Dependencies for the target
vtkPythonInterpreterPython_LIB_DEPENDS:STATIC=general;vtkPythonInterpreterPythonD;

//Dependencies for the target
vtkPythonInterpreter_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;C:/Python27/libs/python27.lib;general;vtksys;

//Dependencies for the target
vtkQvis_LIB_DEPENDS:STATIC=general;vtkCommonCore;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkRenderingAnnotationCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingAnnotation;

//Dependencies for the target
vtkRenderingAnnotationPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotation;general;vtkWrappingPythonCore;general;vtkFiltersSourcesPythonD;general;vtkImagingColorPythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingAnnotationPython_LIB_DEPENDS:STATIC=general;vtkRenderingAnnotationPythonD;

//Dependencies for the target
vtkRenderingAnnotation_LIB_DEPENDS:STATIC=general;vtkImagingColor;general;vtkRenderingFreeType;general;vtkFiltersSources;

//Dependencies for the target
vtkRenderingContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContext2D;

//Dependencies for the target
vtkRenderingContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkWrappingPythonCore;general;vtkCommonDataModelPythonD;general;vtkCommonMathPythonD;general;vtkCommonTransformsPythonD;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingContext2DPython_LIB_DEPENDS:STATIC=general;vtkRenderingContext2DPythonD;

//Dependencies for the target
vtkRenderingContext2D_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkCommonDataModel;general;vtkCommonMath;general;vtkCommonTransforms;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingContextOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingContextOpenGL;

//Dependencies for the target
vtkRenderingContextOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL;general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingContextOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGLPythonD;

//Dependencies for the target
vtkRenderingContextOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkRenderingOpenGL;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingCorePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkWrappingPythonCore;general;vtkCommonExecutionModelPythonD;general;vtkCommonTransformsPythonD;general;vtkFiltersExtractionPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersSourcesPythonD;

//Dependencies for the target
vtkRenderingCorePython_LIB_DEPENDS:STATIC=general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingCore_LIB_DEPENDS:STATIC=general;vtkCommonExecutionModel;general;vtkCommonTransforms;general;vtkFiltersSources;general;vtkFiltersGeometry;general;vtkFiltersExtraction;general;vtksys;

//Dependencies for the target
vtkRenderingFreeTypeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeType;

//Dependencies for the target
vtkRenderingFreeTypeOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingFreeTypeOpenGL;

//Dependencies for the target
vtkRenderingFreeTypeOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypeOpenGL;general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingFreeTypeOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypeOpenGLPythonD;

//Dependencies for the target
vtkRenderingFreeTypeOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkRenderingFreeType;general;vtkRenderingOpenGL;

//Dependencies for the target
vtkRenderingFreeTypePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingFreeType;general;vtkWrappingPythonCore;general;vtkRenderingCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingFreeTypePython_LIB_DEPENDS:STATIC=general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingFreeType_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkRenderingCore;general;vtkfreetype;general;vtkftgl;

//Dependencies for the target
vtkRenderingGL2PSCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingGL2PS;

//Dependencies for the target
vtkRenderingGL2PSPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PS;general;vtkWrappingPythonCore;general;vtkRenderingContextOpenGLPythonD;general;vtkRenderingFreeTypePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingGL2PSPython_LIB_DEPENDS:STATIC=general;vtkRenderingGL2PSPythonD;

//Dependencies for the target
vtkRenderingGL2PS_LIB_DEPENDS:STATIC=general;vtkRenderingContextOpenGL;general;vtkRenderingOpenGL;general;vtkRenderingFreeType;general;vtkgl2ps;

//Dependencies for the target
vtkRenderingLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLIC;

//Dependencies for the target
vtkRenderingLICPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLIC;general;vtkWrappingPythonCore;general;vtkIOLegacyPythonD;general;vtkIOXMLPythonD;general;vtkImagingSourcesPythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingLICPythonD;

//Dependencies for the target
vtkRenderingLIC_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkIOXML;general;vtkImagingSources;general;vtkRenderingOpenGL;general;vtksys;

//Dependencies for the target
vtkRenderingLODCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLOD;

//Dependencies for the target
vtkRenderingLODPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLOD;general;vtkWrappingPythonCore;general;vtkFiltersModelingPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingLODPython_LIB_DEPENDS:STATIC=general;vtkRenderingLODPythonD;

//Dependencies for the target
vtkRenderingLOD_LIB_DEPENDS:STATIC=general;vtkFiltersModeling;general;vtkRenderingCore;

//Dependencies for the target
vtkRenderingLabelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingLabel;

//Dependencies for the target
vtkRenderingLabelPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingLabel;general;vtkWrappingPythonCore;general;vtkFiltersExtractionPythonD;general;vtkRenderingFreeTypePythonD;

//Dependencies for the target
vtkRenderingLabelPython_LIB_DEPENDS:STATIC=general;vtkRenderingLabelPythonD;

//Dependencies for the target
vtkRenderingLabel_LIB_DEPENDS:STATIC=general;vtkRenderingFreeType;general;vtkFiltersExtraction;

//Dependencies for the target
vtkRenderingOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingOpenGL;

//Dependencies for the target
vtkRenderingOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;general;vtkWrappingPythonCore;general;vtkImagingHybridPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingCore;general;vtkImagingHybrid;general;vtksys;general;glu32;general;opengl32;general;C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/d3d9.lib;general;wbemuuid;

//Dependencies for the target
vtkRenderingParallelCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallel;

//Dependencies for the target
vtkRenderingParallelLICCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingParallelLIC;

//Dependencies for the target
vtkRenderingParallelLICPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLIC;general;vtkWrappingPythonCore;general;vtkIOLegacyPythonD;general;vtkParallelMPIPythonD;general;vtkRenderingLICPythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingParallelLICPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelLICPythonD;

//Dependencies for the target
vtkRenderingParallelLIC_LIB_DEPENDS:STATIC=general;vtkIOLegacy;general;vtkParallelMPI;general;vtkRenderingLIC;general;vtkRenderingOpenGL;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkRenderingParallelPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingParallel;general;vtkWrappingPythonCore;general;vtkFiltersParallelPythonD;general;vtkIOImagePythonD;general;vtkParallelCorePythonD;general;vtkRenderingOpenGLPythonD;

//Dependencies for the target
vtkRenderingParallelPython_LIB_DEPENDS:STATIC=general;vtkRenderingParallelPythonD;

//Dependencies for the target
vtkRenderingParallel_LIB_DEPENDS:STATIC=general;vtkFiltersParallel;general;vtkParallelCore;general;vtkRenderingOpenGL;general;vtkIOImage;

//Dependencies for the target
vtkRenderingQtCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingQt;

//Dependencies for the target
vtkRenderingQtPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingQt;general;vtkWrappingPythonCore;general;vtkFiltersSourcesPythonD;general;vtkFiltersTexturePythonD;general;vtkRenderingLabelPythonD;

//Dependencies for the target
vtkRenderingQtPython_LIB_DEPENDS:STATIC=general;vtkRenderingQtPythonD;

//Dependencies for the target
vtkRenderingQt_LIB_DEPENDS:STATIC=general;vtkRenderingLabel;general;vtkFiltersTexture;general;vtkFiltersSources;general;vtkGUISupportQt;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkRenderingVolumeAMRCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeAMR;

//Dependencies for the target
vtkRenderingVolumeAMRPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMR;general;vtkWrappingPythonCore;general;vtkFiltersAMRPythonD;general;vtkParallelCorePythonD;general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkRenderingVolumeAMRPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeAMRPythonD;

//Dependencies for the target
vtkRenderingVolumeAMR_LIB_DEPENDS:STATIC=general;vtkFiltersAMR;general;vtkParallelCore;general;vtkRenderingVolume;

//Dependencies for the target
vtkRenderingVolumeCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolume;

//Dependencies for the target
vtkRenderingVolumeOpenGLCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkRenderingVolumeOpenGL;

//Dependencies for the target
vtkRenderingVolumeOpenGLPythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGL;general;vtkWrappingPythonCore;general;vtkFiltersGeneralPythonD;general;vtkFiltersSourcesPythonD;general;vtkRenderingOpenGLPythonD;general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkRenderingVolumeOpenGLPython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumeOpenGLPythonD;

//Dependencies for the target
vtkRenderingVolumeOpenGL_LIB_DEPENDS:STATIC=general;vtkRenderingOpenGL;general;vtkRenderingVolume;general;vtksys;general;vtkFiltersGeneral;general;vtkFiltersSources;

//Dependencies for the target
vtkRenderingVolumePythonD_LIB_DEPENDS:STATIC=general;vtkRenderingVolume;general;vtkWrappingPythonCore;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkRenderingVolumePython_LIB_DEPENDS:STATIC=general;vtkRenderingVolumePythonD;

//Dependencies for the target
vtkRenderingVolume_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingCore;

//Dependencies for the target
vtkSciberQuestCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkSciberQuest;

//Dependencies for the target
vtkSciberQuest_LIB_DEPENDS:STATIC=general;vtkFiltersFlowPaths;general;vtkIOLegacy;general;vtkPVCommon;general;vtkPVVTKExtensionsCore;general;vtkParallelCore;general;vtksys;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;general;C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib;

//Dependencies for the target
vtkTestingGenericBridge_LIB_DEPENDS:STATIC=general;vtkCommonDataModel;

//Dependencies for the target
vtkTestingIOSQL_LIB_DEPENDS:STATIC=general;vtkIOSQL;

//Dependencies for the target
vtkTestingRenderingCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkTestingRendering;

//Dependencies for the target
vtkTestingRenderingPythonD_LIB_DEPENDS:STATIC=general;vtkTestingRendering;general;vtkWrappingPythonCore;general;vtkIOImagePythonD;general;vtkImagingCorePythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkTestingRenderingPython_LIB_DEPENDS:STATIC=general;vtkTestingRenderingPythonD;

//Dependencies for the target
vtkTestingRendering_LIB_DEPENDS:STATIC=general;vtkImagingCore;general;vtkRenderingCore;general;vtksys;general;vtkIOImage;

//Dependencies for the target
vtkUtilitiesPythonInitializer_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;vtkWrappingPythonCore;general;vtkWrappingPythonCore;general;vtkCommonCore;

//Dependencies for the target
vtkViewsContext2DCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsContext2D;

//Dependencies for the target
vtkViewsContext2DPythonD_LIB_DEPENDS:STATIC=general;vtkViewsContext2D;general;vtkWrappingPythonCore;general;vtkRenderingContext2DPythonD;general;vtkViewsCorePythonD;

//Dependencies for the target
vtkViewsContext2DPython_LIB_DEPENDS:STATIC=general;vtkViewsContext2DPythonD;

//Dependencies for the target
vtkViewsContext2D_LIB_DEPENDS:STATIC=general;vtkRenderingContext2D;general;vtkViewsCore;

//Dependencies for the target
vtkViewsCoreCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsCore;

//Dependencies for the target
vtkViewsCorePythonD_LIB_DEPENDS:STATIC=general;vtkViewsCore;general;vtkWrappingPythonCore;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkViewsCorePython_LIB_DEPENDS:STATIC=general;vtkViewsCorePythonD;

//Dependencies for the target
vtkViewsCore_LIB_DEPENDS:STATIC=general;vtkInteractionWidgets;general;vtkRenderingCore;

//Dependencies for the target
vtkViewsGeovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsGeovis;

//Dependencies for the target
vtkViewsGeovisPythonD_LIB_DEPENDS:STATIC=general;vtkViewsGeovis;general;vtkWrappingPythonCore;general;vtkGeovisCorePythonD;general;vtkViewsInfovisPythonD;

//Dependencies for the target
vtkViewsGeovisPython_LIB_DEPENDS:STATIC=general;vtkViewsGeovisPythonD;

//Dependencies for the target
vtkViewsGeovis_LIB_DEPENDS:STATIC=general;vtkGeovisCore;general;vtkViewsInfovis;

//Dependencies for the target
vtkViewsInfovisCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkViewsInfovis;

//Dependencies for the target
vtkViewsInfovisPythonD_LIB_DEPENDS:STATIC=general;vtkViewsInfovis;general;vtkWrappingPythonCore;general;vtkChartsCorePythonD;general;vtkCommonColorPythonD;general;vtkFiltersGeometryPythonD;general;vtkFiltersImagingPythonD;general;vtkFiltersModelingPythonD;general;vtkInfovisLayoutPythonD;general;vtkInteractionStylePythonD;general;vtkRenderingContext2DPythonD;general;vtkRenderingLabelPythonD;general;vtkViewsCorePythonD;

//Dependencies for the target
vtkViewsInfovisPython_LIB_DEPENDS:STATIC=general;vtkViewsInfovisPythonD;

//Dependencies for the target
vtkViewsInfovis_LIB_DEPENDS:STATIC=general;vtkChartsCore;general;vtkCommonColor;general;vtkFiltersImaging;general;vtkFiltersModeling;general;vtkInfovisLayout;general;vtkInteractionStyle;general;vtkRenderingContext2D;general;vtkRenderingLabel;general;vtkViewsCore;general;vtkFiltersGeometry;

//Dependencies for the target
vtkViewsQt_LIB_DEPENDS:STATIC=general;vtkGUISupportQt;general;vtkViewsInfovis;optimized;C:/Qt/4.8.6/lib/QtGui4.lib;debug;C:/Qt/4.8.6/lib/QtGuid4.lib;optimized;C:/Qt/4.8.6/lib/QtNetwork4.lib;debug;C:/Qt/4.8.6/lib/QtNetworkd4.lib;optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib;

//Dependencies for the target
vtkWebGLExporterCS_LIB_DEPENDS:STATIC=general;vtkClientServer;general;vtkWebGLExporter;

//Dependencies for the target
vtkWebGLExporterPythonD_LIB_DEPENDS:STATIC=general;vtkWebGLExporter;general;vtkWrappingPythonCore;general;vtkFiltersGeometryPythonD;general;vtkIOExportPythonD;general;vtkInteractionWidgetsPythonD;general;vtkRenderingCorePythonD;

//Dependencies for the target
vtkWebGLExporterPython_LIB_DEPENDS:STATIC=general;vtkWebGLExporterPythonD;

//Dependencies for the target
vtkWebGLExporter_LIB_DEPENDS:STATIC=general;vtkIOExport;general;vtksys;general;vtkFiltersGeometry;general;vtkInteractionWidgets;general;vtkRenderingCore;

//Dependencies for the target
vtkWrappingPythonCore_LIB_DEPENDS:STATIC=general;vtkCommonCore;general;C:/Python27/libs/python27.lib;general;vtksys;

//Dependencies for target
vtkWrappingTools_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkalglib_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkexoIIc_LIB_DEPENDS:STATIC=general;vtkNetCDF;general;vtkNetCDF_cxx;

//Dependencies for target
vtkexpat_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkfreetype_LIB_DEPENDS:STATIC=general;vtkzlib;

//Dependencies for the target
vtkftgl_LIB_DEPENDS:STATIC=general;opengl32;general;vtkfreetype;

//Dependencies for the target
vtkgl2ps_LIB_DEPENDS:STATIC=general;glu32;general;opengl32;general;vtkzlib;general;vtkpng;

//Dependencies for the target
vtkhdf5_LIB_DEPENDS:STATIC=general;ws2_32;general;wsock32;general;vtkzlib;

//Dependencies for the target
vtkhdf5_hl_LIB_DEPENDS:STATIC=general;vtkhdf5;

//Dependencies for target
vtkjpeg_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkjsoncpp_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtklibxml2_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/libxml2/vtklibxml2

//Dependencies for the target
vtklibxml2_LIB_DEPENDS:STATIC=general;vtkzlib;

//Value Computed by CMake
vtklibxml2_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/libxml2/vtklibxml2

//Value Computed by CMake
vtkmetaio_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/Utilities/MetaIO/vtkmetaio

//Dependencies for the target
vtkmetaio_LIB_DEPENDS:STATIC=general;vtkzlib;general;comctl32;general;wsock32;

//Value Computed by CMake
vtkmetaio_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/Utilities/MetaIO/vtkmetaio

//Dependencies for target
vtkoggtheora_LIB_DEPENDS:STATIC=

//Dependencies for the target
vtkpng_LIB_DEPENDS:STATIC=general;vtkzlib;

//Dependencies for target
vtkproj4_LIB_DEPENDS:STATIC=

//Dependencies for target
vtkpugixml_LIB_DEPENDS:STATIC=

//Dependencies for target
vtksqlite_LIB_DEPENDS:STATIC=

//Value Computed by CMake
vtksys_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/Utilities/KWSys/vtksys

//Dependencies for the target
vtksys_LIB_DEPENDS:STATIC=general;ws2_32;general;Psapi;

//Value Computed by CMake
vtksys_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/Utilities/KWSys/vtksys

//Dependencies for the target
vtktiff_LIB_DEPENDS:STATIC=general;vtkzlib;general;vtkjpeg;

//Dependencies for the target
vtkxdmf2_LIB_DEPENDS:STATIC=general;vtklibxml2;general;vtkhdf5_hl;general;vtkhdf5;

//Dependencies for target
vtkzlib_LIB_DEPENDS:STATIC=

//Value Computed by CMake
xdmf2_BINARY_DIR:STATIC=E:/immersiveParaview/ParaView-build/VTK/ThirdParty/xdmf2/vtkxdmf2

//Value Computed by CMake
xdmf2_SOURCE_DIR:STATIC=E:/immersiveParaview/ParaView/VTK/ThirdParty/xdmf2/vtkxdmf2


########################
# INTERNAL cache entries
########################

ALGLIB_SHARED_LIB:INTERNAL=ON
//Host Arcitecture : Linux IRIXN32 IRIX64 AIX CYGWIN
ARCH_TO_BUILD:INTERNAL=Windows
//ADVANCED property for variable: BZRCOMMAND
BZRCOMMAND-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_ANSI_FOR_SCOPE:INTERNAL=TRUE
//Have include iostream
CMAKE_ANSI_STREAM_HEADERS:INTERNAL=1
//ADVANCED property for variable: CMAKE_BUILD_TOOL
CMAKE_BUILD_TOOL-ADVANCED:INTERNAL=1
//What is the target build tool cmake is generating for.
CMAKE_BUILD_TOOL:INTERNAL=E:/immersiveParaview/ninja/ninja.exe
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=e:/immersiveParaview/ParaView-build
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=2
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=8
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=12
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=c:/Program Files (x86)/CMake 2.8/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=c:/Program Files (x86)/CMake 2.8/bin/cpack.exe
//ADVANCED property for variable: CMAKE_CTEST_COMMAND
CMAKE_CTEST_COMMAND-ADVANCED:INTERNAL=1
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=c:/Program Files (x86)/CMake 2.8/bin/ctest.exe
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS
CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_CXX_STANDARD_LIBRARIES
CMAKE_CXX_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=c:/Program Files (x86)/CMake 2.8/bin/cmake-gui.exe
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Result of TRY_COMPILE
CMAKE_HAS_ANSI_STRING_STREAM:INTERNAL=TRUE
//Have includes pthread.h
CMAKE_HAVE_PTHREAD_H:INTERNAL=
//Start directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=E:/immersiveParaview/ParaView
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MAKE_PROGRAM
CMAKE_MAKE_PROGRAM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Does the compiler support ansi for scope.
CMAKE_NO_ANSI_FOR_SCOPE:INTERNAL=0
//ADVANCED property for variable: CMAKE_NO_ANSI_STREAM_HEADERS
CMAKE_NO_ANSI_STREAM_HEADERS-ADVANCED:INTERNAL=1
//Does the compiler support headers like iostream.
CMAKE_NO_ANSI_STREAM_HEADERS:INTERNAL=0
//Does the compiler support sstream
CMAKE_NO_ANSI_STRING_STREAM:INTERNAL=0
//Does the compiler support std::.
CMAKE_NO_STD_NAMESPACE:INTERNAL=0
//number of local generators
CMAKE_NUMBER_OF_LOCAL_GENERATORS:INTERNAL=377
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//Test Support for 64 bit file systems
CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=c:/Program Files (x86)/CMake 2.8/share/cmake-2.8
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(unsigned short)
CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=2
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
CMAKE_STD_NAMESPACE:INTERNAL=TRUE
//Suppress Warnings that are meant for the author of the CMakeLists.txt
// files.
CMAKE_SUPPRESS_DEVELOPER_WARNINGS:INTERNAL=FALSE
//ADVANCED property for variable: CMAKE_THREAD_LIBS
CMAKE_THREAD_LIBS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_USE_RELATIVE_PATHS
CMAKE_USE_RELATIVE_PATHS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Result of TEST_BIG_ENDIAN
CMAKE_WORDS_BIGENDIAN:INTERNAL=0
//Test COMPILER_HAS_DEPRECATED
COMPILER_HAS_DEPRECATED:INTERNAL=1
//Test COMPILER_HAS_DEPRECATED_ATTR
COMPILER_HAS_DEPRECATED_ATTR:INTERNAL=
//ADVANCED property for variable: COMPRESSIONCOMMAND
COMPRESSIONCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COVERAGE_COMMAND
COVERAGE_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: COVERAGE_EXTRA_FLAGS
COVERAGE_EXTRA_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_NSIS
CPACK_BINARY_NSIS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_WIX
CPACK_BINARY_WIX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_BINARY_ZIP
CPACK_BINARY_ZIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CPACK_SOURCE_ZIP
CPACK_SOURCE_ZIP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_COUNT
CTEST_SUBMIT_RETRY_COUNT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CTEST_SUBMIT_RETRY_DELAY
CTEST_SUBMIT_RETRY_DELAY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVSCOMMAND
CVSCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CVS_UPDATE_OPTIONS
CVS_UPDATE_OPTIONS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_BUILD_ERROR_REPORT_LIMIT
DART_BUILD_ERROR_REPORT_LIMIT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_BUILD_WARNING_REPORT_LIMIT
DART_BUILD_WARNING_REPORT_LIMIT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_ROOT
DART_ROOT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_TESTING_TIMEOUT
DART_TESTING_TIMEOUT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DART_VERBOSE_BUILD
DART_VERBOSE_BUILD-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DELIVER_CONTINUOUS_EMAIL
DELIVER_CONTINUOUS_EMAIL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DirectX_INCLUDE_DIR
DirectX_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: DirectX_LIBRARY
DirectX_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: EXECUTABLE_OUTPUT_PATH
EXECUTABLE_OUTPUT_PATH-ADVANCED:INTERNAL=1
EXECUTABLE_OUTPUT_PATH:INTERNAL=E:/immersiveParaview/ParaView-build/ThirdParty/protobuf/vtkprotobuf/bin
//ADVANCED property for variable: EXODUSII_DISABLE_COMPILER_WARNINGS
EXODUSII_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//Have include malloc.h
EX_HAVE_MALLOC_H:INTERNAL=1
//ADVANCED property for variable: Eigen_DIR
Eigen_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ExternalData_URL_TEMPLATES
ExternalData_URL_TEMPLATES-ADVANCED:INTERNAL=1
//Details about finding GLUT
FIND_PACKAGE_MESSAGE_DETAILS_GLUT:INTERNAL=[C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/glut32.lib][C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Include][v()]
//Details about finding Git
FIND_PACKAGE_MESSAGE_DETAILS_Git:INTERNAL=[C:/Program Files (x86)/Git/cmd/git.exe][v1.8.4.msysgit.0()]
//Details about finding MPI_C
FIND_PACKAGE_MESSAGE_DETAILS_MPI_C:INTERNAL=[C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib][C:/Program Files/Microsoft HPC Pack 2008 R2/Inc][v()]
//Details about finding MPI_CXX
FIND_PACKAGE_MESSAGE_DETAILS_MPI_CXX:INTERNAL=[C:/Program Files/Microsoft HPC Pack 2008 R2/lib/i386/msmpi.lib][C:/Program Files/Microsoft HPC Pack 2008 R2/Inc][v()]
//Details about finding OpenGL
FIND_PACKAGE_MESSAGE_DETAILS_OpenGL:INTERNAL=[opengl32][v()]
//Details about finding PythonInterp
FIND_PACKAGE_MESSAGE_DETAILS_PythonInterp:INTERNAL=[C:/Python27/python.exe][v2.7.7()]
//Details about finding PythonLibs
FIND_PACKAGE_MESSAGE_DETAILS_PythonLibs:INTERNAL=[C:/Python27/libs/python27.lib][C:/Python27/include][v()]
//Details about finding Qt4
FIND_PACKAGE_MESSAGE_DETAILS_Qt4:INTERNAL=[C:/Qt/4.8.6/bin/qmake.exe][C:/Qt/4.8.6/bin/moc.exe][C:/Qt/4.8.6/bin/rcc.exe][C:/Qt/4.8.6/bin/uic.exe][C:/Qt/4.8.6/include][C:/Qt/4.8.6/lib][optimized;C:/Qt/4.8.6/lib/QtCore4.lib;debug;C:/Qt/4.8.6/lib/QtCored4.lib][v4.8.6(4.7.0)]
//Details about finding Threads
FIND_PACKAGE_MESSAGE_DETAILS_Threads:INTERNAL=[TRUE][v()]
//ADVANCED property for variable: GITCOMMAND
GITCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GIT_EXECUTABLE
GIT_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GLUT_INCLUDE_DIR
GLUT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GLUT_glut_LIBRARY
GLUT_glut_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GUNZIPCOMMAND
GUNZIPCOMMAND-ADVANCED:INTERNAL=1
//Checking IF overflows normally converting floating-point to integer
// values
H5_FP_TO_INTEGER_OVERFLOW_WORKS:INTERNAL=1
//Result of TRY_COMPILE
H5_FP_TO_INTEGER_OVERFLOW_WORKS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_INTEGER_OVERFLOW_WORKS_RUN:INTERNAL=0
//Checking IF accurately roundup converting floating-point to unsigned
// long long values
H5_FP_TO_ULLONG_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_FP_TO_ULLONG_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_ULLONG_ACCURATE_RUN:INTERNAL=0
H5_FP_TO_ULLONG_RIGHT_MAXIMUM:INTERNAL=
//Result of TRY_COMPILE
H5_FP_TO_ULLONG_RIGHT_MAXIMUM_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_FP_TO_ULLONG_RIGHT_MAXIMUM_RUN:INTERNAL=0
//Have function alarm
H5_HAVE_ALARM:INTERNAL=
//Have symbol tzname
H5_HAVE_DECL_TZNAME:INTERNAL=1
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h;sys/timeb.h;sys/types.h;stdlib.h;memory.h;dlfcn.h
H5_HAVE_DLFCN_H:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h;sys/timeb.h;sys/types.h;stdlib.h;memory.h;features.h
H5_HAVE_FEATURES_H:INTERNAL=
//Have function fork
H5_HAVE_FORK:INTERNAL=
//Have function frexpf
H5_HAVE_FREXPF:INTERNAL=
//Have function frexpl
H5_HAVE_FREXPL:INTERNAL=
//Have function fseeko
H5_HAVE_FSEEKO:INTERNAL=
//Have function fstat64
H5_HAVE_FSTAT64:INTERNAL=
//Have function ftello
H5_HAVE_FTELLO:INTERNAL=
//Have function getpwuid
H5_HAVE_GETPWUID:INTERNAL=
//Have function getrusage
H5_HAVE_GETRUSAGE:INTERNAL=
//Have includes ;globus/common.h
H5_HAVE_GLOBUS_COMMON_H:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h;sys/timeb.h;sys/types.h;stdlib.h;memory.h;inttypes.h
H5_HAVE_INTTYPES_H:INTERNAL=
//Have function ioctl
H5_HAVE_IOCTL:INTERNAL=
//Have library nsl;ws2_32;wsock32
H5_HAVE_LIBNSL:INTERNAL=
//Have library socket;ws2_32;wsock32
H5_HAVE_LIBSOCKET:INTERNAL=
//Have library ucb;ws2_32;wsock32
H5_HAVE_LIBUCB:INTERNAL=
//Have library ws2_32;
H5_HAVE_LIBWS2_32:INTERNAL=1
//Have library wsock32;ws2_32
H5_HAVE_LIBWSOCK32:INTERNAL=1
//Have function lstat
H5_HAVE_LSTAT:INTERNAL=
//Have include io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h;sys/timeb.h;sys/types.h;stdlib.h;memory.h
H5_HAVE_MEMORY_H:INTERNAL=1
//Have includes io.h;mfhdf.h
H5_HAVE_MFHDF_H:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h;sys/timeb.h;sys/types.h;stdlib.h;memory.h;winsock.h;netinet/in.h
H5_HAVE_NETINET_IN_H:INTERNAL=
//Have includes io.h;pdb.h
H5_HAVE_PDB_H:INTERNAL=
//Have includes io.h;pthread.h
H5_HAVE_PTHREAD_H:INTERNAL=
//Have function random
H5_HAVE_RANDOM:INTERNAL=
//Have function rand_r
H5_HAVE_RAND_R:INTERNAL=
//Have function setjmp
H5_HAVE_SETJMP:INTERNAL=
//Have function setsysinfo
H5_HAVE_SETSYSINFO:INTERNAL=
//Have function sigaction
H5_HAVE_SIGACTION:INTERNAL=
//Have function siglongjmp
H5_HAVE_SIGLONGJMP:INTERNAL=
//Have function signal
H5_HAVE_SIGNAL:INTERNAL=1
//Have function sigprocmask
H5_HAVE_SIGPROCMASK:INTERNAL=
//Have function sigsetjmp
H5_HAVE_SIGSETJMP:INTERNAL=
//Have function snprintf
H5_HAVE_SNPRINTF:INTERNAL=
//Have function srandom
H5_HAVE_SRANDOM:INTERNAL=
//Have includes io.h;setjmp.h;srbclient.h
H5_HAVE_SRBCLIENT_H:INTERNAL=
//Have function stat64
H5_HAVE_STAT64:INTERNAL=
//Have include io.h;setjmp.h;stddef.h;stdint.h
H5_HAVE_STDINT_H:INTERNAL=1
//Have include stdint.h
H5_HAVE_STDINT_H_CXX:INTERNAL=1
//Have include io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h;sys/timeb.h;sys/types.h;stdlib.h
H5_HAVE_STDLIB_H:INTERNAL=1
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;strings.h
H5_HAVE_STRINGS_H:INTERNAL=
//Have include io.h;setjmp.h;stddef.h;stdint.h;string.h
H5_HAVE_STRING_H:INTERNAL=1
//Have function symlink
H5_HAVE_SYMLINK:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/ioctl.h
H5_HAVE_SYS_IOCTL_H:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/proc.h
H5_HAVE_SYS_PROC_H:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/resource.h
H5_HAVE_SYS_RESOURCE_H:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/socket.h
H5_HAVE_SYS_SOCKET_H:INTERNAL=
H5_HAVE_SYS_SYSINFO_H:INTERNAL=
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;sys/time.h
H5_HAVE_SYS_TIME_H:INTERNAL=
//Have include io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h
H5_HAVE_TIME_H:INTERNAL=1
//Have includes io.h;setjmp.h;stddef.h;stdint.h;string.h;sys/stat.h;time.h;sys/timeb.h;sys/types.h;unistd.h
H5_HAVE_UNISTD_H:INTERNAL=
//Have function vasprintf
H5_HAVE_VASPRINTF:INTERNAL=
//Have function vsnprintf
H5_HAVE_VSNPRINTF:INTERNAL=1
//Have function waitpid
H5_HAVE_WAITPID:INTERNAL=
//Other test 
H5_INLINE_TEST___inline:INTERNAL=1
//Other test 
H5_INLINE_TEST___inline__:INTERNAL=
//Other test 
H5_INLINE_TEST_inline:INTERNAL=
//checking IF accurately converting from integers to long double
H5_INTEGER_TO_LDOUBLE_ACCURATE:INTERNAL=1
//checking IF converting from long double to integers is accurate
H5_LDOUBLE_TO_INTEGER_ACCURATE:INTERNAL=1
//Checking IF converting from long double to integers works
H5_LDOUBLE_TO_INTEGER_WORKS:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_INTEGER_WORKS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_INTEGER_WORKS_RUN:INTERNAL=0
//Checking IF correctly converting long double to (unsigned) long
// long values
H5_LDOUBLE_TO_LLONG_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_LLONG_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_LLONG_ACCURATE_RUN:INTERNAL=0
//Checking IF correctly converting long double to unsigned int
// values
H5_LDOUBLE_TO_UINT_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_LDOUBLE_TO_UINT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LDOUBLE_TO_UINT_ACCURATE_RUN:INTERNAL=0
//Use Legacy Names for Libraries and Programs
H5_LEGACY_NAMING:INTERNAL=ON
//Checking IF compiling long long to floating-point typecasts work
H5_LLONG_TO_FP_CAST_WORKS:INTERNAL=1
//Checking IF correctly converting (unsigned) long long to long
// double values
H5_LLONG_TO_LDOUBLE_CORRECT:INTERNAL=1
//Result of TRY_COMPILE
H5_LLONG_TO_LDOUBLE_CORRECT_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_LLONG_TO_LDOUBLE_CORRECT_RUN:INTERNAL=0
//Checking IF alignment restrictions are strictly enforced
H5_NO_ALIGNMENT_RESTRICTIONS:INTERNAL=1
//Result of TRY_COMPILE
H5_NO_ALIGNMENT_RESTRICTIONS_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_NO_ALIGNMENT_RESTRICTIONS_RUN:INTERNAL=0
//Width for printf for type `long long' or `__int64', us. `ll
H5_PRINTF_LL_WIDTH:INTERNAL="ll"
//CHECK_TYPE_SIZE: sizeof(char)
H5_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
H5_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
H5_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
H5_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int16_t)
H5_SIZEOF_INT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int32_t)
H5_SIZEOF_INT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int64_t)
H5_SIZEOF_INT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int8_t)
H5_SIZEOF_INT8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int_fast16_t)
H5_SIZEOF_INT_FAST16_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int_fast32_t)
H5_SIZEOF_INT_FAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int_fast64_t)
H5_SIZEOF_INT_FAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_fast8_t)
H5_SIZEOF_INT_FAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int_least16_t)
H5_SIZEOF_INT_LEAST16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int_least32_t)
H5_SIZEOF_INT_LEAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int_least64_t)
H5_SIZEOF_INT_LEAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(int_least8_t)
H5_SIZEOF_INT_LEAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(long)
H5_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long double)
H5_SIZEOF_LONG_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long long)
H5_SIZEOF_LONG_LONG:INTERNAL=8
//SizeOf for off64_t
H5_SIZEOF_OFF64_T:INTERNAL=0
//CHECK_TYPE_SIZE: sizeof(off_t)
H5_SIZEOF_OFF_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(short)
H5_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(size_t)
H5_SIZEOF_SIZE_T:INTERNAL=4
//SizeOf for ssize_t
H5_SIZEOF_SSIZE_T:INTERNAL=0
//CHECK_TYPE_SIZE: sizeof(uint16_t)
H5_SIZEOF_UINT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint32_t)
H5_SIZEOF_UINT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint64_t)
H5_SIZEOF_UINT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint8_t)
H5_SIZEOF_UINT8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(uint_fast16_t)
H5_SIZEOF_UINT_FAST16_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint_fast32_t)
H5_SIZEOF_UINT_FAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint_fast64_t)
H5_SIZEOF_UINT_FAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_fast8_t)
H5_SIZEOF_UINT_FAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(uint_least16_t)
H5_SIZEOF_UINT_LEAST16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint_least32_t)
H5_SIZEOF_UINT_LEAST32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(uint_least64_t)
H5_SIZEOF_UINT_LEAST64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(uint_least8_t)
H5_SIZEOF_UINT_LEAST8_T:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(unsigned)
H5_SIZEOF_UNSIGNED:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(__int64)
H5_SIZEOF___INT64:INTERNAL=8
//Checking IF compiling unsigned long long to floating-point typecasts
// work
H5_ULLONG_TO_FP_CAST_WORKS:INTERNAL=1
//Checking IF converting unsigned long long to long double with
// precision
H5_ULLONG_TO_LDOUBLE_PRECISION:INTERNAL=
//Result of TRY_COMPILE
H5_ULLONG_TO_LDOUBLE_PRECISION_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_ULLONG_TO_LDOUBLE_PRECISION_RUN:INTERNAL=1
//Checking IF accurately converting unsigned long to float values
H5_ULONG_TO_FLOAT_ACCURATE:INTERNAL=1
//Result of TRY_COMPILE
H5_ULONG_TO_FLOAT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_ULONG_TO_FLOAT_ACCURATE_RUN:INTERNAL=0
//Checking IF accurately converting unsigned long long to floating-point
// values
H5_ULONG_TO_FP_BOTTOM_BIT_ACCURATE:INTERNAL=
//Result of TRY_COMPILE
H5_ULONG_TO_FP_BOTTOM_BIT_ACCURATE_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
H5_ULONG_TO_FP_BOTTOM_BIT_ACCURATE_RUN:INTERNAL=1
HASH_MAP_CLASS:INTERNAL=hash_map
HASH_MAP_H:INTERNAL=hash_map
HASH_NAMESPACE:INTERNAL=std
HASH_SET_CLASS:INTERNAL=hash_set
HASH_SET_H:INTERNAL=hash_set
//Have symbol alloca
HAVE_ALLOCA:INTERNAL=
//Have includes ;alloca.h
HAVE_ALLOCA_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ansidecl.h
HAVE_ANSIDECL_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;arpa/inet.h
HAVE_ARPA_INET_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;arpa/nameser.h
HAVE_ARPA_NAMESER_H:INTERNAL=
//Have include assert.h
HAVE_ASSERT_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_CMAKE_REQUIRE_LARGE_FILE_SUPPORT:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_CMAKE_SIZEOF_UNSIGNED_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_CMAKE_WORDS_BIGENDIAN:INTERNAL=TRUE
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h
HAVE_CTYPE_H:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;dirent.h
HAVE_DIRENT_H:INTERNAL=
//Have includes dlfcn.h
HAVE_DLFCN_H:INTERNAL=
//Have library 
HAVE_DLOPEN:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;dl.h
HAVE_DL_H:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h
HAVE_ERRNO_H:INTERNAL=1
//Have include fcntl.h
HAVE_FCNTL_H:INTERNAL=1
//Have include fenv.h
HAVE_FENV_H:INTERNAL=
//Have symbol finite
HAVE_FINITE:INTERNAL=
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h
HAVE_FLOAT_H:INTERNAL=1
//Have function floor
HAVE_FLOOR:INTERNAL=1
//Have symbol fpclass
HAVE_FPCLASS:INTERNAL=
//Have symbol fprintf
HAVE_FPRINTF:INTERNAL=1
//Have symbol fp_class
HAVE_FP_CLASS:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;fp_class.h
HAVE_FP_CLASS_H:INTERNAL=
//Have symbol ftime
HAVE_FTIME:INTERNAL=1
//NetCDF test 
HAVE_FTRUNCATE:INTERNAL=
//Result of TRY_COMPILE
HAVE_GETADDRINFO_COMPILED:INTERNAL=FALSE
//Have function getopt
HAVE_GETOPT:INTERNAL=
//Have symbol gettimeofday
HAVE_GETTIMEOFDAY:INTERNAL=
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_FAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_INT_LEAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_OFF64_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_OFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_SSIZE_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_FAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UINT_LEAST8_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF_UNSIGNED:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_H5_SIZEOF___INT64:INTERNAL=TRUE
HAVE_HASH_MAP:INTERNAL=1
HAVE_HASH_SET:INTERNAL=1
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF_VOID_P:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_ICET_SIZEOF___INT64:INTERNAL=TRUE
//Have includes ieeefp.h
HAVE_IEEEFP_H:INTERNAL=
//Have includes inttypes.h
HAVE_INTTYPES_H:INTERNAL=
//Have function isascii
HAVE_ISASCII:INTERNAL=
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_KWSYS_SIZEOF___INT64:INTERNAL=TRUE
//Have library dl;
HAVE_LIBDL:INTERNAL=
//Have include limits.h
HAVE_LIMITS_H:INTERNAL=1
//Have symbol localtime
HAVE_LOCALTIME:INTERNAL=1
//Have include malloc.h
HAVE_MALLOC_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h
HAVE_MATH_H:INTERNAL=1
//Have function memmove
HAVE_MEMMOVE:INTERNAL=1
//Have include memory.h
HAVE_MEMORY_H:INTERNAL=1
//Have function memset
HAVE_MEMSET:INTERNAL=1
//Have function mmap
HAVE_MMAP:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;nan.h
HAVE_NAN_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;ndir.h
HAVE_NDIR_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;netdb.h
HAVE_NETDB_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;netinet/in.h
HAVE_NETINET_IN_H:INTERNAL=
//Have function pow
HAVE_POW:INTERNAL=1
//Have symbol printf
HAVE_PRINTF:INTERNAL=1
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;pthread.h
HAVE_PTHREAD_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;resolv.h
HAVE_RESOLV_H:INTERNAL=
//Have library dld;
HAVE_SHLLOAD:INTERNAL=
//Have symbol signal
HAVE_SIGNAL:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h
HAVE_SIGNAL_H:INTERNAL=1
//Result of TRY_COMPILE
HAVE_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_OFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_PTRDIFF_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SIZE_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_SIZEOF_SSIZE_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF_UCHAR:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF__BOOL:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_SIZEOF___INT64:INTERNAL=TRUE
//Have symbol snprintf
HAVE_SNPRINTF:INTERNAL=
//Result of TRY_COMPILE
HAVE_SOCKLEN_T_COMPILED:INTERNAL=FALSE
//Have symbol sprintf
HAVE_SPRINTF:INTERNAL=1
//Have function sqrt
HAVE_SQRT:INTERNAL=1
//Have symbol sscanf
HAVE_SSCANF:INTERNAL=1
//Have symbol stat
HAVE_STAT:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;stdarg.h
HAVE_STDARG_H:INTERNAL=1
//Have includes stdlib.h;sys/types.h;sys/stat.h;fcntl.h;stdio.h;string.h;stddef.h;stdint.h;stdbool.h
HAVE_STDBOOL_H:INTERNAL=
//Have include stddef.h
HAVE_STDDEF_H:INTERNAL=1
//Have include stdint.h
HAVE_STDINT_H:INTERNAL=1
//Have include ;stdio.h
HAVE_STDIO_H:INTERNAL=1
//Have include stdlib.h
HAVE_STDLIB_H:INTERNAL=1
//Have function strcasecmp
HAVE_STRCASECMP:INTERNAL=
//Have function strchr
HAVE_STRCHR:INTERNAL=1
//Have symbol strdup
HAVE_STRDUP:INTERNAL=1
//Have symbol strerror
HAVE_STRERROR:INTERNAL=1
//Have symbol strftime
HAVE_STRFTIME:INTERNAL=1
//Have includes strings.h
HAVE_STRINGS_H:INTERNAL=
//Have include string.h
HAVE_STRING_H:INTERNAL=1
//Have symbol strndup
HAVE_STRNDUP:INTERNAL=
//Have function strrchr
HAVE_STRRCHR:INTERNAL=1
//Have function strstr
HAVE_STRSTR:INTERNAL=1
//Have function strtol
HAVE_STRTOL:INTERNAL=1
//Have function strtoll
HAVE_STRTOLL:INTERNAL=
//Have function strtoul
HAVE_STRTOUL:INTERNAL=1
//NetCDF test 
HAVE_ST_BLKSIZE:INTERNAL=
//Result of TRY_COMPILE
HAVE_SYS_DIR_H_COMPILED:INTERNAL=FALSE
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;stdarg.h;sys/mman.h
HAVE_SYS_MMAN_H:INTERNAL=
//Result of TRY_COMPILE
HAVE_SYS_NDIR_H_COMPILED:INTERNAL=FALSE
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;sys/select.h
HAVE_SYS_SELECT_H:INTERNAL=
//Have includes stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;sys/socket.h
HAVE_SYS_SOCKET_H:INTERNAL=
//Have include sys/stat.h
HAVE_SYS_STAT_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h;signal.h;errno.h;ctype.h;float.h;math.h;stdarg.h;sys/timeb.h
HAVE_SYS_TIMEB_H:INTERNAL=1
//Have includes sys/time.h
HAVE_SYS_TIME_H:INTERNAL=
//Have include sys/types.h
HAVE_SYS_TYPES_H:INTERNAL=1
//Have include stdio.h;stddef.h;sys/types.h;fcntl.h;malloc.h;memory.h;limits.h;stdint.h;stdlib.h;string.h;sys/stat.h;time.h
HAVE_TIME_H:INTERNAL=1
//Have includes unistd.h
HAVE_UNISTD_H:INTERNAL=
//Result of TRY_COMPILE
HAVE_VA_COPY_COMPILED:INTERNAL=FALSE
//Have symbol vfprintf
HAVE_VFPRINTF:INTERNAL=1
//Have symbol vsnprintf
HAVE_VSNPRINTF:INTERNAL=1
//Have symbol vsprintf
HAVE_VSPRINTF:INTERNAL=1
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_INT64_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_UINT16_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_UINT32_T:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_U_INT16_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_VTKOGGTHEORA_U_INT32_T:INTERNAL=FALSE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_CHAR:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_DOUBLE:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_FLOAT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_INT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_LONG_LONG:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF_SHORT:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_SIZEOF___INT64:INTERNAL=TRUE
//Result of TRY_COMPILE
HAVE_VTK_UINTPTR_T:INTERNAL=TRUE
//Have include windows.h
HAVE_WINDOWS_H:INTERNAL=1
//Have symbol _stat
HAVE__STAT:INTERNAL=1
//Result of TRY_COMPILE
HAVE___VA_COPY_COMPILED:INTERNAL=FALSE
//Allow External Library Building
HDF5_ALLOW_EXTERNAL_SUPPORT:INTERNAL=OFF
//Build HDF5 C++ Library
HDF5_BUILD_CPP_LIB:INTERNAL=OFF
//Build HIGH Level HDF5 Library
HDF5_BUILD_HL_LIB:INTERNAL=ON
//Disable compiler warnings
HDF5_DISABLE_COMPILER_WARNINGS:INTERNAL=ON
//Enable the function stack tracing (for developer debugging).
HDF5_ENABLE_CODESTACK:INTERNAL=OFF
//Enable code coverage for Libraries and Programs
HDF5_ENABLE_COVERAGE:INTERNAL=OFF
//Enable deprecated public API symbols
HDF5_ENABLE_DEPRECATED_SYMBOLS:INTERNAL=ON
//Enable GPFS hints for the MPI/POSIX file driver
HDF5_ENABLE_GPFS:INTERNAL=OFF
//Enable datasets larger than memory
HDF5_ENABLE_HSIZET:INTERNAL=ON
//Enable support for large (64-bit) files on Linux.
HDF5_ENABLE_LARGE_FILE:INTERNAL=ON
//Enable parallel build (requires MPI)
HDF5_ENABLE_PARALLEL:INTERNAL=OFF
//Use SZip Filter
HDF5_ENABLE_SZIP_SUPPORT:INTERNAL=OFF
//Enable Threadsafety
HDF5_ENABLE_THREADSAFE:INTERNAL=OFF
//Enable API tracing capability
HDF5_ENABLE_TRACE:INTERNAL=OFF
//Indicate that a memory checker is used
HDF5_ENABLE_USING_MEMCHECKER:INTERNAL=OFF
//Enable Zlib Filters
HDF5_ENABLE_Z_LIB_SUPPORT:INTERNAL=ON
//Securely clear file buffers before writing to file
HDF5_Enable_Clear_File_Buffers:INTERNAL=ON
//Instrument The library
HDF5_Enable_Instrument:INTERNAL=OFF
//Used to pass variables between directories
HDF5_LIBRARIES_TO_EXPORT:INTERNAL=vtkhdf5;vtkhdf5_hl
//Enable metadata trace file collection
HDF5_METADATA_TRACE_FILE:INTERNAL=OFF
//CPACK - include external libraries
HDF5_PACKAGE_EXTLIBS:INTERNAL=OFF
//Result of TRY_COMPILE
HDF5_PRINTF_LL_TEST_COMPILE:INTERNAL=TRUE
//Result of TRY_RUN
HDF5_PRINTF_LL_TEST_RUN:INTERNAL=0
//Whether to perform strict file format checks
HDF5_STRICT_FORMAT_CHECKS:INTERNAL=OFF
//Use the HDF5 1.6.x API by default
HDF5_USE_16_API_DEFAULT:INTERNAL=OFF
//Use the FLETCHER32 Filter
HDF5_USE_FILTER_FLETCHER32:INTERNAL=ON
//Use the NBIT Filter
HDF5_USE_FILTER_NBIT:INTERNAL=ON
//Use the SCALEOFFSET Filter
HDF5_USE_FILTER_SCALEOFFSET:INTERNAL=ON
//Use the SHUFFLE Filter
HDF5_USE_FILTER_SHUFFLE:INTERNAL=ON
//Use the PACKED BITS feature in h5dump
HDF5_USE_H5DUMP_PACKED_BITS:INTERNAL=ON
//IF data accuracy is guaranteed during data conversions
HDF5_WANT_DATA_ACCURACY:INTERNAL=ON
//exception handling functions is checked during data conversions
HDF5_WANT_DCONV_EXCEPTION:INTERNAL=ON
//ADVANCED property for variable: HGCOMMAND
HGCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_BUILD_TESTING
ICET_BUILD_TESTING-ADVANCED:INTERNAL=1
ICET_INSTALL_TARGETS:INTERNAL=IceTCore;IceTMPI;IceTGL
//ADVANCED property for variable: ICET_MAGIC_K
ICET_MAGIC_K-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_MAX_IMAGE_SPLIT
ICET_MAX_IMAGE_SPLIT-ADVANCED:INTERNAL=1
//This is set from VTK_MPIRUN_EXE.
ICET_MPIRUN_EXE:INTERNAL=C:/Program Files/Microsoft HPC Pack 2008 R2/Bin/mpiexec.exe
//ADVANCED property for variable: ICET_MPI_MAX_NUMPROCS
ICET_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//This is set from VTK_MPI_MAX_NUMPROCS.
ICET_MPI_MAX_NUMPROCS:INTERNAL=2
//This is set from a combination of VTK_MPI_PRENUMPROC_FLAGS and
// VTK_MPI_NUMPROC_FLAG
ICET_MPI_NUMPROC_FLAG:INTERNAL=;-np
//This is set from VTK_MPI_POSTFLAGS.
ICET_MPI_POSTFLAGS:INTERNAL=
//This is set from VTK_MPI_PREFLAGS.
ICET_MPI_PREFLAGS:INTERNAL=
//CHECK_TYPE_SIZE: sizeof(char)
ICET_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
ICET_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
ICET_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
ICET_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
ICET_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
ICET_SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
ICET_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(void*)
ICET_SIZEOF_VOID_P:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(__int64)
ICET_SIZEOF___INT64:INTERNAL=8
//ADVANCED property for variable: ICET_TEST_FLAGS
ICET_TEST_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_USE_MPE
ICET_USE_MPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_USE_MPI
ICET_USE_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ICET_USE_OPENGL
ICET_USE_OPENGL-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
INLINE_TEST___inline:INTERNAL=TRUE
//Result of TRY_COMPILE
INLINE_TEST___inline__:INTERNAL=FALSE
//Result of TRY_COMPILE
INLINE_TEST_inline:INTERNAL=FALSE
//ADVANCED property for variable: JAVACOMMAND
JAVACOMMAND-ADVANCED:INTERNAL=1
//Result of TRY_RUN
KWSYS_CHAR_IS_SIGNED:INTERNAL=0
//Result of TRY_COMPILE
KWSYS_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ARGUMENT_DEPENDENT_LOOKUP_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ATOLL_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ATOL_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CSTDDEF_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_CSTDIO_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_ENVIRON_IN_STDLIB_H_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_FULL_SPECIALIZATION_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_LONG_LONG_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_MEMBER_TEMPLATES_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_NULL_TEMPLATE_ARGS_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_RLIMIT64_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_SETENV_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UNSETENV_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UTIMENSAT_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS_UTIMES_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_HAS__ATOI64_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_HAS___INT64_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_CXX_SAME_LONG_AND___INT64_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_CXX_SAME_LONG_LONG_AND___INT64_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_C_HAS_PTRDIFF_T_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_C_HAS_SSIZE_T_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_C_TYPE_MACROS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_HAVE_BINARY_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_HAVE_STD_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_USE_ANSI_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_IOS_USE_SSTREAM_COMPILED:INTERNAL=TRUE
//Checking for Large File Support failed to compile.
KWSYS_LFS_WORKS:INTERNAL=-1
//Result of TRY_COMPILE
KWSYS_LFS_WORKS_COMPILED:INTERNAL=FALSE
//CHECK_TYPE_SIZE: sizeof(char)
KWSYS_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int)
KWSYS_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
KWSYS_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
KWSYS_SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
KWSYS_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(__int64)
KWSYS_SIZEOF___INT64:INTERNAL=8
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_MAX_SIZE_ARGUMENT_COMPILED:INTERNAL=FALSE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_OBJECTS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_REBIND_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ALLOCATOR_TEMPLATE_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_ITERATOR_TRAITS_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAS_WSTRING_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_HAVE_STD_COMPILED:INTERNAL=TRUE
//Result of TRY_COMPILE
KWSYS_STL_STRING_HAVE_NEQ_CHAR_COMPILED:INTERNAL=TRUE
//Have includes sys/types.h;ifaddrs.h
KWSYS_SYS_HAS_IFADDRS_H:INTERNAL=
//Have symbol GetProcessMemoryInfo
KWSYS_SYS_HAS_PSAPI:INTERNAL=1
//ADVANCED property for variable: LIBRARY_OUTPUT_PATH
LIBRARY_OUTPUT_PATH-ADVANCED:INTERNAL=1
LIBRARY_OUTPUT_PATH:INTERNAL=E:/immersiveParaview/ParaView-build/ThirdParty/protobuf/vtkprotobuf/bin
//ADVANCED property for variable: MAKECOMMAND
MAKECOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MEMORYCHECK_COMMAND
MEMORYCHECK_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MEMORYCHECK_SUPPRESSIONS_FILE
MEMORYCHECK_SUPPRESSIONS_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC
MPIEXEC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_MAX_NUMPROCS
MPIEXEC_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_NUMPROC_FLAG
MPIEXEC_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_POSTFLAGS
MPIEXEC_POSTFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPIEXEC_PREFLAGS
MPIEXEC_PREFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILER
MPI_CXX_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_COMPILE_FLAGS
MPI_CXX_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_INCLUDE_PATH
MPI_CXX_INCLUDE_PATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_LIBRARIES
MPI_CXX_LIBRARIES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_CXX_LINK_FLAGS
MPI_CXX_LINK_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILER
MPI_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_COMPILE_FLAGS
MPI_C_COMPILE_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_C_INCLUDE_PATH
MPI_C_INCLUDE_PATH-ADVANCED:INTERNAL=0
//ADVANCED property for variable: MPI_C_LIBRARIES
MPI_C_LIBRARIES-ADVANCED:INTERNAL=0
//ADVANCED property for variable: MPI_C_LINK_FLAGS
MPI_C_LINK_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: MPI_EXTRA_LIBRARY
MPI_EXTRA_LIBRARY-ADVANCED:INTERNAL=1
//Scratch variable for MPI header detection
MPI_HEADER_PATH:INTERNAL=MPI_HEADER_PATH-NOTFOUND
//Scratch variable for MPI lib detection
MPI_LIB:INTERNAL=MPI_LIB-NOTFOUND
//ADVANCED property for variable: MPI_LIBRARY
MPI_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_AutobahnPython
Module_AutobahnPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_SixPython
Module_SixPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_Twisted
Module_Twisted-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_VisItLib
Module_VisItLib-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_ZopeInterface
Module_ZopeInterface-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqApplicationComponents
Module_pqApplicationComponents-ADVANCED:INTERNAL=1
//Request building pqApplicationComponents
Module_pqApplicationComponents:INTERNAL=OFF
//ADVANCED property for variable: Module_pqComponents
Module_pqComponents-ADVANCED:INTERNAL=1
//Request building pqComponents
Module_pqComponents:INTERNAL=OFF
//ADVANCED property for variable: Module_pqCore
Module_pqCore-ADVANCED:INTERNAL=1
//Request building pqCore
Module_pqCore:INTERNAL=OFF
//ADVANCED property for variable: Module_pqDeprecated
Module_pqDeprecated-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_pqPython
Module_pqPython-ADVANCED:INTERNAL=1
//Request building pqPython
Module_pqPython:INTERNAL=OFF
//ADVANCED property for variable: Module_pqWidgets
Module_pqWidgets-ADVANCED:INTERNAL=1
//Request building pqWidgets
Module_pqWidgets:INTERNAL=OFF
//ADVANCED property for variable: Module_smTestDriver
Module_smTestDriver-ADVANCED:INTERNAL=1
//Request building smTestDriver
Module_smTestDriver:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkAcceleratorsDax
Module_vtkAcceleratorsDax-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkAcceleratorsPiston
Module_vtkAcceleratorsPiston-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkChartsCore
Module_vtkChartsCore-ADVANCED:INTERNAL=1
//Request building vtkChartsCore
Module_vtkChartsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkClientServer
Module_vtkClientServer-ADVANCED:INTERNAL=1
//Request building vtkClientServer
Module_vtkClientServer:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonColor
Module_vtkCommonColor-ADVANCED:INTERNAL=1
//Request building vtkCommonColor
Module_vtkCommonColor:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonComputationalGeometry
Module_vtkCommonComputationalGeometry-ADVANCED:INTERNAL=1
//Request building vtkCommonComputationalGeometry
Module_vtkCommonComputationalGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonCore
Module_vtkCommonCore-ADVANCED:INTERNAL=1
//Request building vtkCommonCore
Module_vtkCommonCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonDataModel
Module_vtkCommonDataModel-ADVANCED:INTERNAL=1
//Request building vtkCommonDataModel
Module_vtkCommonDataModel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonExecutionModel
Module_vtkCommonExecutionModel-ADVANCED:INTERNAL=1
//Request building vtkCommonExecutionModel
Module_vtkCommonExecutionModel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonMath
Module_vtkCommonMath-ADVANCED:INTERNAL=1
//Request building vtkCommonMath
Module_vtkCommonMath:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonMisc
Module_vtkCommonMisc-ADVANCED:INTERNAL=1
//Request building vtkCommonMisc
Module_vtkCommonMisc:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonSystem
Module_vtkCommonSystem-ADVANCED:INTERNAL=1
//Request building vtkCommonSystem
Module_vtkCommonSystem:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkCommonTransforms
Module_vtkCommonTransforms-ADVANCED:INTERNAL=1
//Request building vtkCommonTransforms
Module_vtkCommonTransforms:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDICOMParser
Module_vtkDICOMParser-ADVANCED:INTERNAL=1
//Request building vtkDICOMParser
Module_vtkDICOMParser:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkDomainsChemistry
Module_vtkDomainsChemistry-ADVANCED:INTERNAL=1
//Request building vtkDomainsChemistry
Module_vtkDomainsChemistry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersAMR
Module_vtkFiltersAMR-ADVANCED:INTERNAL=1
//Request building vtkFiltersAMR
Module_vtkFiltersAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersCore
Module_vtkFiltersCore-ADVANCED:INTERNAL=1
//Request building vtkFiltersCore
Module_vtkFiltersCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersExtraction
Module_vtkFiltersExtraction-ADVANCED:INTERNAL=1
//Request building vtkFiltersExtraction
Module_vtkFiltersExtraction:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersFlowPaths
Module_vtkFiltersFlowPaths-ADVANCED:INTERNAL=1
//Request building vtkFiltersFlowPaths
Module_vtkFiltersFlowPaths:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeneral
Module_vtkFiltersGeneral-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeneral
Module_vtkFiltersGeneral:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeneric
Module_vtkFiltersGeneric-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeneric
Module_vtkFiltersGeneric:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersGeometry
Module_vtkFiltersGeometry-ADVANCED:INTERNAL=1
//Request building vtkFiltersGeometry
Module_vtkFiltersGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersHybrid
Module_vtkFiltersHybrid-ADVANCED:INTERNAL=1
//Request building vtkFiltersHybrid
Module_vtkFiltersHybrid:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersHyperTree
Module_vtkFiltersHyperTree-ADVANCED:INTERNAL=1
//Request building vtkFiltersHyperTree
Module_vtkFiltersHyperTree:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersImaging
Module_vtkFiltersImaging-ADVANCED:INTERNAL=1
//Request building vtkFiltersImaging
Module_vtkFiltersImaging:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersModeling
Module_vtkFiltersModeling-ADVANCED:INTERNAL=1
//Request building vtkFiltersModeling
Module_vtkFiltersModeling:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallel
Module_vtkFiltersParallel-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallel
Module_vtkFiltersParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelFlowPaths
Module_vtkFiltersParallelFlowPaths-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelFlowPaths
Module_vtkFiltersParallelFlowPaths:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelGeometry
Module_vtkFiltersParallelGeometry-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelGeometry
Module_vtkFiltersParallelGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelImaging
Module_vtkFiltersParallelImaging-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelImaging
Module_vtkFiltersParallelImaging:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelMPI
Module_vtkFiltersParallelMPI-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelMPI
Module_vtkFiltersParallelMPI:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersParallelStatistics
Module_vtkFiltersParallelStatistics-ADVANCED:INTERNAL=1
//Request building vtkFiltersParallelStatistics
Module_vtkFiltersParallelStatistics:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersProgrammable
Module_vtkFiltersProgrammable-ADVANCED:INTERNAL=1
//Request building vtkFiltersProgrammable
Module_vtkFiltersProgrammable:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersPython
Module_vtkFiltersPython-ADVANCED:INTERNAL=1
//Request building vtkFiltersPython
Module_vtkFiltersPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersReebGraph
Module_vtkFiltersReebGraph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSMP
Module_vtkFiltersSMP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSelection
Module_vtkFiltersSelection-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersSources
Module_vtkFiltersSources-ADVANCED:INTERNAL=1
//Request building vtkFiltersSources
Module_vtkFiltersSources:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersStatistics
Module_vtkFiltersStatistics-ADVANCED:INTERNAL=1
//Request building vtkFiltersStatistics
Module_vtkFiltersStatistics:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersStatisticsGnuR
Module_vtkFiltersStatisticsGnuR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkFiltersTexture
Module_vtkFiltersTexture-ADVANCED:INTERNAL=1
//Request building vtkFiltersTexture
Module_vtkFiltersTexture:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkFiltersVerdict
Module_vtkFiltersVerdict-ADVANCED:INTERNAL=1
//Request building vtkFiltersVerdict
Module_vtkFiltersVerdict:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkGUISupportMFC
Module_vtkGUISupportMFC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQt
Module_vtkGUISupportQt-ADVANCED:INTERNAL=1
//Request building vtkGUISupportQt
Module_vtkGUISupportQt:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkGUISupportQtOpenGL
Module_vtkGUISupportQtOpenGL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkGUISupportQtSQL
Module_vtkGUISupportQtSQL-ADVANCED:INTERNAL=1
//Request building vtkGUISupportQtSQL
Module_vtkGUISupportQtSQL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkGUISupportQtWebkit
Module_vtkGUISupportQtWebkit-ADVANCED:INTERNAL=1
//Request building vtkGUISupportQtWebkit
Module_vtkGUISupportQtWebkit:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkGeovisCore
Module_vtkGeovisCore-ADVANCED:INTERNAL=1
//Request building vtkGeovisCore
Module_vtkGeovisCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOAMR
Module_vtkIOAMR-ADVANCED:INTERNAL=1
//Request building vtkIOAMR
Module_vtkIOAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOCore
Module_vtkIOCore-ADVANCED:INTERNAL=1
//Request building vtkIOCore
Module_vtkIOCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOEnSight
Module_vtkIOEnSight-ADVANCED:INTERNAL=1
//Request building vtkIOEnSight
Module_vtkIOEnSight:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExodus
Module_vtkIOExodus-ADVANCED:INTERNAL=1
//Request building vtkIOExodus
Module_vtkIOExodus:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOExport
Module_vtkIOExport-ADVANCED:INTERNAL=1
//Request building vtkIOExport
Module_vtkIOExport:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOFFMPEG
Module_vtkIOFFMPEG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGDAL
Module_vtkIOGDAL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGeoJSON
Module_vtkIOGeoJSON-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOGeometry
Module_vtkIOGeometry-ADVANCED:INTERNAL=1
//Request building vtkIOGeometry
Module_vtkIOGeometry:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOImage
Module_vtkIOImage-ADVANCED:INTERNAL=1
//Request building vtkIOImage
Module_vtkIOImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOImport
Module_vtkIOImport-ADVANCED:INTERNAL=1
//Request building vtkIOImport
Module_vtkIOImport:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOInfovis
Module_vtkIOInfovis-ADVANCED:INTERNAL=1
//Request building vtkIOInfovis
Module_vtkIOInfovis:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOLSDyna
Module_vtkIOLSDyna-ADVANCED:INTERNAL=1
//Request building vtkIOLSDyna
Module_vtkIOLSDyna:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOLegacy
Module_vtkIOLegacy-ADVANCED:INTERNAL=1
//Request building vtkIOLegacy
Module_vtkIOLegacy:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMINC
Module_vtkIOMINC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOMPIImage
Module_vtkIOMPIImage-ADVANCED:INTERNAL=1
//Request building vtkIOMPIImage
Module_vtkIOMPIImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMPIParallel
Module_vtkIOMPIParallel-ADVANCED:INTERNAL=1
//Request building vtkIOMPIParallel
Module_vtkIOMPIParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMovie
Module_vtkIOMovie-ADVANCED:INTERNAL=1
//Request building vtkIOMovie
Module_vtkIOMovie:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOMySQL
Module_vtkIOMySQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIONetCDF
Module_vtkIONetCDF-ADVANCED:INTERNAL=1
//Request building vtkIONetCDF
Module_vtkIONetCDF:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOODBC
Module_vtkIOODBC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOPLY
Module_vtkIOPLY-ADVANCED:INTERNAL=1
//Request building vtkIOPLY
Module_vtkIOPLY:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallel
Module_vtkIOParallel-ADVANCED:INTERNAL=1
//Request building vtkIOParallel
Module_vtkIOParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelExodus
Module_vtkIOParallelExodus-ADVANCED:INTERNAL=1
//Request building vtkIOParallelExodus
Module_vtkIOParallelExodus:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelLSDyna
Module_vtkIOParallelLSDyna-ADVANCED:INTERNAL=1
//Request building vtkIOParallelLSDyna
Module_vtkIOParallelLSDyna:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelNetCDF
Module_vtkIOParallelNetCDF-ADVANCED:INTERNAL=1
//Request building vtkIOParallelNetCDF
Module_vtkIOParallelNetCDF:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOParallelXML
Module_vtkIOParallelXML-ADVANCED:INTERNAL=1
//Request building vtkIOParallelXML
Module_vtkIOParallelXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOPostgreSQL
Module_vtkIOPostgreSQL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOSQL
Module_vtkIOSQL-ADVANCED:INTERNAL=1
//Request building vtkIOSQL
Module_vtkIOSQL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOVPIC
Module_vtkIOVPIC-ADVANCED:INTERNAL=1
//Request building vtkIOVPIC
Module_vtkIOVPIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOVideo
Module_vtkIOVideo-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOVisItBridge
Module_vtkIOVisItBridge-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkIOXML
Module_vtkIOXML-ADVANCED:INTERNAL=1
//Request building vtkIOXML
Module_vtkIOXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXMLParser
Module_vtkIOXMLParser-ADVANCED:INTERNAL=1
//Request building vtkIOXMLParser
Module_vtkIOXMLParser:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkIOXdmf2
Module_vtkIOXdmf2-ADVANCED:INTERNAL=1
//Request building vtkIOXdmf2
Module_vtkIOXdmf2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingColor
Module_vtkImagingColor-ADVANCED:INTERNAL=1
//Request building vtkImagingColor
Module_vtkImagingColor:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingCore
Module_vtkImagingCore-ADVANCED:INTERNAL=1
//Request building vtkImagingCore
Module_vtkImagingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingFourier
Module_vtkImagingFourier-ADVANCED:INTERNAL=1
//Request building vtkImagingFourier
Module_vtkImagingFourier:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingGeneral
Module_vtkImagingGeneral-ADVANCED:INTERNAL=1
//Request building vtkImagingGeneral
Module_vtkImagingGeneral:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingHybrid
Module_vtkImagingHybrid-ADVANCED:INTERNAL=1
//Request building vtkImagingHybrid
Module_vtkImagingHybrid:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingMath
Module_vtkImagingMath-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingMorphological
Module_vtkImagingMorphological-ADVANCED:INTERNAL=1
//Request building vtkImagingMorphological
Module_vtkImagingMorphological:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingSources
Module_vtkImagingSources-ADVANCED:INTERNAL=1
//Request building vtkImagingSources
Module_vtkImagingSources:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkImagingStatistics
Module_vtkImagingStatistics-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkImagingStencil
Module_vtkImagingStencil-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisBoost
Module_vtkInfovisBoost-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisBoostGraphAlgorithms
Module_vtkInfovisBoostGraphAlgorithms-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInfovisCore
Module_vtkInfovisCore-ADVANCED:INTERNAL=1
//Request building vtkInfovisCore
Module_vtkInfovisCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInfovisLayout
Module_vtkInfovisLayout-ADVANCED:INTERNAL=1
//Request building vtkInfovisLayout
Module_vtkInfovisLayout:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInfovisParallel
Module_vtkInfovisParallel-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkInteractionImage
Module_vtkInteractionImage-ADVANCED:INTERNAL=1
//Request building vtkInteractionImage
Module_vtkInteractionImage:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInteractionStyle
Module_vtkInteractionStyle-ADVANCED:INTERNAL=1
//Request building vtkInteractionStyle
Module_vtkInteractionStyle:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkInteractionWidgets
Module_vtkInteractionWidgets-ADVANCED:INTERNAL=1
//Request building vtkInteractionWidgets
Module_vtkInteractionWidgets:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkMetaIO
Module_vtkMetaIO-ADVANCED:INTERNAL=1
//Request building vtkMetaIO
Module_vtkMetaIO:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVAnimation
Module_vtkPVAnimation-ADVANCED:INTERNAL=1
//Request building vtkPVAnimation
Module_vtkPVAnimation:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCatalyst
Module_vtkPVCatalyst-ADVANCED:INTERNAL=1
//Request building vtkPVCatalyst
Module_vtkPVCatalyst:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCatalystTestDriver
Module_vtkPVCatalystTestDriver-ADVANCED:INTERNAL=1
//Request building vtkPVCatalystTestDriver
Module_vtkPVCatalystTestDriver:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreCore
Module_vtkPVClientServerCoreCore-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreCore
Module_vtkPVClientServerCoreCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreDefault
Module_vtkPVClientServerCoreDefault-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreDefault
Module_vtkPVClientServerCoreDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVClientServerCoreRendering
Module_vtkPVClientServerCoreRendering-ADVANCED:INTERNAL=1
//Request building vtkPVClientServerCoreRendering
Module_vtkPVClientServerCoreRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVCommon
Module_vtkPVCommon-ADVANCED:INTERNAL=1
//Request building vtkPVCommon
Module_vtkPVCommon:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerImplementationCore
Module_vtkPVServerImplementationCore-ADVANCED:INTERNAL=1
//Request building vtkPVServerImplementationCore
Module_vtkPVServerImplementationCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerImplementationRendering
Module_vtkPVServerImplementationRendering-ADVANCED:INTERNAL=1
//Request building vtkPVServerImplementationRendering
Module_vtkPVServerImplementationRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerApplication
Module_vtkPVServerManagerApplication-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerApplication
Module_vtkPVServerManagerApplication:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerCore
Module_vtkPVServerManagerCore-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerCore
Module_vtkPVServerManagerCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerDefault
Module_vtkPVServerManagerDefault-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerDefault
Module_vtkPVServerManagerDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVServerManagerRendering
Module_vtkPVServerManagerRendering-ADVANCED:INTERNAL=1
//Request building vtkPVServerManagerRendering
Module_vtkPVServerManagerRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsCore
Module_vtkPVVTKExtensionsCore-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsCore
Module_vtkPVVTKExtensionsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsCosmoTools
Module_vtkPVVTKExtensionsCosmoTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkPVVTKExtensionsDefault
Module_vtkPVVTKExtensionsDefault-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsDefault
Module_vtkPVVTKExtensionsDefault:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPVVTKExtensionsRendering
Module_vtkPVVTKExtensionsRendering-ADVANCED:INTERNAL=1
//Request building vtkPVVTKExtensionsRendering
Module_vtkPVVTKExtensionsRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelCore
Module_vtkParallelCore-ADVANCED:INTERNAL=1
//Request building vtkParallelCore
Module_vtkParallelCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelMPI
Module_vtkParallelMPI-ADVANCED:INTERNAL=1
//Request building vtkParallelMPI
Module_vtkParallelMPI:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParallelMPI4Py
Module_vtkParallelMPI4Py-ADVANCED:INTERNAL=1
//Request building vtkParallelMPI4Py
Module_vtkParallelMPI4Py:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkParseOGLExt
Module_vtkParseOGLExt-ADVANCED:INTERNAL=1
//Request building vtkParseOGLExt
Module_vtkParseOGLExt:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPython
Module_vtkPython-ADVANCED:INTERNAL=1
//Request building vtkPython
Module_vtkPython:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkPythonInterpreter
Module_vtkPythonInterpreter-ADVANCED:INTERNAL=1
//Request building vtkPythonInterpreter
Module_vtkPythonInterpreter:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingAnnotation
Module_vtkRenderingAnnotation-ADVANCED:INTERNAL=1
//Request building vtkRenderingAnnotation
Module_vtkRenderingAnnotation:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContext2D
Module_vtkRenderingContext2D-ADVANCED:INTERNAL=1
//Request building vtkRenderingContext2D
Module_vtkRenderingContext2D:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContextOpenGL
Module_vtkRenderingContextOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingContextOpenGL
Module_vtkRenderingContextOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingContextOpenGL2
Module_vtkRenderingContextOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingCore
Module_vtkRenderingCore-ADVANCED:INTERNAL=1
//Request building vtkRenderingCore
Module_vtkRenderingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingFreeType
Module_vtkRenderingFreeType-ADVANCED:INTERNAL=1
//Request building vtkRenderingFreeType
Module_vtkRenderingFreeType:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingFreeTypeFontConfig
Module_vtkRenderingFreeTypeFontConfig-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingFreeTypeOpenGL
Module_vtkRenderingFreeTypeOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingFreeTypeOpenGL
Module_vtkRenderingFreeTypeOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingGL2PS
Module_vtkRenderingGL2PS-ADVANCED:INTERNAL=1
//Request building vtkRenderingGL2PS
Module_vtkRenderingGL2PS:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingImage
Module_vtkRenderingImage-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingLIC
Module_vtkRenderingLIC-ADVANCED:INTERNAL=1
//Request building vtkRenderingLIC
Module_vtkRenderingLIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingLOD
Module_vtkRenderingLOD-ADVANCED:INTERNAL=1
//Request building vtkRenderingLOD
Module_vtkRenderingLOD:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingLabel
Module_vtkRenderingLabel-ADVANCED:INTERNAL=1
//Request building vtkRenderingLabel
Module_vtkRenderingLabel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingMatplotlib
Module_vtkRenderingMatplotlib-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingOpenGL
Module_vtkRenderingOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingOpenGL
Module_vtkRenderingOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingOpenGL2
Module_vtkRenderingOpenGL2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingParallel
Module_vtkRenderingParallel-ADVANCED:INTERNAL=1
//Request building vtkRenderingParallel
Module_vtkRenderingParallel:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingParallelLIC
Module_vtkRenderingParallelLIC-ADVANCED:INTERNAL=1
//Request building vtkRenderingParallelLIC
Module_vtkRenderingParallelLIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingQt
Module_vtkRenderingQt-ADVANCED:INTERNAL=1
//Request building vtkRenderingQt
Module_vtkRenderingQt:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingTk
Module_vtkRenderingTk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkRenderingVolume
Module_vtkRenderingVolume-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolume
Module_vtkRenderingVolume:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeAMR
Module_vtkRenderingVolumeAMR-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolumeAMR
Module_vtkRenderingVolumeAMR:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkRenderingVolumeOpenGL
Module_vtkRenderingVolumeOpenGL-ADVANCED:INTERNAL=1
//Request building vtkRenderingVolumeOpenGL
Module_vtkRenderingVolumeOpenGL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTclTk
Module_vtkTclTk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkTestingCore
Module_vtkTestingCore-ADVANCED:INTERNAL=1
//Request building vtkTestingCore
Module_vtkTestingCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTestingGenericBridge
Module_vtkTestingGenericBridge-ADVANCED:INTERNAL=1
//Request building vtkTestingGenericBridge
Module_vtkTestingGenericBridge:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTestingIOSQL
Module_vtkTestingIOSQL-ADVANCED:INTERNAL=1
//Request building vtkTestingIOSQL
Module_vtkTestingIOSQL:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkTestingRendering
Module_vtkTestingRendering-ADVANCED:INTERNAL=1
//Request building vtkTestingRendering
Module_vtkTestingRendering:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesColorSeriesToXML
Module_vtkUtilitiesColorSeriesToXML-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkUtilitiesEncodeString
Module_vtkUtilitiesEncodeString-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesEncodeString
Module_vtkUtilitiesEncodeString:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesHashSource
Module_vtkUtilitiesHashSource-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesHashSource
Module_vtkUtilitiesHashSource:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesProcessXML
Module_vtkUtilitiesProcessXML-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesProcessXML
Module_vtkUtilitiesProcessXML:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkUtilitiesWrapClientServer
Module_vtkUtilitiesWrapClientServer-ADVANCED:INTERNAL=1
//Request building vtkUtilitiesWrapClientServer
Module_vtkUtilitiesWrapClientServer:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkVPIC
Module_vtkVPIC-ADVANCED:INTERNAL=1
//Request building vtkVPIC
Module_vtkVPIC:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsContext2D
Module_vtkViewsContext2D-ADVANCED:INTERNAL=1
//Request building vtkViewsContext2D
Module_vtkViewsContext2D:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsCore
Module_vtkViewsCore-ADVANCED:INTERNAL=1
//Request building vtkViewsCore
Module_vtkViewsCore:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsGeovis
Module_vtkViewsGeovis-ADVANCED:INTERNAL=1
//Request building vtkViewsGeovis
Module_vtkViewsGeovis:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsInfovis
Module_vtkViewsInfovis-ADVANCED:INTERNAL=1
//Request building vtkViewsInfovis
Module_vtkViewsInfovis:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkViewsQt
Module_vtkViewsQt-ADVANCED:INTERNAL=1
//Request building vtkViewsQt
Module_vtkViewsQt:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkWebApplications
Module_vtkWebApplications-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebCore
Module_vtkWebCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebGLExporter
Module_vtkWebGLExporter-ADVANCED:INTERNAL=1
//Request building vtkWebGLExporter
Module_vtkWebGLExporter:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkWebInstall
Module_vtkWebInstall-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebJavaScript
Module_vtkWebJavaScript-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWebPython
Module_vtkWebPython-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingJava
Module_vtkWrappingJava-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingPythonCore
Module_vtkWrappingPythonCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingTcl
Module_vtkWrappingTcl-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtkWrappingTools
Module_vtkWrappingTools-ADVANCED:INTERNAL=1
//Request building vtkWrappingTools
Module_vtkWrappingTools:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkalglib
Module_vtkalglib-ADVANCED:INTERNAL=1
//Request building vtkalglib
Module_vtkalglib:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkexodusII
Module_vtkexodusII-ADVANCED:INTERNAL=1
//Request building vtkexodusII
Module_vtkexodusII:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkexpat
Module_vtkexpat-ADVANCED:INTERNAL=1
//Request building vtkexpat
Module_vtkexpat:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkfreetype
Module_vtkfreetype-ADVANCED:INTERNAL=1
//Request building vtkfreetype
Module_vtkfreetype:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkftgl
Module_vtkftgl-ADVANCED:INTERNAL=1
//Request building vtkftgl
Module_vtkftgl:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkgl2ps
Module_vtkgl2ps-ADVANCED:INTERNAL=1
//Request building vtkgl2ps
Module_vtkgl2ps:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkhdf5
Module_vtkhdf5-ADVANCED:INTERNAL=1
//Request building vtkhdf5
Module_vtkhdf5:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkicet
Module_vtkicet-ADVANCED:INTERNAL=1
//Request building vtkicet
Module_vtkicet:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkjpeg
Module_vtkjpeg-ADVANCED:INTERNAL=1
//Request building vtkjpeg
Module_vtkjpeg:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkjsoncpp
Module_vtkjsoncpp-ADVANCED:INTERNAL=1
//Request building vtkjsoncpp
Module_vtkjsoncpp:INTERNAL=OFF
//ADVANCED property for variable: Module_vtklibproj4
Module_vtklibproj4-ADVANCED:INTERNAL=1
//Request building vtklibproj4
Module_vtklibproj4:INTERNAL=OFF
//ADVANCED property for variable: Module_vtklibxml2
Module_vtklibxml2-ADVANCED:INTERNAL=1
//Request building vtklibxml2
Module_vtklibxml2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkmpi4py
Module_vtkmpi4py-ADVANCED:INTERNAL=1
//Request building vtkmpi4py
Module_vtkmpi4py:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkmrmpi
Module_vtkmrmpi-ADVANCED:INTERNAL=1
//ADVANCED property for variable: Module_vtknetcdf
Module_vtknetcdf-ADVANCED:INTERNAL=1
//Request building vtknetcdf
Module_vtknetcdf:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkoggtheora
Module_vtkoggtheora-ADVANCED:INTERNAL=1
//Request building vtkoggtheora
Module_vtkoggtheora:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkpng
Module_vtkpng-ADVANCED:INTERNAL=1
//Request building vtkpng
Module_vtkpng:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkprotobuf
Module_vtkprotobuf-ADVANCED:INTERNAL=1
//Request building vtkprotobuf
Module_vtkprotobuf:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkpugixml
Module_vtkpugixml-ADVANCED:INTERNAL=1
//Request building vtkpugixml
Module_vtkpugixml:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkqttesting
Module_vtkqttesting-ADVANCED:INTERNAL=1
//Request building vtkqttesting
Module_vtkqttesting:INTERNAL=OFF
//ADVANCED property for variable: Module_vtksqlite
Module_vtksqlite-ADVANCED:INTERNAL=1
//Request building vtksqlite
Module_vtksqlite:INTERNAL=OFF
//ADVANCED property for variable: Module_vtksys
Module_vtksys-ADVANCED:INTERNAL=1
//Request building vtksys
Module_vtksys:INTERNAL=OFF
//ADVANCED property for variable: Module_vtktiff
Module_vtktiff-ADVANCED:INTERNAL=1
//Request building vtktiff
Module_vtktiff:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkverdict
Module_vtkverdict-ADVANCED:INTERNAL=1
//Request building vtkverdict
Module_vtkverdict:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkxdmf2
Module_vtkxdmf2-ADVANCED:INTERNAL=1
//Request building vtkxdmf2
Module_vtkxdmf2:INTERNAL=OFF
//ADVANCED property for variable: Module_vtkzlib
Module_vtkzlib-ADVANCED:INTERNAL=1
//Request building vtkzlib
Module_vtkzlib:INTERNAL=OFF
//ADVANCED property for variable: NETCDF4_CHUNK_CACHE_NELEMS
NETCDF4_CHUNK_CACHE_NELEMS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_CHUNK_CACHE_PREEMPTION
NETCDF4_CHUNK_CACHE_PREEMPTION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_CHUNK_CACHE_SIZE
NETCDF4_CHUNK_CACHE_SIZE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_DEFAULT_CHUNKS_IN_CACHE
NETCDF4_DEFAULT_CHUNKS_IN_CACHE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_DEFAULT_CHUNK_SIZE
NETCDF4_DEFAULT_CHUNK_SIZE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF4_MAX_DEFAULT_CACHE_SIZE
NETCDF4_MAX_DEFAULT_CACHE_SIZE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF_DISABLE_COMPILER_WARNINGS
NETCDF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: NETCDF_ENABLE_CXX
NETCDF_ENABLE_CXX-ADVANCED:INTERNAL=1
//Have library c
NOT_NEED_LIBNSL:INTERNAL=
//ADVANCED property for variable: OPENGL_gl_LIBRARY
OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OPENGL_glu_LIBRARY
OPENGL_glu_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_CATALYST_ADAPTORS
PARAVIEW_BUILD_CATALYST_ADAPTORS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AdiosReader
PARAVIEW_BUILD_PLUGIN_AdiosReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO
PARAVIEW_BUILD_PLUGIN_AnalyzeNIfTIIO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ArrowGlyph
PARAVIEW_BUILD_PLUGIN_ArrowGlyph-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_CoProcessingScriptGenerator
PARAVIEW_BUILD_PLUGIN_CoProcessingScriptGenerator-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_EyeDomeLighting
PARAVIEW_BUILD_PLUGIN_EyeDomeLighting-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_ForceTime
PARAVIEW_BUILD_PLUGIN_ForceTime-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_GMVReader
PARAVIEW_BUILD_PLUGIN_GMVReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_H5PartReader
PARAVIEW_BUILD_PLUGIN_H5PartReader-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_InSituExodus
PARAVIEW_BUILD_PLUGIN_InSituExodus-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_MantaView
PARAVIEW_BUILD_PLUGIN_MantaView-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_MobileRemoteControl
PARAVIEW_BUILD_PLUGIN_MobileRemoteControl-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_Moments
PARAVIEW_BUILD_PLUGIN_Moments-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource
PARAVIEW_BUILD_PLUGIN_NonOrthogonalSource-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PacMan
PARAVIEW_BUILD_PLUGIN_PacMan-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PointSprite
PARAVIEW_BUILD_PLUGIN_PointSprite-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_PythonQtPlugin
PARAVIEW_BUILD_PLUGIN_PythonQtPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_QuadView
PARAVIEW_BUILD_PLUGIN_QuadView-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_RGBZView
PARAVIEW_BUILD_PLUGIN_RGBZView-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SLACTools
PARAVIEW_BUILD_PLUGIN_SLACTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit
PARAVIEW_BUILD_PLUGIN_SciberQuestToolKit-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SierraPlotTools
PARAVIEW_BUILD_PLUGIN_SierraPlotTools-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_StreamingParticles
PARAVIEW_BUILD_PLUGIN_StreamingParticles-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_SurfaceLIC
PARAVIEW_BUILD_PLUGIN_SurfaceLIC-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator
PARAVIEW_BUILD_PLUGIN_TemporalParallelismScriptGenerator-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_UncertaintyRendering
PARAVIEW_BUILD_PLUGIN_UncertaintyRendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VRPlugin
PARAVIEW_BUILD_PLUGIN_VRPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_PLUGIN_VaporPlugin
PARAVIEW_BUILD_PLUGIN_VaporPlugin-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_BUILD_WEB_DOCUMENTATION
PARAVIEW_BUILD_WEB_DOCUMENTATION-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_CLIENT_RENDER_SERVER_TESTS
PARAVIEW_CLIENT_RENDER_SERVER_TESTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_COLLABORATION_TESTING
PARAVIEW_COLLABORATION_TESTING-ADVANCED:INTERNAL=1
//List of modules to CS wrap
PARAVIEW_CURRENT_CS_MODULES:INTERNAL=vtkCommonCore;vtkCommonMath;vtkCommonMisc;vtkCommonSystem;vtkCommonTransforms;vtkCommonDataModel;vtkCommonExecutionModel;vtkFiltersCore;vtkCommonComputationalGeometry;vtkFiltersGeneral;vtkImagingCore;vtkImagingFourier;vtkFiltersStatistics;vtkFiltersExtraction;vtkFiltersSources;vtkFiltersGeometry;vtkRenderingCore;vtkInteractionStyle;vtkIOCore;vtkIOImage;vtkImagingHybrid;vtkRenderingOpenGL;vtkFiltersModeling;vtkIOLegacy;vtkParallelCore;vtkFiltersParallel;vtkFiltersProgrammable;vtkPythonInterpreter;vtkIOXMLParser;vtkPVCommon;vtkPVVTKExtensionsCore;vtkParallelMPI;vtkPVClientServerCoreCore;vtkPVServerImplementationCore;vtkPVServerManagerCore;vtkIOMovie;vtkFiltersAMR;vtkIOGeometry;vtkIOXML;vtkDomainsChemistry;vtkFiltersParallelStatistics;vtkIOEnSight;vtkIOImport;vtkInfovisCore;vtkIOInfovis;vtkIOMPIImage;vtkIONetCDF;vtkIOParallel;vtkIOExodus;vtkIOParallelExodus;vtkIOParallelXML;vtkImagingSources;vtkFiltersHybrid;vtkImagingGeneral;vtkImagingColor;vtkRenderingFreeType;vtkRenderingAnnotation;vtkRenderingVolume;vtkInteractionWidgets;vtkCommonColor;vtkRenderingContext2D;vtkChartsCore;vtkFiltersGeneric;vtkFiltersHyperTree;vtkFiltersParallelMPI;vtkRenderingContextOpenGL;vtkRenderingGL2PS;vtkRenderingLabel;vtkIOExport;vtkRenderingFreeTypeOpenGL;vtkRenderingLIC;vtkRenderingParallel;vtkRenderingParallelLIC;vtkPVVTKExtensionsRendering;vtkPVVTKExtensionsDefault;vtkRenderingVolumeAMR;vtkRenderingVolumeOpenGL;vtkViewsCore;vtkViewsContext2D;vtkWebGLExporter;vtkPVClientServerCoreRendering;vtkPVClientServerCoreDefault;vtkPVServerImplementationRendering;vtkPVServerManagerRendering;vtkTestingRendering;vtkPVServerManagerDefault;vtkPVAnimation;vtkFiltersFlowPaths;vtkFiltersParallelFlowPaths;vtkFiltersImaging;vtkFiltersParallelImaging;vtkFiltersPython;vtkFiltersTexture;vtkFiltersVerdict;vtkIOAMR;vtkIOPLY;vtkIOLSDyna;vtkIOParallelLSDyna;vtkIOParallelNetCDF;vtkIOVPIC;vtkIOXdmf2;vtkImagingMorphological;vtkInteractionImage;vtkRenderingLOD;vtkPVServerManagerApplication;vtkFiltersParallelGeometry;vtkIOSQL;vtkInfovisLayout;vtkViewsInfovis;vtkGeovisCore;vtkViewsGeovis;vtkIOMPIParallel;vtkPVCatalyst;vtkPVCatalystTestDriver;vtkParallelMPI4Py;vtkRenderingQt
//ADVANCED property for variable: PARAVIEW_DATA_EXCLUDE_FROM_ALL
PARAVIEW_DATA_EXCLUDE_FROM_ALL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_DATA_STORE
PARAVIEW_DATA_STORE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_SPYPLOT_MARKERS
PARAVIEW_ENABLE_SPYPLOT_MARKERS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED
PARAVIEW_ENABLE_VTK_MODULES_AS_NEEDED-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_ENABLE_WEB
PARAVIEW_ENABLE_WEB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_EXTERNAL_PLUGIN_DIRS
PARAVIEW_EXTERNAL_PLUGIN_DIRS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_INITIALIZE_MPI_ON_CLIENT
PARAVIEW_INITIALIZE_MPI_ON_CLIENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_QT_VERSION
PARAVIEW_QT_VERSION-ADVANCED:INTERNAL=1
//STRINGS property for variable: PARAVIEW_QT_VERSION
PARAVIEW_QT_VERSION-STRINGS:INTERNAL=4;5
//Server Manager XMLs
PARAVIEW_SERVERMANAGER_XMLS:INTERNAL=E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/Default/settings.xml;E:/immersiveParaview/ParaView/ParaViewCore/Animation/animation.xml;E:/immersiveParaview/ParaView/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml
//ADVANCED property for variable: PARAVIEW_USE_ICE_T
PARAVIEW_USE_ICE_T-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_MPI_SSEND
PARAVIEW_USE_MPI_SSEND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PARAVIEW_USE_SYSTEM_MPI4PY
PARAVIEW_USE_SYSTEM_MPI4PY-ADVANCED:INTERNAL=1
//Have symbol atanh
PROJ_HAVE_ATANH:INTERNAL=
//Have symbol csin
PROJ_HAVE_COMPLEX:INTERNAL=
//ADVANCED property for variable: PROJ_LIST_EXTERNAL
PROJ_LIST_EXTERNAL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PROJ_USE_GSL
PROJ_USE_GSL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PROJ_USE_PTHREADS
PROJ_USE_PTHREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PROTOBUF_DISABLE_COMPILER_WARNINGS
PROTOBUF_DISABLE_COMPILER_WARNINGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_CLEAN_COMMAND
PV_TEST_CLEAN_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_CLIENT
PV_TEST_CLIENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_INIT_COMMAND
PV_TEST_INIT_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PV_TEST_USE_RANDOM_PORTS
PV_TEST_USE_RANDOM_PORTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_DEBUG_LIBRARY
PYTHON_DEBUG_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_EXECUTABLE
PYTHON_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: PYTHON_INCLUDE_DIR
PYTHON_INCLUDE_DIR-ADVANCED:INTERNAL=1
//Path to where Python.h is found (deprecated)
PYTHON_INCLUDE_PATH:INTERNAL=C:/Python27/include
//ADVANCED property for variable: PYTHON_LIBRARY
PYTHON_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_DEBUG
QT_ARTHURPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_ARTHURPLUGIN_PLUGIN_RELEASE
QT_ARTHURPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
QT_BINARY_DIR:INTERNAL=C:/Qt/4.8.6/bin
//ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_DEBUG
QT_CONTAINEREXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_CONTAINEREXTENSION_PLUGIN_RELEASE
QT_CONTAINEREXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG
QT_CUSTOMWIDGETPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE
QT_CUSTOMWIDGETPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DBUSCPP2XML_EXECUTABLE
QT_DBUSCPP2XML_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DBUSXML2CPP_EXECUTABLE
QT_DBUSXML2CPP_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DESIGNER_EXECUTABLE
QT_DESIGNER_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_DOC_DIR
QT_DOC_DIR-ADVANCED:INTERNAL=1
QT_HEADERS_DIR:INTERNAL=C:/Qt/4.8.6/include
//ADVANCED property for variable: QT_HELP_GENERATOR
QT_HELP_GENERATOR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_IMPORTS_DIR
QT_IMPORTS_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_LIBRARY_DIR
QT_LIBRARY_DIR-ADVANCED:INTERNAL=1
//Qt library dir
QT_LIBRARY_DIR:INTERNAL=C:/Qt/4.8.6/lib
//ADVANCED property for variable: QT_LINGUIST_EXECUTABLE
QT_LINGUIST_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_LRELEASE_EXECUTABLE
QT_LRELEASE_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_LUPDATE_EXECUTABLE
QT_LUPDATE_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_MKSPECS_DIR
QT_MKSPECS_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_MOC_EXECUTABLE
QT_MOC_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_DEBUG
QT_PHONONWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONONWIDGETS_PLUGIN_RELEASE
QT_PHONONWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_DS9_PLUGIN_DEBUG
QT_PHONON_DS9_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_DS9_PLUGIN_RELEASE
QT_PHONON_DS9_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_INCLUDE_DIR
QT_PHONON_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_LIBRARY
QT_PHONON_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_LIBRARY_DEBUG
QT_PHONON_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PHONON_LIBRARY_RELEASE
QT_PHONON_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_PLUGINS_DIR
QT_PLUGINS_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXCONTAINER_INCLUDE_DIR
QT_QAXCONTAINER_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXCONTAINER_LIBRARY
QT_QAXCONTAINER_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXCONTAINER_LIBRARY_DEBUG
QT_QAXCONTAINER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXCONTAINER_LIBRARY_RELEASE
QT_QAXCONTAINER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXSERVER_INCLUDE_DIR
QT_QAXSERVER_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXSERVER_LIBRARY
QT_QAXSERVER_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXSERVER_LIBRARY_DEBUG
QT_QAXSERVER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QAXSERVER_LIBRARY_RELEASE
QT_QAXSERVER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCNCODECS_PLUGIN_DEBUG
QT_QCNCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCNCODECS_PLUGIN_RELEASE
QT_QCNCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCOLLECTIONGENERATOR_EXECUTABLE
QT_QCOLLECTIONGENERATOR_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_DEBUG
QT_QCOREWLANBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QCOREWLANBEARER_PLUGIN_RELEASE
QT_QCOREWLANBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_DEBUG
QT_QDECLARATIVEVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECLARATIVEVIEW_PLUGIN_RELEASE
QT_QDECLARATIVEVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_DEBUG
QT_QDECORATIONDEFAULT_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONDEFAULT_PLUGIN_RELEASE
QT_QDECORATIONDEFAULT_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_DEBUG
QT_QDECORATIONWINDOWS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QDECORATIONWINDOWS_PLUGIN_RELEASE
QT_QDECORATIONWINDOWS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_DEBUG
QT_QGENERICBEARER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGENERICBEARER_PLUGIN_RELEASE
QT_QGENERICBEARER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGIF_PLUGIN_DEBUG
QT_QGIF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGIF_PLUGIN_RELEASE
QT_QGIF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG
QT_QGLGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE
QT_QGLGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QICO_PLUGIN_DEBUG
QT_QICO_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QICO_PLUGIN_RELEASE
QT_QICO_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_DEBUG
QT_QIMSW_MULTI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QIMSW_MULTI_PLUGIN_RELEASE
QT_QIMSW_MULTI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPCODECS_PLUGIN_DEBUG
QT_QJPCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPCODECS_PLUGIN_RELEASE
QT_QJPCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPEG_PLUGIN_DEBUG
QT_QJPEG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QJPEG_PLUGIN_RELEASE
QT_QJPEG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QKRCODECS_PLUGIN_DEBUG
QT_QKRCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QKRCODECS_PLUGIN_RELEASE
QT_QKRCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QMAKE_EXECUTABLE
QT_QMAKE_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QMNG_PLUGIN_DEBUG
QT_QMNG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QMNG_PLUGIN_RELEASE
QT_QMNG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLDB2_PLUGIN_DEBUG
QT_QSQLDB2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLDB2_PLUGIN_RELEASE
QT_QSQLDB2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_DEBUG
QT_QSQLIBASE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLIBASE_PLUGIN_RELEASE
QT_QSQLIBASE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE2_PLUGIN_DEBUG
QT_QSQLITE2_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE2_PLUGIN_RELEASE
QT_QSQLITE2_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE_PLUGIN_DEBUG
QT_QSQLITE_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLITE_PLUGIN_RELEASE
QT_QSQLITE_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_DEBUG
QT_QSQLMYSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLMYSQL_PLUGIN_RELEASE
QT_QSQLMYSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLOCI_PLUGIN_DEBUG
QT_QSQLOCI_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLOCI_PLUGIN_RELEASE
QT_QSQLOCI_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLODBC_PLUGIN_DEBUG
QT_QSQLODBC_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLODBC_PLUGIN_RELEASE
QT_QSQLODBC_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_DEBUG
QT_QSQLPSQL_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLPSQL_PLUGIN_RELEASE
QT_QSQLPSQL_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLTDS_PLUGIN_DEBUG
QT_QSQLTDS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSQLTDS_PLUGIN_RELEASE
QT_QSQLTDS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVGICON_PLUGIN_DEBUG
QT_QSVGICON_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVGICON_PLUGIN_RELEASE
QT_QSVGICON_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVG_PLUGIN_DEBUG
QT_QSVG_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QSVG_PLUGIN_RELEASE
QT_QSVG_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG
QT_QT3SUPPORTWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE
QT_QT3SUPPORTWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_INCLUDE_DIR
QT_QT3SUPPORT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY
QT_QT3SUPPORT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_DEBUG
QT_QT3SUPPORT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QT3SUPPORT_LIBRARY_RELEASE
QT_QT3SUPPORT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE
QT_QTACCESSIBLECOMPATWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG
QT_QTACCESSIBLEWIDGETS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE
QT_QTACCESSIBLEWIDGETS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_INCLUDE_DIR
QT_QTASSISTANTCLIENT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY
QT_QTASSISTANTCLIENT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_DEBUG
QT_QTASSISTANTCLIENT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANTCLIENT_LIBRARY_RELEASE
QT_QTASSISTANTCLIENT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_INCLUDE_DIR
QT_QTASSISTANT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_LIBRARY
QT_QTASSISTANT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_DEBUG
QT_QTASSISTANT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTASSISTANT_LIBRARY_RELEASE
QT_QTASSISTANT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCLUCENE_LIBRARY
QT_QTCLUCENE_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_DEBUG
QT_QTCLUCENE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCLUCENE_LIBRARY_RELEASE
QT_QTCLUCENE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_INCLUDE_DIR
QT_QTCORE_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_LIBRARY
QT_QTCORE_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_LIBRARY_DEBUG
QT_QTCORE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTCORE_LIBRARY_RELEASE
QT_QTCORE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_INCLUDE_DIR
QT_QTDBUS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_LIBRARY
QT_QTDBUS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_LIBRARY_DEBUG
QT_QTDBUS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDBUS_LIBRARY_RELEASE
QT_QTDBUS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_INCLUDE_DIR
QT_QTDECLARATIVE_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY
QT_QTDECLARATIVE_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_DEBUG
QT_QTDECLARATIVE_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDECLARATIVE_LIBRARY_RELEASE
QT_QTDECLARATIVE_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR
QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY
QT_QTDESIGNERCOMPONENTS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG
QT_QTDESIGNERCOMPONENTS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE
QT_QTDESIGNERCOMPONENTS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_INCLUDE_DIR
QT_QTDESIGNER_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_LIBRARY
QT_QTDESIGNER_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_DEBUG
QT_QTDESIGNER_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTDESIGNER_LIBRARY_RELEASE
QT_QTDESIGNER_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_INCLUDE_DIR
QT_QTGUI_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_LIBRARY
QT_QTGUI_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_LIBRARY_DEBUG
QT_QTGUI_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTGUI_LIBRARY_RELEASE
QT_QTGUI_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_INCLUDE_DIR
QT_QTHELP_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_LIBRARY
QT_QTHELP_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_LIBRARY_DEBUG
QT_QTHELP_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTHELP_LIBRARY_RELEASE
QT_QTHELP_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTIFF_PLUGIN_DEBUG
QT_QTIFF_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTIFF_PLUGIN_RELEASE
QT_QTIFF_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMAIN_LIBRARY
QT_QTMAIN_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMAIN_LIBRARY_DEBUG
QT_QTMAIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMAIN_LIBRARY_RELEASE
QT_QTMAIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_INCLUDE_DIR
QT_QTMULTIMEDIA_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY
QT_QTMULTIMEDIA_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_DEBUG
QT_QTMULTIMEDIA_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTMULTIMEDIA_LIBRARY_RELEASE
QT_QTMULTIMEDIA_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_INCLUDE_DIR
QT_QTNETWORK_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_LIBRARY
QT_QTNETWORK_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_LIBRARY_DEBUG
QT_QTNETWORK_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNETWORK_LIBRARY_RELEASE
QT_QTNETWORK_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_INCLUDE_DIR
QT_QTNSPLUGIN_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY
QT_QTNSPLUGIN_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_DEBUG
QT_QTNSPLUGIN_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTNSPLUGIN_LIBRARY_RELEASE
QT_QTNSPLUGIN_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_INCLUDE_DIR
QT_QTOPENGL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_LIBRARY
QT_QTOPENGL_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_LIBRARY_DEBUG
QT_QTOPENGL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTOPENGL_LIBRARY_RELEASE
QT_QTOPENGL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE
QT_QTRACEGRAPHICSSYSTEM_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_DEBUG
QT_QTSCRIPTDBUS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTDBUS_PLUGIN_RELEASE
QT_QTSCRIPTDBUS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_INCLUDE_DIR
QT_QTSCRIPTTOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY
QT_QTSCRIPTTOOLS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_DEBUG
QT_QTSCRIPTTOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPTTOOLS_LIBRARY_RELEASE
QT_QTSCRIPTTOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_INCLUDE_DIR
QT_QTSCRIPT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_LIBRARY
QT_QTSCRIPT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_DEBUG
QT_QTSCRIPT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSCRIPT_LIBRARY_RELEASE
QT_QTSCRIPT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_INCLUDE_DIR
QT_QTSQL_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_LIBRARY
QT_QTSQL_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_LIBRARY_DEBUG
QT_QTSQL_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSQL_LIBRARY_RELEASE
QT_QTSQL_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_INCLUDE_DIR
QT_QTSVG_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_LIBRARY
QT_QTSVG_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_LIBRARY_DEBUG
QT_QTSVG_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTSVG_LIBRARY_RELEASE
QT_QTSVG_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_INCLUDE_DIR
QT_QTTEST_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_LIBRARY
QT_QTTEST_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_LIBRARY_DEBUG
QT_QTTEST_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTTEST_LIBRARY_RELEASE
QT_QTTEST_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_INCLUDE_DIR
QT_QTUITOOLS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_LIBRARY
QT_QTUITOOLS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_DEBUG
QT_QTUITOOLS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTUITOOLS_LIBRARY_RELEASE
QT_QTUITOOLS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWCODECS_PLUGIN_DEBUG
QT_QTWCODECS_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWCODECS_PLUGIN_RELEASE
QT_QTWCODECS_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_INCLUDE_DIR
QT_QTWEBKIT_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_LIBRARY
QT_QTWEBKIT_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_DEBUG
QT_QTWEBKIT_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTWEBKIT_LIBRARY_RELEASE
QT_QTWEBKIT_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_INCLUDE_DIR
QT_QTXMLPATTERNS_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY
QT_QTXMLPATTERNS_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_DEBUG
QT_QTXMLPATTERNS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXMLPATTERNS_LIBRARY_RELEASE
QT_QTXMLPATTERNS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_INCLUDE_DIR
QT_QTXML_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_LIBRARY
QT_QTXML_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_LIBRARY_DEBUG
QT_QTXML_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QTXML_LIBRARY_RELEASE
QT_QTXML_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_DEBUG
QT_QWEBVIEW_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWEBVIEW_PLUGIN_RELEASE
QT_QWEBVIEW_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE
QT_QWSTSLIBMOUSEHANDLER_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_RCC_EXECUTABLE
QT_RCC_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_DEBUG
QT_TASKMENUEXTENSION_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TASKMENUEXTENSION_PLUGIN_RELEASE
QT_TASKMENUEXTENSION_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TESTING_EVENT_PLAYBACK_DELAY
QT_TESTING_EVENT_PLAYBACK_DELAY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_TRANSLATIONS_DIR
QT_TRANSLATIONS_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_UIC3_EXECUTABLE
QT_UIC3_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_UIC_EXECUTABLE
QT_UIC_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE
QT_WORLDTIMECLOCKPLUGIN_PLUGIN_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: QT_XMLPATTERNS_EXECUTABLE
QT_XMLPATTERNS_EXECUTABLE-ADVANCED:INTERNAL=1
//Have symbol Q_WS_MAC
Q_WS_MAC:INTERNAL=
//Have symbol Q_WS_QWS
Q_WS_QWS:INTERNAL=
//Have symbol Q_WS_WIN
Q_WS_WIN:INTERNAL=1
//Have symbol Q_WS_X11
Q_WS_X11:INTERNAL=
//ADVANCED property for variable: SCPCOMMAND
SCPCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SITE
SITE-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(off_t)
SIZEOF_OFF_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(ptrdiff_t)
SIZEOF_PTRDIFF_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(short)
SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(size_t)
SIZEOF_SIZE_T:INTERNAL=4
//CHECK_TYPE_SIZE: ssize_t unknown
SIZEOF_SSIZE_T:INTERNAL=
//CHECK_TYPE_SIZE: uchar unknown
SIZEOF_UCHAR:INTERNAL=
//CHECK_TYPE_SIZE: _Bool unknown
SIZEOF__BOOL:INTERNAL=
//CHECK_TYPE_SIZE: sizeof(__int64)
SIZEOF___INT64:INTERNAL=8
//ADVANCED property for variable: SLURM_SBATCH_COMMAND
SLURM_SBATCH_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SLURM_SRUN_COMMAND
SLURM_SRUN_COMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SQTK_CUDA
SQTK_CUDA-ADVANCED:INTERNAL=1
//ADVANCED property for variable: SQTK_DEBUG
SQTK_DEBUG-ADVANCED:INTERNAL=1
//Have include stdlib.h;stdarg.h;string.h;float.h
STDC_HEADERS:INTERNAL=1
//Result of TRY_COMPILE
SUCCEED:INTERNAL=FALSE
//Result of TRY_COMPILE
SUCCEED_MAP:INTERNAL=TRUE
//Result of TRY_COMPILE
SUCCEED_SET:INTERNAL=TRUE
//Result of TRY_COMPILE
SUPPORT_IP6_COMPILED:INTERNAL=FALSE
//ADVANCED property for variable: SVNCOMMAND
SVNCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VERDICT_BUILD_DOC
VERDICT_BUILD_DOC-ADVANCED:INTERNAL=1
//Build the 2007 Verdict User Manual
VERDICT_BUILD_DOC:INTERNAL=OFF
//ADVANCED property for variable: VERDICT_ENABLE_TESTING
VERDICT_ENABLE_TESTING-ADVANCED:INTERNAL=1
//Should tests of the VERDICT library be built?
VERDICT_ENABLE_TESTING:INTERNAL=OFF
//ADVANCED property for variable: VERDICT_MANGLE
VERDICT_MANGLE-ADVANCED:INTERNAL=1
//Mangle verdict names for inclusion in a larger library?
VERDICT_MANGLE:INTERNAL=OFF
//A string to prepend to all verdict function names and classes.
VERDICT_MANGLE_PREFIX:INTERNAL=
//ADVANCED property for variable: VRPN_INCLUDE_DIR
VRPN_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VRPN_LIBRARY
VRPN_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTKOGGTHEORA_DISABLE_ASM
VTKOGGTHEORA_DISABLE_ASM-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTKOGGTHEORA_DISABLE_FLOAT
VTKOGGTHEORA_DISABLE_FLOAT-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(int)
VTKOGGTHEORA_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int16_t)
VTKOGGTHEORA_INT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(int32_t)
VTKOGGTHEORA_INT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int64_t)
VTKOGGTHEORA_INT64_T:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(long)
VTKOGGTHEORA_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
VTKOGGTHEORA_LONG_LONG:INTERNAL=8
//ADVANCED property for variable: VTKOGGTHEORA_SHARED_LINKER_FLAGS
VTKOGGTHEORA_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(short)
VTKOGGTHEORA_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint16_t)
VTKOGGTHEORA_UINT16_T:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(uint32_t)
VTKOGGTHEORA_UINT32_T:INTERNAL=4
//CHECK_TYPE_SIZE: u_int16_t unknown
VTKOGGTHEORA_U_INT16_T:INTERNAL=
//CHECK_TYPE_SIZE: u_int32_t unknown
VTKOGGTHEORA_U_INT32_T:INTERNAL=
//ADVANCED property for variable: VTK_ALL_NEW_OBJECT_FACTORY
VTK_ALL_NEW_OBJECT_FACTORY-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
VTK_ANSI_STREAM_EOF_COMPILED:INTERNAL=TRUE
//Result of TRY_RUN
VTK_ANSI_STREAM_EOF_RESULT:INTERNAL=0
//ADVANCED property for variable: VTK_BUILD_ALL_MODULES
VTK_BUILD_ALL_MODULES-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_BUILD_ALL_MODULES_FOR_TESTS
VTK_BUILD_ALL_MODULES_FOR_TESTS-ADVANCED:INTERNAL=1
//Directory where python modules will be installed
VTK_BUILD_PYTHON_MODULE_DIR:INTERNAL=E:/immersiveParaview/ParaView-build/lib/site-packages
//Support for full template specialization syntax
VTK_COMPILER_HAS_FULL_SPECIALIZATION:INTERNAL=1
//Test VTK_CONST_REVERSE_ITERATOR_COMPARISON
VTK_CONST_REVERSE_ITERATOR_COMPARISON:INTERNAL=1
//ADVANCED property for variable: VTK_DATA_STORE
VTK_DATA_STORE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_DEBUG_LEAKS
VTK_DEBUG_LEAKS-ADVANCED:INTERNAL=1
//Support for C++ explict templates
VTK_EXPLICIT_TEMPLATES:INTERNAL=1
//ADVANCED property for variable: VTK_GHOSTSCRIPT_EXECUTABLE
VTK_GHOSTSCRIPT_EXECUTABLE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_GLEXT_FILE
VTK_GLEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_GLXEXT_FILE
VTK_GLXEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Imaging
VTK_Group_Imaging-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_MPI
VTK_Group_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewCore
VTK_Group_ParaViewCore-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewQt
VTK_Group_ParaViewQt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_ParaViewRendering
VTK_Group_ParaViewRendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Qt
VTK_Group_Qt-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Rendering
VTK_Group_Rendering-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_StandAlone
VTK_Group_StandAlone-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Tk
VTK_Group_Tk-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Views
VTK_Group_Views-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_Group_Web
VTK_Group_Web-ADVANCED:INTERNAL=1
//Have symbol finite
VTK_HAS_FINITE:INTERNAL=
//Have symbol InterlockedAdd
VTK_HAS_INTERLOCKEDADD:INTERNAL=
//Have symbol isfinite
VTK_HAS_ISFINITE:INTERNAL=
//Have symbol isinf
VTK_HAS_ISINF:INTERNAL=
//Have symbol isnan
VTK_HAS_ISNAN:INTERNAL=
//Test VTK_HAS_STD_ISFINITE
VTK_HAS_STD_ISFINITE:INTERNAL=
//Test VTK_HAS_STD_ISINF
VTK_HAS_STD_ISINF:INTERNAL=
//Test VTK_HAS_STD_ISNAN
VTK_HAS_STD_ISNAN:INTERNAL=
//Have symbol _finite
VTK_HAS__FINITE:INTERNAL=1
//Have symbol _isnan
VTK_HAS__ISNAN:INTERNAL=1
//Support for getsockname with socklen_t
VTK_HAVE_GETSOCKNAME_WITH_SOCKLEN_T:INTERNAL=0
//Have library socket
VTK_HAVE_LIBSOCKET:INTERNAL=
//Have symbol SO_REUSEADDR
VTK_HAVE_SO_REUSEADDR:INTERNAL=
//VTK modular always ignores BTX
VTK_IGNORE_BTX:INTERNAL=ON
//ADVANCED property for variable: VTK_IGNORE_GLDRIVER_BUGS
VTK_IGNORE_GLDRIVER_BUGS-ADVANCED:INTERNAL=1
//Directory where python modules will be installed
VTK_INSTALL_PYTHON_MODULE_DIR:INTERNAL=lib/paraview-4.1/site-packages
//Whether istream supports long long
VTK_ISTREAM_SUPPORTS_LONG_LONG:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_REMOVE
VTK_LEGACY_REMOVE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_LEGACY_SILENT
VTK_LEGACY_SILENT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MAKE_INSTANTIATORS
VTK_MAKE_INSTANTIATORS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MAX_THREADS
VTK_MAX_THREADS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPIRUN_EXE
VTK_MPIRUN_EXE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_MAX_NUMPROCS
VTK_MPI_MAX_NUMPROCS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_NUMPROC_FLAG
VTK_MPI_NUMPROC_FLAG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_POSTFLAGS
VTK_MPI_POSTFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_PREFLAGS
VTK_MPI_PREFLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_MPI_PRENUMPROC_FLAGS
VTK_MPI_PRENUMPROC_FLAGS-ADVANCED:INTERNAL=1
//Disable Python Threads support
VTK_NO_PYTHON_THREADS:INTERNAL=1
//ADVANCED property for variable: VTK_OPENGL_HAS_OSMESA
VTK_OPENGL_HAS_OSMESA-ADVANCED:INTERNAL=1
//Whether ostream supports long long
VTK_OSTREAM_SUPPORTS_LONG_LONG:INTERNAL=1
//ADVANCED property for variable: VTK_QT_VERSION
VTK_QT_VERSION-ADVANCED:INTERNAL=1
//STRINGS property for variable: VTK_QT_VERSION
VTK_QT_VERSION-STRINGS:INTERNAL=4;5
//ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER
VTK_RENDERINGPARALLELLIC_LINEINTEGRALCONVLOLUTION2D_TIMER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER
VTK_RENDERINGPARALLELLIC_SURFACELICPAINTER_TIMER-ADVANCED:INTERNAL=1
//STRINGS property for variable: VTK_RENDERING_BACKEND
VTK_RENDERING_BACKEND-STRINGS:INTERNAL=OpenGL;OpenGL2;None
//ADVANCED property for variable: VTK_REPORT_OPENGL_ERRORS
VTK_REPORT_OPENGL_ERRORS-ADVANCED:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(char)
VTK_SIZEOF_CHAR:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(double)
VTK_SIZEOF_DOUBLE:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(float)
VTK_SIZEOF_FLOAT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(int)
VTK_SIZEOF_INT:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long)
VTK_SIZEOF_LONG:INTERNAL=4
//CHECK_TYPE_SIZE: sizeof(long long)
VTK_SIZEOF_LONG_LONG:INTERNAL=8
//CHECK_TYPE_SIZE: sizeof(short)
VTK_SIZEOF_SHORT:INTERNAL=2
//CHECK_TYPE_SIZE: sizeof(__int64)
VTK_SIZEOF___INT64:INTERNAL=8
//STRINGS property for variable: VTK_SMP_IMPLEMENTATION_TYPE
VTK_SMP_IMPLEMENTATION_TYPE-STRINGS:INTERNAL=Sequential;Simple;Kaapi;TBB
//Whether char is signed.
VTK_TYPE_CHAR_IS_SIGNED:INTERNAL=1
//Result of TRY_COMPILE
VTK_TYPE_CHAR_IS_SIGNED_COMPILED:INTERNAL=TRUE
//Whether long and __int64 are the same type
VTK_TYPE_SAME_LONG_AND___INT64:INTERNAL=0
//Whether long long and __int64 are the same type
VTK_TYPE_SAME_LONG_LONG_AND___INT64:INTERNAL=1
//CHECK_TYPE_SIZE: sizeof(uintptr_t)
VTK_UINTPTR_T:INTERNAL=4
//ADVANCED property for variable: VTK_USE_64BIT_IDS
VTK_USE_64BIT_IDS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_OFFSCREEN
VTK_USE_OFFSCREEN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_EXPAT
VTK_USE_SYSTEM_EXPAT-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_FREETYPE
VTK_USE_SYSTEM_FREETYPE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_GL2PS
VTK_USE_SYSTEM_GL2PS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_HDF5
VTK_USE_SYSTEM_HDF5-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_ICET
VTK_USE_SYSTEM_ICET-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_JPEG
VTK_USE_SYSTEM_JPEG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_JSONCPP
VTK_USE_SYSTEM_JSONCPP-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBPROJ4
VTK_USE_SYSTEM_LIBPROJ4-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_LIBXML2
VTK_USE_SYSTEM_LIBXML2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_NETCDF
VTK_USE_SYSTEM_NETCDF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_OGGTHEORA
VTK_USE_SYSTEM_OGGTHEORA-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PNG
VTK_USE_SYSTEM_PNG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PROTOBUF
VTK_USE_SYSTEM_PROTOBUF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_PUGIXML
VTK_USE_SYSTEM_PUGIXML-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_QTTESTING
VTK_USE_SYSTEM_QTTESTING-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_TIFF
VTK_USE_SYSTEM_TIFF-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_XDMF2
VTK_USE_SYSTEM_XDMF2-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_SYSTEM_ZLIB
VTK_USE_SYSTEM_ZLIB-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TDX
VTK_USE_TDX-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_TK
VTK_USE_TK-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_USE_VIDEO_FOR_WINDOWS
VTK_USE_VIDEO_FOR_WINDOWS-ADVANCED:INTERNAL=1
//Result of TRY_COMPILE
VTK_USE_VIDEO_FOR_WINDOWS_DEFAULT:INTERNAL=TRUE
//ADVANCED property for variable: VTK_USE_X
VTK_USE_X-ADVANCED:INTERNAL=1
//Enable using Video for Windows (vfw32) for video capture.
VTK_VFW_SUPPORTS_CAPTURE:INTERNAL=1
//ADVANCED property for variable: VTK_VPIC_USE_MPI
VTK_VPIC_USE_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WGLEXT_FILE
VTK_WGLEXT_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_HINTS
VTK_WRAP_HINTS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_WRAP_JAVA
VTK_WRAP_JAVA-ADVANCED:INTERNAL=1
//Should VTK Python wrapping be built?
VTK_WRAP_PYTHON:INTERNAL=ON
//ADVANCED property for variable: VTK_WRAP_TCL
VTK_WRAP_TCL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: VTK_XDMF_USE_MPI
VTK_XDMF_USE_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_BUILD_MPI
XDMF_BUILD_MPI-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAS_NDGM
XDMF_HAS_NDGM-ADVANCED:INTERNAL=1
//Whether streams support 64-bit types
XDMF_HAVE_64BIT_STREAMS:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_FCNTL
XDMF_HAVE_FCNTL-ADVANCED:INTERNAL=1
//Have include malloc.h
XDMF_HAVE_MALLOC_H:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_MMAN
XDMF_HAVE_MMAN-ADVANCED:INTERNAL=1
//ADVANCED property for variable: XDMF_HAVE_NETINET
XDMF_HAVE_NETINET-ADVANCED:INTERNAL=1
XDMF_REGENERATE_WRAPPERS:INTERNAL=OFF
XDMF_REGENERATE_YACCLEX:INTERNAL=OFF
//ADVANCED property for variable: XDMF_USE_MYSQL
XDMF_USE_MYSQL-ADVANCED:INTERNAL=1
XDMF_WRAP_CSHARP:INTERNAL=OFF
XDMF_WRAP_PYTHON:INTERNAL=OFF
XDMF_WRAP_TCL:INTERNAL=OFF
//ADVANCED property for variable: ZLIB_INCLUDE_DIR
ZLIB_INCLUDE_DIR-ADVANCED:INTERNAL=1
//ADVANCED property for variable: ZLIB_LIBRARY
ZLIB_LIBRARY-ADVANCED:INTERNAL=1
//ParaView has been configured
__paraview_configured:INTERNAL=TRUE
netcdf_cxx_SOURCES:INTERNAL=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/cxx/netcdf.cpp;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/cxx/ncvalues.cpp
netcdf_dispatch_SOURCES:INTERNAL=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/parallel.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/copy.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/file.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/dim.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/att.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/error.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/var.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/dispatch.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/nc_url.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/nclist.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/ncbytes.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/ncbytes.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libdispatch/nc4.c
netcdf_liblib_SOURCES:INTERNAL=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/liblib/stub.c
netcdf_src4_SOURCES:INTERNAL=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4internal.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/error4.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4dispatch.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4dispatch.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4attr.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4dim.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4file.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4grp.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4type.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4var.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/ncfunc.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4internal.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc4/nc4hdf.c
netcdf_src_SOURCES:INTERNAL=E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/string.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/v1hpg.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/onstack.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/rnd.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/utf8proc.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/utf8proc_data.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/nclistmgr.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/putget.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/attr.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/nc3dispatch.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/nc.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/var.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/dim.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/ncx.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/ncx.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/lookup3.c;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/pstdint.h;E:/immersiveParaview/ParaView/VTK/ThirdParty/netcdf/vtknetcdf/libsrc/posixio.c
protobut_determine_hash_namespace_done:INTERNAL=TRUE
protobut_pthread_test_done:INTERNAL=TRUE
pthread_test_result:INTERNAL=UNKNOWN
//ADVANCED property for variable: smooth_flash
smooth_flash-ADVANCED:INTERNAL=1


From cory.quammen at kitware.com  Tue Jul 15 10:46:04 2014
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 15 Jul 2014 10:46:04 -0400
Subject: [Paraview] New in ParaView: Easy saving of custom defaults in
	ParaView
Message-ID: <CAB5Fpx6SKXi1Ek9RXQ=0xf8Co3Hb9AJwYWTZ_A+71BCbJ7V1fQ@mail.gmail.com>

Dear ParaView users,

I just wrote a blog post about a new way to easily save custom default
values for pipeline objects, representations, and views, that is
coming to ParaView 4.2.

You can find the post at

http://www.kitware.com/blog/home/post/702

As always, your feedback is appreciated.

Cory

From shermanw at indiana.edu  Tue Jul 15 13:09:26 2014
From: shermanw at indiana.edu (William Sherman)
Date: Tue, 15 Jul 2014 13:09:26 -0400
Subject: [Paraview] ParaView Digest, Vol 123,
	Issue 25 [VR plugin cannot be built.]
In-Reply-To: <mailman.1009.1405399644.20882.paraview@paraview.org>
References: <mailman.1009.1405399644.20882.paraview@paraview.org>
Message-ID: <53C56046.1040701@indiana.edu>

On 7/15/14 12:47 AM, paraview-request at paraview.org wrote:
> Message: 2
> Date: Tue, 15 Jul 2014 13:22:02 +0900
> From: Daisuke Meno<menonon at port.kobe-u.ac.jp>
> To:paraview at paraview.org
> Subject: [Paraview] VR plugin cannot be built.

Hello,

> VR plugin cannot be built on Windows7.
> I have followed this page.
> http://www.paraview.org/Wiki/ParaView/VRPN_with_MS-MPI
>
> But I got errors.
> Sorry, text files include some Japanese characters.
>
> Would you give me any solution ?

You'll have to give us some details on what the errors were
and what version of ParaView you have downloaded -- and also,
were there any deviations from the instructions on the Wiki
page.

	Bill

> Thanks
> Daisuke
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Kobe University
> Education Center on Computational Science and Engineering

--
Bill Sherman
Sr. Technology Advisor
Advanced Visualization Lab
Pervasive Technology Inst
Indiana University
shermanw at indiana.edu

From livia.barazzetti at istb.unibe.ch  Tue Jul 15 13:34:59 2014
From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch)
Date: Tue, 15 Jul 2014 17:34:59 +0000
Subject: [Paraview] CopyArray property in Python Programmable Filter using
 the python_filter_generator
Message-ID: <C8921E2F87E8024BBD6C59CB07C0F47D1EB74FAE@aai-exch-mbx1.campus.unibe.ch>

Hi,

I found very interesting the feature "Easy Customization of the ParaView Python Programmable Filter Property Panel" (http://www.kitware.com/blog/home/post/534). I have tried that python_filter_generator for some simple programmable filter, but I  couldn't find how to set the CopyArrays property in my python filter.
What I am doing now is editing the following line in my python filter:

ExtraXml = ' <IntVectorProperty command="SetCopyArrays"  default_values="1"   name="CopyArrays"   number_of_elements="1"  panel_visibility="advanced">   <Documentation>Copy arrays</Documentation>  <BooleanDomain name="bool"/>  </IntVectorProperty>'

Is there a simpler method that I've missed?

Thank you
Livia

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140715/3322c724/attachment.html>

From matthew.woehlke at kitware.com  Tue Jul 15 15:31:32 2014
From: matthew.woehlke at kitware.com (Matthew Woehlke)
Date: Tue, 15 Jul 2014 19:31:32 +0000 (UTC)
Subject: [Paraview] Plugin Crashing on PV 3.12 RC2
References: <73D838C2-D2BA-41B7-9905-C039A702B515@bluequartz.net>
 <CADHSJjC87oZjiDdu2ga3597Vt0qeBvNLE5BmvEgyC+Z3f=ThiA@mail.gmail.com>
 <1C3DC8E9-DAD6-4047-9F9B-B5D8ABDE760B@bluequartz.net>
 <CADHSJjCPBcpbqc0mmHSfsR5LzL8Y=JSKxPjR4+4W+pHmcmSTUw@mail.gmail.com>
Message-ID: <loom.20140715T212150-850@post.gmane.org>

Utkarsh Ayachit <utkarsh.ayachit <at> kitware.com> writes:
> The problem is your VTk classes aren't getting compiled in/wrapped
> correctly. Let me check it out.

Is there a general solution to this?

I'm having the same problem. I have a paraview plugin that I am trying 
to refactor so that the VTK pieces are in their own library (I want to 
be able to use them in other tools without dragging in all the paraview 
stuff on top). Here's the condensed CMake:

  vtk_module(MyLib)
  vtk_module_library(MyLib ${MyLib_sources})

  add_paraview_plugin(MyPlugin "1.0" ...)
  target_link_libraries(MyPlugin MyLib)

Before I split things (i.e. ${MyLib_sources} were passed to 
add_paraview_plugin as SERVER_SOURCES), everything worked fine.

(Note: just for grins, I verified that I can call methods on the 
classes in MyLib from MyPlugin without link errors, so it's not that 
the classes just aren't being exported. It's something with then not 
being properly registered such that they can be created by name.)

-- 
Matthew


From dave.demarle at kitware.com  Tue Jul 15 16:08:59 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 15 Jul 2014 16:08:59 -0400
Subject: [Paraview] Plugin Crashing on PV 3.12 RC2
In-Reply-To: <loom.20140715T212150-850@post.gmane.org>
References: <73D838C2-D2BA-41B7-9905-C039A702B515@bluequartz.net>
 <CADHSJjC87oZjiDdu2ga3597Vt0qeBvNLE5BmvEgyC+Z3f=ThiA@mail.gmail.com>
 <1C3DC8E9-DAD6-4047-9F9B-B5D8ABDE760B@bluequartz.net>
 <CADHSJjCPBcpbqc0mmHSfsR5LzL8Y=JSKxPjR4+4W+pHmcmSTUw@mail.gmail.com>
 <loom.20140715T212150-850@post.gmane.org>
Message-ID: <CANjZAi-fPU-QW74yT0aponPQFgdDGRS3=VxTKyAqOKtT_DdcTQ@mail.gmail.com>

The trick is that you have to make sure that the VTK classes are wrapped
into paraview's client server language and instantiable at run time. Check
the Manta View plugin for an example.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Tue, Jul 15, 2014 at 3:31 PM, Matthew Woehlke <
matthew.woehlke at kitware.com> wrote:

> Utkarsh Ayachit <utkarsh.ayachit <at> kitware.com> writes:
> > The problem is your VTk classes aren't getting compiled in/wrapped
> > correctly. Let me check it out.
>
> Is there a general solution to this?
>
> I'm having the same problem. I have a paraview plugin that I am trying
> to refactor so that the VTK pieces are in their own library (I want to
> be able to use them in other tools without dragging in all the paraview
> stuff on top). Here's the condensed CMake:
>
>   vtk_module(MyLib)
>   vtk_module_library(MyLib ${MyLib_sources})
>
>   add_paraview_plugin(MyPlugin "1.0" ...)
>   target_link_libraries(MyPlugin MyLib)
>
> Before I split things (i.e. ${MyLib_sources} were passed to
> add_paraview_plugin as SERVER_SOURCES), everything worked fine.
>
> (Note: just for grins, I verified that I can call methods on the
> classes in MyLib from MyPlugin without link errors, so it's not that
> the classes just aren't being exported. It's something with then not
> being properly registered such that they can be created by name.)
>
> --
> Matthew
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140715/d082d420/attachment.html>

From dave.demarle at kitware.com  Tue Jul 15 16:45:08 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 15 Jul 2014 16:45:08 -0400
Subject: [Paraview] Plugin Crashing on PV 3.12 RC2
In-Reply-To: <53C58E10.6070503@kitware.com>
References: <73D838C2-D2BA-41B7-9905-C039A702B515@bluequartz.net>
 <CADHSJjC87oZjiDdu2ga3597Vt0qeBvNLE5BmvEgyC+Z3f=ThiA@mail.gmail.com>
 <1C3DC8E9-DAD6-4047-9F9B-B5D8ABDE760B@bluequartz.net>
 <CADHSJjCPBcpbqc0mmHSfsR5LzL8Y=JSKxPjR4+4W+pHmcmSTUw@mail.gmail.com>
 <loom.20140715T212150-850@post.gmane.org>
 <CANjZAi-fPU-QW74yT0aponPQFgdDGRS3=VxTKyAqOKtT_DdcTQ@mail.gmail.com>
 <53C58E10.6070503@kitware.com>
Message-ID: <CANjZAi9ZPJndBSdW=7Evp5aHSFTYxovjg5czZ767Xz_Yfysyww@mail.gmail.com>

The syntax has changed repeatedly over the years.

I _think_ that the magic you are missing is currently buried underneath the
CMake call to pv_process_modules.

That configures a file that makes void @PLUGIN_NAME at _CombinedInitialize()
that paraview calls at run time to make those CS wrapped classes
instantiable by the process module. (or something like that)

Seb and Utkarsh know this part of the code very well. You should bug them
off list and then post on list with an simplified answer that normal humans
can follow.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Tue, Jul 15, 2014 at 4:24 PM, Matthew Woehlke <
matthew.woehlke at kitware.com> wrote:

> On 2014-07-15 16:08, David E DeMarle wrote:
> > The trick is that you have to make sure that the VTK classes are wrapped
> > into paraview's client server language and instantiable at run time.
> Check
> > the Manta View plugin for an example.
>
> Yes, I figured that... I still don't see how to actually do that,
> though. (I don't see where paraview/Plugins/MantaView - is that what you
> meant? - is doing that... or indeed, doing anything substantively
> different that what I'm doing.)
>
> I tried adding this:
>
>   include(vtkClientServerWrapping)
>   vtk_add_cs_wrapping(MyLib)
>   target_link_libraries(MyPlugin MyLibCS)
>
> ...but to no effect :-(. (It generates the CS library, but I still get
> the same error.)
>
> --
> Matthew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140715/e771aa84/attachment-0001.html>

From amiramir12345 at outlook.com  Tue Jul 15 19:54:17 2014
From: amiramir12345 at outlook.com (Amir A)
Date: Tue, 15 Jul 2014 18:54:17 -0500
Subject: [Paraview] pvti point data without sharing
Message-ID: <SNT150-W65D46A6C308BC85222BA0EEDF60@phx.gbl>

Hi Guys:
I am trying to use VTK pvti format to write distributed data and then visualize it in paraview.Chunks of data are distributed among processes and there is no ghost element shared (as my algorithm does not need it). Now the problem is that the point data format in VTK seems to need overlapping data (?).This is problematic since the processes do not share any data.I tried with cell data type and that one worked without the need for this sharing.Am I missing sth with the point data or is it supposed to be like this?
So for example assume I have 2 processes each having two 5x5 slabs (4 slabs in total).The obvious way that I supposed would work is as follows:
test.pvti:{<?xml version="1.0"?><VTKFile type="PImageData" version="0.1" byte_order="LittleEndian">    <PImageData WholeExtent="0 4 0 4 0 3" GhostLevel="0" Origin="0 0 0" Spacing="1 1 1">        <PPointData>            <PDataArray Name="value" type="Float64" format="ascii">            </PDataArray>        </PPointData>
        <Piece Extent="0 4 0 4 0 1" Source="test_0.vti"/>        <Piece Extent="0 4 0 4 2 3" Source="test_1.vti"/></PImageData></VTKFile>

}
test_0.vti:{<?xml version="1.0"?><VTKFile type="ImageData" version="0.1" byte_order="LittleEndian">    <ImageData WholeExtent="0 4 0 4 0 1" Origin="0 0 0" Spacing="1 1 1">        <Piece Extent="0 4 0 4 0 1">            <PointData Scalars="value">                <DataArray Name="value" type="Float64" format="ascii">                    0 0 0 0 0                    0 0 0 0 0                    0 0 0 0 0                    0 0 0 0 0                    0 0 0 0 0                    1 1 1 1 1                    1 1 1 1 1                    1 1 1 1 1                    1 1 1 1 1                    1 1 1 1 1                </DataArray>            </PointData>        </Piece>    </ImageData></VTKFile>
}
test_1.vti:{<?xml version="1.0"?><VTKFile type="ImageData" version="0.1" byte_order="LittleEndian">    <ImageData WholeExtent="0 4 0 4 2 3" Origin="0 0 0" Spacing="1 1 1">        <Piece Extent="0 4 0 4 2 3">            <PointData Scalars="value">                <DataArray Name="value" type="Float64" format="ascii">                    2 2 2 2 2                    2 2 2 2 2                    2 2 2 2 2                    2 2 2 2 2                    2 2 2 2 2                    3 3 3 3 3                    3 3 3 3 3                    3 3 3 3 3                    3 3 3 3 3                    3 3 3 3 3                </DataArray>            </PointData>        </Piece>    </ImageData></VTKFile>}

But this does not work. Paraview loads it but then does not show anything.It would only work if I share one of the slabs.
Any help is appreciated.
Regards,-Amir 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140715/88e5803f/attachment.html>

From shermanw at indiana.edu  Wed Jul 16 00:51:35 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Wed, 16 Jul 2014 00:51:35 -0400
Subject: [Paraview] Determining the ParaView pipeline via Python
Message-ID: <53C604D7.10807@indiana.edu>

Community,

I've been creating some simple python scripts that help me see a
simple representation of the state of ParaView.

One thing I wanted was to be able to see what changes had been
made such that a value was no longer the default.  Then, I'm going
to print this out at the beginning of my batch animation jobs, which
will then go into the log file generated by the queuing system.

So here is my function to do that for an object:

----------
def altered(object):
     if (object == None):
         return
     dup = object.__class__()
     for prop in dup.ListProperties():
         if (hasattr(object.GetProperty(prop), 'GetData')):
             if (dup.GetProperty(prop).GetData() != 
object.GetProperty(prop).GetData()):
                 print prop + ": " + str(object.GetProperty(prop))[:80] 
+ " [" + str(dup.GetProperty(prop)) + "]"
     del(dup)
     del(prop)
----------

And then I can loop over all the sources to get a handy list:

----------
for src in GetSources():
   srcp = FindSource(src[0])
   print "********************"
   print "    " + src[0] + " -- " + srcp.GetXMLLabel()
   altered(srcp)
   print "    ---------------"
   print "    Representation:"
   altered(GetDisplayProperties(srcp))
----------

So the main missing feature for me is trying to show how the sources
are linked together -- basically recreating the pipeline display,
except as ASCII text.  But I haven't yet figured out how to
programmatically determine which "sources" are connected to which.


The other thing I'd like to be able to do is report what other
field data is available from a file reader -- I can see by looking
in the .pvsm file that that data was saved, so I hope it might
be somehow available via the Python interface.



So here's some sample output from a state file I'm experimenting
with:

********************
     Glyph1 -- Glyph
GlyphTransform: <paraview.servermanager.Transform2 object at 0x163 
[<paraview.servermanager.Transform2 object at 0x1632910>]
Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
MaximumNumberofPoints: 50000 [5000]
Scalars: ['POINTS', 'mass'] [[None, '']]
Vectors: ['POINTS', 'velocity'] [[None, '']]
SetScaleFactor: 0.462090686322849 [1.0]
GlyphType: <paraview.servermanager.Sphere object at 0x16f24d0 
[<paraview.servermanager.Arrow object at 0x1632190>]
MaskPoints: 0 [1]
     ----------------
     Representations
Input: <paraview.servermanager.Glyph object at 0x162e890> [None]
SelectionPointFieldDataArrayName: 'mass' ['vtkOriginalPointIds']
ColorArrayName: ('POINT_DATA', 'mass') [('POINT_DATA', '')]
DataBounds: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0] [[5.6965768965495727e-321, 
4.7846668906873337e-316, 4.7559715579768741e-316, 
9.3872472709836843e-323, 0.0, 5.6490774253583952e-318]]
LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
ScaleFactor: 0.68949565887451203 [1.0]
********************
     TemporalParticlesToPathlines1 -- Temporal Particles To Pathlines
Input: <paraview.servermanager.LegacyVTKReader object at  [None]
MaskPoints: 1 [100]
     ----------------
     Representations
Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
SelectionPointFieldDataArrayName: 'TrailId' ['vtkOriginalPointIds']
Visibility: 0 [1]
DataBounds: [0.0, nan, nan, nan, nan, 4.243991581436479e-314] 
[[2.0018638793749296e-316, 2.0020954973496999e-316, 
4.7763681688472674e-316, 2.0021053786626168e-316, 
2.0021022166424834e-316, 2.0001733843611191e-316]]
LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
ScaleFactor: 0.45304816961288502 [1.0]
********************
     Tube1 -- Tube
Capping: 0 [1]
Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
NumberofSides: 5 [6]
Radius: 0.0060000000000000001 [1.0]
Scalars: ['POINTS', 'TrailId'] [[None, '']]
Vectors: ['POINTS', 'velocity'] [[None, '']]
     ----------------
     Representations
Input: <paraview.servermanager.Tube object at 0x162e090> [None]
SelectionPointFieldDataArrayName: 'TrailId' ['vtkOriginalPointIds']
DataBounds: [0.0, 1.2648080533535912e-321, 1.5810100666919889e 
[[5.0085616312819197e-316, 3.1620201333839779e-321, 
3.9525251667299724e-322, 5.0084066922953839e-316, 
2.3176438028922704e-310, 0.0]]
DiffuseColor: [1.0, 0.66666666666666696, 1.0] [[1.0, 1.0, 1.0]]
LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
Opacity: 0.0 [1.0]
ScaleFactor: 0.76622586250305202 [1.0]
********************
     vectors.vrml -- VRML Reader
FileName: '/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Initi ['']
     ----------------
     Representations
Input: <paraview.servermanager.VRMLReader object at 0x162 [None]
SelectionPointFieldDataArrayName: 'VRMLColor' ['vtkOriginalPointIds']
ColorArrayName: ('POINT_DATA', 'VRMLColor') [('POINT_DATA', '')]
DataBounds: [2.3715151000379834e-322, 2.7872298394991417e-316, 
[[4.7835752032362829e-316, 2.0008125076805794e-316, 
2.4209216646221081e-322, 2.0009002537392808e-316, 
2.0006433396034433e-316, 0.0]]
LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
MapScalars: 0 [1]
ScaleFactor: 1.16120505332947 [1.0]
********************
     AnnotateTime1 -- Annotate Time
Format: 'I-V2F: %.1f' ['Time: %f']
     ----------------
     Representations
Input: <paraview.servermanager.AnnotateTime object at 0x1 [None]
Opacity: 0.5 [1.0]
********************
     jhdata_* -- Legacy VTK Reader
FileNameInfo: '/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Initi [None]
FileNames: ['/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Init [['']]
TimestepValues: [0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, [[]]
     ----------------
     Representations
Input: <paraview.servermanager.LegacyVTKReader object at  [None]
SelectionPointFieldDataArrayName: 'mass' ['vtkOriginalPointIds']
Visibility: 0 [1]
ColorArrayName: ('POINT_DATA', 'mass') [('POINT_DATA', '')]
DataBounds: [2.3177925133422193e-310, 0.0, 0.0, 0.0, 0.0, 0.0] 
[[4.738173337151089e-316, 0.0, 0.0, 0.0, 0.0, 0.0]]
InterpolateScalarsBeforeMapping: 0 [1]
LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
ScaleFactor: 0.74854731559753396 [1.0]

--------------------------------------------------------------------------


Thanks for any advice.  I'll report back when I figure out a script that
does something more complete.

	Bill

--
Bill Sherman
Sr. Technology Advisor
Advanced Visualization Lab
Pervasive Technology Inst
Indiana University


From menonon at port.kobe-u.ac.jp  Wed Jul 16 02:33:23 2014
From: menonon at port.kobe-u.ac.jp (Daisuke Meno)
Date: Wed, 16 Jul 2014 15:33:23 +0900
Subject: [Paraview] ParaView Digest, Vol 123,
	Issue 25 [VR plugin cannot be built.]
Message-ID: <CAA+mDZj9V5PMZi=xw5MJZ9=CAGYZosbBnTBmdbR2B-WPuLks0Q@mail.gmail.com>

I have forgot digest reader.
Dosen't digest include any attachment ?

I got ParaView and 3rd party software by git.
So I got the latest version of ParaView.

There is no deviation from the instructions.

I got a following error.


==================
[2/2] Linking CXX shared library bin\VRPlugin.dll FAILED: cmd.exe /c
cd . && "c:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -E
vs_link_dll C:\PROGRA~2\MICROS~2.0\VC\bin\link.exe /nologo
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRAddConnectionDialog.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRAddStyleDialog.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRDockPanel.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRStarter.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRAddConnectionDialog.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRAddStyleDialog.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRConnectionManager.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRDockPanel.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRQueueHandler.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRStarter.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRPNConnection.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRPNEventListener.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRControlSliceOrientationStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRControlSlicePositionStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRGrabWorldStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRInteractorStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRInteractorStyleFactory.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRQueue.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_vtkVRTrackStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRConnectionManager.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRQueueHandler.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRPNConnection.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRPNEventListener.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRPNCallBackHandlers.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRControlSliceOrientationStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRControlSlicePositionStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRGrabWorldStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRInteractorStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRInteractorStyleFactory.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRQueue.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRTrackStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\vtkVRSpaceNavigatorGrabWorldStyle.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRStarterImplementation.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRStarterImplementation.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\pqVRDockPanelImplementation.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_pqVRDockPanelImplementation.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\VRPlugin_Plugin.obj
Plugins\VR\CMakeFiles\VRPlugin.dir\moc_VRPlugin_Plugin.obj
/out:bin\VRPlugin.dll /implib:lib\VRPlugin.lib /pdb:bin\VRPlugin.pdb
/dll /version:1.0 /machine:X86 /INCREMENTAL:NO /MANIFEST:NO
lib\vtkpqComponents-pv4.1.lib E:\immersiveParaview\vrpn-bin\vrpn.lib
lib\vtkpqApplicationComponents-pv4.1.lib lib\vtkpqComponents-pv4.1.lib
lib\vtkpqPython-pv4.1.lib lib\vtkpqCore-pv4.1.lib
lib\vtkpqWidgets-pv4.1.lib lib\QtTesting.lib
C:\Qt\4.8.6\lib\QtHelp4.lib C:\Qt\4.8.6\lib\QtSql4.lib
C:\Qt\4.8.6\lib\QtUiTools.lib C:\Qt\4.8.6\lib\QtXml4.lib
lib\vtkPVServerManagerCore-pv4.1.lib
lib\vtkPVServerImplementationCore-pv4.1.lib lib\protobuf.lib
lib\vtkPVClientServerCoreCore-pv4.1.lib
lib\vtkFiltersProgrammable-pv4.1.lib lib\vtkGUISupportQt-pv4.1.lib
C:\Qt\4.8.6\lib\QtGui4.lib C:\Qt\4.8.6\lib\QtNetwork4.lib
C:\Qt\4.8.6\lib\QtCore4.lib lib\vtkPVVTKExtensionsCore-pv4.1.lib
lib\vtkPVCommon-pv4.1.lib lib\vtkClientServer-pv4.1.lib
lib\vtkPythonInterpreter-pv4.1.lib
lib\vtkWrappingPython27Core-pv4.1.lib C:\Python27\libs\python27.lib
lib\vtkFiltersParallel-pv4.1.lib lib\vtkParallelMPI-pv4.1.lib
lib\vtkIOXMLParser-pv4.1.lib lib\vtkParallelCore-pv4.1.lib
lib\vtkIOLegacy-pv4.1.lib lib\vtkInteractionStyle-pv4.1.lib
lib\vtkFiltersModeling-pv4.1.lib lib\vtkRenderingOpenGL-pv4.1.lib
glu32.lib opengl32.lib "C:\Program Files (x86)\Microsoft
SDKs\Windows\v7.0A\Lib\d3d9.lib" wbemuuid.lib lib\vtkIOCore-pv4.1.lib
lib\vtkRenderingCore-pv4.1.lib lib\vtkFiltersExtraction-pv4.1.lib
lib\vtkFiltersStatistics-pv4.1.lib lib\vtkImagingFourier-pv4.1.lib
lib\vtkImagingCore-pv4.1.lib lib\vtkalglib-pv4.1.lib
lib\vtkFiltersGeometry-pv4.1.lib lib\vtkFiltersSources-pv4.1.lib
lib\vtkFiltersGeneral-pv4.1.lib lib\vtkFiltersCore-pv4.1.lib
lib\vtkCommonExecutionModel-pv4.1.lib
lib\vtkCommonComputationalGeometry-pv4.1.lib
lib\vtkCommonDataModel-pv4.1.lib lib\vtkCommonTransforms-pv4.1.lib
lib\vtkCommonMisc-pv4.1.lib lib\vtkCommonMath-pv4.1.lib
lib\vtkCommonSystem-pv4.1.lib lib\vtkCommonCore-pv4.1.lib
lib\vtksys-pv4.1.lib ws2_32.lib Psapi.lib kernel32.lib user32.lib
gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
comdlg32.lib advapi32.lib && cd .

???C?u???? lib\VRPlugin.lib ???I?u?W?F?N?g lib\VRPlugin.exp ????????
pqVRDockPanel.obj : error LNK2019: ?????????O???V???{??
"__declspec(dllimport)
public: class vtkCamera * __thiscall
vtkSMRenderViewProxy::GetActiveCamera(void)"
(__imp_?GetActiveCamera at vtkSMRenderViewProxy@@QAEPAVvtkCamera@@XZ) ??????
"private: void __thiscall pqVRDockPanel::setActiveView(class pqView *)"
(?setActiveView at pqVRDockPanel@@AAEXPAVpqView@@@Z) ???Q?????????????B
vtkVRGrabWorldStyle.obj : error LNK2001: ?O???V???{??
""__declspec(dllimport)
public: class vtkCamera * __thiscall
vtkSMRenderViewProxy::GetActiveCamera(void)"(__imp_?GetActiveCamera at vtkSMRenderViewProxy@@QAEPAVvtkCamera@@XZ)"
?????????????B vtkVRSpaceNavigatorGrabWorldStyle.obj : error LNK2001:
?O???V???{??
""__declspec(dllimport) public: class vtkCamera * __thiscall
vtkSMRenderViewProxy::GetActiveCamera(void)"
(__imp_?GetActiveCamera at vtkSMRenderViewProxy@@QAEPAVvtkCamera@@XZ)"
?????????????B vtkVRSpaceNavigatorGrabWorldStyle.obj : error LNK2001:
?O???V???{??
""__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl
vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)"
(__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)"
?????????????B pqVRQueueHandler.obj : error LNK2019: ?????????O???V???{??
"__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl
vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)"
(__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z) ??????
"private: void __thiscall pqVRQueueHandler::render(void)"
(?render at pqVRQueueHandler@@AAEXXZ) ???Q?????????????B
vtkVRControlSliceOrientationStyle.obj : error LNK2001: ?O???V???{??
""__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl
vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)"
(__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)"
?????????????B vtkVRControlSlicePositionStyle.obj : error LNK2001: ?O???V???{??
""__declspec(dllimport) public: static class vtkSMRenderViewProxy * __cdecl
vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)"
(__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)"
?????????????B vtkVRGrabWorldStyle.obj : error LNK2001: ?O???V???{??
""__declspec(dllimport)
public: static class vtkSMRenderViewProxy * __cdecl
vtkSMRenderViewProxy::SafeDownCast(class vtkObjectBase *)"
(__imp_?SafeDownCast at vtkSMRenderViewProxy@@SAPAV1 at PAVvtkObjectBase@@@Z)"
?????????????B bin\VRPlugin.dll : fatal error LNK1120: ?O???Q?? 2
?????????????B LINK failed. with 1120 ninja: build stopped: subcommand
failed.
===================

Thanks
Daisuke



2014-07-16 2:09 GMT+09:00 William Sherman <shermanw at indiana.edu>:
> On 7/15/14 12:47 AM, paraview-request at paraview.org wrote:
>>
>> Message: 2
>> Date: Tue, 15 Jul 2014 13:22:02 +0900
>> From: Daisuke Meno<menonon at port.kobe-u.ac.jp>
>> To:paraview at paraview.org
>> Subject: [Paraview] VR plugin cannot be built.
>
>
> Hello,
>
>> VR plugin cannot be built on Windows7.
>> I have followed this page.
>> http://www.paraview.org/Wiki/ParaView/VRPN_with_MS-MPI
>>
>> But I got errors.
>> Sorry, text files include some Japanese characters.
>>
>> Would you give me any solution ?
>
>
> You'll have to give us some details on what the errors were
> and what version of ParaView you have downloaded -- and also,
> were there any deviations from the instructions on the Wiki
> page.
>
>         Bill
>
>> Thanks
>> Daisuke
>>
>> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Kobe University
>> Education Center on Computational Science and Engineering
>
>
> --
> Bill Sherman
> Sr. Technology Advisor
> Advanced Visualization Lab
> Pervasive Technology Inst
> Indiana University
> shermanw at indiana.edu



-- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Kobe University
Education Center on Computational Science and Engineering

                Daisuke MENO
    (Limited-term Assistant Professor)

 Integrated Research Center @ Port Island
      078-599-6723     080-3136-9659
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

From victorsv at gmail.com  Wed Jul 16 05:04:17 2014
From: victorsv at gmail.com (victor sv)
Date: Wed, 16 Jul 2014 11:04:17 +0200
Subject: [Paraview]  PVD file format
Message-ID: <CA+Wz_Fzovy4rsZVWPr__8NqxM7cfM-MLk5i0hSDqvEKoqcFq2g@mail.gmail.com>

Hi all,

i'm searching for a description for the PVD file format and i don't find
any official document. Is there any official document describing the PVD
format?

I have some doubts:

Can exists several collection sections?,
Is there another type of labels, instead of collection?

Thanks,
V?ctor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/7b25a42f/attachment.html>

From a.huebl at hzdr.de  Wed Jul 16 05:28:06 2014
From: a.huebl at hzdr.de (Huebl, Axel)
Date: Wed, 16 Jul 2014 11:28:06 +0200
Subject: [Paraview] Building Piston
In-Reply-To: <1B75FE20F814944EA42F9A3A76476C253C4A76C358@HQMAIL03.nvidia.com>
References: <1B75FE20F814944EA42F9A3A76476C253C4A76C358@HQMAIL03.nvidia.com>
Message-ID: <53C645A6.1020406@hzdr.de>

Hi,

looking at the piston code [1] in piston/piston_math.h that looks like a
thrust-related problem to me.

```
  #if THRUST_DEVICE_BACKEND == THRUST_DEVICE_BACKEND_CUDA

  #include "cuda_runtime.h"

  #else

  #include <thrust/detail/config.h>


  typedef struct float3
  // ...
```

Checking Piston's `CMakeLists.txt` it looks like it might be necessary
to set -DUSE_CUDA=ON or -DTHRUST_DIR=... with cmake?

The sm_10 warnings could be avoided by specifying the target platform.


Best,
Axel

[1] https://github.com/losalamos/PISTON/blob/master/piston/piston_math.h

On 15.07.2014 00:34, Praveen Narayanan wrote:
> Hi
> 
>  
> 
> I have been trying to build piston from the paraview source (on
> website), and standalone piston from the lanl website.
> 
>  
> 
> I run into this error:
> 
>  
> 
> urces
> 
> [ 32%] Built target vtkRenderingCore
> 
> [ 32%] Built target vtkParseOGLExt
> 
> [ 32%] Built target vtkEncodeString
> 
> [ 32%] Built target vtkEncodeString-launcher
> 
> [ 32%] Built target vtkRenderingOpenGL
> 
> [ 32%] *Building NVCC (Device) object
> VTK/Accelerators/Piston/CMakeFiles/cuda_compile.dir//./cuda_compile_generated_vtkPistonThreshold.cu.o*
> 
> nvcc warning : The 'compute_10' and 'sm_10' architectures are
> deprecated, and may be removed in a future release.
> 
> nvcc warning : The 'compute_10' and 'sm_10' architectures are
> deprecated, and may be removed in a future release.
> 
> /home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(13):
> error: invalid redeclaration of type name "float3"
> 
> /usr/local/cuda/include/vector_types.h(394): here
> 
>  
> 
> /home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(18):
> error: invalid redeclaration of type name "float4"
> 
> /usr/local/cuda/include/vector_types.h(395): here
> 
>  
> 
> /home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(23):
> error: invalid redeclaration of type name "uint3"
> 
> /usr/local/cuda/include/vector_types.h(381): here
> 
>  
> 
> /home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(29):
> error: cannot overload functions distinguished by return type alone
> 
>  
> 
> /home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(34):
> error: cannot overload functions distinguished by return type alone
> 
>  
> 
> ?.
> 
>  
> 
>  
> 
> Several such errors appear. Float2, float3 etc are cuda specific things,
> so I am not sure what is happening here.
> 
>  
> 
> Ideas?
> 
> Thanks
> 
> Praveen
> 
>  
> 
> Applied Engineer
> 
> NVIDIA
> 
>  
> 
> http://devblogs.nvidia.com/parallelforall/
> 
>  
> 
> ------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and
> may contain confidential information.  Any unauthorized review, use,
> disclosure or distribution is prohibited.  If you are not the intended
> recipient, please contact the sender by reply email and destroy all
> copies of the original message.
> ------------------------------------------------------------------------
> 
> 
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
> 

-- 

Axel Huebl
Diploma Student
Phone +49 351 260 3582
https://www.hzdr.de/crp
Computational Radiation Physics
Laser Particle Acceleration Division
Helmholtz-Zentrum Dresden - Rossendorf e.V.

Bautzner Landstrasse 400, 01328 Dresden
POB 510119, D-01314 Dresden
Vorstand: Prof. Dr.Dr.h.c. R. Sauerbrey
          Prof. Dr.Dr.h.c. P. Joehnk
VR 1693 beim Amtsgericht Dresden

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5002 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/dfa2660c/attachment.bin>

From schneider at vision.ee.ethz.ch  Wed Jul 16 06:50:25 2014
From: schneider at vision.ee.ethz.ch (Matthias Schneider)
Date: Wed, 16 Jul 2014 12:50:25 +0200
Subject: [Paraview] Slice representation
Message-ID: <53C658F1.5040200@vision.ee.ethz.ch>

Hi,

I am trying to visualize volumetric image data (Uniform Rectilinear 
Grid) as single axial slices. The built-in "Slice" representation in 
ParaView has a rather 'non-intuitive' behavior -- from an 
image-processing point of view where I (would like to) consider a point 
as the center of a single voxel (as in ITK) rather than the voxel corner 
as used for Paraview's slice representation, which essentially results 
in slightly 'squeezed' pixels.

For example, consider an axial slice of 3x3 voxels with an isotropic 
voxel spacing of 1cm. Paraview's slice representation then renders a 
quad with the same *bounds* as the slice, i.e. the quad dimensions are 
2cm in each direction. The superimposed texture, however, shows 3x3 
voxels, which results in an effective/apparent voxel size of 2/3cm.

There might be different applications/data where this kind of 
representation is meaningful/desired (?) but it is rather misleading 
when trying to visualize volumetric image data.
Could anybody possibly comment on whether or not this behavior is 
intentional?

As I could not find an easy way to adjust this behavior for my needs, I 
was trying to include a 'voxel-centric slice' representation following 
the 'Plugin HowTo'. I more or less succeeded by adding my own data 
mappers that eventually use a modified version of vtkTexturePainter 
which renders the quad with outer bounds increased by half the spacing 
of the input slice - not quite sure if that will eventually have some 
other unexpected side effects.

There are two rather GUI-related issues that I did not get right yet.

1. How can I set the panel visibility of the "Slicing" property group to 
default for the modified slice representation?
The representation xml file uses the 
panel_visibility_default_for_representation attribute to select a single 
representation for default visibility in the SliceRepresenation proxy:

<ExposedProperties>
<PropertyGroup label="Slicing">
   <Property name="SliceMode"
             panel_visibility="advanced"
             panel_visibility_default_for_representation="slice" />
   <Property name="Slice"
             panel_visibility="advanced"
             panel_visibility_default_for_representation="slice" />
</PropertyGroup>
</ExposedProperties>

Is there any way to add the modified slice representation without 
duplicating the GUI elements?

Also not quite sure what the meaning of the share property exception is:
<ShareProperties subproxy="SliceRepresentation">
   <Exception name="Input" />
   <Exception name="Visibility" />
</ShareProperties>
I couldn't find any proper documentation for these parts but it might be 
related to the visibility problem.

2. When loading new image data from a file into ParaView and selecting 
the modified slice representation, I always get a 'Failed to locate 
selected scalars. Will use image scalars by default.' error. Doing the 
same with the built-in slice representation, the 'MetaImage' point 
attribute containing the image data gets selected automatically. The 
error vanishes of course when I manually select the point attribute. Am 
I missing something here or what is the 'trick' to automatically select 
the point attribute?

Any hint is appreciated very much!

I am more than happy to provide the source code if that helps.


Kind regards,
Matthias

From aashish.chaudhary at kitware.com  Wed Jul 16 09:06:53 2014
From: aashish.chaudhary at kitware.com (Aashish Chaudhary)
Date: Wed, 16 Jul 2014 09:06:53 -0400
Subject: [Paraview] VR plugin cannot be built.
In-Reply-To: <CAA+mDZg5TL+98jKh7hd4b_76treKV8uA5f6GZ70NprHupM0Cmg@mail.gmail.com>
References: <CAA+mDZg5TL+98jKh7hd4b_76treKV8uA5f6GZ70NprHupM0Cmg@mail.gmail.com>
Message-ID: <CAEw35Z82Mo1K=Qc_9a1FEatZj3TKsDNMAa_oy=Ti9yC=V=Vb=Q@mail.gmail.com>

What version of ParaView is this?

Thanks,



On Tue, Jul 15, 2014 at 12:22 AM, Daisuke Meno <menonon at port.kobe-u.ac.jp>
wrote:

> Hi,
>
> VR plugin cannot be built on Windows7.
> I have followed this page.
> http://www.paraview.org/Wiki/ParaView/VRPN_with_MS-MPI
>
> But I got errors.
> Sorry, text files include some Japanese characters.
>
> Would you give me any solution ?
>
> Thanks
> Daisuke
>
> --
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Kobe University
> Education Center on Computational Science and Engineering
>
>                 Daisuke MENO
>     (Limited-term Assistant Professor)
>
>  Integrated Research Center @ Port Island
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>


-- 



*| Aashish Chaudhary | Technical Leader         | Kitware Inc.            *
*| http://www.kitware.com/company/team/chaudhary.html
<http://www.kitware.com/company/team/chaudhary.html>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/821bd690/attachment.html>

From simon.m.su.ctr at mail.mil  Wed Jul 16 11:51:01 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Wed, 16 Jul 2014 15:51:01 +0000
Subject: [Paraview] filter to use for data analysis in ParaView
	(UNCLASSIFIED)
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CDD741@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hello,

I am trying to do some data analysis in ParaView. The simulation data shows
the deformation of a surface. What pipeline can I use to find out the
distance of the deformed surface from its original mesh? Can it be done with
filters like Plot Over Line?

Any suggestions is greatly appreciated

Thanks
-simon

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 9990 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/6809e6d2/attachment-0001.bin>

From matthew.woehlke at kitware.com  Wed Jul 16 12:28:14 2014
From: matthew.woehlke at kitware.com (Matthew Woehlke)
Date: Wed, 16 Jul 2014 16:28:14 +0000 (UTC)
Subject: [Paraview] Plugin Crashing on PV 3.12 RC2
References: <73D838C2-D2BA-41B7-9905-C039A702B515@bluequartz.net>
 <CADHSJjC87oZjiDdu2ga3597Vt0qeBvNLE5BmvEgyC+Z3f=ThiA@mail.gmail.com>
 <1C3DC8E9-DAD6-4047-9F9B-B5D8ABDE760B@bluequartz.net>
 <CADHSJjCPBcpbqc0mmHSfsR5LzL8Y=JSKxPjR4+4W+pHmcmSTUw@mail.gmail.com>
 <loom.20140715T212150-850@post.gmane.org>
 <CANjZAi-fPU-QW74yT0aponPQFgdDGRS3=VxTKyAqOKtT_DdcTQ@mail.gmail.com>
 <53C58E10.6070503@kitware.com>
 <CANjZAi9ZPJndBSdW=7Evp5aHSFTYxovjg5czZ767Xz_Yfysyww@mail.gmail.com>
Message-ID: <loom.20140716T182207-740@post.gmane.org>

On 2014-07-15 16:45, David E DeMarle wrote:
> The syntax has changed repeatedly over the years.
> 
> I _think_ that the magic you are missing is currently buried underneath the 
> CMake call to pv_process_modules.
> 
> That configures a file that makes void @PLUGIN_NAME at _CombinedInitialize() 
> that paraview calls at run time to make those CS wrapped classes 
> instantiable by the process module. (or something like that)

Thanks! That was the hint I needed... chasing down _CombinedInitialize 
led me to PLUGIN_EXTRA_CS_INITS, which is set by the CS_KITS argument 
to add_paraview_plugin.

So now I am doing this:

  # library/CMakeLists.txt

  vtk_module(MyLib)
  vtk_module_library(MyLib ${MyLib_sources})


  # plugin/CMakeLists.txt

  include(vtkClientServerWrapping)

  vtk_add_cs_wrapping(MyLib)
  add_paraview_plugin(MyPlugin "1.0" ... CS_KITS MyLib)
  target_link_libraries(MyPlugin MyLib MyLibCS)

...and it works :-D.

-- 
Matthew


From wascott at sandia.gov  Wed Jul 16 13:20:09 2014
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 16 Jul 2014 17:20:09 +0000
Subject: [Paraview] [EXTERNAL] filter to use for data analysis in
 ParaView	(UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CDD741@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CDD741@umechp9h.easf.csd.disa.mil>
Message-ID: <93a6cdf07e174227b0637405e2cbe26e@ES05AMSNLNT.srn.sandia.gov>

Simon,
Could you read your data in twice, deform only one of the them, and use the sources/ ruler?

Other thing I can think of is to start at time 0, undeformed.  Select your point.  Open a spreadsheet window.  Select point data.  Show only Selected Nodes/Elements.  Write down this location.  Now, go to your desired deformed time step.  You now have the second location, and can figure out the distance.

Alan

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Su, Simon M CTR USARMY ARL (US)
Sent: Wednesday, July 16, 2014 9:51 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] filter to use for data analysis in ParaView (UNCLASSIFIED)

Classification: UNCLASSIFIED
Caveats: NONE

Hello,

I am trying to do some data analysis in ParaView. The simulation data shows the deformation of a surface. What pipeline can I use to find out the distance of the deformed surface from its original mesh? Can it be done with filters like Plot Over Line?

Any suggestions is greatly appreciated

Thanks
-simon

Classification: UNCLASSIFIED
Caveats: NONE



From simon.m.su.ctr at mail.mil  Wed Jul 16 13:27:40 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Wed, 16 Jul 2014 17:27:40 +0000
Subject: [Paraview] [EXTERNAL] filter to use for data analysis in
 ParaView	(UNCLASSIFIED)
In-Reply-To: <93a6cdf07e174227b0637405e2cbe26e@ES05AMSNLNT.srn.sandia.gov>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CDD741@umechp9h.easf.csd.disa.mil>
 <93a6cdf07e174227b0637405e2cbe26e@ES05AMSNLNT.srn.sandia.gov>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CDD78C@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hi Alan,

Yes I believe can read the data in twice or load the undeformed data and let
the deformation run and get the differences. Thanks for the idea. I am going
to give it a try.

Thanks
-simon

-----Original Message-----
From: Scott, W Alan [mailto:wascott at sandia.gov] 
Sent: Wednesday, July 16, 2014 1:20 PM
To: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org
Subject: RE: [EXTERNAL] [Paraview] filter to use for data analysis in
ParaView (UNCLASSIFIED)

Simon,
Could you read your data in twice, deform only one of the them, and use the
sources/ ruler?

Other thing I can think of is to start at time 0, undeformed.  Select your
point.  Open a spreadsheet window.  Select point data.  Show only Selected
Nodes/Elements.  Write down this location.  Now, go to your desired deformed
time step.  You now have the second location, and can figure out the
distance.

Alan

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Su, Simon
M CTR USARMY ARL (US)
Sent: Wednesday, July 16, 2014 9:51 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] filter to use for data analysis in ParaView
(UNCLASSIFIED)

Classification: UNCLASSIFIED
Caveats: NONE

Hello,

I am trying to do some data analysis in ParaView. The simulation data shows
the deformation of a surface. What pipeline can I use to find out the
distance of the deformed surface from its original mesh? Can it be done with
filters like Plot Over Line?

Any suggestions is greatly appreciated

Thanks
-simon

Classification: UNCLASSIFIED
Caveats: NONE



Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/094f2f76/attachment.bin>

From amiramir12345 at outlook.com  Wed Jul 16 15:01:16 2014
From: amiramir12345 at outlook.com (Amir A)
Date: Wed, 16 Jul 2014 14:01:16 -0500
Subject: [Paraview] =?cp1256?q?pvti_point_data_without_sharing=FE?=
Message-ID: <SNT150-W29DBCCD8741D6AD73F1F56EDF70@phx.gbl>


(The previous message got scrambled ...)

Hi Guys:

I am trying to use VTK pvti format to write distributed data and then visualize it in paraview.?
Chunks of data are distributed among processes and there is no ghost element shared (as my algorithm does not need it).?
Now the problem is that the point data format in VTK seems to need overlapping data (?).?
This is problematic since the processes do not share any data.?
I tried with cell data type and that one worked without the need for this sharing.?

Am I missing sth with the point data or is it supposed to be like this?


So for example assume I have 2 processes each having two 5x5 slabs (4 slabs in total).?
The obvious way that I supposed would work is as follows:?

test.pvti:
{
<?xml version="1.0"?>
<VTKFile type="PImageData" version="0.1" byte_order="LittleEndian">
? ? <PImageData WholeExtent="0 4 0 4 0 3" GhostLevel="0" Origin="0 0 0" Spacing="1 1 1">
? ? ? ? <PPointData>
? ? ? ? ? ? <PDataArray Name="value" type="Float64" format="ascii">
? ? ? ? ? ? </PDataArray>
? ? ? ? </PPointData>?
? ? ? ? ? ? ? ? ? ??
? ? ? ? <Piece Extent="0 4 0 4 0 1" Source="test_00.vti"/>
? ? ? ? <Piece Extent="0 4 0 4 2 3" Source="test_01.vti"/>
</PImageData> ? ? ??
</VTKFile>
}



test_00.vti:
{
<?xml version="1.0"?>
<VTKFile type="ImageData" version="0.1" byte_order="LittleEndian">
? ? <ImageData WholeExtent="0 4 0 4 0 1" Origin="0 0 0" Spacing="1 1 1">
? ? ? ? <Piece Extent="0 4 0 4 0 1">
? ? ? ? ? ? <PointData Scalars="value">
? ? ? ? ? ? ? ? <DataArray Name="value" type="Float64" format="ascii">
? ? ? ? ? ? ? ? ? ? 0 0 0 0 0
? ? ? ? ? ? ? ? ? ? 0 0 0 0 0
? ? ? ? ? ? ? ? ? ? 0 0 0 0 0
? ? ? ? ? ? ? ? ? ? 0 0 0 0 0
? ? ? ? ? ? ? ? ? ? 0 0 0 0 0
? ? ? ? ? ? ? ? ? ? 1 1 1 1 1
? ? ? ? ? ? ? ? ? ? 1 1 1 1 1
? ? ? ? ? ? ? ? ? ? 1 1 1 1 1
? ? ? ? ? ? ? ? ? ? 1 1 1 1 1
? ? ? ? ? ? ? ? ? ? 1 1 1 1 1
? ? ? ? ? ? ? ? </DataArray>
? ? ? ? ? ? </PointData>
? ? ? ? </Piece>
? ? </ImageData>
</VTKFile>
}


test_01.vti:
{
<?xml version="1.0"?>
<VTKFile type="ImageData" version="0.1" byte_order="LittleEndian">
? ? <ImageData WholeExtent="0 4 0 4 2 3" Origin="0 0 0" Spacing="1 1 1">
? ? ? ? <Piece Extent="0 4 0 4 2 3">
? ? ? ? ? ? <PointData Scalars="value">
? ? ? ? ? ? ? ? <DataArray Name="value" type="Float64" format="ascii">
? ? ? ? ? ? ? ? ? ? 2 2 2 2 2
? ? ? ? ? ? ? ? ? ? 2 2 2 2 2
? ? ? ? ? ? ? ? ? ? 2 2 2 2 2
? ? ? ? ? ? ? ? ? ? 2 2 2 2 2
? ? ? ? ? ? ? ? ? ? 2 2 2 2 2
? ? ? ? ? ? ? ? ? ? 3 3 3 3 3
? ? ? ? ? ? ? ? ? ? 3 3 3 3 3
? ? ? ? ? ? ? ? ? ? 3 3 3 3 3
? ? ? ? ? ? ? ? ? ? 3 3 3 3 3
? ? ? ? ? ? ? ? ? ? 3 3 3 3 3
? ? ? ? ? ? ? ? </DataArray>
? ? ? ? ? ? </PointData>
? ? ? ? </Piece>
? ? </ImageData>
</VTKFile>
}




But this does not work. Paraview loads it but then does not show anything.?
It would only work if I share one of the slabs, that is share the 111... slab or the 222... slab.?

Any help is appreciated.?

You can download the files at:

https://www.dropbox.com/sh/8lthk9ssxpyakbt/AAAdrHy9f8IGbWmtooJ3O5uoa




Regards,?
-Amir 		 	   		  

From mta2122 at columbia.edu  Wed Jul 16 16:45:59 2014
From: mta2122 at columbia.edu (Miguel Arriaga)
Date: Wed, 16 Jul 2014 16:45:59 -0400
Subject: [Paraview] Types of elements
Message-ID: <CAPjQ4T4meONkbbWZBHReCp0A+yTLduH4baQWAGkCG3C1xKTnaA@mail.gmail.com>

Hi,
In the FEM software that I'm using I have single node elements that
correspond to special nodal boundary conditions. I need to tell the
software which type of paraview element is a single node element because if
I leave it empty paraview complains with the error: "Cannot read cell types
from Cells in piece 0 because the "types" array is not long enough."

Q1: Is there a table/list that shows the type of elements that paraview has
and what are their respective numbers? If yes where is it?

Q2: Does paraview have such a thing as a single node element?

Best regards,
Miguel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/4405859b/attachment.html>

From andy.bauer at kitware.com  Wed Jul 16 16:53:53 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 16 Jul 2014 16:53:53 -0400
Subject: [Paraview] Types of elements
In-Reply-To: <CAPjQ4T4meONkbbWZBHReCp0A+yTLduH4baQWAGkCG3C1xKTnaA@mail.gmail.com>
References: <CAPjQ4T4meONkbbWZBHReCp0A+yTLduH4baQWAGkCG3C1xKTnaA@mail.gmail.com>
Message-ID: <CAMaOp+ECTeiwsY7dfB7HkAbpHdsSJC=yM2dZdS+2tapJfhT6rA@mail.gmail.com>

Hi,

http://www.tukizakura.org/~fujim2/cgi-bin/pukiwiki/pukiwiki.php?plugin=ref&page=UnstructuredGrid%B7%C1%BC%B0%20Legacy&src=VTK_UnstructuredGrid_CellTypeFigure.PNG
has a picture of the cell types. It sounds like you want the VTK_VERTEX one.

Regards,
Andy


On Wed, Jul 16, 2014 at 4:45 PM, Miguel Arriaga <mta2122 at columbia.edu>
wrote:

> Hi,
> In the FEM software that I'm using I have single node elements that
> correspond to special nodal boundary conditions. I need to tell the
> software which type of paraview element is a single node element because if
> I leave it empty paraview complains with the error: "Cannot read cell types
> from Cells in piece 0 because the "types" array is not long enough."
>
> Q1: Is there a table/list that shows the type of elements that paraview
> has and what are their respective numbers? If yes where is it?
>
> Q2: Does paraview have such a thing as a single node element?
>
> Best regards,
> 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
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/e60e110d/attachment-0001.html>

From mta2122 at columbia.edu  Wed Jul 16 17:01:44 2014
From: mta2122 at columbia.edu (Miguel Arriaga)
Date: Wed, 16 Jul 2014 17:01:44 -0400
Subject: [Paraview] Types of elements
In-Reply-To: <CAMaOp+ECTeiwsY7dfB7HkAbpHdsSJC=yM2dZdS+2tapJfhT6rA@mail.gmail.com>
References: <CAPjQ4T4meONkbbWZBHReCp0A+yTLduH4baQWAGkCG3C1xKTnaA@mail.gmail.com>
 <CAMaOp+ECTeiwsY7dfB7HkAbpHdsSJC=yM2dZdS+2tapJfhT6rA@mail.gmail.com>
Message-ID: <CAPjQ4T4nL1rJobZPHrd0gE_DNzk2i9C_+4x6QCsOZSrEWEoExQ@mail.gmail.com>

Thank you so much! It worked like a charm!


On Wed, Jul 16, 2014 at 4:53 PM, Andy Bauer <andy.bauer at kitware.com> wrote:

> Hi,
>
>
> http://www.tukizakura.org/~fujim2/cgi-bin/pukiwiki/pukiwiki.php?plugin=ref&page=UnstructuredGrid%B7%C1%BC%B0%20Legacy&src=VTK_UnstructuredGrid_CellTypeFigure.PNG
> has a picture of the cell types. It sounds like you want the VTK_VERTEX one.
>
> Regards,
> Andy
>
>
> On Wed, Jul 16, 2014 at 4:45 PM, Miguel Arriaga <mta2122 at columbia.edu>
> wrote:
>
>> Hi,
>> In the FEM software that I'm using I have single node elements that
>> correspond to special nodal boundary conditions. I need to tell the
>> software which type of paraview element is a single node element because if
>> I leave it empty paraview complains with the error: "Cannot read cell types
>> from Cells in piece 0 because the "types" array is not long enough."
>>
>> Q1: Is there a table/list that shows the type of elements that paraview
>> has and what are their respective numbers? If yes where is it?
>>
>> Q2: Does paraview have such a thing as a single node element?
>>
>> Best regards,
>> 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
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/1633e5a0/attachment.html>

From andy.bauer at kitware.com  Wed Jul 16 17:07:15 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 16 Jul 2014 17:07:15 -0400
Subject: [Paraview] Determining the ParaView pipeline via Python
In-Reply-To: <53C604D7.10807@indiana.edu>
References: <53C604D7.10807@indiana.edu>
Message-ID: <CAMaOp+GBWv4nFbJ_L9joRxJRbsHjfjZniu=Vdj3J+szzhC8Fjg@mail.gmail.com>

Hi Bill,

A couple of hopefully helpful hints:

   - Maybe using a filter's Input object is enough to get the pipeline
   connections you want (i.e. aa = bb.Input). This though assumes you're
   working from the sink in the pipeline as opposed to a source.
   - As for getting the available arrays for a filter, you can do something
   like:

for da in range(aa.PointData.NumberOfArrays):
  bb.PointData.GetArray(da)


   - There was work on only writing out Python scripts with non-default
   values which made the scripts much shorter. Somewhere there was an option
   to specify whether to write out all values of the objects for trace and
   python state or just the non-defaults but I can't find it now. It looks
   like what you have already works but just wanted to mention that.

Does this answer your questions?


Regards,

Andy


On Wed, Jul 16, 2014 at 12:51 AM, Bill Sherman <shermanw at indiana.edu> wrote:

> Community,
>
> I've been creating some simple python scripts that help me see a
> simple representation of the state of ParaView.
>
> One thing I wanted was to be able to see what changes had been
> made such that a value was no longer the default.  Then, I'm going
> to print this out at the beginning of my batch animation jobs, which
> will then go into the log file generated by the queuing system.
>
> So here is my function to do that for an object:
>
> ----------
> def altered(object):
>     if (object == None):
>         return
>     dup = object.__class__()
>     for prop in dup.ListProperties():
>         if (hasattr(object.GetProperty(prop), 'GetData')):
>             if (dup.GetProperty(prop).GetData() !=
> object.GetProperty(prop).GetData()):
>                 print prop + ": " + str(object.GetProperty(prop))[:80] +
> " [" + str(dup.GetProperty(prop)) + "]"
>     del(dup)
>     del(prop)
> ----------
>
> And then I can loop over all the sources to get a handy list:
>
> ----------
> for src in GetSources():
>   srcp = FindSource(src[0])
>   print "********************"
>   print "    " + src[0] + " -- " + srcp.GetXMLLabel()
>   altered(srcp)
>   print "    ---------------"
>   print "    Representation:"
>   altered(GetDisplayProperties(srcp))
> ----------
>
> So the main missing feature for me is trying to show how the sources
> are linked together -- basically recreating the pipeline display,
> except as ASCII text.  But I haven't yet figured out how to
> programmatically determine which "sources" are connected to which.
>
>
> The other thing I'd like to be able to do is report what other
> field data is available from a file reader -- I can see by looking
> in the .pvsm file that that data was saved, so I hope it might
> be somehow available via the Python interface.
>
>
>
> So here's some sample output from a state file I'm experimenting
> with:
>
> ********************
>     Glyph1 -- Glyph
> GlyphTransform: <paraview.servermanager.Transform2 object at 0x163
> [<paraview.servermanager.Transform2 object at 0x1632910>]
> Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
> MaximumNumberofPoints: 50000 [5000]
> Scalars: ['POINTS', 'mass'] [[None, '']]
> Vectors: ['POINTS', 'velocity'] [[None, '']]
> SetScaleFactor: 0.462090686322849 [1.0]
> GlyphType: <paraview.servermanager.Sphere object at 0x16f24d0
> [<paraview.servermanager.Arrow object at 0x1632190>]
> MaskPoints: 0 [1]
>     ----------------
>     Representations
> Input: <paraview.servermanager.Glyph object at 0x162e890> [None]
> SelectionPointFieldDataArrayName: 'mass' ['vtkOriginalPointIds']
> ColorArrayName: ('POINT_DATA', 'mass') [('POINT_DATA', '')]
> DataBounds: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0] [[5.6965768965495727e-321,
> 4.7846668906873337e-316, 4.7559715579768741e-316, 9.3872472709836843e-323,
> 0.0, 5.6490774253583952e-318]]
> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
> ScaleFactor: 0.68949565887451203 [1.0]
> ********************
>     TemporalParticlesToPathlines1 -- Temporal Particles To Pathlines
> Input: <paraview.servermanager.LegacyVTKReader object at  [None]
> MaskPoints: 1 [100]
>     ----------------
>     Representations
> Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
> SelectionPointFieldDataArrayName: 'TrailId' ['vtkOriginalPointIds']
> Visibility: 0 [1]
> DataBounds: [0.0, nan, nan, nan, nan, 4.243991581436479e-314]
> [[2.0018638793749296e-316, 2.0020954973496999e-316,
> 4.7763681688472674e-316, 2.0021053786626168e-316, 2.0021022166424834e-316,
> 2.0001733843611191e-316]]
> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
> ScaleFactor: 0.45304816961288502 [1.0]
> ********************
>     Tube1 -- Tube
> Capping: 0 [1]
> Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
> NumberofSides: 5 [6]
> Radius: 0.0060000000000000001 [1.0]
> Scalars: ['POINTS', 'TrailId'] [[None, '']]
> Vectors: ['POINTS', 'velocity'] [[None, '']]
>     ----------------
>     Representations
> Input: <paraview.servermanager.Tube object at 0x162e090> [None]
> SelectionPointFieldDataArrayName: 'TrailId' ['vtkOriginalPointIds']
> DataBounds: [0.0, 1.2648080533535912e-321, 1.5810100666919889e
> [[5.0085616312819197e-316, 3.1620201333839779e-321,
> 3.9525251667299724e-322, 5.0084066922953839e-316, 2.3176438028922704e-310,
> 0.0]]
> DiffuseColor: [1.0, 0.66666666666666696, 1.0] [[1.0, 1.0, 1.0]]
> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
> Opacity: 0.0 [1.0]
> ScaleFactor: 0.76622586250305202 [1.0]
> ********************
>     vectors.vrml -- VRML Reader
> FileName: '/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Initi ['']
>     ----------------
>     Representations
> Input: <paraview.servermanager.VRMLReader object at 0x162 [None]
> SelectionPointFieldDataArrayName: 'VRMLColor' ['vtkOriginalPointIds']
> ColorArrayName: ('POINT_DATA', 'VRMLColor') [('POINT_DATA', '')]
> DataBounds: [2.3715151000379834e-322, 2.7872298394991417e-316,
> [[4.7835752032362829e-316, 2.0008125076805794e-316,
> 2.4209216646221081e-322, 2.0009002537392808e-316, 2.0006433396034433e-316,
> 0.0]]
> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
> MapScalars: 0 [1]
> ScaleFactor: 1.16120505332947 [1.0]
> ********************
>     AnnotateTime1 -- Annotate Time
> Format: 'I-V2F: %.1f' ['Time: %f']
>     ----------------
>     Representations
> Input: <paraview.servermanager.AnnotateTime object at 0x1 [None]
> Opacity: 0.5 [1.0]
> ********************
>     jhdata_* -- Legacy VTK Reader
> FileNameInfo: '/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Initi [None]
> FileNames: ['/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Init [['']]
> TimestepValues: [0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, [[]]
>     ----------------
>     Representations
> Input: <paraview.servermanager.LegacyVTKReader object at  [None]
> SelectionPointFieldDataArrayName: 'mass' ['vtkOriginalPointIds']
> Visibility: 0 [1]
> ColorArrayName: ('POINT_DATA', 'mass') [('POINT_DATA', '')]
> DataBounds: [2.3177925133422193e-310, 0.0, 0.0, 0.0, 0.0, 0.0]
> [[4.738173337151089e-316, 0.0, 0.0, 0.0, 0.0, 0.0]]
> InterpolateScalarsBeforeMapping: 0 [1]
> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
> ScaleFactor: 0.74854731559753396 [1.0]
>
> --------------------------------------------------------------------------
>
>
> Thanks for any advice.  I'll report back when I figure out a script that
> does something more complete.
>
>         Bill
>
> --
> Bill Sherman
> Sr. Technology Advisor
> Advanced Visualization Lab
> Pervasive Technology Inst
> Indiana University
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/e1728a90/attachment.html>

From scott.wittenburg at kitware.com  Wed Jul 16 17:34:31 2014
From: scott.wittenburg at kitware.com (Scott Wittenburg)
Date: Wed, 16 Jul 2014 15:34:31 -0600
Subject: [Paraview] Determining the ParaView pipeline via Python
In-Reply-To: <CAMaOp+GBWv4nFbJ_L9joRxJRbsHjfjZniu=Vdj3J+szzhC8Fjg@mail.gmail.com>
References: <53C604D7.10807@indiana.edu>
 <CAMaOp+GBWv4nFbJ_L9joRxJRbsHjfjZniu=Vdj3J+szzhC8Fjg@mail.gmail.com>
Message-ID: <CAPiw4fAPK0+YxhwiAb9ehKF5yAZG98-rdi8f4DpAm16-DdPv0A@mail.gmail.com>

On Wed, Jul 16, 2014 at 3:07 PM, Andy Bauer <andy.bauer at kitware.com> wrote:

> Hi Bill,
>
> A couple of hopefully helpful hints:
>
>    - Maybe using a filter's Input object is enough to get the pipeline
>    connections you want (i.e. aa = bb.Input). This though assumes you're
>    working from the sink in the pipeline as opposed to a source.
>
>
I have recently added something like this to the server side protocols for
ParaViewWeb, though it's not yet in master.  Effectively, it just does what
you recommended, Andy, but doesn't require starting at the sink, and is a
complete example.  Here's how I got the pipeline connections:

proxies = servermanager.ProxyManager().GetProxiesInGroup("sources")
proxyList = []
for key in proxies:
    listElt = {}
    listElt['name'] = key[0]
    listElt['id'] = key[1]
    proxy = proxies[key]
    parentId = '0'
    if hasattr(proxy, 'Input'):
        parentId = proxy.Input.GetGlobalIDAsString()
    listElt['parent'] = parentId
    proxyList.append(listElt)

After this code finishes, proxyList contains all the sources and filters in
the pipeline and identifies each one's Input proxy id with the key 'parent'.
 The actual source (reader or whatever has no Input), has 'parent': '0'.
 Perhaps modifying this code so it builds a dictionary (mapping each proxy
id to the appropriate listElt object) instead of a list, and then making a
note of the proxy which does not have an Input property when it is
encountered, this would allow Bill to efficiently build the ascii map he is
looking for?

Cheers,
Scott


>
>    - As for getting the available arrays for a filter, you can do
>    something like:
>
> for da in range(aa.PointData.NumberOfArrays):
>   bb.PointData.GetArray(da)
>
>
>    - There was work on only writing out Python scripts with non-default
>    values which made the scripts much shorter. Somewhere there was an option
>    to specify whether to write out all values of the objects for trace and
>    python state or just the non-defaults but I can't find it now. It looks
>    like what you have already works but just wanted to mention that.
>
> Does this answer your questions?
>
>
> Regards,
>
> Andy
>
>
> On Wed, Jul 16, 2014 at 12:51 AM, Bill Sherman <shermanw at indiana.edu>
> wrote:
>
>> Community,
>>
>> I've been creating some simple python scripts that help me see a
>> simple representation of the state of ParaView.
>>
>> One thing I wanted was to be able to see what changes had been
>> made such that a value was no longer the default.  Then, I'm going
>> to print this out at the beginning of my batch animation jobs, which
>> will then go into the log file generated by the queuing system.
>>
>> So here is my function to do that for an object:
>>
>> ----------
>> def altered(object):
>>     if (object == None):
>>         return
>>     dup = object.__class__()
>>     for prop in dup.ListProperties():
>>         if (hasattr(object.GetProperty(prop), 'GetData')):
>>             if (dup.GetProperty(prop).GetData() !=
>> object.GetProperty(prop).GetData()):
>>                 print prop + ": " + str(object.GetProperty(prop))[:80] +
>> " [" + str(dup.GetProperty(prop)) + "]"
>>     del(dup)
>>     del(prop)
>> ----------
>>
>> And then I can loop over all the sources to get a handy list:
>>
>> ----------
>> for src in GetSources():
>>   srcp = FindSource(src[0])
>>   print "********************"
>>   print "    " + src[0] + " -- " + srcp.GetXMLLabel()
>>   altered(srcp)
>>   print "    ---------------"
>>   print "    Representation:"
>>   altered(GetDisplayProperties(srcp))
>> ----------
>>
>> So the main missing feature for me is trying to show how the sources
>> are linked together -- basically recreating the pipeline display,
>> except as ASCII text.  But I haven't yet figured out how to
>> programmatically determine which "sources" are connected to which.
>>
>>
>> The other thing I'd like to be able to do is report what other
>> field data is available from a file reader -- I can see by looking
>> in the .pvsm file that that data was saved, so I hope it might
>> be somehow available via the Python interface.
>>
>>
>>
>> So here's some sample output from a state file I'm experimenting
>> with:
>>
>> ********************
>>     Glyph1 -- Glyph
>> GlyphTransform: <paraview.servermanager.Transform2 object at 0x163
>> [<paraview.servermanager.Transform2 object at 0x1632910>]
>> Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
>> MaximumNumberofPoints: 50000 [5000]
>> Scalars: ['POINTS', 'mass'] [[None, '']]
>> Vectors: ['POINTS', 'velocity'] [[None, '']]
>> SetScaleFactor: 0.462090686322849 [1.0]
>> GlyphType: <paraview.servermanager.Sphere object at 0x16f24d0
>> [<paraview.servermanager.Arrow object at 0x1632190>]
>> MaskPoints: 0 [1]
>>     ----------------
>>     Representations
>> Input: <paraview.servermanager.Glyph object at 0x162e890> [None]
>> SelectionPointFieldDataArrayName: 'mass' ['vtkOriginalPointIds']
>> ColorArrayName: ('POINT_DATA', 'mass') [('POINT_DATA', '')]
>> DataBounds: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0] [[5.6965768965495727e-321,
>> 4.7846668906873337e-316, 4.7559715579768741e-316, 9.3872472709836843e-323,
>> 0.0, 5.6490774253583952e-318]]
>> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
>> ScaleFactor: 0.68949565887451203 [1.0]
>> ********************
>>     TemporalParticlesToPathlines1 -- Temporal Particles To Pathlines
>> Input: <paraview.servermanager.LegacyVTKReader object at  [None]
>> MaskPoints: 1 [100]
>>     ----------------
>>     Representations
>> Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
>> SelectionPointFieldDataArrayName: 'TrailId' ['vtkOriginalPointIds']
>> Visibility: 0 [1]
>> DataBounds: [0.0, nan, nan, nan, nan, 4.243991581436479e-314]
>> [[2.0018638793749296e-316, 2.0020954973496999e-316,
>> 4.7763681688472674e-316, 2.0021053786626168e-316, 2.0021022166424834e-316,
>> 2.0001733843611191e-316]]
>> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
>> ScaleFactor: 0.45304816961288502 [1.0]
>> ********************
>>     Tube1 -- Tube
>> Capping: 0 [1]
>> Input: <paraview.servermanager.TemporalParticlesToPathlin [None]
>> NumberofSides: 5 [6]
>> Radius: 0.0060000000000000001 [1.0]
>> Scalars: ['POINTS', 'TrailId'] [[None, '']]
>> Vectors: ['POINTS', 'velocity'] [[None, '']]
>>     ----------------
>>     Representations
>> Input: <paraview.servermanager.Tube object at 0x162e090> [None]
>> SelectionPointFieldDataArrayName: 'TrailId' ['vtkOriginalPointIds']
>> DataBounds: [0.0, 1.2648080533535912e-321, 1.5810100666919889e
>> [[5.0085616312819197e-316, 3.1620201333839779e-321,
>> 3.9525251667299724e-322, 5.0084066922953839e-316, 2.3176438028922704e-310,
>> 0.0]]
>> DiffuseColor: [1.0, 0.66666666666666696, 1.0] [[1.0, 1.0, 1.0]]
>> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
>> Opacity: 0.0 [1.0]
>> ScaleFactor: 0.76622586250305202 [1.0]
>> ********************
>>     vectors.vrml -- VRML Reader
>> FileName: '/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Initi ['']
>>     ----------------
>>     Representations
>> Input: <paraview.servermanager.VRMLReader object at 0x162 [None]
>> SelectionPointFieldDataArrayName: 'VRMLColor' ['vtkOriginalPointIds']
>> ColorArrayName: ('POINT_DATA', 'VRMLColor') [('POINT_DATA', '')]
>> DataBounds: [2.3715151000379834e-322, 2.7872298394991417e-316,
>> [[4.7835752032362829e-316, 2.0008125076805794e-316,
>> 2.4209216646221081e-322, 2.0009002537392808e-316, 2.0006433396034433e-316,
>> 0.0]]
>> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
>> MapScalars: 0 [1]
>> ScaleFactor: 1.16120505332947 [1.0]
>> ********************
>>     AnnotateTime1 -- Annotate Time
>> Format: 'I-V2F: %.1f' ['Time: %f']
>>     ----------------
>>     Representations
>> Input: <paraview.servermanager.AnnotateTime object at 0x1 [None]
>> Opacity: 0.5 [1.0]
>> ********************
>>     jhdata_* -- Legacy VTK Reader
>> FileNameInfo: '/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Initi [None]
>> FileNames: ['/N/dc2/scratch/shermanw/BinaryStars/Run_30k/Init [['']]
>> TimestepValues: [0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, [[]]
>>     ----------------
>>     Representations
>> Input: <paraview.servermanager.LegacyVTKReader object at  [None]
>> SelectionPointFieldDataArrayName: 'mass' ['vtkOriginalPointIds']
>> Visibility: 0 [1]
>> ColorArrayName: ('POINT_DATA', 'mass') [('POINT_DATA', '')]
>> DataBounds: [2.3177925133422193e-310, 0.0, 0.0, 0.0, 0.0, 0.0]
>> [[4.738173337151089e-316, 0.0, 0.0, 0.0, 0.0, 0.0]]
>> InterpolateScalarsBeforeMapping: 0 [1]
>> LookupTable: <paraview.servermanager.PVLookupTable object at 0x [None]
>> ScaleFactor: 0.74854731559753396 [1.0]
>>
>> ------------------------------------------------------------
>> --------------
>>
>>
>> Thanks for any advice.  I'll report back when I figure out a script that
>> does something more complete.
>>
>>         Bill
>>
>> --
>> Bill Sherman
>> Sr. Technology Advisor
>> Advanced Visualization Lab
>> Pervasive Technology Inst
>> Indiana University
>>
>> _______________________________________________
>> 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://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
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140716/b9dc269d/attachment-0001.html>

From cook47 at llnl.gov  Wed Jul 16 20:14:21 2014
From: cook47 at llnl.gov (Cook, Rich)
Date: Thu, 17 Jul 2014 00:14:21 +0000
Subject: [Paraview] building paraview with vtkManta
Message-ID: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>

I just ran across mention of vtkManta support in paraview.
http://www.kitware.com/media/html/RenderedRealismAtNearlyRealTimeRates.html

Yay!  Yay?

How solid is this?  The documentation how to enable is pretty vague.
"To use vtkManta in ParaView, simply build Manta as described above, and then turn on both shared libraries and the Manta plug-in when you build ParaView. You will then have to specify the location of the Manta source and build trees as described above.?

Changing my paraview build is always a daunting experience but the idea of getting this working is very attractive.  What are the magic flags to cmake?   My builds are automated and interacting with ccmake is problematic on a build farm.

Here?s what I currently do.  Can you see why I?m confused?   :-)
Is there just a -DVTK_MANTA flag?  Do I still turn OSMESA on?

Thanks for any help.

    $CMAKE_PATH/bin/cmake \
        $CMAKE_SPECIAL_ARGS \
        -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
-DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
-DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
 -DOSMESA_LIBRARY:FILEPATH='/usr/lib64/libOSMesa.so' \
 -DVTK_USE_OFFSCREEN:BOOL=ON -DOPENGL_gl_LIBRARY:FILEPATH= -DVTK_USE_X:BOOL=OFF" \
        -DQT_QMAKE_EXECUTABLE:FILEPATH=$QT_PATH/bin/qmake.real \
        -DOPENGL_glu_LIBRARY:FILEPATH="/usr/lib64/libGLU.so" \
        -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR" \
        -DPARAVIEW_USE_BOOST:BOOL=ON \
        -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
        -DVISIT_BUILD_READER_CGNS:BOOL=ON \
        -DVISIT_BUILD_READER_Mili:BOOL=ON \
        -DVISIT_BUILD_READER_Silo:BOOL=ON \
        -DCGNS_INCLUDE_DIR:PATH="${CGNS_PATH}/include" \
        -DCGNS_LIBRARY:FILEPATH="${CGNS_PATH}/lib/libcgns.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DMILI_INCLUDE_DIR:PATH="$MILI_PATH/include" \
        -DMILI_LIBRARY:FILEPATH="$MILI_PATH/lib/libmili.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DSILO_INCLUDE_DIR:PATH="$SILO_PATH/include;$MILI_PATH/include" \
        -DSILO_LIBRARY:FILEPATH="$SILO_PATH/lib/libsiloh5.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBoost_INCLUDE_DIR:PATH="${BOOST_PATH}/include" \
        -DBoost_LIBRARY_DIRS:FILEPATH="${BOOST_PATH}/lib" \
        -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
        -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" \
        -DCMAKE_CXX_FLAGS:STRING=" -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DCMAKE_C_FLAGS:STRING="  -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DVTK_USE_SYSTEM_HDF5:BOOL=ON \
        -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \
        -DHDF5_DIR:PATH="$HDF5_PATH" \
        -DHDF5_C_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_HL_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_hdf5_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBUILD_SHARED_LIBS:BOOL=ON \
        -DBUILD_TESTING:BOOL=OFF \
        $PARAVIEW_SOURCE || errexit "cmake exited with an error status. Please try again."


--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605
? (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140717/ed0728d2/attachment.html>

From shermanw at indiana.edu  Wed Jul 16 23:58:51 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Wed, 16 Jul 2014 23:58:51 -0400
Subject: [Paraview] Determining the ParaView pipeline via Python
In-Reply-To: <CAPiw4fAPK0+YxhwiAb9ehKF5yAZG98-rdi8f4DpAm16-DdPv0A@mail.gmail.com>
References: <53C604D7.10807@indiana.edu>	<CAMaOp+GBWv4nFbJ_L9joRxJRbsHjfjZniu=Vdj3J+szzhC8Fjg@mail.gmail.com>
 <CAPiw4fAPK0+YxhwiAb9ehKF5yAZG98-rdi8f4DpAm16-DdPv0A@mail.gmail.com>
Message-ID: <53C749FB.5060206@indiana.edu>

Andy, Scott,

Thank you for your responses!


Comments embedded:

On 07/16/2014 05:34 PM, Scott Wittenburg wrote:
>
>
>
> On Wed, Jul 16, 2014 at 3:07 PM, Andy Bauer <andy.bauer at kitware.com
> <mailto:andy.bauer at kitware.com>> wrote:
>
>     Hi Bill,
>
>     A couple of hopefully helpful hints:
>
>         * Maybe using a filter's Input object is enough to get the
>           pipeline connections you want (i.e. aa = bb.Input). This
>           though assumes you're working from the sink in the pipeline as
>           opposed to a source.
>
>
> I have recently added something like this to the server side protocols
> for ParaViewWeb, though it's not yet in master. Effectively, it just
> does what you recommended, Andy, but doesn't require starting at the
> sink, and is a complete example. Here's how I got the pipeline connections:
>
> proxies = servermanager.ProxyManager().GetProxiesInGroup("sources")
> proxyList = []
> for key in proxies:
> listElt = {}
> listElt['name'] = key[0]
> listElt['id'] = key[1]
> proxy = proxies[key]
> parentId = '0'
> if hasattr(proxy, 'Input'):
> parentId = proxy.Input.GetGlobalIDAsString()
> listElt['parent'] = parentId
> proxyList.append(listElt)
>
> After this code finishes, proxyList contains all the sources and filters
> in the pipeline and identifies each one's Input proxy id with the key
> 'parent'. The actual source (reader or whatever has no Input), has
> 'parent': '0'. Perhaps modifying this code so it builds a dictionary
> (mapping each proxy id to the appropriate listElt object) instead of a
> list, and then making a note of the proxy which does not have an Input
> property when it is encountered, this would allow Bill to efficiently
> build the ascii map he is looking for?

Yes, very good.  I can definitely work from that to create an ASCII tree
representation.  Thanks for the code.

My initial thought was that: yes, I could work from the sinks on up,
but at some point I have to determine which nodes are the sinks (leaves).
Using the node "0" as the root node, I can follow the branches easily
enough.

> Cheers,
> Scott
>
>         * As for getting the available arrays for a filter, you can do
>           something like:
>
>     for da in range(aa.PointData.NumberOfArrays):
>     bb.PointData.GetArray(da)

Good -- though I presume you mean "aa.PointData.GetArray(da)" on
the last line.

>         * There was work on only writing out Python scripts with
>           non-default values which made the scripts much shorter.
>           Somewhere there was an option to specify whether to write out
>           all values of the objects for trace and python state or just
>           the non-defaults but I can't find it now. It looks like what
>           you have already works but just wanted to mention that.

Yes, good to be aware of I guess.  I suppose as a means of communicating
values to future versions of ParaView, there's always the chance that the
default value may have changed between ParaView versions, and so saving
all the values protects against that.

When trying to evaluate my state files though, I often just want to know
what I changed -- for example if somehow my state is broken/corrupted, and
so I want to start from scratch, I at least want to know what values I'd
gone through and modified.

>     Does this answer your questions?

Yes, thank you both.

The one thing I haven't figured out yet though is how to find out other
objects that got created -- for example a sphere object created to be
the Glyph representation.  The XML of the .pvsm file suggests that it
gets added to the "sources" Proxy group, but it's not listed when
queried.  And I went through all the Proxy groups I could find names
for.

In the meantime, I can just have some special-case code that knows
that Glyph objects have a "hidden" object that they point to.

>     Regards,
>
>     Andy

	Thanks again,
	Bill


>     On Wed, Jul 16, 2014 at 12:51 AM, Bill Sherman <shermanw at indiana.edu
>     <mailto:shermanw at indiana.edu>> wrote:
>
>         Community,
>
>         I've been creating some simple python scripts that help me see a
>         simple representation of the state of ParaView.
>
>         One thing I wanted was to be able to see what changes had been
>         made such that a value was no longer the default. Then, I'm going
>         to print this out at the beginning of my batch animation jobs, which
>         will then go into the log file generated by the queuing system.
>
>         So here is my function to do that for an object:
>
>         ----------
>         def altered(object):
>         if (object == None):
>         return
>         dup = object.__class__()
>         for prop in dup.ListProperties():
>         if (hasattr(object.GetProperty(__prop), 'GetData')):
>         if (dup.GetProperty(prop).__GetData() !=
>         object.GetProperty(prop).__GetData()):
>         print prop + ": " + str(object.GetProperty(prop))[__:80] + " ["
>         + str(dup.GetProperty(prop)) + "]"
>         del(dup)
>         del(prop)
>         ----------
>
>         And then I can loop over all the sources to get a handy list:
>
>         ----------
>         for src in GetSources():
>         srcp = FindSource(src[0])
>         print "********************"
>         print " " + src[0] + " -- " + srcp.GetXMLLabel()
>         altered(srcp)
>         print " ---------------"
>         print " Representation:"
>         altered(GetDisplayProperties(__srcp))
>         ----------
>
>         So the main missing feature for me is trying to show how the sources
>         are linked together -- basically recreating the pipeline display,
>         except as ASCII text. But I haven't yet figured out how to
>         programmatically determine which "sources" are connected to which.
>
>
>         The other thing I'd like to be able to do is report what other
>         field data is available from a file reader -- I can see by looking
>         in the .pvsm file that that data was saved, so I hope it might
>         be somehow available via the Python interface.
>
>
>
>         So here's some sample output from a state file I'm experimenting
>         with:
>
>         ********************

[removed -- see original post]
>
>         ------------------------------__------------------------------__--------------
>
>
>         Thanks for any advice. I'll report back when I figure out a
>         script that
>         does something more complete.
>
>         Bill
>
>         --
>         Bill Sherman
>         Sr. Technology Advisor
>         Advanced Visualization Lab
>         Pervasive Technology Inst
>         Indiana University
>

From grothausmann.roman at mh-hannover.de  Thu Jul 17 06:36:16 2014
From: grothausmann.roman at mh-hannover.de (Dr. Roman Grothausmann)
Date: Thu, 17 Jul 2014 12:36:16 +0200
Subject: [Paraview] special field-data annotation filter or similar
	functionality
Message-ID: <53C7A720.3070701@mh-hannover.de>

Dear mailing list members,


Is there a filter in paraview that allows one to display specific field-data 
(e.g. of points or cells) at the 3D position of the corresponding point/cell in 
such a way that the annotation is hidden if some mesh or voxel object is in 
front? Or if the objects in front have some transparency the annotations are 
only visible as much as the transparency of the objects in front dictates?
I know about the possibility of displaying selection labels via the Find-Dialog.
However these annotations are
- always in front,
- cannot be made partially transparent (as I think was possible in older 
paraview versions than 4.1.0 when vtkVectorText was used) and
- only the active selection can be annotated, ie not multiple datasets.

I found this example in which the text is not always rendered in front of the axes:
https://github.com/Kitware/VTK/blob/master/Examples/Annotation/Python/textOrigin.py
However it uses vtkVectorText (which is not exportable as text into e.g. SVGs 
however vtkTextActor3D is).
I now wonder if only vtkVectorText allows being hidden by other objects or if 
some settings of vtkTextActor3D are not offered for adjustment in the Find-Dialog?
In any case a paraview filter that would offer all 3 features mentioned above 
would be really helpful. Are there any reasons that such a filter cannot be 
implemented in paraview at the present state?
Can such functionality be implemented in general with the current state of VTK?

Any help or hints are very much appreciated
Roman

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-9574

From mexas at bris.ac.uk  Thu Jul 17 06:55:09 2014
From: mexas at bris.ac.uk (Anton Shterenlikht)
Date: Thu, 17 Jul 2014 11:55:09 +0100 (BST)
Subject: [Paraview] vtkXOpenGLRenderWindow (0x25abb70): bad X server
	connection. DISPLAY=ERROR
Message-ID: <201407171055.s6HAt9J6038108@mech-cluster241.men.bris.ac.uk>

The error is from a pvbatch 4.0.1.
Please help.

job submission script:

newblue2> cat z.pv
#!/bin/bash --login
#
#$Id: sample.bc3.pvbatch 1022 2013-12-25 15:32:33Z mexas $
#
#PBS -l walltime=00:10:00,nodes=1:ppn=16
#PBS -j oe
#PBS -m abe

cd $HOME/nobkp/cgpack/branches/coarray/tests
export OUTFILE=z.out
echo > $OUTFILE

module load apps/paraview-4.0.1
echo "module list" >> $OUTFILE
module list >> $OUTFILE 2>&1

echo "LD_LIBRARY_PATH: " $LD_LIBRARY_PATH >> $OUTFILE
echo "which mpirun: " `which mpirun` >> $OUTFILE
export I_MPI_DAPL_PROVIDER=ofa-v2-ib0 >> $OUTFILE

mpirun -n 16 pvbatch --use-offscreen-rendering z.xdmf.py
#mpirun -n 16 pvbatch z.xdmf.py
newblue2> 


The error:

Warning: no access to tty (Bad file descriptor).
Thus no job control in this shell.
ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0x25abb70): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5ed90): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5edb0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0x25abb70): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5edb0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5ed90): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)


newblue2> echo $DISPLAY
DISPLAY: Undefined variable.
newblue2> 

Should DISPLAY be set?

Below is z.xdmf.py, if needed.

Thanks

Anton

************************

#$Id: sample.xdmf.py 1129 2014-07-16 12:24:06Z mexas $

try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

z_xdmf = XDMFReader( FileName='z.xdmf' )

AnimationScene1 = GetAnimationScene()
AnimationScene1.EndTime = 10.0
AnimationScene1.PlayMode = 'Snap To TimeSteps'

z_xdmf.Sets = []
z_xdmf.Grids = ['T0', 'T30', 'T60', 'T90', 'T120', 'T150', 'T180', 'T210', 'T240', 'T270', 'T300']
z_xdmf.PointArrays = ['crack']

RenderView1 = GetRenderView()
RenderView1.CenterOfRotation = [99.5, 99.5, 199.5]

DataRepresentation1 = Show()
DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
DataRepresentation1.Slice = 199
DataRepresentation1.SelectionPointFieldDataArrayName = 'crack'
DataRepresentation1.ScalarOpacityUnitDistance = 1.9457909325696094
DataRepresentation1.Representation = 'Outline'
DataRepresentation1.ScaleFactor = 39.900000000000006

RenderView1.CameraPosition = [99.5, 99.5, 1142.7561204025358]
RenderView1.CameraFocalPoint = [99.5, 99.5, 199.5]
RenderView1.CameraClippingRange = [536.8185591985105, 1457.1524622085738]
RenderView1.CameraParallelScale = 244.13264836969265

Threshold1 = Threshold()

Threshold1.Scalars = ['POINTS', 'crack']
Threshold1.ThresholdRange = [-3.0, 2147483647.0]

Threshold1.AllScalars = 0
Threshold1.ThresholdRange = [-3.0, 0.0]

DataRepresentation2 = Show()
DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
DataRepresentation2.SelectionPointFieldDataArrayName = 'crack'
DataRepresentation2.ColorArrayName = ('POINT_DATA', 'crack')
DataRepresentation2.ScalarOpacityUnitDistance = 1.7320508075688772
DataRepresentation2.ScaleFactor = 0.2

a1_crack_PVLookupTable = GetLookupTableForArray( "crack", 1, RGBPoints=[-3.0, 0.23, 0.299, 0.754, 1073741822.0, 0.865, 0.865, 0.865, 2147483647.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', NanColor=[0.25, 0.0, 0.0], ColorSpace='Diverging', ScalarRangeInitialized=1.0 )

a1_crack_PiecewiseFunction = CreatePiecewiseFunction( Points=[-3.0, 0.0, 0.5, 0.0, 2147483647.0, 1.0, 0.5, 0.0] )

DataRepresentation2.ScalarOpacityFunction = a1_crack_PiecewiseFunction
DataRepresentation2.LookupTable = a1_crack_PVLookupTable

a1_crack_PVLookupTable.ScalarOpacityFunction = a1_crack_PiecewiseFunction

RenderView1.CameraViewUp = [-0.23168815510934399, 0.295870302962722, -0.9267045713747051]
RenderView1.CameraPosition = [168.38086733394152, 1000.5240094507878, 469.95012328596755]
RenderView1.CameraClippingRange = [616.3953868850049, 1356.9816313770839]
RenderView1.CameraFocalPoint = [99.49999999999996, 99.50000000000001, 199.49999999999994]

WriteAnimation('z.ogv', Magnification=1, Quality=2, FrameRate=1.000000)


Render()


From dave.demarle at kitware.com  Thu Jul 17 09:55:30 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 17 Jul 2014 09:55:30 -0400
Subject: [Paraview] building paraview with vtkManta
In-Reply-To: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
Message-ID: <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>

Hey Rich,

I just ran across mention of vtkManta support in paraview.
>

Wow, 2010? You've got some catching up to do. :)

It still compiles, runs and passes high level tests tests. The nightly
linux binaries have it if you want to try it out quickly.

To compile it you need to:
* compile manta (specifically r2439)
* configure paraview with PARAVIEW_BUILD_PLUGIN_MantaView ON and
MANTA_BUILD variable pointed to your manta build tree.

Let me know if you need the exact syntax for unattended builds and I'll
send you a shell script.

How solid is this?
>

I am aware of a couple of bugs that have crept in while this has been in
cold storage (i.e. no project since the initial LANL push to pick up
development on it).
* Manta (r2439 specifically) needs patches for OSX 10.8+ and MSVC.
* View level options are not exposed in the GUI (very recent regression)
* off by one bug in point associated color mapping (probably old)

We did get to the "future work" item from that article about integrating
manta at the Renderer level so that OpenGL and Manta can coexist and it can
be used in standalone builds.

TACC is working on something that will address the limitation that
secondary rays don't work in HPC contexts.

Feel free to send me or the list emails for help getting it running.

cheers,

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jul 16, 2014 at 8:14 PM, Cook, Rich <cook47 at llnl.gov> wrote:

>  I just ran across mention of vtkManta support in paraview.
> http://www.kitware.com/media/html/RenderedRealismAtNearlyRealTimeRates.html
>
>  Yay!  Yay?
>
>  How solid is this?  The documentation how to enable is pretty vague.
> "To use vtkManta in ParaView, simply build Manta as described above, and
> then turn on both shared libraries and the Manta plug-in when you build
> ParaView. You will then have to specify the location of the Manta source
> and build trees as described above.?
>
>  Changing my paraview build is always a daunting experience but the idea
> of getting this working is very attractive.  What are the magic flags to
> cmake?   My builds are automated and interacting with ccmake is problematic
> on a build farm.
>
>  Here?s what I currently do.  Can you see why I?m confused?   :-)
> Is there just a -DVTK_MANTA flag?  Do I still turn OSMESA on?
>
>  Thanks for any help.
>
>       $CMAKE_PATH/bin/cmake \
>         $CMAKE_SPECIAL_ARGS \
>         -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
> -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
> -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
>   -DOSMESA_LIBRARY:FILEPATH='/usr/lib64/libOSMesa.so' \
>   -DVTK_USE_OFFSCREEN:BOOL=ON -DOPENGL_gl_LIBRARY:FILEPATH=
> -DVTK_USE_X:BOOL=OFF" \
>          -DQT_QMAKE_EXECUTABLE:FILEPATH=$QT_PATH/bin/qmake.real \
>         -DOPENGL_glu_LIBRARY:FILEPATH="/usr/lib64/libGLU.so" \
>         -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR" \
>         -DPARAVIEW_USE_BOOST:BOOL=ON \
>         -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
>         -DVISIT_BUILD_READER_CGNS:BOOL=ON \
>         -DVISIT_BUILD_READER_Mili:BOOL=ON \
>         -DVISIT_BUILD_READER_Silo:BOOL=ON \
>         -DCGNS_INCLUDE_DIR:PATH="${CGNS_PATH}/include" \
>
> -DCGNS_LIBRARY:FILEPATH="${CGNS_PATH}/lib/libcgns.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>         -DMILI_INCLUDE_DIR:PATH="$MILI_PATH/include" \
>
> -DMILI_LIBRARY:FILEPATH="$MILI_PATH/lib/libmili.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>         -DSILO_INCLUDE_DIR:PATH="$SILO_PATH/include;$MILI_PATH/include" \
>
> -DSILO_LIBRARY:FILEPATH="$SILO_PATH/lib/libsiloh5.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>         -DBoost_INCLUDE_DIR:PATH="${BOOST_PATH}/include" \
>         -DBoost_LIBRARY_DIRS:FILEPATH="${BOOST_PATH}/lib" \
>         -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
>         -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" \
>         -DCMAKE_CXX_FLAGS:STRING=" -I$MILI_PATH/include
> -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
>         -DCMAKE_C_FLAGS:STRING="  -I$MILI_PATH/include
> -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
>         -DVTK_USE_SYSTEM_HDF5:BOOL=ON \
>         -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \
>         -DHDF5_DIR:PATH="$HDF5_PATH" \
>         -DHDF5_C_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>         -DHDF5_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>         -DHDF5_HL_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>
> -DHDF5_hdf5_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>
> -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>
> -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>
> -DHDF5_hdf5_hl_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>
> -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>
> -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
> \
>         -DBUILD_SHARED_LIBS:BOOL=ON \
>         -DBUILD_TESTING:BOOL=OFF \
>         $PARAVIEW_SOURCE || errexit "cmake exited with an error status.
> Please try again."
>
>
>  --
> ?Richard Cook
> ? Lawrence Livermore National Laboratory
> Bldg-453 Rm-4024, Mail Stop L-557
> 7000 East Avenue,  Livermore, CA, 94550, USA
> ? (office) (925) 423-9605
> ? (fax) (925) 423-6961
> ---
> Information Management & Graphics Grp., Services & Development Div.,
> Integrated Computing & Communications Dept.
> (opinions expressed herein are mine and not those of LLNL)
>
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140717/1e7053f0/attachment-0001.html>

From bloring at lbl.gov  Thu Jul 17 11:26:53 2014
From: bloring at lbl.gov (Burlen Loring)
Date: Thu, 17 Jul 2014 08:26:53 -0700
Subject: [Paraview] vtkXOpenGLRenderWindow (0x25abb70): bad X server
 connection. DISPLAY=ERROR
In-Reply-To: <201407171055.s6HAt9J6038108@mech-cluster241.men.bris.ac.uk>
References: <201407171055.s6HAt9J6038108@mech-cluster241.men.bris.ac.uk>
Message-ID: <53C7EB3D.208@lbl.gov>

> Should DISPLAY be set?
yes if you have GPU hardware running on your cluster. In that case the 
xserver needs to be running. If it's not then you need to start it 
before launching PV.

if you don't have GPU's then you need to recompile ParaView for use with 
OSMesa. Here <http://www.paraview.org/Wiki/ParaView_And_Mesa_3D> are 
details.

On 07/17/2014 03:55 AM, Anton Shterenlikht wrote:
> The error is from a pvbatch 4.0.1.
> Please help.
>
> job submission script:
>
> newblue2> cat z.pv
> #!/bin/bash --login
> #
> #$Id: sample.bc3.pvbatch 1022 2013-12-25 15:32:33Z mexas $
> #
> #PBS -l walltime=00:10:00,nodes=1:ppn=16
> #PBS -j oe
> #PBS -m abe
>
> cd $HOME/nobkp/cgpack/branches/coarray/tests
> export OUTFILE=z.out
> echo > $OUTFILE
>
> module load apps/paraview-4.0.1
> echo "module list" >> $OUTFILE
> module list >> $OUTFILE 2>&1
>
> echo "LD_LIBRARY_PATH: " $LD_LIBRARY_PATH >> $OUTFILE
> echo "which mpirun: " `which mpirun` >> $OUTFILE
> export I_MPI_DAPL_PROVIDER=ofa-v2-ib0 >> $OUTFILE
>
> mpirun -n 16 pvbatch --use-offscreen-rendering z.xdmf.py
> #mpirun -n 16 pvbatch z.xdmf.py
> newblue2>
>
>
> The error:
>
> Warning: no access to tty (Bad file descriptor).
> Thus no job control in this shell.
> ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0x25abb70): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5ed90): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5edb0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0x25abb70): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5edb0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5ed90): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 531
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
> vtkXOpenGLRenderWindow (0xe5eef0): bad X server connection. DISPLAY=APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)
>
>
> newblue2> echo $DISPLAY
> DISPLAY: Undefined variable.
> newblue2>
>
> Should DISPLAY be set?
>
> Below is z.xdmf.py, if needed.
>
> Thanks
>
> Anton
>
> ************************
>
> #$Id: sample.xdmf.py 1129 2014-07-16 12:24:06Z mexas $
>
> try: paraview.simple
> except: from paraview.simple import *
> paraview.simple._DisableFirstRenderCameraReset()
>
> z_xdmf = XDMFReader( FileName='z.xdmf' )
>
> AnimationScene1 = GetAnimationScene()
> AnimationScene1.EndTime = 10.0
> AnimationScene1.PlayMode = 'Snap To TimeSteps'
>
> z_xdmf.Sets = []
> z_xdmf.Grids = ['T0', 'T30', 'T60', 'T90', 'T120', 'T150', 'T180', 'T210', 'T240', 'T270', 'T300']
> z_xdmf.PointArrays = ['crack']
>
> RenderView1 = GetRenderView()
> RenderView1.CenterOfRotation = [99.5, 99.5, 199.5]
>
> DataRepresentation1 = Show()
> DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
> DataRepresentation1.Slice = 199
> DataRepresentation1.SelectionPointFieldDataArrayName = 'crack'
> DataRepresentation1.ScalarOpacityUnitDistance = 1.9457909325696094
> DataRepresentation1.Representation = 'Outline'
> DataRepresentation1.ScaleFactor = 39.900000000000006
>
> RenderView1.CameraPosition = [99.5, 99.5, 1142.7561204025358]
> RenderView1.CameraFocalPoint = [99.5, 99.5, 199.5]
> RenderView1.CameraClippingRange = [536.8185591985105, 1457.1524622085738]
> RenderView1.CameraParallelScale = 244.13264836969265
>
> Threshold1 = Threshold()
>
> Threshold1.Scalars = ['POINTS', 'crack']
> Threshold1.ThresholdRange = [-3.0, 2147483647.0]
>
> Threshold1.AllScalars = 0
> Threshold1.ThresholdRange = [-3.0, 0.0]
>
> DataRepresentation2 = Show()
> DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
> DataRepresentation2.SelectionPointFieldDataArrayName = 'crack'
> DataRepresentation2.ColorArrayName = ('POINT_DATA', 'crack')
> DataRepresentation2.ScalarOpacityUnitDistance = 1.7320508075688772
> DataRepresentation2.ScaleFactor = 0.2
>
> a1_crack_PVLookupTable = GetLookupTableForArray( "crack", 1, RGBPoints=[-3.0, 0.23, 0.299, 0.754, 1073741822.0, 0.865, 0.865, 0.865, 2147483647.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', NanColor=[0.25, 0.0, 0.0], ColorSpace='Diverging', ScalarRangeInitialized=1.0 )
>
> a1_crack_PiecewiseFunction = CreatePiecewiseFunction( Points=[-3.0, 0.0, 0.5, 0.0, 2147483647.0, 1.0, 0.5, 0.0] )
>
> DataRepresentation2.ScalarOpacityFunction = a1_crack_PiecewiseFunction
> DataRepresentation2.LookupTable = a1_crack_PVLookupTable
>
> a1_crack_PVLookupTable.ScalarOpacityFunction = a1_crack_PiecewiseFunction
>
> RenderView1.CameraViewUp = [-0.23168815510934399, 0.295870302962722, -0.9267045713747051]
> RenderView1.CameraPosition = [168.38086733394152, 1000.5240094507878, 469.95012328596755]
> RenderView1.CameraClippingRange = [616.3953868850049, 1356.9816313770839]
> RenderView1.CameraFocalPoint = [99.49999999999996, 99.50000000000001, 199.49999999999994]
>
> WriteAnimation('z.ogv', Magnification=1, Quality=2, FrameRate=1.000000)
>
>
> Render()
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140717/9398304f/attachment.html>

From cook47 at llnl.gov  Thu Jul 17 12:25:04 2014
From: cook47 at llnl.gov (Cook, Rich)
Date: Thu, 17 Jul 2014 16:25:04 +0000
Subject: [Paraview] building paraview with vtkManta
In-Reply-To: <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
 <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
Message-ID: <7AC6E2E2-970C-4DAB-9ADE-0992765A6BA6@llnl.gov>

Thanks
What kind of experience can I expect?  I couldn?t find a description, tutorial or other presentation on the subject other than the page I stumbled across.
I?m hoping this will scale better than e.g blender does, where I?m hitting size limitations at disappointing scales.  I?m dusting off my old POVray stuff and I recall being seriously limited there as well in terms of size and speed but haven?t gotten it working again yet to be able to tell if it?s the same now as it was.
I?d love to see your build script, thanks.
? Rich

On Jul 17, 2014, at 6:55 AM, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:

Hey Rich,

I just ran across mention of vtkManta support in paraview.

Wow, 2010? You've got some catching up to do. :)

It still compiles, runs and passes high level tests tests. The nightly linux binaries have it if you want to try it out quickly.

To compile it you need to:
* compile manta (specifically r2439)
* configure paraview with PARAVIEW_BUILD_PLUGIN_MantaView ON and MANTA_BUILD variable pointed to your manta build tree.

Let me know if you need the exact syntax for unattended builds and I'll send you a shell script.

How solid is this?

I am aware of a couple of bugs that have crept in while this has been in cold storage (i.e. no project since the initial LANL push to pick up development on it).
* Manta (r2439 specifically) needs patches for OSX 10.8+ and MSVC.
* View level options are not exposed in the GUI (very recent regression)
* off by one bug in point associated color mapping (probably old)

We did get to the "future work" item from that article about integrating manta at the Renderer level so that OpenGL and Manta can coexist and it can be used in standalone builds.

TACC is working on something that will address the limitation that secondary rays don't work in HPC contexts.

Feel free to send me or the list emails for help getting it running.

cheers,

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jul 16, 2014 at 8:14 PM, Cook, Rich <cook47 at llnl.gov<mailto:cook47 at llnl.gov>> wrote:
I just ran across mention of vtkManta support in paraview.
http://www.kitware.com/media/html/RenderedRealismAtNearlyRealTimeRates.html

Yay!  Yay?

How solid is this?  The documentation how to enable is pretty vague.
"To use vtkManta in ParaView, simply build Manta as described above, and then turn on both shared libraries and the Manta plug-in when you build ParaView. You will then have to specify the location of the Manta source and build trees as described above.?

Changing my paraview build is always a daunting experience but the idea of getting this working is very attractive.  What are the magic flags to cmake?   My builds are automated and interacting with ccmake is problematic on a build farm.

Here?s what I currently do.  Can you see why I?m confused?   :-)
Is there just a -DVTK_MANTA flag?  Do I still turn OSMESA on?

Thanks for any help.

    $CMAKE_PATH/bin/cmake \
        $CMAKE_SPECIAL_ARGS \
        -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
-DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
-DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
 -DOSMESA_LIBRARY:FILEPATH='/usr/lib64/libOSMesa.so' \
 -DVTK_USE_OFFSCREEN:BOOL=ON -DOPENGL_gl_LIBRARY:FILEPATH= -DVTK_USE_X:BOOL=OFF" \
        -DQT_QMAKE_EXECUTABLE:FILEPATH=$QT_PATH/bin/qmake.real \
        -DOPENGL_glu_LIBRARY:FILEPATH="/usr/lib64/libGLU.so" \
        -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR" \
        -DPARAVIEW_USE_BOOST:BOOL=ON \
        -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
        -DVISIT_BUILD_READER_CGNS:BOOL=ON \
        -DVISIT_BUILD_READER_Mili:BOOL=ON \
        -DVISIT_BUILD_READER_Silo:BOOL=ON \
        -DCGNS_INCLUDE_DIR:PATH="${CGNS_PATH}/include" \
        -DCGNS_LIBRARY:FILEPATH="${CGNS_PATH}/lib/libcgns.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DMILI_INCLUDE_DIR:PATH="$MILI_PATH/include" \
        -DMILI_LIBRARY:FILEPATH="$MILI_PATH/lib/libmili.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DSILO_INCLUDE_DIR:PATH="$SILO_PATH/include;$MILI_PATH/include" \
        -DSILO_LIBRARY:FILEPATH="$SILO_PATH/lib/libsiloh5.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBoost_INCLUDE_DIR:PATH="${BOOST_PATH}/include" \
        -DBoost_LIBRARY_DIRS:FILEPATH="${BOOST_PATH}/lib" \
        -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
        -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" \
        -DCMAKE_CXX_FLAGS:STRING=" -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DCMAKE_C_FLAGS:STRING="  -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DVTK_USE_SYSTEM_HDF5:BOOL=ON \
        -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \
        -DHDF5_DIR:PATH="$HDF5_PATH" \
        -DHDF5_C_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_HL_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_hdf5_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBUILD_SHARED_LIBS:BOOL=ON \
        -DBUILD_TESTING:BOOL=OFF \
        $PARAVIEW_SOURCE || errexit "cmake exited with an error status. Please try again."


--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605<tel:%28925%29%20423-9605>
? (fax) (925) 423-6961<tel:%28925%29%20423-6961>
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)




_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview



--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605
? (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140717/13a3d006/attachment-0001.html>

From shermanw at indiana.edu  Thu Jul 17 12:41:51 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Thu, 17 Jul 2014 12:41:51 -0400
Subject: [Paraview] building paraview with vtkManta [Re: ParaView Digest, Vol 123,
 Issue 33]
In-Reply-To: <mailman.1299.1405614308.20882.paraview@paraview.org>
References: <mailman.1299.1405614308.20882.paraview@paraview.org>
Message-ID: <53C7FCCF.7040703@indiana.edu>

Dave,

+1 on the Manta stuff for me.  I'll give it a try myself in August once
I get my current Vis project done.

Rich,

Something else you might consider (as am I), instead of Blender/POVray
is RenderMan -- Pixar is making it freely available for non commercial
use in the next month or so (hopefully at SIGGRAPH), and I anticipate
RenderMan will be able to handle big rendering jobs.

I've seen that there is a vtk module for outputting RenderMan RiB files,
which is a hopeful sign, though I'd suspect that there's been some
atrophy in that, so who knows how easy it will be to make it work.

I plan to put RenderMan on our Cray ASAP once the release happens.

	Bill


> Message: 2
> Date: Thu, 17 Jul 2014 16:25:04 +0000
> From: "Cook, Rich"<cook47 at llnl.gov>
> To: David E DeMarle<dave.demarle at kitware.com>
> Cc: "paraview at paraview.org"<paraview at paraview.org>
> Subject: Re: [Paraview] building paraview with vtkManta
> Message-ID:<7AC6E2E2-970C-4DAB-9ADE-0992765A6BA6 at llnl.gov>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks
> What kind of experience can I expect?  I couldn?t find a description, tutorial or other presentation on the subject other than the page I stumbled across.
> I?m hoping this will scale better than e.g blender does, where I?m hitting size limitations at disappointing scales.  I?m dusting off my old POVray stuff and I recall being seriously limited there as well in terms of size and speed but haven?t gotten it working again yet to be able to tell if it?s the same now as it was.
> I?d love to see your build script, thanks.
> ? Rich
>
> On Jul 17, 2014, at 6:55 AM, David E DeMarle<dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>  wrote:
>
> Hey Rich,
>
> I just ran across mention of vtkManta support in paraview.
>
> Wow, 2010? You've got some catching up to do. :)
>
> It still compiles, runs and passes high level tests tests. The nightly linux binaries have it if you want to try it out quickly.
>
> To compile it you need to:
> * compile manta (specifically r2439)
> * configure paraview with PARAVIEW_BUILD_PLUGIN_MantaView ON and MANTA_BUILD variable pointed to your manta build tree.
>
> Let me know if you need the exact syntax for unattended builds and I'll send you a shell script.
>
> How solid is this?
>
> I am aware of a couple of bugs that have crept in while this has been in cold storage (i.e. no project since the initial LANL push to pick up development on it).
> * Manta (r2439 specifically) needs patches for OSX 10.8+ and MSVC.
> * View level options are not exposed in the GUI (very recent regression)
> * off by one bug in point associated color mapping (probably old)
>
> We did get to the "future work" item from that article about integrating manta at the Renderer level so that OpenGL and Manta can coexist and it can be used in standalone builds.
>
> TACC is working on something that will address the limitation that secondary rays don't work in HPC contexts.
>
> Feel free to send me or the list emails for help getting it running.
>
> cheers,
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>

From dave.demarle at kitware.com  Thu Jul 17 13:47:51 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 17 Jul 2014 13:47:51 -0400
Subject: [Paraview] PVD file format
In-Reply-To: <CA+Wz_Fzovy4rsZVWPr__8NqxM7cfM-MLk5i0hSDqvEKoqcFq2g@mail.gmail.com>
References: <CA+Wz_Fzovy4rsZVWPr__8NqxM7cfM-MLk5i0hSDqvEKoqcFq2g@mail.gmail.com>
Message-ID: <CANjZAi82Ys+qyP1SZaTAV6g0w4e=p8K9Cs1OLQn4Y6WU8EyCrQ@mail.gmail.com>

This question comes up every once in a while.

So, I just ported Appendix D from the old Paraview Guide to the wiki (and
updated the timestep description to be float instead of counting number.)

See:
http://www.paraview.org/Wiki/ParaView/Data_formats

I _think_ the answer to both of your questions is no but don't have time to
verify.
Try it and see.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jul 16, 2014 at 5:04 AM, victor sv <victorsv at gmail.com> wrote:

> Hi all,
>
> i'm searching for a description for the PVD file format and i don't find
> any official document. Is there any official document describing the PVD
> format?
>
> I have some doubts:
>
> Can exists several collection sections?,
> Is there another type of labels, instead of collection?
>
> Thanks,
> V?ctor
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140717/86fe388f/attachment.html>

From menonon at port.kobe-u.ac.jp  Fri Jul 18 01:36:14 2014
From: menonon at port.kobe-u.ac.jp (Daisuke Meno)
Date: Fri, 18 Jul 2014 14:36:14 +0900
Subject: [Paraview] VR plugin cannot be built.
In-Reply-To: <CAEw35Z82Mo1K=Qc_9a1FEatZj3TKsDNMAa_oy=Ti9yC=V=Vb=Q@mail.gmail.com>
References: <CAA+mDZg5TL+98jKh7hd4b_76treKV8uA5f6GZ70NprHupM0Cmg@mail.gmail.com>
 <CAEw35Z82Mo1K=Qc_9a1FEatZj3TKsDNMAa_oy=Ti9yC=V=Vb=Q@mail.gmail.com>
Message-ID: <CAA+mDZgxh2CyxmRxryTE4Uipn0-J2c9qz5X=wdduVDbwqukXeg@mail.gmail.com>

I got ParaView by git.
So I got the latest version of ParaView.
The commit ID is 0f36f0e1c3ca2a33c369e72c3eb424980cdfb2ce .

Regards,

2014-07-16 22:06 GMT+09:00 Aashish Chaudhary <aashish.chaudhary at kitware.com>:
> What version of ParaView is this?
>
> Thanks,
>
>
>
> On Tue, Jul 15, 2014 at 12:22 AM, Daisuke Meno <menonon at port.kobe-u.ac.jp>
> wrote:
>>
>> Hi,
>>
>> VR plugin cannot be built on Windows7.
>> I have followed this page.
>> http://www.paraview.org/Wiki/ParaView/VRPN_with_MS-MPI
>>
>> But I got errors.
>> Sorry, text files include some Japanese characters.
>>
>> Would you give me any solution ?
>>
>> Thanks
>> Daisuke
>>
>> --
>> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> Kobe University
>> Education Center on Computational Science and Engineering
>>
>>                 Daisuke MENO
>>     (Limited-term Assistant Professor)
>>
>>  Integrated Research Center @ Port Island
>> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>
>
>
> --
> | Aashish Chaudhary
> | Technical Leader
> | Kitware Inc.
> | http://www.kitware.com/company/team/chaudhary.html



-- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
???? ??????????
Kobe University
Education Center on Computational Science and Engineering

             ??????????
                Daisuke MENO
    (Limited-term Assistant Professor)

    menonon at port.kobe-u.ac.jp

      ??????2F@????????
 Integrated Research Center @ Port Island
      078-599-6723     080-3136-9659
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

From victorsv at gmail.com  Fri Jul 18 03:31:14 2014
From: victorsv at gmail.com (victor sv)
Date: Fri, 18 Jul 2014 09:31:14 +0200
Subject: [Paraview] PVD file format
In-Reply-To: <CANjZAi82Ys+qyP1SZaTAV6g0w4e=p8K9Cs1OLQn4Y6WU8EyCrQ@mail.gmail.com>
References: <CA+Wz_Fzovy4rsZVWPr__8NqxM7cfM-MLk5i0hSDqvEKoqcFq2g@mail.gmail.com>
 <CANjZAi82Ys+qyP1SZaTAV6g0w4e=p8K9Cs1OLQn4Y6WU8EyCrQ@mail.gmail.com>
Message-ID: <CA+Wz_FxrQ+GhunUQJhuehdM=ELRce283OknJhQMcvNwMka74dA@mail.gmail.com>

Ok, Thank you!

This is all I need to know. I was googling and i didn't find anything about
that ... but, Paraview wiki seems to be the natural place to search for
that :)

Thanks again,
V?ctor.


2014-07-17 19:47 GMT+02:00 David E DeMarle <dave.demarle at kitware.com>:

> This question comes up every once in a while.
>
> So, I just ported Appendix D from the old Paraview Guide to the wiki (and
> updated the timestep description to be float instead of counting number.)
>
> See:
> http://www.paraview.org/Wiki/ParaView/Data_formats
>
> I _think_ the answer to both of your questions is no but don't have time
> to verify.
> Try it and see.
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
> On Wed, Jul 16, 2014 at 5:04 AM, victor sv <victorsv at gmail.com> wrote:
>
>> Hi all,
>>
>> i'm searching for a description for the PVD file format and i don't find
>> any official document. Is there any official document describing the PVD
>> format?
>>
>> I have some doubts:
>>
>> Can exists several collection sections?,
>> Is there another type of labels, instead of collection?
>>
>> Thanks,
>> V?ctor
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140718/5b56f851/attachment.html>

From kotya.lists at gmail.com  Fri Jul 18 10:09:49 2014
From: kotya.lists at gmail.com (Kotya Karapetyan)
Date: Fri, 18 Jul 2014 16:09:49 +0200
Subject: [Paraview] Applying 3D data to an STL object surface
Message-ID: <CAK2dJ-wsypNWP9o6roLiezB+-ohdnbYxLii_fWCnk9JZU+tV-g@mail.gmail.com>

Dear all,

I am very new to ParaView so please excuse me for asking possibly stupid things.

I would like to use ParaView to display the 3D distribution of some
value (optical radiation load) on the surface of a 3D object. So get
something similar to this:
http://www2.argenco.ulg.ac.be/logiciels/SAFIR/images/appex2-4.jpg

I am thinking of something like the following.

The 3D object is described by an STL file. The load data is saved in a
CSV file as x, y, z, power.
This data should be somehow applied to the object surface. For example
by assigning it to the nearest facet of the STL mesh.

Does is sound reasonable, is ParaView the right tool to use at all,
and if yes, how can I achieve what I want? The load data (the CSV
file) is created with Matlab, after performing ray-tracing with Zemax,
so I am very flexible in any data processing to make it well-shaped
for ParaView.

Thanks a lot in advance!

Best regards,
Kotya

From biddisco at cscs.ch  Fri Jul 18 13:58:22 2014
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Fri, 18 Jul 2014 17:58:22 +0000
Subject: [Paraview] Building Piston
In-Reply-To: <1B75FE20F814944EA42F9A3A76476C253C4A76C358@HQMAIL03.nvidia.com>
Message-ID: <CFEF2C3E.604F2%biddisco@cscs.ch>

https://github.com/biddisco/PISTON/tree/pv-cuda
Is a fork I made of piston some time back where I fixed some thrust related problems I had ? mostly using piston with newer versions of cuda and newer thrust versions than it was originally intended for.

Warning : I made a lot of changes to data types for the vtk-piston rendering as my needs were not covered by the piston from lanl. This may mean you can?t use it for whatever you wanted. It might be useful for compilation fixes etc.

JB

From: Praveen Narayanan <praveenn at nvidia.com<mailto:praveenn at nvidia.com>>
Date: Tuesday 15 July 2014 00:34
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [Paraview] Building Piston

Hi

I have been trying to build piston from the paraview source (on website), and standalone piston from the lanl website.

I run into this error:

urces
[ 32%] Built target vtkRenderingCore
[ 32%] Built target vtkParseOGLExt
[ 32%] Built target vtkEncodeString
[ 32%] Built target vtkEncodeString-launcher
[ 32%] Built target vtkRenderingOpenGL
[ 32%] Building NVCC (Device) object VTK/Accelerators/Piston/CMakeFiles/cuda_compile.dir//./cuda_compile_generated_vtkPistonThreshold.cu.o
nvcc warning : The 'compute_10' and 'sm_10' architectures are deprecated, and may be removed in a future release.
nvcc warning : The 'compute_10' and 'sm_10' architectures are deprecated, and may be removed in a future release.
/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(13): error: invalid redeclaration of type name "float3"
/usr/local/cuda/include/vector_types.h(394): here

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(18): error: invalid redeclaration of type name "float4"
/usr/local/cuda/include/vector_types.h(395): here

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(23): error: invalid redeclaration of type name "uint3"
/usr/local/cuda/include/vector_types.h(381): here

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(29): error: cannot overload functions distinguished by return type alone

/home/praveen/projects/paraview/piston_try2/ParaView/VTK/Accelerators/Piston/piston/piston_math.h(34): error: cannot overload functions distinguished by return type alone

?.


Several such errors appear. Float2, float3 etc are cuda specific things, so I am not sure what is happening here.

Ideas?
Thanks
Praveen

Applied Engineer
NVIDIA

http://devblogs.nvidia.com/parallelforall/

________________________________
This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________

From marcus.hanwell at kitware.com  Fri Jul 18 15:53:34 2014
From: marcus.hanwell at kitware.com (Marcus D. Hanwell)
Date: Fri, 18 Jul 2014 15:53:34 -0400
Subject: [Paraview] Using JOIN to load images from Many HDF files.
In-Reply-To: <53C059B8.9050504@anl.gov>
References: <53BFFA00.9040605@anl.gov>
 <CAMkPkZVK9mOXTf2e3f_uU5reo3gCuYVSiJ7LvSBiK+yW=SfoPQ@mail.gmail.com>
 <53C059B8.9050504@anl.gov>
Message-ID: <CAMkPkZW0y9JzRDXLHudYZmBR7CM_NmTAAwj8381q_pbO1nmTtg@mail.gmail.com>

John,

Thanks for the additional information, this is really useful and
certainly helps us as we look at data coming from experimental domains
such as this. I will take a look at the links provided, and am very
interested in hearing more as you work with facility users to make use
of ParaView in this area.

I did some work on improving the TIFF reader (already merged), and
added support for 32 bit floats among other things. Were you thinking
of this, http://www.aps.anl.gov/DataExchange/, for the tomography
data? I hadn't come across it, but it is great to see it so
well-defined with example code.

Thanks,

Marcus

On Fri, Jul 11, 2014 at 5:40 PM, John Hammonds <JPHammonds at anl.gov> wrote:
> Marcus,
>
> The HDF data that I am working with is currently collected using the NeXus
> data format (http://www.nexusformat.org/).  Some of the data that is
> collected has all of the data in one big file and others have the data in
> separate files.  For the case that all of the data is in one big file, XDMF
> actually works pretty smoothly once you get over the initial hurdles.  For
> the case that the data is in different files, I had the issues that I
> described.  Note that I have also looked the last couple of days on loading
> Tiff images (for another beamline here www.aps.anl.gov) using Binary instead
> of HDF. This went pretty smoothly except that the XDMF pages do not mention
> that you can use Short as the NumberType for 16 bit data. Eventually I tried
> it and it fixed my loading issues.
>
> Note that we also have some Tomography beamlines here.  Their data is
> captured in a similar but different HDF format (can't see to find the link
> at the moment).
>
> John
>
> On 7/11/2014 2:42 PM, Marcus D. Hanwell wrote:
>>
>> On Fri, Jul 11, 2014 at 10:51 AM, John Hammonds <JPHammonds at anl.gov>
>> wrote:
>>>
>>> I tried posting this to the XDMF mailing list and have received no
>>> response.
>>> Hoping someone here can help...
>>>
>>> I have a number of images(a few hundred) , each collected in an
>>> individual
>>> HDF file, that I am trying to read into Paraview using a XDMF file.  I
>>> have
>>> found that I can use JOIN to do this but it seems that I need to nest the
>>> JOINs.  The nesting seems to be due to some limit on the number of things
>>> that can be referenced in the JOIN.  I seem to be limited to ten items in
>>> the join list.  All of this has me building some odd Join files due to
>>> the
>>> way things are joined at each level.  I am wondering if I am missing
>>> something that would make this a lot simpler.  Esp since I seem to have
>>> trouble when large sets are not the same size.  I am including a working
>>> XDMF file an example of one of the HDF files for reference.
>>>
>> How is your data produced? We are developing a custom ParaView
>> application, and as part of that we are adding some new readers to VTK
>> to support S/TEM tomography using an HDF5-based format. The spec is
>> here,
>>
>> http://emdatasets.lbl.gov/spec/
>>
>> It would be great to understand your needs, and whether some of this
>> development work could be tweaked in order to address a wider range of
>> experimental data that might help your user community. If XDMF is one
>> path, then we should also look more closely at supporting that too.
>>
>> Thanks,
>>
>> Marcus
>
>
> --
> --------------------------------------------
> John Hammonds
> Software Services Group
> Advanced Photon Source
> Argonne National Laboratory
> JPHammonds at anl.gov
>

From linzhenhua at 163.com  Sat Jul 19 09:48:36 2014
From: linzhenhua at 163.com (linzhenhua)
Date: Sat, 19 Jul 2014 21:48:36 +0800 (CST)
Subject: [Paraview] Error when comparing multiple datasets
Message-ID: <28689d99.574c.1474ee1a5a0.Coremail.linzhenhua@163.com>

Hi

I want to compare the difference from the data from two dataset with the same grid topology. I load in two dataset separately, then apply the PythonCalculator filter, but immediately encounter the following error. What is the problem? The version is 4.1 for 32bit linux OS.

ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140719/2b1bdd53/attachment.html>

From paul.m.edwards at gmail.com  Sat Jul 19 16:18:08 2014
From: paul.m.edwards at gmail.com (Paul Edwards)
Date: Sat, 19 Jul 2014 21:18:08 +0100
Subject: [Paraview] Error when comparing multiple datasets
In-Reply-To: <28689d99.574c.1474ee1a5a0.Coremail.linzhenhua@163.com>
References: <28689d99.574c.1474ee1a5a0.Coremail.linzhenhua@163.com>
Message-ID: <CABWOrb_VscfVa9gqAxrgehwbKac4y4q_hsX4VSK8yUD=z12r6A@mail.gmail.com>

Try using "Merge Blocks" on each of the two input datasets before using the
python calculator.

Regards,
Paul


On 19 July 2014 14:48, linzhenhua <linzhenhua at 163.com> wrote:

> Hi
>
> I want to compare the difference from the data from two dataset with the
> same grid topology. I load in two dataset separately, then apply the
> PythonCalculator filter, but immediately encounter the following error.
> What is the problem? The version is 4.1 for 32bit linux OS.
>
> ERROR: In
> /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx,
> line 815
> vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on
> input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type
> vtkMultiBlockDataSet, but a vtkDataSet is required.
>
>
> ERROR: In
> /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx,
> line 815
> vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on
> input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type
> vtkMultiBlockDataSet, but a vtkDataSet is required.
>
>
> ERROR: In
> /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx,
> line 815
> vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on
> input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type
> vtkMultiBlockDataSet, but a vtkDataSet is required.
>
>
> ERROR: In
> /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx,
> line 815
> vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on
> input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type
> vtkMultiBlockDataSet, but a vtkDataSet is required.
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140719/49d2e5b5/attachment.html>

From linzhenhua at 163.com  Sat Jul 19 20:54:06 2014
From: linzhenhua at 163.com (linzhenhua)
Date: Sun, 20 Jul 2014 08:54:06 +0800 (CST)
Subject: [Paraview] Error when comparing multiple datasets
In-Reply-To: <CABWOrb_VscfVa9gqAxrgehwbKac4y4q_hsX4VSK8yUD=z12r6A@mail.gmail.com>
References: <28689d99.574c.1474ee1a5a0.Coremail.linzhenhua@163.com>
 <CABWOrb_VscfVa9gqAxrgehwbKac4y4q_hsX4VSK8yUD=z12r6A@mail.gmail.com>
Message-ID: <78007e1f.66f0.1475142ed97.Coremail.linzhenhua@163.com>

Hi Paul

Thanks for your help. But this does not work for me as "Merge Blocks" can not be applied to the two input datasets, which is in grey color.

This is very strange to me as the example in the usermanual, "Comparing Multiple Datasets" section in page 96, work perfectly for me. The data I used is from OpenFOAM calculation.







? 2014-07-20 04:18:08?"Paul Edwards" <paul.m.edwards at gmail.com> ???

Try using "Merge Blocks" on each of the two input datasets before using the python calculator.


Regards,
Paul



On 19 July 2014 14:48, linzhenhua <linzhenhua at 163.com> wrote:

Hi

I want to compare the difference from the data from two dataset with the same grid topology. I load in two dataset separately, then apply the PythonCalculator filter, but immediately encounter the following error. What is the problem? The version is 4.1 for 32bit linux OS.

ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.











_______________________________________________
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://public.kitware.com/mailman/listinfo/paraview



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140720/93494bbe/attachment-0001.html>

From linzhenhua at 163.com  Sat Jul 19 21:04:38 2014
From: linzhenhua at 163.com (linzhenhua)
Date: Sun, 20 Jul 2014 09:04:38 +0800 (CST)
Subject: [Paraview] Error when comparing multiple datasets
In-Reply-To: <CABWOrb_VscfVa9gqAxrgehwbKac4y4q_hsX4VSK8yUD=z12r6A@mail.gmail.com>
References: <28689d99.574c.1474ee1a5a0.Coremail.linzhenhua@163.com>
 <CABWOrb_VscfVa9gqAxrgehwbKac4y4q_hsX4VSK8yUD=z12r6A@mail.gmail.com>
Message-ID: <5f1269ca.67a0.147514c91ba.Coremail.linzhenhua@163.com>

Thanks Paul. Your suggestion works. Just now I did not read your message carefully. I've tried to apply the "Merge Blocks" filter on both inputs at the same time, sorry for that.


? 2014-07-20 04:18:08?"Paul Edwards" <paul.m.edwards at gmail.com> ???

Try using "Merge Blocks" on each of the two input datasets before using the python calculator.


Regards,
Paul



On 19 July 2014 14:48, linzhenhua <linzhenhua at 163.com> wrote:

Hi

I want to compare the difference from the data from two dataset with the same grid topology. I load in two dataset separately, then apply the PythonCalculator filter, but immediately encounter the following error. What is the problem? The version is 4.1 for 32bit linux OS.

ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 0 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.


ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 815
vtkPVCompositeDataPipeline (0xb4711d0): Input for connection index 1 on input port index 0 for algorithm vtkPythonCalculator(0xb4aa0b0) is of type vtkMultiBlockDataSet, but a vtkDataSet is required.











_______________________________________________
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://public.kitware.com/mailman/listinfo/paraview



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140720/fa07bc2a/attachment.html>

From domican at ualberta.ca  Sun Jul 20 00:00:00 2014
From: domican at ualberta.ca (Kailyn Domican)
Date: Sat, 19 Jul 2014 22:00:00 -0600
Subject: [Paraview] Paraview 4.1.0: New Scale Bar Format
Message-ID: <CA+gGT99uOQfJJFvW=N0ziL+qi-QPdudcCgSLfwX-J-NEFzAjYA@mail.gmail.com>

Hi,

I have a quick question about Paraview's new scale bar.

Until recently I've been using ParaView-3.98.1-Linux-64bit, however I'm
interested in using Greek letters (matplotlib formatting) on the scale bar
to shorten up my scale titles. To use the Greek letters I switched to
ParaView-4.1.0-Linux-64bit.

I use a phython scripting to carry out the data analysis and was curious is
it possible to have the old style of scale bar as the new style is printing
on both sides of the bar. Ideally I'd like to keep the annotations as it
gives the max and min range on the Paraview plots.


Attached are Three .png's

   1. *H20_1_2:* Is the desired numbering format (all on the right side)
2. * 2_0A_i:* Is the desired title format however the numbering
   (annotations) appear on the opposite side.
   3.  *2_1A_i:* Is my attempt to increase the number of labels and turning
   annotations off *(DrawAnnotations=0, NumberOfLabels=8*), however this
   loses the desired max and min values.


Any help or advice would be greatly appreciated.

Thanks,
-- 
Kailyn Domican  B.A.  B.A.I.

Energy System Design Laboratory
Department of Mechanical Engineering
University of Alberta
Edmonton AB T6G 2G8 Canada
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140719/7284cdca/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: H20_1_2A_i_desired_number_format_on_one_side.png
Type: image/png
Size: 49712 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140719/7284cdca/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2_0A_i_CCL_New_Paraview_format.png
Type: image/png
Size: 28137 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140719/7284cdca/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2_1A_i_CCL_no_annotation_or_max_min_values.png
Type: image/png
Size: 18506 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140719/7284cdca/attachment-0005.png>

From duplyakin at uchicago.edu  Sun Jul 20 12:12:38 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Sun, 20 Jul 2014 11:12:38 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
Message-ID: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>

Hi all,

My name is Dmitry Duplyakin. I am a PhD student helping to build a
ParaViewWeb system at University of Chicago.

We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu 12.04
instances.

We have verified that PV builds without errors and that PVW launcher is
functioning (new entries are added to the proxy file, vis sessions are
created and are listening to ports in the specified range, etc.)

We are trying to visualize a simple cone:
(added app in launch.json)
"cone": {"cmd": ["${python_exec}",
"/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
"${port}"]}},

We have verified that vtk_web_cone.py actually gets called. In order to
test it, we used /pv/www/apps/TestApp/index.html as a template and created
/pv/www/apps/Cone/index.html where we have:
...
  var config = {
    sessionManagerURL: vtkWeb.properties.sessionManagerURL,
    application: "cone"
  };
...

Now when we access this app via a browser at: http://<hostname>/apps/Cone/
we either get a timeout or "connection can't be established" message.

In the apache error log we see:
[Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy: Error
reading from remote server returned by /paraview/, referer:
http://54.211.22.94/apps/Cone/
[Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does not
exist: /pv/www/ws

It appears that it has do to with Apache configuration, where we have:
ProxyPass        /paraview http://localhost:8080/paraview
ProxyPassReverse /paraview http://localhost:8080/paraview
RewriteEngine On
RewriteMap session-to-port txt:/pv/conf/proxy.conf
RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]

Do these Rewrite commands look right? How can their actions be logged and
verified?

Do we actually need ProxyPassReverse here?

Is it possible that we are missing a module or some additional
configuration in Apache?
# apachectl -t -D DUMP_MODULES
...
 proxy_module (shared)
 proxy_http_module (shared)
 proxy_wstunnel_module (shared)
 rewrite_module (shared)
...
Syntax OK

Any debugging advice?

Your help will be much appreciated and will allow to move forward with our
isntallation.

-------------------------------------------------------------------------------

Dmitry Duplyakin
PhD student, CS at University of Colorado - Boulder
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140720/5664e1e4/attachment.html>

From sebastien.jourdain at kitware.com  Sun Jul 20 20:01:44 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Sun, 20 Jul 2014 18:01:44 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
Message-ID: <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>

Everything should be explained here:
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04

But for that you need to have apache 2.4.6+ and make sure the launcher
configuration and apache one match.

Launcher side:

"sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect
to apache)/proxy?sessionId=${id}",

"proxy_file": "/data/proxy.txt"

Apache side

RewriteMap  session-to-port  txt:/data/proxy.txt

Then when a session start you can check the content of that /data/proxy.txt
and that should one line by running session with {sessionId} localhost:yyyyy

On the other hand you forgot that line in the config of your cone app:
"ready_line" : "Starting factory"

You can check is any pvpython process is running, on which port, see if
that match in the proxy file (/data/proxy.txt) and also looking at the log
directory with the output of the pvpython process.

A common error could also be that the apache does not have the right to
read the /data/proxy.txt file or that the launcher is not able to write it.

Good luck,

Seb


On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Hi all,
>
> My name is Dmitry Duplyakin. I am a PhD student helping to build a
> ParaViewWeb system at University of Chicago.
>
> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu 12.04
> instances.
>
> We have verified that PV builds without errors and that PVW launcher is
> functioning (new entries are added to the proxy file, vis sessions are
> created and are listening to ports in the specified range, etc.)
>
> We are trying to visualize a simple cone:
> (added app in launch.json)
> "cone": {"cmd": ["${python_exec}",
> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
> "${port}"]}},
>
> We have verified that vtk_web_cone.py actually gets called. In order to
> test it, we used /pv/www/apps/TestApp/index.html as a template and created
> /pv/www/apps/Cone/index.html where we have:
> ...
>   var config = {
>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>     application: "cone"
>   };
> ...
>
> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
> we either get a timeout or "connection can't be established" message.
>
> In the apache error log we see:
> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy: Error
> reading from remote server returned by /paraview/, referer:
> http://54.211.22.94/apps/Cone/
> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does not
> exist: /pv/www/ws
>
> It appears that it has do to with Apache configuration, where we have:
> ProxyPass        /paraview http://localhost:8080/paraview
> ProxyPassReverse /paraview http://localhost:8080/paraview
> RewriteEngine On
> RewriteMap session-to-port txt:/pv/conf/proxy.conf
> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>
> Do these Rewrite commands look right? How can their actions be logged and
> verified?
>
> Do we actually need ProxyPassReverse here?
>
> Is it possible that we are missing a module or some additional
> configuration in Apache?
> # apachectl -t -D DUMP_MODULES
> ...
>  proxy_module (shared)
>  proxy_http_module (shared)
>  proxy_wstunnel_module (shared)
>  rewrite_module (shared)
> ...
> Syntax OK
>
> Any debugging advice?
>
> Your help will be much appreciated and will allow to move forward with our
> isntallation.
>
>
> -------------------------------------------------------------------------------
>
> Dmitry Duplyakin
> PhD student, CS at University of Colorado - Boulder
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140720/4d7db56c/attachment.html>

From utkarsh.ayachit at kitware.com  Sun Jul 20 21:16:25 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 20 Jul 2014 21:16:25 -0400
Subject: [Paraview] Paraview 4.1.0: New Scale Bar Format
In-Reply-To: <CA+gGT99uOQfJJFvW=N0ziL+qi-QPdudcCgSLfwX-J-NEFzAjYA@mail.gmail.com>
References: <CA+gGT99uOQfJJFvW=N0ziL+qi-QPdudcCgSLfwX-J-NEFzAjYA@mail.gmail.com>
Message-ID: <CADHSJjBkOGN=HPRT-udFm=3H8nNL=btdyuStEw3Y1n=jS9qArQ@mail.gmail.com>

Kailyn,

Not in 4.1, alas. This has been addressed in the development version of
ParaView (http://www.paraview.org/Bug/view.php?id=14686) and will be
available in the next release. You can download the nightly development
binaries from paraview.org. Note that these are the bleeding edge binaries
and may have issues/bug introduced by ongoing development.

Utkarsh


On Sun, Jul 20, 2014 at 12:00 AM, Kailyn Domican <domican at ualberta.ca>
wrote:

> Hi,
>
> I have a quick question about Paraview's new scale bar.
>
> Until recently I've been using ParaView-3.98.1-Linux-64bit, however I'm
> interested in using Greek letters (matplotlib formatting) on the scale bar
> to shorten up my scale titles. To use the Greek letters I switched to
> ParaView-4.1.0-Linux-64bit.
>
> I use a phython scripting to carry out the data analysis and was curious
> is it possible to have the old style of scale bar as the new style is
> printing on both sides of the bar. Ideally I'd like to keep the annotations
> as it gives the max and min range on the Paraview plots.
>
>
> Attached are Three .png's
>
>    1. *H20_1_2:* Is the desired numbering format (all on the right side)
> 2. * 2_0A_i:* Is the desired title format however the numbering
>    (annotations) appear on the opposite side.
>    3.  *2_1A_i:* Is my attempt to increase the number of labels and
>    turning annotations off *(DrawAnnotations=0, NumberOfLabels=8*),
>    however this loses the desired max and min values.
>
>
> Any help or advice would be greatly appreciated.
>
> Thanks,
> --
> Kailyn Domican  B.A.  B.A.I.
>
> Energy System Design Laboratory
> Department of Mechanical Engineering
> University of Alberta
> Edmonton AB T6G 2G8 Canada
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140720/a398fd1f/attachment-0001.html>

From markus.fuger at outlook.com  Mon Jul 21 03:35:59 2014
From: markus.fuger at outlook.com (Markus Fuger)
Date: Mon, 21 Jul 2014 09:35:59 +0200
Subject: [Paraview] Use vtkLookupTable for PV scalarbar (and rendering)
Message-ID: <DUB111-W109DAB10373C26DA58AB97182F00@phx.gbl>

Hello everybody,

I am developing some Python code that uses VTK quite intensively. I as well needed to create certain color bars and lookup tables. Due to the fact that I am not intending to replace ParaView for the users completely but want to make them use the same lookup tables (which are file dependent) - I provided some script that loads the new ParaView style lookup tables (using macros and the GetLookupTableForArray command in PV)
I was now wondering if I could use my library and somehow register the created vtkLookupTable to the PVservermanager so that I can assign it to the array within the PV pipeline objects data.

I hope it is clear what I want to do - if not here in other words.
I want to "link" the vtkLookupTable to the mapper of the scalarbar and displayed dataset in ParaView.

Thanks for your help,
Markus
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/7c72a5fc/attachment.html>

From duplyakin at uchicago.edu  Mon Jul 21 10:01:28 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Mon, 21 Jul 2014 09:01:28 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
Message-ID: <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>

Thank you very much, Sebastien!

Launcher side:
>
> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>
> "proxy_file": "/data/proxy.txt"
>
> This is exactly what we have in our launcher:

  "sessionURL": "ws://${host}:${port}/ws",

  "host": "localhost",

  "port": 8080,

Your sessionURL looks different. Do you actually use "proxy?sessionId="
there? Ours came directly from the script you've suggested earlier:
http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD


> Apache side
>
> RewriteMap  session-to-port  txt:/data/proxy.txt
>
> In Apache we have:
RewriteEngine On
RewriteMap session-to-port txt:/pv/conf/proxy.conf
RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]

>
> Then when a session start you can check the content of that
> /data/proxy.txt and that should one line by running session with
> {sessionId} localhost:yyyyy
>

Verified that those entires are added to the file and have the right
format.


> On the other hand you forgot that line in the config of your cone app:
> "ready_line" : "Starting factory"
>
> Thanks! Added it and now the app looks like this:

"cone": {"cmd": ["${python_exec}",
"/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
"${port}"], "ready_line" : "Starting factory"}},


> You can check is any pvpython process is running, on which port, see if
> that match in the proxy file (/data/proxy.txt) and also looking at the log
> directory with the output of the pvpython process.
>
> A common error could also be that the apache does not have the right to
> read the /data/proxy.txt file or that the launcher is not able to write it.
>

Verified that launcher can write it and that entries are added.

These are the rest of our questions (we need to sort these out because they
have caused some confusion and we want to clear things up and do not come
back to these issues anymore):

- can we specifically log and debug Rewrite rule actions?
- do we actually need ProxyPassReverse in Apache?
- what particular modules in Apache are required? So far we have:
proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
we need proxy_wstunnel_module or not.
- in launch.json there are two particular lines:
"host": "localhost",
"resources": [{"port_range": [9901, 9999], "host": "localhost"}],
where we have some confusion about using "localhost" vs. "0.0.0.0". What
exactly should we use in either case?

Appreciate your help!


> Good luck,
>
> Seb
>
>
> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <duplyakin at uchicago.edu
> > wrote:
>
>> Hi all,
>>
>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>> ParaViewWeb system at University of Chicago.
>>
>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu 12.04
>> instances.
>>
>> We have verified that PV builds without errors and that PVW launcher is
>> functioning (new entries are added to the proxy file, vis sessions are
>> created and are listening to ports in the specified range, etc.)
>>
>> We are trying to visualize a simple cone:
>> (added app in launch.json)
>> "cone": {"cmd": ["${python_exec}",
>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>> "${port}"]}},
>>
>> We have verified that vtk_web_cone.py actually gets called. In order to
>> test it, we used /pv/www/apps/TestApp/index.html as a template and created
>> /pv/www/apps/Cone/index.html where we have:
>> ...
>>   var config = {
>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>     application: "cone"
>>   };
>> ...
>>
>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>> we either get a timeout or "connection can't be established" message.
>>
>> In the apache error log we see:
>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy: Error
>> reading from remote server returned by /paraview/, referer:
>> http://54.211.22.94/apps/Cone/
>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does not
>> exist: /pv/www/ws
>>
>> It appears that it has do to with Apache configuration, where we have:
>> ProxyPass        /paraview http://localhost:8080/paraview
>> ProxyPassReverse /paraview http://localhost:8080/paraview
>> RewriteEngine On
>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>
>> Do these Rewrite commands look right? How can their actions be logged and
>> verified?
>>
>> Do we actually need ProxyPassReverse here?
>>
>> Is it possible that we are missing a module or some additional
>> configuration in Apache?
>> # apachectl -t -D DUMP_MODULES
>> ...
>>  proxy_module (shared)
>>  proxy_http_module (shared)
>>  proxy_wstunnel_module (shared)
>>  rewrite_module (shared)
>> ...
>> Syntax OK
>>
>> Any debugging advice?
>>
>> Your help will be much appreciated and will allow to move forward with
>> our isntallation.
>>
>>
>> -------------------------------------------------------------------------------
>>
>> Dmitry Duplyakin
>> PhD student, CS at University of Colorado - Boulder
>>
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/e05d140b/attachment.html>

From henry.lehmann at informatik.tu-freiberg.de  Mon Jul 21 09:59:54 2014
From: henry.lehmann at informatik.tu-freiberg.de (Henry Lehmann)
Date: Mon, 21 Jul 2014 15:59:54 +0200
Subject: [Paraview] AMR Cut Plane
In-Reply-To: <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
 <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
Message-ID: <53CD1CDA.7020206@informatik.tu-freiberg.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Paraview Users,

i am recently working with vtkOverlappingAMR. i set up one of this
data sets using the "Image to AMR" filter in paraview, which basicly
creates an octree with 4 levels and 512 blocks on level 4 in my setup.
so i basicly converted mydata.vti into mydata.vth.

now i want to use mydata.vth in order to quickly calculate the result
of an arbitrary pipeline and save time adjusting the parameters of the
pipeline. i want to adjust the parameters on level 0 and then increase
the level to see the full resolution result.

for example i have the pipeline: mydata.vth (vtkOverlappingAMR) -> AMR
Cut Plane. now i move the cut plane and apply to see the result. when
increasing the level from 1 to 2 in the reader i get a strange result.
it looks like paraview doesnt remove the regions in which the amr
levels overlap. this means the amr cut plane cuts out the data on
level 0 and on level 1. Since Image to AMR creates an octree in which
all lower levels are overlapping with higher ones, the lower levels
always cover the higher resolution results when setting the level
above 1 in the amr reader.

how can i fix this?

Best regards,
Henry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTzRzaAAoJEM0zIsxevdB2dt0H/RoNtiBcpmvl8jmqqCdQXRm9
PeUCcNw57sZHF3H8Wcl18vL8Vz/38h+T9JcpWEDEj33atElRHeKfXXkpMkaxz9qN
YJKvTgPh4i94v7mfg+LnQk4LvgiTIv/3cYwD5mz2ga5EMC/FflLuZluR46JllZLi
AS+arxbVEIW5yqEMFlrEtLoItqXkLIVUCjdfTbbfEmaBW1w73rA4/7tSVW7LaSKi
yMt8qPOgVTis89dSN1v/d750X7Rz0HLZGmFz0QdasLJy9PHBaFo6Uz8mjEH0hJ5t
kZdxZISIpxxl9GQNDKwZVRF6t1h8MqyOPwhQEjQHJOnHkbWS927xjyezn/8rDv0=
=K0aa
-----END PGP SIGNATURE-----

From sebastien.jourdain at kitware.com  Mon Jul 21 11:02:15 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 21 Jul 2014 09:02:15 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
Message-ID: <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>

Hi Dmitry,

First of all you need to understand the role of apache here in order to see
how the configuration should be.
As you may know, you can use ParaViewWeb without Apache, but such setup is
not meant for production.

The list below is what you get when you add Apache:
- Apache can be use to serve the static content (html, js, png, css...)
- Apache provide a single entry point host + port. This prevent
cross-domain issue or firewall limitation.
- Apache will relay the WebSocket communication to the proper ParaViewWeb
instance on the backend based on a session ID. This mean that the
ParaViewWeb process DOES NOT need to be on the same machine as the Apache
Web Server.

Then you need to understand how the launcher works and its role.
In ParaViewWeb a launcher is used to start a new visualization process for
a given user. This simply mean running a command line with some dynamic
parameters like the port number on which this specific instance should
listen.
So when a user connect to the system and request a new visualization
session, it is the responsibility of the launcher to start the process and
let the client know on which WebSocket URL it should connect to in order to
reach the requested visualization session.

In a setup that DOES NOT contain Apache, we can not use the same port as
the main server (the process would not start). Hence, we start it with some
port and we let the user know that it should connect to
"ws://{host}:{port}/ws" where host and port get replaced with the set that
was used to create the process.

See section "resources" in launcher configuration.

BUT with Apache that is different, now we have a process which is meant to
relay the communication to the backend using the port and host that Apache
is using. So the launcher should let the client know what URL they should
use so Apache could handle it and forward it to the backend. Hence the
ws://{apache_host}/proxy?sessionId=${id}.
In the same time to keep track on which host/port a process is running the
launcher generate a text file with the proper mapping.
That mapping file is then used inside Apache to figure out how it should
establish the connection to the backend.

This should help you understand how to fix your configuration.
Moreover, here is the remaining set of questions:

> can we specifically log and debug Rewrite rule actions?

Don't know, Google will be your friend here...

> do we actually need ProxyPassReverse in Apache?

Don't know, Google will be your friend here as well as the documentation on
how to setup ParaViewWeb on Ubuntu 14LTS.

> what particular modules in Apache are required?

Read the documentation, the list is minimum and provided in it.

> in launch.json there are two particular lines host/resources:

So the "host" is to select the proper network card when you have several
for the actual launcher server.

Then the resources are use for process management and URL generation for
the client. Which mean, what name should be used by Apache to connect to
the machine that actually run a ParaViewWeb process.

Seb


On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Thank you very much, Sebastien!
>
> Launcher side:
>>
>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>
>> "proxy_file": "/data/proxy.txt"
>>
>> This is exactly what we have in our launcher:
>
>   "sessionURL": "ws://${host}:${port}/ws",
>
>   "host": "localhost",
>
>   "port": 8080,
>
> Your sessionURL looks different. Do you actually use "proxy?sessionId="
> there? Ours came directly from the script you've suggested earlier:
> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>
>
>> Apache side
>>
>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>
>> In Apache we have:
> RewriteEngine On
> RewriteMap session-to-port txt:/pv/conf/proxy.conf
> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>
>
>> Then when a session start you can check the content of that
>> /data/proxy.txt and that should one line by running session with
>> {sessionId} localhost:yyyyy
>>
>
> Verified that those entires are added to the file and have the right
> format.
>
>
>> On the other hand you forgot that line in the config of your cone app:
>> "ready_line" : "Starting factory"
>>
>> Thanks! Added it and now the app looks like this:
>
> "cone": {"cmd": ["${python_exec}",
> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
> "${port}"], "ready_line" : "Starting factory"}},
>
>
>> You can check is any pvpython process is running, on which port, see if
>> that match in the proxy file (/data/proxy.txt) and also looking at the log
>> directory with the output of the pvpython process.
>>
>> A common error could also be that the apache does not have the right to
>> read the /data/proxy.txt file or that the launcher is not able to write it.
>>
>
> Verified that launcher can write it and that entries are added.
>
> These are the rest of our questions (we need to sort these out because
> they have caused some confusion and we want to clear things up and do not
> come back to these issues anymore):
>
> - can we specifically log and debug Rewrite rule actions?
> - do we actually need ProxyPassReverse in Apache?
> - what particular modules in Apache are required? So far we have:
> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
> we need proxy_wstunnel_module or not.
> - in launch.json there are two particular lines:
> "host": "localhost",
> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
> where we have some confusion about using "localhost" vs. "0.0.0.0". What
> exactly should we use in either case?
>
> Appreciate your help!
>
>
>> Good luck,
>>
>> Seb
>>
>>
>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>> duplyakin at uchicago.edu> wrote:
>>
>>> Hi all,
>>>
>>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>>> ParaViewWeb system at University of Chicago.
>>>
>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu 12.04
>>> instances.
>>>
>>> We have verified that PV builds without errors and that PVW launcher is
>>> functioning (new entries are added to the proxy file, vis sessions are
>>> created and are listening to ports in the specified range, etc.)
>>>
>>> We are trying to visualize a simple cone:
>>> (added app in launch.json)
>>> "cone": {"cmd": ["${python_exec}",
>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>> "${port}"]}},
>>>
>>> We have verified that vtk_web_cone.py actually gets called. In order to
>>> test it, we used /pv/www/apps/TestApp/index.html as a template and created
>>> /pv/www/apps/Cone/index.html where we have:
>>> ...
>>>   var config = {
>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>     application: "cone"
>>>   };
>>> ...
>>>
>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>> we either get a timeout or "connection can't be established" message.
>>>
>>> In the apache error log we see:
>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy: Error
>>> reading from remote server returned by /paraview/, referer:
>>> http://54.211.22.94/apps/Cone/
>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does
>>> not exist: /pv/www/ws
>>>
>>> It appears that it has do to with Apache configuration, where we have:
>>> ProxyPass        /paraview http://localhost:8080/paraview
>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>> RewriteEngine On
>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>
>>> Do these Rewrite commands look right? How can their actions be logged
>>> and verified?
>>>
>>> Do we actually need ProxyPassReverse here?
>>>
>>> Is it possible that we are missing a module or some additional
>>> configuration in Apache?
>>> # apachectl -t -D DUMP_MODULES
>>> ...
>>>  proxy_module (shared)
>>>  proxy_http_module (shared)
>>>  proxy_wstunnel_module (shared)
>>>  rewrite_module (shared)
>>> ...
>>> Syntax OK
>>>
>>> Any debugging advice?
>>>
>>> Your help will be much appreciated and will allow to move forward with
>>> our isntallation.
>>>
>>>
>>> -------------------------------------------------------------------------------
>>>
>>> Dmitry Duplyakin
>>> PhD student, CS at University of Colorado - Boulder
>>>
>>>
>>> _______________________________________________
>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/0457e9ac/attachment-0001.html>

From duplyakin at uchicago.edu  Mon Jul 21 12:58:35 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Mon, 21 Jul 2014 11:58:35 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
Message-ID: <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>

Thanks for this detailed description! The process is starting to make sense
and we can communicate more efficiently about our configuration and
problems.

Here is our complete launch.json (with the right sessionURL for a config
with Apache, according to your email):
{
"configuration": {
  "content": "/pv/www",
  "log_dir": "/pv/logs",
  "host": "localhost",
  "endpoint": "paraview",
  "sessionURL": "ws://${host}/proxy?sessionId=${id}",
  "timeout": 5,
  "upload_dir": "/pv/data",
  "fields": ["file", "host", "port", "updir"],
  "port": 8080,
  "proxy_file": "/pv/conf/proxy.conf"},
"apps": {
  "data_prober": {"cmd": ["${python_exec}",
"${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
"--data-dir", "${data}"], "ready_line" : "Starting factory"},
  "pipeline": {"cmd": ["${python_exec}",
"${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
"--data-dir", "${data}"], "ready_line" : "Starting factory"},
  "loader": {"cmd": ["${python_exec}",
"${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
"--data-dir", "${data}"], "ready_line" : "Starting factory"},
  "cone": {"cmd": ["${python_exec}",
"/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
"${port}"], "ready_line" : "Starting factory"}},
"properties": {
  "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
  "data": "/pv/data",
  "python_exec": "/pv/paraview/bin/pvpython"},
"resources": [{"port_range": [9901, 9999], "host": "localhost"}],
"sessionData": {"updir": "/Home"}
}

Apache host file:
<VirtualHost *:80>
        ServerAdmin webmaster at localhost
        DocumentRoot /pv/www
        <Directory /pv/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

        ProxyPass        /paraview http://localhost:8080/paraview

        RewriteEngine On
        RewriteMap session-to-port txt:/pv/conf/proxy.conf
        RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
        RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]

        RewriteLog "/var/log/apache2/rewrite.log"
        RewriteLogLevel 3
        ErrorLog ${APACHE_LOG_DIR}/error.log
        LogLevel debug
        CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Now when we access http://<PVW server>/apps/Cone/ in the browser,
it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
server>:/paraview/","application":"cone"}. Then Launcher starts a process
listening to a port from the range (e.g. 9999). We can see that process:
ps auwx | grep cone
root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
/pv/paraview/lib/paraview-4.1/pvpython
/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999

After that we get a session timeout and this response: "Session did not
start before timeout expired. Check session logs."

Any further advice?


On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Hi Dmitry,
>
> First of all you need to understand the role of apache here in order to
> see how the configuration should be.
> As you may know, you can use ParaViewWeb without Apache, but such setup is
> not meant for production.
>
> The list below is what you get when you add Apache:
> - Apache can be use to serve the static content (html, js, png, css...)
> - Apache provide a single entry point host + port. This prevent
> cross-domain issue or firewall limitation.
> - Apache will relay the WebSocket communication to the proper ParaViewWeb
> instance on the backend based on a session ID. This mean that the
> ParaViewWeb process DOES NOT need to be on the same machine as the Apache
> Web Server.
>
> Then you need to understand how the launcher works and its role.
> In ParaViewWeb a launcher is used to start a new visualization process for
> a given user. This simply mean running a command line with some dynamic
> parameters like the port number on which this specific instance should
> listen.
> So when a user connect to the system and request a new visualization
> session, it is the responsibility of the launcher to start the process and
> let the client know on which WebSocket URL it should connect to in order to
> reach the requested visualization session.
>
> In a setup that DOES NOT contain Apache, we can not use the same port as
> the main server (the process would not start). Hence, we start it with some
> port and we let the user know that it should connect to
> "ws://{host}:{port}/ws" where host and port get replaced with the set that
> was used to create the process.
>
> See section "resources" in launcher configuration.
>
> BUT with Apache that is different, now we have a process which is meant to
> relay the communication to the backend using the port and host that Apache
> is using. So the launcher should let the client know what URL they should
> use so Apache could handle it and forward it to the backend. Hence the
> ws://{apache_host}/proxy?sessionId=${id}.
> In the same time to keep track on which host/port a process is running the
> launcher generate a text file with the proper mapping.
> That mapping file is then used inside Apache to figure out how it should
> establish the connection to the backend.
>
> This should help you understand how to fix your configuration.
> Moreover, here is the remaining set of questions:
>
> > can we specifically log and debug Rewrite rule actions?
>
> Don't know, Google will be your friend here...
>
> > do we actually need ProxyPassReverse in Apache?
>
> Don't know, Google will be your friend here as well as the documentation
> on how to setup ParaViewWeb on Ubuntu 14LTS.
>
> > what particular modules in Apache are required?
>
> Read the documentation, the list is minimum and provided in it.
>
> > in launch.json there are two particular lines host/resources:
>
> So the "host" is to select the proper network card when you have several
> for the actual launcher server.
>
> Then the resources are use for process management and URL generation for
> the client. Which mean, what name should be used by Apache to connect to
> the machine that actually run a ParaViewWeb process.
>
> Seb
>
>
> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> Thank you very much, Sebastien!
>>
>> Launcher side:
>>>
>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>
>>> "proxy_file": "/data/proxy.txt"
>>>
>>> This is exactly what we have in our launcher:
>>
>>   "sessionURL": "ws://${host}:${port}/ws",
>>
>>   "host": "localhost",
>>
>>   "port": 8080,
>>
>> Your sessionURL looks different. Do you actually use "proxy?sessionId="
>> there? Ours came directly from the script you've suggested earlier:
>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>
>>
>>> Apache side
>>>
>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>
>>> In Apache we have:
>> RewriteEngine On
>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>
>>
>>> Then when a session start you can check the content of that
>>> /data/proxy.txt and that should one line by running session with
>>> {sessionId} localhost:yyyyy
>>>
>>
>> Verified that those entires are added to the file and have the right
>> format.
>>
>>
>>> On the other hand you forgot that line in the config of your cone app:
>>> "ready_line" : "Starting factory"
>>>
>>>  Thanks! Added it and now the app looks like this:
>>
>> "cone": {"cmd": ["${python_exec}",
>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>> "${port}"], "ready_line" : "Starting factory"}},
>>
>>
>>> You can check is any pvpython process is running, on which port, see if
>>> that match in the proxy file (/data/proxy.txt) and also looking at the log
>>> directory with the output of the pvpython process.
>>>
>>> A common error could also be that the apache does not have the right to
>>> read the /data/proxy.txt file or that the launcher is not able to write it.
>>>
>>
>> Verified that launcher can write it and that entries are added.
>>
>> These are the rest of our questions (we need to sort these out because
>> they have caused some confusion and we want to clear things up and do not
>> come back to these issues anymore):
>>
>> - can we specifically log and debug Rewrite rule actions?
>> - do we actually need ProxyPassReverse in Apache?
>> - what particular modules in Apache are required? So far we have:
>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>> we need proxy_wstunnel_module or not.
>> - in launch.json there are two particular lines:
>> "host": "localhost",
>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>> where we have some confusion about using "localhost" vs. "0.0.0.0". What
>> exactly should we use in either case?
>>
>> Appreciate your help!
>>
>>
>>> Good luck,
>>>
>>> Seb
>>>
>>>
>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> Hi all,
>>>>
>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>>>> ParaViewWeb system at University of Chicago.
>>>>
>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu 12.04
>>>> instances.
>>>>
>>>> We have verified that PV builds without errors and that PVW launcher is
>>>> functioning (new entries are added to the proxy file, vis sessions are
>>>> created and are listening to ports in the specified range, etc.)
>>>>
>>>> We are trying to visualize a simple cone:
>>>> (added app in launch.json)
>>>> "cone": {"cmd": ["${python_exec}",
>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>> "${port}"]}},
>>>>
>>>> We have verified that vtk_web_cone.py actually gets called. In order to
>>>> test it, we used /pv/www/apps/TestApp/index.html as a template and created
>>>> /pv/www/apps/Cone/index.html where we have:
>>>> ...
>>>>   var config = {
>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>     application: "cone"
>>>>   };
>>>> ...
>>>>
>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>> we either get a timeout or "connection can't be established" message.
>>>>
>>>> In the apache error log we see:
>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy:
>>>> Error reading from remote server returned by /paraview/, referer:
>>>> http://54.211.22.94/apps/Cone/
>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does
>>>> not exist: /pv/www/ws
>>>>
>>>> It appears that it has do to with Apache configuration, where we have:
>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>> RewriteEngine On
>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>
>>>> Do these Rewrite commands look right? How can their actions be logged
>>>> and verified?
>>>>
>>>> Do we actually need ProxyPassReverse here?
>>>>
>>>> Is it possible that we are missing a module or some additional
>>>> configuration in Apache?
>>>> # apachectl -t -D DUMP_MODULES
>>>> ...
>>>>  proxy_module (shared)
>>>>  proxy_http_module (shared)
>>>>  proxy_wstunnel_module (shared)
>>>>  rewrite_module (shared)
>>>> ...
>>>> Syntax OK
>>>>
>>>> Any debugging advice?
>>>>
>>>> Your help will be much appreciated and will allow to move forward with
>>>> our isntallation.
>>>>
>>>>
>>>> -------------------------------------------------------------------------------
>>>>
>>>> Dmitry Duplyakin
>>>> PhD student, CS at University of Colorado - Boulder
>>>>
>>>>
>>>> _______________________________________________
>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/085776a6/attachment-0001.html>

From sebastien.jourdain at kitware.com  Mon Jul 21 13:59:45 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 21 Jul 2014 11:59:45 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
Message-ID: <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>

Hi Dmitry,

you may still have a typo

=> "ws://${host}/proxy?sessionId=${id}",

${host} should have been replaced with a static string that match the host
that the web browser is using to reach apache.

Moreover, I forgot to mention that you need to add "-f" in your set of
arguments. That will force some output generation to fill some buffer which
will allow the launcher to detect when the server is actually ready.

I've noticed that the documentation is missing them. Don't know why... Will
update it at some point.
Although this page show that option:
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher

And the value for "timeout" should be way bigger than 5. Like 25 maybe.

Seb



On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Thanks for this detailed description! The process is starting to make
> sense and we can communicate more efficiently about our configuration and
> problems.
>
> Here is our complete launch.json (with the right sessionURL for a config
> with Apache, according to your email):
> {
> "configuration": {
>   "content": "/pv/www",
>   "log_dir": "/pv/logs",
>   "host": "localhost",
>   "endpoint": "paraview",
>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>   "timeout": 5,
>   "upload_dir": "/pv/data",
>   "fields": ["file", "host", "port", "updir"],
>   "port": 8080,
>   "proxy_file": "/pv/conf/proxy.conf"},
> "apps": {
>   "data_prober": {"cmd": ["${python_exec}",
> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>   "pipeline": {"cmd": ["${python_exec}",
> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>   "loader": {"cmd": ["${python_exec}",
> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>   "cone": {"cmd": ["${python_exec}",
> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
> "${port}"], "ready_line" : "Starting factory"}},
> "properties": {
>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>   "data": "/pv/data",
>   "python_exec": "/pv/paraview/bin/pvpython"},
> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
> "sessionData": {"updir": "/Home"}
> }
>
> Apache host file:
> <VirtualHost *:80>
>         ServerAdmin webmaster at localhost
>         DocumentRoot /pv/www
>         <Directory /pv/www/>
>                 Options Indexes FollowSymLinks MultiViews
>                 AllowOverride None
>                 Order allow,deny
>                 allow from all
>         </Directory>
>
>         ProxyPass        /paraview http://localhost:8080/paraview
>
>         RewriteEngine On
>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>
>         RewriteLog "/var/log/apache2/rewrite.log"
>         RewriteLogLevel 3
>         ErrorLog ${APACHE_LOG_DIR}/error.log
>         LogLevel debug
>         CustomLog ${APACHE_LOG_DIR}/access.log combined
> </VirtualHost>
>
> Now when we access http://<PVW server>/apps/Cone/ in the browser,
> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
> server>:/paraview/","application":"cone"}. Then Launcher starts a process
> listening to a port from the range (e.g. 9999). We can see that process:
> ps auwx | grep cone
> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
> /pv/paraview/lib/paraview-4.1/pvpython
> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>
> After that we get a session timeout and this response: "Session did not
> start before timeout expired. Check session logs."
>
> Any further advice?
>
>
> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Hi Dmitry,
>>
>> First of all you need to understand the role of apache here in order to
>> see how the configuration should be.
>> As you may know, you can use ParaViewWeb without Apache, but such setup
>> is not meant for production.
>>
>> The list below is what you get when you add Apache:
>> - Apache can be use to serve the static content (html, js, png, css...)
>> - Apache provide a single entry point host + port. This prevent
>> cross-domain issue or firewall limitation.
>> - Apache will relay the WebSocket communication to the proper ParaViewWeb
>> instance on the backend based on a session ID. This mean that the
>> ParaViewWeb process DOES NOT need to be on the same machine as the Apache
>> Web Server.
>>
>> Then you need to understand how the launcher works and its role.
>> In ParaViewWeb a launcher is used to start a new visualization process
>> for a given user. This simply mean running a command line with some dynamic
>> parameters like the port number on which this specific instance should
>> listen.
>> So when a user connect to the system and request a new visualization
>> session, it is the responsibility of the launcher to start the process and
>> let the client know on which WebSocket URL it should connect to in order to
>> reach the requested visualization session.
>>
>> In a setup that DOES NOT contain Apache, we can not use the same port as
>> the main server (the process would not start). Hence, we start it with some
>> port and we let the user know that it should connect to
>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>> was used to create the process.
>>
>> See section "resources" in launcher configuration.
>>
>> BUT with Apache that is different, now we have a process which is meant
>> to relay the communication to the backend using the port and host that
>> Apache is using. So the launcher should let the client know what URL they
>> should use so Apache could handle it and forward it to the backend. Hence
>> the ws://{apache_host}/proxy?sessionId=${id}.
>> In the same time to keep track on which host/port a process is running
>> the launcher generate a text file with the proper mapping.
>> That mapping file is then used inside Apache to figure out how it should
>> establish the connection to the backend.
>>
>> This should help you understand how to fix your configuration.
>> Moreover, here is the remaining set of questions:
>>
>> > can we specifically log and debug Rewrite rule actions?
>>
>> Don't know, Google will be your friend here...
>>
>> > do we actually need ProxyPassReverse in Apache?
>>
>> Don't know, Google will be your friend here as well as the documentation
>> on how to setup ParaViewWeb on Ubuntu 14LTS.
>>
>> > what particular modules in Apache are required?
>>
>> Read the documentation, the list is minimum and provided in it.
>>
>> > in launch.json there are two particular lines host/resources:
>>
>> So the "host" is to select the proper network card when you have several
>> for the actual launcher server.
>>
>> Then the resources are use for process management and URL generation for
>> the client. Which mean, what name should be used by Apache to connect to
>> the machine that actually run a ParaViewWeb process.
>>
>> Seb
>>
>>
>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <duplyakin at uchicago.edu
>> > wrote:
>>
>>> Thank you very much, Sebastien!
>>>
>>> Launcher side:
>>>>
>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>
>>>> "proxy_file": "/data/proxy.txt"
>>>>
>>>> This is exactly what we have in our launcher:
>>>
>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>
>>>   "host": "localhost",
>>>
>>>   "port": 8080,
>>>
>>> Your sessionURL looks different. Do you actually use "proxy?sessionId="
>>> there? Ours came directly from the script you've suggested earlier:
>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>
>>>
>>>> Apache side
>>>>
>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>
>>>> In Apache we have:
>>> RewriteEngine On
>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>
>>>
>>>> Then when a session start you can check the content of that
>>>> /data/proxy.txt and that should one line by running session with
>>>> {sessionId} localhost:yyyyy
>>>>
>>>
>>> Verified that those entires are added to the file and have the right
>>> format.
>>>
>>>
>>>> On the other hand you forgot that line in the config of your cone app:
>>>> "ready_line" : "Starting factory"
>>>>
>>>>  Thanks! Added it and now the app looks like this:
>>>
>>> "cone": {"cmd": ["${python_exec}",
>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>> "${port}"], "ready_line" : "Starting factory"}},
>>>
>>>
>>>> You can check is any pvpython process is running, on which port, see if
>>>> that match in the proxy file (/data/proxy.txt) and also looking at the log
>>>> directory with the output of the pvpython process.
>>>>
>>>> A common error could also be that the apache does not have the right to
>>>> read the /data/proxy.txt file or that the launcher is not able to write it.
>>>>
>>>
>>> Verified that launcher can write it and that entries are added.
>>>
>>> These are the rest of our questions (we need to sort these out because
>>> they have caused some confusion and we want to clear things up and do not
>>> come back to these issues anymore):
>>>
>>> - can we specifically log and debug Rewrite rule actions?
>>> - do we actually need ProxyPassReverse in Apache?
>>> - what particular modules in Apache are required? So far we have:
>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>> we need proxy_wstunnel_module or not.
>>> - in launch.json there are two particular lines:
>>> "host": "localhost",
>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>> where we have some confusion about using "localhost" vs. "0.0.0.0". What
>>> exactly should we use in either case?
>>>
>>> Appreciate your help!
>>>
>>>
>>>> Good luck,
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>>>>> ParaViewWeb system at University of Chicago.
>>>>>
>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu
>>>>> 12.04 instances.
>>>>>
>>>>> We have verified that PV builds without errors and that PVW launcher
>>>>> is functioning (new entries are added to the proxy file, vis sessions are
>>>>> created and are listening to ports in the specified range, etc.)
>>>>>
>>>>> We are trying to visualize a simple cone:
>>>>> (added app in launch.json)
>>>>> "cone": {"cmd": ["${python_exec}",
>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>> "${port}"]}},
>>>>>
>>>>> We have verified that vtk_web_cone.py actually gets called. In order
>>>>> to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>> ...
>>>>>   var config = {
>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>     application: "cone"
>>>>>   };
>>>>> ...
>>>>>
>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>> we either get a timeout or "connection can't be established" message.
>>>>>
>>>>> In the apache error log we see:
>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy:
>>>>> Error reading from remote server returned by /paraview/, referer:
>>>>> http://54.211.22.94/apps/Cone/
>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does
>>>>> not exist: /pv/www/ws
>>>>>
>>>>> It appears that it has do to with Apache configuration, where we have:
>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>> RewriteEngine On
>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>
>>>>> Do these Rewrite commands look right? How can their actions be logged
>>>>> and verified?
>>>>>
>>>>> Do we actually need ProxyPassReverse here?
>>>>>
>>>>> Is it possible that we are missing a module or some additional
>>>>> configuration in Apache?
>>>>> # apachectl -t -D DUMP_MODULES
>>>>> ...
>>>>>  proxy_module (shared)
>>>>>  proxy_http_module (shared)
>>>>>  proxy_wstunnel_module (shared)
>>>>>  rewrite_module (shared)
>>>>> ...
>>>>> Syntax OK
>>>>>
>>>>> Any debugging advice?
>>>>>
>>>>> Your help will be much appreciated and will allow to move forward with
>>>>> our isntallation.
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------------------
>>>>>
>>>>> Dmitry Duplyakin
>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/a794d3fe/attachment-0001.html>

From duplyakin at uchicago.edu  Mon Jul 21 15:07:17 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Mon, 21 Jul 2014 14:07:17 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
Message-ID: <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>

This helped tremendously!

Both "-f" and "${host}" now make a lot more sense.

POST works fine now and we can see the Rewrite rule in action. Something
there still needs attention and we are investigating further.

Thanks for you patience and all the help that allows us to move forward.


On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Hi Dmitry,
>
> you may still have a typo
>
> => "ws://${host}/proxy?sessionId=${id}",
>
> ${host} should have been replaced with a static string that match the host
> that the web browser is using to reach apache.
>
> Moreover, I forgot to mention that you need to add "-f" in your set of
> arguments. That will force some output generation to fill some buffer which
> will allow the launcher to detect when the server is actually ready.
>
> I've noticed that the documentation is missing them. Don't know why...
> Will update it at some point.
> Although this page show that option:
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>
> And the value for "timeout" should be way bigger than 5. Like 25 maybe.
>
> Seb
>
>
>
> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <duplyakin at uchicago.edu
> > wrote:
>
>> Thanks for this detailed description! The process is starting to make
>> sense and we can communicate more efficiently about our configuration and
>> problems.
>>
>> Here is our complete launch.json (with the right sessionURL for a config
>> with Apache, according to your email):
>> {
>> "configuration": {
>>   "content": "/pv/www",
>>   "log_dir": "/pv/logs",
>>   "host": "localhost",
>>   "endpoint": "paraview",
>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>   "timeout": 5,
>>   "upload_dir": "/pv/data",
>>   "fields": ["file", "host", "port", "updir"],
>>   "port": 8080,
>>   "proxy_file": "/pv/conf/proxy.conf"},
>> "apps": {
>>   "data_prober": {"cmd": ["${python_exec}",
>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>   "pipeline": {"cmd": ["${python_exec}",
>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>   "loader": {"cmd": ["${python_exec}",
>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>    "cone": {"cmd": ["${python_exec}",
>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>> "${port}"], "ready_line" : "Starting factory"}},
>> "properties": {
>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>   "data": "/pv/data",
>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>> "sessionData": {"updir": "/Home"}
>> }
>>
>> Apache host file:
>> <VirtualHost *:80>
>>         ServerAdmin webmaster at localhost
>>         DocumentRoot /pv/www
>>         <Directory /pv/www/>
>>                 Options Indexes FollowSymLinks MultiViews
>>                 AllowOverride None
>>                 Order allow,deny
>>                 allow from all
>>         </Directory>
>>
>>         ProxyPass        /paraview http://localhost:8080/paraview
>>
>>         RewriteEngine On
>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>
>>         RewriteLog "/var/log/apache2/rewrite.log"
>>         RewriteLogLevel 3
>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>         LogLevel debug
>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>> </VirtualHost>
>>
>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>> listening to a port from the range (e.g. 9999). We can see that process:
>> ps auwx | grep cone
>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>> /pv/paraview/lib/paraview-4.1/pvpython
>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>
>> After that we get a session timeout and this response: "Session did not
>> start before timeout expired. Check session logs."
>>
>> Any further advice?
>>
>>
>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Hi Dmitry,
>>>
>>> First of all you need to understand the role of apache here in order to
>>> see how the configuration should be.
>>> As you may know, you can use ParaViewWeb without Apache, but such setup
>>> is not meant for production.
>>>
>>> The list below is what you get when you add Apache:
>>> - Apache can be use to serve the static content (html, js, png, css...)
>>> - Apache provide a single entry point host + port. This prevent
>>> cross-domain issue or firewall limitation.
>>> - Apache will relay the WebSocket communication to the proper
>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>> Apache Web Server.
>>>
>>> Then you need to understand how the launcher works and its role.
>>> In ParaViewWeb a launcher is used to start a new visualization process
>>> for a given user. This simply mean running a command line with some dynamic
>>> parameters like the port number on which this specific instance should
>>> listen.
>>> So when a user connect to the system and request a new visualization
>>> session, it is the responsibility of the launcher to start the process and
>>> let the client know on which WebSocket URL it should connect to in order to
>>> reach the requested visualization session.
>>>
>>> In a setup that DOES NOT contain Apache, we can not use the same port as
>>> the main server (the process would not start). Hence, we start it with some
>>> port and we let the user know that it should connect to
>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>> was used to create the process.
>>>
>>> See section "resources" in launcher configuration.
>>>
>>> BUT with Apache that is different, now we have a process which is meant
>>> to relay the communication to the backend using the port and host that
>>> Apache is using. So the launcher should let the client know what URL they
>>> should use so Apache could handle it and forward it to the backend. Hence
>>> the ws://{apache_host}/proxy?sessionId=${id}.
>>> In the same time to keep track on which host/port a process is running
>>> the launcher generate a text file with the proper mapping.
>>> That mapping file is then used inside Apache to figure out how it should
>>> establish the connection to the backend.
>>>
>>> This should help you understand how to fix your configuration.
>>> Moreover, here is the remaining set of questions:
>>>
>>> > can we specifically log and debug Rewrite rule actions?
>>>
>>> Don't know, Google will be your friend here...
>>>
>>> > do we actually need ProxyPassReverse in Apache?
>>>
>>> Don't know, Google will be your friend here as well as the documentation
>>> on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>
>>> > what particular modules in Apache are required?
>>>
>>> Read the documentation, the list is minimum and provided in it.
>>>
>>> > in launch.json there are two particular lines host/resources:
>>>
>>> So the "host" is to select the proper network card when you have several
>>> for the actual launcher server.
>>>
>>> Then the resources are use for process management and URL generation for
>>> the client. Which mean, what name should be used by Apache to connect to
>>> the machine that actually run a ParaViewWeb process.
>>>
>>> Seb
>>>
>>>
>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> Thank you very much, Sebastien!
>>>>
>>>> Launcher side:
>>>>>
>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>
>>>>> "proxy_file": "/data/proxy.txt"
>>>>>
>>>>> This is exactly what we have in our launcher:
>>>>
>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>
>>>>   "host": "localhost",
>>>>
>>>>   "port": 8080,
>>>>
>>>> Your sessionURL looks different. Do you actually use "proxy?sessionId="
>>>> there? Ours came directly from the script you've suggested earlier:
>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>
>>>>
>>>>> Apache side
>>>>>
>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>
>>>>> In Apache we have:
>>>> RewriteEngine On
>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>
>>>>
>>>>> Then when a session start you can check the content of that
>>>>> /data/proxy.txt and that should one line by running session with
>>>>> {sessionId} localhost:yyyyy
>>>>>
>>>>
>>>> Verified that those entires are added to the file and have the right
>>>> format.
>>>>
>>>>
>>>>> On the other hand you forgot that line in the config of your cone app:
>>>>> "ready_line" : "Starting factory"
>>>>>
>>>>>  Thanks! Added it and now the app looks like this:
>>>>
>>>> "cone": {"cmd": ["${python_exec}",
>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>
>>>>
>>>>> You can check is any pvpython process is running, on which port, see
>>>>> if that match in the proxy file (/data/proxy.txt) and also looking at the
>>>>> log directory with the output of the pvpython process.
>>>>>
>>>>> A common error could also be that the apache does not have the right
>>>>> to read the /data/proxy.txt file or that the launcher is not able to write
>>>>> it.
>>>>>
>>>>
>>>> Verified that launcher can write it and that entries are added.
>>>>
>>>> These are the rest of our questions (we need to sort these out because
>>>> they have caused some confusion and we want to clear things up and do not
>>>> come back to these issues anymore):
>>>>
>>>> - can we specifically log and debug Rewrite rule actions?
>>>> - do we actually need ProxyPassReverse in Apache?
>>>> - what particular modules in Apache are required? So far we have:
>>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>>> we need proxy_wstunnel_module or not.
>>>> - in launch.json there are two particular lines:
>>>> "host": "localhost",
>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>> where we have some confusion about using "localhost" vs. "0.0.0.0".
>>>> What exactly should we use in either case?
>>>>
>>>> Appreciate your help!
>>>>
>>>>
>>>>> Good luck,
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>>>>>> ParaViewWeb system at University of Chicago.
>>>>>>
>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu
>>>>>> 12.04 instances.
>>>>>>
>>>>>> We have verified that PV builds without errors and that PVW launcher
>>>>>> is functioning (new entries are added to the proxy file, vis sessions are
>>>>>> created and are listening to ports in the specified range, etc.)
>>>>>>
>>>>>> We are trying to visualize a simple cone:
>>>>>> (added app in launch.json)
>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>> "${port}"]}},
>>>>>>
>>>>>> We have verified that vtk_web_cone.py actually gets called. In order
>>>>>> to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>> ...
>>>>>>   var config = {
>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>     application: "cone"
>>>>>>   };
>>>>>> ...
>>>>>>
>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>
>>>>>> In the apache error log we see:
>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy:
>>>>>> Error reading from remote server returned by /paraview/, referer:
>>>>>> http://54.211.22.94/apps/Cone/
>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File does
>>>>>> not exist: /pv/www/ws
>>>>>>
>>>>>> It appears that it has do to with Apache configuration, where we have:
>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>> RewriteEngine On
>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>
>>>>>> Do these Rewrite commands look right? How can their actions be logged
>>>>>> and verified?
>>>>>>
>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>
>>>>>> Is it possible that we are missing a module or some additional
>>>>>> configuration in Apache?
>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>> ...
>>>>>>  proxy_module (shared)
>>>>>>  proxy_http_module (shared)
>>>>>>  proxy_wstunnel_module (shared)
>>>>>>  rewrite_module (shared)
>>>>>> ...
>>>>>> Syntax OK
>>>>>>
>>>>>> Any debugging advice?
>>>>>>
>>>>>> Your help will be much appreciated and will allow to move forward
>>>>>> with our isntallation.
>>>>>>
>>>>>>
>>>>>> -------------------------------------------------------------------------------
>>>>>>
>>>>>> Dmitry Duplyakin
>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/5fdee94a/attachment-0001.html>

From duplyakin at uchicago.edu  Mon Jul 21 15:59:13 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Mon, 21 Jul 2014 14:59:13 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
Message-ID: <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>

Continue troubleshooting...

Now we get this in response to POST:

{"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
"port": 9999, "host": "localhost", "sessionURL": "ws://
54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8", "id":
"369f8648-110f-11e4-b402-22000b0185a8"}

Looks right to me. Then, after that POST, it does GETs that do not look
right:

54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
*/ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
rv:30.0) Gecko/20100101 Firefox/30.0"

130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
Firefox/30.0"

And the message:

Firefox can't establish a connection to the server at ws://
54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8. return
new WebSocket(url, protocols);

What can possibly cause this? Again, complete apache and launcher configs
are in the previous email.


On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> This helped tremendously!
>
> Both "-f" and "${host}" now make a lot more sense.
>
> POST works fine now and we can see the Rewrite rule in action. Something
> there still needs attention and we are investigating further.
>
> Thanks for you patience and all the help that allows us to move forward.
>
>
> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Hi Dmitry,
>>
>> you may still have a typo
>>
>> => "ws://${host}/proxy?sessionId=${id}",
>>
>> ${host} should have been replaced with a static string that match the
>> host that the web browser is using to reach apache.
>>
>> Moreover, I forgot to mention that you need to add "-f" in your set of
>> arguments. That will force some output generation to fill some buffer which
>> will allow the launcher to detect when the server is actually ready.
>>
>> I've noticed that the documentation is missing them. Don't know why...
>> Will update it at some point.
>> Although this page show that option:
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>
>> And the value for "timeout" should be way bigger than 5. Like 25 maybe.
>>
>> Seb
>>
>>
>>
>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>> duplyakin at uchicago.edu> wrote:
>>
>>> Thanks for this detailed description! The process is starting to make
>>> sense and we can communicate more efficiently about our configuration and
>>> problems.
>>>
>>> Here is our complete launch.json (with the right sessionURL for a config
>>> with Apache, according to your email):
>>> {
>>> "configuration": {
>>>   "content": "/pv/www",
>>>   "log_dir": "/pv/logs",
>>>   "host": "localhost",
>>>   "endpoint": "paraview",
>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>   "timeout": 5,
>>>   "upload_dir": "/pv/data",
>>>   "fields": ["file", "host", "port", "updir"],
>>>   "port": 8080,
>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>> "apps": {
>>>   "data_prober": {"cmd": ["${python_exec}",
>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>   "pipeline": {"cmd": ["${python_exec}",
>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>   "loader": {"cmd": ["${python_exec}",
>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>    "cone": {"cmd": ["${python_exec}",
>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>> "${port}"], "ready_line" : "Starting factory"}},
>>> "properties": {
>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>   "data": "/pv/data",
>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>> "sessionData": {"updir": "/Home"}
>>> }
>>>
>>> Apache host file:
>>> <VirtualHost *:80>
>>>         ServerAdmin webmaster at localhost
>>>         DocumentRoot /pv/www
>>>         <Directory /pv/www/>
>>>                 Options Indexes FollowSymLinks MultiViews
>>>                 AllowOverride None
>>>                 Order allow,deny
>>>                 allow from all
>>>         </Directory>
>>>
>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>
>>>         RewriteEngine On
>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>
>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>         RewriteLogLevel 3
>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>         LogLevel debug
>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>> </VirtualHost>
>>>
>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>> listening to a port from the range (e.g. 9999). We can see that process:
>>> ps auwx | grep cone
>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>> /pv/paraview/lib/paraview-4.1/pvpython
>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>
>>> After that we get a session timeout and this response: "Session did not
>>> start before timeout expired. Check session logs."
>>>
>>> Any further advice?
>>>
>>>
>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Hi Dmitry,
>>>>
>>>> First of all you need to understand the role of apache here in order to
>>>> see how the configuration should be.
>>>> As you may know, you can use ParaViewWeb without Apache, but such setup
>>>> is not meant for production.
>>>>
>>>> The list below is what you get when you add Apache:
>>>> - Apache can be use to serve the static content (html, js, png, css...)
>>>> - Apache provide a single entry point host + port. This prevent
>>>> cross-domain issue or firewall limitation.
>>>> - Apache will relay the WebSocket communication to the proper
>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>> Apache Web Server.
>>>>
>>>> Then you need to understand how the launcher works and its role.
>>>> In ParaViewWeb a launcher is used to start a new visualization process
>>>> for a given user. This simply mean running a command line with some dynamic
>>>> parameters like the port number on which this specific instance should
>>>> listen.
>>>> So when a user connect to the system and request a new visualization
>>>> session, it is the responsibility of the launcher to start the process and
>>>> let the client know on which WebSocket URL it should connect to in order to
>>>> reach the requested visualization session.
>>>>
>>>> In a setup that DOES NOT contain Apache, we can not use the same port
>>>> as the main server (the process would not start). Hence, we start it with
>>>> some port and we let the user know that it should connect to
>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>> was used to create the process.
>>>>
>>>> See section "resources" in launcher configuration.
>>>>
>>>> BUT with Apache that is different, now we have a process which is meant
>>>> to relay the communication to the backend using the port and host that
>>>> Apache is using. So the launcher should let the client know what URL they
>>>> should use so Apache could handle it and forward it to the backend. Hence
>>>> the ws://{apache_host}/proxy?sessionId=${id}.
>>>> In the same time to keep track on which host/port a process is running
>>>> the launcher generate a text file with the proper mapping.
>>>> That mapping file is then used inside Apache to figure out how it
>>>> should establish the connection to the backend.
>>>>
>>>> This should help you understand how to fix your configuration.
>>>> Moreover, here is the remaining set of questions:
>>>>
>>>> > can we specifically log and debug Rewrite rule actions?
>>>>
>>>> Don't know, Google will be your friend here...
>>>>
>>>> > do we actually need ProxyPassReverse in Apache?
>>>>
>>>> Don't know, Google will be your friend here as well as the
>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>
>>>> > what particular modules in Apache are required?
>>>>
>>>> Read the documentation, the list is minimum and provided in it.
>>>>
>>>> > in launch.json there are two particular lines host/resources:
>>>>
>>>> So the "host" is to select the proper network card when you have
>>>> several for the actual launcher server.
>>>>
>>>> Then the resources are use for process management and URL generation
>>>> for the client. Which mean, what name should be used by Apache to connect
>>>> to the machine that actually run a ParaViewWeb process.
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> Thank you very much, Sebastien!
>>>>>
>>>>> Launcher side:
>>>>>>
>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>
>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>
>>>>>> This is exactly what we have in our launcher:
>>>>>
>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>
>>>>>   "host": "localhost",
>>>>>
>>>>>   "port": 8080,
>>>>>
>>>>> Your sessionURL looks different. Do you actually use "proxy?sessionId="
>>>>> there? Ours came directly from the script you've suggested earlier:
>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>
>>>>>
>>>>>> Apache side
>>>>>>
>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>
>>>>>> In Apache we have:
>>>>> RewriteEngine On
>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>
>>>>>
>>>>>> Then when a session start you can check the content of that
>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>> {sessionId} localhost:yyyyy
>>>>>>
>>>>>
>>>>> Verified that those entires are added to the file and have the right
>>>>> format.
>>>>>
>>>>>
>>>>>> On the other hand you forgot that line in the config of your cone
>>>>>> app: "ready_line" : "Starting factory"
>>>>>>
>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>
>>>>> "cone": {"cmd": ["${python_exec}",
>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>
>>>>>
>>>>>> You can check is any pvpython process is running, on which port, see
>>>>>> if that match in the proxy file (/data/proxy.txt) and also looking at the
>>>>>> log directory with the output of the pvpython process.
>>>>>>
>>>>>> A common error could also be that the apache does not have the right
>>>>>> to read the /data/proxy.txt file or that the launcher is not able to write
>>>>>> it.
>>>>>>
>>>>>
>>>>> Verified that launcher can write it and that entries are added.
>>>>>
>>>>> These are the rest of our questions (we need to sort these out because
>>>>> they have caused some confusion and we want to clear things up and do not
>>>>> come back to these issues anymore):
>>>>>
>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>> - what particular modules in Apache are required? So far we have:
>>>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>>>> we need proxy_wstunnel_module or not.
>>>>> - in launch.json there are two particular lines:
>>>>> "host": "localhost",
>>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>> where we have some confusion about using "localhost" vs. "0.0.0.0".
>>>>> What exactly should we use in either case?
>>>>>
>>>>> Appreciate your help!
>>>>>
>>>>>
>>>>>> Good luck,
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>>>>>>> ParaViewWeb system at University of Chicago.
>>>>>>>
>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu
>>>>>>> 12.04 instances.
>>>>>>>
>>>>>>> We have verified that PV builds without errors and that PVW launcher
>>>>>>> is functioning (new entries are added to the proxy file, vis sessions are
>>>>>>> created and are listening to ports in the specified range, etc.)
>>>>>>>
>>>>>>> We are trying to visualize a simple cone:
>>>>>>> (added app in launch.json)
>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>> "${port}"]}},
>>>>>>>
>>>>>>> We have verified that vtk_web_cone.py actually gets called. In order
>>>>>>> to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>>> ...
>>>>>>>   var config = {
>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>     application: "cone"
>>>>>>>   };
>>>>>>> ...
>>>>>>>
>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>
>>>>>>> In the apache error log we see:
>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy:
>>>>>>> Error reading from remote server returned by /paraview/, referer:
>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File
>>>>>>> does not exist: /pv/www/ws
>>>>>>>
>>>>>>> It appears that it has do to with Apache configuration, where we
>>>>>>> have:
>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>> RewriteEngine On
>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>
>>>>>>> Do these Rewrite commands look right? How can their actions be
>>>>>>> logged and verified?
>>>>>>>
>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>
>>>>>>> Is it possible that we are missing a module or some additional
>>>>>>> configuration in Apache?
>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>> ...
>>>>>>>  proxy_module (shared)
>>>>>>>  proxy_http_module (shared)
>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>  rewrite_module (shared)
>>>>>>> ...
>>>>>>> Syntax OK
>>>>>>>
>>>>>>> Any debugging advice?
>>>>>>>
>>>>>>> Your help will be much appreciated and will allow to move forward
>>>>>>> with our isntallation.
>>>>>>>
>>>>>>>
>>>>>>> -------------------------------------------------------------------------------
>>>>>>>
>>>>>>> Dmitry Duplyakin
>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/8ffc4850/attachment-0001.html>

From sebastien.jourdain at kitware.com  Mon Jul 21 16:10:24 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 21 Jul 2014 14:10:24 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
Message-ID: <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>

Which version of Apache are you using? Do you have the ws_tunnelling (<=
wrong name but something like that) module enabled?

You may be able to check the system log that apache generate to see what
went wrong.
Do you know how much time the POST request took?

Seb


On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Continue troubleshooting...
>
> Now we get this in response to POST:
>
> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
> "port": 9999, "host": "localhost", "sessionURL": "ws://
> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8", "id":
> "369f8648-110f-11e4-b402-22000b0185a8"}
>
> Looks right to me. Then, after that POST, it does GETs that do not look
> right:
>
> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
> rv:30.0) Gecko/20100101 Firefox/30.0"
>
> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
> Firefox/30.0"
>
> And the message:
>
> Firefox can't establish a connection to the server at ws://
> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8. return
> new WebSocket(url, protocols);
>
> What can possibly cause this? Again, complete apache and launcher configs
> are in the previous email.
>
>
> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> This helped tremendously!
>>
>> Both "-f" and "${host}" now make a lot more sense.
>>
>> POST works fine now and we can see the Rewrite rule in action. Something
>> there still needs attention and we are investigating further.
>>
>> Thanks for you patience and all the help that allows us to move forward.
>>
>>
>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Hi Dmitry,
>>>
>>> you may still have a typo
>>>
>>> => "ws://${host}/proxy?sessionId=${id}",
>>>
>>> ${host} should have been replaced with a static string that match the
>>> host that the web browser is using to reach apache.
>>>
>>> Moreover, I forgot to mention that you need to add "-f" in your set of
>>> arguments. That will force some output generation to fill some buffer which
>>> will allow the launcher to detect when the server is actually ready.
>>>
>>> I've noticed that the documentation is missing them. Don't know why...
>>> Will update it at some point.
>>> Although this page show that option:
>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>
>>> And the value for "timeout" should be way bigger than 5. Like 25 maybe.
>>>
>>> Seb
>>>
>>>
>>>
>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> Thanks for this detailed description! The process is starting to make
>>>> sense and we can communicate more efficiently about our configuration and
>>>> problems.
>>>>
>>>> Here is our complete launch.json (with the right sessionURL for a
>>>> config with Apache, according to your email):
>>>> {
>>>> "configuration": {
>>>>   "content": "/pv/www",
>>>>   "log_dir": "/pv/logs",
>>>>   "host": "localhost",
>>>>   "endpoint": "paraview",
>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>   "timeout": 5,
>>>>   "upload_dir": "/pv/data",
>>>>   "fields": ["file", "host", "port", "updir"],
>>>>   "port": 8080,
>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>> "apps": {
>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>   "loader": {"cmd": ["${python_exec}",
>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>    "cone": {"cmd": ["${python_exec}",
>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>> "properties": {
>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>   "data": "/pv/data",
>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>> "sessionData": {"updir": "/Home"}
>>>> }
>>>>
>>>> Apache host file:
>>>> <VirtualHost *:80>
>>>>         ServerAdmin webmaster at localhost
>>>>         DocumentRoot /pv/www
>>>>         <Directory /pv/www/>
>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>                 AllowOverride None
>>>>                 Order allow,deny
>>>>                 allow from all
>>>>         </Directory>
>>>>
>>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>>
>>>>         RewriteEngine On
>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>
>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>         RewriteLogLevel 3
>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>         LogLevel debug
>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>> </VirtualHost>
>>>>
>>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>> ps auwx | grep cone
>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>>> /pv/paraview/lib/paraview-4.1/pvpython
>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>
>>>> After that we get a session timeout and this response: "Session did
>>>> not start before timeout expired. Check session logs."
>>>>
>>>> Any further advice?
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com> wrote:
>>>>
>>>>> Hi Dmitry,
>>>>>
>>>>> First of all you need to understand the role of apache here in order
>>>>> to see how the configuration should be.
>>>>> As you may know, you can use ParaViewWeb without Apache, but such
>>>>> setup is not meant for production.
>>>>>
>>>>> The list below is what you get when you add Apache:
>>>>> - Apache can be use to serve the static content (html, js, png, css...)
>>>>> - Apache provide a single entry point host + port. This prevent
>>>>> cross-domain issue or firewall limitation.
>>>>> - Apache will relay the WebSocket communication to the proper
>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>> Apache Web Server.
>>>>>
>>>>> Then you need to understand how the launcher works and its role.
>>>>> In ParaViewWeb a launcher is used to start a new visualization process
>>>>> for a given user. This simply mean running a command line with some dynamic
>>>>> parameters like the port number on which this specific instance should
>>>>> listen.
>>>>> So when a user connect to the system and request a new visualization
>>>>> session, it is the responsibility of the launcher to start the process and
>>>>> let the client know on which WebSocket URL it should connect to in order to
>>>>> reach the requested visualization session.
>>>>>
>>>>> In a setup that DOES NOT contain Apache, we can not use the same port
>>>>> as the main server (the process would not start). Hence, we start it with
>>>>> some port and we let the user know that it should connect to
>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>> was used to create the process.
>>>>>
>>>>> See section "resources" in launcher configuration.
>>>>>
>>>>> BUT with Apache that is different, now we have a process which is
>>>>> meant to relay the communication to the backend using the port and host
>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>> In the same time to keep track on which host/port a process is running
>>>>> the launcher generate a text file with the proper mapping.
>>>>> That mapping file is then used inside Apache to figure out how it
>>>>> should establish the connection to the backend.
>>>>>
>>>>> This should help you understand how to fix your configuration.
>>>>> Moreover, here is the remaining set of questions:
>>>>>
>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>
>>>>> Don't know, Google will be your friend here...
>>>>>
>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>
>>>>> Don't know, Google will be your friend here as well as the
>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>
>>>>> > what particular modules in Apache are required?
>>>>>
>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>
>>>>> > in launch.json there are two particular lines host/resources:
>>>>>
>>>>> So the "host" is to select the proper network card when you have
>>>>> several for the actual launcher server.
>>>>>
>>>>> Then the resources are use for process management and URL generation
>>>>> for the client. Which mean, what name should be used by Apache to connect
>>>>> to the machine that actually run a ParaViewWeb process.
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> Thank you very much, Sebastien!
>>>>>>
>>>>>> Launcher side:
>>>>>>>
>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>
>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>
>>>>>>> This is exactly what we have in our launcher:
>>>>>>
>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>
>>>>>>   "host": "localhost",
>>>>>>
>>>>>>   "port": 8080,
>>>>>>
>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>> proxy?sessionId=" there? Ours came directly from the script you've
>>>>>> suggested earlier:
>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>
>>>>>>
>>>>>>> Apache side
>>>>>>>
>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>
>>>>>>> In Apache we have:
>>>>>> RewriteEngine On
>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>
>>>>>>
>>>>>>> Then when a session start you can check the content of that
>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>
>>>>>>
>>>>>> Verified that those entires are added to the file and have the right
>>>>>> format.
>>>>>>
>>>>>>
>>>>>>> On the other hand you forgot that line in the config of your cone
>>>>>>> app: "ready_line" : "Starting factory"
>>>>>>>
>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>
>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>
>>>>>>
>>>>>>> You can check is any pvpython process is running, on which port, see
>>>>>>> if that match in the proxy file (/data/proxy.txt) and also looking at the
>>>>>>> log directory with the output of the pvpython process.
>>>>>>>
>>>>>>> A common error could also be that the apache does not have the right
>>>>>>> to read the /data/proxy.txt file or that the launcher is not able to write
>>>>>>> it.
>>>>>>>
>>>>>>
>>>>>> Verified that launcher can write it and that entries are added.
>>>>>>
>>>>>> These are the rest of our questions (we need to sort these out
>>>>>> because they have caused some confusion and we want to clear things up and
>>>>>> do not come back to these issues anymore):
>>>>>>
>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>> - what particular modules in Apache are required? So far we have:
>>>>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>>>>> we need proxy_wstunnel_module or not.
>>>>>> - in launch.json there are two particular lines:
>>>>>> "host": "localhost",
>>>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>> where we have some confusion about using "localhost" vs. "0.0.0.0".
>>>>>> What exactly should we use in either case?
>>>>>>
>>>>>> Appreciate your help!
>>>>>>
>>>>>>
>>>>>>> Good luck,
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>>>>>>>> ParaViewWeb system at University of Chicago.
>>>>>>>>
>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu
>>>>>>>> 12.04 instances.
>>>>>>>>
>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>> etc.)
>>>>>>>>
>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>> (added app in launch.json)
>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>> "--port", "${port}"]}},
>>>>>>>>
>>>>>>>> We have verified that vtk_web_cone.py actually gets called. In
>>>>>>>> order to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>>>> ...
>>>>>>>>   var config = {
>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>     application: "cone"
>>>>>>>>   };
>>>>>>>> ...
>>>>>>>>
>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>
>>>>>>>> In the apache error log we see:
>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy:
>>>>>>>> Error reading from remote server returned by /paraview/, referer:
>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File
>>>>>>>> does not exist: /pv/www/ws
>>>>>>>>
>>>>>>>> It appears that it has do to with Apache configuration, where we
>>>>>>>> have:
>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>> RewriteEngine On
>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>
>>>>>>>> Do these Rewrite commands look right? How can their actions be
>>>>>>>> logged and verified?
>>>>>>>>
>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>
>>>>>>>> Is it possible that we are missing a module or some additional
>>>>>>>> configuration in Apache?
>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>> ...
>>>>>>>>  proxy_module (shared)
>>>>>>>>  proxy_http_module (shared)
>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>  rewrite_module (shared)
>>>>>>>> ...
>>>>>>>> Syntax OK
>>>>>>>>
>>>>>>>> Any debugging advice?
>>>>>>>>
>>>>>>>> Your help will be much appreciated and will allow to move forward
>>>>>>>> with our isntallation.
>>>>>>>>
>>>>>>>>
>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> Dmitry Duplyakin
>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/acb062ce/attachment-0001.html>

From duplyakin at uchicago.edu  Mon Jul 21 16:25:15 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Mon, 21 Jul 2014 15:25:15 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
Message-ID: <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>

We are running Apache/2.2.22 with loaded proxy_wstunnel_module (that we had
to build from source).

>From Apache error log (with debug):
[Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
canonicalising URL //localhost:8080/paraview/
[Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
130.202.2.217] proxy: http: found worker http://localhost:8080/paraview for
http://localhost:8080/paraview/, referer: http://54.211.22.94/apps/Cone/
[Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running scheme http
handler (attempt 0)
[Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
serving URL http://localhost:8080/paraview/
[Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
acquired connection for (localhost)
[Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy: connecting
http://localhost:8080/paraview/ to localhost:8080
[Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy: connected
/paraview/ to localhost:8080
[Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
body send
[Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
http://54.211.22.94/apps/Cone/
[Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end body
send
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
released connection for (localhost)
[Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
canonicalising URL //54.211.22.94/ws://localhost:9998/ws
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
130.202.2.217] proxy: *: found reverse proxy worker for
http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
[Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running scheme http
handler (attempt 0)
[Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
serving URL
http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
acquired connection for (*)
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy: connecting
http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
to 54.211.22.94:80
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy: connected
/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
54.211.22.94:80
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP: fam 2
socket created to connect to *
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
connection complete to 54.211.22.94:80 (54.211.22.94)
[Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does not
exist: /pv/www/ws:
[Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
body send
[Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end body
send
[Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
released connection for (*)


POST took ~1 second. Timestamps for POST and the following GET:
21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03


On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Which version of Apache are you using? Do you have the ws_tunnelling (<=
> wrong name but something like that) module enabled?
>
> You may be able to check the system log that apache generate to see what
> went wrong.
> Do you know how much time the POST request took?
>
> Seb
>
>
> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> Continue troubleshooting...
>>
>> Now we get this in response to POST:
>>
>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>
>> Looks right to me. Then, after that POST, it does GETs that do not look
>> right:
>>
>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>
>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>> Firefox/30.0"
>>
>> And the message:
>>
>> Firefox can't establish a connection to the server at ws://
>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>> return new WebSocket(url, protocols);
>>
>> What can possibly cause this? Again, complete apache and launcher configs
>> are in the previous email.
>>
>>
>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <duplyakin at uchicago.edu
>> > wrote:
>>
>>> This helped tremendously!
>>>
>>> Both "-f" and "${host}" now make a lot more sense.
>>>
>>> POST works fine now and we can see the Rewrite rule in action. Something
>>> there still needs attention and we are investigating further.
>>>
>>> Thanks for you patience and all the help that allows us to move forward.
>>>
>>>
>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Hi Dmitry,
>>>>
>>>> you may still have a typo
>>>>
>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>
>>>> ${host} should have been replaced with a static string that match the
>>>> host that the web browser is using to reach apache.
>>>>
>>>> Moreover, I forgot to mention that you need to add "-f" in your set of
>>>> arguments. That will force some output generation to fill some buffer which
>>>> will allow the launcher to detect when the server is actually ready.
>>>>
>>>> I've noticed that the documentation is missing them. Don't know why...
>>>> Will update it at some point.
>>>> Although this page show that option:
>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>
>>>> And the value for "timeout" should be way bigger than 5. Like 25 maybe.
>>>>
>>>> Seb
>>>>
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> Thanks for this detailed description! The process is starting to make
>>>>> sense and we can communicate more efficiently about our configuration and
>>>>> problems.
>>>>>
>>>>> Here is our complete launch.json (with the right sessionURL for a
>>>>> config with Apache, according to your email):
>>>>> {
>>>>> "configuration": {
>>>>>   "content": "/pv/www",
>>>>>   "log_dir": "/pv/logs",
>>>>>   "host": "localhost",
>>>>>   "endpoint": "paraview",
>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>   "timeout": 5,
>>>>>   "upload_dir": "/pv/data",
>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>   "port": 8080,
>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>> "apps": {
>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>> "properties": {
>>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>   "data": "/pv/data",
>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>> "sessionData": {"updir": "/Home"}
>>>>> }
>>>>>
>>>>> Apache host file:
>>>>> <VirtualHost *:80>
>>>>>         ServerAdmin webmaster at localhost
>>>>>         DocumentRoot /pv/www
>>>>>         <Directory /pv/www/>
>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>                 AllowOverride None
>>>>>                 Order allow,deny
>>>>>                 allow from all
>>>>>         </Directory>
>>>>>
>>>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>>>
>>>>>         RewriteEngine On
>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>
>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>         RewriteLogLevel 3
>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>         LogLevel debug
>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>> </VirtualHost>
>>>>>
>>>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>> ps auwx | grep cone
>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>>>> /pv/paraview/lib/paraview-4.1/pvpython
>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>
>>>>> After that we get a session timeout and this response: "Session did
>>>>> not start before timeout expired. Check session logs."
>>>>>
>>>>> Any further advice?
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> Hi Dmitry,
>>>>>>
>>>>>> First of all you need to understand the role of apache here in order
>>>>>> to see how the configuration should be.
>>>>>> As you may know, you can use ParaViewWeb without Apache, but such
>>>>>> setup is not meant for production.
>>>>>>
>>>>>> The list below is what you get when you add Apache:
>>>>>> - Apache can be use to serve the static content (html, js, png,
>>>>>> css...)
>>>>>> - Apache provide a single entry point host + port. This prevent
>>>>>> cross-domain issue or firewall limitation.
>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>> Apache Web Server.
>>>>>>
>>>>>> Then you need to understand how the launcher works and its role.
>>>>>> In ParaViewWeb a launcher is used to start a new visualization
>>>>>> process for a given user. This simply mean running a command line with some
>>>>>> dynamic parameters like the port number on which this specific instance
>>>>>> should listen.
>>>>>> So when a user connect to the system and request a new visualization
>>>>>> session, it is the responsibility of the launcher to start the process and
>>>>>> let the client know on which WebSocket URL it should connect to in order to
>>>>>> reach the requested visualization session.
>>>>>>
>>>>>> In a setup that DOES NOT contain Apache, we can not use the same port
>>>>>> as the main server (the process would not start). Hence, we start it with
>>>>>> some port and we let the user know that it should connect to
>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>> was used to create the process.
>>>>>>
>>>>>> See section "resources" in launcher configuration.
>>>>>>
>>>>>> BUT with Apache that is different, now we have a process which is
>>>>>> meant to relay the communication to the backend using the port and host
>>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>> In the same time to keep track on which host/port a process is
>>>>>> running the launcher generate a text file with the proper mapping.
>>>>>> That mapping file is then used inside Apache to figure out how it
>>>>>> should establish the connection to the backend.
>>>>>>
>>>>>> This should help you understand how to fix your configuration.
>>>>>> Moreover, here is the remaining set of questions:
>>>>>>
>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>
>>>>>> Don't know, Google will be your friend here...
>>>>>>
>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>
>>>>>> Don't know, Google will be your friend here as well as the
>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>
>>>>>> > what particular modules in Apache are required?
>>>>>>
>>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>>
>>>>>> > in launch.json there are two particular lines host/resources:
>>>>>>
>>>>>> So the "host" is to select the proper network card when you have
>>>>>> several for the actual launcher server.
>>>>>>
>>>>>> Then the resources are use for process management and URL generation
>>>>>> for the client. Which mean, what name should be used by Apache to connect
>>>>>> to the machine that actually run a ParaViewWeb process.
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> Thank you very much, Sebastien!
>>>>>>>
>>>>>>> Launcher side:
>>>>>>>>
>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>
>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>
>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>
>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>
>>>>>>>   "host": "localhost",
>>>>>>>
>>>>>>>   "port": 8080,
>>>>>>>
>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>> proxy?sessionId=" there? Ours came directly from the script you've
>>>>>>> suggested earlier:
>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>
>>>>>>>
>>>>>>>> Apache side
>>>>>>>>
>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>
>>>>>>>> In Apache we have:
>>>>>>> RewriteEngine On
>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>
>>>>>>>
>>>>>>>> Then when a session start you can check the content of that
>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>
>>>>>>>
>>>>>>> Verified that those entires are added to the file and have the right
>>>>>>> format.
>>>>>>>
>>>>>>>
>>>>>>>> On the other hand you forgot that line in the config of your cone
>>>>>>>> app: "ready_line" : "Starting factory"
>>>>>>>>
>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>
>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>
>>>>>>>
>>>>>>>> You can check is any pvpython process is running, on which port,
>>>>>>>> see if that match in the proxy file (/data/proxy.txt) and also looking at
>>>>>>>> the log directory with the output of the pvpython process.
>>>>>>>>
>>>>>>>> A common error could also be that the apache does not have the
>>>>>>>> right to read the /data/proxy.txt file or that the launcher is not able to
>>>>>>>> write it.
>>>>>>>>
>>>>>>>
>>>>>>> Verified that launcher can write it and that entries are added.
>>>>>>>
>>>>>>> These are the rest of our questions (we need to sort these out
>>>>>>> because they have caused some confusion and we want to clear things up and
>>>>>>> do not come back to these issues anymore):
>>>>>>>
>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>> - what particular modules in Apache are required? So far we have:
>>>>>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>>>>>> we need proxy_wstunnel_module or not.
>>>>>>> - in launch.json there are two particular lines:
>>>>>>> "host": "localhost",
>>>>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>> where we have some confusion about using "localhost" vs. "0.0.0.0".
>>>>>>> What exactly should we use in either case?
>>>>>>>
>>>>>>> Appreciate your help!
>>>>>>>
>>>>>>>
>>>>>>>> Good luck,
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build a
>>>>>>>>> ParaViewWeb system at University of Chicago.
>>>>>>>>>
>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu
>>>>>>>>> 12.04 instances.
>>>>>>>>>
>>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>> etc.)
>>>>>>>>>
>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>> (added app in launch.json)
>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>
>>>>>>>>> We have verified that vtk_web_cone.py actually gets called. In
>>>>>>>>> order to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>> ...
>>>>>>>>>   var config = {
>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>     application: "cone"
>>>>>>>>>   };
>>>>>>>>> ...
>>>>>>>>>
>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>
>>>>>>>>> In the apache error log we see:
>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] proxy:
>>>>>>>>> Error reading from remote server returned by /paraview/, referer:
>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File
>>>>>>>>> does not exist: /pv/www/ws
>>>>>>>>>
>>>>>>>>> It appears that it has do to with Apache configuration, where we
>>>>>>>>> have:
>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>> RewriteEngine On
>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>
>>>>>>>>> Do these Rewrite commands look right? How can their actions be
>>>>>>>>> logged and verified?
>>>>>>>>>
>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>
>>>>>>>>> Is it possible that we are missing a module or some additional
>>>>>>>>> configuration in Apache?
>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>> ...
>>>>>>>>>  proxy_module (shared)
>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>  rewrite_module (shared)
>>>>>>>>> ...
>>>>>>>>> Syntax OK
>>>>>>>>>
>>>>>>>>> Any debugging advice?
>>>>>>>>>
>>>>>>>>> Your help will be much appreciated and will allow to move forward
>>>>>>>>> with our isntallation.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> Dmitry Duplyakin
>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/f2e152e9/attachment-0001.html>

From sebastien.jourdain at kitware.com  Mon Jul 21 16:29:33 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 21 Jul 2014 14:29:33 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
Message-ID: <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>

You must have Apache 2.4.7+
Their is a fix in that version which allow mod_rewrite to work on web
socket protocol instead of just http.
You can look at the apache section in here
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2

Seb


On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> We are running Apache/2.2.22 with loaded proxy_wstunnel_module (that we
> had to build from source).
>
> From Apache error log (with debug):
> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
> canonicalising URL //localhost:8080/paraview/
> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
> 130.202.2.217] proxy: http: found worker http://localhost:8080/paraview
> for http://localhost:8080/paraview/, referer:
> http://54.211.22.94/apps/Cone/
> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running scheme http
> handler (attempt 0)
> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
> serving URL http://localhost:8080/paraview/
> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
> acquired connection for (localhost)
> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy: connecting
> http://localhost:8080/paraview/ to localhost:8080
> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy: connected
> /paraview/ to localhost:8080
> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
> body send
> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
> http://54.211.22.94/apps/Cone/
> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end body
> send
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
> released connection for (localhost)
> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
> canonicalising URL //54.211.22.94/ws://localhost:9998/ws
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
> 130.202.2.217] proxy: *: found reverse proxy worker for
> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running scheme http
> handler (attempt 0)
> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
> serving URL
> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
> acquired connection for (*)
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy: connecting
> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
> to 54.211.22.94:80
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy: connected
> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
> 54.211.22.94:80
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP: fam 2
> socket created to connect to *
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
> connection complete to 54.211.22.94:80 (54.211.22.94)
> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does not
> exist: /pv/www/ws:
> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
> body send
> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end body
> send
> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
> released connection for (*)
>
>
> POST took ~1 second. Timestamps for POST and the following GET:
> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>
>
>
> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Which version of Apache are you using? Do you have the ws_tunnelling (<=
>> wrong name but something like that) module enabled?
>>
>> You may be able to check the system log that apache generate to see what
>> went wrong.
>> Do you know how much time the POST request took?
>>
>> Seb
>>
>>
>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <duplyakin at uchicago.edu
>> > wrote:
>>
>>> Continue troubleshooting...
>>>
>>> Now we get this in response to POST:
>>>
>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>
>>> Looks right to me. Then, after that POST, it does GETs that do not look
>>> right:
>>>
>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>
>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>> Firefox/30.0"
>>>
>>> And the message:
>>>
>>> Firefox can't establish a connection to the server at ws://
>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>> return new WebSocket(url, protocols);
>>>
>>> What can possibly cause this? Again, complete apache and launcher
>>> configs are in the previous email.
>>>
>>>
>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> This helped tremendously!
>>>>
>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>
>>>> POST works fine now and we can see the Rewrite rule in action.
>>>> Something there still needs attention and we are investigating further.
>>>>
>>>> Thanks for you patience and all the help that allows us to move forward.
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com> wrote:
>>>>
>>>>> Hi Dmitry,
>>>>>
>>>>> you may still have a typo
>>>>>
>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>
>>>>> ${host} should have been replaced with a static string that match the
>>>>> host that the web browser is using to reach apache.
>>>>>
>>>>> Moreover, I forgot to mention that you need to add "-f" in your set of
>>>>> arguments. That will force some output generation to fill some buffer which
>>>>> will allow the launcher to detect when the server is actually ready.
>>>>>
>>>>> I've noticed that the documentation is missing them. Don't know why...
>>>>> Will update it at some point.
>>>>> Although this page show that option:
>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>
>>>>> And the value for "timeout" should be way bigger than 5. Like 25
>>>>> maybe.
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> Thanks for this detailed description! The process is starting to make
>>>>>> sense and we can communicate more efficiently about our configuration and
>>>>>> problems.
>>>>>>
>>>>>> Here is our complete launch.json (with the right sessionURL for a
>>>>>> config with Apache, according to your email):
>>>>>> {
>>>>>> "configuration": {
>>>>>>   "content": "/pv/www",
>>>>>>   "log_dir": "/pv/logs",
>>>>>>   "host": "localhost",
>>>>>>   "endpoint": "paraview",
>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>   "timeout": 5,
>>>>>>   "upload_dir": "/pv/data",
>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>   "port": 8080,
>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>> "apps": {
>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>> "properties": {
>>>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>   "data": "/pv/data",
>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>> "sessionData": {"updir": "/Home"}
>>>>>> }
>>>>>>
>>>>>> Apache host file:
>>>>>> <VirtualHost *:80>
>>>>>>         ServerAdmin webmaster at localhost
>>>>>>         DocumentRoot /pv/www
>>>>>>         <Directory /pv/www/>
>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>                 AllowOverride None
>>>>>>                 Order allow,deny
>>>>>>                 allow from all
>>>>>>         </Directory>
>>>>>>
>>>>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>
>>>>>>         RewriteEngine On
>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>
>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>         RewriteLogLevel 3
>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>         LogLevel debug
>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>> </VirtualHost>
>>>>>>
>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>>> ps auwx | grep cone
>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>>>>> /pv/paraview/lib/paraview-4.1/pvpython
>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>
>>>>>> After that we get a session timeout and this response: "Session did
>>>>>> not start before timeout expired. Check session logs."
>>>>>>
>>>>>> Any further advice?
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>
>>>>>>> Hi Dmitry,
>>>>>>>
>>>>>>> First of all you need to understand the role of apache here in order
>>>>>>> to see how the configuration should be.
>>>>>>> As you may know, you can use ParaViewWeb without Apache, but such
>>>>>>> setup is not meant for production.
>>>>>>>
>>>>>>> The list below is what you get when you add Apache:
>>>>>>> - Apache can be use to serve the static content (html, js, png,
>>>>>>> css...)
>>>>>>> - Apache provide a single entry point host + port. This prevent
>>>>>>> cross-domain issue or firewall limitation.
>>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>> Apache Web Server.
>>>>>>>
>>>>>>> Then you need to understand how the launcher works and its role.
>>>>>>> In ParaViewWeb a launcher is used to start a new visualization
>>>>>>> process for a given user. This simply mean running a command line with some
>>>>>>> dynamic parameters like the port number on which this specific instance
>>>>>>> should listen.
>>>>>>> So when a user connect to the system and request a new visualization
>>>>>>> session, it is the responsibility of the launcher to start the process and
>>>>>>> let the client know on which WebSocket URL it should connect to in order to
>>>>>>> reach the requested visualization session.
>>>>>>>
>>>>>>> In a setup that DOES NOT contain Apache, we can not use the same
>>>>>>> port as the main server (the process would not start). Hence, we start it
>>>>>>> with some port and we let the user know that it should connect to
>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>> was used to create the process.
>>>>>>>
>>>>>>> See section "resources" in launcher configuration.
>>>>>>>
>>>>>>> BUT with Apache that is different, now we have a process which is
>>>>>>> meant to relay the communication to the backend using the port and host
>>>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>> In the same time to keep track on which host/port a process is
>>>>>>> running the launcher generate a text file with the proper mapping.
>>>>>>> That mapping file is then used inside Apache to figure out how it
>>>>>>> should establish the connection to the backend.
>>>>>>>
>>>>>>> This should help you understand how to fix your configuration.
>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>
>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>
>>>>>>> Don't know, Google will be your friend here...
>>>>>>>
>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>
>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>
>>>>>>> > what particular modules in Apache are required?
>>>>>>>
>>>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>>>
>>>>>>> > in launch.json there are two particular lines host/resources:
>>>>>>>
>>>>>>> So the "host" is to select the proper network card when you have
>>>>>>> several for the actual launcher server.
>>>>>>>
>>>>>>> Then the resources are use for process management and URL generation
>>>>>>> for the client. Which mean, what name should be used by Apache to connect
>>>>>>> to the machine that actually run a ParaViewWeb process.
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>
>>>>>>>> Launcher side:
>>>>>>>>>
>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>
>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>
>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>
>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>
>>>>>>>>   "host": "localhost",
>>>>>>>>
>>>>>>>>   "port": 8080,
>>>>>>>>
>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>> proxy?sessionId=" there? Ours came directly from the script you've
>>>>>>>> suggested earlier:
>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>
>>>>>>>>
>>>>>>>>> Apache side
>>>>>>>>>
>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>
>>>>>>>>> In Apache we have:
>>>>>>>> RewriteEngine On
>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>
>>>>>>>>
>>>>>>>>> Then when a session start you can check the content of that
>>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>
>>>>>>>>
>>>>>>>> Verified that those entires are added to the file and have the
>>>>>>>> right format.
>>>>>>>>
>>>>>>>>
>>>>>>>>> On the other hand you forgot that line in the config of your cone
>>>>>>>>> app: "ready_line" : "Starting factory"
>>>>>>>>>
>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>
>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>
>>>>>>>>
>>>>>>>>> You can check is any pvpython process is running, on which port,
>>>>>>>>> see if that match in the proxy file (/data/proxy.txt) and also looking at
>>>>>>>>> the log directory with the output of the pvpython process.
>>>>>>>>>
>>>>>>>>> A common error could also be that the apache does not have the
>>>>>>>>> right to read the /data/proxy.txt file or that the launcher is not able to
>>>>>>>>> write it.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Verified that launcher can write it and that entries are added.
>>>>>>>>
>>>>>>>> These are the rest of our questions (we need to sort these out
>>>>>>>> because they have caused some confusion and we want to clear things up and
>>>>>>>> do not come back to these issues anymore):
>>>>>>>>
>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>> - what particular modules in Apache are required? So far we have:
>>>>>>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>>>>>>> we need proxy_wstunnel_module or not.
>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>> "host": "localhost",
>>>>>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>>> where we have some confusion about using "localhost" vs. "0.0.0.0".
>>>>>>>> What exactly should we use in either case?
>>>>>>>>
>>>>>>>> Appreciate your help!
>>>>>>>>
>>>>>>>>
>>>>>>>>> Good luck,
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build
>>>>>>>>>> a ParaViewWeb system at University of Chicago.
>>>>>>>>>>
>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2 Ubuntu
>>>>>>>>>> 12.04 instances.
>>>>>>>>>>
>>>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>> etc.)
>>>>>>>>>>
>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>> (added app in launch.json)
>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>
>>>>>>>>>> We have verified that vtk_web_cone.py actually gets called. In
>>>>>>>>>> order to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>> ...
>>>>>>>>>>   var config = {
>>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>     application: "cone"
>>>>>>>>>>   };
>>>>>>>>>> ...
>>>>>>>>>>
>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>
>>>>>>>>>> In the apache error log we see:
>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>> proxy: Error reading from remote server returned by /paraview/, referer:
>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File
>>>>>>>>>> does not exist: /pv/www/ws
>>>>>>>>>>
>>>>>>>>>> It appears that it has do to with Apache configuration, where we
>>>>>>>>>> have:
>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>> RewriteEngine On
>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>
>>>>>>>>>> Do these Rewrite commands look right? How can their actions be
>>>>>>>>>> logged and verified?
>>>>>>>>>>
>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>
>>>>>>>>>> Is it possible that we are missing a module or some additional
>>>>>>>>>> configuration in Apache?
>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>> ...
>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>> ...
>>>>>>>>>> Syntax OK
>>>>>>>>>>
>>>>>>>>>> Any debugging advice?
>>>>>>>>>>
>>>>>>>>>> Your help will be much appreciated and will allow to move forward
>>>>>>>>>> with our isntallation.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/ad65747a/attachment-0001.html>

From duplyakin at uchicago.edu  Mon Jul 21 16:36:58 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Mon, 21 Jul 2014 15:36:58 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
Message-ID: <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>

Got it. Rebuilding Apache now.

Thanks!


On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> You must have Apache 2.4.7+
> Their is a fix in that version which allow mod_rewrite to work on web
> socket protocol instead of just http.
> You can look at the apache section in here
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>
> Seb
>
>
> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module (that we
>> had to build from source).
>>
>> From Apache error log (with debug):
>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>> canonicalising URL //localhost:8080/paraview/
>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>> 130.202.2.217] proxy: http: found worker http://localhost:8080/paraview
>> for http://localhost:8080/paraview/, referer:
>> http://54.211.22.94/apps/Cone/
>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running scheme http
>> handler (attempt 0)
>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
>> serving URL http://localhost:8080/paraview/
>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
>> acquired connection for (localhost)
>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy: connecting
>> http://localhost:8080/paraview/ to localhost:8080
>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy: connected
>> /paraview/ to localhost:8080
>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
>> body send
>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>> http://54.211.22.94/apps/Cone/
>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>> body send
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
>> released connection for (localhost)
>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>> canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>> 130.202.2.217] proxy: *: found reverse proxy worker for
>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running scheme http
>> handler (attempt 0)
>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
>> serving URL
>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
>> acquired connection for (*)
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy: connecting
>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>> to 54.211.22.94:80
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy: connected
>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>> 54.211.22.94:80
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP: fam 2
>> socket created to connect to *
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
>> connection complete to 54.211.22.94:80 (54.211.22.94)
>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does not
>> exist: /pv/www/ws:
>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
>> body send
>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>> body send
>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
>> released connection for (*)
>>
>>
>> POST took ~1 second. Timestamps for POST and the following GET:
>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>
>>
>>
>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Which version of Apache are you using? Do you have the ws_tunnelling (<=
>>> wrong name but something like that) module enabled?
>>>
>>> You may be able to check the system log that apache generate to see what
>>> went wrong.
>>> Do you know how much time the POST request took?
>>>
>>> Seb
>>>
>>>
>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> Continue troubleshooting...
>>>>
>>>> Now we get this in response to POST:
>>>>
>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>
>>>> Looks right to me. Then, after that POST, it does GETs that do not look
>>>> right:
>>>>
>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>
>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>> Firefox/30.0"
>>>>
>>>> And the message:
>>>>
>>>> Firefox can't establish a connection to the server at ws://
>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>> return new WebSocket(url, protocols);
>>>>
>>>> What can possibly cause this? Again, complete apache and launcher
>>>> configs are in the previous email.
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> This helped tremendously!
>>>>>
>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>
>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>> Something there still needs attention and we are investigating further.
>>>>>
>>>>> Thanks for you patience and all the help that allows us to move
>>>>> forward.
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> Hi Dmitry,
>>>>>>
>>>>>> you may still have a typo
>>>>>>
>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>
>>>>>> ${host} should have been replaced with a static string that match the
>>>>>> host that the web browser is using to reach apache.
>>>>>>
>>>>>> Moreover, I forgot to mention that you need to add "-f" in your set
>>>>>> of arguments. That will force some output generation to fill some buffer
>>>>>> which will allow the launcher to detect when the server is actually ready.
>>>>>>
>>>>>> I've noticed that the documentation is missing them. Don't know
>>>>>> why... Will update it at some point.
>>>>>> Although this page show that option:
>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>
>>>>>> And the value for "timeout" should be way bigger than 5. Like 25
>>>>>> maybe.
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> Thanks for this detailed description! The process is starting to
>>>>>>> make sense and we can communicate more efficiently about our configuration
>>>>>>> and problems.
>>>>>>>
>>>>>>> Here is our complete launch.json (with the right sessionURL for a
>>>>>>> config with Apache, according to your email):
>>>>>>> {
>>>>>>> "configuration": {
>>>>>>>   "content": "/pv/www",
>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>   "host": "localhost",
>>>>>>>   "endpoint": "paraview",
>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>   "timeout": 5,
>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>   "port": 8080,
>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>> "apps": {
>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>> "properties": {
>>>>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>   "data": "/pv/data",
>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>> }
>>>>>>>
>>>>>>> Apache host file:
>>>>>>> <VirtualHost *:80>
>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>         DocumentRoot /pv/www
>>>>>>>         <Directory /pv/www/>
>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>                 AllowOverride None
>>>>>>>                 Order allow,deny
>>>>>>>                 allow from all
>>>>>>>         </Directory>
>>>>>>>
>>>>>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>
>>>>>>>         RewriteEngine On
>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>
>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>         RewriteLogLevel 3
>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>         LogLevel debug
>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>> </VirtualHost>
>>>>>>>
>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>>>> ps auwx | grep cone
>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>>>>>> /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>
>>>>>>> After that we get a session timeout and this response: "Session did
>>>>>>> not start before timeout expired. Check session logs."
>>>>>>>
>>>>>>> Any further advice?
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>
>>>>>>>> Hi Dmitry,
>>>>>>>>
>>>>>>>> First of all you need to understand the role of apache here in
>>>>>>>> order to see how the configuration should be.
>>>>>>>> As you may know, you can use ParaViewWeb without Apache, but such
>>>>>>>> setup is not meant for production.
>>>>>>>>
>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>> - Apache can be use to serve the static content (html, js, png,
>>>>>>>> css...)
>>>>>>>> - Apache provide a single entry point host + port. This prevent
>>>>>>>> cross-domain issue or firewall limitation.
>>>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>> Apache Web Server.
>>>>>>>>
>>>>>>>> Then you need to understand how the launcher works and its role.
>>>>>>>> In ParaViewWeb a launcher is used to start a new visualization
>>>>>>>> process for a given user. This simply mean running a command line with some
>>>>>>>> dynamic parameters like the port number on which this specific instance
>>>>>>>> should listen.
>>>>>>>> So when a user connect to the system and request a new
>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>
>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the same
>>>>>>>> port as the main server (the process would not start). Hence, we start it
>>>>>>>> with some port and we let the user know that it should connect to
>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>> was used to create the process.
>>>>>>>>
>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>
>>>>>>>> BUT with Apache that is different, now we have a process which is
>>>>>>>> meant to relay the communication to the backend using the port and host
>>>>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>> In the same time to keep track on which host/port a process is
>>>>>>>> running the launcher generate a text file with the proper mapping.
>>>>>>>> That mapping file is then used inside Apache to figure out how it
>>>>>>>> should establish the connection to the backend.
>>>>>>>>
>>>>>>>> This should help you understand how to fix your configuration.
>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>
>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>
>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>
>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>
>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>
>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>
>>>>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>>>>
>>>>>>>> > in launch.json there are two particular lines host/resources:
>>>>>>>>
>>>>>>>> So the "host" is to select the proper network card when you have
>>>>>>>> several for the actual launcher server.
>>>>>>>>
>>>>>>>> Then the resources are use for process management and URL
>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>
>>>>>>>>> Launcher side:
>>>>>>>>>>
>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>
>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>
>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>
>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>
>>>>>>>>>   "host": "localhost",
>>>>>>>>>
>>>>>>>>>   "port": 8080,
>>>>>>>>>
>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>> proxy?sessionId=" there? Ours came directly from the script
>>>>>>>>> you've suggested earlier:
>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Apache side
>>>>>>>>>>
>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>
>>>>>>>>>> In Apache we have:
>>>>>>>>> RewriteEngine On
>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Then when a session start you can check the content of that
>>>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Verified that those entires are added to the file and have the
>>>>>>>>> right format.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On the other hand you forgot that line in the config of your cone
>>>>>>>>>> app: "ready_line" : "Starting factory"
>>>>>>>>>>
>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>
>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> You can check is any pvpython process is running, on which port,
>>>>>>>>>> see if that match in the proxy file (/data/proxy.txt) and also looking at
>>>>>>>>>> the log directory with the output of the pvpython process.
>>>>>>>>>>
>>>>>>>>>> A common error could also be that the apache does not have the
>>>>>>>>>> right to read the /data/proxy.txt file or that the launcher is not able to
>>>>>>>>>> write it.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Verified that launcher can write it and that entries are added.
>>>>>>>>>
>>>>>>>>> These are the rest of our questions (we need to sort these out
>>>>>>>>> because they have caused some confusion and we want to clear things up and
>>>>>>>>> do not come back to these issues anymore):
>>>>>>>>>
>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>> - what particular modules in Apache are required? So far we have:
>>>>>>>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>>>>>>>> we need proxy_wstunnel_module or not.
>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>> "host": "localhost",
>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>
>>>>>>>>> Appreciate your help!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Good luck,
>>>>>>>>>>
>>>>>>>>>> Seb
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi all,
>>>>>>>>>>>
>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to build
>>>>>>>>>>> a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>
>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2
>>>>>>>>>>> Ubuntu 12.04 instances.
>>>>>>>>>>>
>>>>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>> etc.)
>>>>>>>>>>>
>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>
>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets called. In
>>>>>>>>>>> order to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>> ...
>>>>>>>>>>>   var config = {
>>>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>   };
>>>>>>>>>>> ...
>>>>>>>>>>>
>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>
>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>> proxy: Error reading from remote server returned by /paraview/, referer:
>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231] File
>>>>>>>>>>> does not exist: /pv/www/ws
>>>>>>>>>>>
>>>>>>>>>>> It appears that it has do to with Apache configuration, where we
>>>>>>>>>>> have:
>>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>
>>>>>>>>>>> Do these Rewrite commands look right? How can their actions be
>>>>>>>>>>> logged and verified?
>>>>>>>>>>>
>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>
>>>>>>>>>>> Is it possible that we are missing a module or some additional
>>>>>>>>>>> configuration in Apache?
>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>> ...
>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>> ...
>>>>>>>>>>> Syntax OK
>>>>>>>>>>>
>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>
>>>>>>>>>>> Your help will be much appreciated and will allow to move
>>>>>>>>>>> forward with our isntallation.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/861df0cf/attachment-0001.html>

From duplyakin at uchicago.edu  Mon Jul 21 17:02:19 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Mon, 21 Jul 2014 16:02:19 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
Message-ID: <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>

Trying to follow instructions from
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
now.
It looks like those urls used with wget are broken.

Found a replacement for httpd:

wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O httpd.tgz

Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here is a
working command:

wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz

The last one works fine:

wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O apr-util.tgz


On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Got it. Rebuilding Apache now.
>
> Thanks!
>
>
>
> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> You must have Apache 2.4.7+
>> Their is a fix in that version which allow mod_rewrite to work on web
>> socket protocol instead of just http.
>> You can look at the apache section in here
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>
>> Seb
>>
>>
>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <duplyakin at uchicago.edu
>> > wrote:
>>
>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module (that we
>>> had to build from source).
>>>
>>> From Apache error log (with debug):
>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>>> canonicalising URL //localhost:8080/paraview/
>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>> 130.202.2.217] proxy: http: found worker http://localhost:8080/paraview
>>> for http://localhost:8080/paraview/, referer:
>>> http://54.211.22.94/apps/Cone/
>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running scheme
>>> http handler (attempt 0)
>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
>>> serving URL http://localhost:8080/paraview/
>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
>>> acquired connection for (localhost)
>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy: connecting
>>> http://localhost:8080/paraview/ to localhost:8080
>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy: connected
>>> /paraview/ to localhost:8080
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
>>> body send
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>> http://54.211.22.94/apps/Cone/
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>>> body send
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
>>> released connection for (localhost)
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>>> canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running scheme
>>> http handler (attempt 0)
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
>>> serving URL
>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
>>> acquired connection for (*)
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy: connecting
>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>> to 54.211.22.94:80
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy: connected
>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>> 54.211.22.94:80
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP: fam
>>> 2 socket created to connect to *
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
>>> connection complete to 54.211.22.94:80 (54.211.22.94)
>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does not
>>> exist: /pv/www/ws:
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
>>> body send
>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>>> body send
>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
>>> released connection for (*)
>>>
>>>
>>> POST took ~1 second. Timestamps for POST and the following GET:
>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>
>>>
>>>
>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Which version of Apache are you using? Do you have the ws_tunnelling
>>>> (<= wrong name but something like that) module enabled?
>>>>
>>>> You may be able to check the system log that apache generate to see
>>>> what went wrong.
>>>> Do you know how much time the POST request took?
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> Continue troubleshooting...
>>>>>
>>>>> Now we get this in response to POST:
>>>>>
>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>
>>>>> Looks right to me. Then, after that POST, it does GETs that do not
>>>>> look right:
>>>>>
>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>
>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>> Firefox/30.0"
>>>>>
>>>>> And the message:
>>>>>
>>>>> Firefox can't establish a connection to the server at ws://
>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>> return new WebSocket(url, protocols);
>>>>>
>>>>> What can possibly cause this? Again, complete apache and launcher
>>>>> configs are in the previous email.
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> This helped tremendously!
>>>>>>
>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>
>>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>>> Something there still needs attention and we are investigating further.
>>>>>>
>>>>>> Thanks for you patience and all the help that allows us to move
>>>>>> forward.
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>
>>>>>>> Hi Dmitry,
>>>>>>>
>>>>>>> you may still have a typo
>>>>>>>
>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>
>>>>>>> ${host} should have been replaced with a static string that match
>>>>>>> the host that the web browser is using to reach apache.
>>>>>>>
>>>>>>> Moreover, I forgot to mention that you need to add "-f" in your set
>>>>>>> of arguments. That will force some output generation to fill some buffer
>>>>>>> which will allow the launcher to detect when the server is actually ready.
>>>>>>>
>>>>>>> I've noticed that the documentation is missing them. Don't know
>>>>>>> why... Will update it at some point.
>>>>>>> Although this page show that option:
>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>
>>>>>>> And the value for "timeout" should be way bigger than 5. Like 25
>>>>>>> maybe.
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>> Thanks for this detailed description! The process is starting to
>>>>>>>> make sense and we can communicate more efficiently about our configuration
>>>>>>>> and problems.
>>>>>>>>
>>>>>>>> Here is our complete launch.json (with the right sessionURL for a
>>>>>>>> config with Apache, according to your email):
>>>>>>>> {
>>>>>>>> "configuration": {
>>>>>>>>   "content": "/pv/www",
>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>   "host": "localhost",
>>>>>>>>   "endpoint": "paraview",
>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>   "timeout": 5,
>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>   "port": 8080,
>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>> "apps": {
>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>> "properties": {
>>>>>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>   "data": "/pv/data",
>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>> }
>>>>>>>>
>>>>>>>> Apache host file:
>>>>>>>> <VirtualHost *:80>
>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>         <Directory /pv/www/>
>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>                 AllowOverride None
>>>>>>>>                 Order allow,deny
>>>>>>>>                 allow from all
>>>>>>>>         </Directory>
>>>>>>>>
>>>>>>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>
>>>>>>>>         RewriteEngine On
>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>  [P]
>>>>>>>>
>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>         RewriteLogLevel 3
>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>         LogLevel debug
>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>> </VirtualHost>
>>>>>>>>
>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>>>>> ps auwx | grep cone
>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>>>>>>> /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>
>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>
>>>>>>>> Any further advice?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Dmitry,
>>>>>>>>>
>>>>>>>>> First of all you need to understand the role of apache here in
>>>>>>>>> order to see how the configuration should be.
>>>>>>>>> As you may know, you can use ParaViewWeb without Apache, but such
>>>>>>>>> setup is not meant for production.
>>>>>>>>>
>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>> - Apache can be use to serve the static content (html, js, png,
>>>>>>>>> css...)
>>>>>>>>> - Apache provide a single entry point host + port. This prevent
>>>>>>>>> cross-domain issue or firewall limitation.
>>>>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>> Apache Web Server.
>>>>>>>>>
>>>>>>>>> Then you need to understand how the launcher works and its role.
>>>>>>>>> In ParaViewWeb a launcher is used to start a new visualization
>>>>>>>>> process for a given user. This simply mean running a command line with some
>>>>>>>>> dynamic parameters like the port number on which this specific instance
>>>>>>>>> should listen.
>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>
>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the same
>>>>>>>>> port as the main server (the process would not start). Hence, we start it
>>>>>>>>> with some port and we let the user know that it should connect to
>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>> was used to create the process.
>>>>>>>>>
>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>
>>>>>>>>> BUT with Apache that is different, now we have a process which is
>>>>>>>>> meant to relay the communication to the backend using the port and host
>>>>>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>> In the same time to keep track on which host/port a process is
>>>>>>>>> running the launcher generate a text file with the proper mapping.
>>>>>>>>> That mapping file is then used inside Apache to figure out how it
>>>>>>>>> should establish the connection to the backend.
>>>>>>>>>
>>>>>>>>> This should help you understand how to fix your configuration.
>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>
>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>
>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>
>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>
>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>
>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>
>>>>>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>>>>>
>>>>>>>>> > in launch.json there are two particular lines host/resources:
>>>>>>>>>
>>>>>>>>> So the "host" is to select the proper network card when you have
>>>>>>>>> several for the actual launcher server.
>>>>>>>>>
>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>
>>>>>>>>>> Launcher side:
>>>>>>>>>>>
>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>
>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>
>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>
>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>
>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>
>>>>>>>>>>   "port": 8080,
>>>>>>>>>>
>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the script
>>>>>>>>>> you've suggested earlier:
>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Apache side
>>>>>>>>>>>
>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>
>>>>>>>>>>> In Apache we have:
>>>>>>>>>> RewriteEngine On
>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Then when a session start you can check the content of that
>>>>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Verified that those entires are added to the file and have the
>>>>>>>>>> right format.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On the other hand you forgot that line in the config of your
>>>>>>>>>>> cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>
>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>
>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> You can check is any pvpython process is running, on which port,
>>>>>>>>>>> see if that match in the proxy file (/data/proxy.txt) and also looking at
>>>>>>>>>>> the log directory with the output of the pvpython process.
>>>>>>>>>>>
>>>>>>>>>>> A common error could also be that the apache does not have the
>>>>>>>>>>> right to read the /data/proxy.txt file or that the launcher is not able to
>>>>>>>>>>> write it.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Verified that launcher can write it and that entries are added.
>>>>>>>>>>
>>>>>>>>>> These are the rest of our questions (we need to sort these out
>>>>>>>>>> because they have caused some confusion and we want to clear things up and
>>>>>>>>>> do not come back to these issues anymore):
>>>>>>>>>>
>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>> - what particular modules in Apache are required? So far we have:
>>>>>>>>>> proxy_module, proxy_http_module, and rewrite_module. We are unsure whether
>>>>>>>>>> we need proxy_wstunnel_module or not.
>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>> "host": "localhost",
>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>
>>>>>>>>>> Appreciate your help!
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Good luck,
>>>>>>>>>>>
>>>>>>>>>>> Seb
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>
>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to
>>>>>>>>>>>> build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>
>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2
>>>>>>>>>>>> Ubuntu 12.04 instances.
>>>>>>>>>>>>
>>>>>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>> etc.)
>>>>>>>>>>>>
>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>
>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets called. In
>>>>>>>>>>>> order to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>>>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>> ...
>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>   };
>>>>>>>>>>>> ...
>>>>>>>>>>>>
>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>
>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>> proxy: Error reading from remote server returned by /paraview/, referer:
>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>> File does not exist: /pv/www/ws
>>>>>>>>>>>>
>>>>>>>>>>>> It appears that it has do to with Apache configuration, where
>>>>>>>>>>>> we have:
>>>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>
>>>>>>>>>>>> Do these Rewrite commands look right? How can their actions be
>>>>>>>>>>>> logged and verified?
>>>>>>>>>>>>
>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>
>>>>>>>>>>>> Is it possible that we are missing a module or some additional
>>>>>>>>>>>> configuration in Apache?
>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>> ...
>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>> ...
>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>
>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>
>>>>>>>>>>>> Your help will be much appreciated and will allow to move
>>>>>>>>>>>> forward with our isntallation.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/5ab03088/attachment-0001.html>

From sebastien.jourdain at kitware.com  Mon Jul 21 17:06:25 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 21 Jul 2014 15:06:25 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
Message-ID: <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>

Should work... I guess this documentation will always be out of date. ;-)

But the good news is that modern system have the right version of Apache,
so no fancy build are needed anymore...

Seb


On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

>  Trying to follow instructions from
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
> It looks like those urls used with wget are broken.
>
> Found a replacement for httpd:
>
> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O httpd.tgz
>
> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here is a
> working command:
>
> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>
> The last one works fine:
>
> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O apr-util.tgz
>
>
> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> Got it. Rebuilding Apache now.
>>
>> Thanks!
>>
>>
>>
>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> You must have Apache 2.4.7+
>>> Their is a fix in that version which allow mod_rewrite to work on web
>>> socket protocol instead of just http.
>>> You can look at the apache section in here
>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>
>>> Seb
>>>
>>>
>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module (that we
>>>> had to build from source).
>>>>
>>>> From Apache error log (with debug):
>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>>>> canonicalising URL //localhost:8080/paraview/
>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>> 130.202.2.217] proxy: http: found worker http://localhost:8080/paraview
>>>> for http://localhost:8080/paraview/, referer:
>>>> http://54.211.22.94/apps/Cone/
>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running scheme
>>>> http handler (attempt 0)
>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
>>>> serving URL http://localhost:8080/paraview/
>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
>>>> acquired connection for (localhost)
>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy: connected
>>>> /paraview/ to localhost:8080
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
>>>> body send
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>> http://54.211.22.94/apps/Cone/
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>>>> body send
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
>>>> released connection for (localhost)
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>>>> canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running scheme
>>>> http handler (attempt 0)
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy: HTTP:
>>>> serving URL
>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP: has
>>>> acquired connection for (*)
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>> connecting
>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>> to 54.211.22.94:80
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy: connected
>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>> 54.211.22.94:80
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP: fam
>>>> 2 socket created to connect to *
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
>>>> connection complete to 54.211.22.94:80 (54.211.22.94)
>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does not
>>>> exist: /pv/www/ws:
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy: start
>>>> body send
>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>>>> body send
>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP: has
>>>> released connection for (*)
>>>>
>>>>
>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com> wrote:
>>>>
>>>>> Which version of Apache are you using? Do you have the ws_tunnelling
>>>>> (<= wrong name but something like that) module enabled?
>>>>>
>>>>> You may be able to check the system log that apache generate to see
>>>>> what went wrong.
>>>>> Do you know how much time the POST request took?
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> Continue troubleshooting...
>>>>>>
>>>>>> Now we get this in response to POST:
>>>>>>
>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>
>>>>>> Looks right to me. Then, after that POST, it does GETs that do not
>>>>>> look right:
>>>>>>
>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>
>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>> Firefox/30.0"
>>>>>>
>>>>>> And the message:
>>>>>>
>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>> return new WebSocket(url, protocols);
>>>>>>
>>>>>> What can possibly cause this? Again, complete apache and launcher
>>>>>> configs are in the previous email.
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> This helped tremendously!
>>>>>>>
>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>
>>>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>>>> Something there still needs attention and we are investigating further.
>>>>>>>
>>>>>>> Thanks for you patience and all the help that allows us to move
>>>>>>> forward.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>
>>>>>>>> Hi Dmitry,
>>>>>>>>
>>>>>>>> you may still have a typo
>>>>>>>>
>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>
>>>>>>>> ${host} should have been replaced with a static string that match
>>>>>>>> the host that the web browser is using to reach apache.
>>>>>>>>
>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in your set
>>>>>>>> of arguments. That will force some output generation to fill some buffer
>>>>>>>> which will allow the launcher to detect when the server is actually ready.
>>>>>>>>
>>>>>>>> I've noticed that the documentation is missing them. Don't know
>>>>>>>> why... Will update it at some point.
>>>>>>>> Although this page show that option:
>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>
>>>>>>>> And the value for "timeout" should be way bigger than 5. Like 25
>>>>>>>> maybe.
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> Thanks for this detailed description! The process is starting to
>>>>>>>>> make sense and we can communicate more efficiently about our configuration
>>>>>>>>> and problems.
>>>>>>>>>
>>>>>>>>> Here is our complete launch.json (with the right sessionURL for a
>>>>>>>>> config with Apache, according to your email):
>>>>>>>>> {
>>>>>>>>> "configuration": {
>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>   "host": "localhost",
>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>   "timeout": 5,
>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>   "port": 8080,
>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>> "apps": {
>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>> "properties": {
>>>>>>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> Apache host file:
>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>                 AllowOverride None
>>>>>>>>>                 Order allow,deny
>>>>>>>>>                 allow from all
>>>>>>>>>         </Directory>
>>>>>>>>>
>>>>>>>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>
>>>>>>>>>         RewriteEngine On
>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>  [P]
>>>>>>>>>
>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>         LogLevel debug
>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>> </VirtualHost>
>>>>>>>>>
>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>>>>>> ps auwx | grep cone
>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>>>>>>>> /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>
>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>
>>>>>>>>> Any further advice?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>
>>>>>>>>>> First of all you need to understand the role of apache here in
>>>>>>>>>> order to see how the configuration should be.
>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache, but such
>>>>>>>>>> setup is not meant for production.
>>>>>>>>>>
>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>> - Apache can be use to serve the static content (html, js, png,
>>>>>>>>>> css...)
>>>>>>>>>> - Apache provide a single entry point host + port. This prevent
>>>>>>>>>> cross-domain issue or firewall limitation.
>>>>>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>> Apache Web Server.
>>>>>>>>>>
>>>>>>>>>> Then you need to understand how the launcher works and its role.
>>>>>>>>>> In ParaViewWeb a launcher is used to start a new visualization
>>>>>>>>>> process for a given user. This simply mean running a command line with some
>>>>>>>>>> dynamic parameters like the port number on which this specific instance
>>>>>>>>>> should listen.
>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>
>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the same
>>>>>>>>>> port as the main server (the process would not start). Hence, we start it
>>>>>>>>>> with some port and we let the user know that it should connect to
>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>> was used to create the process.
>>>>>>>>>>
>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>
>>>>>>>>>> BUT with Apache that is different, now we have a process which is
>>>>>>>>>> meant to relay the communication to the backend using the port and host
>>>>>>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>>>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>>>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>> In the same time to keep track on which host/port a process is
>>>>>>>>>> running the launcher generate a text file with the proper mapping.
>>>>>>>>>> That mapping file is then used inside Apache to figure out how it
>>>>>>>>>> should establish the connection to the backend.
>>>>>>>>>>
>>>>>>>>>> This should help you understand how to fix your configuration.
>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>
>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>
>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>
>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>
>>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>
>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>
>>>>>>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>>>>>>
>>>>>>>>>> > in launch.json there are two particular lines host/resources:
>>>>>>>>>>
>>>>>>>>>> So the "host" is to select the proper network card when you have
>>>>>>>>>> several for the actual launcher server.
>>>>>>>>>>
>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>
>>>>>>>>>> Seb
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>
>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>
>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>
>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>
>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>
>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>
>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>
>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>
>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the script
>>>>>>>>>>> you've suggested earlier:
>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Apache side
>>>>>>>>>>>>
>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>
>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Then when a session start you can check the content of that
>>>>>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Verified that those entires are added to the file and have the
>>>>>>>>>>> right format.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On the other hand you forgot that line in the config of your
>>>>>>>>>>>> cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>
>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>
>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> You can check is any pvpython process is running, on which
>>>>>>>>>>>> port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>
>>>>>>>>>>>> A common error could also be that the apache does not have the
>>>>>>>>>>>> right to read the /data/proxy.txt file or that the launcher is not able to
>>>>>>>>>>>> write it.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Verified that launcher can write it and that entries are added.
>>>>>>>>>>>
>>>>>>>>>>> These are the rest of our questions (we need to sort these out
>>>>>>>>>>> because they have caused some confusion and we want to clear things up and
>>>>>>>>>>> do not come back to these issues anymore):
>>>>>>>>>>>
>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>> - what particular modules in Apache are required? So far we
>>>>>>>>>>> have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host": "localhost"}],
>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>
>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>
>>>>>>>>>>>> Seb
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>
>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to
>>>>>>>>>>>>> build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2
>>>>>>>>>>>>> Ubuntu 12.04 instances.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>
>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>
>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets called. In
>>>>>>>>>>>>> order to test it, we used /pv/www/apps/TestApp/index.html as a template and
>>>>>>>>>>>>> created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>   };
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>
>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>>> proxy: Error reading from remote server returned by /paraview/, referer:
>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>>> File does not exist: /pv/www/ws
>>>>>>>>>>>>>
>>>>>>>>>>>>> It appears that it has do to with Apache configuration, where
>>>>>>>>>>>>> we have:
>>>>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>
>>>>>>>>>>>>> Do these Rewrite commands look right? How can their actions be
>>>>>>>>>>>>> logged and verified?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Is it possible that we are missing a module or some additional
>>>>>>>>>>>>> configuration in Apache?
>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>> ...
>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>
>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Your help will be much appreciated and will allow to move
>>>>>>>>>>>>> forward with our isntallation.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140721/0d663935/attachment-0001.html>

From Patrick.Begou at legi.grenoble-inp.fr  Tue Jul 22 04:17:38 2014
From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou)
Date: Tue, 22 Jul 2014 10:17:38 +0200
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
Message-ID: <53CE1E22.80008@legi.grenoble-inp.fr>

I've setup 4 new desktops using an Intel HD graphics 4600 chipset, runing CentOS 
6.5.
I'm using paraview 3.98 with Pvserver runing on a remonte cluster. Rendering is 
doftware and done on the cluster.

On these hosts I've some troubles whit the color map when viewing datas.

example:
I load the datas (it is a large 3D visualisation), use "Surface" mode, add a 
color legend it's OK.
Now I add a slice and click apply.
With this last command the colormap of the previous "surface" change and is no 
more in agrement with the color legend.

Removing the slice doesn't restore the right view.
I've switched from kernel-2.6.32-431 to kernel-ml-3.15 no change.

This problem doesn't exist with desktops using nvidia graphics boards and the 
same OS/software.
This problem doesn't exist when runing standalone paraview on the desktop (but 
it is realy slow with such large datas)

I don't know if it is paraview or Intel driver related.

Any suggestion ?

Patrick

-- 
===================================================================
|  Equipe M.O.S.T.         |                                      |
|  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
|  LEGI                    |                                      |
|  BP 53 X                 | Tel 04 76 82 51 35                   |
|  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
===================================================================


From utkarsh.ayachit at kitware.com  Tue Jul 22 08:26:40 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 08:26:40 -0400
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
In-Reply-To: <53CE1E22.80008@legi.grenoble-inp.fr>
References: <53CE1E22.80008@legi.grenoble-inp.fr>
Message-ID: <CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>

Do you any images that you can share that could illustrate the change?

Thanks
Utkarsh


On Tue, Jul 22, 2014 at 4:17 AM, Patrick Begou <
Patrick.Begou at legi.grenoble-inp.fr> wrote:

> I've setup 4 new desktops using an Intel HD graphics 4600 chipset, runing
> CentOS 6.5.
> I'm using paraview 3.98 with Pvserver runing on a remonte cluster.
> Rendering is doftware and done on the cluster.
>
> On these hosts I've some troubles whit the color map when viewing datas.
>
> example:
> I load the datas (it is a large 3D visualisation), use "Surface" mode, add
> a color legend it's OK.
> Now I add a slice and click apply.
> With this last command the colormap of the previous "surface" change and
> is no more in agrement with the color legend.
>
> Removing the slice doesn't restore the right view.
> I've switched from kernel-2.6.32-431 to kernel-ml-3.15 no change.
>
> This problem doesn't exist with desktops using nvidia graphics boards and
> the same OS/software.
> This problem doesn't exist when runing standalone paraview on the desktop
> (but it is realy slow with such large datas)
>
> I don't know if it is paraview or Intel driver related.
>
> Any suggestion ?
>
> Patrick
>
> --
> ===================================================================
> |  Equipe M.O.S.T.         |                                      |
> |  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
> |  LEGI                    |                                      |
> |  BP 53 X                 | Tel 04 76 82 51 35                   |
> |  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
> ===================================================================
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/af47a470/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jul 22 08:31:18 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 08:31:18 -0400
Subject: [Paraview] AMR Cut Plane
In-Reply-To: <53CD1CDA.7020206@informatik.tu-freiberg.de>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
 <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
 <53CD1CDA.7020206@informatik.tu-freiberg.de>
Message-ID: <CADHSJjD82cVekpFYCVUw4vTVDTQXRn-5xpuq7qUrtxcjgi3NGA@mail.gmail.com>

I believe the reader is missing the BlankCells(
http://www.vtk.org/doc/nightly/html/classvtkAMRUtilities.html#a6656bada8c6d01b43e15299567af7657)
call. If I remember correctly, the blanking cells generated
by vtkImageToAMR.cxx get lost when the data is saved to disk (since we
don't have a "true" vtkUniformGrid writer, we just write it out as
vtkImageData in the vth writer. As a result the blanking arrays need to
recomputed on reading back in.

Mind reporting a bug for this? Thanks.

Utkarsh


On Mon, Jul 21, 2014 at 9:59 AM, Henry Lehmann <
henry.lehmann at informatik.tu-freiberg.de> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello Paraview Users,
>
> i am recently working with vtkOverlappingAMR. i set up one of this
> data sets using the "Image to AMR" filter in paraview, which basicly
> creates an octree with 4 levels and 512 blocks on level 4 in my setup.
> so i basicly converted mydata.vti into mydata.vth.
>
> now i want to use mydata.vth in order to quickly calculate the result
> of an arbitrary pipeline and save time adjusting the parameters of the
> pipeline. i want to adjust the parameters on level 0 and then increase
> the level to see the full resolution result.
>
> for example i have the pipeline: mydata.vth (vtkOverlappingAMR) -> AMR
> Cut Plane. now i move the cut plane and apply to see the result. when
> increasing the level from 1 to 2 in the reader i get a strange result.
> it looks like paraview doesnt remove the regions in which the amr
> levels overlap. this means the amr cut plane cuts out the data on
> level 0 and on level 1. Since Image to AMR creates an octree in which
> all lower levels are overlapping with higher ones, the lower levels
> always cover the higher resolution results when setting the level
> above 1 in the amr reader.
>
> how can i fix this?
>
> Best regards,
> Henry
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTzRzaAAoJEM0zIsxevdB2dt0H/RoNtiBcpmvl8jmqqCdQXRm9
> PeUCcNw57sZHF3H8Wcl18vL8Vz/38h+T9JcpWEDEj33atElRHeKfXXkpMkaxz9qN
> YJKvTgPh4i94v7mfg+LnQk4LvgiTIv/3cYwD5mz2ga5EMC/FflLuZluR46JllZLi
> AS+arxbVEIW5yqEMFlrEtLoItqXkLIVUCjdfTbbfEmaBW1w73rA4/7tSVW7LaSKi
> yMt8qPOgVTis89dSN1v/d750X7Rz0HLZGmFz0QdasLJy9PHBaFo6Uz8mjEH0hJ5t
> kZdxZISIpxxl9GQNDKwZVRF6t1h8MqyOPwhQEjQHJOnHkbWS927xjyezn/8rDv0=
> =K0aa
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/651e1651/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jul 22 10:23:09 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 10:23:09 -0400
Subject: [Paraview] How to run ParaView in parallel
In-Reply-To: <CAJTHAufEtSsokyWr6kXzO2tXdLApMNFUs85qd-tx7czT=NjVuQ@mail.gmail.com>
References: <CAJTHAufEtSsokyWr6kXzO2tXdLApMNFUs85qd-tx7czT=NjVuQ@mail.gmail.com>
Message-ID: <CADHSJjD67Q9FZDeqrfiLLOgAPAj+uWrmwacHYMu+aEonBoZsEQ@mail.gmail.com>

I am guessing you get a spotty visualization when you manually connect to
the pvserver, is that correct. What type of dataset are you loading? Can
you share the data? Not sure if it's a rendering artifact or a side effect
of the data distribution, or something else.

Utkarsh


On Sun, Jun 22, 2014 at 9:55 PM, Victor <victor.major at gmail.com> wrote:

> I have compiled ParaView with MPI support, searched the internet, looked
> at examples and I cannot get it to work.
>
> I tried to run it with the following methods:
>
> 1. "Use multicore" setting within the GUI. I set it at 6 and got this
> during startup
>
> AutoMPI: SUCCESS: command is:
>  "/opt/openmpi-1.8.1/bin/mpiexec" "-np" "6"
> "/usr/local/lib/paraview-4.1/pvserver" "--server-port=45024"
> AutoMPI: starting process server
> -------------- server output --------------
> Waiting for client...
> AutoMPI: server successfully started.
>
>
> It looks normal.
>
> 2. Start pvserver with "mpirun -np 6 pvserver" and connect the client
> manually:
>
> Waiting for client...
> Connection URL: cs://consilience-ssd:11111
> Accepting connection(s): consilience-ssd:11111
> Client connected.
>
>
> It looks normal.
>
>
> The problem is that the output does not look normal. I am trying to
> display CFD external flow simulation data using a Slice filter and instead
> of a correct visualization of the flow I get a spotty field as per the
> image attached. I am also attaching the PV ProcessID screenshot.
>
> What do I need to do to make ParaView render in parallel and deliver
> correct visualization results?
>
> Thanks,
>
> Victor
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/3c147835/attachment-0001.html>

From duplyakin at uchicago.edu  Tue Jul 22 10:30:33 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Tue, 22 Jul 2014 09:30:33 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
Message-ID: <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>

Hi Sebastien,

Thanks again for your help yesterday!

We have upgraded and running Apache-2.4.7 now.

We are seeing a now error:
Firefox can't establish a connection to the server at ws://
ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
.
return new WebSocket(url, protocols);

Last line points to code in autobahn.js
ab._construct = function (url, protocols) {
   if ("WebSocket" in window) {
      // Chrome, MSIE, newer Firefox
      if (protocols) {
         *return new WebSocket(url, protocols);*
      } else {
         return new WebSocket(url);
      }
   } else if ("MozWebSocket" in window) {
      // older versions of Firefox prefix the WebSocket object
      if (protocols) {
         return new MozWebSocket(url, protocols);
      } else {
         return new MozWebSocket(url);
      }
   } else {
      return null;
   }
};

In the meantime, session gets created, session log has a standard opening
followed by many lines with "+" signs (which means it is running fine,
right?), POST is successful:
130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/ HTTP/1.1"
200 78 "http://54.211.22.94/apps/FileViewer/" "Mozilla/5.0 (Macintosh;
Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0".

Its response:

{"updir": "/Home", "sessionManagerURL":
"http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost",
"sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8",
"id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}

Are possibly missing anything here?

Looks like Apache log verifies that wstunnel is working:

[Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid
140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449]
AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8
to localhost:9999
[Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid
140393354098432] proxy_util.c(2610): AH00962: WS: connection complete
to 127.0.0.1:9999 (localhost)
[Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid
140393354098432] mod_proxy_wstunnel.c(253): [client
130.202.2.217:63449] AH02445: woke from poll(), i=1
[Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid
140393354098432] mod_proxy_wstunnel.c(262): [client
130.202.2.217:63449] AH02446: sock was readable
[Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid
140393354098432] mod_proxy_wstunnel.c(253): [client
130.202.2.217:63449] AH02445: woke from poll(), i=1
[Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid
140393354098432] mod_proxy_wstunnel.c(262): [client
130.202.2.217:63449] AH02446: sock was readable
[Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid
140393354098432] mod_proxy_wstunnel.c(253): [client
130.202.2.217:63449] AH02445: woke from poll(), i=1
[Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid
140393354098432] mod_proxy_wstunnel.c(262): [client
130.202.2.217:63449] AH02446: sock was readable
[Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid
140393354098432] proxy_util.c(2035): AH00943: WS: has released
connection for (*)

Any thoughts on what might be causing this problem?


On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Should work... I guess this documentation will always be out of date. ;-)
>
> But the good news is that modern system have the right version of Apache,
> so no fancy build are needed anymore...
>
> Seb
>
>
> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>>  Trying to follow instructions from
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>> It looks like those urls used with wget are broken.
>>
>> Found a replacement for httpd:
>>
>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O httpd.tgz
>>
>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here is a
>> working command:
>>
>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>
>> The last one works fine:
>>
>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O apr-util.tgz
>>
>>
>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <duplyakin at uchicago.edu
>> > wrote:
>>
>>> Got it. Rebuilding Apache now.
>>>
>>> Thanks!
>>>
>>>
>>>
>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> You must have Apache 2.4.7+
>>>> Their is a fix in that version which allow mod_rewrite to work on web
>>>> socket protocol instead of just http.
>>>> You can look at the apache section in here
>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module (that
>>>>> we had to build from source).
>>>>>
>>>>> From Apache error log (with debug):
>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>>>>> canonicalising URL //localhost:8080/paraview/
>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>> 130.202.2.217] proxy: http: found worker
>>>>> http://localhost:8080/paraview for http://localhost:8080/paraview/,
>>>>> referer: http://54.211.22.94/apps/Cone/
>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running scheme
>>>>> http handler (attempt 0)
>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>> HTTP: serving URL http://localhost:8080/paraview/
>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP:
>>>>> has acquired connection for (localhost)
>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>> connected /paraview/ to localhost:8080
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>> start body send
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>> http://54.211.22.94/apps/Cone/
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>>>>> body send
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP:
>>>>> has released connection for (localhost)
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy: HTTP:
>>>>> canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running scheme
>>>>> http handler (attempt 0)
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>> HTTP: serving URL
>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP:
>>>>> has acquired connection for (*)
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>> connecting
>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>> to 54.211.22.94:80
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>> connected
>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>> 54.211.22.94:80
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP:
>>>>> fam 2 socket created to connect to *
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
>>>>> connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does not
>>>>> exist: /pv/www/ws:
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>> start body send
>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy: end
>>>>> body send
>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP:
>>>>> has released connection for (*)
>>>>>
>>>>>
>>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> Which version of Apache are you using? Do you have the ws_tunnelling
>>>>>> (<= wrong name but something like that) module enabled?
>>>>>>
>>>>>> You may be able to check the system log that apache generate to see
>>>>>> what went wrong.
>>>>>> Do you know how much time the POST request took?
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> Continue troubleshooting...
>>>>>>>
>>>>>>> Now we get this in response to POST:
>>>>>>>
>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>
>>>>>>> Looks right to me. Then, after that POST, it does GETs that do not
>>>>>>> look right:
>>>>>>>
>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>
>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>> Firefox/30.0"
>>>>>>>
>>>>>>> And the message:
>>>>>>>
>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>> return new WebSocket(url, protocols);
>>>>>>>
>>>>>>> What can possibly cause this? Again, complete apache and launcher
>>>>>>> configs are in the previous email.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>> This helped tremendously!
>>>>>>>>
>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>
>>>>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>>>>> Something there still needs attention and we are investigating further.
>>>>>>>>
>>>>>>>> Thanks for you patience and all the help that allows us to move
>>>>>>>> forward.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Dmitry,
>>>>>>>>>
>>>>>>>>> you may still have a typo
>>>>>>>>>
>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>
>>>>>>>>> ${host} should have been replaced with a static string that match
>>>>>>>>> the host that the web browser is using to reach apache.
>>>>>>>>>
>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in your
>>>>>>>>> set of arguments. That will force some output generation to fill some
>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>> ready.
>>>>>>>>>
>>>>>>>>> I've noticed that the documentation is missing them. Don't know
>>>>>>>>> why... Will update it at some point.
>>>>>>>>> Although this page show that option:
>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>
>>>>>>>>> And the value for "timeout" should be way bigger than 5. Like 25
>>>>>>>>> maybe.
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Thanks for this detailed description! The process is starting to
>>>>>>>>>> make sense and we can communicate more efficiently about our configuration
>>>>>>>>>> and problems.
>>>>>>>>>>
>>>>>>>>>> Here is our complete launch.json (with the right sessionURL for a
>>>>>>>>>> config with Apache, according to your email):
>>>>>>>>>> {
>>>>>>>>>> "configuration": {
>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>   "port": 8080,
>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>> "apps": {
>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>> "properties": {
>>>>>>>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>> "localhost"}],
>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> Apache host file:
>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>                 allow from all
>>>>>>>>>>         </Directory>
>>>>>>>>>>
>>>>>>>>>>         ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>
>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>         RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>  [P]
>>>>>>>>>>
>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>         LogLevel debug
>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>> </VirtualHost>
>>>>>>>>>>
>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the browser,
>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>>>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>>>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32   0:00
>>>>>>>>>> /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>
>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>
>>>>>>>>>> Any further advice?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>
>>>>>>>>>>> First of all you need to understand the role of apache here in
>>>>>>>>>>> order to see how the configuration should be.
>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache, but
>>>>>>>>>>> such setup is not meant for production.
>>>>>>>>>>>
>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>> - Apache can be use to serve the static content (html, js, png,
>>>>>>>>>>> css...)
>>>>>>>>>>> - Apache provide a single entry point host + port. This prevent
>>>>>>>>>>> cross-domain issue or firewall limitation.
>>>>>>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>
>>>>>>>>>>> Then you need to understand how the launcher works and its role.
>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new visualization
>>>>>>>>>>> process for a given user. This simply mean running a command line with some
>>>>>>>>>>> dynamic parameters like the port number on which this specific instance
>>>>>>>>>>> should listen.
>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>
>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the same
>>>>>>>>>>> port as the main server (the process would not start). Hence, we start it
>>>>>>>>>>> with some port and we let the user know that it should connect to
>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>
>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>
>>>>>>>>>>> BUT with Apache that is different, now we have a process which
>>>>>>>>>>> is meant to relay the communication to the backend using the port and host
>>>>>>>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>>>>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>>>>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>> In the same time to keep track on which host/port a process is
>>>>>>>>>>> running the launcher generate a text file with the proper mapping.
>>>>>>>>>>> That mapping file is then used inside Apache to figure out how
>>>>>>>>>>> it should establish the connection to the backend.
>>>>>>>>>>>
>>>>>>>>>>> This should help you understand how to fix your configuration.
>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>
>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>
>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>
>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>
>>>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>
>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>
>>>>>>>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>>>>>>>
>>>>>>>>>>> > in launch.json there are two particular lines host/resources:
>>>>>>>>>>>
>>>>>>>>>>> So the "host" is to select the proper network card when you have
>>>>>>>>>>> several for the actual launcher server.
>>>>>>>>>>>
>>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>
>>>>>>>>>>> Seb
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>
>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>
>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>
>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>
>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>
>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>
>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>
>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>
>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the script
>>>>>>>>>>>> you've suggested earlier:
>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>
>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>
>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Then when a session start you can check the content of that
>>>>>>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Verified that those entires are added to the file and have the
>>>>>>>>>>>> right format.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> On the other hand you forgot that line in the config of your
>>>>>>>>>>>>> cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>
>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> You can check is any pvpython process is running, on which
>>>>>>>>>>>>> port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>
>>>>>>>>>>>>> A common error could also be that the apache does not have the
>>>>>>>>>>>>> right to read the /data/proxy.txt file or that the launcher is not able to
>>>>>>>>>>>>> write it.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Verified that launcher can write it and that entries are added.
>>>>>>>>>>>>
>>>>>>>>>>>> These are the rest of our questions (we need to sort these out
>>>>>>>>>>>> because they have caused some confusion and we want to clear things up and
>>>>>>>>>>>> do not come back to these issues anymore):
>>>>>>>>>>>>
>>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>> - what particular modules in Apache are required? So far we
>>>>>>>>>>>> have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>
>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to
>>>>>>>>>>>>>> build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2
>>>>>>>>>>>>>> Ubuntu 12.04 instances.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets called.
>>>>>>>>>>>>>> In order to test it, we used /pv/www/apps/TestApp/index.html as a template
>>>>>>>>>>>>>> and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>>>> proxy: Error reading from remote server returned by /paraview/, referer:
>>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>>>> File does not exist: /pv/www/ws
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> It appears that it has do to with Apache configuration, where
>>>>>>>>>>>>>> we have:
>>>>>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their actions
>>>>>>>>>>>>>> be logged and verified?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Your help will be much appreciated and will allow to move
>>>>>>>>>>>>>> forward with our isntallation.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/faa4d7cf/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Tue Jul 22 10:31:52 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 10:31:52 -0400
Subject: [Paraview] storing output calculated by python running in
 parallel - write to a file? (UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7AF1@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7ABF@umechp9h.easf.csd.disa.mil>
 <CADHSJjB6eb1qoGMAWXeoc7rb87mOjCMPt+pqp4Ed5Zxoh5oE3Q@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CC7AF1@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjBce+ND7gW-kWEarADnCthL1aUXSK8QycJxe6EJEBqy6w@mail.gmail.com>

Ah...no. Alas, you cannot directly use "CreateWriter" in the script
for the Programmable Filter. You'll need to use "save data" after
applying the filter. Alternatively, you can use mpi4py module to
gather the sum result to the root node and then on the root node,
create vtkDelimitedTextWriter directly and save the result out. I can
send you sample script, if you need one.

Utkarsh

p.s.  This email was waiting in draft state for a while for this
sample script, didn't get around to it. Figured I'd at least send this
response and work on the sample script if needed :).

On Mon, Jul 7, 2014 at 11:52 AM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hi Utkarsh,
>
> Yes that is exactly what I wanted to do. I am using the programmable filter to
> add up all the values for a cell/point variable by iterating through the
> number of cells/points using python loop and write out the sum. Is there an
> example on how to do this? How will I format the output before writing it to
> the file? In my script below which you helped with last week, how would you
> have the paraview.simple.CreateWriter() class to write out just the sum
> variable?
>
> Thank you very much
> -simon
>
>
>
>
> def calculateSum(input, output):
>     # Copy the cells etc.
>     output.ShallowCopy(input)
>
>     # Get the array to calculate the coefficient
>     toSum = output.GetPointData().GetArray("MOMENT_X")
>
>     # for each of the elements, calculate the three roots and store the real
> and imaginary output in separate arrays
>     numPoints = toSum.GetSize()
>
>     tsum = 0
>
>     for i in range(0, numPoints):
>         tsum = tsum + toSum.GetValue(i)
>     return tsum
>
>
> input = self.GetInputDataObject(0, 0)
> output = self.GetOutputDataObject(0)
> sum = 0
>
> print sum
> if input.IsA("vtkUniformGridAMR"):
>     # This initializes AMR properly. It will share the dataset instances
>     # but we will clone those later.
>     output.ShallowCopy(input)
>
>     iter = input.NewIterator()
>     iter.UnRegister(None)
>     iter.InitTraversal()
>     while not iter.IsDoneWithTraversal():
>         curInput = iter.GetCurrentDataObject()
>         curOutput = curInput.NewInstance()
>         sum = sum + calculateSum(curInput, curOutput)
>         output.SetDataSet(iter, curOutput)
>         curOutput.UnRegister(None)
>         iter.GoToNextItem();
> else:
>     sum = sum + calculateSum(input, output)
>
> # write sum to file
> writer = CreateWriter('foo.csv')
> ......
>
>
>
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Monday, July 07, 2014 11:36 AM
> To: Su, Simon M CTR USARMY ARL (US)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] storing output calculated by python running in
> parallel - write to a file? (UNCLASSIFIED)
>
> Simon,
>
> If you're saving out data generated by a pipeline (which can include
> Programmable filter or Python calculator), then you should use
> CreateWriter(http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.simple.html#paraview.simple.CreateWriter)
> to create a writer and then write the data out -- akin to "Save Data"
> in ParaView.
>
> Utkarsh
>
> On Mon, Jul 7, 2014 at 11:30 AM, Su, Simon M CTR USARMY ARL (US)
> <simon.m.su.ctr at mail.mil> wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Hello,
>>
>> In my python script (ran using pvbatch mypythonscript.py in parallel
>> environment), how do I save out the data I calculated to a file? How
>> will be parallel execution affect the writing of the output to a file
>> (which process will be doing the writing)?
>>
>> In a none parallel mode, this is what I want to do which write the
>> output to out.txt file.
>>
>> f = open('out.txt', 'w')
>> print >> f, 'Filename:', filename  # or f.write('...\n')
>> f.close()
>>
>> what is the parallel equivalent of that?
>>
>> Any help is much appreciated.
>>
>> Thanks
>> -simon
>>
>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>

From Patrick.Begou at legi.grenoble-inp.fr  Tue Jul 22 10:32:39 2014
From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou)
Date: Tue, 22 Jul 2014 16:32:39 +0200
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
In-Reply-To: <CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>
References: <53CE1E22.80008@legi.grenoble-inp.fr>
 <CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>
Message-ID: <53CE7607.50503@legi.grenoble-inp.fr>

Hi Utkarsh

I can't show you this dataset (as the geomtry studied by this PhD student is 
confidential) but I can reproduce the problem with another dataset. Here, it 
appears immediatly, no need to add a slice to show the problem.

This is a large dataset (1024? grid points).

Thanks

Patrick

-- 
===================================================================
|  Equipe M.O.S.T.         |                                      |
|  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
|  LEGI                    |                                      |
|  BP 53 X                 | Tel 04 76 82 51 35                   |
|  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
===================================================================

-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraviewbad.jpg
Type: image/jpeg
Size: 46139 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/c009383a/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paraviewgood.jpg
Type: image/jpeg
Size: 60748 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/c009383a/attachment-0003.jpg>

From utkarsh.ayachit at kitware.com  Tue Jul 22 10:35:19 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 10:35:19 -0400
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
In-Reply-To: <53CE7607.50503@legi.grenoble-inp.fr>
References: <53CE1E22.80008@legi.grenoble-inp.fr>
 <CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>
 <53CE7607.50503@legi.grenoble-inp.fr>
Message-ID: <CADHSJjC3hO6xDt3kOJ26YXpfQqYPe=1K7S3zBF9c-3UDU41m5g@mail.gmail.com>

Alas, no idea what could be happening. A random guess, try toggling
"Interpolate Scalars Before Mapping" check box on the Properties panel.
Let's see if that makes any difference.

Utkarsh


On Tue, Jul 22, 2014 at 10:32 AM, Patrick Begou <
Patrick.Begou at legi.grenoble-inp.fr> wrote:

> Hi Utkarsh
>
> I can't show you this dataset (as the geomtry studied by this PhD student
> is confidential) but I can reproduce the problem with another dataset.
> Here, it appears immediatly, no need to add a slice to show the problem.
>
> This is a large dataset (1024? grid points).
>
> Thanks
>
>
> Patrick
>
> --
> ===================================================================
> |  Equipe M.O.S.T.         |                                      |
> |  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
> |  LEGI                    |                                      |
> |  BP 53 X                 | Tel 04 76 82 51 35                   |
> |  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
> ===================================================================
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/68b57bc2/attachment.html>

From duplyakin at uchicago.edu  Tue Jul 22 10:39:56 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Tue, 22 Jul 2014 09:39:56 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
Message-ID: <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>

All I see is described js error. (I see it in the Firefox'es Firebug
console)


On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <karpeev at mcs.anl.gov>
wrote:

> Is there a Python error/stack trace that comes with this?
> On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <duplyakin at uchicago.edu>
> wrote:
>
>> Hi Sebastien,
>>
>> Thanks again for your help yesterday!
>>
>> We have upgraded and running Apache-2.4.7 now.
>>
>> We are seeing a now error:
>>  Firefox can't establish a connection to the server at ws://
>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>> .
>> return new WebSocket(url, protocols);
>>
>> Last line points to code in autobahn.js
>> ab._construct = function (url, protocols) {
>>    if ("WebSocket" in window) {
>>       // Chrome, MSIE, newer Firefox
>>       if (protocols) {
>>          *return new WebSocket(url, protocols);*
>>       } else {
>>          return new WebSocket(url);
>>       }
>>    } else if ("MozWebSocket" in window) {
>>       // older versions of Firefox prefix the WebSocket object
>>       if (protocols) {
>>          return new MozWebSocket(url, protocols);
>>       } else {
>>          return new MozWebSocket(url);
>>       }
>>    } else {
>>       return null;
>>    }
>> };
>>
>> In the meantime, session gets created, session log has a standard opening
>> followed by many lines with "+" signs (which means it is running fine,
>> right?), POST is successful:
>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/ HTTP/1.1"
>> 200 78 "http://54.211.22.94/apps/FileViewer/" "Mozilla/5.0 (Macintosh;
>> Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0".
>>
>> Its response:
>>
>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>
>> Are possibly missing anything here?
>>
>> Looks like Apache log verifies that wstunnel is working:
>>
>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>
>> Any thoughts on what might be causing this problem?
>>
>>
>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Should work... I guess this documentation will always be out of date. ;-)
>>>
>>> But the good news is that modern system have the right version of
>>> Apache, so no fancy build are needed anymore...
>>>
>>> Seb
>>>
>>>
>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>>  Trying to follow instructions from
>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>> It looks like those urls used with wget are broken.
>>>>
>>>> Found a replacement for httpd:
>>>>
>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>> httpd.tgz
>>>>
>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here is a
>>>> working command:
>>>>
>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>
>>>> The last one works fine:
>>>>
>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O apr-util.tgz
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> Got it. Rebuilding Apache now.
>>>>>
>>>>> Thanks!
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> You must have Apache 2.4.7+
>>>>>> Their is a fix in that version which allow mod_rewrite to work on web
>>>>>> socket protocol instead of just http.
>>>>>> You can look at the apache section in here
>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module (that
>>>>>>> we had to build from source).
>>>>>>>
>>>>>>> From Apache error log (with debug):
>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>> HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>>>> 130.202.2.217] proxy: http: found worker
>>>>>>> http://localhost:8080/paraview for http://localhost:8080/paraview/,
>>>>>>> referer: http://54.211.22.94/apps/Cone/
>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running scheme
>>>>>>> http handler (attempt 0)
>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>> HTTP: serving URL http://localhost:8080/paraview/
>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP:
>>>>>>> has acquired connection for (localhost)
>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>> connected /paraview/ to localhost:8080
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>> start body send
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>> end body send
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP:
>>>>>>> has released connection for (localhost)
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>> HTTP: canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running scheme
>>>>>>> http handler (attempt 0)
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>> HTTP: serving URL
>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP:
>>>>>>> has acquired connection for (*)
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>> connecting
>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>> to 54.211.22.94:80
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>> connected
>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>> 54.211.22.94:80
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP:
>>>>>>> fam 2 socket created to connect to *
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
>>>>>>> connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does
>>>>>>> not exist: /pv/www/ws:
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>> start body send
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>> end body send
>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP:
>>>>>>> has released connection for (*)
>>>>>>>
>>>>>>>
>>>>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>
>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>
>>>>>>>> You may be able to check the system log that apache generate to see
>>>>>>>> what went wrong.
>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> Continue troubleshooting...
>>>>>>>>>
>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>
>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>
>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that do not
>>>>>>>>> look right:
>>>>>>>>>
>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>
>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>> Firefox/30.0"
>>>>>>>>>
>>>>>>>>> And the message:
>>>>>>>>>
>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>
>>>>>>>>> What can possibly cause this? Again, complete apache and launcher
>>>>>>>>> configs are in the previous email.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> This helped tremendously!
>>>>>>>>>>
>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>
>>>>>>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>>>>>>> Something there still needs attention and we are investigating further.
>>>>>>>>>>
>>>>>>>>>> Thanks for you patience and all the help that allows us to move
>>>>>>>>>> forward.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>
>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>
>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>
>>>>>>>>>>> ${host} should have been replaced with a static string that
>>>>>>>>>>> match the host that the web browser is using to reach apache.
>>>>>>>>>>>
>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in your
>>>>>>>>>>> set of arguments. That will force some output generation to fill some
>>>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>>>> ready.
>>>>>>>>>>>
>>>>>>>>>>> I've noticed that the documentation is missing them. Don't know
>>>>>>>>>>> why... Will update it at some point.
>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>
>>>>>>>>>>> And the value for "timeout" should be way bigger than 5. Like
>>>>>>>>>>> 25 maybe.
>>>>>>>>>>>
>>>>>>>>>>> Seb
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks for this detailed description! The process is starting
>>>>>>>>>>>> to make sense and we can communicate more efficiently about our
>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>
>>>>>>>>>>>> Here is our complete launch.json (with the right sessionURL for
>>>>>>>>>>>> a config with Apache, according to your email):
>>>>>>>>>>>> {
>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>   "python_path": "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>
>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>
>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>
>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>
>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the
>>>>>>>>>>>> browser,
>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>>>>>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>>>>>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32
>>>>>>>>>>>> 0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>
>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>
>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>
>>>>>>>>>>>>> First of all you need to understand the role of apache here in
>>>>>>>>>>>>> order to see how the configuration should be.
>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache, but
>>>>>>>>>>>>> such setup is not meant for production.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>> - Apache can be use to serve the static content (html, js,
>>>>>>>>>>>>> png, css...)
>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>>>>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>>>>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Then you need to understand how the launcher works and its
>>>>>>>>>>>>> role.
>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new visualization
>>>>>>>>>>>>> process for a given user. This simply mean running a command line with some
>>>>>>>>>>>>> dynamic parameters like the port number on which this specific instance
>>>>>>>>>>>>> should listen.
>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>
>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the
>>>>>>>>>>>>> same port as the main server (the process would not start). Hence, we start
>>>>>>>>>>>>> it with some port and we let the user know that it should connect to
>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>
>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>
>>>>>>>>>>>>> BUT with Apache that is different, now we have a process which
>>>>>>>>>>>>> is meant to relay the communication to the backend using the port and host
>>>>>>>>>>>>> that Apache is using. So the launcher should let the client know what URL
>>>>>>>>>>>>> they should use so Apache could handle it and forward it to the backend.
>>>>>>>>>>>>> Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>> In the same time to keep track on which host/port a process is
>>>>>>>>>>>>> running the launcher generate a text file with the proper mapping.
>>>>>>>>>>>>> That mapping file is then used inside Apache to figure out how
>>>>>>>>>>>>> it should establish the connection to the backend.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This should help you understand how to fix your configuration.
>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>
>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>
>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>
>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Read the documentation, the list is minimum and provided in it.
>>>>>>>>>>>>>
>>>>>>>>>>>>> > in launch.json there are two particular lines host/resources:
>>>>>>>>>>>>>
>>>>>>>>>>>>> So the "host" is to select the proper network card when you
>>>>>>>>>>>>> have several for the actual launcher server.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the script
>>>>>>>>>>>>>> you've suggested earlier:
>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Then when a session start you can check the content of that
>>>>>>>>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Verified that those entires are added to the file and have
>>>>>>>>>>>>>> the right format.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On the other hand you forgot that line in the config of your
>>>>>>>>>>>>>>> cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> You can check is any pvpython process is running, on which
>>>>>>>>>>>>>>> port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> A common error could also be that the apache does not have
>>>>>>>>>>>>>>> the right to read the /data/proxy.txt file or that the launcher is not able
>>>>>>>>>>>>>>> to write it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Verified that launcher can write it and that entries are
>>>>>>>>>>>>>> added.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> These are the rest of our questions (we need to sort these
>>>>>>>>>>>>>> out because they have caused some confusion and we want to clear things up
>>>>>>>>>>>>>> and do not come back to these issues anymore):
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>> - what particular modules in Apache are required? So far we
>>>>>>>>>>>>>> have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to
>>>>>>>>>>>>>>>> build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2
>>>>>>>>>>>>>>>> Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We have verified that PV builds without errors and that PVW
>>>>>>>>>>>>>>>> launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets called.
>>>>>>>>>>>>>>>> In order to test it, we used /pv/www/apps/TestApp/index.html as a template
>>>>>>>>>>>>>>>> and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>>>>>> proxy: Error reading from remote server returned by /paraview/, referer:
>>>>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client 128.135.188.231]
>>>>>>>>>>>>>>>> File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> It appears that it has do to with Apache configuration,
>>>>>>>>>>>>>>>> where we have:
>>>>>>>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their actions
>>>>>>>>>>>>>>>> be logged and verified?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to move
>>>>>>>>>>>>>>>> forward with our isntallation.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/ae5973e1/attachment-0001.html>

From louie.cardone-noott at linacre.ox.ac.uk  Tue Jul 22 10:51:48 2014
From: louie.cardone-noott at linacre.ox.ac.uk (Louie Cardone-Noott)
Date: Tue, 22 Jul 2014 15:51:48 +0100
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
In-Reply-To: <54624cd4-64de-4f86-98cc-7ab430a17c7a@HUB02.ad.oak.ox.ac.uk>
References: <53CE1E22.80008@legi.grenoble-inp.fr>
 <CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>
 <53CE7607.50503@legi.grenoble-inp.fr>
 <54624cd4-64de-4f86-98cc-7ab430a17c7a@HUB02.ad.oak.ox.ac.uk>
Message-ID: <CAOCDKs_2E5xxUM=6wyxsa+9jNkoG22mJeaiHBT4SSoJvLbexnQ@mail.gmail.com>

I used to get a similar effect when setting the opacity or manually
adjusting slices etc. on the integrated graphics of an Intel i5-3570 (HD
2500 graphics). I gave up trying to find a solution and got a discrete GPU
installed.

Louie


On 22 July 2014 15:35, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:

> Alas, no idea what could be happening. A random guess, try toggling
> "Interpolate Scalars Before Mapping" check box on the Properties panel.
> Let's see if that makes any difference.
>
> Utkarsh
>
>
> On Tue, Jul 22, 2014 at 10:32 AM, Patrick Begou <
> Patrick.Begou at legi.grenoble-inp.fr> wrote:
>
>> Hi Utkarsh
>>
>> I can't show you this dataset (as the geomtry studied by this PhD student
>> is confidential) but I can reproduce the problem with another dataset.
>> Here, it appears immediatly, no need to add a slice to show the problem.
>>
>> This is a large dataset (1024? grid points).
>>
>> Thanks
>>
>>
>> Patrick
>>
>> --
>> ===================================================================
>> |  Equipe M.O.S.T.         |                                      |
>> |  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
>> |  LEGI                    |                                      |
>> |  BP 53 X                 | Tel 04 76 82 51 35                   |
>> |  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
>> ===================================================================
>>
>>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/452a523a/attachment.html>

From sebastien.jourdain at kitware.com  Tue Jul 22 11:44:20 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 22 Jul 2014 09:44:20 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
Message-ID: <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>

Hi Dmitry,

I've just tried to connect to your server and it seems that the process
start in about 1s. That might be correct but it seems fast to me.
Do you see any error after the +++++ log file?

Could you edit your launcher config to add an entry for the "pipeline" app?
The cone is just relying on VTK and I was curious if we could see something
different with our main sample app that use paraview.

For that you just need to kill the launcher process and restart it with the
new config.

Seb


On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> All I see is described js error. (I see it in the Firefox'es Firebug
> console)
>
>
> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <karpeev at mcs.anl.gov>
> wrote:
>
>> Is there a Python error/stack trace that comes with this?
>> On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <duplyakin at uchicago.edu>
>> wrote:
>>
>>> Hi Sebastien,
>>>
>>> Thanks again for your help yesterday!
>>>
>>> We have upgraded and running Apache-2.4.7 now.
>>>
>>> We are seeing a now error:
>>>  Firefox can't establish a connection to the server at ws://
>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>> .
>>> return new WebSocket(url, protocols);
>>>
>>> Last line points to code in autobahn.js
>>> ab._construct = function (url, protocols) {
>>>    if ("WebSocket" in window) {
>>>       // Chrome, MSIE, newer Firefox
>>>       if (protocols) {
>>>          *return new WebSocket(url, protocols);*
>>>       } else {
>>>          return new WebSocket(url);
>>>       }
>>>    } else if ("MozWebSocket" in window) {
>>>       // older versions of Firefox prefix the WebSocket object
>>>       if (protocols) {
>>>          return new MozWebSocket(url, protocols);
>>>       } else {
>>>          return new MozWebSocket(url);
>>>       }
>>>    } else {
>>>       return null;
>>>    }
>>> };
>>>
>>> In the meantime, session gets created, session log has a standard
>>> opening followed by many lines with "+" signs (which means it is running
>>> fine, right?), POST is successful:
>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/" "Mozilla/5.0
>>> (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0".
>>>
>>> Its response:
>>>
>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>
>>> Are possibly missing anything here?
>>>
>>> Looks like Apache log verifies that wstunnel is working:
>>>
>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>
>>> Any thoughts on what might be causing this problem?
>>>
>>>
>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Should work... I guess this documentation will always be out of date.
>>>> ;-)
>>>>
>>>> But the good news is that modern system have the right version of
>>>> Apache, so no fancy build are needed anymore...
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>>  Trying to follow instructions from
>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>> It looks like those urls used with wget are broken.
>>>>>
>>>>> Found a replacement for httpd:
>>>>>
>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>>> httpd.tgz
>>>>>
>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here is a
>>>>> working command:
>>>>>
>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>
>>>>> The last one works fine:
>>>>>
>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>> apr-util.tgz
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> Got it. Rebuilding Apache now.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>
>>>>>>> You must have Apache 2.4.7+
>>>>>>> Their is a fix in that version which allow mod_rewrite to work
>>>>>>> on web socket protocol instead of just http.
>>>>>>> You can look at the apache section in here
>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module
>>>>>>>> (that we had to build from source).
>>>>>>>>
>>>>>>>> From Apache error log (with debug):
>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>> HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>>>>> 130.202.2.217] proxy: http: found worker
>>>>>>>> http://localhost:8080/paraview for http://localhost:8080/paraview/,
>>>>>>>> referer: http://54.211.22.94/apps/Cone/
>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>> scheme http handler (attempt 0)
>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>>> HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy: HTTP:
>>>>>>>> has acquired connection for (localhost)
>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>> connected /paraview/ to localhost:8080
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>>> start body send
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>>> end body send
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP:
>>>>>>>> has released connection for (localhost)
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>> HTTP: canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>> scheme http handler (attempt 0)
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>>> HTTP: serving URL
>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy: HTTP:
>>>>>>>> has acquired connection for (*)
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>> connecting
>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>> to 54.211.22.94:80
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>> connected
>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>> 54.211.22.94:80
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy: HTTP:
>>>>>>>> fam 2 socket created to connect to *
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy: HTTP:
>>>>>>>> connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does
>>>>>>>> not exist: /pv/www/ws:
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>>> start body send
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>>> end body send
>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy: HTTP:
>>>>>>>> has released connection for (*)
>>>>>>>>
>>>>>>>>
>>>>>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>>>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>
>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>
>>>>>>>>> You may be able to check the system log that apache generate to
>>>>>>>>> see what went wrong.
>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>
>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>
>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>
>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that do
>>>>>>>>>> not look right:
>>>>>>>>>>
>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>
>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>
>>>>>>>>>> And the message:
>>>>>>>>>>
>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>
>>>>>>>>>> What can possibly cause this? Again, complete apache and launcher
>>>>>>>>>> configs are in the previous email.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>
>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>
>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>>>>>>>> Something there still needs attention and we are investigating further.
>>>>>>>>>>>
>>>>>>>>>>> Thanks for you patience and all the help that allows us to move
>>>>>>>>>>> forward.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>
>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>
>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>
>>>>>>>>>>>> ${host} should have been replaced with a static string that
>>>>>>>>>>>> match the host that the web browser is using to reach apache.
>>>>>>>>>>>>
>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in your
>>>>>>>>>>>> set of arguments. That will force some output generation to fill some
>>>>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>>>>> ready.
>>>>>>>>>>>>
>>>>>>>>>>>> I've noticed that the documentation is missing them. Don't know
>>>>>>>>>>>> why... Will update it at some point.
>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>
>>>>>>>>>>>> And the value for "timeout" should be way bigger than 5. Like
>>>>>>>>>>>> 25 maybe.
>>>>>>>>>>>>
>>>>>>>>>>>> Seb
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for this detailed description! The process is starting
>>>>>>>>>>>>> to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here is our complete launch.json (with the right sessionURL
>>>>>>>>>>>>> for a config with Apache, according to your email):
>>>>>>>>>>>>> {
>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>> }
>>>>>>>>>>>>>
>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>
>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>
>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>
>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the
>>>>>>>>>>>>> browser,
>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR PVW
>>>>>>>>>>>>> server>:/paraview/","application":"cone"}. Then Launcher starts a process
>>>>>>>>>>>>> listening to a port from the range (e.g. 9999). We can see that process:
>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32
>>>>>>>>>>>>> 0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>
>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>
>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> First of all you need to understand the role of apache here
>>>>>>>>>>>>>> in order to see how the configuration should be.
>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache, but
>>>>>>>>>>>>>> such setup is not meant for production.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>> - Apache can be use to serve the static content (html, js,
>>>>>>>>>>>>>> png, css...)
>>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the proper
>>>>>>>>>>>>>> ParaViewWeb instance on the backend based on a session ID. This mean that
>>>>>>>>>>>>>> the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Then you need to understand how the launcher works and its
>>>>>>>>>>>>>> role.
>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the
>>>>>>>>>>>>>> same port as the main server (the process would not start). Hence, we start
>>>>>>>>>>>>>> it with some port and we let the user know that it should connect to
>>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> BUT with Apache that is different, now we have a process
>>>>>>>>>>>>>> which is meant to relay the communication to the backend using the port and
>>>>>>>>>>>>>> host that Apache is using. So the launcher should let the client know what
>>>>>>>>>>>>>> URL they should use so Apache could handle it and forward it to the
>>>>>>>>>>>>>> backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>> In the same time to keep track on which host/port a process
>>>>>>>>>>>>>> is running the launcher generate a text file with the proper mapping.
>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure out
>>>>>>>>>>>>>> how it should establish the connection to the backend.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This should help you understand how to fix your configuration.
>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Read the documentation, the list is minimum and provided in
>>>>>>>>>>>>>> it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So the "host" is to select the proper network card when you
>>>>>>>>>>>>>> have several for the actual launcher server.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the script
>>>>>>>>>>>>>>> you've suggested earlier:
>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Then when a session start you can check the content of that
>>>>>>>>>>>>>>>> /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Verified that those entires are added to the file and have
>>>>>>>>>>>>>>> the right format.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config of
>>>>>>>>>>>>>>>> your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on which
>>>>>>>>>>>>>>>> port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> A common error could also be that the apache does not have
>>>>>>>>>>>>>>>> the right to read the /data/proxy.txt file or that the launcher is not able
>>>>>>>>>>>>>>>> to write it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Verified that launcher can write it and that entries are
>>>>>>>>>>>>>>> added.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort these
>>>>>>>>>>>>>>> out because they have caused some confusion and we want to clear things up
>>>>>>>>>>>>>>> and do not come back to these issues anymore):
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>> - what particular modules in Apache are required? So far we
>>>>>>>>>>>>>>> have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping to
>>>>>>>>>>>>>>>>> build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon EC2
>>>>>>>>>>>>>>>>> Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and that
>>>>>>>>>>>>>>>>> PVW launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>     sessionManagerURL: vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> It appears that it has do to with Apache configuration,
>>>>>>>>>>>>>>>>> where we have:
>>>>>>>>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to move
>>>>>>>>>>>>>>>>> forward with our isntallation.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/5fe238bf/attachment-0001.html>

From sebastien.jourdain at kitware.com  Tue Jul 22 11:47:51 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 22 Jul 2014 09:47:51 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
Message-ID: <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>

Just a though...

Which version of ParaView did you build? git master?

If so, did you use the www directory from that build or did you use the one
from the binaries?
There could be a version miss match in that later case.

Seb


On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Hi Dmitry,
>
> I've just tried to connect to your server and it seems that the process
> start in about 1s. That might be correct but it seems fast to me.
> Do you see any error after the +++++ log file?
>
> Could you edit your launcher config to add an entry for the "pipeline" app?
> The cone is just relying on VTK and I was curious if we could see
> something different with our main sample app that use paraview.
>
> For that you just need to kill the launcher process and restart it with
> the new config.
>
> Seb
>
>
> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> All I see is described js error. (I see it in the Firefox'es Firebug
>> console)
>>
>>
>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <karpeev at mcs.anl.gov>
>> wrote:
>>
>>> Is there a Python error/stack trace that comes with this?
>>> On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <duplyakin at uchicago.edu>
>>> wrote:
>>>
>>>> Hi Sebastien,
>>>>
>>>> Thanks again for your help yesterday!
>>>>
>>>> We have upgraded and running Apache-2.4.7 now.
>>>>
>>>> We are seeing a now error:
>>>>  Firefox can't establish a connection to the server at ws://
>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>> .
>>>> return new WebSocket(url, protocols);
>>>>
>>>> Last line points to code in autobahn.js
>>>> ab._construct = function (url, protocols) {
>>>>    if ("WebSocket" in window) {
>>>>       // Chrome, MSIE, newer Firefox
>>>>       if (protocols) {
>>>>          *return new WebSocket(url, protocols);*
>>>>       } else {
>>>>          return new WebSocket(url);
>>>>       }
>>>>    } else if ("MozWebSocket" in window) {
>>>>       // older versions of Firefox prefix the WebSocket object
>>>>       if (protocols) {
>>>>          return new MozWebSocket(url, protocols);
>>>>       } else {
>>>>          return new MozWebSocket(url);
>>>>       }
>>>>    } else {
>>>>       return null;
>>>>    }
>>>> };
>>>>
>>>> In the meantime, session gets created, session log has a standard
>>>> opening followed by many lines with "+" signs (which means it is running
>>>> fine, right?), POST is successful:
>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/" "Mozilla/5.0
>>>> (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0".
>>>>
>>>> Its response:
>>>>
>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>
>>>> Are possibly missing anything here?
>>>>
>>>> Looks like Apache log verifies that wstunnel is working:
>>>>
>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>
>>>> Any thoughts on what might be causing this problem?
>>>>
>>>>
>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com> wrote:
>>>>
>>>>> Should work... I guess this documentation will always be out of date.
>>>>> ;-)
>>>>>
>>>>> But the good news is that modern system have the right version of
>>>>> Apache, so no fancy build are needed anymore...
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>>  Trying to follow instructions from
>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>> It looks like those urls used with wget are broken.
>>>>>>
>>>>>> Found a replacement for httpd:
>>>>>>
>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>>>> httpd.tgz
>>>>>>
>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here is
>>>>>> a working command:
>>>>>>
>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>
>>>>>> The last one works fine:
>>>>>>
>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>> apr-util.tgz
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>
>>>>>>>> You must have Apache 2.4.7+
>>>>>>>> Their is a fix in that version which allow mod_rewrite to work
>>>>>>>> on web socket protocol instead of just http.
>>>>>>>> You can look at the apache section in here
>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module
>>>>>>>>> (that we had to build from source).
>>>>>>>>>
>>>>>>>>> From Apache error log (with debug):
>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>> HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>>>>>> 130.202.2.217] proxy: http: found worker
>>>>>>>>> http://localhost:8080/paraview for http://localhost:8080/paraview/,
>>>>>>>>> referer: http://54.211.22.94/apps/Cone/
>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>>>> HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>> HTTP: has acquired connection for (localhost)
>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>> connected /paraview/ to localhost:8080
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>>>> start body send
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>>>> end body send
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>> HTTP: has released connection for (localhost)
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>> HTTP: canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>>>> HTTP: serving URL
>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>> HTTP: has acquired connection for (*)
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>> connecting
>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>> to 54.211.22.94:80
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>> connected
>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>> 54.211.22.94:80
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy:
>>>>>>>>> HTTP: fam 2 socket created to connect to *
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy:
>>>>>>>>> HTTP: connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File does
>>>>>>>>> not exist: /pv/www/ws:
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>>>> start body send
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>>>> end body send
>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>> HTTP: has released connection for (*)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>>>>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>
>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>
>>>>>>>>>> You may be able to check the system log that apache generate to
>>>>>>>>>> see what went wrong.
>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>
>>>>>>>>>> Seb
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>
>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>
>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>
>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that do
>>>>>>>>>>> not look right:
>>>>>>>>>>>
>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>
>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>
>>>>>>>>>>> And the message:
>>>>>>>>>>>
>>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>
>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>
>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>
>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>>>>>>>>> Something there still needs attention and we are investigating further.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks for you patience and all the help that allows us to move
>>>>>>>>>>>> forward.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>
>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>
>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>
>>>>>>>>>>>>> ${host} should have been replaced with a static string that
>>>>>>>>>>>>> match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in
>>>>>>>>>>>>> your set of arguments. That will force some output generation to fill some
>>>>>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>>>>>> ready.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've noticed that the documentation is missing them. Don't
>>>>>>>>>>>>> know why... Will update it at some point.
>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>
>>>>>>>>>>>>> And the value for "timeout" should be way bigger than 5. Like
>>>>>>>>>>>>> 25 maybe.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks for this detailed description! The process is starting
>>>>>>>>>>>>>> to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Here is our complete launch.json (with the right sessionURL
>>>>>>>>>>>>>> for a config with Apache, according to your email):
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the
>>>>>>>>>>>>>> browser,
>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR
>>>>>>>>>>>>>> PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32
>>>>>>>>>>>>>> 0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> First of all you need to understand the role of apache here
>>>>>>>>>>>>>>> in order to see how the configuration should be.
>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache, but
>>>>>>>>>>>>>>> such setup is not meant for production.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>> - Apache can be use to serve the static content (html, js,
>>>>>>>>>>>>>>> png, css...)
>>>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the
>>>>>>>>>>>>>>> proper ParaViewWeb instance on the backend based on a session ID. This mean
>>>>>>>>>>>>>>> that the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Then you need to understand how the launcher works and its
>>>>>>>>>>>>>>> role.
>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the
>>>>>>>>>>>>>>> same port as the main server (the process would not start). Hence, we start
>>>>>>>>>>>>>>> it with some port and we let the user know that it should connect to
>>>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a process
>>>>>>>>>>>>>>> which is meant to relay the communication to the backend using the port and
>>>>>>>>>>>>>>> host that Apache is using. So the launcher should let the client know what
>>>>>>>>>>>>>>> URL they should use so Apache could handle it and forward it to the
>>>>>>>>>>>>>>> backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>> In the same time to keep track on which host/port a process
>>>>>>>>>>>>>>> is running the launcher generate a text file with the proper mapping.
>>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure out
>>>>>>>>>>>>>>> how it should establish the connection to the backend.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Read the documentation, the list is minimum and provided in
>>>>>>>>>>>>>>> it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So the "host" is to select the proper network card when you
>>>>>>>>>>>>>>> have several for the actual launcher server.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the
>>>>>>>>>>>>>>>> script you've suggested earlier:
>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Then when a session start you can check the content of
>>>>>>>>>>>>>>>>> that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Verified that those entires are added to the file and have
>>>>>>>>>>>>>>>> the right format.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config of
>>>>>>>>>>>>>>>>> your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on which
>>>>>>>>>>>>>>>>> port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> A common error could also be that the apache does not have
>>>>>>>>>>>>>>>>> the right to read the /data/proxy.txt file or that the launcher is not able
>>>>>>>>>>>>>>>>> to write it.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries are
>>>>>>>>>>>>>>>> added.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort these
>>>>>>>>>>>>>>>> out because they have caused some confusion and we want to clear things up
>>>>>>>>>>>>>>>> and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So far we
>>>>>>>>>>>>>>>> have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping
>>>>>>>>>>>>>>>>>> to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon
>>>>>>>>>>>>>>>>>> EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and that
>>>>>>>>>>>>>>>>>> PVW launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache configuration,
>>>>>>>>>>>>>>>>>> where we have:
>>>>>>>>>>>>>>>>>> ProxyPass        /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to move
>>>>>>>>>>>>>>>>>> forward with our isntallation.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/77176518/attachment-0001.html>

From duplyakin at uchicago.edu  Tue Jul 22 12:16:54 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Tue, 22 Jul 2014 11:16:54 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
 <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
Message-ID: <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>

Definitely worth checking.

Here is what I did to install it:

I used the script from: http://www.paraview.org/files/web/pvw-setup

which unpacks ParaView-4.1.0-Linux-64bit-glibc-2.3.6.tar.gz

and sets up directories like www, conf, etc.

Then in order to build ParaView from source I did: git://
paraview.org/stage/ParaView.git

followed by "git submodule update --init", as recommended at
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup

for Apache <2.4, which I was running until yesterday.

See anything wrong?


On Tue, Jul 22, 2014 at 10:47 AM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Just a though...
>
> Which version of ParaView did you build? git master?
>
> If so, did you use the www directory from that build or did you use the
> one from the binaries?
> There could be a version miss match in that later case.
>
> Seb
>
>
> On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Hi Dmitry,
>>
>> I've just tried to connect to your server and it seems that the process
>> start in about 1s. That might be correct but it seems fast to me.
>> Do you see any error after the +++++ log file?
>>
>> Could you edit your launcher config to add an entry for the "pipeline"
>> app?
>> The cone is just relying on VTK and I was curious if we could see
>> something different with our main sample app that use paraview.
>>
>> For that you just need to kill the launcher process and restart it with
>> the new config.
>>
>> Seb
>>
>>
>> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <duplyakin at uchicago.edu
>> > wrote:
>>
>>> All I see is described js error. (I see it in the Firefox'es Firebug
>>> console)
>>>
>>>
>>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <karpeev at mcs.anl.gov>
>>> wrote:
>>>
>>>> Is there a Python error/stack trace that comes with this?
>>>> On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <duplyakin at uchicago.edu>
>>>> wrote:
>>>>
>>>>> Hi Sebastien,
>>>>>
>>>>> Thanks again for your help yesterday!
>>>>>
>>>>> We have upgraded and running Apache-2.4.7 now.
>>>>>
>>>>> We are seeing a now error:
>>>>>  Firefox can't establish a connection to the server at ws://
>>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>>> .
>>>>> return new WebSocket(url, protocols);
>>>>>
>>>>> Last line points to code in autobahn.js
>>>>> ab._construct = function (url, protocols) {
>>>>>    if ("WebSocket" in window) {
>>>>>       // Chrome, MSIE, newer Firefox
>>>>>       if (protocols) {
>>>>>          *return new WebSocket(url, protocols);*
>>>>>       } else {
>>>>>          return new WebSocket(url);
>>>>>       }
>>>>>    } else if ("MozWebSocket" in window) {
>>>>>       // older versions of Firefox prefix the WebSocket object
>>>>>       if (protocols) {
>>>>>          return new MozWebSocket(url, protocols);
>>>>>       } else {
>>>>>          return new MozWebSocket(url);
>>>>>       }
>>>>>    } else {
>>>>>       return null;
>>>>>    }
>>>>> };
>>>>>
>>>>> In the meantime, session gets created, session log has a standard
>>>>> opening followed by many lines with "+" signs (which means it is running
>>>>> fine, right?), POST is successful:
>>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/" "Mozilla/5.0
>>>>> (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0".
>>>>>
>>>>> Its response:
>>>>>
>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>>
>>>>> Are possibly missing anything here?
>>>>>
>>>>> Looks like Apache log verifies that wstunnel is working:
>>>>>
>>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>>
>>>>> Any thoughts on what might be causing this problem?
>>>>>
>>>>>
>>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> Should work... I guess this documentation will always be out of date.
>>>>>> ;-)
>>>>>>
>>>>>> But the good news is that modern system have the right version of
>>>>>> Apache, so no fancy build are needed anymore...
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>>  Trying to follow instructions from
>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>>> It looks like those urls used with wget are broken.
>>>>>>>
>>>>>>> Found a replacement for httpd:
>>>>>>>
>>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>>>>> httpd.tgz
>>>>>>>
>>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here is
>>>>>>> a working command:
>>>>>>>
>>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>>
>>>>>>> The last one works fine:
>>>>>>>
>>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>>> apr-util.tgz
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>
>>>>>>>>> You must have Apache 2.4.7+
>>>>>>>>> Their is a fix in that version which allow mod_rewrite to work
>>>>>>>>> on web socket protocol instead of just http.
>>>>>>>>> You can look at the apache section in here
>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module
>>>>>>>>>> (that we had to build from source).
>>>>>>>>>>
>>>>>>>>>> From Apache error log (with debug):
>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>>> HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>>>>>>> 130.202.2.217] proxy: http: found worker
>>>>>>>>>> http://localhost:8080/paraview for
>>>>>>>>>> http://localhost:8080/paraview/, referer:
>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>>>>> HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>> HTTP: has acquired connection for (localhost)
>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>> connected /paraview/ to localhost:8080
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>>>>> start body send
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>>>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>>>>> end body send
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>> HTTP: has released connection for (localhost)
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>>> HTTP: canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>>>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973): proxy:
>>>>>>>>>> HTTP: serving URL
>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>> HTTP: has acquired connection for (*)
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>> connecting
>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>> to 54.211.22.94:80
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>> connected
>>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>>> 54.211.22.94:80
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy:
>>>>>>>>>> HTTP: fam 2 socket created to connect to *
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy:
>>>>>>>>>> HTTP: connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File
>>>>>>>>>> does not exist: /pv/www/ws:
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743): proxy:
>>>>>>>>>> start body send
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847): proxy:
>>>>>>>>>> end body send
>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>> HTTP: has released connection for (*)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>>>>>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>>
>>>>>>>>>>> You may be able to check the system log that apache generate to
>>>>>>>>>>> see what went wrong.
>>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>>
>>>>>>>>>>> Seb
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>>
>>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>>
>>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>>
>>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that do
>>>>>>>>>>>> not look right:
>>>>>>>>>>>>
>>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>>
>>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>>
>>>>>>>>>>>> And the message:
>>>>>>>>>>>>
>>>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>>
>>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>>
>>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in action.
>>>>>>>>>>>>> Something there still needs attention and we are investigating further.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for you patience and all the help that allows us to
>>>>>>>>>>>>> move forward.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ${host} should have been replaced with a static string that
>>>>>>>>>>>>>> match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in
>>>>>>>>>>>>>> your set of arguments. That will force some output generation to fill some
>>>>>>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>>>>>>> ready.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I've noticed that the documentation is missing them. Don't
>>>>>>>>>>>>>> know why... Will update it at some point.
>>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> And the value for "timeout" should be way bigger than 5.
>>>>>>>>>>>>>> Like 25 maybe.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for this detailed description! The process is
>>>>>>>>>>>>>>> starting to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Here is our complete launch.json (with the right sessionURL
>>>>>>>>>>>>>>> for a config with Apache, according to your email):
>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the
>>>>>>>>>>>>>>> browser,
>>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR
>>>>>>>>>>>>>>> PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32
>>>>>>>>>>>>>>> 0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> First of all you need to understand the role of apache here
>>>>>>>>>>>>>>>> in order to see how the configuration should be.
>>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache,
>>>>>>>>>>>>>>>> but such setup is not meant for production.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>>> - Apache can be use to serve the static content (html, js,
>>>>>>>>>>>>>>>> png, css...)
>>>>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the
>>>>>>>>>>>>>>>> proper ParaViewWeb instance on the backend based on a session ID. This mean
>>>>>>>>>>>>>>>> that the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Then you need to understand how the launcher works and its
>>>>>>>>>>>>>>>> role.
>>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use the
>>>>>>>>>>>>>>>> same port as the main server (the process would not start). Hence, we start
>>>>>>>>>>>>>>>> it with some port and we let the user know that it should connect to
>>>>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a process
>>>>>>>>>>>>>>>> which is meant to relay the communication to the backend using the port and
>>>>>>>>>>>>>>>> host that Apache is using. So the launcher should let the client know what
>>>>>>>>>>>>>>>> URL they should use so Apache could handle it and forward it to the
>>>>>>>>>>>>>>>> backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>>> In the same time to keep track on which host/port a process
>>>>>>>>>>>>>>>> is running the launcher generate a text file with the proper mapping.
>>>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure out
>>>>>>>>>>>>>>>> how it should establish the connection to the backend.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Read the documentation, the list is minimum and provided in
>>>>>>>>>>>>>>>> it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So the "host" is to select the proper network card when you
>>>>>>>>>>>>>>>> have several for the actual launcher server.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the
>>>>>>>>>>>>>>>>> script you've suggested earlier:
>>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Then when a session start you can check the content of
>>>>>>>>>>>>>>>>>> that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Verified that those entires are added to the file and have
>>>>>>>>>>>>>>>>> the right format.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config of
>>>>>>>>>>>>>>>>>> your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on
>>>>>>>>>>>>>>>>>> which port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> A common error could also be that the apache does not
>>>>>>>>>>>>>>>>>> have the right to read the /data/proxy.txt file or that the launcher is not
>>>>>>>>>>>>>>>>>> able to write it.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries are
>>>>>>>>>>>>>>>>> added.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort these
>>>>>>>>>>>>>>>>> out because they have caused some confusion and we want to clear things up
>>>>>>>>>>>>>>>>> and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So far
>>>>>>>>>>>>>>>>> we have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping
>>>>>>>>>>>>>>>>>>> to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon
>>>>>>>>>>>>>>>>>>> EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and that
>>>>>>>>>>>>>>>>>>> PVW launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache configuration,
>>>>>>>>>>>>>>>>>>> where we have:
>>>>>>>>>>>>>>>>>>> ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview
>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to
>>>>>>>>>>>>>>>>>>> move forward with our isntallation.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/f3c5abc8/attachment-0001.html>

From duplyakin at uchicago.edu  Tue Jul 22 15:21:05 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Tue, 22 Jul 2014 14:21:05 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
 <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
 <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>
Message-ID: <CAJiCY3ZtyR1s0Xadx=EQ6-w3sxAt_AZq8BaQ63ThLg0m3u+-QQ@mail.gmail.com>

Any comments on our build process?

We are a bit concerned about compatibility between the stuff from that tar
file and the stuff that we build from the cloned paraview code. Anything we
should pay special attention to?

Also, yesterday we saw the error when we called pvpython:

/pv/paraview/lib/paraview-4.1/pvpython: error while loading shared
libraries: libvtkPVServerManagerApplication-pv4.1.so.1: cannot open shared
object file: No such file or directory

and fixed it by adding

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/pv/paraview/lib/paraview-4.1

to our environment's profile. Seems to be a solved problem now, but can it
possibly be caused by a compatibility issue?

Finally, the cone file,
/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py, in our case
remains in the src dir, the one where we clone paraview code from git. We
understand that it is used with pvpython that knows about specific
locations in our environment, but still it looks odd that the cone file
remains in src, directory that can be considered for removal after
installation is done. Are we missing something here?


On Tue, Jul 22, 2014 at 11:16 AM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Definitely worth checking.
>
> Here is what I did to install it:
>
> I used the script from: http://www.paraview.org/files/web/pvw-setup
>
> which unpacks ParaView-4.1.0-Linux-64bit-glibc-2.3.6.tar.gz
>
> and sets up directories like www, conf, etc.
>
> Then in order to build ParaView from source I did: git://
> paraview.org/stage/ParaView.git
>
> followed by "git submodule update --init", as recommended at
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup
>
> for Apache <2.4, which I was running until yesterday.
>
> See anything wrong?
>
>
>
> On Tue, Jul 22, 2014 at 10:47 AM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Just a though...
>>
>> Which version of ParaView did you build? git master?
>>
>> If so, did you use the www directory from that build or did you use the
>> one from the binaries?
>> There could be a version miss match in that later case.
>>
>> Seb
>>
>>
>> On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Hi Dmitry,
>>>
>>> I've just tried to connect to your server and it seems that the process
>>> start in about 1s. That might be correct but it seems fast to me.
>>> Do you see any error after the +++++ log file?
>>>
>>> Could you edit your launcher config to add an entry for the "pipeline"
>>> app?
>>> The cone is just relying on VTK and I was curious if we could see
>>> something different with our main sample app that use paraview.
>>>
>>> For that you just need to kill the launcher process and restart it with
>>> the new config.
>>>
>>> Seb
>>>
>>>
>>> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> All I see is described js error. (I see it in the Firefox'es Firebug
>>>> console)
>>>>
>>>>
>>>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <karpeev at mcs.anl.gov>
>>>> wrote:
>>>>
>>>>> Is there a Python error/stack trace that comes with this?
>>>>>  On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <duplyakin at uchicago.edu>
>>>>> wrote:
>>>>>
>>>>>> Hi Sebastien,
>>>>>>
>>>>>> Thanks again for your help yesterday!
>>>>>>
>>>>>> We have upgraded and running Apache-2.4.7 now.
>>>>>>
>>>>>> We are seeing a now error:
>>>>>>  Firefox can't establish a connection to the server at ws://
>>>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>>>> .
>>>>>> return new WebSocket(url, protocols);
>>>>>>
>>>>>> Last line points to code in autobahn.js
>>>>>> ab._construct = function (url, protocols) {
>>>>>>    if ("WebSocket" in window) {
>>>>>>       // Chrome, MSIE, newer Firefox
>>>>>>       if (protocols) {
>>>>>>          *return new WebSocket(url, protocols);*
>>>>>>       } else {
>>>>>>          return new WebSocket(url);
>>>>>>       }
>>>>>>    } else if ("MozWebSocket" in window) {
>>>>>>       // older versions of Firefox prefix the WebSocket object
>>>>>>       if (protocols) {
>>>>>>          return new MozWebSocket(url, protocols);
>>>>>>       } else {
>>>>>>          return new MozWebSocket(url);
>>>>>>       }
>>>>>>    } else {
>>>>>>       return null;
>>>>>>    }
>>>>>> };
>>>>>>
>>>>>> In the meantime, session gets created, session log has a standard
>>>>>> opening followed by many lines with "+" signs (which means it is running
>>>>>> fine, right?), POST is successful:
>>>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/" "Mozilla/5.0
>>>>>> (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0".
>>>>>>
>>>>>> Its response:
>>>>>>
>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>>>
>>>>>> Are possibly missing anything here?
>>>>>>
>>>>>> Looks like Apache log verifies that wstunnel is working:
>>>>>>
>>>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>>>
>>>>>> Any thoughts on what might be causing this problem?
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>
>>>>>>> Should work... I guess this documentation will always be out of
>>>>>>> date. ;-)
>>>>>>>
>>>>>>> But the good news is that modern system have the right version of
>>>>>>> Apache, so no fancy build are needed anymore...
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>>  Trying to follow instructions from
>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>>>> It looks like those urls used with wget are broken.
>>>>>>>>
>>>>>>>> Found a replacement for httpd:
>>>>>>>>
>>>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>>>>>> httpd.tgz
>>>>>>>>
>>>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here
>>>>>>>> is a working command:
>>>>>>>>
>>>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>>>
>>>>>>>> The last one works fine:
>>>>>>>>
>>>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>>>> apr-util.tgz
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>
>>>>>>>>>> You must have Apache 2.4.7+
>>>>>>>>>> Their is a fix in that version which allow mod_rewrite to work
>>>>>>>>>> on web socket protocol instead of just http.
>>>>>>>>>> You can look at the apache section in here
>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>>>
>>>>>>>>>> Seb
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module
>>>>>>>>>>> (that we had to build from source).
>>>>>>>>>>>
>>>>>>>>>>> From Apache error log (with debug):
>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>>>> HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>>>>>>>> 130.202.2.217] proxy: http: found worker
>>>>>>>>>>> http://localhost:8080/paraview for
>>>>>>>>>>> http://localhost:8080/paraview/, referer:
>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>> proxy: HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>> HTTP: has acquired connection for (localhost)
>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>> connected /paraview/ to localhost:8080
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>> proxy: start body send
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>>>>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>> proxy: end body send
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>> HTTP: has released connection for (localhost)
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>>>> HTTP: canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>>>>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>> proxy: HTTP: serving URL
>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>> HTTP: has acquired connection for (*)
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>> connecting
>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>> to 54.211.22.94:80
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>> connected
>>>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>>>> 54.211.22.94:80
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy:
>>>>>>>>>>> HTTP: fam 2 socket created to connect to *
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy:
>>>>>>>>>>> HTTP: connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File
>>>>>>>>>>> does not exist: /pv/www/ws:
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>> proxy: start body send
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>> proxy: end body send
>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>> HTTP: has released connection for (*)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>>>>>>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>>>
>>>>>>>>>>>> You may be able to check the system log that apache generate to
>>>>>>>>>>>> see what went wrong.
>>>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>>>
>>>>>>>>>>>> Seb
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>>>
>>>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>>>
>>>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that do
>>>>>>>>>>>>> not look right:
>>>>>>>>>>>>>
>>>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>>>
>>>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>>>
>>>>>>>>>>>>> And the message:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>>>
>>>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in
>>>>>>>>>>>>>> action. Something there still needs attention and we are investigating
>>>>>>>>>>>>>> further.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks for you patience and all the help that allows us to
>>>>>>>>>>>>>> move forward.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ${host} should have been replaced with a static string that
>>>>>>>>>>>>>>> match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in
>>>>>>>>>>>>>>> your set of arguments. That will force some output generation to fill some
>>>>>>>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>>>>>>>> ready.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I've noticed that the documentation is missing them. Don't
>>>>>>>>>>>>>>> know why... Will update it at some point.
>>>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And the value for "timeout" should be way bigger than 5.
>>>>>>>>>>>>>>> Like 25 maybe.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks for this detailed description! The process is
>>>>>>>>>>>>>>>> starting to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Here is our complete launch.json (with the right sessionURL
>>>>>>>>>>>>>>>> for a config with Apache, according to your email):
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$
>>>>>>>>>>>>>>>> [NC]
>>>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the
>>>>>>>>>>>>>>>> browser,
>>>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR
>>>>>>>>>>>>>>>> PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32
>>>>>>>>>>>>>>>> 0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> First of all you need to understand the role of apache
>>>>>>>>>>>>>>>>> here in order to see how the configuration should be.
>>>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache,
>>>>>>>>>>>>>>>>> but such setup is not meant for production.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>>>> - Apache can be use to serve the static content (html, js,
>>>>>>>>>>>>>>>>> png, css...)
>>>>>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the
>>>>>>>>>>>>>>>>> proper ParaViewWeb instance on the backend based on a session ID. This mean
>>>>>>>>>>>>>>>>> that the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Then you need to understand how the launcher works and its
>>>>>>>>>>>>>>>>> role.
>>>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use
>>>>>>>>>>>>>>>>> the same port as the main server (the process would not start). Hence, we
>>>>>>>>>>>>>>>>> start it with some port and we let the user know that it should connect to
>>>>>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a process
>>>>>>>>>>>>>>>>> which is meant to relay the communication to the backend using the port and
>>>>>>>>>>>>>>>>> host that Apache is using. So the launcher should let the client know what
>>>>>>>>>>>>>>>>> URL they should use so Apache could handle it and forward it to the
>>>>>>>>>>>>>>>>> backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>>>> In the same time to keep track on which host/port a
>>>>>>>>>>>>>>>>> process is running the launcher generate a text file with the proper
>>>>>>>>>>>>>>>>> mapping.
>>>>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure out
>>>>>>>>>>>>>>>>> how it should establish the connection to the backend.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as the
>>>>>>>>>>>>>>>>> documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Read the documentation, the list is minimum and provided
>>>>>>>>>>>>>>>>> in it.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> So the "host" is to select the proper network card when
>>>>>>>>>>>>>>>>> you have several for the actual launcher server.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the
>>>>>>>>>>>>>>>>>> script you've suggested earlier:
>>>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Then when a session start you can check the content of
>>>>>>>>>>>>>>>>>>> that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Verified that those entires are added to the file and
>>>>>>>>>>>>>>>>>> have the right format.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config of
>>>>>>>>>>>>>>>>>>> your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"}}
>>>>>>>>>>>>>>>>>> ,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on
>>>>>>>>>>>>>>>>>>> which port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> A common error could also be that the apache does not
>>>>>>>>>>>>>>>>>>> have the right to read the /data/proxy.txt file or that the launcher is not
>>>>>>>>>>>>>>>>>>> able to write it.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries are
>>>>>>>>>>>>>>>>>> added.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort
>>>>>>>>>>>>>>>>>> these out because they have caused some confusion and we want to clear
>>>>>>>>>>>>>>>>>> things up and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So far
>>>>>>>>>>>>>>>>>> we have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student helping
>>>>>>>>>>>>>>>>>>>> to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon
>>>>>>>>>>>>>>>>>>>> EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and that
>>>>>>>>>>>>>>>>>>>> PVW launcher is functioning (new entries are added to the proxy file, vis
>>>>>>>>>>>>>>>>>>>> sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache configuration,
>>>>>>>>>>>>>>>>>>>> where we have:
>>>>>>>>>>>>>>>>>>>> ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview
>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to
>>>>>>>>>>>>>>>>>>>> move forward with our isntallation.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/76672ad2/attachment-0001.html>

From sebastien.jourdain at kitware.com  Tue Jul 22 15:35:02 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 22 Jul 2014 13:35:02 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3ZtyR1s0Xadx=EQ6-w3sxAt_AZq8BaQ63ThLg0m3u+-QQ@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
 <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
 <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>
 <CAJiCY3ZtyR1s0Xadx=EQ6-w3sxAt_AZq8BaQ63ThLg0m3u+-QQ@mail.gmail.com>
Message-ID: <CABObKxfrPXkUuXPyYNV4=QQiXU=haYU8dNthk1g_ThzUuFL=Sw@mail.gmail.com>

Yes you should replace the content of the directory that you share with
apache with the content that come from your {build-tree}/www.

Just replace the three following dirs: apps, lib, ext

Seb


On Tue, Jul 22, 2014 at 1:21 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> Any comments on our build process?
>
> We are a bit concerned about compatibility between the stuff from that tar
> file and the stuff that we build from the cloned paraview code. Anything we
> should pay special attention to?
>
> Also, yesterday we saw the error when we called pvpython:
>
> /pv/paraview/lib/paraview-4.1/pvpython: error while loading shared
> libraries: libvtkPVServerManagerApplication-pv4.1.so.1: cannot open shared
> object file: No such file or directory
>
> and fixed it by adding
>
> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/pv/paraview/lib/paraview-4.1
>
> to our environment's profile. Seems to be a solved problem now, but can it
> possibly be caused by a compatibility issue?
>
> Finally, the cone file,
> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py, in our case
> remains in the src dir, the one where we clone paraview code from git. We
> understand that it is used with pvpython that knows about specific
> locations in our environment, but still it looks odd that the cone file
> remains in src, directory that can be considered for removal after
> installation is done. Are we missing something here?
>
>
> On Tue, Jul 22, 2014 at 11:16 AM, Dmitry Duplyakin <duplyakin at uchicago.edu
> > wrote:
>
>> Definitely worth checking.
>>
>> Here is what I did to install it:
>>
>> I used the script from: http://www.paraview.org/files/web/pvw-setup
>>
>> which unpacks ParaView-4.1.0-Linux-64bit-glibc-2.3.6.tar.gz
>>
>> and sets up directories like www, conf, etc.
>>
>> Then in order to build ParaView from source I did: git://
>> paraview.org/stage/ParaView.git
>>
>> followed by "git submodule update --init", as recommended at
>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup
>>
>> for Apache <2.4, which I was running until yesterday.
>>
>> See anything wrong?
>>
>>
>>
>> On Tue, Jul 22, 2014 at 10:47 AM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Just a though...
>>>
>>> Which version of ParaView did you build? git master?
>>>
>>> If so, did you use the www directory from that build or did you use the
>>> one from the binaries?
>>> There could be a version miss match in that later case.
>>>
>>> Seb
>>>
>>>
>>> On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Hi Dmitry,
>>>>
>>>> I've just tried to connect to your server and it seems that the process
>>>> start in about 1s. That might be correct but it seems fast to me.
>>>> Do you see any error after the +++++ log file?
>>>>
>>>> Could you edit your launcher config to add an entry for the "pipeline"
>>>> app?
>>>> The cone is just relying on VTK and I was curious if we could see
>>>> something different with our main sample app that use paraview.
>>>>
>>>> For that you just need to kill the launcher process and restart it with
>>>> the new config.
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> All I see is described js error. (I see it in the Firefox'es Firebug
>>>>> console)
>>>>>
>>>>>
>>>>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <karpeev at mcs.anl.gov>
>>>>> wrote:
>>>>>
>>>>>> Is there a Python error/stack trace that comes with this?
>>>>>>  On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <duplyakin at uchicago.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Sebastien,
>>>>>>>
>>>>>>> Thanks again for your help yesterday!
>>>>>>>
>>>>>>> We have upgraded and running Apache-2.4.7 now.
>>>>>>>
>>>>>>> We are seeing a now error:
>>>>>>>  Firefox can't establish a connection to the server at ws://
>>>>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>>>>> .
>>>>>>> return new WebSocket(url, protocols);
>>>>>>>
>>>>>>> Last line points to code in autobahn.js
>>>>>>> ab._construct = function (url, protocols) {
>>>>>>>    if ("WebSocket" in window) {
>>>>>>>       // Chrome, MSIE, newer Firefox
>>>>>>>       if (protocols) {
>>>>>>>          *return new WebSocket(url, protocols);*
>>>>>>>       } else {
>>>>>>>          return new WebSocket(url);
>>>>>>>       }
>>>>>>>    } else if ("MozWebSocket" in window) {
>>>>>>>       // older versions of Firefox prefix the WebSocket object
>>>>>>>       if (protocols) {
>>>>>>>          return new MozWebSocket(url, protocols);
>>>>>>>       } else {
>>>>>>>          return new MozWebSocket(url);
>>>>>>>       }
>>>>>>>    } else {
>>>>>>>       return null;
>>>>>>>    }
>>>>>>> };
>>>>>>>
>>>>>>> In the meantime, session gets created, session log has a standard
>>>>>>> opening followed by many lines with "+" signs (which means it is running
>>>>>>> fine, right?), POST is successful:
>>>>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/"
>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>> Firefox/30.0".
>>>>>>>
>>>>>>> Its response:
>>>>>>>
>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>>>>
>>>>>>> Are possibly missing anything here?
>>>>>>>
>>>>>>> Looks like Apache log verifies that wstunnel is working:
>>>>>>>
>>>>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>>>>
>>>>>>> Any thoughts on what might be causing this problem?
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>
>>>>>>>> Should work... I guess this documentation will always be out of
>>>>>>>> date. ;-)
>>>>>>>>
>>>>>>>> But the good news is that modern system have the right version of
>>>>>>>> Apache, so no fancy build are needed anymore...
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>>  Trying to follow instructions from
>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>>>>> It looks like those urls used with wget are broken.
>>>>>>>>>
>>>>>>>>> Found a replacement for httpd:
>>>>>>>>>
>>>>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>>>>>>> httpd.tgz
>>>>>>>>>
>>>>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here
>>>>>>>>> is a working command:
>>>>>>>>>
>>>>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>>>>
>>>>>>>>> The last one works fine:
>>>>>>>>>
>>>>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>>>>> apr-util.tgz
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> You must have Apache 2.4.7+
>>>>>>>>>>> Their is a fix in that version which allow mod_rewrite to work
>>>>>>>>>>> on web socket protocol instead of just http.
>>>>>>>>>>> You can look at the apache section in here
>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>>>>
>>>>>>>>>>> Seb
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module
>>>>>>>>>>>> (that we had to build from source).
>>>>>>>>>>>>
>>>>>>>>>>>> From Apache error log (with debug):
>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>>>>> HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>>>>>>>>> 130.202.2.217] proxy: http: found worker
>>>>>>>>>>>> http://localhost:8080/paraview for
>>>>>>>>>>>> http://localhost:8080/paraview/, referer:
>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>> proxy: HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>>> HTTP: has acquired connection for (localhost)
>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>>> connected /paraview/ to localhost:8080
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>>>>>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>>> HTTP: has released connection for (localhost)
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56): proxy:
>>>>>>>>>>>> HTTP: canonicalising URL //54.211.22.94/ws://localhost:9998/ws
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>>>>>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>> proxy: HTTP: serving URL
>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>>> HTTP: has acquired connection for (*)
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>>> connecting
>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>> to 54.211.22.94:80
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>>> connected
>>>>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>>>>> 54.211.22.94:80
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy:
>>>>>>>>>>>> HTTP: fam 2 socket created to connect to *
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy:
>>>>>>>>>>>> HTTP: connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File
>>>>>>>>>>>> does not exist: /pv/www/ws:
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>>> HTTP: has released connection for (*)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> POST took ~1 second. Timestamps for POST and the following GET:
>>>>>>>>>>>> 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>>>>
>>>>>>>>>>>>> You may be able to check the system log that apache generate
>>>>>>>>>>>>> to see what went wrong.
>>>>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>>>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that
>>>>>>>>>>>>>> do not look right:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> And the message:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in
>>>>>>>>>>>>>>> action. Something there still needs attention and we are investigating
>>>>>>>>>>>>>>> further.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for you patience and all the help that allows us to
>>>>>>>>>>>>>>> move forward.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ${host} should have been replaced with a static string that
>>>>>>>>>>>>>>>> match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in
>>>>>>>>>>>>>>>> your set of arguments. That will force some output generation to fill some
>>>>>>>>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>>>>>>>>> ready.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I've noticed that the documentation is missing them. Don't
>>>>>>>>>>>>>>>> know why... Will update it at some point.
>>>>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> And the value for "timeout" should be way bigger than 5.
>>>>>>>>>>>>>>>> Like 25 maybe.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks for this detailed description! The process is
>>>>>>>>>>>>>>>>> starting to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Here is our complete launch.json (with the right
>>>>>>>>>>>>>>>>> sessionURL for a config with Apache, according to your email):
>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$
>>>>>>>>>>>>>>>>> [NC]
>>>>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the
>>>>>>>>>>>>>>>>> browser,
>>>>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP FOR
>>>>>>>>>>>>>>>>> PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32
>>>>>>>>>>>>>>>>>   0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> First of all you need to understand the role of apache
>>>>>>>>>>>>>>>>>> here in order to see how the configuration should be.
>>>>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache,
>>>>>>>>>>>>>>>>>> but such setup is not meant for production.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>>>>> - Apache can be use to serve the static content (html,
>>>>>>>>>>>>>>>>>> js, png, css...)
>>>>>>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the
>>>>>>>>>>>>>>>>>> proper ParaViewWeb instance on the backend based on a session ID. This mean
>>>>>>>>>>>>>>>>>> that the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Then you need to understand how the launcher works and
>>>>>>>>>>>>>>>>>> its role.
>>>>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use
>>>>>>>>>>>>>>>>>> the same port as the main server (the process would not start). Hence, we
>>>>>>>>>>>>>>>>>> start it with some port and we let the user know that it should connect to
>>>>>>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a process
>>>>>>>>>>>>>>>>>> which is meant to relay the communication to the backend using the port and
>>>>>>>>>>>>>>>>>> host that Apache is using. So the launcher should let the client know what
>>>>>>>>>>>>>>>>>> URL they should use so Apache could handle it and forward it to the
>>>>>>>>>>>>>>>>>> backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>>>>> In the same time to keep track on which host/port a
>>>>>>>>>>>>>>>>>> process is running the launcher generate a text file with the proper
>>>>>>>>>>>>>>>>>> mapping.
>>>>>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure
>>>>>>>>>>>>>>>>>> out how it should establish the connection to the backend.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as
>>>>>>>>>>>>>>>>>> the documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Read the documentation, the list is minimum and provided
>>>>>>>>>>>>>>>>>> in it.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> So the "host" is to select the proper network card when
>>>>>>>>>>>>>>>>>> you have several for the actual launcher server.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Then the resources are use for process management and URL
>>>>>>>>>>>>>>>>>> generation for the client. Which mean, what name should be used by Apache
>>>>>>>>>>>>>>>>>> to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the
>>>>>>>>>>>>>>>>>>> script you've suggested earlier:
>>>>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws
>>>>>>>>>>>>>>>>>>>  [P]
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Then when a session start you can check the content of
>>>>>>>>>>>>>>>>>>>> that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Verified that those entires are added to the file and
>>>>>>>>>>>>>>>>>>> have the right format.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config of
>>>>>>>>>>>>>>>>>>>> your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>> }},
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on
>>>>>>>>>>>>>>>>>>>> which port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> A common error could also be that the apache does not
>>>>>>>>>>>>>>>>>>>> have the right to read the /data/proxy.txt file or that the launcher is not
>>>>>>>>>>>>>>>>>>>> able to write it.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries are
>>>>>>>>>>>>>>>>>>> added.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort
>>>>>>>>>>>>>>>>>>> these out because they have caused some confusion and we want to clear
>>>>>>>>>>>>>>>>>>> things up and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So far
>>>>>>>>>>>>>>>>>>> we have: proxy_module, proxy_http_module, and rewrite_module. We are unsure
>>>>>>>>>>>>>>>>>>> whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>> where we have some confusion about using "localhost" vs.
>>>>>>>>>>>>>>>>>>> "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student
>>>>>>>>>>>>>>>>>>>>> helping to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on Amazon
>>>>>>>>>>>>>>>>>>>>> EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and
>>>>>>>>>>>>>>>>>>>>> that PVW launcher is functioning (new entries are added to the proxy file,
>>>>>>>>>>>>>>>>>>>>> vis sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache
>>>>>>>>>>>>>>>>>>>>> configuration, where we have:
>>>>>>>>>>>>>>>>>>>>> ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview
>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to
>>>>>>>>>>>>>>>>>>>>> move forward with our isntallation.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/4eaf7a67/attachment-0001.html>

From sebastien.jourdain at kitware.com  Tue Jul 22 15:36:10 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 22 Jul 2014 13:36:10 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxfrPXkUuXPyYNV4=QQiXU=haYU8dNthk1g_ThzUuFL=Sw@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
 <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
 <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>
 <CAJiCY3ZtyR1s0Xadx=EQ6-w3sxAt_AZq8BaQ63ThLg0m3u+-QQ@mail.gmail.com>
 <CABObKxfrPXkUuXPyYNV4=QQiXU=haYU8dNthk1g_ThzUuFL=Sw@mail.gmail.com>
Message-ID: <CABObKxd8EWZbm_haO4Bxf0pS4KPtb4ebmtLoeY3AzQ22NToopA@mail.gmail.com>

The script is great when you don't want to build ParaView, but since you
did, you should make sure the server and the client code (html+js) are in
synch. Which is basically the content of that lib/ext/apps directories.


On Tue, Jul 22, 2014 at 1:35 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Yes you should replace the content of the directory that you share with
> apache with the content that come from your {build-tree}/www.
>
> Just replace the three following dirs: apps, lib, ext
>
> Seb
>
>
> On Tue, Jul 22, 2014 at 1:21 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> Any comments on our build process?
>>
>> We are a bit concerned about compatibility between the stuff from that
>> tar file and the stuff that we build from the cloned paraview code.
>> Anything we should pay special attention to?
>>
>> Also, yesterday we saw the error when we called pvpython:
>>
>> /pv/paraview/lib/paraview-4.1/pvpython: error while loading shared
>> libraries: libvtkPVServerManagerApplication-pv4.1.so.1: cannot open shared
>> object file: No such file or directory
>>
>> and fixed it by adding
>>
>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/pv/paraview/lib/paraview-4.1
>>
>> to our environment's profile. Seems to be a solved problem now, but can
>> it possibly be caused by a compatibility issue?
>>
>> Finally, the cone file,
>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py, in our case
>> remains in the src dir, the one where we clone paraview code from git. We
>> understand that it is used with pvpython that knows about specific
>> locations in our environment, but still it looks odd that the cone file
>> remains in src, directory that can be considered for removal after
>> installation is done. Are we missing something here?
>>
>>
>> On Tue, Jul 22, 2014 at 11:16 AM, Dmitry Duplyakin <
>> duplyakin at uchicago.edu> wrote:
>>
>>> Definitely worth checking.
>>>
>>> Here is what I did to install it:
>>>
>>> I used the script from: http://www.paraview.org/files/web/pvw-setup
>>>
>>> which unpacks ParaView-4.1.0-Linux-64bit-glibc-2.3.6.tar.gz
>>>
>>> and sets up directories like www, conf, etc.
>>>
>>> Then in order to build ParaView from source I did: git://
>>> paraview.org/stage/ParaView.git
>>>
>>> followed by "git submodule update --init", as recommended at
>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup
>>>
>>> for Apache <2.4, which I was running until yesterday.
>>>
>>> See anything wrong?
>>>
>>>
>>>
>>> On Tue, Jul 22, 2014 at 10:47 AM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Just a though...
>>>>
>>>> Which version of ParaView did you build? git master?
>>>>
>>>> If so, did you use the www directory from that build or did you use the
>>>> one from the binaries?
>>>> There could be a version miss match in that later case.
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com> wrote:
>>>>
>>>>> Hi Dmitry,
>>>>>
>>>>> I've just tried to connect to your server and it seems that the
>>>>> process start in about 1s. That might be correct but it seems fast to me.
>>>>> Do you see any error after the +++++ log file?
>>>>>
>>>>> Could you edit your launcher config to add an entry for the "pipeline"
>>>>> app?
>>>>> The cone is just relying on VTK and I was curious if we could see
>>>>> something different with our main sample app that use paraview.
>>>>>
>>>>> For that you just need to kill the launcher process and restart it
>>>>> with the new config.
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> All I see is described js error. (I see it in the Firefox'es Firebug
>>>>>> console)
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <karpeev at mcs.anl.gov
>>>>>> > wrote:
>>>>>>
>>>>>>> Is there a Python error/stack trace that comes with this?
>>>>>>>  On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <duplyakin at uchicago.edu>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Sebastien,
>>>>>>>>
>>>>>>>> Thanks again for your help yesterday!
>>>>>>>>
>>>>>>>> We have upgraded and running Apache-2.4.7 now.
>>>>>>>>
>>>>>>>> We are seeing a now error:
>>>>>>>>  Firefox can't establish a connection to the server at ws://
>>>>>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>>>>>> .
>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>
>>>>>>>> Last line points to code in autobahn.js
>>>>>>>> ab._construct = function (url, protocols) {
>>>>>>>>    if ("WebSocket" in window) {
>>>>>>>>       // Chrome, MSIE, newer Firefox
>>>>>>>>       if (protocols) {
>>>>>>>>          *return new WebSocket(url, protocols);*
>>>>>>>>       } else {
>>>>>>>>          return new WebSocket(url);
>>>>>>>>       }
>>>>>>>>    } else if ("MozWebSocket" in window) {
>>>>>>>>       // older versions of Firefox prefix the WebSocket object
>>>>>>>>       if (protocols) {
>>>>>>>>          return new MozWebSocket(url, protocols);
>>>>>>>>       } else {
>>>>>>>>          return new MozWebSocket(url);
>>>>>>>>       }
>>>>>>>>    } else {
>>>>>>>>       return null;
>>>>>>>>    }
>>>>>>>> };
>>>>>>>>
>>>>>>>> In the meantime, session gets created, session log has a standard
>>>>>>>> opening followed by many lines with "+" signs (which means it is running
>>>>>>>> fine, right?), POST is successful:
>>>>>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>>>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/"
>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>> Firefox/30.0".
>>>>>>>>
>>>>>>>> Its response:
>>>>>>>>
>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>>>>>
>>>>>>>> Are possibly missing anything here?
>>>>>>>>
>>>>>>>> Looks like Apache log verifies that wstunnel is working:
>>>>>>>>
>>>>>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>>>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>>>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>>>>>
>>>>>>>> Any thoughts on what might be causing this problem?
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>
>>>>>>>>> Should work... I guess this documentation will always be out of
>>>>>>>>> date. ;-)
>>>>>>>>>
>>>>>>>>> But the good news is that modern system have the right version of
>>>>>>>>> Apache, so no fancy build are needed anymore...
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>>  Trying to follow instructions from
>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>>>>>> It looks like those urls used with wget are broken.
>>>>>>>>>>
>>>>>>>>>> Found a replacement for httpd:
>>>>>>>>>>
>>>>>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>>>>>>>> httpd.tgz
>>>>>>>>>>
>>>>>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so, here
>>>>>>>>>> is a working command:
>>>>>>>>>>
>>>>>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>>>>>
>>>>>>>>>> The last one works fine:
>>>>>>>>>>
>>>>>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>>>>>> apr-util.tgz
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> You must have Apache 2.4.7+
>>>>>>>>>>>> Their is a fix in that version which allow mod_rewrite to work
>>>>>>>>>>>> on web socket protocol instead of just http.
>>>>>>>>>>>> You can look at the apache section in here
>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>>>>>
>>>>>>>>>>>> Seb
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> We are running Apache/2.2.22 with loaded proxy_wstunnel_module
>>>>>>>>>>>>> (that we had to build from source).
>>>>>>>>>>>>>
>>>>>>>>>>>>> From Apache error log (with debug):
>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506): [client
>>>>>>>>>>>>> 130.202.2.217] proxy: http: found worker
>>>>>>>>>>>>> http://localhost:8080/paraview for
>>>>>>>>>>>>> http://localhost:8080/paraview/, referer:
>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>> proxy: HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>>>> HTTP: has acquired connection for (localhost)
>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>>>> connected /paraview/ to localhost:8080
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615): [client
>>>>>>>>>>>>> 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/, referer:
>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>>>> HTTP: has released connection for (localhost)
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //
>>>>>>>>>>>>> 54.211.22.94/ws://localhost:9998/ws
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525): [client
>>>>>>>>>>>>> 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>> proxy: HTTP: serving URL
>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>>>> HTTP: has acquired connection for (*)
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>>>> connecting
>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>> to 54.211.22.94:80
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>>>> connected
>>>>>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>>>>>> 54.211.22.94:80
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy:
>>>>>>>>>>>>> HTTP: fam 2 socket created to connect to *
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy:
>>>>>>>>>>>>> HTTP: connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File
>>>>>>>>>>>>> does not exist: /pv/www/ws:
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>>>> HTTP: has released connection for (*)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> POST took ~1 second. Timestamps for POST and the following
>>>>>>>>>>>>> GET: 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> You may be able to check the system log that apache generate
>>>>>>>>>>>>>> to see what went wrong.
>>>>>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/",
>>>>>>>>>>>>>>> "port": 9999, "host": "localhost", "sessionURL": "ws://
>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that
>>>>>>>>>>>>>>> do not look right:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And the message:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in
>>>>>>>>>>>>>>>> action. Something there still needs attention and we are investigating
>>>>>>>>>>>>>>>> further.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks for you patience and all the help that allows us to
>>>>>>>>>>>>>>>> move forward.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ${host} should have been replaced with a static string
>>>>>>>>>>>>>>>>> that match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f" in
>>>>>>>>>>>>>>>>> your set of arguments. That will force some output generation to fill some
>>>>>>>>>>>>>>>>> buffer which will allow the launcher to detect when the server is actually
>>>>>>>>>>>>>>>>> ready.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I've noticed that the documentation is missing them. Don't
>>>>>>>>>>>>>>>>> know why... Will update it at some point.
>>>>>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> And the value for "timeout" should be way bigger than 5.
>>>>>>>>>>>>>>>>> Like 25 maybe.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks for this detailed description! The process is
>>>>>>>>>>>>>>>>>> starting to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Here is our complete launch.json (with the right
>>>>>>>>>>>>>>>>>> sessionURL for a config with Apache, according to your email):
>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>>>>>         RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$
>>>>>>>>>>>>>>>>>> [NC]
>>>>>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in the
>>>>>>>>>>>>>>>>>> browser,
>>>>>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP
>>>>>>>>>>>>>>>>>> FOR PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+  16:32
>>>>>>>>>>>>>>>>>>   0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> First of all you need to understand the role of apache
>>>>>>>>>>>>>>>>>>> here in order to see how the configuration should be.
>>>>>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without Apache,
>>>>>>>>>>>>>>>>>>> but such setup is not meant for production.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>>>>>> - Apache can be use to serve the static content (html,
>>>>>>>>>>>>>>>>>>> js, png, css...)
>>>>>>>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the
>>>>>>>>>>>>>>>>>>> proper ParaViewWeb instance on the backend based on a session ID. This mean
>>>>>>>>>>>>>>>>>>> that the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Then you need to understand how the launcher works and
>>>>>>>>>>>>>>>>>>> its role.
>>>>>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use
>>>>>>>>>>>>>>>>>>> the same port as the main server (the process would not start). Hence, we
>>>>>>>>>>>>>>>>>>> start it with some port and we let the user know that it should connect to
>>>>>>>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a process
>>>>>>>>>>>>>>>>>>> which is meant to relay the communication to the backend using the port and
>>>>>>>>>>>>>>>>>>> host that Apache is using. So the launcher should let the client know what
>>>>>>>>>>>>>>>>>>> URL they should use so Apache could handle it and forward it to the
>>>>>>>>>>>>>>>>>>> backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>>>>>> In the same time to keep track on which host/port a
>>>>>>>>>>>>>>>>>>> process is running the launcher generate a text file with the proper
>>>>>>>>>>>>>>>>>>> mapping.
>>>>>>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure
>>>>>>>>>>>>>>>>>>> out how it should establish the connection to the backend.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule actions?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as
>>>>>>>>>>>>>>>>>>> the documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Read the documentation, the list is minimum and provided
>>>>>>>>>>>>>>>>>>> in it.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> So the "host" is to select the proper network card when
>>>>>>>>>>>>>>>>>>> you have several for the actual launcher server.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Then the resources are use for process management and
>>>>>>>>>>>>>>>>>>> URL generation for the client. Which mean, what name should be used by
>>>>>>>>>>>>>>>>>>> Apache to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the
>>>>>>>>>>>>>>>>>>>> script you've suggested earlier:
>>>>>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Then when a session start you can check the content of
>>>>>>>>>>>>>>>>>>>>> that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Verified that those entires are added to the file and
>>>>>>>>>>>>>>>>>>>> have the right format.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config
>>>>>>>>>>>>>>>>>>>>> of your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>>> }},
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on
>>>>>>>>>>>>>>>>>>>>> which port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> A common error could also be that the apache does not
>>>>>>>>>>>>>>>>>>>>> have the right to read the /data/proxy.txt file or that the launcher is not
>>>>>>>>>>>>>>>>>>>>> able to write it.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries
>>>>>>>>>>>>>>>>>>>> are added.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort
>>>>>>>>>>>>>>>>>>>> these out because they have caused some confusion and we want to clear
>>>>>>>>>>>>>>>>>>>> things up and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule
>>>>>>>>>>>>>>>>>>>> actions?
>>>>>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So
>>>>>>>>>>>>>>>>>>>> far we have: proxy_module, proxy_http_module, and rewrite_module. We are
>>>>>>>>>>>>>>>>>>>> unsure whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>>> where we have some confusion about using "localhost"
>>>>>>>>>>>>>>>>>>>> vs. "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student
>>>>>>>>>>>>>>>>>>>>>> helping to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on
>>>>>>>>>>>>>>>>>>>>>> Amazon EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and
>>>>>>>>>>>>>>>>>>>>>> that PVW launcher is functioning (new entries are added to the proxy file,
>>>>>>>>>>>>>>>>>>>>>> vis sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache
>>>>>>>>>>>>>>>>>>>>>> configuration, where we have:
>>>>>>>>>>>>>>>>>>>>>> ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview
>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to
>>>>>>>>>>>>>>>>>>>>>> move forward with our isntallation.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/4b50e6c0/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Tue Jul 22 15:43:00 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 15:43:00 -0400
Subject: [Paraview] get the sum of a cell or point variable
	(UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101C482@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101C482@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjAMjX=LFwM6c68e0eLPY89SErtmk2g43YSE28m52JmqWA@mail.gmail.com>

Simon,

As I am cleaning my inbox, I ran into this email. Since there have been
other emails about this I'll skip your original query :). Just wanted to
give you an update on recent developments in ParaView. We recently pushed
updates to VTK/ParaView to allow you to use Python calculator to compute
"sum" in parallel across all blocks in the dataset. e.g. for can.ex2, you
can apply the Python Calculator and select "Cell Data", with expression
"sum(EQPS)" the result array will have the true global sum. This also
includes operations like min/max/mean etc.

Utkarsh


On Wed, Jun 25, 2014 at 11:21 AM, Su, Simon M CTR USARMY ARL (US) <
simon.m.su.ctr at mail.mil> wrote:

> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hello,
>
> Running in PV client/server mode, is there a calculator function that will
> add up all the values of a variable (cell or point variable).
>
> I can use the programmable filter to write a python loop to iterate through
> all the cell/point of the variable and add them up. But, running in a
> client/server mode, how would you store that value? Can I just add a single
> value (not array) to the data? If so, what vtk data structure shall I use
> to
> store a double variable? vtk.vtkDouble()? Or is there a way to write that
> value out to a file. Running it in parallel, how would that be handled?
>
> Thanks
> -simon
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/b2ceb1b3/attachment.html>

From simon.m.su.ctr at mail.mil  Tue Jul 22 15:49:32 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Tue, 22 Jul 2014 19:49:32 +0000
Subject: [Paraview] get the sum of a cell or point variable
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjAMjX=LFwM6c68e0eLPY89SErtmk2g43YSE28m52JmqWA@mail.gmail.com>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101C482@umechp9h.easf.csd.disa.mil>
 <CADHSJjAMjX=LFwM6c68e0eLPY89SErtmk2g43YSE28m52JmqWA@mail.gmail.com>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE7030@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hi Utkarsh,

That's great. That will eliminate the programmable filter part of my pipeline. 
You didn't happen to also pushed update to VTK/ParaView that will write the 
expression "sum(EQPS)" to a file that will work in parallel, did you? :)

Thanks
-simon

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Tuesday, July 22, 2014 3:43 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] get the sum of a cell or point variable (UNCLASSIFIED)

Simon,

As I am cleaning my inbox, I ran into this email. Since there have been other 
emails about this I'll skip your original query :). Just wanted to give you an 
update on recent developments in ParaView. We recently pushed updates to 
VTK/ParaView to allow you to use Python calculator to compute "sum" in 
parallel across all blocks in the dataset. e.g. for can.ex2, you can apply the 
Python Calculator and select "Cell Data", with expression "sum(EQPS)" the 
result array will have the true global sum. This also includes operations like 
min/max/mean etc.

Utkarsh


On Wed, Jun 25, 2014 at 11:21 AM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:


	Classification: UNCLASSIFIED
	Caveats: NONE

	Hello,

	Running in PV client/server mode, is there a calculator function that will
	add up all the values of a variable (cell or point variable).

	I can use the programmable filter to write a python loop to iterate through
	all the cell/point of the variable and add them up. But, running in a
	client/server mode, how would you store that value? Can I just add a single
	value (not array) to the data? If so, what vtk data structure shall I use to
	store a double variable? vtk.vtkDouble()? Or is there a way to write that
	value out to a file. Running it in parallel, how would that be handled?

	Thanks
	-simon

	Classification: UNCLASSIFIED
	Caveats: NONE



	_______________________________________________
	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://public.kitware.com/mailman/listinfo/paraview





Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/be10679b/attachment.bin>

From duplyakin at uchicago.edu  Tue Jul 22 16:07:36 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Tue, 22 Jul 2014 15:07:36 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxd8EWZbm_haO4Bxf0pS4KPtb4ebmtLoeY3AzQ22NToopA@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
 <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
 <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>
 <CAJiCY3ZtyR1s0Xadx=EQ6-w3sxAt_AZq8BaQ63ThLg0m3u+-QQ@mail.gmail.com>
 <CABObKxfrPXkUuXPyYNV4=QQiXU=haYU8dNthk1g_ThzUuFL=Sw@mail.gmail.com>
 <CABObKxd8EWZbm_haO4Bxf0pS4KPtb4ebmtLoeY3AzQ22NToopA@mail.gmail.com>
Message-ID: <CAJiCY3Zcc4GJUy+s4cVzUDebVaa1V+wFa1-98gw9KaJ4sNC=Lg@mail.gmail.com>

This makes sense and it most definitely helped!

We can now see this when we access: http://54.211.22.94/apps/Cone/


[image: Inline image 1]

but we are getting:
*uncaught exception: cannot resolve CURIE prefix 'vtk'*

What might be causing this?


On Tue, Jul 22, 2014 at 2:36 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> The script is great when you don't want to build ParaView, but since you
> did, you should make sure the server and the client code (html+js) are in
> synch. Which is basically the content of that lib/ext/apps directories.
>
>
> On Tue, Jul 22, 2014 at 1:35 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Yes you should replace the content of the directory that you share with
>> apache with the content that come from your {build-tree}/www.
>>
>> Just replace the three following dirs: apps, lib, ext
>>
>> Seb
>>
>>
>> On Tue, Jul 22, 2014 at 1:21 PM, Dmitry Duplyakin <duplyakin at uchicago.edu
>> > wrote:
>>
>>> Any comments on our build process?
>>>
>>> We are a bit concerned about compatibility between the stuff from that
>>> tar file and the stuff that we build from the cloned paraview code.
>>> Anything we should pay special attention to?
>>>
>>> Also, yesterday we saw the error when we called pvpython:
>>>
>>> /pv/paraview/lib/paraview-4.1/pvpython: error while loading shared
>>> libraries: libvtkPVServerManagerApplication-pv4.1.so.1: cannot open shared
>>> object file: No such file or directory
>>>
>>> and fixed it by adding
>>>
>>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/pv/paraview/lib/paraview-4.1
>>>
>>> to our environment's profile. Seems to be a solved problem now, but can
>>> it possibly be caused by a compatibility issue?
>>>
>>> Finally, the cone file,
>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py, in our case
>>> remains in the src dir, the one where we clone paraview code from git. We
>>> understand that it is used with pvpython that knows about specific
>>> locations in our environment, but still it looks odd that the cone file
>>> remains in src, directory that can be considered for removal after
>>> installation is done. Are we missing something here?
>>>
>>>
>>> On Tue, Jul 22, 2014 at 11:16 AM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> Definitely worth checking.
>>>>
>>>> Here is what I did to install it:
>>>>
>>>> I used the script from: http://www.paraview.org/files/web/pvw-setup
>>>>
>>>> which unpacks ParaView-4.1.0-Linux-64bit-glibc-2.3.6.tar.gz
>>>>
>>>> and sets up directories like www, conf, etc.
>>>>
>>>> Then in order to build ParaView from source I did: git://
>>>> paraview.org/stage/ParaView.git
>>>>
>>>> followed by "git submodule update --init", as recommended at
>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup
>>>>
>>>> for Apache <2.4, which I was running until yesterday.
>>>>
>>>> See anything wrong?
>>>>
>>>>
>>>>
>>>> On Tue, Jul 22, 2014 at 10:47 AM, Sebastien Jourdain <
>>>> sebastien.jourdain at kitware.com> wrote:
>>>>
>>>>> Just a though...
>>>>>
>>>>> Which version of ParaView did you build? git master?
>>>>>
>>>>> If so, did you use the www directory from that build or did you use
>>>>> the one from the binaries?
>>>>> There could be a version miss match in that later case.
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>> On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> Hi Dmitry,
>>>>>>
>>>>>> I've just tried to connect to your server and it seems that the
>>>>>> process start in about 1s. That might be correct but it seems fast to me.
>>>>>> Do you see any error after the +++++ log file?
>>>>>>
>>>>>> Could you edit your launcher config to add an entry for the
>>>>>> "pipeline" app?
>>>>>> The cone is just relying on VTK and I was curious if we could see
>>>>>> something different with our main sample app that use paraview.
>>>>>>
>>>>>> For that you just need to kill the launcher process and restart it
>>>>>> with the new config.
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <
>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>
>>>>>>> All I see is described js error. (I see it in the Firefox'es Firebug
>>>>>>> console)
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <
>>>>>>> karpeev at mcs.anl.gov> wrote:
>>>>>>>
>>>>>>>> Is there a Python error/stack trace that comes with this?
>>>>>>>>  On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> Hi Sebastien,
>>>>>>>>>
>>>>>>>>> Thanks again for your help yesterday!
>>>>>>>>>
>>>>>>>>> We have upgraded and running Apache-2.4.7 now.
>>>>>>>>>
>>>>>>>>> We are seeing a now error:
>>>>>>>>>  Firefox can't establish a connection to the server at ws://
>>>>>>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>>>>>>> .
>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>
>>>>>>>>> Last line points to code in autobahn.js
>>>>>>>>> ab._construct = function (url, protocols) {
>>>>>>>>>    if ("WebSocket" in window) {
>>>>>>>>>       // Chrome, MSIE, newer Firefox
>>>>>>>>>       if (protocols) {
>>>>>>>>>          *return new WebSocket(url, protocols);*
>>>>>>>>>       } else {
>>>>>>>>>          return new WebSocket(url);
>>>>>>>>>       }
>>>>>>>>>    } else if ("MozWebSocket" in window) {
>>>>>>>>>       // older versions of Firefox prefix the WebSocket object
>>>>>>>>>       if (protocols) {
>>>>>>>>>          return new MozWebSocket(url, protocols);
>>>>>>>>>       } else {
>>>>>>>>>          return new MozWebSocket(url);
>>>>>>>>>       }
>>>>>>>>>    } else {
>>>>>>>>>       return null;
>>>>>>>>>    }
>>>>>>>>> };
>>>>>>>>>
>>>>>>>>> In the meantime, session gets created, session log has a standard
>>>>>>>>> opening followed by many lines with "+" signs (which means it is running
>>>>>>>>> fine, right?), POST is successful:
>>>>>>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>>>>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/"
>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>> Firefox/30.0".
>>>>>>>>>
>>>>>>>>> Its response:
>>>>>>>>>
>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>>>>>>
>>>>>>>>> Are possibly missing anything here?
>>>>>>>>>
>>>>>>>>> Looks like Apache log verifies that wstunnel is working:
>>>>>>>>>
>>>>>>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>>>>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>>>>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>>>>>>
>>>>>>>>> Any thoughts on what might be causing this problem?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>
>>>>>>>>>> Should work... I guess this documentation will always be out of
>>>>>>>>>> date. ;-)
>>>>>>>>>>
>>>>>>>>>> But the good news is that modern system have the right version of
>>>>>>>>>> Apache, so no fancy build are needed anymore...
>>>>>>>>>>
>>>>>>>>>> Seb
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>>  Trying to follow instructions from
>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>>>>>>> It looks like those urls used with wget are broken.
>>>>>>>>>>>
>>>>>>>>>>> Found a replacement for httpd:
>>>>>>>>>>>
>>>>>>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz -O
>>>>>>>>>>> httpd.tgz
>>>>>>>>>>>
>>>>>>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so,
>>>>>>>>>>> here is a working command:
>>>>>>>>>>>
>>>>>>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>>>>>>
>>>>>>>>>>> The last one works fine:
>>>>>>>>>>>
>>>>>>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>>>>>>> apr-util.tgz
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> You must have Apache 2.4.7+
>>>>>>>>>>>>> Their is a fix in that version which allow mod_rewrite to work
>>>>>>>>>>>>> on web socket protocol instead of just http.
>>>>>>>>>>>>> You can look at the apache section in here
>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>>>>>>
>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> We are running Apache/2.2.22 with loaded
>>>>>>>>>>>>>> proxy_wstunnel_module (that we had to build from source).
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> From Apache error log (with debug):
>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506):
>>>>>>>>>>>>>> [client 130.202.2.217] proxy: http: found worker
>>>>>>>>>>>>>> http://localhost:8080/paraview for
>>>>>>>>>>>>>> http://localhost:8080/paraview/, referer:
>>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>>> proxy: HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>>>>> HTTP: has acquired connection for (localhost)
>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>>>>> connecting http://localhost:8080/paraview/ to localhost:8080
>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>>>>> connected /paraview/ to localhost:8080
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615):
>>>>>>>>>>>>>> [client 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/,
>>>>>>>>>>>>>> referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>>>>> HTTP: has released connection for (localhost)
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //
>>>>>>>>>>>>>> 54.211.22.94/ws://localhost:9998/ws
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525):
>>>>>>>>>>>>>> [client 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020): Running
>>>>>>>>>>>>>> scheme http handler (attempt 0)
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>>> proxy: HTTP: serving URL
>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011): proxy:
>>>>>>>>>>>>>> HTTP: has acquired connection for (*)
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067): proxy:
>>>>>>>>>>>>>> connecting
>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>> to 54.211.22.94:80
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193): proxy:
>>>>>>>>>>>>>> connected
>>>>>>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>>>>>>> 54.211.22.94:80
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444): proxy:
>>>>>>>>>>>>>> HTTP: fam 2 socket created to connect to *
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576): proxy:
>>>>>>>>>>>>>> HTTP: connection complete to 54.211.22.94:80 (54.211.22.94)
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94] File
>>>>>>>>>>>>>> does not exist: /pv/www/ws:
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029): proxy:
>>>>>>>>>>>>>> HTTP: has released connection for (*)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> POST took ~1 second. Timestamps for POST and the following
>>>>>>>>>>>>>> GET: 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> You may be able to check the system log that apache generate
>>>>>>>>>>>>>>> to see what went wrong.
>>>>>>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL":
>>>>>>>>>>>>>>>> "http://54.211.22.94:/paraview/", "port": 9999, "host":
>>>>>>>>>>>>>>>> "localhost", "sessionURL": "ws://
>>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs that
>>>>>>>>>>>>>>>> do not look right:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> And the message:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in
>>>>>>>>>>>>>>>>> action. Something there still needs attention and we are investigating
>>>>>>>>>>>>>>>>> further.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks for you patience and all the help that allows us to
>>>>>>>>>>>>>>>>> move forward.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ${host} should have been replaced with a static string
>>>>>>>>>>>>>>>>>> that match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f"
>>>>>>>>>>>>>>>>>> in your set of arguments. That will force some output generation to fill
>>>>>>>>>>>>>>>>>> some buffer which will allow the launcher to detect when the server is
>>>>>>>>>>>>>>>>>> actually ready.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I've noticed that the documentation is missing them.
>>>>>>>>>>>>>>>>>> Don't know why... Will update it at some point.
>>>>>>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> And the value for "timeout" should be way bigger than 5.
>>>>>>>>>>>>>>>>>> Like 25 maybe.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks for this detailed description! The process is
>>>>>>>>>>>>>>>>>>> starting to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Here is our complete launch.json (with the right
>>>>>>>>>>>>>>>>>>> sessionURL for a config with Apache, according to your email):
>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks MultiViews
>>>>>>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>>>>>>         RewriteMap session-to-port
>>>>>>>>>>>>>>>>>>> txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$
>>>>>>>>>>>>>>>>>>> [NC]
>>>>>>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in
>>>>>>>>>>>>>>>>>>> the browser,
>>>>>>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP
>>>>>>>>>>>>>>>>>>> FOR PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+
>>>>>>>>>>>>>>>>>>>  16:32   0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> First of all you need to understand the role of apache
>>>>>>>>>>>>>>>>>>>> here in order to see how the configuration should be.
>>>>>>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without
>>>>>>>>>>>>>>>>>>>> Apache, but such setup is not meant for production.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>>>>>>> - Apache can be use to serve the static content (html,
>>>>>>>>>>>>>>>>>>>> js, png, css...)
>>>>>>>>>>>>>>>>>>>> - Apache provide a single entry point host + port. This
>>>>>>>>>>>>>>>>>>>> prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the
>>>>>>>>>>>>>>>>>>>> proper ParaViewWeb instance on the backend based on a session ID. This mean
>>>>>>>>>>>>>>>>>>>> that the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Then you need to understand how the launcher works and
>>>>>>>>>>>>>>>>>>>> its role.
>>>>>>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not use
>>>>>>>>>>>>>>>>>>>> the same port as the main server (the process would not start). Hence, we
>>>>>>>>>>>>>>>>>>>> start it with some port and we let the user know that it should connect to
>>>>>>>>>>>>>>>>>>>> "ws://{host}:{port}/ws" where host and port get replaced with the set that
>>>>>>>>>>>>>>>>>>>> was used to create the process.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a
>>>>>>>>>>>>>>>>>>>> process which is meant to relay the communication to the backend using the
>>>>>>>>>>>>>>>>>>>> port and host that Apache is using. So the launcher should let the client
>>>>>>>>>>>>>>>>>>>> know what URL they should use so Apache could handle it and forward it to
>>>>>>>>>>>>>>>>>>>> the backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>>>>>>> In the same time to keep track on which host/port a
>>>>>>>>>>>>>>>>>>>> process is running the launcher generate a text file with the proper
>>>>>>>>>>>>>>>>>>>> mapping.
>>>>>>>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure
>>>>>>>>>>>>>>>>>>>> out how it should establish the connection to the backend.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule
>>>>>>>>>>>>>>>>>>>> actions?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as
>>>>>>>>>>>>>>>>>>>> the documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Read the documentation, the list is minimum and
>>>>>>>>>>>>>>>>>>>> provided in it.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> So the "host" is to select the proper network card when
>>>>>>>>>>>>>>>>>>>> you have several for the actual launcher server.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Then the resources are use for process management and
>>>>>>>>>>>>>>>>>>>> URL generation for the client. Which mean, what name should be used by
>>>>>>>>>>>>>>>>>>>> Apache to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the
>>>>>>>>>>>>>>>>>>>>> script you've suggested earlier:
>>>>>>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Then when a session start you can check the content
>>>>>>>>>>>>>>>>>>>>>> of that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Verified that those entires are added to the file and
>>>>>>>>>>>>>>>>>>>>> have the right format.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config
>>>>>>>>>>>>>>>>>>>>>> of your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting
>>>>>>>>>>>>>>>>>>>>> factory"}},
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on
>>>>>>>>>>>>>>>>>>>>>> which port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> A common error could also be that the apache does not
>>>>>>>>>>>>>>>>>>>>>> have the right to read the /data/proxy.txt file or that the launcher is not
>>>>>>>>>>>>>>>>>>>>>> able to write it.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries
>>>>>>>>>>>>>>>>>>>>> are added.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort
>>>>>>>>>>>>>>>>>>>>> these out because they have caused some confusion and we want to clear
>>>>>>>>>>>>>>>>>>>>> things up and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule
>>>>>>>>>>>>>>>>>>>>> actions?
>>>>>>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So
>>>>>>>>>>>>>>>>>>>>> far we have: proxy_module, proxy_http_module, and rewrite_module. We are
>>>>>>>>>>>>>>>>>>>>> unsure whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>>>> where we have some confusion about using "localhost"
>>>>>>>>>>>>>>>>>>>>> vs. "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student
>>>>>>>>>>>>>>>>>>>>>>> helping to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on
>>>>>>>>>>>>>>>>>>>>>>> Amazon EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and
>>>>>>>>>>>>>>>>>>>>>>> that PVW launcher is functioning (new entries are added to the proxy file,
>>>>>>>>>>>>>>>>>>>>>>> vis sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at: http://<hostname>/apps/Cone/
>>>>>>>>>>>>>>>>>>>>>>> we either get a timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache
>>>>>>>>>>>>>>>>>>>>>>> configuration, where we have:
>>>>>>>>>>>>>>>>>>>>>>> ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview
>>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow to
>>>>>>>>>>>>>>>>>>>>>>> move forward with our isntallation.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/e6038a6a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 154565 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/e6038a6a/attachment-0001.png>

From utkarsh.ayachit at kitware.com  Tue Jul 22 16:10:41 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 16:10:41 -0400
Subject: [Paraview] get the sum of a cell or point variable
	(UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE7030@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101C482@umechp9h.easf.csd.disa.mil>
 <CADHSJjAMjX=LFwM6c68e0eLPY89SErtmk2g43YSE28m52JmqWA@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE7030@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjCTh8K9up=XLBGtWkO5wfS-eqt1bdVHEAUeUMzg3S_Now@mail.gmail.com>

Hey, once the sum() is computed by the calculator, you can just use "save
data" from the menu and save it out as a CSV :P.

Utkarsh


On Tue, Jul 22, 2014 at 3:49 PM, Su, Simon M CTR USARMY ARL (US) <
simon.m.su.ctr at mail.mil> wrote:

> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hi Utkarsh,
>
> That's great. That will eliminate the programmable filter part of my
> pipeline.
> You didn't happen to also pushed update to VTK/ParaView that will write the
> expression "sum(EQPS)" to a file that will work in parallel, did you? :)
>
> Thanks
> -simon
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Tuesday, July 22, 2014 3:43 PM
> To: Su, Simon M CTR USARMY ARL (US)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] get the sum of a cell or point variable
> (UNCLASSIFIED)
>
> Simon,
>
> As I am cleaning my inbox, I ran into this email. Since there have been
> other
> emails about this I'll skip your original query :). Just wanted to give
> you an
> update on recent developments in ParaView. We recently pushed updates to
> VTK/ParaView to allow you to use Python calculator to compute "sum" in
> parallel across all blocks in the dataset. e.g. for can.ex2, you can apply
> the
> Python Calculator and select "Cell Data", with expression "sum(EQPS)" the
> result array will have the true global sum. This also includes operations
> like
> min/max/mean etc.
>
> Utkarsh
>
>
> On Wed, Jun 25, 2014 at 11:21 AM, Su, Simon M CTR USARMY ARL (US)
> <simon.m.su.ctr at mail.mil> wrote:
>
>
>         Classification: UNCLASSIFIED
>         Caveats: NONE
>
>         Hello,
>
>         Running in PV client/server mode, is there a calculator function
> that will
>         add up all the values of a variable (cell or point variable).
>
>         I can use the programmable filter to write a python loop to
> iterate through
>         all the cell/point of the variable and add them up. But, running
> in a
>         client/server mode, how would you store that value? Can I just add
> a single
>         value (not array) to the data? If so, what vtk data structure
> shall I use to
>         store a double variable? vtk.vtkDouble()? Or is there a way to
> write that
>         value out to a file. Running it in parallel, how would that be
> handled?
>
>         Thanks
>         -simon
>
>         Classification: UNCLASSIFIED
>         Caveats: NONE
>
>
>
>         _______________________________________________
>         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://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/fd71fd39/attachment.html>

From simon.m.su.ctr at mail.mil  Tue Jul 22 16:20:11 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Tue, 22 Jul 2014 20:20:11 +0000
Subject: [Paraview] get the sum of a cell or point variable
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjCTh8K9up=XLBGtWkO5wfS-eqt1bdVHEAUeUMzg3S_Now@mail.gmail.com>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101C482@umechp9h.easf.csd.disa.mil>
 <CADHSJjAMjX=LFwM6c68e0eLPY89SErtmk2g43YSE28m52JmqWA@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE7030@umechp9h.easf.csd.disa.mil>
 <CADHSJjCTh8K9up=XLBGtWkO5wfS-eqt1bdVHEAUeUMzg3S_Now@mail.gmail.com>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE707A@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Errr.... what would be the equivalent to "menu->save" in python script? Sorry 
for making it difficult as the whole thing is a part of a elaborate automation 
from running simulation to getting the final result. Calling python calculator 
to calculate sum will be in a script run with pvbatch in parallel environment. 
Is CSV file format the best format if I just want to write that sum value out 
to a file? Any example script on writing 1 variable to CSV file format?

Thanks
-simon

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Tuesday, July 22, 2014 4:11 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] get the sum of a cell or point variable (UNCLASSIFIED)

Hey, once the sum() is computed by the calculator, you can just use "save 
data" from the menu and save it out as a CSV :P.

Utkarsh


On Tue, Jul 22, 2014 at 3:49 PM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:


	Classification: UNCLASSIFIED
	Caveats: NONE

	Hi Utkarsh,

	That's great. That will eliminate the programmable filter part of my 
pipeline.
	You didn't happen to also pushed update to VTK/ParaView that will write the
	expression "sum(EQPS)" to a file that will work in parallel, did you? :)

	Thanks
	-simon


	-----Original Message-----
	From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
	Sent: Tuesday, July 22, 2014 3:43 PM
	To: Su, Simon M CTR USARMY ARL (US)
	Cc: paraview at paraview.org
	Subject: Re: [Paraview] get the sum of a cell or point variable 
(UNCLASSIFIED)

	Simon,

	As I am cleaning my inbox, I ran into this email. Since there have been other
	emails about this I'll skip your original query :). Just wanted to give you 
an
	update on recent developments in ParaView. We recently pushed updates to
	VTK/ParaView to allow you to use Python calculator to compute "sum" in
	parallel across all blocks in the dataset. e.g. for can.ex2, you can apply 
the
	Python Calculator and select "Cell Data", with expression "sum(EQPS)" the
	result array will have the true global sum. This also includes operations 
like
	min/max/mean etc.

	Utkarsh


	On Wed, Jun 25, 2014 at 11:21 AM, Su, Simon M CTR USARMY ARL (US)
	<simon.m.su.ctr at mail.mil> wrote:


	        Classification: UNCLASSIFIED
	        Caveats: NONE

	        Hello,

	        Running in PV client/server mode, is there a calculator function that 
will
	        add up all the values of a variable (cell or point variable).

	        I can use the programmable filter to write a python loop to iterate 
through
	        all the cell/point of the variable and add them up. But, running in a
	        client/server mode, how would you store that value? Can I just add a 
single
	        value (not array) to the data? If so, what vtk data structure shall I 
use to
	        store a double variable? vtk.vtkDouble()? Or is there a way to write 
that
	        value out to a file. Running it in parallel, how would that be 
handled?

	        Thanks
	        -simon

	        Classification: UNCLASSIFIED
	        Caveats: NONE



	        _______________________________________________
	        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://public.kitware.com/mailman/listinfo/paraview






	Classification: UNCLASSIFIED
	Caveats: NONE






Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5633 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/f0936842/attachment.bin>

From utkarsh.ayachit at kitware.com  Tue Jul 22 16:26:39 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 22 Jul 2014 16:26:39 -0400
Subject: [Paraview] get the sum of a cell or point variable
	(UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE707A@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD821101C482@umechp9h.easf.csd.disa.mil>
 <CADHSJjAMjX=LFwM6c68e0eLPY89SErtmk2g43YSE28m52JmqWA@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE7030@umechp9h.easf.csd.disa.mil>
 <CADHSJjCTh8K9up=XLBGtWkO5wfS-eqt1bdVHEAUeUMzg3S_Now@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CE707A@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjBpwpnT5GM+cMDwKLCtetHA7E7k6CBc=H3rg45=VQYjNw@mail.gmail.com>

Simon,

So there are two types of Python scripts in ParaView: the data processing
(which goes in programmable filter, python calculator etc.) and the
client-side. For automation, you'd be interested in the scripting the
client. For that, you have WriteData() (or something like that) in the
simple.py module (
http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.simple.html).
It's not there yet, the code went in git/master earlier today. But you'll
be able to use Python trace to determine what call to use :).

Utkarsh


On Tue, Jul 22, 2014 at 4:20 PM, Su, Simon M CTR USARMY ARL (US) <
simon.m.su.ctr at mail.mil> wrote:

> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Errr.... what would be the equivalent to "menu->save" in python script?
> Sorry
> for making it difficult as the whole thing is a part of a elaborate
> automation
> from running simulation to getting the final result. Calling python
> calculator
> to calculate sum will be in a script run with pvbatch in parallel
> environment.
> Is CSV file format the best format if I just want to write that sum value
> out
> to a file? Any example script on writing 1 variable to CSV file format?
>
> Thanks
> -simon
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Tuesday, July 22, 2014 4:11 PM
> To: Su, Simon M CTR USARMY ARL (US)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] get the sum of a cell or point variable
> (UNCLASSIFIED)
>
> Hey, once the sum() is computed by the calculator, you can just use "save
> data" from the menu and save it out as a CSV :P.
>
> Utkarsh
>
>
> On Tue, Jul 22, 2014 at 3:49 PM, Su, Simon M CTR USARMY ARL (US)
> <simon.m.su.ctr at mail.mil> wrote:
>
>
>         Classification: UNCLASSIFIED
>         Caveats: NONE
>
>         Hi Utkarsh,
>
>         That's great. That will eliminate the programmable filter part of
> my
> pipeline.
>         You didn't happen to also pushed update to VTK/ParaView that will
> write the
>         expression "sum(EQPS)" to a file that will work in parallel, did
> you? :)
>
>         Thanks
>         -simon
>
>
>         -----Original Message-----
>         From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>         Sent: Tuesday, July 22, 2014 3:43 PM
>         To: Su, Simon M CTR USARMY ARL (US)
>         Cc: paraview at paraview.org
>         Subject: Re: [Paraview] get the sum of a cell or point variable
> (UNCLASSIFIED)
>
>         Simon,
>
>         As I am cleaning my inbox, I ran into this email. Since there have
> been other
>         emails about this I'll skip your original query :). Just wanted to
> give you
> an
>         update on recent developments in ParaView. We recently pushed
> updates to
>         VTK/ParaView to allow you to use Python calculator to compute
> "sum" in
>         parallel across all blocks in the dataset. e.g. for can.ex2, you
> can apply
> the
>         Python Calculator and select "Cell Data", with expression
> "sum(EQPS)" the
>         result array will have the true global sum. This also includes
> operations
> like
>         min/max/mean etc.
>
>         Utkarsh
>
>
>         On Wed, Jun 25, 2014 at 11:21 AM, Su, Simon M CTR USARMY ARL (US)
>         <simon.m.su.ctr at mail.mil> wrote:
>
>
>                 Classification: UNCLASSIFIED
>                 Caveats: NONE
>
>                 Hello,
>
>                 Running in PV client/server mode, is there a calculator
> function that
> will
>                 add up all the values of a variable (cell or point
> variable).
>
>                 I can use the programmable filter to write a python loop
> to iterate
> through
>                 all the cell/point of the variable and add them up. But,
> running in a
>                 client/server mode, how would you store that value? Can I
> just add a
> single
>                 value (not array) to the data? If so, what vtk data
> structure shall I
> use to
>                 store a double variable? vtk.vtkDouble()? Or is there a
> way to write
> that
>                 value out to a file. Running it in parallel, how would
> that be
> handled?
>
>                 Thanks
>                 -simon
>
>                 Classification: UNCLASSIFIED
>                 Caveats: NONE
>
>
>
>                 _______________________________________________
>                 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://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
>
>
>         Classification: UNCLASSIFIED
>         Caveats: NONE
>
>
>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/a8520be8/attachment-0001.html>

From sebastien.jourdain at kitware.com  Tue Jul 22 18:06:21 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 22 Jul 2014 16:06:21 -0600
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CAJiCY3Zcc4GJUy+s4cVzUDebVaa1V+wFa1-98gw9KaJ4sNC=Lg@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
 <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
 <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>
 <CAJiCY3ZtyR1s0Xadx=EQ6-w3sxAt_AZq8BaQ63ThLg0m3u+-QQ@mail.gmail.com>
 <CABObKxfrPXkUuXPyYNV4=QQiXU=haYU8dNthk1g_ThzUuFL=Sw@mail.gmail.com>
 <CABObKxd8EWZbm_haO4Bxf0pS4KPtb4ebmtLoeY3AzQ22NToopA@mail.gmail.com>
 <CAJiCY3Zcc4GJUy+s4cVzUDebVaa1V+wFa1-98gw9KaJ4sNC=Lg@mail.gmail.com>
Message-ID: <CABObKxfoQHJOTN18A-XBB7d5P4H-z4-oq8+MehwC0K3uigis9w@mail.gmail.com>

It seems to work now... ;-)


On Tue, Jul 22, 2014 at 2:07 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
wrote:

> This makes sense and it most definitely helped!
>
> We can now see this when we access: http://54.211.22.94/apps/Cone/
>
>
> [image: Inline image 1]
>
> but we are getting:
> *uncaught exception: cannot resolve CURIE prefix 'vtk'*
>
> What might be causing this?
>
>
> On Tue, Jul 22, 2014 at 2:36 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> The script is great when you don't want to build ParaView, but since you
>> did, you should make sure the server and the client code (html+js) are in
>> synch. Which is basically the content of that lib/ext/apps directories.
>>
>>
>> On Tue, Jul 22, 2014 at 1:35 PM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> Yes you should replace the content of the directory that you share with
>>> apache with the content that come from your {build-tree}/www.
>>>
>>> Just replace the three following dirs: apps, lib, ext
>>>
>>> Seb
>>>
>>>
>>> On Tue, Jul 22, 2014 at 1:21 PM, Dmitry Duplyakin <
>>> duplyakin at uchicago.edu> wrote:
>>>
>>>> Any comments on our build process?
>>>>
>>>> We are a bit concerned about compatibility between the stuff from that
>>>> tar file and the stuff that we build from the cloned paraview code.
>>>> Anything we should pay special attention to?
>>>>
>>>> Also, yesterday we saw the error when we called pvpython:
>>>>
>>>> /pv/paraview/lib/paraview-4.1/pvpython: error while loading shared
>>>> libraries: libvtkPVServerManagerApplication-pv4.1.so.1: cannot open shared
>>>> object file: No such file or directory
>>>>
>>>> and fixed it by adding
>>>>
>>>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/pv/paraview/lib/paraview-4.1
>>>>
>>>> to our environment's profile. Seems to be a solved problem now, but can
>>>> it possibly be caused by a compatibility issue?
>>>>
>>>> Finally, the cone file,
>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py, in our case
>>>> remains in the src dir, the one where we clone paraview code from git. We
>>>> understand that it is used with pvpython that knows about specific
>>>> locations in our environment, but still it looks odd that the cone file
>>>> remains in src, directory that can be considered for removal after
>>>> installation is done. Are we missing something here?
>>>>
>>>>
>>>> On Tue, Jul 22, 2014 at 11:16 AM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> Definitely worth checking.
>>>>>
>>>>> Here is what I did to install it:
>>>>>
>>>>> I used the script from: http://www.paraview.org/files/web/pvw-setup
>>>>>
>>>>> which unpacks ParaView-4.1.0-Linux-64bit-glibc-2.3.6.tar.gz
>>>>>
>>>>> and sets up directories like www, conf, etc.
>>>>>
>>>>> Then in order to build ParaView from source I did: git://
>>>>> paraview.org/stage/ParaView.git
>>>>>
>>>>> followed by "git submodule update --init", as recommended at
>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup
>>>>>
>>>>> for Apache <2.4, which I was running until yesterday.
>>>>>
>>>>> See anything wrong?
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jul 22, 2014 at 10:47 AM, Sebastien Jourdain <
>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>>> Just a though...
>>>>>>
>>>>>> Which version of ParaView did you build? git master?
>>>>>>
>>>>>> If so, did you use the www directory from that build or did you use
>>>>>> the one from the binaries?
>>>>>> There could be a version miss match in that later case.
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>
>>>>>>> Hi Dmitry,
>>>>>>>
>>>>>>> I've just tried to connect to your server and it seems that the
>>>>>>> process start in about 1s. That might be correct but it seems fast to me.
>>>>>>> Do you see any error after the +++++ log file?
>>>>>>>
>>>>>>> Could you edit your launcher config to add an entry for the
>>>>>>> "pipeline" app?
>>>>>>> The cone is just relying on VTK and I was curious if we could see
>>>>>>> something different with our main sample app that use paraview.
>>>>>>>
>>>>>>> For that you just need to kill the launcher process and restart it
>>>>>>> with the new config.
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <
>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>
>>>>>>>> All I see is described js error. (I see it in the Firefox'es
>>>>>>>> Firebug console)
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <
>>>>>>>> karpeev at mcs.anl.gov> wrote:
>>>>>>>>
>>>>>>>>> Is there a Python error/stack trace that comes with this?
>>>>>>>>>  On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <
>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Sebastien,
>>>>>>>>>>
>>>>>>>>>> Thanks again for your help yesterday!
>>>>>>>>>>
>>>>>>>>>> We have upgraded and running Apache-2.4.7 now.
>>>>>>>>>>
>>>>>>>>>> We are seeing a now error:
>>>>>>>>>>  Firefox can't establish a connection to the server at ws://
>>>>>>>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>>>>>>>> .
>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>
>>>>>>>>>> Last line points to code in autobahn.js
>>>>>>>>>> ab._construct = function (url, protocols) {
>>>>>>>>>>    if ("WebSocket" in window) {
>>>>>>>>>>       // Chrome, MSIE, newer Firefox
>>>>>>>>>>       if (protocols) {
>>>>>>>>>>          *return new WebSocket(url, protocols);*
>>>>>>>>>>       } else {
>>>>>>>>>>          return new WebSocket(url);
>>>>>>>>>>       }
>>>>>>>>>>    } else if ("MozWebSocket" in window) {
>>>>>>>>>>       // older versions of Firefox prefix the WebSocket object
>>>>>>>>>>       if (protocols) {
>>>>>>>>>>          return new MozWebSocket(url, protocols);
>>>>>>>>>>       } else {
>>>>>>>>>>          return new MozWebSocket(url);
>>>>>>>>>>       }
>>>>>>>>>>    } else {
>>>>>>>>>>       return null;
>>>>>>>>>>    }
>>>>>>>>>> };
>>>>>>>>>>
>>>>>>>>>> In the meantime, session gets created, session log has a standard
>>>>>>>>>> opening followed by many lines with "+" signs (which means it is running
>>>>>>>>>> fine, right?), POST is successful:
>>>>>>>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>>>>>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/"
>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>> Firefox/30.0".
>>>>>>>>>>
>>>>>>>>>> Its response:
>>>>>>>>>>
>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>>>>>>>
>>>>>>>>>> Are possibly missing anything here?
>>>>>>>>>>
>>>>>>>>>> Looks like Apache log verifies that wstunnel is working:
>>>>>>>>>>
>>>>>>>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>>>>>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>>>>>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>>>>>>>
>>>>>>>>>> Any thoughts on what might be causing this problem?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Should work... I guess this documentation will always be out of
>>>>>>>>>>> date. ;-)
>>>>>>>>>>>
>>>>>>>>>>> But the good news is that modern system have the right version
>>>>>>>>>>> of Apache, so no fancy build are needed anymore...
>>>>>>>>>>>
>>>>>>>>>>> Seb
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>  Trying to follow instructions from
>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>>>>>>>> It looks like those urls used with wget are broken.
>>>>>>>>>>>>
>>>>>>>>>>>> Found a replacement for httpd:
>>>>>>>>>>>>
>>>>>>>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz
>>>>>>>>>>>> -O httpd.tgz
>>>>>>>>>>>>
>>>>>>>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so,
>>>>>>>>>>>> here is a working command:
>>>>>>>>>>>>
>>>>>>>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>>>>>>>
>>>>>>>>>>>> The last one works fine:
>>>>>>>>>>>>
>>>>>>>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>>>>>>>> apr-util.tgz
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> You must have Apache 2.4.7+
>>>>>>>>>>>>>> Their is a fix in that version which allow mod_rewrite to
>>>>>>>>>>>>>> work on web socket protocol instead of just http.
>>>>>>>>>>>>>> You can look at the apache section in here
>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We are running Apache/2.2.22 with loaded
>>>>>>>>>>>>>>> proxy_wstunnel_module (that we had to build from source).
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> From Apache error log (with debug):
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506):
>>>>>>>>>>>>>>> [client 130.202.2.217] proxy: http: found worker
>>>>>>>>>>>>>>> http://localhost:8080/paraview for
>>>>>>>>>>>>>>> http://localhost:8080/paraview/, referer:
>>>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020):
>>>>>>>>>>>>>>> Running scheme http handler (attempt 0)
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>>>> proxy: HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011):
>>>>>>>>>>>>>>> proxy: HTTP: has acquired connection for (localhost)
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067):
>>>>>>>>>>>>>>> proxy: connecting http://localhost:8080/paraview/ to
>>>>>>>>>>>>>>> localhost:8080
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193):
>>>>>>>>>>>>>>> proxy: connected /paraview/ to localhost:8080
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615):
>>>>>>>>>>>>>>> [client 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/,
>>>>>>>>>>>>>>> referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029):
>>>>>>>>>>>>>>> proxy: HTTP: has released connection for (localhost)
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //
>>>>>>>>>>>>>>> 54.211.22.94/ws://localhost:9998/ws
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525):
>>>>>>>>>>>>>>> [client 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020):
>>>>>>>>>>>>>>> Running scheme http handler (attempt 0)
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>>>> proxy: HTTP: serving URL
>>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011):
>>>>>>>>>>>>>>> proxy: HTTP: has acquired connection for (*)
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067):
>>>>>>>>>>>>>>> proxy: connecting
>>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>>> to 54.211.22.94:80
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193):
>>>>>>>>>>>>>>> proxy: connected
>>>>>>>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>>>>>>>> 54.211.22.94:80
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444):
>>>>>>>>>>>>>>> proxy: HTTP: fam 2 socket created to connect to *
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576):
>>>>>>>>>>>>>>> proxy: HTTP: connection complete to 54.211.22.94:80
>>>>>>>>>>>>>>> (54.211.22.94)
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94]
>>>>>>>>>>>>>>> File does not exist: /pv/www/ws:
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029):
>>>>>>>>>>>>>>> proxy: HTTP: has released connection for (*)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> POST took ~1 second. Timestamps for POST and the following
>>>>>>>>>>>>>>> GET: 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> You may be able to check the system log that apache
>>>>>>>>>>>>>>>> generate to see what went wrong.
>>>>>>>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL":
>>>>>>>>>>>>>>>>> "http://54.211.22.94:/paraview/", "port": 9999, "host":
>>>>>>>>>>>>>>>>> "localhost", "sessionURL": "ws://
>>>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs
>>>>>>>>>>>>>>>>> that do not look right:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> And the message:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Firefox can't establish a connection to the server at ws://
>>>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in
>>>>>>>>>>>>>>>>>> action. Something there still needs attention and we are investigating
>>>>>>>>>>>>>>>>>> further.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks for you patience and all the help that allows us
>>>>>>>>>>>>>>>>>> to move forward.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> ${host} should have been replaced with a static string
>>>>>>>>>>>>>>>>>>> that match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f"
>>>>>>>>>>>>>>>>>>> in your set of arguments. That will force some output generation to fill
>>>>>>>>>>>>>>>>>>> some buffer which will allow the launcher to detect when the server is
>>>>>>>>>>>>>>>>>>> actually ready.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I've noticed that the documentation is missing them.
>>>>>>>>>>>>>>>>>>> Don't know why... Will update it at some point.
>>>>>>>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> And the value for "timeout" should be way bigger than
>>>>>>>>>>>>>>>>>>> 5. Like 25 maybe.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Thanks for this detailed description! The process is
>>>>>>>>>>>>>>>>>>>> starting to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Here is our complete launch.json (with the right
>>>>>>>>>>>>>>>>>>>> sessionURL for a config with Apache, according to your email):
>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks
>>>>>>>>>>>>>>>>>>>> MultiViews
>>>>>>>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>>>>>>>         RewriteMap session-to-port
>>>>>>>>>>>>>>>>>>>> txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}
>>>>>>>>>>>>>>>>>>>> ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in
>>>>>>>>>>>>>>>>>>>> the browser,
>>>>>>>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP
>>>>>>>>>>>>>>>>>>>> FOR PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+
>>>>>>>>>>>>>>>>>>>>  16:32   0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> First of all you need to understand the role of apache
>>>>>>>>>>>>>>>>>>>>> here in order to see how the configuration should be.
>>>>>>>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without
>>>>>>>>>>>>>>>>>>>>> Apache, but such setup is not meant for production.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>>>>>>>> - Apache can be use to serve the static content (html,
>>>>>>>>>>>>>>>>>>>>> js, png, css...)
>>>>>>>>>>>>>>>>>>>>> - Apache provide a single entry point host + port.
>>>>>>>>>>>>>>>>>>>>> This prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to the
>>>>>>>>>>>>>>>>>>>>> proper ParaViewWeb instance on the backend based on a session ID. This mean
>>>>>>>>>>>>>>>>>>>>> that the ParaViewWeb process DOES NOT need to be on the same machine as the
>>>>>>>>>>>>>>>>>>>>> Apache Web Server.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Then you need to understand how the launcher works and
>>>>>>>>>>>>>>>>>>>>> its role.
>>>>>>>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>>>>>>>> So when a user connect to the system and request a new
>>>>>>>>>>>>>>>>>>>>> visualization session, it is the responsibility of the launcher to start
>>>>>>>>>>>>>>>>>>>>> the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not
>>>>>>>>>>>>>>>>>>>>> use the same port as the main server (the process would not start). Hence,
>>>>>>>>>>>>>>>>>>>>> we start it with some port and we let the user know that it should connect
>>>>>>>>>>>>>>>>>>>>> to "ws://{host}:{port}/ws" where host and port get replaced with the set
>>>>>>>>>>>>>>>>>>>>> that was used to create the process.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a
>>>>>>>>>>>>>>>>>>>>> process which is meant to relay the communication to the backend using the
>>>>>>>>>>>>>>>>>>>>> port and host that Apache is using. So the launcher should let the client
>>>>>>>>>>>>>>>>>>>>> know what URL they should use so Apache could handle it and forward it to
>>>>>>>>>>>>>>>>>>>>> the backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>>>>>>>> In the same time to keep track on which host/port a
>>>>>>>>>>>>>>>>>>>>> process is running the launcher generate a text file with the proper
>>>>>>>>>>>>>>>>>>>>> mapping.
>>>>>>>>>>>>>>>>>>>>> That mapping file is then used inside Apache to figure
>>>>>>>>>>>>>>>>>>>>> out how it should establish the connection to the backend.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule
>>>>>>>>>>>>>>>>>>>>> actions?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well as
>>>>>>>>>>>>>>>>>>>>> the documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Read the documentation, the list is minimum and
>>>>>>>>>>>>>>>>>>>>> provided in it.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> So the "host" is to select the proper network card
>>>>>>>>>>>>>>>>>>>>> when you have several for the actual launcher server.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Then the resources are use for process management and
>>>>>>>>>>>>>>>>>>>>> URL generation for the client. Which mean, what name should be used by
>>>>>>>>>>>>>>>>>>>>> Apache to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use "
>>>>>>>>>>>>>>>>>>>>>> proxy?sessionId=" there? Ours came directly from the
>>>>>>>>>>>>>>>>>>>>>> script you've suggested earlier:
>>>>>>>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Then when a session start you can check the content
>>>>>>>>>>>>>>>>>>>>>>> of that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Verified that those entires are added to the file and
>>>>>>>>>>>>>>>>>>>>>> have the right format.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the config
>>>>>>>>>>>>>>>>>>>>>>> of your cone app: "ready_line" : "Starting factory"
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting
>>>>>>>>>>>>>>>>>>>>>> factory"}},
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> You can check is any pvpython process is running, on
>>>>>>>>>>>>>>>>>>>>>>> which port, see if that match in the proxy file (/data/proxy.txt) and also
>>>>>>>>>>>>>>>>>>>>>>> looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> A common error could also be that the apache does
>>>>>>>>>>>>>>>>>>>>>>> not have the right to read the /data/proxy.txt file or that the launcher is
>>>>>>>>>>>>>>>>>>>>>>> not able to write it.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries
>>>>>>>>>>>>>>>>>>>>>> are added.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort
>>>>>>>>>>>>>>>>>>>>>> these out because they have caused some confusion and we want to clear
>>>>>>>>>>>>>>>>>>>>>> things up and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule
>>>>>>>>>>>>>>>>>>>>>> actions?
>>>>>>>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So
>>>>>>>>>>>>>>>>>>>>>> far we have: proxy_module, proxy_http_module, and rewrite_module. We are
>>>>>>>>>>>>>>>>>>>>>> unsure whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>>>>> where we have some confusion about using "localhost"
>>>>>>>>>>>>>>>>>>>>>> vs. "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student
>>>>>>>>>>>>>>>>>>>>>>>> helping to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on
>>>>>>>>>>>>>>>>>>>>>>>> Amazon EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and
>>>>>>>>>>>>>>>>>>>>>>>> that PVW launcher is functioning (new entries are added to the proxy file,
>>>>>>>>>>>>>>>>>>>>>>>> vis sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually gets
>>>>>>>>>>>>>>>>>>>>>>>> called. In order to test it, we used /pv/www/apps/TestApp/index.html as a
>>>>>>>>>>>>>>>>>>>>>>>> template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at:
>>>>>>>>>>>>>>>>>>>>>>>> http://<hostname>/apps/Cone/ we either get a
>>>>>>>>>>>>>>>>>>>>>>>> timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>>>>>>>> /paraview/, referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache
>>>>>>>>>>>>>>>>>>>>>>>> configuration, where we have:
>>>>>>>>>>>>>>>>>>>>>>>> ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview
>>>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$
>>>>>>>>>>>>>>>>>>>>>>>> [NC]
>>>>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can their
>>>>>>>>>>>>>>>>>>>>>>>> actions be logged and verified?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or some
>>>>>>>>>>>>>>>>>>>>>>>> additional configuration in Apache?
>>>>>>>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow
>>>>>>>>>>>>>>>>>>>>>>>> to move forward with our isntallation.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/8ded1f0a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 154565 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/8ded1f0a/attachment-0001.png>

From duplyakin at uchicago.edu  Tue Jul 22 18:14:59 2014
From: duplyakin at uchicago.edu (Dmitry Duplyakin)
Date: Tue, 22 Jul 2014 17:14:59 -0500
Subject: [Paraview] Visualizing a Cone with PVW - Connection can't be
	established
In-Reply-To: <CABObKxfoQHJOTN18A-XBB7d5P4H-z4-oq8+MehwC0K3uigis9w@mail.gmail.com>
References: <CALyczHyQvRQMzjO6=gker+Y8LtsmwihKvWKbohCuc24CmnuO8g@mail.gmail.com>
 <CABObKxd+7yjYdRb=jjSkYYfT1WAu-b2C4WCUZQMDaMXO3=3Xpg@mail.gmail.com>
 <CAJiCY3ZSUK8FHbeH2AFHE_JGJuO6brbRMeq6co5tJMPpH-640A@mail.gmail.com>
 <CABObKxc2NH7aWrvUJEyXpN2Ssagbv8-AYJgzytw67UxPPYpXrA@mail.gmail.com>
 <CAJiCY3aup2pgAX76N0tirseM1Wq2dcvg7-gJTzFuU8-W8XB+og@mail.gmail.com>
 <CABObKxfPd=WBDetVLeA+XWn6h4dvGRdGgDesHY=VN7VL-TOtPQ@mail.gmail.com>
 <CAJiCY3Y4DfUhe-UrhWrsnresXwCZEhJ0-miRbyc1eqAo89_SaA@mail.gmail.com>
 <CAJiCY3bS6MKuyppvb3EcWww9_Fupwn7kFb3iNiA=J5D-wvC8vw@mail.gmail.com>
 <CABObKxc04VhC6u2Vh=a0C8Vn2crnXC9u7+2Kc7P6TKY93wAJpw@mail.gmail.com>
 <CAJiCY3Zd+7hxd+R1RScoL+fstYJZb79qUgPEqm9Zv8fRqGw6RQ@mail.gmail.com>
 <CABObKxdMurTqq1jjD-oZAFHdjEkf_ukW0fbi+1TbJN_3-T4UTQ@mail.gmail.com>
 <CAJiCY3bGro-_bT3uk8gSnG2gtrWTHYf3oDsPfJy6DXvNb+jPag@mail.gmail.com>
 <CAJiCY3Z4eMX5n0bQos553EKQ1+-+B5-vJ3CH=V1GfAA2uY7a=g@mail.gmail.com>
 <CABObKxe0tVnpBaNsSL9CydAzJL8d0bCAWSWqD_Upi9Q8jybYQA@mail.gmail.com>
 <CAJiCY3ZeAB9RN+qy9LEdjoSaUfV+a-E3dh6=1or467ixmNg2Dw@mail.gmail.com>
 <CA+Y_9ULthhZrXspYhDmM_TZRviFSCVm=8dhCXEFJxMKoSfKF5Q@mail.gmail.com>
 <CAJiCY3ZwoyAQhy+DBM95X0nGsKWoFx9TPfnCu94vxHUNM-CeUg@mail.gmail.com>
 <CABObKxf8DSLMD_UDemUx7VyXd3s4fnYNmWo0zFRpYAepoB55aQ@mail.gmail.com>
 <CABObKxdnGUedx6ksgoa_GGyMKPV3GWgWi0FoBuBU0_P2J7YB3w@mail.gmail.com>
 <CAJiCY3Y9Z9d_itrnaGNqVc-Z4fmJaB=0oCeiUy4p0iWvBz+wEg@mail.gmail.com>
 <CAJiCY3ZtyR1s0Xadx=EQ6-w3sxAt_AZq8BaQ63ThLg0m3u+-QQ@mail.gmail.com>
 <CABObKxfrPXkUuXPyYNV4=QQiXU=haYU8dNthk1g_ThzUuFL=Sw@mail.gmail.com>
 <CABObKxd8EWZbm_haO4Bxf0pS4KPtb4ebmtLoeY3AzQ22NToopA@mail.gmail.com>
 <CAJiCY3Zcc4GJUy+s4cVzUDebVaa1V+wFa1-98gw9KaJ4sNC=Lg@mail.gmail.com>
 <CABObKxfoQHJOTN18A-XBB7d5P4H-z4-oq8+MehwC0K3uigis9w@mail.gmail.com>
Message-ID: <CAJiCY3bj0xzRheimHQ5HubNzoSEO1cNmzJdW0_vX8k+=fKCQvw@mail.gmail.com>

Yes, We have just resolved our last issue!!

[image: Inline image 1]

Sebastien, thank you so much for your generous help and patience!!

We are now making sure that we have configs, versions, paths, etc.
preserved and documented.

We are getting excited about using ParaViewWeb now and doing a number of
cool things with it!



On Tue, Jul 22, 2014 at 5:06 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> It seems to work now... ;-)
>
>
> On Tue, Jul 22, 2014 at 2:07 PM, Dmitry Duplyakin <duplyakin at uchicago.edu>
> wrote:
>
>> This makes sense and it most definitely helped!
>>
>> We can now see this when we access: http://54.211.22.94/apps/Cone/
>>
>>
>> [image: Inline image 1]
>>
>> but we are getting:
>> *uncaught exception: cannot resolve CURIE prefix 'vtk'*
>>
>> What might be causing this?
>>
>>
>> On Tue, Jul 22, 2014 at 2:36 PM, Sebastien Jourdain <
>> sebastien.jourdain at kitware.com> wrote:
>>
>>> The script is great when you don't want to build ParaView, but since you
>>> did, you should make sure the server and the client code (html+js) are in
>>> synch. Which is basically the content of that lib/ext/apps directories.
>>>
>>>
>>> On Tue, Jul 22, 2014 at 1:35 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>>> Yes you should replace the content of the directory that you share with
>>>> apache with the content that come from your {build-tree}/www.
>>>>
>>>> Just replace the three following dirs: apps, lib, ext
>>>>
>>>> Seb
>>>>
>>>>
>>>> On Tue, Jul 22, 2014 at 1:21 PM, Dmitry Duplyakin <
>>>> duplyakin at uchicago.edu> wrote:
>>>>
>>>>> Any comments on our build process?
>>>>>
>>>>> We are a bit concerned about compatibility between the stuff from that
>>>>> tar file and the stuff that we build from the cloned paraview code.
>>>>> Anything we should pay special attention to?
>>>>>
>>>>> Also, yesterday we saw the error when we called pvpython:
>>>>>
>>>>> /pv/paraview/lib/paraview-4.1/pvpython: error while loading shared
>>>>> libraries: libvtkPVServerManagerApplication-pv4.1.so.1: cannot open shared
>>>>> object file: No such file or directory
>>>>>
>>>>> and fixed it by adding
>>>>>
>>>>> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/pv/paraview/lib/paraview-4.1
>>>>>
>>>>> to our environment's profile. Seems to be a solved problem now, but
>>>>> can it possibly be caused by a compatibility issue?
>>>>>
>>>>> Finally, the cone file,
>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py, in our case
>>>>> remains in the src dir, the one where we clone paraview code from git. We
>>>>> understand that it is used with pvpython that knows about specific
>>>>> locations in our environment, but still it looks odd that the cone file
>>>>> remains in src, directory that can be considered for removal after
>>>>> installation is done. Are we missing something here?
>>>>>
>>>>>
>>>>> On Tue, Jul 22, 2014 at 11:16 AM, Dmitry Duplyakin <
>>>>> duplyakin at uchicago.edu> wrote:
>>>>>
>>>>>> Definitely worth checking.
>>>>>>
>>>>>> Here is what I did to install it:
>>>>>>
>>>>>> I used the script from: http://www.paraview.org/files/web/pvw-setup
>>>>>>
>>>>>> which unpacks ParaView-4.1.0-Linux-64bit-glibc-2.3.6.tar.gz
>>>>>>
>>>>>> and sets up directories like www, conf, etc.
>>>>>>
>>>>>> Then in order to build ParaView from source I did: git://
>>>>>> paraview.org/stage/ParaView.git
>>>>>>
>>>>>> followed by "git submodule update --init", as recommended at
>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup
>>>>>>
>>>>>> for Apache <2.4, which I was running until yesterday.
>>>>>>
>>>>>> See anything wrong?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 22, 2014 at 10:47 AM, Sebastien Jourdain <
>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>
>>>>>>> Just a though...
>>>>>>>
>>>>>>> Which version of ParaView did you build? git master?
>>>>>>>
>>>>>>> If so, did you use the www directory from that build or did you use
>>>>>>> the one from the binaries?
>>>>>>> There could be a version miss match in that later case.
>>>>>>>
>>>>>>> Seb
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jul 22, 2014 at 9:44 AM, Sebastien Jourdain <
>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>
>>>>>>>> Hi Dmitry,
>>>>>>>>
>>>>>>>> I've just tried to connect to your server and it seems that the
>>>>>>>> process start in about 1s. That might be correct but it seems fast to me.
>>>>>>>> Do you see any error after the +++++ log file?
>>>>>>>>
>>>>>>>> Could you edit your launcher config to add an entry for the
>>>>>>>> "pipeline" app?
>>>>>>>> The cone is just relying on VTK and I was curious if we could see
>>>>>>>> something different with our main sample app that use paraview.
>>>>>>>>
>>>>>>>> For that you just need to kill the launcher process and restart it
>>>>>>>> with the new config.
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jul 22, 2014 at 8:39 AM, Dmitry Duplyakin <
>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>
>>>>>>>>> All I see is described js error. (I see it in the Firefox'es
>>>>>>>>> Firebug console)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jul 22, 2014 at 9:33 AM, Dmitry Karpeyev <
>>>>>>>>> karpeev at mcs.anl.gov> wrote:
>>>>>>>>>
>>>>>>>>>> Is there a Python error/stack trace that comes with this?
>>>>>>>>>>  On Jul 22, 2014 9:30 AM, "Dmitry Duplyakin" <
>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Sebastien,
>>>>>>>>>>>
>>>>>>>>>>> Thanks again for your help yesterday!
>>>>>>>>>>>
>>>>>>>>>>> We have upgraded and running Apache-2.4.7 now.
>>>>>>>>>>>
>>>>>>>>>>> We are seeing a now error:
>>>>>>>>>>>  Firefox can't establish a connection to the server at ws://
>>>>>>>>>>> ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8
>>>>>>>>>>> .
>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>
>>>>>>>>>>> Last line points to code in autobahn.js
>>>>>>>>>>> ab._construct = function (url, protocols) {
>>>>>>>>>>>    if ("WebSocket" in window) {
>>>>>>>>>>>       // Chrome, MSIE, newer Firefox
>>>>>>>>>>>       if (protocols) {
>>>>>>>>>>>          *return new WebSocket(url, protocols);*
>>>>>>>>>>>       } else {
>>>>>>>>>>>          return new WebSocket(url);
>>>>>>>>>>>       }
>>>>>>>>>>>    } else if ("MozWebSocket" in window) {
>>>>>>>>>>>       // older versions of Firefox prefix the WebSocket object
>>>>>>>>>>>       if (protocols) {
>>>>>>>>>>>          return new MozWebSocket(url, protocols);
>>>>>>>>>>>       } else {
>>>>>>>>>>>          return new MozWebSocket(url);
>>>>>>>>>>>       }
>>>>>>>>>>>    } else {
>>>>>>>>>>>       return null;
>>>>>>>>>>>    }
>>>>>>>>>>> };
>>>>>>>>>>>
>>>>>>>>>>> In the meantime, session gets created, session log has a
>>>>>>>>>>> standard opening followed by many lines with "+" signs (which means it is
>>>>>>>>>>> running fine, right?), POST is successful:
>>>>>>>>>>> 130.202.2.217 - - [22/Jul/2014:14:09:48 +0000] "POST /paraview/
>>>>>>>>>>> HTTP/1.1" 200 78 "http://54.211.22.94/apps/FileViewer/"
>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>> Firefox/30.0".
>>>>>>>>>>>
>>>>>>>>>>> Its response:
>>>>>>>>>>>
>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL": "http://54.211.22.94:/paraview/", "port": 9997, "host": "localhost", "sessionURL": "ws://ec2-54-211-22-94.compute-1.amazonaws.com/proxy?sessionId=d9e328ce-11a9-11e4-b402-22000b0185a8", "id": "d9e328ce-11a9-11e4-b402-22000b0185a8"}
>>>>>>>>>>>
>>>>>>>>>>> Are possibly missing anything here?
>>>>>>>>>>>
>>>>>>>>>>> Looks like Apache log verifies that wstunnel is working:
>>>>>>>>>>>
>>>>>>>>>>> [Tue Jul 22 14:26:22.617495 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2206): [client 130.202.2.217:63449] AH00947: connected /ws?sessionId=270f885c-11ac-11e4-b402-22000b0185a8 to localhost:9999
>>>>>>>>>>> [Tue Jul 22 14:26:22.617574 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2610): AH00962: WS: connection complete to 127.0.0.1:9999 (localhost)
>>>>>>>>>>> [Tue Jul 22 14:26:22.619784 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>>>> [Tue Jul 22 14:26:22.619806 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>>>> [Tue Jul 22 14:26:22.619905 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>>>> [Tue Jul 22 14:26:22.619925 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>>>> [Tue Jul 22 14:26:22.619943 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(253): [client 130.202.2.217:63449] AH02445: woke from poll(), i=1
>>>>>>>>>>> [Tue Jul 22 14:26:22.619953 2014] [proxy_wstunnel:debug] [pid 7236:tid 140393354098432] mod_proxy_wstunnel.c(262): [client 130.202.2.217:63449] AH02446: sock was readable
>>>>>>>>>>> [Tue Jul 22 14:26:22.619964 2014] [proxy:debug] [pid 7236:tid 140393354098432] proxy_util.c(2035): AH00943: WS: has released connection for (*)
>>>>>>>>>>>
>>>>>>>>>>> Any thoughts on what might be causing this problem?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jul 21, 2014 at 4:06 PM, Sebastien Jourdain <
>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Should work... I guess this documentation will always be out of
>>>>>>>>>>>> date. ;-)
>>>>>>>>>>>>
>>>>>>>>>>>> But the good news is that modern system have the right version
>>>>>>>>>>>> of Apache, so no fancy build are needed anymore...
>>>>>>>>>>>>
>>>>>>>>>>>> Seb
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:02 PM, Dmitry Duplyakin <
>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>  Trying to follow instructions from
>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2 now.
>>>>>>>>>>>>> It looks like those urls used with wget are broken.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Found a replacement for httpd:
>>>>>>>>>>>>>
>>>>>>>>>>>>> wget http://archive.apache.org/dist/httpd/httpd-2.4.7.tar.gz
>>>>>>>>>>>>> -O httpd.tgz
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can't seem to find 1.5.0 version. *Will 1.5.1 work?* If so,
>>>>>>>>>>>>> here is a working command:
>>>>>>>>>>>>>
>>>>>>>>>>>>> wget http://apache.petsads.us/apr/apr-1.5.1.tar.gz -O apr.tgz
>>>>>>>>>>>>>
>>>>>>>>>>>>> The last one works fine:
>>>>>>>>>>>>>
>>>>>>>>>>>>> wget http://apache.petsads.us/apr/apr-util-1.5.3.tar.gz -O
>>>>>>>>>>>>> apr-util.tgz
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:36 PM, Dmitry Duplyakin <
>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Got it. Rebuilding Apache now.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:29 PM, Sebastien Jourdain <
>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> You must have Apache 2.4.7+
>>>>>>>>>>>>>>> Their is a fix in that version which allow mod_rewrite to
>>>>>>>>>>>>>>> work on web socket protocol instead of just http.
>>>>>>>>>>>>>>> You can look at the apache section in here
>>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/paraviewweb_on_aws_ec2
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:25 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We are running Apache/2.2.22 with loaded
>>>>>>>>>>>>>>>> proxy_wstunnel_module (that we had to build from source).
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> From Apache error log (with debug):
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //localhost:8080/paraview/
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(1506):
>>>>>>>>>>>>>>>> [client 130.202.2.217] proxy: http: found worker
>>>>>>>>>>>>>>>> http://localhost:8080/paraview for
>>>>>>>>>>>>>>>> http://localhost:8080/paraview/, referer:
>>>>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy.c(1020):
>>>>>>>>>>>>>>>> Running scheme http handler (attempt 0)
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>>>>> proxy: HTTP: serving URL http://localhost:8080/paraview/
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2011):
>>>>>>>>>>>>>>>> proxy: HTTP: has acquired connection for (localhost)
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2067):
>>>>>>>>>>>>>>>> proxy: connecting http://localhost:8080/paraview/ to
>>>>>>>>>>>>>>>> localhost:8080
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:13 2014] [debug] proxy_util.c(2193):
>>>>>>>>>>>>>>>> proxy: connected /paraview/ to localhost:8080
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_deflate.c(615):
>>>>>>>>>>>>>>>> [client 130.202.2.217] Zlib: Compressed 242 to 155 : URL /paraview/,
>>>>>>>>>>>>>>>> referer: http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029):
>>>>>>>>>>>>>>>> proxy: HTTP: has released connection for (localhost)
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(56):
>>>>>>>>>>>>>>>> proxy: HTTP: canonicalising URL //
>>>>>>>>>>>>>>>> 54.211.22.94/ws://localhost:9998/ws
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(1525):
>>>>>>>>>>>>>>>> [client 130.202.2.217] proxy: *: found reverse proxy worker for
>>>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy.c(1020):
>>>>>>>>>>>>>>>> Running scheme http handler (attempt 0)
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1973):
>>>>>>>>>>>>>>>> proxy: HTTP: serving URL
>>>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2011):
>>>>>>>>>>>>>>>> proxy: HTTP: has acquired connection for (*)
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2067):
>>>>>>>>>>>>>>>> proxy: connecting
>>>>>>>>>>>>>>>> http://54.211.22.94/ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8
>>>>>>>>>>>>>>>> to 54.211.22.94:80
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2193):
>>>>>>>>>>>>>>>> proxy: connected
>>>>>>>>>>>>>>>> /ws://localhost:9998/ws?sessionId=6bf080cc-1114-11e4-b402-22000b0185a8 to
>>>>>>>>>>>>>>>> 54.211.22.94:80
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2444):
>>>>>>>>>>>>>>>> proxy: HTTP: fam 2 socket created to connect to *
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2576):
>>>>>>>>>>>>>>>> proxy: HTTP: connection complete to 54.211.22.94:80
>>>>>>>>>>>>>>>> (54.211.22.94)
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [error] [client 54.211.22.94]
>>>>>>>>>>>>>>>> File does not exist: /pv/www/ws:
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1743):
>>>>>>>>>>>>>>>> proxy: start body send
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] mod_proxy_http.c(1847):
>>>>>>>>>>>>>>>> proxy: end body send
>>>>>>>>>>>>>>>> [Mon Jul 21 20:20:14 2014] [debug] proxy_util.c(2029):
>>>>>>>>>>>>>>>> proxy: HTTP: has released connection for (*)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> POST took ~1 second. Timestamps for POST and the following
>>>>>>>>>>>>>>>> GET: 21/Jul/2014:20:23:02 and 21/Jul/2014:20:23:03
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 3:10 PM, Sebastien Jourdain <
>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Which version of Apache are you using? Do you have the
>>>>>>>>>>>>>>>>> ws_tunnelling (<= wrong name but something like that) module enabled?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> You may be able to check the system log that apache
>>>>>>>>>>>>>>>>> generate to see what went wrong.
>>>>>>>>>>>>>>>>> Do you know how much time the POST request took?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 1:59 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Continue troubleshooting...
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Now we get this in response to POST:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> {"updir": "/Home", "sessionManagerURL":
>>>>>>>>>>>>>>>>>> "http://54.211.22.94:/paraview/", "port": 9999, "host":
>>>>>>>>>>>>>>>>>> "localhost", "sessionURL": "ws://
>>>>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=369f8648-110f-11e4-b402-22000b0185a8",
>>>>>>>>>>>>>>>>>> "id": "369f8648-110f-11e4-b402-22000b0185a8"}
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Looks right to me. Then, after that POST, it does GETs
>>>>>>>>>>>>>>>>>> that do not look right:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 54.211.22.94 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>>>>> */ws://localhost:9999/ws?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8*
>>>>>>>>>>>>>>>>>> HTTP/1.1" 404 509 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
>>>>>>>>>>>>>>>>>> rv:30.0) Gecko/20100101 Firefox/30.0"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 130.202.2.217 - - [21/Jul/2014:19:54:29 +0000] "GET
>>>>>>>>>>>>>>>>>> /proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8 HTTP/1.1" 404 509 "-"
>>>>>>>>>>>>>>>>>> "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101
>>>>>>>>>>>>>>>>>> Firefox/30.0"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> And the message:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Firefox can't establish a connection to the server at
>>>>>>>>>>>>>>>>>> ws://
>>>>>>>>>>>>>>>>>> 54.211.22.94/proxy?sessionId=d32a4d8a-1110-11e4-b402-22000b0185a8.
>>>>>>>>>>>>>>>>>> return new WebSocket(url, protocols);
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> What can possibly cause this? Again, complete apache and
>>>>>>>>>>>>>>>>>> launcher configs are in the previous email.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 2:07 PM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> This helped tremendously!
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Both "-f" and "${host}" now make a lot more sense.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> POST works fine now and we can see the Rewrite rule in
>>>>>>>>>>>>>>>>>>> action. Something there still needs attention and we are investigating
>>>>>>>>>>>>>>>>>>> further.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks for you patience and all the help that allows us
>>>>>>>>>>>>>>>>>>> to move forward.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 12:59 PM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> you may still have a typo
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> => "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> ${host} should have been replaced with a static string
>>>>>>>>>>>>>>>>>>>> that match the host that the web browser is using to reach apache.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Moreover, I forgot to mention that you need to add "-f"
>>>>>>>>>>>>>>>>>>>> in your set of arguments. That will force some output generation to fill
>>>>>>>>>>>>>>>>>>>> some buffer which will allow the launcher to detect when the server is
>>>>>>>>>>>>>>>>>>>> actually ready.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I've noticed that the documentation is missing them.
>>>>>>>>>>>>>>>>>>>> Don't know why... Will update it at some point.
>>>>>>>>>>>>>>>>>>>> Although this page show that option:
>>>>>>>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/py_launcher
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> And the value for "timeout" should be way bigger than
>>>>>>>>>>>>>>>>>>>> 5. Like 25 maybe.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:58 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Thanks for this detailed description! The process is
>>>>>>>>>>>>>>>>>>>>> starting to make sense and we can communicate more efficiently about our
>>>>>>>>>>>>>>>>>>>>> configuration and problems.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Here is our complete launch.json (with the right
>>>>>>>>>>>>>>>>>>>>> sessionURL for a config with Apache, according to your email):
>>>>>>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>>>>>>> "configuration": {
>>>>>>>>>>>>>>>>>>>>>   "content": "/pv/www",
>>>>>>>>>>>>>>>>>>>>>   "log_dir": "/pv/logs",
>>>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>>>   "endpoint": "paraview",
>>>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>>   "timeout": 5,
>>>>>>>>>>>>>>>>>>>>>   "upload_dir": "/pv/data",
>>>>>>>>>>>>>>>>>>>>>   "fields": ["file", "host", "port", "updir"],
>>>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>>>   "proxy_file": "/pv/conf/proxy.conf"},
>>>>>>>>>>>>>>>>>>>>> "apps": {
>>>>>>>>>>>>>>>>>>>>>   "data_prober": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_data_prober.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>>>   "pipeline": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_visualizer.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>>>   "loader": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>> "${python_path}/paraview/web/pv_web_file_loader.py", "--port", "${port}",
>>>>>>>>>>>>>>>>>>>>> "--data-dir", "${data}"], "ready_line" : "Starting factory"},
>>>>>>>>>>>>>>>>>>>>>    "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py", "--port",
>>>>>>>>>>>>>>>>>>>>> "${port}"], "ready_line" : "Starting factory"}},
>>>>>>>>>>>>>>>>>>>>> "properties": {
>>>>>>>>>>>>>>>>>>>>>   "python_path":
>>>>>>>>>>>>>>>>>>>>> "/pv/paraview/lib/paraview-4.1/site-packages/",
>>>>>>>>>>>>>>>>>>>>>   "data": "/pv/data",
>>>>>>>>>>>>>>>>>>>>>   "python_exec": "/pv/paraview/bin/pvpython"},
>>>>>>>>>>>>>>>>>>>>>  "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>>>> "sessionData": {"updir": "/Home"}
>>>>>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Apache host file:
>>>>>>>>>>>>>>>>>>>>> <VirtualHost *:80>
>>>>>>>>>>>>>>>>>>>>>         ServerAdmin webmaster at localhost
>>>>>>>>>>>>>>>>>>>>>         DocumentRoot /pv/www
>>>>>>>>>>>>>>>>>>>>>         <Directory /pv/www/>
>>>>>>>>>>>>>>>>>>>>>                 Options Indexes FollowSymLinks
>>>>>>>>>>>>>>>>>>>>> MultiViews
>>>>>>>>>>>>>>>>>>>>>                 AllowOverride None
>>>>>>>>>>>>>>>>>>>>>                 Order allow,deny
>>>>>>>>>>>>>>>>>>>>>                 allow from all
>>>>>>>>>>>>>>>>>>>>>         </Directory>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>         ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>         RewriteEngine On
>>>>>>>>>>>>>>>>>>>>>         RewriteMap session-to-port
>>>>>>>>>>>>>>>>>>>>> txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>>         RewriteCond %{QUERY_STRING}
>>>>>>>>>>>>>>>>>>>>> ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>>         RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>         RewriteLog "/var/log/apache2/rewrite.log"
>>>>>>>>>>>>>>>>>>>>>         RewriteLogLevel 3
>>>>>>>>>>>>>>>>>>>>>         ErrorLog ${APACHE_LOG_DIR}/error.log
>>>>>>>>>>>>>>>>>>>>>         LogLevel debug
>>>>>>>>>>>>>>>>>>>>>         CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>>>>>>>>>>>>>>>>>>> </VirtualHost>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Now when we access http://<PVW server>/apps/Cone/ in
>>>>>>>>>>>>>>>>>>>>> the browser,
>>>>>>>>>>>>>>>>>>>>> it does POST {"sessionManagerURL":"http://<CORRECT IP
>>>>>>>>>>>>>>>>>>>>> FOR PVW server>:/paraview/","application":"cone"}. Then Launcher starts a
>>>>>>>>>>>>>>>>>>>>> process listening to a port from the range (e.g. 9999). We can see that
>>>>>>>>>>>>>>>>>>>>> process:
>>>>>>>>>>>>>>>>>>>>> ps auwx | grep cone
>>>>>>>>>>>>>>>>>>>>> root     27943  2.3  1.8 1015600 137664 pts/2  Sl+
>>>>>>>>>>>>>>>>>>>>>  16:32   0:00 /pv/paraview/lib/paraview-4.1/pvpython
>>>>>>>>>>>>>>>>>>>>> /pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py --port 9999
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> After that we get a session timeout and this response: "Session
>>>>>>>>>>>>>>>>>>>>> did not start before timeout expired. Check session logs."
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Any further advice?
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 10:02 AM, Sebastien Jourdain <
>>>>>>>>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> First of all you need to understand the role of
>>>>>>>>>>>>>>>>>>>>>> apache here in order to see how the configuration should be.
>>>>>>>>>>>>>>>>>>>>>> As you may know, you can use ParaViewWeb without
>>>>>>>>>>>>>>>>>>>>>> Apache, but such setup is not meant for production.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> The list below is what you get when you add Apache:
>>>>>>>>>>>>>>>>>>>>>> - Apache can be use to serve the static content
>>>>>>>>>>>>>>>>>>>>>> (html, js, png, css...)
>>>>>>>>>>>>>>>>>>>>>> - Apache provide a single entry point host + port.
>>>>>>>>>>>>>>>>>>>>>> This prevent cross-domain issue or firewall limitation.
>>>>>>>>>>>>>>>>>>>>>> - Apache will relay the WebSocket communication to
>>>>>>>>>>>>>>>>>>>>>> the proper ParaViewWeb instance on the backend based on a session ID. This
>>>>>>>>>>>>>>>>>>>>>> mean that the ParaViewWeb process DOES NOT need to be on the same machine
>>>>>>>>>>>>>>>>>>>>>> as the Apache Web Server.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Then you need to understand how the launcher works
>>>>>>>>>>>>>>>>>>>>>> and its role.
>>>>>>>>>>>>>>>>>>>>>> In ParaViewWeb a launcher is used to start a new
>>>>>>>>>>>>>>>>>>>>>> visualization process for a given user. This simply mean running a command
>>>>>>>>>>>>>>>>>>>>>> line with some dynamic parameters like the port number on which this
>>>>>>>>>>>>>>>>>>>>>> specific instance should listen.
>>>>>>>>>>>>>>>>>>>>>> So when a user connect to the system and request a
>>>>>>>>>>>>>>>>>>>>>> new visualization session, it is the responsibility of the launcher to
>>>>>>>>>>>>>>>>>>>>>> start the process and let the client know on which WebSocket URL it should
>>>>>>>>>>>>>>>>>>>>>> connect to in order to reach the requested visualization session.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> In a setup that DOES NOT contain Apache, we can not
>>>>>>>>>>>>>>>>>>>>>> use the same port as the main server (the process would not start). Hence,
>>>>>>>>>>>>>>>>>>>>>> we start it with some port and we let the user know that it should connect
>>>>>>>>>>>>>>>>>>>>>> to "ws://{host}:{port}/ws" where host and port get replaced with the set
>>>>>>>>>>>>>>>>>>>>>> that was used to create the process.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> See section "resources" in launcher configuration.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> BUT with Apache that is different, now we have a
>>>>>>>>>>>>>>>>>>>>>> process which is meant to relay the communication to the backend using the
>>>>>>>>>>>>>>>>>>>>>> port and host that Apache is using. So the launcher should let the client
>>>>>>>>>>>>>>>>>>>>>> know what URL they should use so Apache could handle it and forward it to
>>>>>>>>>>>>>>>>>>>>>> the backend. Hence the ws://{apache_host}/proxy?sessionId=${id}.
>>>>>>>>>>>>>>>>>>>>>> In the same time to keep track on which host/port a
>>>>>>>>>>>>>>>>>>>>>> process is running the launcher generate a text file with the proper
>>>>>>>>>>>>>>>>>>>>>> mapping.
>>>>>>>>>>>>>>>>>>>>>> That mapping file is then used inside Apache to
>>>>>>>>>>>>>>>>>>>>>> figure out how it should establish the connection to the backend.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> This should help you understand how to fix your
>>>>>>>>>>>>>>>>>>>>>> configuration.
>>>>>>>>>>>>>>>>>>>>>> Moreover, here is the remaining set of questions:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> > can we specifically log and debug Rewrite rule
>>>>>>>>>>>>>>>>>>>>>> actions?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here...
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> > do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Don't know, Google will be your friend here as well
>>>>>>>>>>>>>>>>>>>>>> as the documentation on how to setup ParaViewWeb on Ubuntu 14LTS.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> > what particular modules in Apache are required?
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Read the documentation, the list is minimum and
>>>>>>>>>>>>>>>>>>>>>> provided in it.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> > in launch.json there are two particular lines
>>>>>>>>>>>>>>>>>>>>>> host/resources:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> So the "host" is to select the proper network card
>>>>>>>>>>>>>>>>>>>>>> when you have several for the actual launcher server.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Then the resources are use for process management and
>>>>>>>>>>>>>>>>>>>>>> URL generation for the client. Which mean, what name should be used by
>>>>>>>>>>>>>>>>>>>>>> Apache to connect to the machine that actually run a ParaViewWeb process.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Mon, Jul 21, 2014 at 8:01 AM, Dmitry Duplyakin <
>>>>>>>>>>>>>>>>>>>>>> duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Thank you very much, Sebastien!
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Launcher side:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> "sessionURL": "ws://YOUR_HOST_NAME_TO_REPLACE(the one used to connect to apache)/proxy?sessionId=${id}",
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> "proxy_file": "/data/proxy.txt"
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> This is exactly what we have in our launcher:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>   "sessionURL": "ws://${host}:${port}/ws",
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>   "host": "localhost",
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>   "port": 8080,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Your sessionURL looks different. Do you actually use
>>>>>>>>>>>>>>>>>>>>>>> "proxy?sessionId=" there? Ours came directly from
>>>>>>>>>>>>>>>>>>>>>>> the script you've suggested earlier:
>>>>>>>>>>>>>>>>>>>>>>> http://www.paraview.org/gitweb?p=ParaViewSuperbuild.git;a=blob_plain;f=Scripts/pvw-setup.py;hb=HEAD
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Apache side
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> RewriteMap  session-to-port  txt:/data/proxy.txt
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> In Apache we have:
>>>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>>>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Then when a session start you can check the content
>>>>>>>>>>>>>>>>>>>>>>>> of that /data/proxy.txt and that should one line by running session with
>>>>>>>>>>>>>>>>>>>>>>>> {sessionId} localhost:yyyyy
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Verified that those entires are added to the file
>>>>>>>>>>>>>>>>>>>>>>> and have the right format.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On the other hand you forgot that line in the
>>>>>>>>>>>>>>>>>>>>>>>> config of your cone app: "ready_line" : "Starting
>>>>>>>>>>>>>>>>>>>>>>>> factory"
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>  Thanks! Added it and now the app looks like this:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"], "ready_line" : "Starting
>>>>>>>>>>>>>>>>>>>>>>> factory"}},
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> You can check is any pvpython process is running,
>>>>>>>>>>>>>>>>>>>>>>>> on which port, see if that match in the proxy file (/data/proxy.txt) and
>>>>>>>>>>>>>>>>>>>>>>>> also looking at the log directory with the output of the pvpython process.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> A common error could also be that the apache does
>>>>>>>>>>>>>>>>>>>>>>>> not have the right to read the /data/proxy.txt file or that the launcher is
>>>>>>>>>>>>>>>>>>>>>>>> not able to write it.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Verified that launcher can write it and that entries
>>>>>>>>>>>>>>>>>>>>>>> are added.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> These are the rest of our questions (we need to sort
>>>>>>>>>>>>>>>>>>>>>>> these out because they have caused some confusion and we want to clear
>>>>>>>>>>>>>>>>>>>>>>> things up and do not come back to these issues anymore):
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> - can we specifically log and debug Rewrite rule
>>>>>>>>>>>>>>>>>>>>>>> actions?
>>>>>>>>>>>>>>>>>>>>>>> - do we actually need ProxyPassReverse in Apache?
>>>>>>>>>>>>>>>>>>>>>>> - what particular modules in Apache are required? So
>>>>>>>>>>>>>>>>>>>>>>> far we have: proxy_module, proxy_http_module, and rewrite_module. We are
>>>>>>>>>>>>>>>>>>>>>>> unsure whether we need proxy_wstunnel_module or not.
>>>>>>>>>>>>>>>>>>>>>>> - in launch.json there are two particular lines:
>>>>>>>>>>>>>>>>>>>>>>> "host": "localhost",
>>>>>>>>>>>>>>>>>>>>>>> "resources": [{"port_range": [9901, 9999], "host":
>>>>>>>>>>>>>>>>>>>>>>> "localhost"}],
>>>>>>>>>>>>>>>>>>>>>>> where we have some confusion about using "localhost"
>>>>>>>>>>>>>>>>>>>>>>> vs. "0.0.0.0". What exactly should we use in either case?
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Appreciate your help!
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Good luck,
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Sun, Jul 20, 2014 at 10:12 AM, Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>>>>>>> <duplyakin at uchicago.edu> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Hi all,
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> My name is Dmitry Duplyakin. I am a PhD student
>>>>>>>>>>>>>>>>>>>>>>>>> helping to build a ParaViewWeb system at University of Chicago.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> We are building ParaView 4.1.0 (with OSMesa) on
>>>>>>>>>>>>>>>>>>>>>>>>> Amazon EC2 Ubuntu 12.04 instances.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> We have verified that PV builds without errors and
>>>>>>>>>>>>>>>>>>>>>>>>> that PVW launcher is functioning (new entries are added to the proxy file,
>>>>>>>>>>>>>>>>>>>>>>>>> vis sessions are created and are listening to ports in the specified range,
>>>>>>>>>>>>>>>>>>>>>>>>> etc.)
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> We are trying to visualize a simple cone:
>>>>>>>>>>>>>>>>>>>>>>>>> (added app in launch.json)
>>>>>>>>>>>>>>>>>>>>>>>>> "cone": {"cmd": ["${python_exec}",
>>>>>>>>>>>>>>>>>>>>>>>>> "/pv/src/VTK/Web/Applications/Cone/server/vtk_web_cone.py",
>>>>>>>>>>>>>>>>>>>>>>>>> "--port", "${port}"]}},
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> We have verified that vtk_web_cone.py actually
>>>>>>>>>>>>>>>>>>>>>>>>> gets called. In order to test it, we used /pv/www/apps/TestApp/index.html
>>>>>>>>>>>>>>>>>>>>>>>>> as a template and created /pv/www/apps/Cone/index.html where we have:
>>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>>>   var config = {
>>>>>>>>>>>>>>>>>>>>>>>>>     sessionManagerURL:
>>>>>>>>>>>>>>>>>>>>>>>>> vtkWeb.properties.sessionManagerURL,
>>>>>>>>>>>>>>>>>>>>>>>>>     application: "cone"
>>>>>>>>>>>>>>>>>>>>>>>>>   };
>>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Now when we access this app via a browser at:
>>>>>>>>>>>>>>>>>>>>>>>>> http://<hostname>/apps/Cone/ we either get a
>>>>>>>>>>>>>>>>>>>>>>>>> timeout or "connection can't be established" message.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> In the apache error log we see:
>>>>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] proxy: Error reading from remote server returned by
>>>>>>>>>>>>>>>>>>>>>>>>> /paraview/, referer:
>>>>>>>>>>>>>>>>>>>>>>>>> http://54.211.22.94/apps/Cone/
>>>>>>>>>>>>>>>>>>>>>>>>> [Sun Jul 20 16:04:15 2014] [error] [client
>>>>>>>>>>>>>>>>>>>>>>>>> 128.135.188.231] File does not exist: /pv/www/ws
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> It appears that it has do to with Apache
>>>>>>>>>>>>>>>>>>>>>>>>> configuration, where we have:
>>>>>>>>>>>>>>>>>>>>>>>>> ProxyPass        /paraview
>>>>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>>>>> ProxyPassReverse /paraview
>>>>>>>>>>>>>>>>>>>>>>>>> http://localhost:8080/paraview
>>>>>>>>>>>>>>>>>>>>>>>>> RewriteEngine On
>>>>>>>>>>>>>>>>>>>>>>>>> RewriteMap session-to-port txt:/pv/conf/proxy.conf
>>>>>>>>>>>>>>>>>>>>>>>>> RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$
>>>>>>>>>>>>>>>>>>>>>>>>> [NC]
>>>>>>>>>>>>>>>>>>>>>>>>> RewriteRule    ^/proxy.*$
>>>>>>>>>>>>>>>>>>>>>>>>>  ws://${session-to-port:%1}/ws  [P]
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Do these Rewrite commands look right? How can
>>>>>>>>>>>>>>>>>>>>>>>>> their actions be logged and verified?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Do we actually need ProxyPassReverse here?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Is it possible that we are missing a module or
>>>>>>>>>>>>>>>>>>>>>>>>> some additional configuration in Apache?
>>>>>>>>>>>>>>>>>>>>>>>>> # apachectl -t -D DUMP_MODULES
>>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>>>  proxy_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>>>  proxy_http_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>>>  proxy_wstunnel_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>>>  rewrite_module (shared)
>>>>>>>>>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>>>>>>>> Syntax OK
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Any debugging advice?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Your help will be much appreciated and will allow
>>>>>>>>>>>>>>>>>>>>>>>>> to move forward with our isntallation.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> -------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Dmitry Duplyakin
>>>>>>>>>>>>>>>>>>>>>>>>> PhD student, CS at University of Colorado - Boulder
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/5dd9bdb0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 26169 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/5dd9bdb0/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 154565 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140722/5dd9bdb0/attachment-0003.png>

From grothausmann.roman at mh-hannover.de  Wed Jul 23 04:38:16 2014
From: grothausmann.roman at mh-hannover.de (Dr. Roman Grothausmann)
Date: Wed, 23 Jul 2014 10:38:16 +0200
Subject: [Paraview] [vtkusers] special field-data annotation filter or
	similar functionality
In-Reply-To: <53C7A720.3070701@mh-hannover.de>
References: <53C7A720.3070701@mh-hannover.de>
Message-ID: <53CF7478.1010603@mh-hannover.de>

Dear mailing list members,


Is there already a filter as described below that I've missed to find?
If not, any recommendation how to start implementing such filter?

Kind regards
Roman


On 17/07/14 12:36, Dr. Roman Grothausmann wrote:
> Dear mailing list members,
>
>
> Is there a filter in paraview that allows one to display specific field-data
> (e.g. of points or cells) at the 3D position of the corresponding point/cell in
> such a way that the annotation is hidden if some mesh or voxel object is in
> front? Or if the objects in front have some transparency the annotations are
> only visible as much as the transparency of the objects in front dictates?
> I know about the possibility of displaying selection labels via the Find-Dialog.
> However these annotations are
> - always in front,
> - cannot be made partially transparent (as I think was possible in older
> paraview versions than 4.1.0 when vtkVectorText was used) and
> - only the active selection can be annotated, ie not multiple datasets.
>
> I found this example in which the text is not always rendered in front of the axes:
> https://github.com/Kitware/VTK/blob/master/Examples/Annotation/Python/textOrigin.py
> However it uses vtkVectorText (which is not exportable as text into e.g. SVGs
> however vtkTextActor3D is).
> I now wonder if only vtkVectorText allows being hidden by other objects or if
> some settings of vtkTextActor3D are not offered for adjustment in the Find-Dialog?
> In any case a paraview filter that would offer all 3 features mentioned above
> would be really helpful. Are there any reasons that such a filter cannot be
> implemented in paraview at the present state?
> Can such functionality be implemented in general with the current state of VTK?
>
> Any help or hints are very much appreciated
> Roman
>

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut f?r Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-9574

From linzhenhua at 163.com  Wed Jul 23 05:05:09 2014
From: linzhenhua at 163.com (linzhenhua)
Date: Wed, 23 Jul 2014 17:05:09 +0800 (CST)
Subject: [Paraview] problem on the max field value over time
Message-ID: <49cf911f.7d84.147627793f0.Coremail.linzhenhua@163.com>

Hi,

I want to plot the temporal variation of the maximum field value over time. I use two methods and the results are different in paraview.

The first method is to use the Descriptive statistics filter (Green line). The second method is to use the Find data tool(orange line). It seems to me that the latter one is more reasonable as the max field value should decrease with time. The result from the find data tool also agree with the scale data range.

Does this mean that there is a bug in Descriptive Statistics filter?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/4b1ef49c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: max.png
Type: image/png
Size: 37227 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/4b1ef49c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: max.png
Type: image/png
Size: 37227 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/4b1ef49c/attachment-0003.png>

From Patrick.Begou at legi.grenoble-inp.fr  Wed Jul 23 08:22:30 2014
From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou)
Date: Wed, 23 Jul 2014 14:22:30 +0200
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
In-Reply-To: <CADHSJjC3hO6xDt3kOJ26YXpfQqYPe=1K7S3zBF9c-3UDU41m5g@mail.gmail.com>
References: <53CE1E22.80008@legi.grenoble-inp.fr>	<CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>	<53CE7607.50503@legi.grenoble-inp.fr>
 <CADHSJjC3hO6xDt3kOJ26YXpfQqYPe=1K7S3zBF9c-3UDU41m5g@mail.gmail.com>
Message-ID: <53CFA906.5070204@legi.grenoble-inp.fr>

I've run some tests since yesterday as they are several kernel available on 
these hosts.

Running with the oldest kernel (kernel-2.6.32-358.el6.x86_64) do not show the 
problem (but this kernel has some problems and the computer freeze at logout). 
Running with all other kernels show the problem!
kernel-2.6.32-431.5.1.el6.x86_64
kernel-2.6.32-431.11.2.el6.x86_64
kernel-2.6.32-431.17.1.el6.x86_64
kernel-ml-3.15.6-1.el6.elrepo.x86_64

I think it could be more intel driver related.... and may be should I cross-post 
this en CentOS forum ?

Patrick

-- 
===================================================================
|  Equipe M.O.S.T.         |                                      |
|  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
|  LEGI                    |                                      |
|  BP 53 X                 | Tel 04 76 82 51 35                   |
|  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
===================================================================


From Patrick.Begou at legi.grenoble-inp.fr  Wed Jul 23 08:23:08 2014
From: Patrick.Begou at legi.grenoble-inp.fr (Patrick Begou)
Date: Wed, 23 Jul 2014 14:23:08 +0200
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
In-Reply-To: <CAOCDKs_2E5xxUM=6wyxsa+9jNkoG22mJeaiHBT4SSoJvLbexnQ@mail.gmail.com>
References: <53CE1E22.80008@legi.grenoble-inp.fr>
 <CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>
 <53CE7607.50503@legi.grenoble-inp.fr>
 <54624cd4-64de-4f86-98cc-7ab430a17c7a@HUB02.ad.oak.ox.ac.uk>
 <CAOCDKs_2E5xxUM=6wyxsa+9jNkoG22mJeaiHBT4SSoJvLbexnQ@mail.gmail.com>
Message-ID: <53CFA92C.3010500@legi.grenoble-inp.fr>

Unfortunatly, it is not possible to add a new graphic board on these hosts....
So I need to find a "software" solution.

Patrick

-- 
===================================================================
|  Equipe M.O.S.T.         |                                      |
|  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
|  LEGI                    |                                      |
|  BP 53 X                 | Tel 04 76 82 51 35                   |
|  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
===================================================================


From utkarsh.ayachit at kitware.com  Wed Jul 23 08:25:03 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 23 Jul 2014 08:25:03 -0400
Subject: [Paraview] Paraview 3.98, Pvserver and Intel graphic HD 4600
In-Reply-To: <53CFA92C.3010500@legi.grenoble-inp.fr>
References: <53CE1E22.80008@legi.grenoble-inp.fr>
 <CADHSJjAvsLxKFgNGb4_kUjNUPQrX4wzYEXYxz3TLLXaLvDaBxg@mail.gmail.com>
 <53CE7607.50503@legi.grenoble-inp.fr>
 <54624cd4-64de-4f86-98cc-7ab430a17c7a@HUB02.ad.oak.ox.ac.uk>
 <CAOCDKs_2E5xxUM=6wyxsa+9jNkoG22mJeaiHBT4SSoJvLbexnQ@mail.gmail.com>
 <53CFA92C.3010500@legi.grenoble-inp.fr>
Message-ID: <CADHSJjBeec9p1Onqgvy=GCW2QB1ppx43nnctUGg49N3-hmOrsA@mail.gmail.com>

Maybe try using mesa3d instead?


On Wed, Jul 23, 2014 at 8:23 AM, Patrick Begou <
Patrick.Begou at legi.grenoble-inp.fr> wrote:

> Unfortunatly, it is not possible to add a new graphic board on these
> hosts....
> So I need to find a "software" solution.
>
>
> Patrick
>
> --
> ===================================================================
> |  Equipe M.O.S.T.         |                                      |
> |  Patrick BEGOU           | mailto:Patrick.Begou at grenoble-inp.fr |
> |  LEGI                    |                                      |
> |  BP 53 X                 | Tel 04 76 82 51 35                   |
> |  38041 GRENOBLE CEDEX    | Fax 04 76 82 52 71                   |
> ===================================================================
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/8c6e893b/attachment.html>

From mexas at bris.ac.uk  Wed Jul 23 09:50:03 2014
From: mexas at bris.ac.uk (Anton Shterenlikht)
Date: Wed, 23 Jul 2014 14:50:03 +0100 (BST)
Subject: [Paraview] vtkPVCameraCueManipulator (0x8353f8e60): Too few
	keyframes to animate.
Message-ID: <201407231350.s6NDo3wV088293@mech-cluster241.men.bris.ac.uk>

I made an animation interactively in PV 4.1.0.
I checked that the animation is fine with mplayer.
I recorded my steps with Tools -> Start Trace.
When I try to run the resulting python script
with pvbatch I get this error:

$ pvbatch --use-offscreen-rendering zpart1.py
ERROR: In /wrkdirs/usr/ports/science/paraview/work/ParaView-v4.1.0/ParaViewCore/ServerManager/Default/vtkPVCameraCueManipulator.cxx, line 52
vtkPVCameraCueManipulator (0x8353f8e60): Too few keyframes to animate.

The python script:


# user defined variables, no identation allowed, start at col 1

infile  = "z.xdmf"  # name of XDMF file
picfile = "z.png"   # image output file
vidfile = "z.ogv"   # animation output file
trlo    = -4        # lower threshold
trhi    = 0         # upper threshold

# end of user variables
 
try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

# load XDMF file
z_xdmf = XDMFReader( FileName=infile )

AnimationScene1 = GetAnimationScene()
AnimationScene1.EndTime = 10.0
AnimationScene1.PlayMode = 'Snap To TimeSteps'

z_xdmf.Sets = []
z_xdmf.Grids = ['T0', 'T30', 'T60', 'T90', 'T120', 'T150', 'T180', 'T210', 'T240', 'T270', 'T300']
z_xdmf.PointArrays = ['crack']

RenderView1 = GetRenderView()
RenderView1.CenterOfRotation = [127.5, 127.5, 95.5]

DataRepresentation1 = Show()
DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
DataRepresentation1.Slice = 95
DataRepresentation1.SelectionPointFieldDataArrayName = 'crack'
DataRepresentation1.ScalarOpacityUnitDistance = 1.762150384296635
DataRepresentation1.Representation = 'Outline'
DataRepresentation1.ScaleFactor = 25.5

RenderView1.CameraPosition = [127.5, 127.5, 883.8540784668097]
RenderView1.CameraFocalPoint = [127.5, 127.5, 95.5]
RenderView1.CameraClippingRange = [590.4255376821416, 1039.4068896438118]
RenderView1.CameraParallelScale = 204.0410497914574

Threshold1 = Threshold()
Threshold1.Scalars = ['POINTS', 'crack']
Threshold1.AllScalars = 0
Threshold1.ThresholdRange = [ trlo, trhi ]

DataRepresentation2 = Show()
DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
DataRepresentation2.SelectionPointFieldDataArrayName = 'crack'
DataRepresentation2.ColorArrayName = ('POINT_DATA', 'crack')
DataRepresentation2.ScalarOpacityUnitDistance = 1.88988157484231
DataRepresentation2.ScaleFactor = 0.2

a1_crack_PVLookupTable = GetLookupTableForArray( "crack", 1, RGBPoints=[-3.0, 0.23, 0.299, 0.754, 1073741822.0, 0.865, 0.865, 0.865, 2147483647.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', NanColor=[0.25, 0.0, 0.0], ColorSpace='Diverging', ScalarRangeInitialized=1.0 )

a1_crack_PiecewiseFunction = CreatePiecewiseFunction( Points=[-3.0, 0.0, 0.5, 0.0, 2147483647.0, 1.0, 0.5, 0.0] )

DataRepresentation2.ScalarOpacityFunction = a1_crack_PiecewiseFunction
DataRepresentation2.LookupTable = a1_crack_PVLookupTable

a1_crack_PVLookupTable.NanColor = [1.0, 1.0, 0.0]
a1_crack_PVLookupTable.RGBPoints = [-3.0, 1.0, 1.0, 1.0, 365072217.5, 0.0, 0.0, 1.0, 730144438.0, 0.0, 1.0, 1.0, 1073741822.0, 0.0, 1.0, 0.0, 1438814042.5, 1.0, 1.0, 0.0, 1803886263.0, 1.0, 0.0, 0.0, 2147483647.0, 0.878431, 0.0, 1.0]
a1_crack_PVLookupTable.ScalarOpacityFunction = a1_crack_PiecewiseFunction
a1_crack_PVLookupTable.ColorSpace = 'RGB'

RenderView1.CameraPosition = [127.49999999999966, 127.5, 883.8540000000002]
RenderView1.CameraClippingRange = [590.4254600000002, 1039.4068100000004]

AnimationScene1.AnimationTime = 10.0
AnimationScene1.NumberOfFrames = 100
AnimationScene1.PlayMode = 'Sequence'

CameraAnimationCue1 = GetCameraTrack()
CameraAnimationCue1.AnimatedProxy = RenderView1
CameraAnimationCue1.Mode = 'Path-based'

TimeAnimationCue1 = GetTimeTrack()
TimeAnimationCue1.Enabled = 0

KeyFrame3658 = CameraKeyFrame( FocalPathPoints=[127.5, 127.5, 95.5], FocalPoint=[127.5, 127.5, 95.5], PositionPathPoints=[127.5, 127.5, 883.854, 740.1661272984488, 127.5, 591.6272475657036, 898.6265736288988, 127.5, -68.40801310294381, 485.4052264316708, 127.5, -606.9285573699966, -193.1524595153794, 127.5, -624.6972157143753, -633.9914888582924, 127.5, -108.54102948275286, -510.2917835834677, 127.5, 558.8828547857805], ClosedPositionPath=1, ParallelScale=204.0410497914574, Position=[127.5, 127.5, 883.8540784668097] )

KeyFrame3659 = CameraKeyFrame( ParallelScale=204.0410497914574, Position=[127.5, 127.5, 883.8540784668097], KeyTime=1.0, FocalPoint=[127.5, 127.5, 95.5] )

WriteAnimation( vidfile , Magnification=1, Quality=2, FrameRate=6.000000)
CameraAnimationCue1.KeyFrames = [ KeyFrame3658, KeyFrame3659 ]

Render()


Please advise

Many thanks

Anton


From utkarsh.ayachit at kitware.com  Wed Jul 23 09:54:21 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 23 Jul 2014 09:54:21 -0400
Subject: [Paraview] vtkPVCameraCueManipulator (0x8353f8e60): Too few
 keyframes to animate.
In-Reply-To: <201407231350.s6NDo3wV088293@mech-cluster241.men.bris.ac.uk>
References: <201407231350.s6NDo3wV088293@mech-cluster241.men.bris.ac.uk>
Message-ID: <CADHSJjAo36GrU23GgN+Wr-KuukAe1zm++X4mKjyzxegPfhhFCA@mail.gmail.com>

Can you switch the lines "WriteAnimation" and "CameraAnimationCue.KeyFrame
=...". The WrieAnimation should happen after that. Seems like a bug in the
tracing code. The tracing code is being revamped. Although animation has
been skipped in this revamp, it's on my todo list for subsequent release.

Utkarsh


On Wed, Jul 23, 2014 at 9:50 AM, Anton Shterenlikht <mexas at bris.ac.uk>
wrote:

> I made an animation interactively in PV 4.1.0.
> I checked that the animation is fine with mplayer.
> I recorded my steps with Tools -> Start Trace.
> When I try to run the resulting python script
> with pvbatch I get this error:
>
> $ pvbatch --use-offscreen-rendering zpart1.py
> ERROR: In
> /wrkdirs/usr/ports/science/paraview/work/ParaView-v4.1.0/ParaViewCore/ServerManager/Default/vtkPVCameraCueManipulator.cxx,
> line 52
> vtkPVCameraCueManipulator (0x8353f8e60): Too few keyframes to animate.
>
> The python script:
>
>
> # user defined variables, no identation allowed, start at col 1
>
> infile  = "z.xdmf"  # name of XDMF file
> picfile = "z.png"   # image output file
> vidfile = "z.ogv"   # animation output file
> trlo    = -4        # lower threshold
> trhi    = 0         # upper threshold
>
> # end of user variables
>
> try: paraview.simple
> except: from paraview.simple import *
> paraview.simple._DisableFirstRenderCameraReset()
>
> # load XDMF file
> z_xdmf = XDMFReader( FileName=infile )
>
> AnimationScene1 = GetAnimationScene()
> AnimationScene1.EndTime = 10.0
> AnimationScene1.PlayMode = 'Snap To TimeSteps'
>
> z_xdmf.Sets = []
> z_xdmf.Grids = ['T0', 'T30', 'T60', 'T90', 'T120', 'T150', 'T180', 'T210',
> 'T240', 'T270', 'T300']
> z_xdmf.PointArrays = ['crack']
>
> RenderView1 = GetRenderView()
> RenderView1.CenterOfRotation = [127.5, 127.5, 95.5]
>
> DataRepresentation1 = Show()
> DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
> DataRepresentation1.Slice = 95
> DataRepresentation1.SelectionPointFieldDataArrayName = 'crack'
> DataRepresentation1.ScalarOpacityUnitDistance = 1.762150384296635
> DataRepresentation1.Representation = 'Outline'
> DataRepresentation1.ScaleFactor = 25.5
>
> RenderView1.CameraPosition = [127.5, 127.5, 883.8540784668097]
> RenderView1.CameraFocalPoint = [127.5, 127.5, 95.5]
> RenderView1.CameraClippingRange = [590.4255376821416, 1039.4068896438118]
> RenderView1.CameraParallelScale = 204.0410497914574
>
> Threshold1 = Threshold()
> Threshold1.Scalars = ['POINTS', 'crack']
> Threshold1.AllScalars = 0
> Threshold1.ThresholdRange = [ trlo, trhi ]
>
> DataRepresentation2 = Show()
> DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
> DataRepresentation2.SelectionPointFieldDataArrayName = 'crack'
> DataRepresentation2.ColorArrayName = ('POINT_DATA', 'crack')
> DataRepresentation2.ScalarOpacityUnitDistance = 1.88988157484231
> DataRepresentation2.ScaleFactor = 0.2
>
> a1_crack_PVLookupTable = GetLookupTableForArray( "crack", 1,
> RGBPoints=[-3.0, 0.23, 0.299, 0.754, 1073741822.0, 0.865, 0.865, 0.865,
> 2147483647.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', NanColor=[0.25,
> 0.0, 0.0], ColorSpace='Diverging', ScalarRangeInitialized=1.0 )
>
> a1_crack_PiecewiseFunction = CreatePiecewiseFunction( Points=[-3.0, 0.0,
> 0.5, 0.0, 2147483647.0, 1.0, 0.5, 0.0] )
>
> DataRepresentation2.ScalarOpacityFunction = a1_crack_PiecewiseFunction
> DataRepresentation2.LookupTable = a1_crack_PVLookupTable
>
> a1_crack_PVLookupTable.NanColor = [1.0, 1.0, 0.0]
> a1_crack_PVLookupTable.RGBPoints = [-3.0, 1.0, 1.0, 1.0, 365072217.5, 0.0,
> 0.0, 1.0, 730144438.0, 0.0, 1.0, 1.0, 1073741822.0, 0.0, 1.0, 0.0,
> 1438814042.5, 1.0, 1.0, 0.0, 1803886263.0, 1.0, 0.0, 0.0, 2147483647.0,
> 0.878431, 0.0, 1.0]
> a1_crack_PVLookupTable.ScalarOpacityFunction = a1_crack_PiecewiseFunction
> a1_crack_PVLookupTable.ColorSpace = 'RGB'
>
> RenderView1.CameraPosition = [127.49999999999966, 127.5, 883.8540000000002]
> RenderView1.CameraClippingRange = [590.4254600000002, 1039.4068100000004]
>
> AnimationScene1.AnimationTime = 10.0
> AnimationScene1.NumberOfFrames = 100
> AnimationScene1.PlayMode = 'Sequence'
>
> CameraAnimationCue1 = GetCameraTrack()
> CameraAnimationCue1.AnimatedProxy = RenderView1
> CameraAnimationCue1.Mode = 'Path-based'
>
> TimeAnimationCue1 = GetTimeTrack()
> TimeAnimationCue1.Enabled = 0
>
> KeyFrame3658 = CameraKeyFrame( FocalPathPoints=[127.5, 127.5, 95.5],
> FocalPoint=[127.5, 127.5, 95.5], PositionPathPoints=[127.5, 127.5, 883.854,
> 740.1661272984488, 127.5, 591.6272475657036, 898.6265736288988, 127.5,
> -68.40801310294381, 485.4052264316708, 127.5, -606.9285573699966,
> -193.1524595153794, 127.5, -624.6972157143753, -633.9914888582924, 127.5,
> -108.54102948275286, -510.2917835834677, 127.5, 558.8828547857805],
> ClosedPositionPath=1, ParallelScale=204.0410497914574, Position=[127.5,
> 127.5, 883.8540784668097] )
>
> KeyFrame3659 = CameraKeyFrame( ParallelScale=204.0410497914574,
> Position=[127.5, 127.5, 883.8540784668097], KeyTime=1.0, FocalPoint=[127.5,
> 127.5, 95.5] )
>
> WriteAnimation( vidfile , Magnification=1, Quality=2, FrameRate=6.000000)
> CameraAnimationCue1.KeyFrames = [ KeyFrame3658, KeyFrame3659 ]
>
> Render()
>
>
> Please advise
>
> Many thanks
>
> Anton
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/cc67b183/attachment-0001.html>

From mexas at bris.ac.uk  Wed Jul 23 10:46:05 2014
From: mexas at bris.ac.uk (Anton Shterenlikht)
Date: Wed, 23 Jul 2014 15:46:05 +0100 (BST)
Subject: [Paraview] vtkPVCameraCueManipulator (0x8353f8e60): Too few
	keyframes to animate.
In-Reply-To: <CADHSJjAo36GrU23GgN+Wr-KuukAe1zm++X4mKjyzxegPfhhFCA@mail.gmail.com>
Message-ID: <201407231446.s6NEk44K088454@mech-cluster241.men.bris.ac.uk>

>From utkarsh.ayachit at kitware.com Wed Jul 23 15:02:03 2014
>
>Can you switch the lines "WriteAnimation" and "CameraAnimationCue.KeyFrame
>=...". The WrieAnimation should happen after that.

yes, that helped, thanks.

> Seems like a bug in the
>tracing code. The tracing code is being revamped. Although animation has
>been skipped in this revamp, it's on my todo list for subsequent release.

If you are talking about revamping,
would be great to get an easier way
to specify various parameters as
variables, not actual values, e.g.
in this code, produced by the tracer:

RenderView1.CameraPosition = [127.5, 127.5, 883.8540784668097]
RenderView1.CameraFocalPoint = [127.5, 127.5, 95.5]
RenderView1.CameraClippingRange = [590.4255376821416, 1039.4068896438118]
RenderView1.CameraParallelScale = 204.0410497914574

all number will have to be changed
if the size of my model changes,
but it's not clear how to scale
them with the data.

Many thanks

Anton


From utkarsh.ayachit at kitware.com  Wed Jul 23 11:11:15 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 23 Jul 2014 11:11:15 -0400
Subject: [Paraview] vtkPVCameraCueManipulator (0x8353f8e60): Too few
 keyframes to animate.
In-Reply-To: <201407231446.s6NEk44K088454@mech-cluster241.men.bris.ac.uk>
References: <CADHSJjAo36GrU23GgN+Wr-KuukAe1zm++X4mKjyzxegPfhhFCA@mail.gmail.com>
 <201407231446.s6NEk44K088454@mech-cluster241.men.bris.ac.uk>
Message-ID: <CADHSJjAduGLSLOnY7m_MXUAB3rb2aJJzQtn=auf1ok5drUvOEQ@mail.gmail.com>

While it's hard to get right of those values from trace, what's definitely
working already is the development version is, if you're tracing and you
hit the "reset camera" button", it will trace the Python method to use to
do extactly that which is "ResetCamera" and not the actual camera property
values. Would that help?

Utkarsh


On Wed, Jul 23, 2014 at 10:46 AM, Anton Shterenlikht <mexas at bris.ac.uk>
wrote:

> >From utkarsh.ayachit at kitware.com Wed Jul 23 15:02:03 2014
> >
> >Can you switch the lines "WriteAnimation" and "CameraAnimationCue.KeyFrame
> >=...". The WrieAnimation should happen after that.
>
> yes, that helped, thanks.
>
> > Seems like a bug in the
> >tracing code. The tracing code is being revamped. Although animation has
> >been skipped in this revamp, it's on my todo list for subsequent release.
>
> If you are talking about revamping,
> would be great to get an easier way
> to specify various parameters as
> variables, not actual values, e.g.
> in this code, produced by the tracer:
>
> RenderView1.CameraPosition = [127.5, 127.5, 883.8540784668097]
> RenderView1.CameraFocalPoint = [127.5, 127.5, 95.5]
> RenderView1.CameraClippingRange = [590.4255376821416, 1039.4068896438118]
> RenderView1.CameraParallelScale = 204.0410497914574
>
> all number will have to be changed
> if the size of my model changes,
> but it's not clear how to scale
> them with the data.
>
> Many thanks
>
> Anton
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/69cc7401/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jul 23 11:28:38 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 23 Jul 2014 11:28:38 -0400
Subject: [Paraview] Discovery of a 'nice' bug in volume rendering
In-Reply-To: <CADHSJjBD0mKY8eCThmYaPWrAGO8tUsDtPQu6uNZFaPKOpqHBiA@mail.gmail.com>
References: <003f01cf0d17$bf97a8b0$3ec6fa10$@infovalley.net.my>
 <CADHSJjBD0mKY8eCThmYaPWrAGO8tUsDtPQu6uNZFaPKOpqHBiA@mail.gmail.com>
Message-ID: <CADHSJjCzMCThkpXHJ6L_55DC24_vvAuP5p8=UCmys3j8zjd+OA@mail.gmail.com>

Den,

Thanks for reporting this issue and sharing the data. I just verified the
issue is no longer present in the development version of ParaView. If you
get a chance to try the nightly binaries, do let me know if you can still
reproduce the issue.

Thanks
Utkarsh


On Mon, Jan 13, 2014 at 6:16 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Den,
>
> Do you think you share the data + state file? That'll make it a little
> easier to track the problem down.
>
> Utkarsh
>
>
> On Thu, Jan 9, 2014 at 3:49 AM, Den Fairol <den.fairol at infovalley.net.my>
> wrote:
>
>> Hi,
>>
>>
>>
>> In the midst of figuring out having synchronize viewports in ParaViewWeb,
>> I accidentally bumped into a ?bug?. This bug actually cropped up from
>> ParaView (see image sequence at the bottom page). First and second exhibits
>> show a before and after rotation around X-axis. How did I arrive to this?
>> Load two objects, volume rendered the first, surface rendered the other.
>> Then I link up the second view/camera to the first one. Aligning the
>> objects together via translation. Apply a transfer function, save the state
>> and exit. Upon reloading the state, interacting with either object will
>> cause a ?clipping-effect? to the first object when it enters a certain
>> planar coordinate, which is neat primarily because now I can perform ROI on
>> volumetric data (at oblique angle) without incurring the wrath of
>> data-explosion from the clipping filter! The catch is, this effect will
>> subside the moment I commit any change to the transfer function or even
>> snapshot (hence why I did screen capture instead). Could anyone shed a
>> light on this some-what welcoming glitch? This
>>
>>
>>
>> Regards,
>>
>> Den
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/4dcb7d01/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 155474 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/4dcb7d01/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 166148 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/4dcb7d01/attachment-0003.png>

From dave.demarle at kitware.com  Wed Jul 23 11:40:33 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 23 Jul 2014 11:40:33 -0400
Subject: [Paraview] building paraview with vtkManta
In-Reply-To: <7AC6E2E2-970C-4DAB-9ADE-0992765A6BA6@llnl.gov>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
 <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
 <7AC6E2E2-970C-4DAB-9ADE-0992765A6BA6@llnl.gov>
Message-ID: <CANjZAi_3TFmSaM-tKFgr=dj4+Wedx+VquRw77fsdOHytan6mOQ@mail.gmail.com>

On Thu, Jul 17, 2014 at 12:25 PM, Cook, Rich <cook47 at llnl.gov> wrote:

>  Thanks
> What kind of experience can I expect?  I couldn?t find a description,
> tutorial or other presentation on the subject other than the page I
> stumbled across.
>

There isn't much to it so far. Basically vtkManta is just a drop in
replacement for OpenGL rendering of surfaces.

There are a few extra controls available on the display section of the
properties tab for per object display options (material type - metal,
dielectric etc) and view section (restored just last week in master) for
scene wide display options (enable shadows, rays per pixel, number of manta
threads etc).

There are not enough controls available to make it the right option for
really high quality (aesthetically pleasing) renderings. In its current
level of development you are better off File->Exporting the scene and then
importing it into some other system as you are doing. Given enough interest
we can of course improve on it from where it sits now and turn it into such
an option.

I?m hoping this will scale better than e.g blender does, where I?m hitting
> size limitations at disappointing scales.  I?m dusting off my old POVray
> stuff and I recall being seriously limited there as well in terms of size
> and speed but haven?t gotten it working again yet to be able to tell if
> it?s the same now as it was.
>

Scaling should be fine. Scaling is what LANL built it for (
http://viz.lanl.gov/publication/presentation/L2.pdf). You can render tens
of millions of triangles on a modern workstation interactively with it. In
HPC settings my personal record is 10 billion triangles (from a synthetic
test data set) at ~10 frames per second. That was with no secondary rays of
course, and only after significant queue wait and setup wait times.



> I?d love to see your build script, thanks.
>

Sure, will send it shortly.


>  ? Rich
>
>  On Jul 17, 2014, at 6:55 AM, David E DeMarle <dave.demarle at kitware.com>
> wrote:
>
>  Hey Rich,
>
>  I just ran across mention of vtkManta support in paraview.
>>
>
>  Wow, 2010? You've got some catching up to do. :)
>
>  It still compiles, runs and passes high level tests tests. The nightly
> linux binaries have it if you want to try it out quickly.
>
>  To compile it you need to:
> * compile manta (specifically r2439)
> * configure paraview with PARAVIEW_BUILD_PLUGIN_MantaView ON and
> MANTA_BUILD variable pointed to your manta build tree.
>
>  Let me know if you need the exact syntax for unattended builds and I'll
> send you a shell script.
>
>   How solid is this?
>>
>
>  I am aware of a couple of bugs that have crept in while this has been in
> cold storage (i.e. no project since the initial LANL push to pick up
> development on it).
>  * Manta (r2439 specifically) needs patches for OSX 10.8+ and MSVC.
> * View level options are not exposed in the GUI (very recent regression)
> * off by one bug in point associated color mapping (probably old)
>
>  We did get to the "future work" item from that article about integrating
> manta at the Renderer level so that OpenGL and Manta can coexist and it can
> be used in standalone builds.
>
>  TACC is working on something that will address the limitation that
> secondary rays don't work in HPC contexts.
>
>  Feel free to send me or the list emails for help getting it running.
>
>  cheers,
>
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
> On Wed, Jul 16, 2014 at 8:14 PM, Cook, Rich <cook47 at llnl.gov> wrote:
>
>>  I just ran across mention of vtkManta support in paraview.
>>
>> http://www.kitware.com/media/html/RenderedRealismAtNearlyRealTimeRates.html
>>
>>  Yay!  Yay?
>>
>>  How solid is this?  The documentation how to enable is pretty vague.
>> "To use vtkManta in ParaView, simply build Manta as described above, and
>> then turn on both shared libraries and the Manta plug-in when you build
>> ParaView. You will then have to specify the location of the Manta source
>> and build trees as described above.?
>>
>>  Changing my paraview build is always a daunting experience but the idea
>> of getting this working is very attractive.  What are the magic flags to
>> cmake?   My builds are automated and interacting with ccmake is problematic
>> on a build farm.
>>
>>  Here?s what I currently do.  Can you see why I?m confused?   :-)
>> Is there just a -DVTK_MANTA flag?  Do I still turn OSMESA on?
>>
>>  Thanks for any help.
>>
>>       $CMAKE_PATH/bin/cmake \
>>         $CMAKE_SPECIAL_ARGS \
>>         -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
>> -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
>> -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
>>   -DOSMESA_LIBRARY:FILEPATH='/usr/lib64/libOSMesa.so' \
>>   -DVTK_USE_OFFSCREEN:BOOL=ON -DOPENGL_gl_LIBRARY:FILEPATH=
>> -DVTK_USE_X:BOOL=OFF" \
>>          -DQT_QMAKE_EXECUTABLE:FILEPATH=$QT_PATH/bin/qmake.real \
>>         -DOPENGL_glu_LIBRARY:FILEPATH="/usr/lib64/libGLU.so" \
>>         -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR" \
>>         -DPARAVIEW_USE_BOOST:BOOL=ON \
>>         -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
>>         -DVISIT_BUILD_READER_CGNS:BOOL=ON \
>>         -DVISIT_BUILD_READER_Mili:BOOL=ON \
>>         -DVISIT_BUILD_READER_Silo:BOOL=ON \
>>         -DCGNS_INCLUDE_DIR:PATH="${CGNS_PATH}/include" \
>>
>> -DCGNS_LIBRARY:FILEPATH="${CGNS_PATH}/lib/libcgns.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>         -DMILI_INCLUDE_DIR:PATH="$MILI_PATH/include" \
>>
>> -DMILI_LIBRARY:FILEPATH="$MILI_PATH/lib/libmili.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>         -DSILO_INCLUDE_DIR:PATH="$SILO_PATH/include;$MILI_PATH/include" \
>>
>> -DSILO_LIBRARY:FILEPATH="$SILO_PATH/lib/libsiloh5.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>         -DBoost_INCLUDE_DIR:PATH="${BOOST_PATH}/include" \
>>         -DBoost_LIBRARY_DIRS:FILEPATH="${BOOST_PATH}/lib" \
>>         -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
>>         -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" \
>>         -DCMAKE_CXX_FLAGS:STRING=" -I$MILI_PATH/include
>> -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
>>         -DCMAKE_C_FLAGS:STRING="  -I$MILI_PATH/include
>> -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
>>         -DVTK_USE_SYSTEM_HDF5:BOOL=ON \
>>         -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \
>>         -DHDF5_DIR:PATH="$HDF5_PATH" \
>>         -DHDF5_C_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>>         -DHDF5_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>>         -DHDF5_HL_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>>
>> -DHDF5_hdf5_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>
>> -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>
>> -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>
>> -DHDF5_hdf5_hl_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>
>> -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>
>> -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>> \
>>         -DBUILD_SHARED_LIBS:BOOL=ON \
>>         -DBUILD_TESTING:BOOL=OFF \
>>         $PARAVIEW_SOURCE || errexit "cmake exited with an error status.
>> Please try again."
>>
>>
>>  --
>> ?Richard Cook
>> ? Lawrence Livermore National Laboratory
>> Bldg-453 Rm-4024, Mail Stop L-557
>> 7000 East Avenue,  Livermore, CA, 94550, USA
>> ? (office) (925) 423-9605
>> ? (fax) (925) 423-6961
>> ---
>> Information Management & Graphics Grp., Services & Development Div.,
>> Integrated Computing & Communications Dept.
>> (opinions expressed herein are mine and not those of LLNL)
>>
>>
>>
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
>  --
> ?Richard Cook
> ? Lawrence Livermore National Laboratory
> Bldg-453 Rm-4024, Mail Stop L-557
> 7000 East Avenue,  Livermore, CA, 94550, USA
> ? (office) (925) 423-9605
> ? (fax) (925) 423-6961
> ---
> Information Management & Graphics Grp., Services & Development Div.,
> Integrated Computing & Communications Dept.
> (opinions expressed herein are mine and not those of LLNL)
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/05cbd9ae/attachment-0001.html>

From senseiwa at gmail.com  Wed Jul 23 11:52:29 2014
From: senseiwa at gmail.com (Sensei)
Date: Wed, 23 Jul 2014 17:52:29 +0200
Subject: [Paraview] Newbie: adding field plot from another file
Message-ID: <53CFDA3D.7040701@gmail.com>

Dear all,

I am following the tutorial (Basic Usage) for ParaView, and I am trying 
to figure out how to do a simple thing:

Adding a filed from another file.

I have two files, one with displacements, and one with stresses. I'd 
like to do two things, basically.

First, deform the shape, and I know how to do it now (warp by vector).
Second, add a stress color map (for instance) on the *deformed* shape.

Obviously I don't know how I can do this. I can have the two separate 
plots, it's a piece of cake with ParaView, I can analyze, and visualize 
the contours... only on the original mesh.

Is it possible to apply a different data source to a warped shape?

Thanks!

From cook47 at llnl.gov  Wed Jul 23 11:55:58 2014
From: cook47 at llnl.gov (Cook, Rich)
Date: Wed, 23 Jul 2014 15:55:58 +0000
Subject: [Paraview] building paraview with vtkManta
In-Reply-To: <CANjZAi_3TFmSaM-tKFgr=dj4+Wedx+VquRw77fsdOHytan6mOQ@mail.gmail.com>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
 <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
 <7AC6E2E2-970C-4DAB-9ADE-0992765A6BA6@llnl.gov>
 <CANjZAi_3TFmSaM-tKFgr=dj4+Wedx+VquRw77fsdOHytan6mOQ@mail.gmail.com>
Message-ID: <314458F7-7428-4D5A-A6D5-8AFC0B8CF62C@llnl.gov>

Actually, from your description, does not sounds like the right fit here.  I?ll keep chugging away with POVRay.  blender gave up the ghost and I haven?t learned RenderMan/Maya, which would probably be a great approach but has fairly steep learning curve

On Jul 23, 2014, at 8:40 AM, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:


On Thu, Jul 17, 2014 at 12:25 PM, Cook, Rich <cook47 at llnl.gov<mailto:cook47 at llnl.gov>> wrote:
Thanks
What kind of experience can I expect?  I couldn?t find a description, tutorial or other presentation on the subject other than the page I stumbled across.

There isn't much to it so far. Basically vtkManta is just a drop in replacement for OpenGL rendering of surfaces.

There are a few extra controls available on the display section of the properties tab for per object display options (material type - metal, dielectric etc) and view section (restored just last week in master) for scene wide display options (enable shadows, rays per pixel, number of manta threads etc).

There are not enough controls available to make it the right option for really high quality (aesthetically pleasing) renderings. In its current level of development you are better off File->Exporting the scene and then importing it into some other system as you are doing. Given enough interest we can of course improve on it from where it sits now and turn it into such an option.

I?m hoping this will scale better than e.g blender does, where I?m hitting size limitations at disappointing scales.  I?m dusting off my old POVray stuff and I recall being seriously limited there as well in terms of size and speed but haven?t gotten it working again yet to be able to tell if it?s the same now as it was.

Scaling should be fine. Scaling is what LANL built it for (http://viz.lanl.gov/publication/presentation/L2.pdf). You can render tens of millions of triangles on a modern workstation interactively with it. In HPC settings my personal record is 10 billion triangles (from a synthetic test data set) at ~10 frames per second. That was with no secondary rays of course, and only after significant queue wait and setup wait times.


I?d love to see your build script, thanks.

Sure, will send it shortly.

? Rich

On Jul 17, 2014, at 6:55 AM, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:

Hey Rich,

I just ran across mention of vtkManta support in paraview.

Wow, 2010? You've got some catching up to do. :)

It still compiles, runs and passes high level tests tests. The nightly linux binaries have it if you want to try it out quickly.

To compile it you need to:
* compile manta (specifically r2439)
* configure paraview with PARAVIEW_BUILD_PLUGIN_MantaView ON and MANTA_BUILD variable pointed to your manta build tree.

Let me know if you need the exact syntax for unattended builds and I'll send you a shell script.

How solid is this?

I am aware of a couple of bugs that have crept in while this has been in cold storage (i.e. no project since the initial LANL push to pick up development on it).
* Manta (r2439 specifically) needs patches for OSX 10.8+ and MSVC.
* View level options are not exposed in the GUI (very recent regression)
* off by one bug in point associated color mapping (probably old)

We did get to the "future work" item from that article about integrating manta at the Renderer level so that OpenGL and Manta can coexist and it can be used in standalone builds.

TACC is working on something that will address the limitation that secondary rays don't work in HPC contexts.

Feel free to send me or the list emails for help getting it running.

cheers,

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>


On Wed, Jul 16, 2014 at 8:14 PM, Cook, Rich <cook47 at llnl.gov<mailto:cook47 at llnl.gov>> wrote:
I just ran across mention of vtkManta support in paraview.
http://www.kitware.com/media/html/RenderedRealismAtNearlyRealTimeRates.html

Yay!  Yay?

How solid is this?  The documentation how to enable is pretty vague.
"To use vtkManta in ParaView, simply build Manta as described above, and then turn on both shared libraries and the Manta plug-in when you build ParaView. You will then have to specify the location of the Manta source and build trees as described above.?

Changing my paraview build is always a daunting experience but the idea of getting this working is very attractive.  What are the magic flags to cmake?   My builds are automated and interacting with ccmake is problematic on a build farm.

Here?s what I currently do.  Can you see why I?m confused?   :-)
Is there just a -DVTK_MANTA flag?  Do I still turn OSMESA on?

Thanks for any help.

    $CMAKE_PATH/bin/cmake \
        $CMAKE_SPECIAL_ARGS \
        -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
-DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
-DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
 -DOSMESA_LIBRARY:FILEPATH='/usr/lib64/libOSMesa.so' \
 -DVTK_USE_OFFSCREEN:BOOL=ON -DOPENGL_gl_LIBRARY:FILEPATH= -DVTK_USE_X:BOOL=OFF" \
        -DQT_QMAKE_EXECUTABLE:FILEPATH=$QT_PATH/bin/qmake.real \
        -DOPENGL_glu_LIBRARY:FILEPATH="/usr/lib64/libGLU.so" \
        -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR" \
        -DPARAVIEW_USE_BOOST:BOOL=ON \
        -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
        -DVISIT_BUILD_READER_CGNS:BOOL=ON \
        -DVISIT_BUILD_READER_Mili:BOOL=ON \
        -DVISIT_BUILD_READER_Silo:BOOL=ON \
        -DCGNS_INCLUDE_DIR:PATH="${CGNS_PATH}/include" \
        -DCGNS_LIBRARY:FILEPATH="${CGNS_PATH}/lib/libcgns.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DMILI_INCLUDE_DIR:PATH="$MILI_PATH/include" \
        -DMILI_LIBRARY:FILEPATH="$MILI_PATH/lib/libmili.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DSILO_INCLUDE_DIR:PATH="$SILO_PATH/include;$MILI_PATH/include" \
        -DSILO_LIBRARY:FILEPATH="$SILO_PATH/lib/libsiloh5.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBoost_INCLUDE_DIR:PATH="${BOOST_PATH}/include" \
        -DBoost_LIBRARY_DIRS:FILEPATH="${BOOST_PATH}/lib" \
        -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
        -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" \
        -DCMAKE_CXX_FLAGS:STRING=" -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DCMAKE_C_FLAGS:STRING="  -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DVTK_USE_SYSTEM_HDF5:BOOL=ON \
        -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \
        -DHDF5_DIR:PATH="$HDF5_PATH" \
        -DHDF5_C_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_HL_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_hdf5_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBUILD_SHARED_LIBS:BOOL=ON \
        -DBUILD_TESTING:BOOL=OFF \
        $PARAVIEW_SOURCE || errexit "cmake exited with an error status. Please try again."


--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605<tel:%28925%29%20423-9605>
? (fax) (925) 423-6961<tel:%28925%29%20423-6961>
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)




_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview



--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605<tel:%28925%29%20423-9605>
? (fax) (925) 423-6961<tel:%28925%29%20423-6961>
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)





--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605
? (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/550c7e82/attachment-0001.html>

From cory.quammen at kitware.com  Wed Jul 23 12:00:58 2014
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 23 Jul 2014 12:00:58 -0400
Subject: [Paraview] Newbie: adding field plot from another file
In-Reply-To: <53CFDA3D.7040701@gmail.com>
References: <53CFDA3D.7040701@gmail.com>
Message-ID: <CAB5Fpx6+-+CRzGpCbMjF4meAKKzTjTbELHesnT6bFrX_Vbkk=Q@mail.gmail.com>

Assuming your two data sets have the same topology, you can try using
the Append Attributes filter to combine them into a single data set.
Select the two files in the pipeline browser and select the Append
Attributes filter.

Hope that helps,
Cory

On Wed, Jul 23, 2014 at 11:52 AM, Sensei <senseiwa at gmail.com> wrote:
> Dear all,
>
> I am following the tutorial (Basic Usage) for ParaView, and I am trying to
> figure out how to do a simple thing:
>
> Adding a filed from another file.
>
> I have two files, one with displacements, and one with stresses. I'd like to
> do two things, basically.
>
> First, deform the shape, and I know how to do it now (warp by vector).
> Second, add a stress color map (for instance) on the *deformed* shape.
>
> Obviously I don't know how I can do this. I can have the two separate plots,
> it's a piece of cake with ParaView, I can analyze, and visualize the
> contours... only on the original mesh.
>
> Is it possible to apply a different data source to a warped shape?
>
> Thanks!
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview

From dave.demarle at kitware.com  Wed Jul 23 14:08:09 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 23 Jul 2014 14:08:09 -0400
Subject: [Paraview] building paraview with vtkManta
In-Reply-To: <CANjZAi_3TFmSaM-tKFgr=dj4+Wedx+VquRw77fsdOHytan6mOQ@mail.gmail.com>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
 <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
 <7AC6E2E2-970C-4DAB-9ADE-0992765A6BA6@llnl.gov>
 <CANjZAi_3TFmSaM-tKFgr=dj4+Wedx+VquRw77fsdOHytan6mOQ@mail.gmail.com>
Message-ID: <CANjZAi_ivBdEMoDmo8SjneZ5qNWk1c=nKBTo+PC8e_weuOnyvA@mail.gmail.com>

As promised a manta enabled paraview build script.

In the superbuild there are patches for this version of manta that fix a
couple of minor compilation issues on recent compilers.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jul 23, 2014 at 11:40 AM, David E DeMarle <dave.demarle at kitware.com>
wrote:

>
> On Thu, Jul 17, 2014 at 12:25 PM, Cook, Rich <cook47 at llnl.gov> wrote:
>
>>  Thanks
>> What kind of experience can I expect?  I couldn?t find a description,
>> tutorial or other presentation on the subject other than the page I
>> stumbled across.
>>
>
> There isn't much to it so far. Basically vtkManta is just a drop in
> replacement for OpenGL rendering of surfaces.
>
> There are a few extra controls available on the display section of the
> properties tab for per object display options (material type - metal,
> dielectric etc) and view section (restored just last week in master) for
> scene wide display options (enable shadows, rays per pixel, number of manta
> threads etc).
>
> There are not enough controls available to make it the right option for
> really high quality (aesthetically pleasing) renderings. In its current
> level of development you are better off File->Exporting the scene and then
> importing it into some other system as you are doing. Given enough interest
> we can of course improve on it from where it sits now and turn it into such
> an option.
>
> I?m hoping this will scale better than e.g blender does, where I?m hitting
>> size limitations at disappointing scales.  I?m dusting off my old POVray
>> stuff and I recall being seriously limited there as well in terms of size
>> and speed but haven?t gotten it working again yet to be able to tell if
>> it?s the same now as it was.
>>
>
> Scaling should be fine. Scaling is what LANL built it for (
> http://viz.lanl.gov/publication/presentation/L2.pdf). You can render tens
> of millions of triangles on a modern workstation interactively with it. In
> HPC settings my personal record is 10 billion triangles (from a synthetic
> test data set) at ~10 frames per second. That was with no secondary rays of
> course, and only after significant queue wait and setup wait times.
>
>
>
>> I?d love to see your build script, thanks.
>>
>
> Sure, will send it shortly.
>
>
>>  ? Rich
>>
>>  On Jul 17, 2014, at 6:55 AM, David E DeMarle <dave.demarle at kitware.com>
>> wrote:
>>
>>  Hey Rich,
>>
>>  I just ran across mention of vtkManta support in paraview.
>>>
>>
>>  Wow, 2010? You've got some catching up to do. :)
>>
>>  It still compiles, runs and passes high level tests tests. The nightly
>> linux binaries have it if you want to try it out quickly.
>>
>>  To compile it you need to:
>> * compile manta (specifically r2439)
>> * configure paraview with PARAVIEW_BUILD_PLUGIN_MantaView ON and
>> MANTA_BUILD variable pointed to your manta build tree.
>>
>>  Let me know if you need the exact syntax for unattended builds and I'll
>> send you a shell script.
>>
>>   How solid is this?
>>>
>>
>>  I am aware of a couple of bugs that have crept in while this has been
>> in cold storage (i.e. no project since the initial LANL push to pick up
>> development on it).
>>  * Manta (r2439 specifically) needs patches for OSX 10.8+ and MSVC.
>> * View level options are not exposed in the GUI (very recent regression)
>> * off by one bug in point associated color mapping (probably old)
>>
>>  We did get to the "future work" item from that article about
>> integrating manta at the Renderer level so that OpenGL and Manta can
>> coexist and it can be used in standalone builds.
>>
>>  TACC is working on something that will address the limitation that
>> secondary rays don't work in HPC contexts.
>>
>>  Feel free to send me or the list emails for help getting it running.
>>
>>  cheers,
>>
>>  David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>>
>> On Wed, Jul 16, 2014 at 8:14 PM, Cook, Rich <cook47 at llnl.gov> wrote:
>>
>>>  I just ran across mention of vtkManta support in paraview.
>>>
>>> http://www.kitware.com/media/html/RenderedRealismAtNearlyRealTimeRates.html
>>>
>>>  Yay!  Yay?
>>>
>>>  How solid is this?  The documentation how to enable is pretty vague.
>>> "To use vtkManta in ParaView, simply build Manta as described above,
>>> and then turn on both shared libraries and the Manta plug-in when you build
>>> ParaView. You will then have to specify the location of the Manta source
>>> and build trees as described above.?
>>>
>>>  Changing my paraview build is always a daunting experience but the
>>> idea of getting this working is very attractive.  What are the magic flags
>>> to cmake?   My builds are automated and interacting with ccmake is
>>> problematic on a build farm.
>>>
>>>  Here?s what I currently do.  Can you see why I?m confused?   :-)
>>> Is there just a -DVTK_MANTA flag?  Do I still turn OSMESA on?
>>>
>>>  Thanks for any help.
>>>
>>>       $CMAKE_PATH/bin/cmake \
>>>         $CMAKE_SPECIAL_ARGS \
>>>         -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
>>> -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
>>> -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
>>>   -DOSMESA_LIBRARY:FILEPATH='/usr/lib64/libOSMesa.so' \
>>>   -DVTK_USE_OFFSCREEN:BOOL=ON -DOPENGL_gl_LIBRARY:FILEPATH=
>>> -DVTK_USE_X:BOOL=OFF" \
>>>          -DQT_QMAKE_EXECUTABLE:FILEPATH=$QT_PATH/bin/qmake.real \
>>>         -DOPENGL_glu_LIBRARY:FILEPATH="/usr/lib64/libGLU.so" \
>>>         -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR" \
>>>         -DPARAVIEW_USE_BOOST:BOOL=ON \
>>>         -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
>>>         -DVISIT_BUILD_READER_CGNS:BOOL=ON \
>>>         -DVISIT_BUILD_READER_Mili:BOOL=ON \
>>>         -DVISIT_BUILD_READER_Silo:BOOL=ON \
>>>         -DCGNS_INCLUDE_DIR:PATH="${CGNS_PATH}/include" \
>>>
>>> -DCGNS_LIBRARY:FILEPATH="${CGNS_PATH}/lib/libcgns.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>         -DMILI_INCLUDE_DIR:PATH="$MILI_PATH/include" \
>>>
>>> -DMILI_LIBRARY:FILEPATH="$MILI_PATH/lib/libmili.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>         -DSILO_INCLUDE_DIR:PATH="$SILO_PATH/include;$MILI_PATH/include" \
>>>
>>> -DSILO_LIBRARY:FILEPATH="$SILO_PATH/lib/libsiloh5.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>         -DBoost_INCLUDE_DIR:PATH="${BOOST_PATH}/include" \
>>>         -DBoost_LIBRARY_DIRS:FILEPATH="${BOOST_PATH}/lib" \
>>>         -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
>>>         -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" \
>>>         -DCMAKE_CXX_FLAGS:STRING=" -I$MILI_PATH/include
>>> -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
>>>         -DCMAKE_C_FLAGS:STRING="  -I$MILI_PATH/include
>>> -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
>>>         -DVTK_USE_SYSTEM_HDF5:BOOL=ON \
>>>         -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \
>>>         -DHDF5_DIR:PATH="$HDF5_PATH" \
>>>         -DHDF5_C_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>>>         -DHDF5_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>>>         -DHDF5_HL_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
>>>
>>> -DHDF5_hdf5_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>
>>> -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>
>>> -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>
>>> -DHDF5_hdf5_hl_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>
>>> -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>
>>> -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so"
>>> \
>>>         -DBUILD_SHARED_LIBS:BOOL=ON \
>>>         -DBUILD_TESTING:BOOL=OFF \
>>>         $PARAVIEW_SOURCE || errexit "cmake exited with an error status.
>>> Please try again."
>>>
>>>
>>>  --
>>> ?Richard Cook
>>> ? Lawrence Livermore National Laboratory
>>> Bldg-453 Rm-4024, Mail Stop L-557
>>> 7000 East Avenue,  Livermore, CA, 94550, USA
>>> ? (office) (925) 423-9605
>>> ? (fax) (925) 423-6961
>>> ---
>>> Information Management & Graphics Grp., Services & Development Div.,
>>> Integrated Computing & Communications Dept.
>>> (opinions expressed herein are mine and not those of LLNL)
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>>  --
>> ?Richard Cook
>> ? Lawrence Livermore National Laboratory
>> Bldg-453 Rm-4024, Mail Stop L-557
>> 7000 East Avenue,  Livermore, CA, 94550, USA
>> ? (office) (925) 423-9605
>> ? (fax) (925) 423-6961
>> ---
>> Information Management & Graphics Grp., Services & Development Div.,
>> Integrated Computing & Communications Dept.
>> (opinions expressed herein are mine and not those of LLNL)
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/799734ff/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: makemanta.sh
Type: application/x-sh
Size: 1100 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/799734ff/attachment-0001.sh>

From cook47 at llnl.gov  Wed Jul 23 14:47:13 2014
From: cook47 at llnl.gov (Cook, Rich)
Date: Wed, 23 Jul 2014 18:47:13 +0000
Subject: [Paraview] building paraview with vtkManta
In-Reply-To: <CANjZAi_ivBdEMoDmo8SjneZ5qNWk1c=nKBTo+PC8e_weuOnyvA@mail.gmail.com>
References: <6BBA675A-8D9A-4C72-B0FB-ADD945496790@llnl.gov>
 <CANjZAi-qqvXPyReMxz0CvJdTyMMrGqPoa4-p_DbGsSK2WL4SxQ@mail.gmail.com>
 <7AC6E2E2-970C-4DAB-9ADE-0992765A6BA6@llnl.gov>
 <CANjZAi_3TFmSaM-tKFgr=dj4+Wedx+VquRw77fsdOHytan6mOQ@mail.gmail.com>
 <CANjZAi_ivBdEMoDmo8SjneZ5qNWk1c=nKBTo+PC8e_weuOnyvA@mail.gmail.com>
Message-ID: <2CAACBC5-7B3E-4701-99AD-1DD956146FD4@llnl.gov>

Thank you!  :-)

On Jul 23, 2014, at 11:08 AM, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:

As promised a manta enabled paraview build script.

In the superbuild there are patches for this version of manta that fix a couple of minor compilation issues on recent compilers.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Jul 23, 2014 at 11:40 AM, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:

On Thu, Jul 17, 2014 at 12:25 PM, Cook, Rich <cook47 at llnl.gov<mailto:cook47 at llnl.gov>> wrote:
Thanks
What kind of experience can I expect?  I couldn?t find a description, tutorial or other presentation on the subject other than the page I stumbled across.

There isn't much to it so far. Basically vtkManta is just a drop in replacement for OpenGL rendering of surfaces.

There are a few extra controls available on the display section of the properties tab for per object display options (material type - metal, dielectric etc) and view section (restored just last week in master) for scene wide display options (enable shadows, rays per pixel, number of manta threads etc).

There are not enough controls available to make it the right option for really high quality (aesthetically pleasing) renderings. In its current level of development you are better off File->Exporting the scene and then importing it into some other system as you are doing. Given enough interest we can of course improve on it from where it sits now and turn it into such an option.

I?m hoping this will scale better than e.g blender does, where I?m hitting size limitations at disappointing scales.  I?m dusting off my old POVray stuff and I recall being seriously limited there as well in terms of size and speed but haven?t gotten it working again yet to be able to tell if it?s the same now as it was.

Scaling should be fine. Scaling is what LANL built it for (http://viz.lanl.gov/publication/presentation/L2.pdf). You can render tens of millions of triangles on a modern workstation interactively with it. In HPC settings my personal record is 10 billion triangles (from a synthetic test data set) at ~10 frames per second. That was with no secondary rays of course, and only after significant queue wait and setup wait times.


I?d love to see your build script, thanks.

Sure, will send it shortly.

? Rich

On Jul 17, 2014, at 6:55 AM, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:

Hey Rich,

I just ran across mention of vtkManta support in paraview.

Wow, 2010? You've got some catching up to do. :)

It still compiles, runs and passes high level tests tests. The nightly linux binaries have it if you want to try it out quickly.

To compile it you need to:
* compile manta (specifically r2439)
* configure paraview with PARAVIEW_BUILD_PLUGIN_MantaView ON and MANTA_BUILD variable pointed to your manta build tree.

Let me know if you need the exact syntax for unattended builds and I'll send you a shell script.

How solid is this?

I am aware of a couple of bugs that have crept in while this has been in cold storage (i.e. no project since the initial LANL push to pick up development on it).
* Manta (r2439 specifically) needs patches for OSX 10.8+ and MSVC.
* View level options are not exposed in the GUI (very recent regression)
* off by one bug in point associated color mapping (probably old)

We did get to the "future work" item from that article about integrating manta at the Renderer level so that OpenGL and Manta can coexist and it can be used in standalone builds.

TACC is working on something that will address the limitation that secondary rays don't work in HPC contexts.

Feel free to send me or the list emails for help getting it running.

cheers,

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909<tel:518-881-4909>


On Wed, Jul 16, 2014 at 8:14 PM, Cook, Rich <cook47 at llnl.gov<mailto:cook47 at llnl.gov>> wrote:
I just ran across mention of vtkManta support in paraview.
http://www.kitware.com/media/html/RenderedRealismAtNearlyRealTimeRates.html

Yay!  Yay?

How solid is this?  The documentation how to enable is pretty vague.
"To use vtkManta in ParaView, simply build Manta as described above, and then turn on both shared libraries and the Manta plug-in when you build ParaView. You will then have to specify the location of the Manta source and build trees as described above.?

Changing my paraview build is always a daunting experience but the idea of getting this working is very attractive.  What are the magic flags to cmake?   My builds are automated and interacting with ccmake is problematic on a build farm.

Here?s what I currently do.  Can you see why I?m confused?   :-)
Is there just a -DVTK_MANTA flag?  Do I still turn OSMESA on?

Thanks for any help.

    $CMAKE_PATH/bin/cmake \
        $CMAKE_SPECIAL_ARGS \
        -DPARAVIEW_ENABLE_PYTHON:BOOL=ON \
-DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
-DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
 -DOSMESA_LIBRARY:FILEPATH='/usr/lib64/libOSMesa.so' \
 -DVTK_USE_OFFSCREEN:BOOL=ON -DOPENGL_gl_LIBRARY:FILEPATH= -DVTK_USE_X:BOOL=OFF" \
        -DQT_QMAKE_EXECUTABLE:FILEPATH=$QT_PATH/bin/qmake.real \
        -DOPENGL_glu_LIBRARY:FILEPATH="/usr/lib64/libGLU.so" \
        -DCMAKE_INSTALL_PREFIX:PATH="$INSTALL_DIR" \
        -DPARAVIEW_USE_BOOST:BOOL=ON \
        -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON \
        -DVISIT_BUILD_READER_CGNS:BOOL=ON \
        -DVISIT_BUILD_READER_Mili:BOOL=ON \
        -DVISIT_BUILD_READER_Silo:BOOL=ON \
        -DCGNS_INCLUDE_DIR:PATH="${CGNS_PATH}/include" \
        -DCGNS_LIBRARY:FILEPATH="${CGNS_PATH}/lib/libcgns.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DMILI_INCLUDE_DIR:PATH="$MILI_PATH/include" \
        -DMILI_LIBRARY:FILEPATH="$MILI_PATH/lib/libmili.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DSILO_INCLUDE_DIR:PATH="$SILO_PATH/include;$MILI_PATH/include" \
        -DSILO_LIBRARY:FILEPATH="$SILO_PATH/lib/libsiloh5.a;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBoost_INCLUDE_DIR:PATH="${BOOST_PATH}/include" \
        -DBoost_LIBRARY_DIRS:FILEPATH="${BOOST_PATH}/lib" \
        -DCMAKE_EXE_LINKER_FLAGS:STRING="$LINKER_FLAGS" \
        -DCMAKE_EXE_LINKER_FLAGS_DEBUG:STRING="$LINKER_FLAGS" \
        -DCMAKE_CXX_FLAGS:STRING=" -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DCMAKE_C_FLAGS:STRING="  -I$MILI_PATH/include -I$HDF5_PATH/include  -I${MPI_PATH}/include " \
        -DVTK_USE_SYSTEM_HDF5:BOOL=ON \
        -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=ON \
        -DHDF5_DIR:PATH="$HDF5_PATH" \
        -DHDF5_C_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_HL_INCLUDE_DIR:PATH="$HDF5_PATH/include" \
        -DHDF5_hdf5_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_DEBUG:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DHDF5_hdf5_hl_LIBRARY_RELEASE:FILEPATH="$HDF5_PATH/lib/libhdf5_hl.so;$SZIP_PATH/lib/libsz.so;/usr/lib64/libz.so" \
        -DBUILD_SHARED_LIBS:BOOL=ON \
        -DBUILD_TESTING:BOOL=OFF \
        $PARAVIEW_SOURCE || errexit "cmake exited with an error status. Please try again."


--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605<tel:%28925%29%20423-9605>
? (fax) (925) 423-6961<tel:%28925%29%20423-6961>
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)




_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview



--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605<tel:%28925%29%20423-9605>
? (fax) (925) 423-6961<tel:%28925%29%20423-6961>
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)





<makemanta.sh>

--
?Richard Cook
? Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
? (office) (925) 423-9605
? (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140723/7d0d4ba8/attachment-0001.html>

From vaurs.geraud at free.fr  Thu Jul 24 03:27:57 2014
From: vaurs.geraud at free.fr (=?ISO-8859-1?Q?G=E9raud_Vaurs?=)
Date: Thu, 24 Jul 2014 09:27:57 +0200
Subject: [Paraview]  CSV data volume rendering
Message-ID: <je3i6rpxj7nvvd6rbst490ga.1406186877620@email.android.com>

Good morning,?

I am a new user of Paraview and I am requesting your support regarding volume rendering.
?

I have a set of data included in a CSV file. The data looks like:

??????????????? X???????????? Y???????????? Z???????????? C (Value to be represented)

The C value typically represents particle concentration.

?

My ultimate goal would be to display a volume with color and opacity being directly linked to C (particle concentration).

?

I managed to import my data in ParaView and then used the ?Tetrahedralize? filter to get an unstructured Grid.

I am able to display my points (using ?Points? representation) such that the color of each point depends on its C value. However, changing representation to ?Volume? just lead to nothing being displayed.

Obviously I am missing something. Do you have an idea about how to get my volume?

?

Thank you in advance for your help.

?

G?raud Vaurs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140724/4ffcd891/attachment.html>

From mexas at bris.ac.uk  Thu Jul 24 07:33:40 2014
From: mexas at bris.ac.uk (Anton Shterenlikht)
Date: Thu, 24 Jul 2014 12:33:40 +0100 (BST)
Subject: [Paraview] pvbatch: python - help make animation window bigger
Message-ID: <201407241133.s6OBXeQR096256@mech-cluster241.men.bris.ac.uk>

I've recorded this python script with PV Trace.
However, the resulting animation window is small.
What do I need to edit to make the window, e.g. 1000x1000 pixels?

Thanks

Anton


# use defined variables, no indent allowed, start at col 1

infile  = "z.xdmf"  # name of XDMF file
picfile = "z.png"   # image output file
vidfile = "z.ogv"   # animation output file
trlo    = -4        # lower threshold
trhi    = 0         # upper threshold

# end of user variables
 
try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()

# load XDMF file
z_xdmf = XDMFReader( FileName=infile )

AnimationScene1 = GetAnimationScene()
AnimationScene1.EndTime = 10.0
AnimationScene1.PlayMode = 'Snap To TimeSteps'

z_xdmf.Sets = []
z_xdmf.Grids = ['T0', 'T30', 'T60', 'T90', 'T120', 'T150', 'T180', 'T210', 'T240', 'T270', 'T300']
z_xdmf.PointArrays = ['crack']

RenderView1 = GetRenderView()
RenderView1.CenterOfRotation = [127.5, 127.5, 95.5]

DataRepresentation1 = Show()
DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
DataRepresentation1.Slice = 95
DataRepresentation1.SelectionPointFieldDataArrayName = 'crack'
DataRepresentation1.ScalarOpacityUnitDistance = 1.762150384296635
DataRepresentation1.Representation = 'Outline'
DataRepresentation1.ScaleFactor = 25.5

RenderView1.CameraPosition = [127.5, 127.5, 883.8540784668097]
RenderView1.CameraFocalPoint = [127.5, 127.5, 95.5]
RenderView1.CameraClippingRange = [590.4255376821416, 1039.4068896438118]
RenderView1.CameraParallelScale = 204.0410497914574

Threshold1 = Threshold()
Threshold1.Scalars = ['POINTS', 'crack']
Threshold1.AllScalars = 0
Threshold1.ThresholdRange = [ trlo, trhi ]

DataRepresentation2 = Show()
DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
DataRepresentation2.SelectionPointFieldDataArrayName = 'crack'
DataRepresentation2.ColorArrayName = ('POINT_DATA', 'crack')
DataRepresentation2.ScalarOpacityUnitDistance = 1.88988157484231
DataRepresentation2.ScaleFactor = 0.2

a1_crack_PVLookupTable = GetLookupTableForArray( "crack", 1, RGBPoints=[-3.0, 0.23, 0.299, 0.754, 1073741822.0, 0.865, 0.865, 0.865, 2147483647.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', NanColor=[0.25, 0.0, 0.0], ColorSpace='Diverging', ScalarRangeInitialized=1.0 )

a1_crack_PiecewiseFunction = CreatePiecewiseFunction( Points=[-3.0, 0.0, 0.5, 0.0, 2147483647.0, 1.0, 0.5, 0.0] )

DataRepresentation2.ScalarOpacityFunction = a1_crack_PiecewiseFunction
DataRepresentation2.LookupTable = a1_crack_PVLookupTable

a1_crack_PVLookupTable.NanColor = [1.0, 1.0, 0.0]
a1_crack_PVLookupTable.RGBPoints = [-3.0, 1.0, 1.0, 1.0, 365072217.5, 0.0, 0.0, 1.0, 730144438.0, 0.0, 1.0, 1.0, 1073741822.0, 0.0, 1.0, 0.0, 1438814042.5, 1.0, 1.0, 0.0, 1803886263.0, 1.0, 0.0, 0.0, 2147483647.0, 0.878431, 0.0, 1.0]
a1_crack_PVLookupTable.ScalarOpacityFunction = a1_crack_PiecewiseFunction
a1_crack_PVLookupTable.ColorSpace = 'RGB'

RenderView1.CameraPosition = [127.49999999999966, 127.5, 883.8540000000002]
RenderView1.CameraClippingRange = [590.4254600000002, 1039.4068100000004]

# custom background

RenderView1.UseGradientBackground = 1
RenderView1.Background2 = [0.0, 0.0, 0.17254901960784313]
RenderView1.Background = [0.32941176470588235, 0.34901960784313724, 0.42745098039215684]

AnimationScene1.AnimationTime = 10.0
AnimationScene1.NumberOfFrames = 100
AnimationScene1.PlayMode = 'Sequence'

CameraAnimationCue1 = GetCameraTrack()
CameraAnimationCue1.AnimatedProxy = RenderView1
CameraAnimationCue1.Mode = 'Path-based'

TimeAnimationCue1 = GetTimeTrack()
#TimeAnimationCue1.Enabled = 0

AnimationScene1.NumberOfFrames = 100
AnimationScene1.PlayMode = 'Sequence'

KeyFrame3658 = CameraKeyFrame( FocalPathPoints=[127.5, 127.5, 95.5], FocalPoint=[127.5, 127.5, 95.5], PositionPathPoints=[127.5, 127.5, 883.854, 740.1661272984488, 127.5, 591.6272475657036, 898.6265736288988, 127.5, -68.40801310294381, 485.4052264316708, 127.5, -606.9285573699966, -193.1524595153794, 127.5, -624.6972157143753, -633.9914888582924, 127.5, -108.54102948275286, -510.2917835834677, 127.5, 558.8828547857805], ClosedPositionPath=1, ParallelScale=204.0410497914574, Position=[127.5, 127.5, 883.8540784668097] )

KeyFrame3659 = CameraKeyFrame( ParallelScale=204.0410497914574, Position=[127.5, 127.5, 883.8540784668097], KeyTime=1.0, FocalPoint=[127.5, 127.5, 95.5] )

CameraAnimationCue1.KeyFrames = [ KeyFrame3658, KeyFrame3659 ]
WriteAnimation( vidfile , Magnification=1, Quality=2, FrameRate=6.000000)

Render()


From louie.cardone-noott at linacre.ox.ac.uk  Thu Jul 24 07:37:28 2014
From: louie.cardone-noott at linacre.ox.ac.uk (Louie Cardone-Noott)
Date: Thu, 24 Jul 2014 12:37:28 +0100
Subject: [Paraview] pvbatch: python - help make animation window bigger
In-Reply-To: <16129c0e-33f9-491f-ad33-1e7853bd22b4@HUB04.ad.oak.ox.ac.uk>
References: <16129c0e-33f9-491f-ad33-1e7853bd22b4@HUB04.ad.oak.ox.ac.uk>
Message-ID: <CAOCDKs90bxKqbVffqUt9W8_Fm50=_bEtOicy9F-2Qwb=MTWcDw@mail.gmail.com>

Hi Anton,

RenderView1.ViewSize = [1000, 1000]

Best wishes,
Louie





On 24 July 2014 12:33, Anton Shterenlikht <mexas at bris.ac.uk> wrote:

> I've recorded this python script with PV Trace.
> However, the resulting animation window is small.
> What do I need to edit to make the window, e.g. 1000x1000 pixels?
>
> Thanks
>
> Anton
>
>
> # use defined variables, no indent allowed, start at col 1
>
> infile  = "z.xdmf"  # name of XDMF file
> picfile = "z.png"   # image output file
> vidfile = "z.ogv"   # animation output file
> trlo    = -4        # lower threshold
> trhi    = 0         # upper threshold
>
> # end of user variables
>
> try: paraview.simple
> except: from paraview.simple import *
> paraview.simple._DisableFirstRenderCameraReset()
>
> # load XDMF file
> z_xdmf = XDMFReader( FileName=infile )
>
> AnimationScene1 = GetAnimationScene()
> AnimationScene1.EndTime = 10.0
> AnimationScene1.PlayMode = 'Snap To TimeSteps'
>
> z_xdmf.Sets = []
> z_xdmf.Grids = ['T0', 'T30', 'T60', 'T90', 'T120', 'T150', 'T180', 'T210',
> 'T240', 'T270', 'T300']
> z_xdmf.PointArrays = ['crack']
>
> RenderView1 = GetRenderView()
> RenderView1.CenterOfRotation = [127.5, 127.5, 95.5]
>
> DataRepresentation1 = Show()
> DataRepresentation1.EdgeColor = [0.0, 0.0, 0.5000076295109483]
> DataRepresentation1.Slice = 95
> DataRepresentation1.SelectionPointFieldDataArrayName = 'crack'
> DataRepresentation1.ScalarOpacityUnitDistance = 1.762150384296635
> DataRepresentation1.Representation = 'Outline'
> DataRepresentation1.ScaleFactor = 25.5
>
> RenderView1.CameraPosition = [127.5, 127.5, 883.8540784668097]
> RenderView1.CameraFocalPoint = [127.5, 127.5, 95.5]
> RenderView1.CameraClippingRange = [590.4255376821416, 1039.4068896438118]
> RenderView1.CameraParallelScale = 204.0410497914574
>
> Threshold1 = Threshold()
> Threshold1.Scalars = ['POINTS', 'crack']
> Threshold1.AllScalars = 0
> Threshold1.ThresholdRange = [ trlo, trhi ]
>
> DataRepresentation2 = Show()
> DataRepresentation2.EdgeColor = [0.0, 0.0, 0.5000076295109483]
> DataRepresentation2.SelectionPointFieldDataArrayName = 'crack'
> DataRepresentation2.ColorArrayName = ('POINT_DATA', 'crack')
> DataRepresentation2.ScalarOpacityUnitDistance = 1.88988157484231
> DataRepresentation2.ScaleFactor = 0.2
>
> a1_crack_PVLookupTable = GetLookupTableForArray( "crack", 1,
> RGBPoints=[-3.0, 0.23, 0.299, 0.754, 1073741822.0, 0.865, 0.865, 0.865,
> 2147483647.0, 0.706, 0.016, 0.15], VectorMode='Magnitude', NanColor=[0.25,
> 0.0, 0.0], ColorSpace='Diverging', ScalarRangeInitialized=1.0 )
>
> a1_crack_PiecewiseFunction = CreatePiecewiseFunction( Points=[-3.0, 0.0,
> 0.5, 0.0, 2147483647.0, 1.0, 0.5, 0.0] )
>
> DataRepresentation2.ScalarOpacityFunction = a1_crack_PiecewiseFunction
> DataRepresentation2.LookupTable = a1_crack_PVLookupTable
>
> a1_crack_PVLookupTable.NanColor = [1.0, 1.0, 0.0]
> a1_crack_PVLookupTable.RGBPoints = [-3.0, 1.0, 1.0, 1.0, 365072217.5, 0.0,
> 0.0, 1.0, 730144438.0, 0.0, 1.0, 1.0, 1073741822.0, 0.0, 1.0, 0.0,
> 1438814042.5, 1.0, 1.0, 0.0, 1803886263.0, 1.0, 0.0, 0.0, 2147483647.0,
> 0.878431, 0.0, 1.0]
> a1_crack_PVLookupTable.ScalarOpacityFunction = a1_crack_PiecewiseFunction
> a1_crack_PVLookupTable.ColorSpace = 'RGB'
>
> RenderView1.CameraPosition = [127.49999999999966, 127.5, 883.8540000000002]
> RenderView1.CameraClippingRange = [590.4254600000002, 1039.4068100000004]
>
> # custom background
>
> RenderView1.UseGradientBackground = 1
> RenderView1.Background2 = [0.0, 0.0, 0.17254901960784313]
> RenderView1.Background = [0.32941176470588235, 0.34901960784313724,
> 0.42745098039215684]
>
> AnimationScene1.AnimationTime = 10.0
> AnimationScene1.NumberOfFrames = 100
> AnimationScene1.PlayMode = 'Sequence'
>
> CameraAnimationCue1 = GetCameraTrack()
> CameraAnimationCue1.AnimatedProxy = RenderView1
> CameraAnimationCue1.Mode = 'Path-based'
>
> TimeAnimationCue1 = GetTimeTrack()
> #TimeAnimationCue1.Enabled = 0
>
> AnimationScene1.NumberOfFrames = 100
> AnimationScene1.PlayMode = 'Sequence'
>
> KeyFrame3658 = CameraKeyFrame( FocalPathPoints=[127.5, 127.5, 95.5],
> FocalPoint=[127.5, 127.5, 95.5], PositionPathPoints=[127.5, 127.5, 883.854,
> 740.1661272984488, 127.5, 591.6272475657036, 898.6265736288988, 127.5,
> -68.40801310294381, 485.4052264316708, 127.5, -606.9285573699966,
> -193.1524595153794, 127.5, -624.6972157143753, -633.9914888582924, 127.5,
> -108.54102948275286, -510.2917835834677, 127.5, 558.8828547857805],
> ClosedPositionPath=1, ParallelScale=204.0410497914574, Position=[127.5,
> 127.5, 883.8540784668097] )
>
> KeyFrame3659 = CameraKeyFrame( ParallelScale=204.0410497914574,
> Position=[127.5, 127.5, 883.8540784668097], KeyTime=1.0, FocalPoint=[127.5,
> 127.5, 95.5] )
>
> CameraAnimationCue1.KeyFrames = [ KeyFrame3658, KeyFrame3659 ]
> WriteAnimation( vidfile , Magnification=1, Quality=2, FrameRate=6.000000)
>
> Render()
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140724/e14fb673/attachment.html>

From mexas at bris.ac.uk  Thu Jul 24 08:02:01 2014
From: mexas at bris.ac.uk (Anton Shterenlikht)
Date: Thu, 24 Jul 2014 13:02:01 +0100 (BST)
Subject: [Paraview] pvbatch: python - help make animation window bigger
In-Reply-To: <CAOCDKs90bxKqbVffqUt9W8_Fm50=_bEtOicy9F-2Qwb=MTWcDw@mail.gmail.com>
Message-ID: <201407241202.s6OC21Yg096341@mech-cluster241.men.bris.ac.uk>

>From paraview-bounces at paraview.org Thu Jul 24 12:40:35 2014
>
>Hi Anton,
>
>RenderView1.ViewSize = [1000, 1000]

cool, thanks.

Where is this documented?

Or this:

KeyFrame3658 = CameraKeyFrame( FocalPathPoints=[127.5, 127.5, 95.5], FocalPoint=[127.5, 127.5, 95.5], PositionPathPoints=[127.5, 127.5, 883.854, 740.1661272984488, 127.5, 591.6272475657036, 898.6265736288988, 127.5, -68.40801310294381, 485.4052264316708, 127.5, -606.9285573699966, -193.1524595153794, 127.5, -624.6972157143753, -633.9914888582924, 127.5, -108.54102948275286, -510.2917835834677, 127.5, 558.8828547857805], ClosedPositionPath=1, ParallelScale=204.0410497914574, Position=[127.5, 127.5, 883.8540784668097] )

I really have no idea of what's going on here.

Thanks

Anton

From andy.bauer at kitware.com  Thu Jul 24 08:50:38 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 24 Jul 2014 08:50:38 -0400
Subject: [Paraview] pvbatch: python - help make animation window bigger
In-Reply-To: <201407241202.s6OC21Yg096341@mech-cluster241.men.bris.ac.uk>
References: <CAOCDKs90bxKqbVffqUt9W8_Fm50=_bEtOicy9F-2Qwb=MTWcDw@mail.gmail.com>
 <201407241202.s6OC21Yg096341@mech-cluster241.men.bris.ac.uk>
Message-ID: <CAMaOp+Gd9Zxjmjec6V7thUwNv0yHG9By3Rm4U1pHvZi3Sd11=g@mail.gmail.com>

You should be able to do a help() on those objects to get more information.
Additionally there is some Python documentation at
http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/.

Finally, the ParaView GUI trace option is a good way to get familiar with
ParaView's Python API.

Regards,
Andy


On Thu, Jul 24, 2014 at 8:02 AM, Anton Shterenlikht <mexas at bris.ac.uk>
wrote:

> >From paraview-bounces at paraview.org Thu Jul 24 12:40:35 2014
> >
> >Hi Anton,
> >
> >RenderView1.ViewSize = [1000, 1000]
>
> cool, thanks.
>
> Where is this documented?
>
> Or this:
>
> KeyFrame3658 = CameraKeyFrame( FocalPathPoints=[127.5, 127.5, 95.5],
> FocalPoint=[127.5, 127.5, 95.5], PositionPathPoints=[127.5, 127.5, 883.854,
> 740.1661272984488, 127.5, 591.6272475657036, 898.6265736288988, 127.5,
> -68.40801310294381, 485.4052264316708, 127.5, -606.9285573699966,
> -193.1524595153794, 127.5, -624.6972157143753, -633.9914888582924, 127.5,
> -108.54102948275286, -510.2917835834677, 127.5, 558.8828547857805],
> ClosedPositionPath=1, ParallelScale=204.0410497914574, Position=[127.5,
> 127.5, 883.8540784668097] )
>
> I really have no idea of what's going on here.
>
> Thanks
>
> Anton
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140724/59969ba6/attachment.html>

From ainswort at slac.stanford.edu  Thu Jul 24 13:45:56 2014
From: ainswort at slac.stanford.edu (Ainsworth, Robert)
Date: Thu, 24 Jul 2014 10:45:56 -0700
Subject: [Paraview] Plotting an extracted selection
References: <5F08C9AE-A05D-4E3C-B052-99F5315CF1D8@slac.stanford.edu>
Message-ID: <CDB70745-A66B-4D45-95BE-C5B218140620@slac.stanford.edu>

Hi,

I am having difficult trying to plot an extracted selection. My workflow is to open the mesh and data using the SLACTools plugin. Then extract a block and then select cells and perform extract selection.

If I save the data of the extracted selection as a csv and plot two variables against each other I get the expected results. However, if I try to use the plot data filter on the same extracted selection I get unexpected results. Essentially, the plot data filter for the same two variables plots far two many data points and the data doesn?t seem to make sense. The bounds of the data seems right thought. I do not understand why the paraview plot and saving as a file and plotting gives different results?

I am using Paraview 4.1.0 on Mac.

Any help would be much appreciated.

Thanks,
Rob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140724/cb7296a6/attachment.html>

From kmorel at sandia.gov  Thu Jul 24 19:52:52 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 24 Jul 2014 23:52:52 +0000
Subject: [Paraview] problem on the max field value over time
In-Reply-To: <49cf911f.7d84.147627793f0.Coremail.linzhenhua@163.com>
Message-ID: <CFF6F828.19E5D%kmorel@sandia.gov>

Uh, oh. That's not right.

I've submitted a bug report about this problem with descriptive statistics (http://www.paraview.org/Bug/view.php?id=14886). Thanks for reporting the problem.

-Ken

From: linzhenhua <linzhenhua at 163.com<mailto:linzhenhua at 163.com>>
Date: Wednesday, July 23, 2014 3:05 AM
To: "Paraview at paraview.org<mailto:Paraview at paraview.org>" <Paraview at paraview.org<mailto:Paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] problem on the max field value over time

Hi,

I want to plot the temporal variation of the maximum field value over time. I use two methods and the results are different in paraview.

The first method is to use the Descriptive statistics filter (Green line). The second method is to use the Find data tool(orange line). It seems to me that the latter one is more reasonable as the max field value should decrease with time. The result from the find data tool also agree with the scale data range.

Does this mean that there is a bug in Descriptive Statistics filter?
[cid:6339d95f$2$147627793ee$Coremail$linzhenhua$163.com]



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140724/8084285a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: max.png
Type: image/png
Size: 37227 bytes
Desc: max.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140724/8084285a/attachment-0001.png>

From dkxls23 at gmail.com  Fri Jul 25 09:03:01 2014
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Fri, 25 Jul 2014 16:03:01 +0300
Subject: [Paraview] Multiple Domains with XDMF
In-Reply-To: <53AB04CD.7090703@ices.utexas.edu>
References: <53AB04CD.7090703@ices.utexas.edu>
Message-ID: <53D25585.4040901@gmail.com>

I faced some weeks ago essentially the same problem. I can just 
recommend you to write separate files for each grid  (if somehow 
possible), it will save you a lot of trouble in many perspectives.

-Armin

P.S.: With ParaView state files you can still "load" several files, i.e. 
grids, at the same time - a very handy feature. ;)




On 06/25/2014 08:20 PM, Truman Ellis wrote:
> I essentially have two grids with different solution variables defined
> on each one. I am using the XDMF format to output the data. When I
> create a spatial collection of the two grids, the solution variables
> show up as "partial" data in Paraview. Say solution variable u lives on
> grid 1 while f lives on grid 2. If I color by u, grid 2 shows up as some
> solid color that doesn't go away unless I turn off the block that
> corresponds to grid 2. And vice versa for f.
>
> I read that XDMF supports multiple domains, which sounded like it might
> be the right solution for this problem. But when I load such a mesh into
> Paraview, it only picks up on the last defined domain. It seems like
> having different solution variables on different grids is a common
> problem, so I'm wondering if anyone has a cleaner solution than
> selectively turning on and off the blocks corresponding to the solution
> variable I am currently considering.
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview


From denis.cohen at gmail.com  Fri Jul 25 09:26:03 2014
From: denis.cohen at gmail.com (denis cohen)
Date: Fri, 25 Jul 2014 15:26:03 +0200
Subject: [Paraview] box "Coordinate Results" in Calculator not in version
	4.1.0
Message-ID: <CAKf_S2+s0SY1LyxSavqjZO1wnsL9SBYV-0HneKVxoUJKiE1F6g@mail.gmail.com>

Hi,
It looks like the box "Coordinate Results" in the calculator is no longer
there in version 4.1.0 (was present in 4.0.1).
How do I replace ticking this box?
Thanks
Denis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140725/3a9c1d43/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jul 25 09:28:09 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 25 Jul 2014 09:28:09 -0400
Subject: [Paraview] box "Coordinate Results" in Calculator not in
	version 4.1.0
In-Reply-To: <CAKf_S2+s0SY1LyxSavqjZO1wnsL9SBYV-0HneKVxoUJKiE1F6g@mail.gmail.com>
References: <CAKf_S2+s0SY1LyxSavqjZO1wnsL9SBYV-0HneKVxoUJKiE1F6g@mail.gmail.com>
Message-ID: <CADHSJjDQ80Wv177UmnvQ+DUP98-C5fgz2Tzh-YHcWX3Ti7frdA@mail.gmail.com>

Denis,

It's an "advanced" property now, either search for it or hit the
"gear" and you'll see it.

http://www.kitware.com/blog/home/post/491

Utkarsh




On Fri, Jul 25, 2014 at 9:26 AM, denis cohen <denis.cohen at gmail.com> wrote:
> Hi,
> It looks like the box "Coordinate Results" in the calculator is no longer
> there in version 4.1.0 (was present in 4.0.1).
> How do I replace ticking this box?
> Thanks
> Denis
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

From qth20 at cam.ac.uk  Fri Jul 25 10:32:55 2014
From: qth20 at cam.ac.uk (Quang Ha)
Date: Fri, 25 Jul 2014 15:32:55 +0100
Subject: [Paraview]  Create 4D Animation from sets of 3D Data
In-Reply-To: <53D26A3A.9020102@cam.ac.uk>
References: <53D26329.4030704@cam.ac.uk> <53D26A3A.9020102@cam.ac.uk>
Message-ID: <53D26A97.3080705@cam.ac.uk>

Hi,

I have a group of 10 data sets of the left ventricle at different 
cardiac phases. They have been 3D reconstructed using segmentation 
method. Now I am trying to use ParaView to see the dynamic changes over 
different cardiac phases.

I have been able to get to the View -> Animation mode and add each 3D 
data at different time, but they only show me a jump from one data to 
another, rather than 'deforming' into another. I have done some searches 
on the internet and found someone suggesting the use of 'Temporal 
Interpolator' but failed to utilise it.

Would anyone be kind enough to give me some advices on this, please?

Thanks,
Quang

From david.thompson at kitware.com  Fri Jul 25 11:40:09 2014
From: david.thompson at kitware.com (David Thompson)
Date: Fri, 25 Jul 2014 11:40:09 -0400
Subject: [Paraview] problem on the max field value over time
In-Reply-To: <CFF6F828.19E5D%kmorel@sandia.gov>
References: <CFF6F828.19E5D%kmorel@sandia.gov>
Message-ID: <54234052-AF9F-4D79-8602-AB8EF454034B@kitware.com>

> Uh, oh. That's not right.

When you run the descriptive statistics filter, are you running on all of the data or a subsample (I believe a subsample is the default)?

	David

> 
> I've submitted a bug report about this problem with descriptive statistics (http://www.paraview.org/Bug/view.php?id=14886). Thanks for reporting the problem.
> 
> -Ken
> 
> From: linzhenhua <linzhenhua at 163.com>
> Date: Wednesday, July 23, 2014 3:05 AM
> To: "Paraview at paraview.org" <Paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] problem on the max field value over time
> 
> Hi,
> 
> I want to plot the temporal variation of the maximum field value over time. I use two methods and the results are different in paraview.
> 
> The first method is to use the Descriptive statistics filter (Green line). The second method is to use the Find data tool(orange line). It seems to me that the latter one is more reasonable as the max field value should decrease with time. The result from the find data tool also agree with the scale data range.
> 
> Does this mean that there is a bug in Descriptive Statistics filter?
> <max.png>
> 
> 
> 
> <max.png>_______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview


From pierre.kestener at cea.fr  Fri Jul 25 19:07:00 2014
From: pierre.kestener at cea.fr (KESTENER Pierre)
Date: Fri, 25 Jul 2014 23:07:00 +0000
Subject: [Paraview] Building Piston
Message-ID: <123B4248067C9C49ABB98E5EA3F72B242613298F@E-EXDAGE-A1.extra.cea.fr>

Hello Praveen,

I faced the same problem as you when trying to build Piston standalone sources today.

you probably have found out by now, but just to let other people know, piston standalone must be configured like this

ccmake -DCUDA_NVCC_FLAGS=" -gencode=arch=compute_30,code=sm_30 -DTHRUST_DEVICE_BACKEND=THRUST_DEVICE_BACKEND_CUDA" ..

this is because THRUST_DEVICE_BACKEND is unset by default that error like

    error: invalid redeclaration of type name "float3"

raises from piston_math.h

So for paraview point of view, piston_math.h must be either modified or parsed with
 THRUST_DEVICE_BACKEND=THRUST_DEVICE_BACKEND_CUDA




I also noticed that thrust interface used in piston standalone is quite old
thrust::detail::default_device_space_tag must be replaced by thrust::device_space_tag

to build, but it is deprecated. I think that someone more skilled than me in thrust details could refresh a bit piston sources.

At least, it working with these small changes.


Pierre.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140725/3b6e5dac/attachment.html>

From linzhenhua at 163.com  Fri Jul 25 23:01:20 2014
From: linzhenhua at 163.com (linzhenhua)
Date: Sat, 26 Jul 2014 11:01:20 +0800 (CST)
Subject: [Paraview] problem on the max field value over time
In-Reply-To: <54234052-AF9F-4D79-8602-AB8EF454034B@kitware.com>
References: <CFF6F828.19E5D%kmorel@sandia.gov>
 <54234052-AF9F-4D79-8602-AB8EF454034B@kitware.com>
Message-ID: <4b6607d.b6f9.147709d9107.Coremail.linzhenhua@163.com>

When I run the descriptive statistics filter, I do not find the option to subsample the data, so I think it is applied to the whole dataset.


At 2014-07-25 11:40:09, "David Thompson" <david.thompson at kitware.com> wrote:
>> Uh, oh. That's not right.
>
>When you run the descriptive statistics filter, are you running on all of the data or a subsample (I believe a subsample is the default)?
>
>	David
>
>> 
>> I've submitted a bug report about this problem with descriptive statistics (http://www.paraview.org/Bug/view.php?id=14886). Thanks for reporting the problem.
>> 
>> -Ken
>> 
>> From: linzhenhua <linzhenhua at 163.com>
>> Date: Wednesday, July 23, 2014 3:05 AM
>> To: "Paraview at paraview.org" <Paraview at paraview.org>
>> Subject: [EXTERNAL] [Paraview] problem on the max field value over time
>> 
>> Hi,
>> 
>> I want to plot the temporal variation of the maximum field value over time. I use two methods and the results are different in paraview.
>> 
>> The first method is to use the Descriptive statistics filter (Green line). The second method is to use the Find data tool(orange line). It seems to me that the latter one is more reasonable as the max field value should decrease with time. The result from the find data tool also agree with the scale data range.
>> 
>> Does this mean that there is a bug in Descriptive Statistics filter?
>> <max.png>
>> 
>> 
>> 
>> <max.png>_______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140726/498f29fa/attachment-0001.html>

From dave.demarle at kitware.com  Fri Jul 25 23:17:58 2014
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 25 Jul 2014 23:17:58 -0400
Subject: [Paraview] Create 4D Animation from sets of 3D Data
In-Reply-To: <53D26A97.3080705@cam.ac.uk>
References: <53D26329.4030704@cam.ac.uk> <53D26A3A.9020102@cam.ac.uk>
 <53D26A97.3080705@cam.ac.uk>
Message-ID: <CANjZAi93zwrOPbAR0gnvm0sGyYek3XGpJpwDABfr07umNXebaA@mail.gmail.com>

1) What file format are the 10 data sets in?
2) do all meshes have the same number of points and cells and do the come
in the same order in every timstep? temporal interpolation requires a 1:1
correspondence so that it knows what to interpolate between.


On Friday, July 25, 2014, Quang Ha <qth20 at cam.ac.uk> wrote:

> Hi,
>
> I have a group of 10 data sets of the left ventricle at different cardiac
> phases. They have been 3D reconstructed using segmentation method. Now I am
> trying to use ParaView to see the dynamic changes over different cardiac
> phases.
>
> I have been able to get to the View -> Animation mode and add each 3D data
> at different time, but they only show me a jump from one data to another,
> rather than 'deforming' into another. I have done some searches on the
> internet and found someone suggesting the use of 'Temporal Interpolator'
> but failed to utilise it.
>
> Would anyone be kind enough to give me some advices on this, please?
>
> Thanks,
> Quang
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>


-- 
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140725/aa955490/attachment.html>

From qth20 at cam.ac.uk  Sat Jul 26 01:34:46 2014
From: qth20 at cam.ac.uk (Quang-Thinh Ha)
Date: Sat, 26 Jul 2014 06:34:46 +0100
Subject: [Paraview] Create 4D Animation from sets of 3D Data
Message-ID: <E1XAud6-0007Pg-jc@ppsw-40.csi.cam.ac.uk>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140726/39371927/attachment.html>

From sebastien.jourdain at kitware.com  Sun Jul 27 11:51:43 2014
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Sun, 27 Jul 2014 09:51:43 -0600
Subject: [Paraview] Gatekeeper review
Message-ID: <CABObKxfO+ZQ9K5GK5nPBj=nhmXOqNe6-SDKyeQKYG=XPJBwzmw@mail.gmail.com>

SUMMARY
---------------------------------------------
Topics merged into master:
        14888_fix_state_loading_for_domains
(VTK)   pvweb-visualizer-widgets


---------------------------------------------
Topics reverted from next:
  widen_properties_panel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140727/c1eab00a/attachment.html>

From kmorel at sandia.gov  Sun Jul 27 17:48:04 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Sun, 27 Jul 2014 21:48:04 +0000
Subject: [Paraview] problem on the max field value over time
In-Reply-To: <54234052-AF9F-4D79-8602-AB8EF454034B@kitware.com>
References: <CFF6F828.19E5D%kmorel@sandia.gov>,
 <54234052-AF9F-4D79-8602-AB8EF454034B@kitware.com>
Message-ID: <41FE41B0-6467-4C7A-9818-1F5419CA743E@sandia.gov>

I added a response note to the bug report. 

-Ken

Sent from my iPad so blame autocorrect.

On Jul 25, 2014, at 9:40 AM, "David Thompson" <david.thompson at kitware.com> wrote:

>> Uh, oh. That's not right.
> 
> When you run the descriptive statistics filter, are you running on all of the data or a subsample (I believe a subsample is the default)?
> 
>    David
> 
>> 
>> I've submitted a bug report about this problem with descriptive statistics (http://www.paraview.org/Bug/view.php?id=14886). Thanks for reporting the problem.
>> 
>> -Ken
>> 
>> From: linzhenhua <linzhenhua at 163.com>
>> Date: Wednesday, July 23, 2014 3:05 AM
>> To: "Paraview at paraview.org" <Paraview at paraview.org>
>> Subject: [EXTERNAL] [Paraview] problem on the max field value over time
>> 
>> Hi,
>> 
>> I want to plot the temporal variation of the maximum field value over time. I use two methods and the results are different in paraview.
>> 
>> The first method is to use the Descriptive statistics filter (Green line). The second method is to use the Find data tool(orange line). It seems to me that the latter one is more reasonable as the max field value should decrease with time. The result from the find data tool also agree with the scale data range.
>> 
>> Does this mean that there is a bug in Descriptive Statistics filter?
>> <max.png>
>> 
>> 
>> 
>> <max.png>_______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
> 

From tristan.schloegl at ltd.uni-erlangen.de  Mon Jul 28 08:37:57 2014
From: tristan.schloegl at ltd.uni-erlangen.de (Tristan =?ISO-8859-1?B?U2NobPZnbA==?=)
Date: Mon, 28 Jul 2014 14:37:57 +0200
Subject: [Paraview] Clean Grid and Average Point Data
Message-ID: <CFFC10C5.283A%tristan.schloegl@ltd.uni-erlangen.de>

Hi,

I'm using ParaView to visualise finite element simulation results created by
the deal.ii C++ library. Deal.ii outputs hex elements such that each element
has its own vertices. To illustrate that point a simple cube consisting of 8
elements and 27 nodes has 8*8=64 data points. When I display vector valued
data as glyphs I have multiple vectors at the same location resulting from
the contributions of neighbouring cells, see
http://blogs.fau.de/schloegl/files/2014/07/orig_grid.png .

I now want to display only a single vector at each point, namely the average
value of all contributions. I tried and applied a "Clean to Grid" filter,
see
http://blogs.fau.de/schloegl/files/2014/07/clean_grid.png .
This is quite good already however, it seems that ParaView only takes one of
the vectors for each point and not the average (see top mid vector of the
front (z-max) face).

Is there any other way to realise what I need in ParaView?

Regards
Tristan


-- 
Dipl.-Ing. Tristan Schl?gl
Chair of Applied Dynamics
University of Erlangen-Nuremberg
Haberstrasse 1
D-91058 Erlangen, Germany
room 01.013
phone +49 (0)9131 85 61003
fax +49 (0)9131 85 61011
url www.ltd.tf.uni-erlangen.de


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/54c9e8f6/attachment.html>

From andy.bauer at kitware.com  Mon Jul 28 10:38:32 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 28 Jul 2014 10:38:32 -0400
Subject: [Paraview] Clean Grid and Average Point Data
In-Reply-To: <CFFC10C5.283A%tristan.schloegl@ltd.uni-erlangen.de>
References: <CFFC10C5.283A%tristan.schloegl@ltd.uni-erlangen.de>
Message-ID: <CAMaOp+HaVNNBYnenCKX7Ahi9qQeM+55Sq5QxYhWEASOBoNfcDw@mail.gmail.com>

Hi Tristan,

There are a couple of things you can try. The best but most complex is
probably the programmable filter where you merge the points yourself and do
the averaging for the point values. The other thing you can try is using
the point data to cell data filter, then use the clean to grid filter and
finally use the cell data to point data filter. This may due more averaging
than you would like for your results. Other than that, did you get any
feedback on the deal.II mailing list?

Regards,
Andy


On Mon, Jul 28, 2014 at 8:37 AM, Tristan Schl?gl <
tristan.schloegl at ltd.uni-erlangen.de> wrote:

> Hi,
>
> I'm using ParaView to visualise finite element simulation results created
> by the deal.ii C++ library. Deal.ii outputs hex elements such that each
> element has its own vertices. To illustrate that point a simple cube
> consisting of 8 elements and 27 nodes has 8*8=64 data points. When I
> display vector valued data as glyphs I have multiple vectors at the same
> location resulting from the contributions of neighbouring cells, see
> http://blogs.fau.de/schloegl/files/2014/07/orig_grid.png .
>
> I now want to display only a single vector at each point, namely the
> average value of all contributions. I tried and applied a "Clean to Grid"
> filter, see
> http://blogs.fau.de/schloegl/files/2014/07/clean_grid.png .
> This is quite good already however, it seems that ParaView only takes one
> of the vectors for each point and not the average (see top mid vector of
> the front (z-max) face).
>
> Is there any other way to realise what I need in ParaView?
>
> Regards
> Tristan
>
>
> --
> Dipl.-Ing. Tristan Schl?gl
> Chair of Applied Dynamics
> University of Erlangen-Nuremberg
> Haberstrasse 1
> D-91058 Erlangen, Germany
> room 01.013
> phone +49 (0)9131 85 61003
> fax +49 (0)9131 85 61011
> url www.ltd.tf.uni-erlangen.de
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/4d8fed9d/attachment-0001.html>

From jordimoliner94 at gmail.com  Mon Jul 28 10:42:12 2014
From: jordimoliner94 at gmail.com (Jordi Moliner)
Date: Mon, 28 Jul 2014 16:42:12 +0200
Subject: [Paraview] Change the SplineSource resolution from Python shell
Message-ID: <CANsX4B3RR9B5Uf5vd2wirKjp5Q7X639hy-vAj5bwJt6MmNtz5A@mail.gmail.com>

Hello ParaView users!

I am quite a newbie in the world of Paraview and Python.

I am trying to create a spline from a list of points in paraview.
I have created a little script so paraview can read my list of points and
creates the spline.

The problem is that no matter how many points I put as an input, the spline
is always composed of 51 points.
So if I put 4 points I'll get a spline resolution of 51 points, and if I
put 400 I'll get a resolution of 51 points too.
Does anybody know how to change the spline resolution ?

Afterwards I'd like to calculate the length of this spline. Is it possible
to get this result from paraview ?

Thanks to everyone,

Jordi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/878ddba9/attachment.html>

From kmorel at sandia.gov  Mon Jul 28 10:46:16 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 28 Jul 2014 14:46:16 +0000
Subject: [Paraview] Create 4D Animation from sets of 3D Data
In-Reply-To: <E1XAud6-0007Pg-jc@ppsw-40.csi.cam.ac.uk>
Message-ID: <CFFBBB1C.19F0B%kmorel@sandia.gov>

Quang,

First before answering your question, let me alert you to an easier way to load your data into ParaView. First, name your files with numbers just before the extension (e.g. left_ventricle_00.stl, left_ventricle_01.stl, left_ventricle_02.stl, etc.). Then just load this file series as one unit (they will be grouped in the ParaView file browser) and ParaView will automatically animate them; no need to add them manually with the Animation View.

Now the bad news. I don't think the Temporal Interpolator is going to work with your data. The Temporal Interpolator needs a way to register where a point in one time step goes to in the next time step. It does this in a very simplistic way by assuming the topology is consistent across time steps. That is, each data set has the exact same triangles listed in the same order connected the same way but at different positions. The surface from your segmentation is surely not of this nature.

-Ken

From: Quang-Thinh Ha <qth20 at cam.ac.uk<mailto:qth20 at cam.ac.uk>>
Date: Friday, July 25, 2014 11:34 PM
To: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Cc: paraview-help <paraview-help at sandia.gov<mailto:paraview-help at sandia.gov>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Create 4D Animation from sets of 3D Data


Hi,

Thanks for your reply.

1) The data sets are all in STL format.

2) I am not very sure about this. After using text editor to open the mesh file I can say that they are not... Is there anyway to change this?

Quang

On 26 Jul 2014 04:17, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:
1) What file format are the 10 data sets in?
2) do all meshes have the same number of points and cells and do the come in the same order in every timstep? temporal interpolation requires a 1:1 correspondence so that it knows what to interpolate between.


On Friday, July 25, 2014, Quang Ha <qth20 at cam.ac.uk<mailto:qth20 at cam.ac.uk>> wrote:
Hi,

I have a group of 10 data sets of the left ventricle at different cardiac phases. They have been 3D reconstructed using segmentation method. Now I am trying to use ParaView to see the dynamic changes over different cardiac phases.

I have been able to get to the View -> Animation mode and add each 3D data at different time, but they only show me a jump from one data to another, rather than 'deforming' into another. I have done some searches on the internet and found someone suggesting the use of 'Temporal Interpolator' but failed to utilise it.

Would anyone be kind enough to give me some advices on this, please?

Thanks,
Quang
_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview


--
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/cd52d7e2/attachment.html>

From david.thompson at kitware.com  Mon Jul 28 10:52:14 2014
From: david.thompson at kitware.com (David Thompson)
Date: Mon, 28 Jul 2014 10:52:14 -0400
Subject: [Paraview] problem on the max field value over time
In-Reply-To: <4b6607d.b6f9.147709d9107.Coremail.linzhenhua@163.com>
References: <CFF6F828.19E5D%kmorel@sandia.gov>
 <54234052-AF9F-4D79-8602-AB8EF454034B@kitware.com>
 <4b6607d.b6f9.147709d9107.Coremail.linzhenhua@163.com>
Message-ID: <2E3F1DA4-0352-435E-B6C7-644525521DF6@kitware.com>

Hi,

> When I run the descriptive statistics filter, I do not find the option to subsample the data, so I think it is applied to the whole dataset.

The option is called "Training Fraction" and should be 1.0 if you want the description to include all of the data.

	David

From qth20 at cam.ac.uk  Mon Jul 28 11:25:08 2014
From: qth20 at cam.ac.uk (Quang Ha)
Date: Mon, 28 Jul 2014 16:25:08 +0100
Subject: [Paraview] Create 4D Animation from sets of 3D Data
In-Reply-To: <CFFBBB1C.19F0B%kmorel@sandia.gov>
References: <CFFBBB1C.19F0B%kmorel@sandia.gov>
Message-ID: <53D66B54.9040802@cam.ac.uk>

Hi,

Thank you very much for your reply. It seems that I would have to deal 
with the input data once again.

Is there a way for the surface to be modified in such way that you have 
stated? Would you suggested starting to look at vtk/CGAL codes or 
something similar?

Best regards,
Quang

On 28/07/14 15:46, Moreland, Kenneth wrote:
> Quang,
>
> First before answering your question, let me alert you to an easier 
> way to load your data into ParaView. First, name your files with 
> numbers just before the extension (e.g. left_ventricle_00.stl, 
> left_ventricle_01.stl, left_ventricle_02.stl, etc.). Then just load 
> this file series as one unit (they will be grouped in the ParaView 
> file browser) and ParaView will automatically animate them; no need to 
> add them manually with the Animation View.
>
> Now the bad news. I don't think the Temporal Interpolator is going to 
> work with your data. The Temporal Interpolator needs a way to register 
> where a point in one time step goes to in the next time step. It does 
> this in a very simplistic way by assuming the topology is consistent 
> across time steps. That is, each data set has the exact same triangles 
> listed in the same order connected the same way but at different 
> positions. The surface from your segmentation is surely not of this 
> nature.
>
> -Ken
>
> From: Quang-Thinh Ha <qth20 at cam.ac.uk <mailto:qth20 at cam.ac.uk>>
> Date: Friday, July 25, 2014 11:34 PM
> To: David E DeMarle <dave.demarle at kitware.com 
> <mailto:dave.demarle at kitware.com>>
> Cc: paraview-help <paraview-help at sandia.gov 
> <mailto:paraview-help at sandia.gov>>, "paraview at paraview.org 
> <mailto:paraview at paraview.org>" <paraview at paraview.org 
> <mailto:paraview at paraview.org>>
> Subject: [EXTERNAL] Re: [Paraview] Create 4D Animation from sets of 3D 
> Data
>
> Hi,
>
> Thanks for your reply.
>
> 1) The data sets are all in STL format.
>
> 2) I am not very sure about this. After using text editor to open the 
> mesh file I can say that they are not... Is there anyway to change this?
>
> Quang
>
> On 26 Jul 2014 04:17, David E DeMarle <dave.demarle at kitware.com 
> <mailto:dave.demarle at kitware.com>> wrote:
>
>     1) What file format are the 10 data sets in?
>     2) do all meshes have the same number of points and cells and do
>     the come in the same order in every timstep? temporal
>     interpolation requires a 1:1 correspondence so that it knows what
>     to interpolate between.
>
>
>     On Friday, July 25, 2014, Quang Ha <qth20 at cam.ac.uk
>     <mailto:qth20 at cam.ac.uk>> wrote:
>
>         Hi,
>
>         I have a group of 10 data sets of the left ventricle at
>         different cardiac phases. They have been 3D reconstructed
>         using segmentation method. Now I am trying to use ParaView to
>         see the dynamic changes over different cardiac phases.
>
>         I have been able to get to the View -> Animation mode and add
>         each 3D data at different time, but they only show me a jump
>         from one data to another, rather than 'deforming' into
>         another. I have done some searches on the internet and found
>         someone suggesting the use of 'Temporal Interpolator' but
>         failed to utilise it.
>
>         Would anyone be kind enough to give me some advices on this,
>         please?
>
>         Thanks,
>         Quang
>         _______________________________________________
>         Powered by www.kitware.com <http://www.kitware.com>
>
>         Visit other Kitware open-source projects at
>         http://www.kitware.com/opensource/opensource.html
>         <http://www.kitware.com/opensource/opensource.html>
>
>         Please keep messages on-topic and check the ParaView Wiki at:
>         http://paraview.org/Wiki/ParaView
>         <http://paraview.org/Wiki/ParaView>
>
>         Follow this link to subscribe/unsubscribe:
>         http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>     -- 
>     David E DeMarle
>     Kitware, Inc.
>     R&D Engineer
>     21 Corporate Drive
>     Clifton Park, NY 12065-8662
>     Phone: 518-881-4909
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/9aa8a6e1/attachment-0001.html>

From simon.m.su.ctr at mail.mil  Mon Jul 28 11:49:22 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Mon, 28 Jul 2014 15:49:22 +0000
Subject: [Paraview] what python library to use when compiling ParaView using
 windows 7 64bit VS2013 express (UNCLASSIFIED)
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F5D@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hello,

When I used WinPython-64bit-2.7.6.4 (which allows installation of Python
library without admin rights but has no python debug library) library to
compile ParaView with VS2013 express edition, I get this tons of warning
messages. Search the web, someone mentioned WinPython-64bit-2.7.6.4 wasn't
compiled with VS2013 express edition and I shouldn't be using library
compiled with one Visual Studio version in another version of VS. 

Is compiling a version of python from source code using vs2013 express the
only way available to me? Or is there python library compiled with vs2013
express out there that I am yet to find? Or can I just ignore the warning
messages in VS2013 express?

Any help is much appreciated

Thanks
-simon



Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 9990 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/6220372e/attachment.bin>

From utkarsh.ayachit at kitware.com  Mon Jul 28 12:08:45 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 28 Jul 2014 12:08:45 -0400
Subject: [Paraview] what python library to use when compiling ParaView
 using windows 7 64bit VS2013 express (UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F5D@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F5D@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjBAk_f87k=-OViErkG3GaH+FyDuO1XP=AUeVF+1SEy7sQ@mail.gmail.com>

You could build ParaView  as a "Release" (rather than Debug) and then
you should not get those warnings, I think.



On Mon, Jul 28, 2014 at 11:49 AM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hello,
>
> When I used WinPython-64bit-2.7.6.4 (which allows installation of Python
> library without admin rights but has no python debug library) library to
> compile ParaView with VS2013 express edition, I get this tons of warning
> messages. Search the web, someone mentioned WinPython-64bit-2.7.6.4 wasn't
> compiled with VS2013 express edition and I shouldn't be using library
> compiled with one Visual Studio version in another version of VS.
>
> Is compiling a version of python from source code using vs2013 express the
> only way available to me? Or is there python library compiled with vs2013
> express out there that I am yet to find? Or can I just ignore the warning
> messages in VS2013 express?
>
> Any help is much appreciated
>
> Thanks
> -simon
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

From simon.m.su.ctr at mail.mil  Mon Jul 28 12:21:24 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Mon, 28 Jul 2014 16:21:24 +0000
Subject: [Paraview] what python library to use when compiling ParaView
 using windows 7 64bit VS2013 express (UNCLASSIFIED)
In-Reply-To: <CADHSJjBAk_f87k=-OViErkG3GaH+FyDuO1XP=AUeVF+1SEy7sQ@mail.gmail.com>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F5D@umechp9h.easf.csd.disa.mil>
 <CADHSJjBAk_f87k=-OViErkG3GaH+FyDuO1XP=AUeVF+1SEy7sQ@mail.gmail.com>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F7C@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Hi Utkarsh,

I am building the release version so, not sure about the warning with Release 
version. Maybe something I didn't do?

On the other hand, can I know what is the combination used to compile the 
windows binary available on the pv 4.1.0 on the website ? 
http://www.paraview.org/Wiki/ParaView/Binaries site mentioned with PV 4.0.x pv 
windows binary was compiled with Visual Studio 2008 x64 9.0.30729.1 SP, 
OpenMPI, v 1.4.4, and python v 2.7.3 (among other things). Was the python v 
2.7.3 used compiled with Visual Studio 2008 x64 9.0.30729.1 SP? If so, what 
python library was used? The binary for python from WinPython-64bit-2.7.6.4 
was compiled with VS2008, is that why VS2008 was picked for pv 4.0.x windows 
compilation?

Thanks
-simon


-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Monday, July 28, 2014 12:09 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] what python library to use when compiling ParaView 
using windows 7 64bit VS2013 express (UNCLASSIFIED)

You could build ParaView  as a "Release" (rather than Debug) and then you 
should not get those warnings, I think.



On Mon, Jul 28, 2014 at 11:49 AM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hello,
>
> When I used WinPython-64bit-2.7.6.4 (which allows installation of
> Python library without admin rights but has no python debug library)
> library to compile ParaView with VS2013 express edition, I get this
> tons of warning messages. Search the web, someone mentioned
> WinPython-64bit-2.7.6.4 wasn't compiled with VS2013 express edition
> and I shouldn't be using library compiled with one Visual Studio version in 
> another version of VS.
>
> Is compiling a version of python from source code using vs2013 express
> the only way available to me? Or is there python library compiled with
> vs2013 express out there that I am yet to find? Or can I just ignore
> the warning messages in VS2013 express?
>
> Any help is much appreciated
>
> Thanks
> -simon
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 9990 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/91c1de79/attachment-0001.bin>

From utkarsh.ayachit at kitware.com  Mon Jul 28 16:24:25 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 28 Jul 2014 16:24:25 -0400
Subject: [Paraview] what python library to use when compiling ParaView
 using windows 7 64bit VS2013 express (UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F7C@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F5D@umechp9h.easf.csd.disa.mil>
 <CADHSJjBAk_f87k=-OViErkG3GaH+FyDuO1XP=AUeVF+1SEy7sQ@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F7C@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjDa-LHjvc5RUW4mPCmu_C2xXdsRNiLse1fXVU+9vpz4tQ@mail.gmail.com>

Simon,

We build our own Python for the binaries we build using the same
compiler as the rest of ParaView. On dashboards, we do use Python
binaries directly from python.org and they work quite well. Did if you
give those a try?

Utkarsh

On Mon, Jul 28, 2014 at 12:21 PM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hi Utkarsh,
>
> I am building the release version so, not sure about the warning with Release
> version. Maybe something I didn't do?
>
> On the other hand, can I know what is the combination used to compile the
> windows binary available on the pv 4.1.0 on the website ?
> http://www.paraview.org/Wiki/ParaView/Binaries site mentioned with PV 4.0.x pv
> windows binary was compiled with Visual Studio 2008 x64 9.0.30729.1 SP,
> OpenMPI, v 1.4.4, and python v 2.7.3 (among other things). Was the python v
> 2.7.3 used compiled with Visual Studio 2008 x64 9.0.30729.1 SP? If so, what
> python library was used? The binary for python from WinPython-64bit-2.7.6.4
> was compiled with VS2008, is that why VS2008 was picked for pv 4.0.x windows
> compilation?
>
> Thanks
> -simon
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Monday, July 28, 2014 12:09 PM
> To: Su, Simon M CTR USARMY ARL (US)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] what python library to use when compiling ParaView
> using windows 7 64bit VS2013 express (UNCLASSIFIED)
>
> You could build ParaView  as a "Release" (rather than Debug) and then you
> should not get those warnings, I think.
>
>
>
> On Mon, Jul 28, 2014 at 11:49 AM, Su, Simon M CTR USARMY ARL (US)
> <simon.m.su.ctr at mail.mil> wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Hello,
>>
>> When I used WinPython-64bit-2.7.6.4 (which allows installation of
>> Python library without admin rights but has no python debug library)
>> library to compile ParaView with VS2013 express edition, I get this
>> tons of warning messages. Search the web, someone mentioned
>> WinPython-64bit-2.7.6.4 wasn't compiled with VS2013 express edition
>> and I shouldn't be using library compiled with one Visual Studio version in
>> another version of VS.
>>
>> Is compiling a version of python from source code using vs2013 express
>> the only way available to me? Or is there python library compiled with
>> vs2013 express out there that I am yet to find? Or can I just ignore
>> the warning messages in VS2013 express?
>>
>> Any help is much appreciated
>>
>> Thanks
>> -simon
>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>

From kmorel at sandia.gov  Mon Jul 28 17:02:39 2014
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 28 Jul 2014 21:02:39 +0000
Subject: [Paraview] Create 4D Animation from sets of 3D Data
In-Reply-To: <53D66B54.9040802@cam.ac.uk>
Message-ID: <CFFBF5A7.19F80%kmorel@sandia.gov>

Image segmentation is not my specialty, but I don't think there is an easy answer. You might be able to use a level set method that starts with the mesh from the first image and constrains the topology to be the same, but that would probably create artifacts that compound over time.

-Ken

From: Quang Ha <qth20 at cam.ac.uk<mailto:qth20 at cam.ac.uk>>
Date: Monday, July 28, 2014 9:25 AM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Cc: paraview-help <paraview-help at sandia.gov<mailto:paraview-help at sandia.gov>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Create 4D Animation from sets of 3D Data

Hi,

Thank you very much for your reply. It seems that I would have to deal with the input data once again.

Is there a way for the surface to be modified in such way that you have stated? Would you suggested starting to look at vtk/CGAL codes or something similar?

Best regards,
Quang

On 28/07/14 15:46, Moreland, Kenneth wrote:
Quang,

First before answering your question, let me alert you to an easier way to load your data into ParaView. First, name your files with numbers just before the extension (e.g. left_ventricle_00.stl, left_ventricle_01.stl, left_ventricle_02.stl, etc.). Then just load this file series as one unit (they will be grouped in the ParaView file browser) and ParaView will automatically animate them; no need to add them manually with the Animation View.

Now the bad news. I don't think the Temporal Interpolator is going to work with your data. The Temporal Interpolator needs a way to register where a point in one time step goes to in the next time step. It does this in a very simplistic way by assuming the topology is consistent across time steps. That is, each data set has the exact same triangles listed in the same order connected the same way but at different positions. The surface from your segmentation is surely not of this nature.

-Ken

From: Quang-Thinh Ha <qth20 at cam.ac.uk<mailto:qth20 at cam.ac.uk>>
Date: Friday, July 25, 2014 11:34 PM
To: David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>>
Cc: paraview-help <paraview-help at sandia.gov<mailto:paraview-help at sandia.gov>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Create 4D Animation from sets of 3D Data


Hi,

Thanks for your reply.

1) The data sets are all in STL format.

2) I am not very sure about this. After using text editor to open the mesh file I can say that they are not... Is there anyway to change this?

Quang

On 26 Jul 2014 04:17, David E DeMarle <dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:
1) What file format are the 10 data sets in?
2) do all meshes have the same number of points and cells and do the come in the same order in every timstep? temporal interpolation requires a 1:1 correspondence so that it knows what to interpolate between.


On Friday, July 25, 2014, Quang Ha <qth20 at cam.ac.uk<mailto:qth20 at cam.ac.uk>> wrote:
Hi,

I have a group of 10 data sets of the left ventricle at different cardiac phases. They have been 3D reconstructed using segmentation method. Now I am trying to use ParaView to see the dynamic changes over different cardiac phases.

I have been able to get to the View -> Animation mode and add each 3D data at different time, but they only show me a jump from one data to another, rather than 'deforming' into another. I have done some searches on the internet and found someone suggesting the use of 'Temporal Interpolator' but failed to utilise it.

Would anyone be kind enough to give me some advices on this, please?

Thanks,
Quang
_______________________________________________
Powered by www.kitware.com<http://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://public.kitware.com/mailman/listinfo/paraview


--
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140728/9c1eca33/attachment.html>

From linzhenhua at 163.com  Mon Jul 28 20:21:44 2014
From: linzhenhua at 163.com (linzhenhua)
Date: Tue, 29 Jul 2014 08:21:44 +0800 (CST)
Subject: [Paraview] problem on the max field value over time
In-Reply-To: <2E3F1DA4-0352-435E-B6C7-644525521DF6@kitware.com>
References: <CFF6F828.19E5D%kmorel@sandia.gov>
 <54234052-AF9F-4D79-8602-AB8EF454034B@kitware.com>
 <4b6607d.b6f9.147709d9107.Coremail.linzhenhua@163.com>
 <2E3F1DA4-0352-435E-B6C7-644525521DF6@kitware.com>
Message-ID: <436beb97.7be.1477f7e8950.Coremail.linzhenhua@163.com>

Thanks David for your guide. This solve my problem.


At 2014-07-28 10:52:14, "David Thompson" <david.thompson at kitware.com> wrote:
>Hi,
>
>> When I run the descriptive statistics filter, I do not find the option to subsample the data, so I think it is applied to the whole dataset.
>
>The option is called "Training Fraction" and should be 1.0 if you want the description to include all of the data.
>
>	David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140729/5c6e61ec/attachment.html>

From tristan.schloegl at ltd.uni-erlangen.de  Tue Jul 29 04:00:49 2014
From: tristan.schloegl at ltd.uni-erlangen.de (Tristan =?ISO-8859-1?B?U2NobPZnbA==?=)
Date: Tue, 29 Jul 2014 10:00:49 +0200
Subject: [Paraview] Clean Grid and Average Point Data
In-Reply-To: <CAMaOp+HaVNNBYnenCKX7Ahi9qQeM+55Sq5QxYhWEASOBoNfcDw@mail.gmail.com>
References: <CFFC10C5.283A%tristan.schloegl@ltd.uni-erlangen.de>
 <CAMaOp+HaVNNBYnenCKX7Ahi9qQeM+55Sq5QxYhWEASOBoNfcDw@mail.gmail.com>
Message-ID: <CFFD1C11.2849%tristan.schloegl@ltd.uni-erlangen.de>

Hi Andy,

thanks for your reply. I tried working with the "point data to cell data"
and "cell data to point data" filters. Indeed, this is too much averaging.
It might be a starting point for only the discontinuous field I'm interested
in, but the filter applies on all data in my model (e.g. I don't want the
continuous displacement field and others to be averaged). Is there a way to
specify only a certain dataset the filter is working on?

Regarding the programmable filter, I'm very new to ParaView internals (I'm
mainly working with the GUI), however I'm a bit experienced with Python. Can
you recommend some tutorial, where I get a quick introduction in how to
access the data and modify it?

I believe dealing with this problem in deal.ii directly requires some
changes in the library itself. Maybe you can also do something with derived
classes. However, having the full information of a discontinuous field, like
deal.ii outputs it, is generally not a bad thing to examine results. I just
sometimes need 'cleaner' pictures and thought that's a post processing task,
best be handled in ParaView.

Tristan


Von:  Andy Bauer <andy.bauer at kitware.com>
Datum:  Montag, 28. Juli 2014 16:38
An:  Tristan Schloegl <tristan.schloegl at ltd.uni-erlangen.de>
Cc:  "Paraview at paraview.org" <Paraview at paraview.org>
Betreff:  Re: [Paraview] Clean Grid and Average Point Data

Hi Tristan,

There are a couple of things you can try. The best but most complex is
probably the programmable filter where you merge the points yourself and do
the averaging for the point values. The other thing you can try is using the
point data to cell data filter, then use the clean to grid filter and
finally use the cell data to point data filter. This may due more averaging
than you would like for your results. Other than that, did you get any
feedback on the deal.II mailing list?

Regards,
Andy


On Mon, Jul 28, 2014 at 8:37 AM, Tristan Schl?gl
<tristan.schloegl at ltd.uni-erlangen.de> wrote:
> Hi,
> 
> I'm using ParaView to visualise finite element simulation results created by
> the deal.ii C++ library. Deal.ii outputs hex elements such that each element
> has its own vertices. To illustrate that point a simple cube consisting of 8
> elements and 27 nodes has 8*8=64 data points. When I display vector valued
> data as glyphs I have multiple vectors at the same location resulting from the
> contributions of neighbouring cells, see
> http://blogs.fau.de/schloegl/files/2014/07/orig_grid.png .
> 
> I now want to display only a single vector at each point, namely the average
> value of all contributions. I tried and applied a "Clean to Grid" filter, see
> http://blogs.fau.de/schloegl/files/2014/07/clean_grid.png .
> This is quite good already however, it seems that ParaView only takes one of
> the vectors for each point and not the average (see top mid vector of the
> front (z-max) face).
> 
> Is there any other way to realise what I need in ParaView?
> 
> Regards
> Tristan
> 
> 
> -- 
> Dipl.-Ing. Tristan Schl?gl
> Chair of Applied Dynamics
> University of Erlangen-Nuremberg
> Haberstrasse 1
> D-91058 Erlangen, Germany
> room 01.013
> phone +49 (0)9131 85 61003 <tel:%2B49%20%280%299131%2085%2061003>
> fax +49 (0)9131 85 61011 <tel:%2B49%20%280%299131%2085%2061011>
> url www.ltd.tf.uni-erlangen.de <http://www.ltd.tf.uni-erlangen.de>
> 
> _______________________________________________
> Powered by www.kitware.com <http://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://public.kitware.com/mailman/listinfo/paraview
> 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140729/567fe906/attachment-0001.html>

From senseiwa at gmail.com  Tue Jul 29 04:10:44 2014
From: senseiwa at gmail.com (Sensei)
Date: Tue, 29 Jul 2014 10:10:44 +0200
Subject: [Paraview] Newbie: adding field plot from another file
In-Reply-To: <CAB5Fpx6+-+CRzGpCbMjF4meAKKzTjTbELHesnT6bFrX_Vbkk=Q@mail.gmail.com>
References: <53CFDA3D.7040701@gmail.com>
 <CAB5Fpx6+-+CRzGpCbMjF4meAKKzTjTbELHesnT6bFrX_Vbkk=Q@mail.gmail.com>
Message-ID: <53D75704.9050100@gmail.com>

On 7/23/14, 6:00pm, Cory Quammen wrote:
> Assuming your two data sets have the same topology, you can try using
> the Append Attributes filter to combine them into a single data set.
> Select the two files in the pipeline browser and select the Append
> Attributes filter.
>
> Hope that helps,
> Cory


Thanks Cory, it worked nicely, thanks! I was under the false assumption 
that the right filter was Append Databases, but I was wrong.

Thank you!


From andy.bauer at kitware.com  Tue Jul 29 09:00:19 2014
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 29 Jul 2014 09:00:19 -0400
Subject: [Paraview] Clean Grid and Average Point Data
In-Reply-To: <CFFD1C11.2849%tristan.schloegl@ltd.uni-erlangen.de>
References: <CFFC10C5.283A%tristan.schloegl@ltd.uni-erlangen.de>
 <CAMaOp+HaVNNBYnenCKX7Ahi9qQeM+55Sq5QxYhWEASOBoNfcDw@mail.gmail.com>
 <CFFD1C11.2849%tristan.schloegl@ltd.uni-erlangen.de>
Message-ID: <CAMaOp+GBfu2006-HR2=ZsYS7mMmy23_cLW2gPYneXjQjVsJ6KQ@mail.gmail.com>

Hi Tristan,

I'm not familiar with deal.II's output format -- could you share a small
sample?

Some other tricks you can try is using the "Pass Point Data" option with
the Point Data to Cell Data filter which will keep your point data around
as well. Then you could use the Pass Arrays filter to get rid of the cell
data that you didn't want generated from the point data before (i.e. the
ones that would overwrite your existing point data when you use the cell
data to point data filter).

As for the programmable filter, you can find more information on it at
http://www.paraview.org/Wiki/Python_Programmable_Filter. There are probably
more examples around the wiki that you can find as well with a little bit
of searching.

Regards,
Andy




On Tue, Jul 29, 2014 at 4:00 AM, Tristan Schl?gl <
tristan.schloegl at ltd.uni-erlangen.de> wrote:

> Hi Andy,
>
> thanks for your reply. I tried working with the "point data to cell data"
> and "cell data to point data" filters. Indeed, this is too much averaging.
> It might be a starting point for only the discontinuous field I'm
> interested in, but the filter applies on all data in my model (e.g. I don't
> want the continuous displacement field and others to be averaged). Is there
> a way to specify only a certain dataset the filter is working on?
>
> Regarding the programmable filter, I'm very new to ParaView internals (I'm
> mainly working with the GUI), however I'm a bit experienced with Python.
> Can you recommend some tutorial, where I get a quick introduction in how to
> access the data and modify it?
>
> I believe dealing with this problem in deal.ii directly requires some
> changes in the library itself. Maybe you can also do something with derived
> classes. However, having the full information of a discontinuous field,
> like deal.ii outputs it, is generally not a bad thing to examine results. I
> just sometimes need 'cleaner' pictures and thought that's a post processing
> task, best be handled in ParaView.
>
> Tristan
>
>
> Von: Andy Bauer <andy.bauer at kitware.com>
> Datum: Montag, 28. Juli 2014 16:38
> An: Tristan Schloegl <tristan.schloegl at ltd.uni-erlangen.de>
> Cc: "Paraview at paraview.org" <Paraview at paraview.org>
> Betreff: Re: [Paraview] Clean Grid and Average Point Data
>
> Hi Tristan,
>
> There are a couple of things you can try. The best but most complex is
> probably the programmable filter where you merge the points yourself and do
> the averaging for the point values. The other thing you can try is using
> the point data to cell data filter, then use the clean to grid filter and
> finally use the cell data to point data filter. This may due more averaging
> than you would like for your results. Other than that, did you get any
> feedback on the deal.II mailing list?
>
> Regards,
> Andy
>
>
> On Mon, Jul 28, 2014 at 8:37 AM, Tristan Schl?gl <
> tristan.schloegl at ltd.uni-erlangen.de> wrote:
>
>> Hi,
>>
>> I'm using ParaView to visualise finite element simulation results created
>> by the deal.ii C++ library. Deal.ii outputs hex elements such that each
>> element has its own vertices. To illustrate that point a simple cube
>> consisting of 8 elements and 27 nodes has 8*8=64 data points. When I
>> display vector valued data as glyphs I have multiple vectors at the same
>> location resulting from the contributions of neighbouring cells, see
>> http://blogs.fau.de/schloegl/files/2014/07/orig_grid.png .
>>
>> I now want to display only a single vector at each point, namely the
>> average value of all contributions. I tried and applied a "Clean to Grid"
>> filter, see
>> http://blogs.fau.de/schloegl/files/2014/07/clean_grid.png .
>> This is quite good already however, it seems that ParaView only takes one
>> of the vectors for each point and not the average (see top mid vector of
>> the front (z-max) face).
>>
>> Is there any other way to realise what I need in ParaView?
>>
>> Regards
>> Tristan
>>
>>
>> --
>> Dipl.-Ing. Tristan Schl?gl
>> Chair of Applied Dynamics
>> University of Erlangen-Nuremberg
>> Haberstrasse 1
>> D-91058 Erlangen, Germany
>> room 01.013
>> phone +49 (0)9131 85 61003
>> fax +49 (0)9131 85 61011
>> url www.ltd.tf.uni-erlangen.de
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140729/5e7d257e/attachment.html>

From simon.m.su.ctr at mail.mil  Tue Jul 29 09:13:46 2014
From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US))
Date: Tue, 29 Jul 2014 13:13:46 +0000
Subject: [Paraview] what python library to use when compiling ParaView
 using windows 7 64bit VS2013 express (UNCLASSIFIED)
In-Reply-To: <CADHSJjDa-LHjvc5RUW4mPCmu_C2xXdsRNiLse1fXVU+9vpz4tQ@mail.gmail.com>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F5D@umechp9h.easf.csd.disa.mil>
 <CADHSJjBAk_f87k=-OViErkG3GaH+FyDuO1XP=AUeVF+1SEy7sQ@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F7C@umechp9h.easf.csd.disa.mil>
 <CADHSJjDa-LHjvc5RUW4mPCmu_C2xXdsRNiLse1fXVU+9vpz4tQ@mail.gmail.com>
Message-ID: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CFA0DE@umechp9h.easf.csd.disa.mil>

Classification: UNCLASSIFIED
Caveats: NONE

Utkarsh,

Thanks for the information. I thought you built your own version of python. I 
will give the binary from python.org a try.

Thanks
-simon

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Monday, July 28, 2014 4:24 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] what python library to use when compiling ParaView 
using windows 7 64bit VS2013 express (UNCLASSIFIED)

Simon,

We build our own Python for the binaries we build using the same compiler as 
the rest of ParaView. On dashboards, we do use Python binaries directly from 
python.org and they work quite well. Did if you give those a try?

Utkarsh

On Mon, Jul 28, 2014 at 12:21 PM, Su, Simon M CTR USARMY ARL (US) 
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hi Utkarsh,
>
> I am building the release version so, not sure about the warning with
> Release version. Maybe something I didn't do?
>
> On the other hand, can I know what is the combination used to compile
> the windows binary available on the pv 4.1.0 on the website ?
> http://www.paraview.org/Wiki/ParaView/Binaries site mentioned with PV
> 4.0.x pv windows binary was compiled with Visual Studio 2008 x64
> 9.0.30729.1 SP, OpenMPI, v 1.4.4, and python v 2.7.3 (among other
> things). Was the python v
> 2.7.3 used compiled with Visual Studio 2008 x64 9.0.30729.1 SP? If so,
> what python library was used? The binary for python from
> WinPython-64bit-2.7.6.4 was compiled with VS2008, is that why VS2008
> was picked for pv 4.0.x windows compilation?
>
> Thanks
> -simon
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Monday, July 28, 2014 12:09 PM
> To: Su, Simon M CTR USARMY ARL (US)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] what python library to use when compiling
> ParaView using windows 7 64bit VS2013 express (UNCLASSIFIED)
>
> You could build ParaView  as a "Release" (rather than Debug) and then
> you should not get those warnings, I think.
>
>
>
> On Mon, Jul 28, 2014 at 11:49 AM, Su, Simon M CTR USARMY ARL (US)
> <simon.m.su.ctr at mail.mil> wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Hello,
>>
>> When I used WinPython-64bit-2.7.6.4 (which allows installation of
>> Python library without admin rights but has no python debug library)
>> library to compile ParaView with VS2013 express edition, I get this
>> tons of warning messages. Search the web, someone mentioned
>> WinPython-64bit-2.7.6.4 wasn't compiled with VS2013 express edition
>> and I shouldn't be using library compiled with one Visual Studio
>> version in another version of VS.
>>
>> Is compiling a version of python from source code using vs2013
>> express the only way available to me? Or is there python library
>> compiled with
>> vs2013 express out there that I am yet to find? Or can I just ignore
>> the warning messages in VS2013 express?
>>
>> Any help is much appreciated
>>
>> Thanks
>> -simon
>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>> _______________________________________________
>> 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://public.kitware.com/mailman/listinfo/paraview
>>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>

Classification: UNCLASSIFIED
Caveats: NONE


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 9990 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140729/90d031de/attachment-0001.bin>

From utkarsh.ayachit at kitware.com  Tue Jul 29 10:18:44 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 29 Jul 2014 10:18:44 -0400
Subject: [Paraview] what python library to use when compiling ParaView
 using windows 7 64bit VS2013 express (UNCLASSIFIED)
In-Reply-To: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CFA0DE@umechp9h.easf.csd.disa.mil>
References: <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F5D@umechp9h.easf.csd.disa.mil>
 <CADHSJjBAk_f87k=-OViErkG3GaH+FyDuO1XP=AUeVF+1SEy7sQ@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CF8F7C@umechp9h.easf.csd.disa.mil>
 <CADHSJjDa-LHjvc5RUW4mPCmu_C2xXdsRNiLse1fXVU+9vpz4tQ@mail.gmail.com>
 <F02E4EC9F4B4BA4189BBDC8BF3B2AD8224CFA0DE@umechp9h.easf.csd.disa.mil>
Message-ID: <CADHSJjCGzfA26bq8y37MzvF+im80C2h8B1kxWBD4DD94s2-BiQ@mail.gmail.com>

Simon,

Just to clarify: yes, the binaries distributed on paraview.org do
indeed include a Python built from source using the same VS compiler
as we use for the rest of the build. Several of the dashboard machines
that run nightly tests and others typically don't use a Python version
built from source, but simply the binaries from python.org.



On Tue, Jul 29, 2014 at 9:13 AM, Su, Simon M CTR USARMY ARL (US)
<simon.m.su.ctr at mail.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Utkarsh,
>
> Thanks for the information. I thought you built your own version of python. I
> will give the binary from python.org a try.
>
> Thanks
> -simon
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Monday, July 28, 2014 4:24 PM
> To: Su, Simon M CTR USARMY ARL (US)
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] what python library to use when compiling ParaView
> using windows 7 64bit VS2013 express (UNCLASSIFIED)
>
> Simon,
>
> We build our own Python for the binaries we build using the same compiler as
> the rest of ParaView. On dashboards, we do use Python binaries directly from
> python.org and they work quite well. Did if you give those a try?
>
> Utkarsh
>
> On Mon, Jul 28, 2014 at 12:21 PM, Su, Simon M CTR USARMY ARL (US)
> <simon.m.su.ctr at mail.mil> wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Hi Utkarsh,
>>
>> I am building the release version so, not sure about the warning with
>> Release version. Maybe something I didn't do?
>>
>> On the other hand, can I know what is the combination used to compile
>> the windows binary available on the pv 4.1.0 on the website ?
>> http://www.paraview.org/Wiki/ParaView/Binaries site mentioned with PV
>> 4.0.x pv windows binary was compiled with Visual Studio 2008 x64
>> 9.0.30729.1 SP, OpenMPI, v 1.4.4, and python v 2.7.3 (among other
>> things). Was the python v
>> 2.7.3 used compiled with Visual Studio 2008 x64 9.0.30729.1 SP? If so,
>> what python library was used? The binary for python from
>> WinPython-64bit-2.7.6.4 was compiled with VS2008, is that why VS2008
>> was picked for pv 4.0.x windows compilation?
>>
>> Thanks
>> -simon
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Sent: Monday, July 28, 2014 12:09 PM
>> To: Su, Simon M CTR USARMY ARL (US)
>> Cc: paraview at paraview.org
>> Subject: Re: [Paraview] what python library to use when compiling
>> ParaView using windows 7 64bit VS2013 express (UNCLASSIFIED)
>>
>> You could build ParaView  as a "Release" (rather than Debug) and then
>> you should not get those warnings, I think.
>>
>>
>>
>> On Mon, Jul 28, 2014 at 11:49 AM, Su, Simon M CTR USARMY ARL (US)
>> <simon.m.su.ctr at mail.mil> wrote:
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> Hello,
>>>
>>> When I used WinPython-64bit-2.7.6.4 (which allows installation of
>>> Python library without admin rights but has no python debug library)
>>> library to compile ParaView with VS2013 express edition, I get this
>>> tons of warning messages. Search the web, someone mentioned
>>> WinPython-64bit-2.7.6.4 wasn't compiled with VS2013 express edition
>>> and I shouldn't be using library compiled with one Visual Studio
>>> version in another version of VS.
>>>
>>> Is compiling a version of python from source code using vs2013
>>> express the only way available to me? Or is there python library
>>> compiled with
>>> vs2013 express out there that I am yet to find? Or can I just ignore
>>> the warning messages in VS2013 express?
>>>
>>> Any help is much appreciated
>>>
>>> Thanks
>>> -simon
>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>> _______________________________________________
>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>

From shermanw at indiana.edu  Tue Jul 29 17:27:21 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Tue, 29 Jul 2014 17:27:21 -0400
Subject: [Paraview] Statistics Inspector data via Python
Message-ID: <53D811B9.7090702@indiana.edu>

ParaView People,

I wonder how I might go about accessing the numbers that appear in
the "Statistics Inspector" view panel via the Python scripting
interface.  I would like to output some data in the log that I
write when generate a batch animation -- items such as memory
consumption and number of polygons for example.

It looks like basically all the data that I am interested in is
contained in the "Statistics Inspector", so I'm hoping there is
a quick way to access the data.

I read through Utkarsh and Ben's Kitware Blog entry on ParaView
memory consumption, but that relies on procfs, and I'd rather
avoid going through that to keep track of things -- besides that
just gives the overall consumption, and then broken down by
shared objects rather than pipeline objects.

One other thing -- I'm curious as to what the difference is between
the "Statistics Inspector" columns named "Memory (MB)" and
"Geometry (MB)".  I'm confident that the first means what is
suggests, but I don't know what Geometry would be measured in
MegaBytes, and how that would differ from basic memory consumption.

	Thanks,
	Bill

--
Bill Sherman
Sr. Technology Advisor
Advanced Visualization Lab
Pervasive Technology Inst
Indiana University
shermanw at indiana.edu

From scott.wittenburg at kitware.com  Tue Jul 29 17:48:23 2014
From: scott.wittenburg at kitware.com (Scott Wittenburg)
Date: Tue, 29 Jul 2014 15:48:23 -0600
Subject: [Paraview] Statistics Inspector data via Python
In-Reply-To: <53D811B9.7090702@indiana.edu>
References: <53D811B9.7090702@indiana.edu>
Message-ID: <CAPiw4fCwzGjeoCgpim3Ass+v=uTQP1DFby9p_fAM5x=DOiRYDg@mail.gmail.com>

The GetDataInformation() function can be used to meet some of your needs,
though maybe not all:

proxy = GetActiveSource()
dataInfo = proxy.GetDataInformation()

# Get some basic statistics about the data
info = { 'bounds': dataInfo.DataInformation.GetBounds(),
         'points': dataInfo.DataInformation.GetNumberOfPoints(),
         'cells': dataInfo.DataInformation.GetNumberOfCells(),
         'type': dataInfo.DataInformation.GetPrettyDataTypeString(),
         'memory': dataInfo.DataInformation.GetMemorySize() }

I'm not sure how to get the number of polygons.  Perhaps there's more in
that DataInformation reference?

Cheers,
Scott





On Tue, Jul 29, 2014 at 3:27 PM, Bill Sherman <shermanw at indiana.edu> wrote:

> ParaView People,
>
> I wonder how I might go about accessing the numbers that appear in
> the "Statistics Inspector" view panel via the Python scripting
> interface.  I would like to output some data in the log that I
> write when generate a batch animation -- items such as memory
> consumption and number of polygons for example.
>
> It looks like basically all the data that I am interested in is
> contained in the "Statistics Inspector", so I'm hoping there is
> a quick way to access the data.
>
> I read through Utkarsh and Ben's Kitware Blog entry on ParaView
> memory consumption, but that relies on procfs, and I'd rather
> avoid going through that to keep track of things -- besides that
> just gives the overall consumption, and then broken down by
> shared objects rather than pipeline objects.
>
> One other thing -- I'm curious as to what the difference is between
> the "Statistics Inspector" columns named "Memory (MB)" and
> "Geometry (MB)".  I'm confident that the first means what is
> suggests, but I don't know what Geometry would be measured in
> MegaBytes, and how that would differ from basic memory consumption.
>
>         Thanks,
>         Bill
>
> --
> Bill Sherman
> Sr. Technology Advisor
> Advanced Visualization Lab
> Pervasive Technology Inst
> Indiana University
> shermanw at indiana.edu
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140729/7764e79a/attachment.html>

From shermanw at indiana.edu  Tue Jul 29 18:46:30 2014
From: shermanw at indiana.edu (Bill Sherman)
Date: Tue, 29 Jul 2014 18:46:30 -0400
Subject: [Paraview] Statistics Inspector data via Python
In-Reply-To: <CAPiw4fCwzGjeoCgpim3Ass+v=uTQP1DFby9p_fAM5x=DOiRYDg@mail.gmail.com>
References: <53D811B9.7090702@indiana.edu>
 <CAPiw4fCwzGjeoCgpim3Ass+v=uTQP1DFby9p_fAM5x=DOiRYDg@mail.gmail.com>
Message-ID: <53D82446.3020302@indiana.edu>

Thanks Scott,

> The GetDataInformation() function can be used to meet some of your
> needs, though maybe not all:

Perfect!

> proxy = GetActiveSource()
> dataInfo = proxy.GetDataInformation()
>
> # Get some basic statistics about the data
> info = { 'bounds': dataInfo.DataInformation.GetBounds(),
>           'points': dataInfo.DataInformation.GetNumberOfPoints(),
>           'cells': dataInfo.DataInformation.GetNumberOfCells(),
>           'type': dataInfo.DataInformation.GetPrettyDataTypeString(),
>           'memory': dataInfo.DataInformation.GetMemorySize() }
>
> I'm not sure how to get the number of polygons.  Perhaps there's more in
> that DataInformation reference?

GetPolygonCount()!

> Cheers,
> Scott

	Thanks again,
	Bill


From aur.marsan at gmail.com  Wed Jul 30 15:45:51 2014
From: aur.marsan at gmail.com (=?UTF-8?Q?Aur=C3=A9lien_Marsan?=)
Date: Wed, 30 Jul 2014 15:45:51 -0400
Subject: [Paraview] vtkPolydata vs. vtkUnstructuredGrid
Message-ID: <CALBJ7LKjeYpFxMqhhgZWXw_s=GoOJud=stHApCo1Uvs8U053SQ@mail.gmail.com>

Dear Paraview users, and VTK users

I want to build a vtkUnstructuredGrid from several numpy arrays, which
contains the points coordinates, the cells, cells locations, cells types
etc...
So : I have all informations that are needed.

vtkPolyData seems a lot easier to define through a python script.

But : what is the fundamental difference between vtkPolyData and
vtkUnstructuredGrid ?
What should be the criterion in order to choose on of these two types ?

Many thanks in advance,
Regards,

Aur?lien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140730/dcde3150/attachment.html>

From f_magician at mac.com  Wed Jul 30 22:03:08 2014
From: f_magician at mac.com (Magician)
Date: Thu, 31 Jul 2014 11:03:08 +0900
Subject: [Paraview] Calculating Wall Height
Message-ID: <A93FB542-BF4C-44A5-A4D5-00CF040ADDE8@mac.com>

Hi all,


I?d like to get height values of wall cells for calculating oil shear velocity or y+.
My datasets have no information about wall direction, prism layer or inside, center of cells.

Does anyone have good ideas to do it?


Magician

From tristan.schloegl at ltd.uni-erlangen.de  Thu Jul 31 03:31:27 2014
From: tristan.schloegl at ltd.uni-erlangen.de (Tristan =?ISO-8859-1?B?U2NobPZnbA==?=)
Date: Thu, 31 Jul 2014 09:31:27 +0200
Subject: [Paraview] Clean Grid and Average Point Data
In-Reply-To: <CAMaOp+GBfu2006-HR2=ZsYS7mMmy23_cLW2gPYneXjQjVsJ6KQ@mail.gmail.com>
References: <CFFC10C5.283A%tristan.schloegl@ltd.uni-erlangen.de>
 <CAMaOp+HaVNNBYnenCKX7Ahi9qQeM+55Sq5QxYhWEASOBoNfcDw@mail.gmail.com>
 <CFFD1C11.2849%tristan.schloegl@ltd.uni-erlangen.de>
 <CAMaOp+GBfu2006-HR2=ZsYS7mMmy23_cLW2gPYneXjQjVsJ6KQ@mail.gmail.com>
Message-ID: <CFFFBC76.288C%tristan.schloegl@ltd.uni-erlangen.de>

Hi Andy,

thanks for the idea with the "Pass Arrays" filter. After realising that the
filter is a bit buggy (see http://www.vtk.org/Bug/view.php?id=14817), I get
some good results using it. If I need more 'accurate' solutions I'll have a
look at the Programmable filter. Thanks for the link to the wiki!

Cheers
Tristan


Von:  Andy Bauer <andy.bauer at kitware.com>
Datum:  Dienstag, 29. Juli 2014 15:00
An:  Tristan Schloegl <tristan.schloegl at ltd.uni-erlangen.de>
Cc:  "Paraview at paraview.org" <Paraview at paraview.org>
Betreff:  Re: [Paraview] Clean Grid and Average Point Data

Hi Tristan,

I'm not familiar with deal.II's output format -- could you share a small
sample? 

Some other tricks you can try is using the "Pass Point Data" option with the
Point Data to Cell Data filter which will keep your point data around as
well. Then you could use the Pass Arrays filter to get rid of the cell data
that you didn't want generated from the point data before (i.e. the ones
that would overwrite your existing point data when you use the cell data to
point data filter).

As for the programmable filter, you can find more information on it at
http://www.paraview.org/Wiki/Python_Programmable_Filter. There are probably
more examples around the wiki that you can find as well with a little bit of
searching.

Regards,
Andy




On Tue, Jul 29, 2014 at 4:00 AM, Tristan Schl?gl
<tristan.schloegl at ltd.uni-erlangen.de> wrote:
> Hi Andy,
> 
> thanks for your reply. I tried working with the "point data to cell data" and
> "cell data to point data" filters. Indeed, this is too much averaging. It
> might be a starting point for only the discontinuous field I'm interested in,
> but the filter applies on all data in my model (e.g. I don't want the
> continuous displacement field and others to be averaged). Is there a way to
> specify only a certain dataset the filter is working on?
> 
> Regarding the programmable filter, I'm very new to ParaView internals (I'm
> mainly working with the GUI), however I'm a bit experienced with Python. Can
> you recommend some tutorial, where I get a quick introduction in how to access
> the data and modify it?
> 
> I believe dealing with this problem in deal.ii directly requires some changes
> in the library itself. Maybe you can also do something with derived classes.
> However, having the full information of a discontinuous field, like deal.ii
> outputs it, is generally not a bad thing to examine results. I just sometimes
> need 'cleaner' pictures and thought that's a post processing task, best be
> handled in ParaView.
> 
> Tristan
> 
> 
> Von:  Andy Bauer <andy.bauer at kitware.com>
> Datum:  Montag, 28. Juli 2014 16:38
> An:  Tristan Schloegl <tristan.schloegl at ltd.uni-erlangen.de>
> Cc:  "Paraview at paraview.org" <Paraview at paraview.org>
> Betreff:  Re: [Paraview] Clean Grid and Average Point Data
> 
> Hi Tristan,
> 
> There are a couple of things you can try. The best but most complex is
> probably the programmable filter where you merge the points yourself and do
> the averaging for the point values. The other thing you can try is using the
> point data to cell data filter, then use the clean to grid filter and finally
> use the cell data to point data filter. This may due more averaging than you
> would like for your results. Other than that, did you get any feedback on the
> deal.II mailing list?
> 
> Regards,
> Andy
> 
> 
> On Mon, Jul 28, 2014 at 8:37 AM, Tristan Schl?gl
> <tristan.schloegl at ltd.uni-erlangen.de> wrote:
>> Hi,
>> 
>> I'm using ParaView to visualise finite element simulation results created by
>> the deal.ii C++ library. Deal.ii outputs hex elements such that each element
>> has its own vertices. To illustrate that point a simple cube consisting of 8
>> elements and 27 nodes has 8*8=64 data points. When I display vector valued
>> data as glyphs I have multiple vectors at the same location resulting from
>> the contributions of neighbouring cells, see
>> http://blogs.fau.de/schloegl/files/2014/07/orig_grid.png .
>> 
>> I now want to display only a single vector at each point, namely the average
>> value of all contributions. I tried and applied a "Clean to Grid" filter, see
>> http://blogs.fau.de/schloegl/files/2014/07/clean_grid.png .
>> This is quite good already however, it seems that ParaView only takes one of
>> the vectors for each point and not the average (see top mid vector of the
>> front (z-max) face).
>> 
>> Is there any other way to realise what I need in ParaView?
>> 
>> Regards
>> Tristan
>> 
>> 
>> -- 
>> Dipl.-Ing. Tristan Schl?gl
>> Chair of Applied Dynamics
>> University of Erlangen-Nuremberg
>> Haberstrasse 1
>> D-91058 Erlangen, Germany
>> room 01.013
>> phone +49 (0)9131 85 61003 <tel:%2B49%20%280%299131%2085%2061003>
>> fax +49 (0)9131 85 61011 <tel:%2B49%20%280%299131%2085%2061011>
>> url www.ltd.tf.uni-erlangen.de <http://www.ltd.tf.uni-erlangen.de>
>> 
>> _______________________________________________
>> Powered by www.kitware.com <http://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://public.kitware.com/mailman/listinfo/paraview
>> 
> 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140731/8d1f5c92/attachment-0001.html>

From dan.mazur at clumeq.ca  Thu Jul 31 09:33:26 2014
From: dan.mazur at clumeq.ca (Dan Mazur)
Date: Thu, 31 Jul 2014 09:33:26 -0400
Subject: [Paraview] Segmentation fault when launching Paraview
Message-ID: <CACWh7n+d4T5ZaxTYrAYn57f8Rk8HhAMYQYJHA6QKxuM8GkAr+A@mail.gmail.com>

Hello,

I have compiled Paraview v4.1.0 from source on CentOS-6.3.  It is my first
time compiling any version of Paraview from source. The configuration,
compilation, and installation all proceed without errors according to the
installation documentation. However, I am having trouble launching the
bin/paraview binary. I find that I get a segmentation fault shortly after
issuing the paraview command, before anything else happens.

The backtrace from the core dump is:
(gdb) bt
#0  0x000000320807efe1 in strcat () from /lib64/libc.so.6
#1  0x00000000004018f5 in vtksys_shared_forward_to_real (argc=1,
argv_in=0x7fff51113898) at
$PARAVIEW/VTK/Utilities/KWSys/vtksys/SharedForward.h:837
#2  0x0000000000401b88 in main (argc=1, argv=0x7fff51113898) at
$PARAVIEW/Applications/ParaView/paraview-forward.c:28

I have not found a solution to this problem from searching the Mailing list
or Google, but I did find an unresolved case that appears to be the same
issue:
https://hpcforge.org/tracker/index.php?func=detail&aid=98&group_id=34&atid=217

When I run 'make test', I find that many of the tests fail (37% tests
passed, 668 tests failed out of 1061). Apparently, the application hasn't
built properly. However, I am not sure what has gone wrong or how to
diagnose the problem from the log files. I have tried rebuilding the
application with the same settings, but got the same results.

I appreciate any guidance/assistance that can be offered. Thanks in advance.

-Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140731/5d46cdd0/attachment.html>

From dan.mazur at clumeq.ca  Thu Jul 31 10:23:58 2014
From: dan.mazur at clumeq.ca (Dan Mazur)
Date: Thu, 31 Jul 2014 10:23:58 -0400
Subject: [Paraview] Segmentation fault when launching Paraview
In-Reply-To: <CACWh7n+d4T5ZaxTYrAYn57f8Rk8HhAMYQYJHA6QKxuM8GkAr+A@mail.gmail.com>
References: <CACWh7n+d4T5ZaxTYrAYn57f8Rk8HhAMYQYJHA6QKxuM8GkAr+A@mail.gmail.com>
Message-ID: <CACWh7n+d0bujLZ7WBz5t2C28ivpwRmz54ubmYAhVeX=5NGd0vQ@mail.gmail.com>

Hello,

I have placed the CMakeCache.txt file online in case it helps with
debugging:
http://pastebin.com/McaX1773

-Dan


On Thu, Jul 31, 2014 at 9:33 AM, Dan Mazur <dan.mazur at clumeq.ca> wrote:

> Hello,
>
> I have compiled Paraview v4.1.0 from source on CentOS-6.3.  It is my first
> time compiling any version of Paraview from source. The configuration,
> compilation, and installation all proceed without errors according to the
> installation documentation. However, I am having trouble launching the
> bin/paraview binary. I find that I get a segmentation fault shortly after
> issuing the paraview command, before anything else happens.
>
> The backtrace from the core dump is:
> (gdb) bt
> #0  0x000000320807efe1 in strcat () from /lib64/libc.so.6
> #1  0x00000000004018f5 in vtksys_shared_forward_to_real (argc=1,
> argv_in=0x7fff51113898) at
> $PARAVIEW/VTK/Utilities/KWSys/vtksys/SharedForward.h:837
> #2  0x0000000000401b88 in main (argc=1, argv=0x7fff51113898) at
> $PARAVIEW/Applications/ParaView/paraview-forward.c:28
>
> I have not found a solution to this problem from searching the Mailing
> list or Google, but I did find an unresolved case that appears to be the
> same issue:
>
> https://hpcforge.org/tracker/index.php?func=detail&aid=98&group_id=34&atid=217
>
> When I run 'make test', I find that many of the tests fail (37% tests
> passed, 668 tests failed out of 1061). Apparently, the application hasn't
> built properly. However, I am not sure what has gone wrong or how to
> diagnose the problem from the log files. I have tried rebuilding the
> application with the same settings, but got the same results.
>
> I appreciate any guidance/assistance that can be offered. Thanks in
> advance.
>
> -Dan
>
>
>
>
>
>


-- 
------------------------------------------------------------------------
Dr. Dan Mazur | daniel.mazur at mcgill.ca  |
dan.mazur at calculquebec.ca
Scientific Computing Analyst / Analyste en calcul scientifique
McGill HPC Centre / Centre de Calcul Haute Performance de McGill |
http://www.hpc.mcgill.ca
Calcul Qu?bec | http://www.calculquebec.ca
Compute/Calcul Canada | http://www.computecanada.ca
Tel/T?l: 514-396-8928 | Fax/T?l?copieur: 514-396-8934

------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140731/e60aaaa4/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Jul 31 14:57:32 2014
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 31 Jul 2014 14:57:32 -0400
Subject: [Paraview] Segmentation fault when launching Paraview
In-Reply-To: <CACWh7n+d0bujLZ7WBz5t2C28ivpwRmz54ubmYAhVeX=5NGd0vQ@mail.gmail.com>
References: <CACWh7n+d4T5ZaxTYrAYn57f8Rk8HhAMYQYJHA6QKxuM8GkAr+A@mail.gmail.com>
 <CACWh7n+d0bujLZ7WBz5t2C28ivpwRmz54ubmYAhVeX=5NGd0vQ@mail.gmail.com>
Message-ID: <CADHSJjD9pWHPwhK44sdvBq71X4eS2d9duhc_DDN-DjV-mUmtyg@mail.gmail.com>

Are you running from the build directory or install directory? Can you
you try running from the build direactory first to see if that works?


On Thu, Jul 31, 2014 at 10:23 AM, Dan Mazur <dan.mazur at clumeq.ca> wrote:
> Hello,
>
> I have placed the CMakeCache.txt file online in case it helps with
> debugging:
> http://pastebin.com/McaX1773
>
> -Dan
>
>
> On Thu, Jul 31, 2014 at 9:33 AM, Dan Mazur <dan.mazur at clumeq.ca> wrote:
>>
>> Hello,
>>
>> I have compiled Paraview v4.1.0 from source on CentOS-6.3.  It is my first
>> time compiling any version of Paraview from source. The configuration,
>> compilation, and installation all proceed without errors according to the
>> installation documentation. However, I am having trouble launching the
>> bin/paraview binary. I find that I get a segmentation fault shortly after
>> issuing the paraview command, before anything else happens.
>>
>> The backtrace from the core dump is:
>> (gdb) bt
>> #0  0x000000320807efe1 in strcat () from /lib64/libc.so.6
>> #1  0x00000000004018f5 in vtksys_shared_forward_to_real (argc=1,
>> argv_in=0x7fff51113898) at
>> $PARAVIEW/VTK/Utilities/KWSys/vtksys/SharedForward.h:837
>> #2  0x0000000000401b88 in main (argc=1, argv=0x7fff51113898) at
>> $PARAVIEW/Applications/ParaView/paraview-forward.c:28
>>
>> I have not found a solution to this problem from searching the Mailing
>> list or Google, but I did find an unresolved case that appears to be the
>> same issue:
>>
>> https://hpcforge.org/tracker/index.php?func=detail&aid=98&group_id=34&atid=217
>>
>> When I run 'make test', I find that many of the tests fail (37% tests
>> passed, 668 tests failed out of 1061). Apparently, the application hasn't
>> built properly. However, I am not sure what has gone wrong or how to
>> diagnose the problem from the log files. I have tried rebuilding the
>> application with the same settings, but got the same results.
>>
>> I appreciate any guidance/assistance that can be offered. Thanks in
>> advance.
>>
>> -Dan
>>
>>
>>
>>
>>
>
>
>
> --
> ------------------------------------------------------------------------
> Dr. Dan Mazur | daniel.mazur at mcgill.ca  |
> dan.mazur at calculquebec.ca
> Scientific Computing Analyst / Analyste en calcul scientifique
> McGill HPC Centre / Centre de Calcul Haute Performance de McGill |
> http://www.hpc.mcgill.ca
> Calcul Qu?bec | http://www.calculquebec.ca
> Compute/Calcul Canada | http://www.computecanada.ca
> Tel/T?l: 514-396-8928 | Fax/T?l?copieur: 514-396-8934
>
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> 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://public.kitware.com/mailman/listinfo/paraview
>

From wascott at sandia.gov  Thu Jul 31 18:21:53 2014
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 31 Jul 2014 22:21:53 +0000
Subject: [Paraview] Coloring by block
Message-ID: <69c7a9ef7d6f4290b483747d46bdd42f@ES05AMSNLNT.srn.sandia.gov>

Here is a question from one of my users - anyone have any ideas?

I realize this is probably the simplest question ever asked, but for some reason I am having trouble finding a "good" way to set block colors.

I have a multiblock data set with about 100 blocks.  I would like to use ParaView to generate some figures for a report that use a consistent block coloring scheme throughout.  Before I make myself seem too ignorant, I am able to get paraview to color blocks in many ways.  I just don't like any of them.

I want to write a file (maybe CSV?) that looks something like this:

Block #, RGB color
100, 1, 0.1, 0.1
200, 1.0, 0.0, 0.0
201, 0.8, 0.8, 0.8
...
... etc.

Or, maybe instead of a CSV it is a ParaView/python script that does all of the block coloring, e.g pseudo code:
<paraviewcommands>.block[number].setcolor<rgb>

I can set block colors individually by using the "Extract Block" filter once for every block (this is not a good solution).
I can also set block colors individually by selecting each block ('b' -> pick block in GUI -> right click, select Set Color), but this is also not a good solution since it is GUI-based.
I can also assign random colors "all at once", but the random scalar numbers generated by the filter are not "frozen", i.e. they change when new filters are applied and the pipeline is processed again.  I want to explicitly specify which colors to use.

Does anybody have any suggestions for going about this?  I'm sure this must have been asked in the past, but I didn't find any sufficient answers while "googling."  I am also interested in alternative solutions that don't rely on "hard-coding" the block colors, but which would color blocks consistently

Thanks,

Alan



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140731/5352c368/attachment.html>