Re: [Paraview] [ANNOUNCE] ParaView 5.5.1 now available for download

2018-06-06 Thread Burlen Loring 

Hi Utkarsh,

Sorry I missed your reply, I thought my post got bounced and didn't look.

BUILD_SHARED_LIBS=OFF and PARAVIEW_USE_VISITBRIDGE=ON will reproduce the 
issue.


I was able to quickly move past it by finding VISIT_STATIC in the cmake 
code and making the following change


ParaView/Utilities/VisItBridge$git diff
diff --git a/Library/VisItLib/CMake/VisItCommon.cmake 
b/Library/VisItLib/CMake/VisItCommon.cmake

index 0bfad93..b4f136c 100644
--- a/Library/VisItLib/CMake/VisItCommon.cmake
+++ b/Library/VisItLib/CMake/VisItCommon.cmake
@@ -26,14 +26,14 @@ if(VISIT_DISABLE_COMPILER_WARNINGS)
 endif(VISIT_DISABLE_COMPILER_WARNINGS)

 #set up some vars we need to compile
-set(VISIT_STATIC)
-if (BUILD_SHARED_LIBS)
+#set(VISIT_STATIC)
+#if (BUILD_SHARED_LIBS)
   set(VISIT_STATIC 0)
   add_definitions(-DVISIT_BUILD_SHARED_LIBS)
-else(VISIT_STATIC)
-  set(VISIT_STATIC 1)
-  add_definitions(-DVISIT_STATIC -DGLEW_STATIC)
-endif()
+#else(VISIT_STATIC)
+#  set(VISIT_STATIC 1)
+#  add_definitions(-DVISIT_STATIC -DGLEW_STATIC)
+#endif()

 set(VISIT_SOURCE_DIR ${VisItBridgePlugin_SOURCE_DIR})
 set(VISIT_BINARY_DIR ${VisItBridgePlugin_BINARY_DIR})


On 06/05/2018 01:15 PM, Utkarsh Ayachit wrote:

Burlen,

Are you doing a static build of ParaView? What Cmake flags did you use?

Utkarsh


___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Adding Filters to Catalyst

2018-06-06 Thread Gregg Streuber 
Hey Andy,

Apologies, I must have hit “reply” without thinking, rather than reply all.  
I’ve actually managed to resolve that issue, it turned out to be a 
configuration issue with my build of OpenGL.

I do have another question though.  I’ve been playing around processing some 
data using Catalyst’s python scripting in parallel and the results aren’t quite 
what I expected.  What I’ve been using is a toy 50,000,000 node cube mesh with 
an arbitrary velocity field, and having Catalyst do some assorted processing – 
taking cuts etc.  I’ve divided the mesh into 256 blocks using the 
VTKMultiBlockDataSet structure, on 256 cores.  But when I load the results into 
Paraview it only indicates 12 VTKBlocks on the VTBBlockColors filter. There are 
256 divisions in the mesh, but 244 of them are duplicates, coloured with one of 
the 1st 12 colours.

Adding new lines to the color map, mapped to values >11, doesn’t appear to 
change anything.

I’m also not seeing much in the way  of performance variation when I use 13-256 
cores, it’s only when I drop below 12 that things take appreciably longer.

Is Paraview by default only taking advantage of 12 cores at a time?  Is this 
something I can change?

From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Wednesday, June 06, 2018 10:18 AM
To: Gregg Streuber ; Paraview 
(parav...@paraview.org) 
Subject: Re: [Paraview] Adding Filters to Catalyst

Hi Gregg,

Please keep the conversations on the mailing list so that everyone can 
participate (also, emails get lost in my inbox so that can also delay a quick 
response).

