Re: [Paraview] [EXTERNAL] Re: Make animation from steady state result

[Andrew Parker]

Thank you very much for these comments.  I'll give them a go and follow up
if need be.
Thanks,
Andy

On 19 January 2018 at 13:18, Cory Quammen  wrote:

> Andrew,
>
> Responses inlined below:
>
> On Fri, Jan 19, 2018 at 6:27 AM, Andrew Parker via ParaView
>  wrote:
> > Dear all,
> >
> > Sorry to post onto an old thread. I have been reading this thread and the
> > related write up here:
> > https://www.paraview.org/Wiki/Advanced_Tips_and_Tricks#
> Animating_a_static_vector_field
> >
> > This thread (and the tips and tricks post) is really close to what I
> want to
> > do, but I have a few follow-up questions.  I too have a steady-state
> > solution field. I want to trace particles from the inlet of my domain to
> the
> > exit, following the steady-state velocity field, and report for each
> > particle the temperature-time history (or any other scalar from my
> > simulation) that the particle sees.  In additional and crucially, the
> time
> > the particle has within the domain: a residence time.  The residence time
> > would be the maximum value or IntegrationTime each particle attains
> before
> > it leaves the domain.
> >
> > I see that if I follow the notes I can plot (using Glyphs) the
> temperature
> > as it varies across my domain as the particles are animated down the
> > streamlines: this is working.  What I do not seem to be able to find
> > however, is the IntegrationTime.  It appears as point-field data after
> the
> > streamlines are created, but vanishes after the contour filter is
> applied.
> > I guess the contour filter is computing a singular value for all values
> of
> > the IntegrationTime from T=0 to T=N with a specific level of granularity.
>
> By default, the Contour filter does not copy the scalar field used to
> determine the contour surface since it will always be the same value.
> You can tell it to copy the scalar field by enabling the Compute
> Scalars option.
>
> > However, I can't seem to extract the specific value of IntegrationTime
> (the
> > contour value) when I stop the simulation at any given point.  Do you
> know
> > how to do that?  The "time" scale in the VCR window always goes from 0->1
> > not from 0->(max value of IntegrationTime in seconds).  Can the actual
> value
> > of time be backed out or animated? If so how do I do that, or am I
> applying
> > the Contour filter wrongly: as per the post, I am only using the default
> > values in the Counter filter panel.
>
> Instead of using the Sequence animation mode, use Real Time. Then, set
> the Start Time to the minimum IntegrationTime value and End Time to
> the maximum IntegrationTime value. You can see these listed either in
> the Information tab of the StreamTracer filter in the Pipeline Browser
> or under the Contour filter's Property tab under the Isosurfaces
> section (Value Range). To show the current time in the render view,
> use an Annotate Time source, available in the Sources menu.
>
> > Finally, and importantly for me, while the Glyphs move across the screen
> > following the streamlines, and render via the temperature field, how to I
> > actually extract information from this pseudo time series to perform
> > analysis?  For example, the min and max temperature seen by a particle
> as it
> > moved across the streamline for instance?  I'm actually hoping to plot
> > offline (as a function of IntegrationTime) the min and max temperature
> > obtained for each particle: I can then take the min and max of that set
> for
> > the quickest and slowest particles.
>
> You can run the Connectivity filter on the StreamTracer output to
> assign a unique value to each streamline. This unique value will be
> called RegionId. It starts at 0 and ends at the number of stream lines
> minus 1. Selecting each stream line can be done with the Threshold
> filter in ParaView using the RegionId as the threshold array, then you
> can see the min/max of your temperature and IntegrationTime variables
> in the Information tab. Iterating over all stream lines and saving the
> min/max of the different scalar fields is possible using ParaView's
> Python scripting capabilities. However, you may find it faster to
> export the data to a tool with which you are more familiar.
>
> To do that, I would suggest saving the Connectivity filter output to a
> .csv file. The CSV file will contain all the scalar fields in
> different columns, including the aforementioned RegionId field. Simply
> filter on the RegionId field using your favorite software/plotting
> tool to find the min and max temperature and max IntegrationTime of
> the particle along the stream line.
>
> HTH,
> Cory
>
>
> > Using the latest stock version of paraview.
> >
> > Cheers,
> > Andy
> >
> > On 6 June 2014 at 20:30, Scott, W Alan  wrote:
> >>
> >> Ken and Jean, excellent idea!  I liked it so much that I wrote it up in
> >> the SNL ParaView tutorials, tips and tricks page.  It is located here:
> >> 

Re: [Paraview] [EXTERNAL] Re: Make animation from steady state result

[Andrew Parker via ParaView]

Dear all,

Sorry to post onto an old thread. I have been reading this thread and the
related write up here:
https://www.paraview.org/Wiki/Advanced_Tips_and_Tricks#Animating_a_static_vector_field

This thread (and the tips and tricks post) is really close to what I want
to do, but I have a few follow-up questions.  I too have a steady-state
solution field. I want to trace particles from the inlet of my domain to
the exit, following the steady-state velocity field, and report for each
particle the temperature-time history (or any other scalar from my
simulation) that the particle sees.  In additional and crucially, the time
the particle has within the domain: a residence time.  The residence time
would be the maximum value or IntegrationTime each particle attains before
it leaves the domain.

