[Paraview] Probe location in a script

[Cory Quammen]

Mc Fly,

ParaView always runs as a client-server application, even when just using
the GUI without connecting to a remote server (i.e., the "builtin" server).
The data resides on the server, while the commands you execute are on the
client. Hence, you need to move the data from the server to the client to
access it directly.

Fortunately, this is easy. Let's assume that your ProbeLocation filter is
named "Probelocation". Then all you need to do is run

polyData = servermanager.Fetch(Probelocation)

This brings the probe data, in the form of a vtkPolyData, over to the
client side. Now you can access the probed data through the PointData
attribute of the polyData object:

pointData = polyData.GetPointData()
rhoArray = pointData.GetArray('rho')
value = rhoArray.GetTuple(0)

I hope that helps. For more information on using Fetch, see [1].

Cheers,
Cory

[1] http://www.paraview.org/Wiki/ParaView/Python_Scripting#Source_Proxies



On Fri, Jul 3, 2015 at 4:21 AM, <mctolille at netcourrier.com> wrote:

>  Thanks for the script, but how can I now access the data that were found
> by ProbeLocation? How can I put them in a variable, print them on the
> screen?
>
> Cheers,
> Mc Fly
>
>
>
>
> ---- Message d'origine ----
> De : "Armin Wehrfritz" <dkxls23 at gmail.com>
> À : paraview at paraview.org
> Objet : Re: [Paraview] Probe location in a script
> Date : 02/07/2015 17:07:42 CEST
>
>
> Here is a little script that shows you how to read and write dataset in
> ParaView using a simple for loop.
>
> Hope this helps.
>
> -Armin
>
>
>
>
> On 07/02/2015 05:47 PM, mctolille at netcourrier.com wrote:
> > Thanks for the tip. I actually already used tracing in order to find the
> > command:
> > Probelocation.ProbeType.Center = [10.0,20.0,30.0]
> >
> > But the problem is that I don't know how to access to the data (rho, vx,
> > vy...) at that location in the python script
> >
> > And since tracing does not capture "Save data", I don't even know how to
> > write the data in a file
> >
> > Cheers,
> > Mc Fly
> >
> >
> >
> >
> > Date : 02/07/2015 15:55:04 CEST
> >
> > Hi McFly,
> >
> > The Python Tracing facility in ParaView is perfect for this kind of
> > task. It records a trace of your actions in the ParaView GUI to a Python
> > script that you can modify a bit to process a bunch of files. To turn on
> > tracing, choose the Tools -> Start Trace menu item.
> >
> > More info on tracing is available in the ParaView User Guide [1] under
> > section 1.6.2.
> >
> > Best regards,
> > Cory
> >
> > [1] http://www.paraview.org/paraview-guide/
> >
> > On Thu, Jul 2, 2015 at 9:39 AM, <mctolille at netcourrier.com
> > <mailto:mctolille at netcourrier.com>> wrote:
> >
> > __
> >
> > Hi everybody,
> >
> > I am a new Paraview user. I am trying to extract points from a bunch
> > of vtu files. It is pretty easily done with "probe location". But
> > since I have a lot of files, I would like to automatize the process
> > (with a macro or a python script).
> >
> > Could someone maybe show me how it's done?
> >
> > My best guess is that I should have the following in a python script:
> > Probelocation.ProbeType.Center = [10.0,20.0,30.0]
> > assuming I want to probe at x=10, y=20, z=30. But then, I don't
> > really know how to retrieve the variables values at that location.
> >
> > Thanks a lot,
> > Mc Fly
> >
> > _______________________________________________
> > Powered by www.kitware.com <http://www.kitware.com>
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
> >
> >
> >
> > --
> > Cory Quammen
> > R&D 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:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150703/1f20eba5/attachment.html>