I believe that the Catalyst examples should compile properly with all of the 
Catalyst editions (though I haven't tested them). If you were able to use an 
OpenGL with some editions then that should work for any edition that depends on 
OpenGL. Are you working with a Catalyst edition build directory or an install 
directory? If you give me some more information on how to reproduce the error I 
can try and track things down.

Also, what version of ParaView are you using?

Cheers,
Andy

On Fri, Jun 1, 2018 at 3:37 PM Gregg Streuber 
mailto:gregg.streu...@aero.bombardier.com>> 
wrote:
Hi Andy,

Thanks for the information.  I had a full compile of Paraview running on the 
side just in case, I was just curious if there was an easy and efficient way to 
customize a Catalyst install.

I’ve since gotten Paraview compiled, but when I try to test the functionality 
using some of the included Catalyst examples (Examples/Catalyst) they don’t 
work.  Specifically several of them throw “undefined reference” errors during 
compilation, referring to a couple of OpenGL files in the Paraview install.  
These examples worked fine when I compiled them with the Catalyst build I was 
testing before.  Do these examples require a specific build of OpenGL (or are 
they incompatible with certain other modules)?

Thanks,
Gregg

From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Friday, June 01, 2018 11:46 AM
To: Gregg Streuber 
mailto:gregg.streu...@aero.bombardier.com>>
Cc: paraview@public.kitware.com
Subject: Re: [Paraview] Adding Filters to Catalyst

Hi Gregg,

You can always use a full build of ParaView for Catalyst to make sure you get 
all of the filters available during Catalyst runs.

There is information at 
https://blog.kitware.com/paraview-catalyst-editions-what-are-they/ which gives 
details about the editions but there's currently not a lot of details on how to 
make your own edition. Editing the cmake.sh script to add in more VTK filters 
will likely not work as the Catalyst editions don't even have all of the source 
code from the ParaView source.

As for finding the full list of filters and modules available, the blog post 
has some of that but it's changed some. My recommendation would be to build an 
edition with Python enabled and then use pvpython to see what's available. 
Alternatively you could look at files like filters.xml in the Catalyst source 
code to see what's there. It's not ideal but allows you to check on stuff 
before actually running a simulation.

Best,
Andy

On Fri, Jun 1, 2018 at 10:10 AM Gregg Streuber 
mailto:gregg.streu...@aero.bombardier.com>> 
wrote:
Hi All,

I’ve recently installed the most full-featured version of Catalyst available on 
the website, but I noticed it’s lacking a lot of filters that I need very much 
(streamlines, for example).  I understand the installed packages are fully 
customizable, but can’t find any good documentation on how to go about doing 
this.   Is this as simple as enabling different options in the cmake.sh script? 
And if so, is there a complete list of the filters in paraview and the modules 
that contain them somewhere?

Cheers,
Gregg
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

Visit other

Re: [Paraview] Find the intersection point between a connectivity and a stream tracer

2018-06-06 Thread Caffagni, Andrea 
Thank you Cory for the answer,
Your idea works also if I have, instead of a slice, only a portion of a slice 
(I cut slices portions thanks to the connectivity filter)?
In the image attached, I have created a connectivity (in blue) of a slice and a 
streamline in red that crosses it.

Best Regards,
Andrea

From: Cory Quammen [mailto:cory.quam...@kitware.com]
Sent: Wednesday, June 06, 2018 15:27
To: Caffagni, Andrea
Cc: paraview@public.kitware.com
Subject: Re: [Paraview] Find the intersection point between a connectivity and 
a stream tracer

Andrea,

In fact, you can use the Slice filter itself to compute the intersection of 
streamlines with a plane. Just apply a Slice filter to your StreamTracer 
output, align the Slice with your desired plane, and you will get the 
intersection points.

See the attached image that shows stream tracer output, the plane widget from 
the Slice filter (red rectangle), and the intersection points depicted with 
blue spherical glyphs.

HTH,
Cory

On Wed, Jun 6, 2018 at 7:23 AM Caffagni, Andrea 
mailto:andrea.caffa...@ferrari.com>> wrote:
Does anyone have an idea on how to deal with this problem?
Does Paraview have no tools to easily find a point of intersection between plan 
and line?

Best Regards,
Andrea

From: Caffagni, Andrea
Sent: Thursday, May 31, 2018 14:19
To: paraview@public.kitware.com
Subject: Find the intersection point between a connectivity and a stream tracer

Dear Users,
I need to find the intersection point between a connectivity surface (portion 
of a slice) and a stream tracer that runs through this.
I have tried the IntersectFragments it doesn’t work with stream tracer.
Someone of you have some suggestions?
Best regards,
Andrea


_



Questo messaggio è da intendersi esclusivamente ad uso del destinatario e può 
contenere informazioni che sono di natura privilegiata, confidenziale o non 
divulgabile secondo le leggi vigenti. Se il lettore del presente messaggio non 
è il destinatario designato, o il dipendente/agente responsabile per la 
consegna del messaggio al destinatario designato, si informa che ogni 
disseminazione, distribuzione o copiatura di questa comunicazione è vietata 
anche ai sensi della normativa vigente in materia di protezione dei dati 
personali. Se avete ricevuto questo messaggio per errore, vi preghiamo di 
notificarcelo immediatamente a mezzo e-mail di risposta e successivamente di 
procedere alla cancellazione di questa e-mail e relativi allegati dal vostro 
sistema.

_



This message is intended only for the use of the addressee and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If the reader of this message is not the intended recipient, or 
the employee or agent responsible for delivering the message to the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is prohibited under the applicable data 
protection law. If you have received this e-mail by mistake, please notify us 
immediately by return e-mail and delete this e-mail and all attachments from 
your system.



_
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview


--
Cory Quammen
Staff R Engineer
Kitware, Inc.

_



Questo messaggio è da intendersi esclusivamente ad uso del destinatario e può 
contenere informazioni che sono di natura privilegiata, confidenziale o non 
divulgabile secondo le leggi vigenti. Se il lettore del presente messaggio non 
è il destinatario designato, o il dipendente/agente responsabile per la 
consegna del messaggio al destinatario designato, si informa che ogni 
disseminazione, distribuzione o copiatura di questa comunicazione è vietata 
anche ai sensi della normativa vigente in materia di protezione dei dati 
personali. Se avete ricevuto questo messaggio per errore, vi preghiamo di 
notificarcelo immediatamente a mezzo e-mail di risposta e successivamente di 
procedere alla cancellazione di questa e-mail e relativi allegati dal vostro 
sistema.

Re: [Paraview] Fw: How do we get the indexes and IDs from the extracted selections to be seen in the Trace?

2018-06-06 Thread Favre Jean 

The indices of the points selected are in a field called "vtkOriginalPointIds". 
It is a field with a special meaning and is hidden in some cases.

if you write the selected data to disk, it will show up as field 
"vtkOriginalPointIds"

Consider the pvpython code below:

from paraview.simple import *

w = Wavelet()
w.UpdatePipeline()

selection=SelectPoints()
selection.QueryString="RTData <= 40"
selection.FieldType = 'POINT'
selection.UpdatePipelineInformation()

# create a new 'Extract Selection'
mySelection = ExtractSelection(Input=w, Selection=selection)
mySelection.UpdatePipeline()
SaveData("foo.vtk", mySelection)

and inspect the contents of foo.vtk, you will find your ids.

if you need more, I simply use a Python Calculator to rename the field and I 
can then access the array

passthru = PythonCalculator(Input = mySelection)
passthru.Expression = 'inputs[0].PointData["vtkOriginalPointIds"]'
passthru.ArrayAssociation = "Point Data"
passthru.ArrayName = 'ids'
passthru.UpdatePipeline()

passthru.GetPointDataInformation().GetArray("ids").GetName()

HTH
Jean





___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

[Paraview] rgb lookup table

2018-06-06 Thread Claudio via ParaView 
Hi,I'm stuck with a problem concerning colors assignment to data.I've a list of 
8 tensors (here represented as circular ellipsoids, see short vtk file below)I 
typically open the file and filter using ("tensor glyph").Now I would like to 
assign to each tensor glyph a unique color specified by an rgba sequence (e.g. 
0.1 0.3 0.2 1)How can I do that? I tried to append a scalar lookup table 
followed by a rgba one but without successThanks   -Claudio

# vtk DataFile Version 3.0Random data to test tensorsASCIIDATASET 
UNSTRUCTURED_GRIDPOINTS 8 float0 0 01 0 00 1 01 1 00 0 11 0 10 1 11 1 1
POINT_DATA 8
TENSORS spherical_ellipsoid float1 0 00 1 00 0 1
1 0 00 1 00 0 1
1 0 00 1 00 0 1
1 0 00 1 00 0 1
1 0 00 1 00 0 1
1 0 00 1 00 0 1
1 0 00 1 00 0 1
1 0 00 1 00 0 1
SCALARS sample_scalars float 1LOOKUP_TABLE rgbtable01234567
LOOKUP_TABLE rgbtable 80.2 0.4 0.3 1.004.0 2.0 1.0 1.00.4 1.0 0.2 1.01.0 1.0 
0.7 1.00.2 0.0 5.0 1.01.0 0.2 1.0 1.02.0 1.0 1.0 1.00.0 1.0 0.9 1.0


___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [Paraview-developers] Reminder: ParaView community support is transitioning to discourse.paraview.org

2018-06-06 Thread Cory Quammen 
On Wed, Jun 6, 2018 at 10:37 AM Sgouros, Thomas 
wrote:

> Thank you. Will the VTK forums be moving there, too?
>

That is eventually the plan.

Cory


>  -Tom
>
> On Wed, Jun 6, 2018 at 10:15 AM, Cory Quammen 
> wrote:
>
>> Hi ParaView community,
>>
>> This is just a reminder that we are transitioning our community support
>> forums to
>>
>> https://discourse.paraview.org/
>>
>> Discourse is now the preferred place to post new topics and help
>> requests. In just a week of operation there are already a good number of
>> discussions taking place there.
>>
>> By the way, if you prefer interacting via mailing list, Discourse
>> provides a mailing list mode that you can enable by following the guide
>> Utkarsh posted:
>>
>> https://discourse.paraview.org/t/using-discourse-as-a-mailing-list/64
>>
>> Thanks!
>>
>> Cory
>>
>> --
>> Cory Quammen
>> Staff R Engineer
>> Kitware, Inc.
>>
>> ___
>> Powered by www.kitware.com
>>
>> ParaView development discussion is moving! Please visit
>> https://discourse.paraview.org/ for future posts.
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> https://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>

-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] [Paraview-developers] Reminder: ParaView community support is transitioning to discourse.paraview.org