I see that if I follow the notes I can plot (using Glyphs) the temperature
as it varies across my domain as the particles are animated down the
streamlines: this is working.  What I do not seem to be able to find
however, is the IntegrationTime.  It appears as point-field data after the
streamlines are created, but vanishes after the contour filter is applied.
I guess the contour filter is computing a singular value for all values of
the IntegrationTime from T=0 to T=N with a specific level of granularity.
However, I can't seem to extract the specific value of IntegrationTime (the
contour value) when I stop the simulation at any given point.  Do you know
how to do that?  The "time" scale in the VCR window always goes from 0->1
not from 0->(max value of IntegrationTime in seconds).  Can the actual
value of time be backed out or animated? If so how do I do that, or am I
applying the Contour filter wrongly: as per the post, I am only using the
default values in the Counter filter panel.

Finally, and importantly for me, while the Glyphs move across the screen
following the streamlines, and render via the temperature field, how to I
actually extract information from this pseudo time series to perform
analysis?  For example, the min and max temperature seen by a particle as
it moved across the streamline for instance?  I'm actually hoping to plot
offline (as a function of IntegrationTime) the min and max temperature
obtained for each particle: I can then take the min and max of that set for
the quickest and slowest particles.

Using the latest stock version of paraview.

Cheers,
Andy

On 6 June 2014 at 20:30, Scott, W Alan  wrote:

> Ken and Jean, excellent idea!  I liked it so much that I wrote it up in
> the SNL ParaView tutorials, tips and tricks page.  It is located here:
> http://www.paraview.org/Wiki/Advanced_Tips_and_Tricks
>
>
>
> Alan
>
>
>
> *From:* ParaView [mailto:paraview-boun...@paraview.org] *On Behalf Of 
> *Moreland,
> Kenneth
> *Sent:* Friday, June 06, 2014 11:43 AM
> *To:* David E DeMarle; minh hien
> *Cc:* paraview@paraview.org
>
> *Subject:* [EXTERNAL] Re: [Paraview] Make animation from steady state
> result
>
>
>
> Here's a more expanded list of steps outlining the solution David gave in
> case you are not very familiar with the contour filter and animation
> controls in ParaView.
>
>
>
> 1. Create the streamlines as you normally would.
>
>
>
> 2. Add a Contour filter to the streamline (third toolbar, second button
> from the left).
>
> 2.a. Change the Contour By property to IntegrationTime.
>
> 2.b. Press Apply.
>
> This little trick will create a point on each streamline at a particular
> time in the particle advection simulation that created the streamlines.
>
>
>
> 3. Open the Animation View (View -> Animation View)
>
> 3.a. On the bottom row, select the contour filter in the first chooser box
> and Isosurfaces in the second chooser box. Then hit the blue plus button at
> the left.
>
> 3.b. Make sure Mode is set to Sequence and change No. Frames to 100.
>
> 3.c. Hit the play button in the VCR controls (green triangle in the top
> toolbar). You will see the dots animate over the streamlines.
>
> 3.d. You can adjust the speed of the animation by changing the No. Frames.
>
>
>
> 4. If you want to see glyphs instead of dots, just add the glyph filter to
> the output of the contour filter.
>
>
>
> BTW, props to Jean Favre for originally posting this solution to the
> ParaView mailing list (http://markmail.org/message/ms57z7jjubh2pzjg).
>
>
>
> -Ken
>
>
>
> *From: *David E DeMarle 
> *Date: *Thursday, June 5, 2014 8:07 AM
> *To: *minh hien 
> *Cc: *"paraview@paraview.org" 
> *Subject: *[EXTERNAL] Re: [Paraview] Make animation from steady state
> result
>
>
>
> Make an isocontour of the streamlines' integrationTime variable.
>
> Then in animation view, make a track for the isocontour value.
>
>
> David E DeMarle
> Kitware, Inc.
> R Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909 <(518)%20881-4909>
>
>
>
> On Thu, Jun 5, 2014 at 9:52 AM, minh hien  wrote:
>
> Hi 

Re: [Paraview] [EXTERNAL] Re: Make animation from steady state result

[Cory Quammen]

Andrew,

Responses inlined below:

On Fri, Jan 19, 2018 at 6:27 AM, Andrew Parker via ParaView
 wrote:
> Dear all,
>
> Sorry to post onto an old thread. I have been reading this thread and the
> related write up here:
> https://www.paraview.org/Wiki/Advanced_Tips_and_Tricks#Animating_a_static_vector_field
>
> This thread (and the tips and tricks post) is really close to what I want to
> do, but I have a few follow-up questions.  I too have a steady-state
> solution field. I want to trace particles from the inlet of my domain to the
> exit, following the steady-state velocity field, and report for each
> particle the temperature-time history (or any other scalar from my
> simulation) that the particle sees.  In additional and crucially, the time
> the particle has within the domain: a residence time.  The residence time
> would be the maximum value or IntegrationTime each particle attains before
> it leaves the domain.
>
> I see that if I follow the notes I can plot (using Glyphs) the temperature
> as it varies across my domain as the particles are animated down the
> streamlines: this is working.  What I do not seem to be able to find
> however, is the IntegrationTime.  It appears as point-field data after the
> streamlines are created, but vanishes after the contour filter is applied.
> I guess the contour filter is computing a singular value for all values of
> the IntegrationTime from T=0 to T=N with a specific level of granularity.

By default, the Contour filter does not copy the scalar field used to
determine the contour surface since it will always be the same value.
You can tell it to copy the scalar field by enabling the Compute
Scalars option.

> However, I can't seem to extract the specific value of IntegrationTime (the
> contour value) when I stop the simulation at any given point.  Do you know
> how to do that?  The "time" scale in the VCR window always goes from 0->1
> not from 0->(max value of IntegrationTime in seconds).  Can the actual value
> of time be backed out or animated? If so how do I do that, or am I applying
> the Contour filter wrongly: as per the post, I am only using the default
> values in the Counter filter panel.

