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

[Cory Quammen]

On Fri, Feb 2, 2018 at 4:44 AM, Andrew Parker
 wrote:
> Cory,
>
> As a follow up.  Can I ask if it would be possible to do all that is
> suggested on Scott's page:
> https://www.paraview.org/Wiki/Advanced_Tips_and_Tricks#Animating_a_static_vector_field
>
> Along with all of your additional steps below from your last post (be great
> to add these to Scott's page), entirely in pvpython or pvbatch?  I make use
> of the anaconda version from here: https://anaconda.org/conda-forge/paraview
>
> Would it be possible do you think to script all of this? I have not tired it
> yet I should add just checking for show stoppers before I begin.

I don't foresee any showstoppers. To make scripting easier, use the
Python tracing capability within the ParaView GUI. Tools menu -> Start
Trace, then perform the suggested actions. When done, choose Tools ->
Stop Trace, and you will see a dialog with the generated script that
you can use as a starting point.

Thanks,
Cory

> 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 

[Paraview] vtu and/or vtu to vtp file

[Daniel Zuidinga]

Hi,

is it possible to convert vtk and/or vtu to vtp file via paraview?

br


___
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

Re: [Paraview] undefined symbol: PyUnicodeUCS2_AsEncodedString

[Fabian Wein]

Hi Shawn,

It looks to me like you built against a Python that was configured with UCS2 
unicode objects and are linking to a Python that was configured with UCS4 
unicode objects.  Python is not ABI-compatible with other Pythons that were 
built with a different kind of unicode support.


I aggree with your observation. The point is, that not me is linking but it is 
the paraview-superbuild which failes. With USE_SYSTEM_python=OFF I would expect 
that my system python is not touched?!

BTW, I can confirm that it works with USE_SYSTEM_python=ON, so a trivial 
workaround exists.

Fabian
___
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

Re: [Paraview] undefined symbol: PyUnicodeUCS2_AsEncodedString

[Shawn Waldon]

Hi Fabian,

It looks to me like you built against a Python that was configured with
UCS2 unicode objects and are linking to a Python that was configured with
UCS4 unicode objects.  Python is not ABI-compatible with other Pythons that
were built with a different kind of unicode support.

Shawn

On Fri, Feb 2, 2018 at 10:55 AM, Fabian Wein  wrote:

> It get's (for me) strange:
>
> nm /home/fwein/code/cfs_paraview/build_python/build/install/lib
> 64/python2.7/lib-dynload/_struct.so | grep PyUni
>  U PyUnicodeUCS2_AsEncodedString
>
> nm -D /usr/lib64/python2.7/lib-dynload/_struct.so | grep PyUnico
>  U PyUnicodeUCS4_AsEncodedString
>
> This is as I would expect it. So, I don't understand the error message:
>
> ImportError: /home/fwein/code/cfs_paraview/build_python/build/install/lib
> 64/python2.7/lib-dynload/_struct.so: undefined symbol:
> PyUnicodeUCS2_AsEncodedString
>
> Is the error message wrong with the filename?
>
> Mabye the path are set wrong?!
>
>
> Fabian
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/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
>
___
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

Re: [Paraview] vtu and/or vtu to vtp file

[Sebastien Jourdain]

Yes, you might need to "Extract Surface" filter, then select the new output
and save the dataset from the menu.

On Fri, Feb 2, 2018 at 8:52 AM, Daniel Zuidinga  wrote:

> Hi,
>
> is it possible to convert vtk and/or vtu to vtp file via paraview?
>
> br
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/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
>
___
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] undefined symbol: PyUnicodeUCS2_AsEncodedString

[Fabian Wein]

I build latest head of paraview-superbuild with Python enabled and 
USE_SYSTEM_PYTHON=OFF on a openSUSE Tumbleweed system