2018-06-06 Thread Sgouros, Thomas 
Thank you. Will the VTK forums be moving there, too?

 -Tom

On Wed, Jun 6, 2018 at 10:15 AM, Cory Quammen 
wrote:

> Hi ParaView community,
>
> This is just a reminder that we are transitioning our community support
> forums to
>
> https://discourse.paraview.org/
>
> Discourse is now the preferred place to post new topics and help
> requests. In just a week of operation there are already a good number of
> discussions taking place there.
>
> By the way, if you prefer interacting via mailing list, Discourse provides
> a mailing list mode that you can enable by following the guide Utkarsh
> posted:
>
> https://discourse.paraview.org/t/using-discourse-as-a-mailing-list/64
>
> Thanks!
>
> Cory
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.
>
> ___
> Powered by www.kitware.com
>
> ParaView development discussion is moving! Please visit
> https://discourse.paraview.org/ for future posts.
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=
> Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview-developers
>
>
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Adding Filters to Catalyst

2018-06-06 Thread Andy Bauer 
Hi Gregg,

Please keep the conversations on the mailing list so that everyone can
participate (also, emails get lost in my inbox so that can also delay a
quick response).

I believe that the Catalyst examples should compile properly with all of
the Catalyst editions (though I haven't tested them). If you were able to
use an OpenGL with some editions then that should work for any edition that
depends on OpenGL. Are you working with a Catalyst edition build directory
or an install directory? If you give me some more information on how to
reproduce the error I can try and track things down.

Also, what version of ParaView are you using?

Cheers,
Andy

On Fri, Jun 1, 2018 at 3:37 PM Gregg Streuber <
gregg.streu...@aero.bombardier.com> wrote:

> Hi Andy,
>
>
>
> Thanks for the information.  I had a full compile of Paraview running on
> the side just in case, I was just curious if there was an easy and
> efficient way to customize a Catalyst install.
>
>
>
> I’ve since gotten Paraview compiled, but when I try to test the
> functionality using some of the included Catalyst examples
> (Examples/Catalyst) they don’t work.  Specifically several of them throw
> “undefined reference” errors during compilation, referring to a couple of
> OpenGL files in the Paraview install.  These examples worked fine when I
> compiled them with the Catalyst build I was testing before.  Do these
> examples require a specific build of OpenGL (or are they incompatible with
> certain other modules)?
>
>
>
> Thanks,
> Gregg
>
>
>
> *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
> *Sent:* Friday, June 01, 2018 11:46 AM
> *To:* Gregg Streuber 
> *Cc:* paraview@public.kitware.com
> *Subject:* Re: [Paraview] Adding Filters to Catalyst
>
>
>
> Hi Gregg,
>
>
>
> You can always use a full build of ParaView for Catalyst to make sure you
> get all of the filters available during Catalyst runs.
>
>
>
> There is information at
> https://blog.kitware.com/paraview-catalyst-editions-what-are-they/ which
> gives details about the editions but there's currently not a lot of details
> on how to make your own edition. Editing the cmake.sh script to add in more
> VTK filters will likely not work as the Catalyst editions don't even have
> all of the source code from the ParaView source.
>
>
>
> As for finding the full list of filters and modules available, the blog
> post has some of that but it's changed some. My recommendation would be to
> build an edition with Python enabled and then use pvpython to see what's
> available. Alternatively you could look at files like filters.xml in the
> Catalyst source code to see what's there. It's not ideal but allows you to
> check on stuff before actually running a simulation.
>
>
>
> Best,
>
> Andy
>
>
>
> On Fri, Jun 1, 2018 at 10:10 AM Gregg Streuber <
> gregg.streu...@aero.bombardier.com> wrote:
>
> Hi All,
>
>
>
> I’ve recently installed the most full-featured version of Catalyst
> available on the website, but I noticed it’s lacking a lot of filters that
> I need very much (streamlines, for example).  I understand the installed
> packages are fully customizable, but can’t find any good documentation on
> how to go about doing this.   Is this as simple as enabling different
> options in the cmake.sh script? And if so, is there a complete list of the
> filters in paraview and the modules that contain them somewhere?
>
>
>
> Cheers,
>
> Gregg
>
> ___
> Powered by www.kitware.com
>
> ParaView discussion is moving! Please visit
> https://discourse.paraview.org/ for future posts.
>
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

[Paraview] Reminder: ParaView community support is transitioning to discourse.paraview.org

2018-06-06 Thread Cory Quammen 
Hi ParaView community,

This is just a reminder that we are transitioning our community support
forums to

https://discourse.paraview.org/

Discourse is now the preferred place to post new topics and help requests.
In just a week of operation there are already a good number of discussions
taking place there.

By the way, if you prefer interacting via mailing list, Discourse provides
a mailing list mode that you can enable by following the guide Utkarsh
posted:

https://discourse.paraview.org/t/using-discourse-as-a-mailing-list/64

Thanks!

Cory

-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Fw: How do we get the indexes and IDs from the extracted selections to be seen in the Trace?

2018-06-06 Thread Cory Quammen 
On Wed, Jun 6, 2018 at 9:37 AM Sarah Flaherty  wrote:

> If it does not show in the trace, is it possible to access those numbers
> through the python shell?
>

Alas, the situation is the same.

As a workaround, you can add a GenerateIds filter to your data to generate
point and cell IDs, and add an Extract Selection filter with Preserve
Topology on, which generates a 'vtkInsidedness' point and cell array
marking which points/cells have been selected. Then, you can add an Append
Attributes filter to both the GenerateIds and Extract Selection filters to
combine the IDs and vtkInsidedness arrays. Finally, add z Threshold filter
and threshold by the vtkInsidedness array. The result will be a data set
containing only selected cells and points with the original cell/point IDs.
You can then access these IDs through Python.

Cory


> Sarah
> --
> *From:* Cory Quammen 
> *Sent:* Wednesday, June 6, 2018 9:31:41 AM
> *To:* Sarah Flaherty
> *Cc:* paraview@public.kitware.com; ParaView
> *Subject:* Re: [Paraview] Fw: How do we get the indexes and IDs from the
> extracted selections to be seen in the Trace?
>
> Hi Sarah,
>
> I'm afraid that selections are not currently well supported in Python.
> Because of that, they are not recorded in Python traces.
>
> It is on our todo list to provide a real Python API for selections in one
> of the next ParaView releases.
>
> Best regards,
> Cory
>
> On Wed, Jun 6, 2018 at 9:17 AM Sarah Flaherty 
> wrote:
>
> Paraview,
>
> I am trying to have the index of the points that are selected and
> extracted displayed in the trace. They are seen in the Properties Bar on
> the right when the ExtractSelection1 is active, however they are not seen
> in the trace. How do I get this information into python script or the trace?
> Thank you,
> Sarah Flaherty
> ___
> Powered by www.kitware.com
>
> ParaView discussion is moving! Please visit
> https://discourse.paraview.org/ for future posts.
>
> 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://public.kitware.com/mailman/listinfo/paraview
>
>
>
> --
> Cory Quammen
> Staff R Engineer
> Kitware, Inc.
>


-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Fw: How do we get the indexes and IDs from the extracted selections to be seen in the Trace?

2018-06-06 Thread Sarah Flaherty 
Cory,

If it does not show in the trace, is it possible to access those numbers 
through the python shell?
Sarah


From: Cory Quammen 
Sent: Wednesday, June 6, 2018 9:31:41 AM
To: Sarah Flaherty
Cc: paraview@public.kitware.com; ParaView
Subject: Re: [Paraview] Fw: How do we get the indexes and IDs from the 
extracted selections to be seen in the Trace?

Hi Sarah,

I'm afraid that selections are not currently well supported in Python. Because 
of that, they are not recorded in Python traces.

It is on our todo list to provide a real Python API for selections in one of 
the next ParaView releases.

Best regards,
Cory

On Wed, Jun 6, 2018 at 9:17 AM Sarah Flaherty 
mailto:sjflahe...@loyola.edu>> wrote:
Paraview,

I am trying to have the index of the points that are selected and extracted 
displayed in the trace. They are seen in the Properties Bar on the right when 
the ExtractSelection1 is active, however they are not seen in the trace. How do 
I get this information into python script or the trace?
Thank you,
Sarah Flaherty

___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview


--
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] Fw: How do we get the indexes and IDs from the extracted selections to be seen in the Trace?