Instead of using the Sequence animation mode, use Real Time. Then, set
the Start Time to the minimum IntegrationTime value and End Time to
the maximum IntegrationTime value. You can see these listed either in
the Information tab of the StreamTracer filter in the Pipeline Browser
or under the Contour filter's Property tab under the Isosurfaces
section (Value Range). To show the current time in the render view,
use an Annotate Time source, available in the Sources menu.

> Finally, and importantly for me, while the Glyphs move across the screen
> following the streamlines, and render via the temperature field, how to I
> actually extract information from this pseudo time series to perform
> analysis?  For example, the min and max temperature seen by a particle as it
> moved across the streamline for instance?  I'm actually hoping to plot
> offline (as a function of IntegrationTime) the min and max temperature
> obtained for each particle: I can then take the min and max of that set for
> the quickest and slowest particles.

You can run the Connectivity filter on the StreamTracer output to
assign a unique value to each streamline. This unique value will be
called RegionId. It starts at 0 and ends at the number of stream lines
minus 1. Selecting each stream line can be done with the Threshold
filter in ParaView using the RegionId as the threshold array, then you
can see the min/max of your temperature and IntegrationTime variables
in the Information tab. Iterating over all stream lines and saving the
min/max of the different scalar fields is possible using ParaView's
Python scripting capabilities. However, you may find it faster to
export the data to a tool with which you are more familiar.

To do that, I would suggest saving the Connectivity filter output to a
.csv file. The CSV file will contain all the scalar fields in
different columns, including the aforementioned RegionId field. Simply
filter on the RegionId field using your favorite software/plotting
tool to find the min and max temperature and max IntegrationTime of
the particle along the stream line.

HTH,
Cory


> Using the latest stock version of paraview.
>
> Cheers,
> Andy
>
> On 6 June 2014 at 20:30, Scott, W Alan  wrote:
>>
>> Ken and Jean, excellent idea!  I liked it so much that I wrote it up in
>> the SNL ParaView tutorials, tips and tricks page.  It is located here:
>> http://www.paraview.org/Wiki/Advanced_Tips_and_Tricks
>>
>>
>>
>> Alan
>>
>>
>>
>> From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of
>> Moreland, Kenneth
>> Sent: Friday, June 06, 2014 11:43 AM
>> To: David E DeMarle; minh hien
>> Cc: paraview@paraview.org
>>
>>
>> Subject: [EXTERNAL] Re: [Paraview] Make animation from steady state result
>>
>>
>>
>> Here's a more expanded 

Re: [Paraview] [Non-DoD Source] Re: ParaView + OpenVR (UNCLASSIFIED)

[Su, Simon M CIV USARMY RDECOM ARL (US)]

CLASSIFICATION: UNCLASSIFIED

Thanks Ken
-simon

-Original Message-
From: Ken Martin [mailto:ken.mar...@kitware.com] 
Sent: Friday, January 19, 2018 9:55 AM
To: Su, Simon M CIV USARMY RDECOM ARL (US) 
Cc: Benson Muite ; ParaView 
Subject: Re: [Non-DoD Source] Re: [Paraview] ParaView + OpenVR (UNCLASSIFIED)

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






Those flags look reasonable, but last I checked the OpenVR  CMake files had 
some minor issues. I use a small patch file for OpenVR 1.0.10 in the paraview 
superbuild. The patch file is here

Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/projects/win32/patches/openvr-improve-install.patch
 < 
Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/projects/win32/patches/openvr-improve-install.patch
 > 


I think it mostly fixes install issues and shared library support.

On Fri, Jan 19, 2018 at 9:49 AM, Su, Simon M CIV USARMY RDECOM ARL (US) 
 > wrote:


CLASSIFICATION: UNCLASSIFIED

Hi Ken,

I guess that's the price to pay when working with cutting edge 
technology :)  Thanks for the OpenVR version info. I used the release version 
of it.  What is your cmake flag for OpenVR? I just used

cmake ../OpenVR -DCMAKE_INSTALL_PREFIX=/path/to/install/OpenVR 
-DCMAKE_BUILD_TYPE=Release

Any other variable I need to specify? I will try to compile it with 
OpenVR version 1.0.10. Thank you

And Benson, yes the binary version worked ok with our HTC Vive.

Thanks
-simon

-Original Message-
From: ParaView [Caution-mailto:paraview-boun...@paraview.org < 
Caution-mailto:paraview-boun...@paraview.org > ] On Behalf Of Ken Martin
Sent: Friday, January 19, 2018 9:42 AM
To: Benson Muite  >
Cc: ParaView  >
Subject: [Non-DoD Source] Re: [Paraview] ParaView + OpenVR 
(UNCLASSIFIED)

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






Hi Simon & Benson,

I would bet steam has changed their API (again :-) and removed that 
method. Maybe try downloading/git checkout using the 1.0.10 version of OpenVR. 
That is what I last tested with and it should build fine against that.

Thanks!
Ken

On Thu, Jan 18, 2018 at 11:50 PM, Benson Muite   < 
Caution-Caution-mailto:benson.mu...@ut.ee < Caution-mailto:benson.mu...@ut.ee > 
 > > wrote:


Hi,

Does binary release version work for you? (At present only 
Windows is available), seem to be a few things to fix on Linux & Mac.


Have you tried build using flags similar to binary release 
version?

Caution-Caution-https://blog.kitware.com/taking-paraview-into-virtual-reality/ 
< Caution-https://blog.kitware.com/taking-paraview-into-virtual-reality/ >  < 
Caution-Caution-https://blog.kitware.com/taking-paraview-into-virtual-reality/ 
< Caution-https://blog.kitware.com/taking-paraview-into-virtual-reality/ >  >

Benson