I get the following error
Scanning dependencies of target CinemaPython
[  2%] Copying files for Python package 'cinema_python'
[  2%] Compiling Python package 'cinema_python'
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 174, in _run_module_as_main
[  2%] Building CXX object 
VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/CMakeFiles/vtkxdmf2.dir/XdmfHeavyData.cxx.o
[  2%] Building CXX object 
ThirdParty/protobuf/vtkprotobuf/src/CMakeFiles/protoc_compiler.dir/google/protobuf/stubs/strutil.cc.o
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib64/python2.7/compileall.py", line 16, in 
import struct
  File "/usr/lib64/python2.7/struct.py", line 1, in 
from _struct import *
ImportError: 
/home/fwein/code/cfs_paraview/build_python/build/install/lib64/python2.7/lib-dynload/_struct.so:
 undefined symbol: PyUnicodeUCS2_AsEncodedString
gmake[8]: *** [ThirdParty/cinema/CMakeFiles/CinemaPython.dir/build.make:61: 
ThirdParty/cinema/cinema_python.build-complete] Error 1
gmake[7]: *** [CMakeFiles/Makefile2:1192: 
ThirdParty/cinema/CMakeFiles/CinemaPython.dir/all] Error 2
gmake[7]: *** Waiting for unfinished jobs

To my knowledge one need to decide if Python is compiled with 16 or 32 bit 
encoding,

on my system I have 32 bit:

/usr/bin/python2
Python 2.7.14 (default, Oct 12 2017, 15:50:02) [GCC] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import sys
print(sys.maxunicode)

1114111

When I try the Python built from PV, it has 16 bits:

/home/fwein/code/cfs_paraview/build_python/build/superbuild/python/build/python
Python 2.7.14 (default, Feb  2 2018, 15:33:16)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import sys
print(sys.maxunicode)

65535

So the mixing from own built python and system python makes problems.

Is this mixing a bug?

Currently, I don't need python in PV, and for my colleague SYSTEM_PYTHON 
worked. So just to let you know.

BTW, what is the status with python3?

Fabian
___
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

Re: [Paraview] How to insert annotate time info into catalyst?

[Andy Bauer]

For Catalyst Live you can use the Python Annotation filter to show the time
after you've extracted the Annotate Time Filter from the Calalyst
simulation run. You'll need to change the Array Association to Row Data and
put in "Text.GetValue(0)" in the Expression.

On Mon, Jan 29, 2018 at 8:59 PM, Seong Mo Yeon 
wrote:

> Hi, Andi Bauer,
>
> I found that annotate time filter works in live visualization and the
> error occurs when output rendering components is activated.
> gdb says the error occurs at vtkSMBoundsDomain.cxx: 60
>   vtkPVDataInformation* info = this->GetInputInformation();
>   if (info)
>   {
> double bounds[6];
> info->GetBounds(bounds);
> this->SetDomainValues(bounds);
>   }
>
> and the vtkPVDataInformation has the following information:
>
> members of vtkPVDataInformation:
>   DataSetType = 19,
>   CompositeDataSetType = -1,
>   NumberOfDataSets = 1,
>   NumberOfPoints = 0,
>   NumberOfCells = 1,
>   NumberOfRows = 1,
>   MemorySize = 1,
>   PolygonCount = 0,
>   Bounds = {1.0001e+299, -1.0001e+299,
> 1.0001e+299, -1.0001e+299, 1.0001e+299,
> -1.0001e+299},
>   Extent = {2147483647 <(214)%20748-3647>, -2147483647 <(214)%20748-3647>,
> 2147483647 <(214)%20748-3647>, -2147483647 <(214)%20748-3647>, 2147483647
> <(214)%20748-3647>, -2147483647 <(214)%20748-3647>},
>   TimeSpan = {-1.0001e+299, 1.0001e+299},
>   Time = 0.0050001,
>   HasTime = 1,
>   NumberOfTimeSteps = 0,
>   DataClassName = 0x5996b050 "vtkTable",
>   TimeLabel = 0x0,
>   CompositeDataClassName = 0x0,
>   CompositeDataSetName = 0x0,
>   PointDataInformation = 0x58ec6430,
>   CellDataInformation = 0x58ec66d0,
>   FieldDataInformation = 0x58ec6770,
>   VertexDataInformation = 0x58ec6890,
>   EdgeDataInformation = 0x58ec67f0,
>   RowDataInformation = 0x58ec6370,
>   CompositeDataInformation = 0x58eb5430,
>   PointArrayInformation = 0x58ec6c50,
>   PortNumber = 0
>
> my guess is that annotate time filter is a type of vtkTable and Bounds
> member variable has too large values. Any idea?
>
> Regards
>
> SeongMo
>
> On 2018년 1월 27일 AM 2:06 +0900, Andy Bauer , wrote:
>
> Hi SeongMo,
>
> The AnnotateTime source should work with Catalyst. See the attached images
> and the annotatetime.py script which I used to create it.
>
> With your script, what do your images look like?
>
> You could also try what Ufuk mentioned. I think his work is based on
> weather/climate time scales so he has to handle months, leap years, etc.
> which ParaView itself doesn't handle naturally. You can see some of the
> things he's done with Catalyst at https://blog.kitware.com/
> integration-of-paraview-catalyst-with-regional-earth-system-model/.
>
> Best,
> Andy
>
> On Thu, Jan 25, 2018 at 10:47 AM, SeongMo  wrote:
>
>> Dear Andy Bauer,
>>
>> For the color map issue, I think ParaView 5.4.1 resolved it. But, I could
>> not figure out annotate time filter issue. may be it is just simple problem
>> but I am not sure. Coprocess routine is as follows and python script is
>> attached.
>>
>> It would be appreciated if you make some advice.
>>
>>
>> void CoProcess(Foam::fvMesh& mesh, Foam::Time& runTime)
>> {
>>vtkNew dataDescription;
>>dataDescription->AddInput("input");
>>const double time = runTime.value();
>>const unsigned int timeStep = runTime.timeIndex();
>>dataDescription->SetTimeData(time, timeStep);
>>
>>if (runTime.end())
>>{
>>// assume that we want to all the pipelines to execute
>>// if it is the last time step
>>dataDescription->ForceOutputOn();
>>}
>>if (Processor->RequestDataDescription(dataDescription.GetPointer())
>> != 0)
>>{
>>Foam::polyMesh::readUpdateState meshState = mesh.readUpdate();
>>
>>if(meshState != Foam::polyMesh::UNCHANGED)
>>{
>>// mesh moved? or mesh topology changed?
>>BuildVTKGrid(mesh, true);
>>}
>>UpdateVTKAttributes(mesh);
>>dataDescription->GetInputDescriptionByName("input")->
>>SetGrid(multiBlockDataSet);
>>Processor->CoProcess(dataDescription.GetPointer());
>>}
>> }
>>
>> Regards.
>>
>> SeongMo
>>
>> SeongMo Yeon, Ph.D, Senior Engineer
>> Offshore Hydrodynamics Research
>> SAMSUNG HEAVY INDUSTRIES CO., LTD.
>> Central Research Institute
>> E-mail : seongmo.y...@gmail.com
>> Tel :
>> 
>> Fluctuat nec mergitur
>>
>> On 01/25/2018 06:56 AM, Andy Bauer wrote:
>>
>> Hi Seongmo,
>>
>> Please keep the conversations on the mailing list so that anyone can
>> follow along or participate. Also, these types of things often get lost in
>> my inbox when they don't make it back to the ParaView mailing list.
>>

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

[Cory Quammen]

Ahmad,

First, I recommend that you try loading your plugin in the ParaView
UI, using the ParaView that you built your plugin against. Then, in
Tools -> Manage Plugins. Click on Load New... and select the file
libvtkPVGlyphFilterP.so. You should now be able to find your filter
GlyphP in the Filters menu.

Second, to instantiate the filter the way you are trying is correct,
but first you need to load the plugin. I believe you can do it this
way:

vtkSMPluginManager::LoadLocalPlugin("//libvtkPVGlyphFilterP.so");

HTH,
Cory



On Thu, Feb 1, 2018 at 1:12 PM, Ahmad .  wrote:
> Sorry about that Cory; will keep this in the mailing list.
>
>
> I have tried to implement your suggestion, and now I have generated a plugin
> file "libvtkPVGlyphFilterP.so".
>
> Please find the files I used to create this plugin in the attachment.
>
>
> What I did after compiling the plugin:
>
>
> Try to use the new class I made, like such:
> `session_manager_->NewProxy("filters", "GlyphP")));`
> where GlyphP is what I called my custom glyph filter (see the xml file in
> the attachment).
> Compile my application against "libvtkPVGlyphFilterP.so".
> Run my application and get the following error:
>
>
> ERROR: In
> /home/ahmad/paraview/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx,
> line 526
> vtkSIProxyDefinitionManager (0x294d320): No proxy that matches:
> group=filters and proxy=GlyphP were found.
>
> I feel like I am missing an important step, which has to do with the XML
> file, but I don't know how.
>
> In the Plugin Wiki of ParaView the instructions I find after compiling are:
> Then using cmake and a build system, one can build a plugin for this new
> filter. Once this plugin is loaded the filter will appear under the
> "Alphabetical" list in the Filters menu.
> There are no instructions on how to use the new class in a C++ pipeline...
>
> Any pointers on this?
>
> Best,
> Ahmad
>
> 
> Van: Cory Quammen 
> Verzonden: vrijdag 19 januari 2018 16:59
> Aan: Ahmad .; ParaView
>
> Onderwerp: Re: [Paraview] Scaling cylinder glyph's radius and height
> individually
>
> 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 

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

[Andrew Parker via ParaView]

Cory,

As a follow up.  Can I ask if it would be possible to do all that is
suggested on Scott's page:
https://www.paraview.org/Wiki/Advanced_Tips_and_Tricks#
Animating_a_static_vector_field

Along with all of your additional steps below from your last post (be great
to add these to Scott's page), entirely in pvpython or pvbatch?  I make use
of the anaconda version from here: https://anaconda.org/conda-forge/paraview

Would it be possible do you think to script all of this? I have not tired
it yet I should add just checking for show stoppers before I begin.
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 

[Paraview] Fwd: Integrate Variables Over a Volume

[Andrew]

[Sorry, I forgot to change the mail address to Paraview. So copying it to
the list.]

Hello. I use ParaView 5.4.1 and I checked Integrate Variables on volume
now. It works but, as in some other cases in ParaView, it requires the
single entities type. For example, if you have a domain (volume) and
boundaries (surfaces), it will not work on you whole input. Use Extract
Block to extract the "real" volume prior the Integrate Variables.
There is the other thing that is not very good concerning this "entity type
problem". If you use the Calculator filter on mixed entities (fluid domain
+ boundaries) it says that it cannot find a variable, although it shows
this variable in it's drop-down list. It's confusing if you encounter this
the first time or have forgotten about this issue. May be it would be
better to introduce some sort of message to inform a user that there is a
"mixed entity issue".

2018-02-01 22:59 GMT+03:00 Steytler, Louis Louw :

> Hi Everyone,
>
> Is there a way to integrate point or cell data over a volume in ParaView?
>
> It seems the "Integrate Variables" filter only integrates point and cell
> data over lines and surfaces. From the help documentation:
>
> "The Integrate Attributes filter integrates point and cell data over lines
> and surfaces. It also computes length of lines, area of surface, or volume.
> "
>
> I tried integrating over a volume, but this produced an error.
>
> Is there another way to do this?
>
> Any advice would be much appreciated.
>
> Thanks very much,
>
> Louis Steytler
> Department of Mechanical Science and Engineering
> University of Illinois at Urbana-Champaign
> 1206 West Green Street
> Urbana, Il 61801
> steyt...@illinois.edu
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/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
>
>
___
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