2018-06-06 Thread Cory Quammen 
Hi Sarah,

I'm afraid that selections are not currently well supported in Python.
Because of that, they are not recorded in Python traces.

It is on our todo list to provide a real Python API for selections in one
of the next ParaView releases.

Best regards,
Cory

On Wed, Jun 6, 2018 at 9:17 AM Sarah Flaherty  wrote:

> Paraview,
>
> I am trying to have the index of the points that are selected and
> extracted displayed in the trace. They are seen in the Properties Bar on
> the right when the ExtractSelection1 is active, however they are not seen
> in the trace. How do I get this information into python script or the trace?
> Thank you,
> Sarah Flaherty
> ___
> Powered by www.kitware.com
>
> ParaView discussion is moving! Please visit
> https://discourse.paraview.org/ for future posts.
>
> 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://public.kitware.com/mailman/listinfo/paraview
>


-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

[Paraview] Fw: How do we get the indexes and IDs from the extracted selections to be seen in the Trace?

2018-06-06 Thread Sarah Flaherty 
Paraview,

I am trying to have the index of the points that are selected and extracted 
displayed in the trace. They are seen in the Properties Bar on the right when 
the ExtractSelection1 is active, however they are not seen in the trace. How do 
I get this information into python script or the trace?
Thank you,
Sarah Flaherty
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] JSON based new meta file format for series added