On 01/19/2018 01:29 AM, Su, Simon M CIV USARMY RDECOM ARL (US) 
wrote:


CLASSIFICATION: UNCLASSIFIED

Hello,

I am wondering how to build a version of ParaView with 
OpenVR plugin? Which version of OpenVR shall I use? I used the OpenVR from 
Caution-Caution-https://github.com/ValveSoftware/openvr < 
Caution-https://github.com/ValveSoftware/openvr >  < 
Caution-Caution-https://github.com/ValveSoftware/openvr < 
Caution-https://github.com/ValveSoftware/openvr >  >   with just basic/minimal 
cmake option. I am using the following  cmake line for ParaView

cmake ..\paraview 
-DCMAKE_INSTALL_PREFIX=U:\tools\ParaView\ParaView -DCMAKE_BUILD_TYPE=Release -G 
Ninja -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DBUILD_TESTING:BOOL=OFF 
-DPARAVIEW_QT_VERSION=5 -DPARAVIEW_USE_MPI:BOOL=ON 
-DPARAVIEW_USE_VISITBRIDGE:BOOL=ON 

Re: [Paraview] [Non-DoD Source] Re: ParaView + OpenVR (UNCLASSIFIED)

[Ken Martin]

Those flags look reasonable, but last I checked the OpenVR  CMake files had
some minor issues. I use a small patch file for OpenVR 1.0.10 in the
paraview superbuild. The patch file is here

https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/projects/win32/patches/openvr-improve-install.patch

I think it mostly fixes install issues and shared library support.

On Fri, Jan 19, 2018 at 9:49 AM, Su, Simon M CIV USARMY RDECOM ARL (US) <
simon.m.su@mail.mil> wrote:

> CLASSIFICATION: UNCLASSIFIED
>
> Hi Ken,
>
> I guess that's the price to pay when working with cutting edge technology
> :)  Thanks for the OpenVR version info. I used the release version of it.
> What is your cmake flag for OpenVR? I just used
>
> cmake ../OpenVR -DCMAKE_INSTALL_PREFIX=/path/to/install/OpenVR
> -DCMAKE_BUILD_TYPE=Release
>
> Any other variable I need to specify? I will try to compile it with OpenVR
> version 1.0.10. Thank you
>
> And Benson, yes the binary version worked ok with our HTC Vive.
>
> Thanks
> -simon
>
> -Original Message-
> From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Ken
> Martin
> Sent: Friday, January 19, 2018 9:42 AM
> To: Benson Muite 
> Cc: ParaView 
> Subject: [Non-DoD Source] Re: [Paraview] ParaView + OpenVR (UNCLASSIFIED)
>
> All active links contained in this email were disabled. Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
> 
>
>
>
> Hi Simon & Benson,
>
> I would bet steam has changed their API (again :-) and removed that
> method. Maybe try downloading/git checkout using the 1.0.10 version of
> OpenVR. That is what I last tested with and it should build fine against
> that.
>
> Thanks!
> Ken
>
> On Thu, Jan 18, 2018 at 11:50 PM, Benson Muite  Caution-mailto:benson.mu...@ut.ee > > wrote:
>
>
> Hi,
>
> Does binary release version work for you? (At present only Windows
> is available), seem to be a few things to fix on Linux & Mac.
>
>
> Have you tried build using flags similar to binary release version?
> Caution-https://blog.kitware.com/taking-paraview-into-
> virtual-reality/ < Caution-https://blog.kitware.com/taking-paraview-into-
> virtual-reality/ >
>
> Benson
>
> On 01/19/2018 01:29 AM, Su, Simon M CIV USARMY RDECOM ARL (US)
> wrote:
>
>
> CLASSIFICATION: UNCLASSIFIED
>
> Hello,
>
> I am wondering how to build a version of ParaView with
> OpenVR plugin? Which version of OpenVR shall I use? I used the OpenVR from
> Caution-https://github.com/ValveSoftware/openvr < Caution-
> https://github.com/ValveSoftware/openvr >   with just basic/minimal cmake
> option. I am using the following  cmake line for ParaView
>
> cmake ..\paraview 
> -DCMAKE_INSTALL_PREFIX=U:\tools\ParaView\ParaView
> -DCMAKE_BUILD_TYPE=Release -G Ninja -DPARAVIEW_ENABLE_PYTHON:BOOL=ON
> -DBUILD_TESTING:BOOL=OFF -DPARAVIEW_QT_VERSION=5 -DPARAVIEW_USE_MPI:BOOL=ON
> -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON -DBOOST_INCLUDEDIR=U:/tools/
> boost/boost-1.65.1/include/boost-1_65_1 
> -DBOOST_ROOT=U:/tools/boost/boost-1.65.1
> -DModule_vtkAcceleratorsVTKm:BOOL=ON -DModule_vtkRenderingOpenVR:BOOL=ON
> -DPARAVIEW_BUILD_PLUGIN_OpenVR:BOOL=ON 
> -DOPENVR_INCLUDE_DIR=U:/tools/OpenVR/OpenVR/include
> -DOPENVR_LIBRARY=U:/tools/OpenVR/OpenVR/lib/openvr_api64.lib
>
> I am running into the following error
>
> C:\Users\one\build\ParaView\b>ninja
> [47/14039] Building CXX object VTK\Rendering\OpenVR\
> CMakeFiles\vtkRenderingOpenVR.dir\vtkOpenVRRenderWindow.cxx.obj
> FAILED: VTK/Rendering/OpenVR/
> CMakeFiles/vtkRenderingOpenVR.dir/vtkOpenVRRenderWindow.cxx.obj
> 
> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx64\x64\cl.exe
> /nologo /TP -DMPICH_IGNORE_CXX_SEEK -DVTK_IN_VTK
> -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE
> -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE
> -D_SCL_SECURE_NO_WARNINGS -DvtkRenderingOpenVR_EXPORTS -I.
> -IVTK\Rendering\OpenVR 
> -IC:\Users\one\build\ParaView\paraview\VTK\Rendering\OpenVR
> -IVTK\Common\Core -IC:\Users\one\build\ParaView\paraview\VTK\Common\Core
> -IVTK\Utilities\KWIML 
> -IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWIML
> -IVTK\Utilities\KWSys 
> -IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWSys
> -IVTK\ThirdParty\utf8 
> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\utf8
> -IVTK\Filters\Sources 
> -IC:\Users\one\build\ParaView\paraview\VTK\Filters\Sources
> -IVTK\Common\ComputationalGeometry -IC:\Users\one\build\ParaView\
> paraview\VTK\Common\ComputationalGeometry -IVTK\Common\DataModel
> -IC:\Users\one\build\ParaView\paraview\VTK\Common\DataModel
> -IVTK\Common\Math 

Re: [Paraview] [Non-DoD Source] Re: ParaView + OpenVR (UNCLASSIFIED)

[Su, Simon M CIV USARMY RDECOM ARL (US)]

CLASSIFICATION: UNCLASSIFIED

Hi Ken,

I guess that's the price to pay when working with cutting edge technology :)  
Thanks for the OpenVR version info. I used the release version of it.  What is 
your cmake flag for OpenVR? I just used

cmake ../OpenVR -DCMAKE_INSTALL_PREFIX=/path/to/install/OpenVR 
-DCMAKE_BUILD_TYPE=Release

Any other variable I need to specify? I will try to compile it with OpenVR 
version 1.0.10. Thank you

And Benson, yes the binary version worked ok with our HTC Vive. 

Thanks
-simon

-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Ken Martin
Sent: Friday, January 19, 2018 9:42 AM
To: Benson Muite 
Cc: ParaView 
Subject: [Non-DoD Source] Re: [Paraview] ParaView + OpenVR (UNCLASSIFIED)

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






Hi Simon & Benson,

I would bet steam has changed their API (again :-) and removed that method. 
Maybe try downloading/git checkout using the 1.0.10 version of OpenVR. That is 
what I last tested with and it should build fine against that.

Thanks!
Ken

On Thu, Jan 18, 2018 at 11:50 PM, Benson Muite  > wrote:


Hi,

Does binary release version work for you? (At present only Windows is 
available), seem to be a few things to fix on Linux & Mac.


Have you tried build using flags similar to binary release version?
Caution-https://blog.kitware.com/taking-paraview-into-virtual-reality/ 
< Caution-https://blog.kitware.com/taking-paraview-into-virtual-reality/ > 

Benson

On 01/19/2018 01:29 AM, Su, Simon M CIV USARMY RDECOM ARL (US) wrote:


CLASSIFICATION: UNCLASSIFIED

Hello,

I am wondering how to build a version of ParaView with OpenVR 
plugin? Which version of OpenVR shall I use? I used the OpenVR from 
Caution-https://github.com/ValveSoftware/openvr < 
Caution-https://github.com/ValveSoftware/openvr >   with just basic/minimal 
cmake option. I am using the following  cmake line for ParaView

cmake ..\paraview 
-DCMAKE_INSTALL_PREFIX=U:\tools\ParaView\ParaView -DCMAKE_BUILD_TYPE=Release -G 
Ninja -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DBUILD_TESTING:BOOL=OFF 
-DPARAVIEW_QT_VERSION=5 -DPARAVIEW_USE_MPI:BOOL=ON 
-DPARAVIEW_USE_VISITBRIDGE:BOOL=ON 
-DBOOST_INCLUDEDIR=U:/tools/boost/boost-1.65.1/include/boost-1_65_1 
-DBOOST_ROOT=U:/tools/boost/boost-1.65.1 -DModule_vtkAcceleratorsVTKm:BOOL=ON 
-DModule_vtkRenderingOpenVR:BOOL=ON -DPARAVIEW_BUILD_PLUGIN_OpenVR:BOOL=ON 
-DOPENVR_INCLUDE_DIR=U:/tools/OpenVR/OpenVR/include 
-DOPENVR_LIBRARY=U:/tools/OpenVR/OpenVR/lib/openvr_api64.lib

I am running into the following error

C:\Users\one\build\ParaView\b>ninja
[47/14039] Building CXX object 
VTK\Rendering\OpenVR\CMakeFiles\vtkRenderingOpenVR.dir\vtkOpenVRRenderWindow.cxx.obj
FAILED: 
VTK/Rendering/OpenVR/CMakeFiles/vtkRenderingOpenVR.dir/vtkOpenVRRenderWindow.cxx.obj

C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx64\x64\cl.exe
  /nologo /TP -DMPICH_IGNORE_CXX_SEEK -DVTK_IN_VTK -D_CRT_NONSTDC_NO_DEPRECATE 
-D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE 
-D_SCL_SECURE_NO_WARNINGS -DvtkRenderingOpenVR_EXPORTS -I. 
-IVTK\Rendering\OpenVR 
-IC:\Users\one\build\ParaView\paraview\VTK\Rendering\OpenVR -IVTK\Common\Core 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Core -IVTK\Utilities\KWIML 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWIML 
-IVTK\Utilities\KWSys 
-IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWSys 
-IVTK\ThirdParty\utf8 
-IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\utf8 
-IVTK\Filters\Sources 
-IC:\Users\one\build\ParaView\paraview\VTK\Filters\Sources 
-IVTK\Common\ComputationalGeometry 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\ComputationalGeometry 
-IVTK\Common\DataModel 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\DataModel -IVTK\Common\Math 
-IC:\Use
 rs\one\build\ParaView\paraview\VTK\Common\Math -IVTK\Common\Misc 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Misc -IVTK\Common\System 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\System 