2018-06-06 Thread Favre Jean 

Never, I'll answer my own question.
Must have been an operator error.

Selecting "All Files (*)" and simply double-clicking on the file name does the 
job.

That is a great addition to ParaView. Well done!

Jean
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview

[Paraview] JSON based new meta file format for series added

2018-06-06 Thread Favre Jean 
ParaView 5.5 Release Notes present a JSON-based reader for time series. I have 
prepared a meta-data file for a series of *vtu files, I called it 
name.vtu.series

but ParaView 5.5.1 does not present me with any choice of reader  which would 
accept it. Is there a compile option to enable, or what is the trick?

*.series are not listed as "Supported Files"

Here are the first few lines of my file:

{
  "file-series-version" : "1.0",
  "files" : [
{ "name" : "noname_000.vtu", "time" : 0.0 },
{ "name" : "noname_251.vtu", "time" : 0.0335713 },
{ "name" : "noname_358.vtu", "time" : 0.066844 },
{ "name" : "noname_440.vtu", "time" : 0.100014 },
..etc...
  ]
}
Any help would be appreciated.
-
Jean
___
Powered by www.kitware.com

ParaView discussion is moving! Please visit https://discourse.paraview.org/ for 
future posts.

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://public.kitware.com/mailman/listinfo/paraview