-IVTK\Common\Transforms 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\Transforms 
-IVTK\Common\ExecutionModel 
-IC:\Users\one\build\ParaView\paraview\VTK\Common\ExecutionModel 
-IVTK\Filters\Core -IC:\Users\one\build\ParaView\paraview\VTK\Filters\Core 
-IVTK\Filters\General 

Re: [Paraview] Scaling cylinder glyph's radius and height individually

[Cory Quammen]

Ahmad,

Please keep replies on the mailing list. Responses are inlined.

On Tue, Jan 16, 2018 at 9:25 AM, Ahmad .  wrote:

> Hi Cory,
>
>
> Thanks for your reply.
>
>
> I am trying to implement your suggestion of extending the vtkGlyph3D with
> this additional "scaling by normals".
>
> The idea seems quite straightforward. I was just wondering how to
> incorporate this new class in my C++ pipeline.
>
> Currently I create the glyph, and set its properties, like this:
>
>
> vtkSmartPointer glyph;
> glyph.TakeReference(vtkSMSourceProxy::SafeDownCast(
> session_manager_->NewProxy("filters", "Glyph")));
> controller_->PreInitializeProxy(glyph);
>
> vtkSMPropertyHelper(glyph, "Input").Set(producer);
> vtkSMPropertyHelper(glyph, "Source").Set(
> GetCylinderSource(glyph));
> vtkSMPropertyHelper(glyph, "ScaleMode", true).Set(0);
> vtkSMPropertyHelper(glyph, "ScaleFactor", true).Set(1.0);
> vtkSMPropertyHelper(glyph, "GlyphMode", true).Set(0);
>
> As you can see I am not directly working with vtkGlyph3D or
> vtkPVGlyphFilter classes, but I am using the vtkSMPropertyHelper to take
> care of the boilerplate code.
>
>
Right. Unfortunately, implementing my suggestion would require creating a
subclass of vtkPVGlyphFilter and importing that with a ParaView plugin. See
the ParaView Howto on how to add a filter to ParaView.

> After I created a new class that has this extra scaling option, how would
> I go about using this in such a pipeline? Do I need to 'register' my "
> ModifiedGlyph" to the filter proxies to be able to do something like
> `NewProxy("filters", "ModifiedGlyph")`?
>

Yes, that should do it. Your modified glyph class will be available once
you've imported the ParaView plugin mentioned above.

A quick question about setting the active normals. Is there an existing way
> to do this, or would I need to do this myself? I would like to do this the
> same way one would set the "Scalars":
>
>
> vtkSMPropertyHelper(glyph, "Normals")
> .SetInputArrayToProcess(vtkDataObject::POINT, "ScalingArray");
>

I think that should work.

Best,
Cory


> Looking forward to your reply.
>
> Best,
> Ahmad
>
>
>
> --
> *Van:* Cory Quammen 
> *Verzonden:* dinsdag 9 januari 2018 15:30
> *Aan:* Ahmad .
> *CC:* paraview@paraview.org
> *Onderwerp:* Re: [Paraview] Scaling cylinder glyph's radius and height
> individually
>
> Hi Ahmad,
>
> Alas, reading the code of vtkGlyph3D, you cannot orient by a vector
> array different from the vector array used to do the scaling using the
> functionality in ParaView. You would have to modify either
> vtkPVGlyphFilter or its parent class vtkGlyph3D, to do this, and
> expose the new VTK class through a ParaView plugin [1]. A simple
> modification would be to add a ScaleMode, say VTK_SCALE_BY_NORMAL, to
> vtkGlyph3D, and then set the active normals in your data set to the
> vector by which you wish to scale. Then the "vectors" property could
> control the orientation and the active normals would control the
> scale. That's kind of kludgey, but it would be a fairly fast
> modification to make.
>
> HTH,
> Cory
>
> [1] https://www.paraview.org/Wiki/ParaView/Plugin_HowTo
> ParaView/Plugin HowTo - KitwarePublic
> 
> www.paraview.org
> Introduction. ParaView comes with plethora of functionality bundled in:
> several readers, multitude of filters, quite a few different types of views
> etc.
>
>
>
>
> On Tue, Jan 9, 2018 at 7:43 AM, Ahmad .  wrote:
> > Just want to add that a programmatic (C++) solution is preferred rather
> than
> > using the GUI
> >
> >
> > I have a C++ pipeline where I can set the properties of the cylinder
> glyph
> > with vtkSMPropertyHelper.
> >
> > I have looked in filters.xml under vtkPVGlyphFilter source proxy (file
> > located in
> > /ParaViewCore/ServerManager/SMApplication/Resources) to
> see
> > what my options are, but there is only one "SetInputArrayToProcess" that
> > takes a vector attribute as input; nothing about a vector specifically
> for
> > orientation..
> >
> > Suggestions on how to handle this issue, are very welcome; other
> approaches
> > than mine as well!
> >
> > 
> > Van: Ahmad . 
> > Verzonden: maandag 8 januari 2018 20:52
> > Aan: paraview@paraview.org
> > Onderwerp: Re: Scaling cylinder glyph's radius and height individually
> >
> >
> > Following up on my own question, I found out that if I scale by "Vector
> > Components" it is possible to change the length of the cylinders with the
> > second vector index, and the radius with the first and third. I need to
> > rearrange my attribute data as such: [radius_x, length, radius_z]. If I
> keep
> > radius_x == radius_z, then the cylinder will not deform, and the cross
> > section stays a perfect circle. See the image in the 

Re: [Paraview] ParaView + OpenVR (UNCLASSIFIED)

[Ken Martin]

Hi Simon & Benson,

I would bet steam has changed their API (again :-) and removed that method.
Maybe try downloading/git checkout using the 1.0.10 version of OpenVR. That
is what I last tested with and it should build fine against that.

Thanks!
Ken

On Thu, Jan 18, 2018 at 11:50 PM, Benson Muite  wrote:

> Hi,
>
> Does binary release version work for you? (At present only Windows is
> available), seem to be a few things to fix on Linux & Mac.
>
>
> Have you tried build using flags similar to binary release version?
> https://blog.kitware.com/taking-paraview-into-virtual-reality/
>
> Benson
>
> On 01/19/2018 01:29 AM, Su, Simon M CIV USARMY RDECOM ARL (US) wrote:
>
>> CLASSIFICATION: UNCLASSIFIED
>>
>> Hello,
>>
>> I am wondering how to build a version of ParaView with OpenVR plugin?
>> Which version of OpenVR shall I use? I used the OpenVR from
>> https://github.com/ValveSoftware/openvr  with just basic/minimal cmake
>> option. I am using the following  cmake line for ParaView
>>
>> cmake ..\paraview -DCMAKE_INSTALL_PREFIX=U:\tools\ParaView\ParaView
>> -DCMAKE_BUILD_TYPE=Release -G Ninja -DPARAVIEW_ENABLE_PYTHON:BOOL=ON
>> -DBUILD_TESTING:BOOL=OFF -DPARAVIEW_QT_VERSION=5 -DPARAVIEW_USE_MPI:BOOL=ON
>> -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON -DBOOST_INCLUDEDIR=U:/tools/bo
>> ost/boost-1.65.1/include/boost-1_65_1 
>> -DBOOST_ROOT=U:/tools/boost/boost-1.65.1
>> -DModule_vtkAcceleratorsVTKm:BOOL=ON -DModule_vtkRenderingOpenVR:BOOL=ON
>> -DPARAVIEW_BUILD_PLUGIN_OpenVR:BOOL=ON 
>> -DOPENVR_INCLUDE_DIR=U:/tools/OpenVR/OpenVR/include
>> -DOPENVR_LIBRARY=U:/tools/OpenVR/OpenVR/lib/openvr_api64.lib
>>
>> I am running into the following error
>>
>> C:\Users\one\build\ParaView\b>ninja
>> [47/14039] Building CXX object VTK\Rendering\OpenVR\CMakeFile
>> s\vtkRenderingOpenVR.dir\vtkOpenVRRenderWindow.cxx.obj
>> FAILED: VTK/Rendering/OpenVR/CMakeFiles/vtkRenderingOpenVR.dir/
>> vtkOpenVRRenderWindow.cxx.obj
>> C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1412~1.258\bin\Hostx64\x64\cl.exe
>> /nologo /TP -DMPICH_IGNORE_CXX_SEEK -DVTK_IN_VTK
>> -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE
>> -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_DEPRECATE
>> -D_SCL_SECURE_NO_WARNINGS -DvtkRenderingOpenVR_EXPORTS -I.
>> -IVTK\Rendering\OpenVR 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Rendering\OpenVR
>> -IVTK\Common\Core -IC:\Users\one\build\ParaView\paraview\VTK\Common\Core
>> -IVTK\Utilities\KWIML 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWIML
>> -IVTK\Utilities\KWSys 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Utilities\KWSys
>> -IVTK\ThirdParty\utf8 
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\utf8
>> -IVTK\Filters\Sources 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Filters\Sources
>> -IVTK\Common\ComputationalGeometry -IC:\Users\one\build\ParaView\
>> paraview\VTK\Common\ComputationalGeometry -IVTK\Common\DataModel
>> -IC:\Users\one\build\ParaView\paraview\VTK\Common\DataModel
>> -IVTK\Common\Math -IC:\Users\one\build\ParaView\paraview\VTK\Common\Math
>> -IVTK\Common\Misc -IC:\Users\one\build\ParaView\paraview\VTK\Common\Misc
>> -IVTK\Common\System -IC:\Users\one\build\ParaView\paraview\VTK\Common\System
>> -IVTK\Common\Transforms 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Common\Transforms
>> -IVTK\Common\ExecutionModel -IC:\Users\one\build\ParaView\
>> paraview\VTK\Common\ExecutionModel -IVTK\Filters\Core
>> -IC:\Users\one\build\ParaView\paraview\VTK\Filters\Core
>> -IVTK\Filters\General 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Filters\General
>> -IVTK\IO\Image -IC:\Users\one\build\ParaView\paraview\VTK\IO\Image
>> -IVTK\Utilities\DICOMParser -IC:\Users\one\build\ParaView\
>> paraview\VTK\Utilities\DICOMParser -IVTK\Utilities\MetaIO\vtkmetaio
>> -IVTK\Utilities\MetaIO 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Utilities\MetaIO
>> -IVTK\ThirdParty\zlib 
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\zlib
>> -IVTK\ThirdParty\jpeg 
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\jpeg
>> -IVTK\ThirdParty\png 
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\png
>> -IVTK\ThirdParty\tiff\vtktiff\libtiff -IVTK\ThirdParty\tiff
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\tiff
>> -IVTK\IO\XMLParser -IC:\Users\one\build\ParaView\paraview\VTK\IO\XMLParser
>> -IVTK\IO\Core -IC:\Users\one\build\ParaView\paraview\VTK\IO\Core
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\lz4\vtklz4\lib
>> -IVTK\ThirdParty\lz4\vtklz4 -IVTK\ThirdParty\lz4
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\lz4
>> -IVTK\ThirdParty\expat 
>> -IC:\Users\one\build\ParaView\paraview\VTK\ThirdParty\expat
>> -IVTK\Imaging\Sources 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Sources
>> -IVTK\Imaging\Core -IC:\Users\one\build\ParaView\paraview\VTK\Imaging\Core
>> -IVTK\Interaction\Style 
>> -IC:\Users\one\build\ParaView\paraview\VTK\Interaction\Style
>> -IVTK\Filters\Extraction -IC:\Users\one\build\ParaView\
>> 

Re: [Paraview] error when compiling Paraview 5.4 macOS 10.13

[Sergio Emanuel Galembeck]

Dear Cory,

Thank you! Paraview is working now!

Best regards,

Sergio

> On 12 Jan 2018, at 16:37, Cory Quammen  wrote:
> 
> Alas, this fix was made after ParaView 5.2 was released.
> 
> If you really need ParaView 5.2 instead of 5.3 or 5.4.1, you can apply
> the patch in my previous email to the VTK subdirectory in the ParaView
> source code. As you can see, just two lines need to be modified, so
> you could easily do this manually.
> 
> Hope that helps,
> Cory
> 
> On Fri, Jan 12, 2018 at 1:15 PM, Sergio Emanuel Galembeck
>  wrote:
>> Cory,
>> 
>> Sorry, I am trying to install Paraview 5.2.0. Even doing 'git submodule 
>> update —init’
>> the error that I noticed continues.
>> 
>> What do you suggest?
>> 
>> Thanks,
>> 
>> Sergio
>> 
>>> On 8 Jan 2018, at 12:38, Cory Quammen  wrote:
>>> 
>>> Sergio,
>>> 
>>> This problem was fixed in November 2016, so I am surprised you are
>>> running into it. Current ParaView master includes VTK that contains
>>> the commit
>>> 
>>> commit 33631146a85dfa64433c3997f166cbaa96bedee9
>>> Author: gnzlbg 
>>> Date:   Wed Nov 23 05:29:14 2016 -0500
>>> 
>>>   [bugfix] Invalid pointer comparisons.
>>> 
>>>   The code was performing a null pointer check
>>>   using (void*)Data <= 0 instead of Data == NULL
>>>   (or nullptr). This results in a compilation
>>>   error with clang trunk (future clang 4.0).
>>> 
>>> diff --git a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx
>>> b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx
>>> index 1e88f08..e89e153 100644
>>> --- a/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx
>>> +++ b/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx
>>> @@ -52,7 +52,7 @@ XdmfDsmComm::Receive(XdmfDsmMsg *Msg){
>>>XdmfErrorMessage("Cannot Receive Message of Length = " << 
>>> Msg->Length);
>>>return(XDMF_FAIL);
>>>}
>>> -if(Msg->Data <= 0 ){
>>> +if(Msg->Data == NULL){
>>>XdmfErrorMessage("Cannot Receive Message into Data Buffer = "
>>> << Msg->Length);
>>>return(XDMF_FAIL);
>>>}
>>> @@ -66,7 +66,7 @@ XdmfDsmComm::Send(XdmfDsmMsg *Msg){
>>>XdmfErrorMessage("Cannot Send Message of Length = " << Msg->Length);
>>>return(XDMF_FAIL);
>>>}
>>> -if(Msg->Data <= 0 ){
>>> +if(Msg->Data == NULL) {
>>>XdmfErrorMessage("Cannot Send Message from Data Buffer = " <<
>>> Msg->Length);
>>>return(XDMF_FAIL);
>>>}
>>> 
>>> Make sure you have run `git submodule update` to ensure your VTK is up to 
>>> date.
>>> 
>>> HTH,
>>> Cory
>>> 
>>> On Mon, Jan 8, 2018 at 6:55 AM, Sergio Emanuel Galembeck
>>>  wrote:
 Hello,
 
 I am trying to compile Paraview 5.4 in MacOS 10.13.2 (High Sierra), using
 software from MacPorts 2.4.2. After a successful configuration,
 the make -j 4 command give the following error:
 
 /Users/sergiogalembeck/paraview_install/ParaView/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx:55:18:
 error:
 ordered comparison between pointer and zero ('void *' and 'int')
   if(Msg->Data <= 0 ){
 
 How can I solve this problem?
 
 Best regards,
 
 Sergio
 
 
 
 ___
 Powered by www.kitware.com
 
 Visit other Kitware open-source projects at
 http://www.kitware.com/opensource/opensource.html
 
 Please keep messages on-topic and check the ParaView Wiki at:
 http://paraview.org/Wiki/ParaView
 
 Search the list archives at: http://markmail.org/search/?q=ParaView
 
 Follow this link to subscribe/unsubscribe:
 https://paraview.org/mailman/listinfo/paraview
 
>>> 
>>> 
>>> 
>>> --
>>> Cory Quammen
>>> Staff R Engineer
>>> Kitware, Inc.
>> 
> 
> 
> 
> -- 
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.

___
Powered by www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

[Paraview] Visualize equdistant cell-centered data

[Buesing, Henrik]

Dear all,

I have a "Structured (Curvilinear) Grid" (*.vts), which gets read in as 314531 
cells and 33 points. I would like to tell Paraview that this is equidistant 
cell-centered data (33 cells). I want every cell to get one color, such 
that color interpolation becomes correct.

Can I somehow convert the data I have?

Thank you!
Henrik Büsing

___
Powered by www.kitware.com

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

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

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

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview