Re: [Paraview] Script driven paraview
Utkarsh: Thanks! Works! I had tried that: I thought it had not worked, because it (python?, pvpython?) did not print to the screen from a test script. Is there a way to print info to the screen (or to a specified file)? When I use Run Script (to run show_vtu.py) from the python shell that is started when Tools - Python Shell is manually selected, prints to the screen work. Thanks, Tim On Wed, May 8, 2013 at 8:09 AM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: You can use the --script command line argument to paraview executable to run a Python script after startup e,g, paraview --script=show_vtu.py Utkarsh On Sat, May 4, 2013 at 12:45 PM, Timothy Cale drtsc.p...@gmail.com wrote: I would like to display a set of meshes that result from a (bash) script driven set of simulations and meshing steps. I have written a script that does what I want (at least basically), if I manually go into the paraview gui and start the (Tools --) Python Shell, then hit run script and select the desired script. In an attempt to automate the visialization, I wrote a bash script with the two relevant lines being: paraview /dev/null pvpython show_vtu.py This generates non-persistent, non-interactive images that I expect - though it would be good to know if there is a way to make such images persistent and interactive. (in addition to starting paraview) Question: Is there a way to use such a script (bash, python called from bash . . . ) to start paraview, and use a script to visualize data in the gui? Thanks, Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] dynamic variable names in pvython
Pat:
Thanks. Makes sense, though complicated (for me).
Being new to python, pvpython and vtk, I used the append attribute of lists.
Do you see a problem with that idea, as shown below? It works, but that is
not always the end of the story.
(num is the read number of vtu files to be processed):
files[]
reader[]
rep[]
. . .
i=0
while inum
. . .
files.append('results/layer_'+str(i+1)+'.vtu')
reader.append(XMLUnstructuredGridReader(FileName=files[i]))
rep.append(Show())
Render()
i=i+1
Thanks,
Ti
On Sun, May 5, 2013 at 2:35 AM, Pat Marion pat.mar...@kitware.com wrote:
Hi Tim,
Variable names in trace are generated by this function defined in
smtrace.py:
def pyvariable_from_proxy_name(proxy_name):
return servermanager._make_name_valid(proxy_name.replace(., _))
That function will generate a suitable variable name from a proxy name. A
proxy is registered with a name in a proxy group. smtrace.py also defines
some functions to lookup the proxy name given a proxy and a proxy group.
For example:
from paraview import smtrace
s = Sphere()
smtrace.get_source_proxy_registration_name(s)
'Sphere1'
smtrace.pyvariable_from_proxy_name('Sphere1')
'Sphere1'
help(smtrace.get_source_proxy_registration_name)
Help on function get_source_proxy_registration_name in module
paraview.smtrace:
get_source_proxy_registration_name(proxy)
Assuming the given proxy is registered in the group 'sources',
lookup the proxy's registration name with the servermanager
help(smtrace.get_view_proxy_registration_name)
Help on function get_view_proxy_registration_name in module
paraview.smtrace:
get_view_proxy_registration_name(proxy)
Assuming the given proxy is registered in the group 'views',
lookup the proxy's registration name with the servermanager
Pat
On Sun, May 5, 2013 at 3:01 AM, Timothy Cale drtsc.p...@gmail.com wrote:
I use paraview to visualize the results of simulations.
I use Trace in the paraview gui, in order to use the generated scripts to
help guide
the development of the pypython script I use to visualize my simulation
results.
I would like to use dynamic variable names, and note that the scripts
generated
by Trace seem to use dynamic variable names.
Aside: The driver for this is that the number of meshes I want to display
differs
with each simulation.
I have looked over python posts on dynamic variable names . . .
Question: How are the (seemingly) dynamic variable names created
in/by/during
Trace?
Regards,
Tim
PS: Linux
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Script driven paraview
I would like to display a set of meshes that result from a (bash) script driven set of simulations and meshing steps. I have written a script that does what I want (at least basically), if I manually go into the paraview gui and start the (Tools --) Python Shell, then hit run script and select the desired script. In an attempt to automate the visialization, I wrote a bash script with the two relevant lines being: paraview /dev/null pvpython show_vtu.py This generates non-persistent, non-interactive images that I expect - though it would be good to know if there is a way to make such images persistent and interactive. (in addition to starting paraview) Question: Is there a way to use such a script (bash, python called from bash . . . ) to start paraview, and use a script to visualize data in the gui? Thanks, Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] dynamic variable names in pvython
I use paraview to visualize the results of simulations. I use Trace in the paraview gui, in order to use the generated scripts to help guide the development of the pypython script I use to visualize my simulation results. I would like to use dynamic variable names, and note that the scripts generated by Trace seem to use dynamic variable names. Aside: The driver for this is that the number of meshes I want to display differs with each simulation. I have looked over python posts on dynamic variable names . . . Question: How are the (seemingly) dynamic variable names created in/by/during Trace? Regards, Tim PS: Linux ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] (no subject)
Sebastien: Thank you! That indeed what I was looking for. Is there a place where one can find out about (look up) such things? I spent an hour or so yesterday trying to guess writer.FileType='Ascii'. My apologies for not including a subject line on my first submission, and for any confusion due to trying to send a file that is too large. New to the mailing list. Thanks again! Regards, Tim On Sat, Dec 1, 2012 at 8:42 AM, Sebastien Jourdain sebastien.jourd...@kitware.com wrote: Here is the script that you should run from paraview.simple import * data = XMLPolyDataReader( FileName=['/.../file.vtp'] ) smooth = Smooth(data) smooth.NumberofIterations = 200 writer = CreateWriter(foo.ply, smooth) writer.FileType = 'Ascii' writer.UpdatePipeline() On Fri, Nov 30, 2012 at 3:10 PM, Timothy Cale drtsc.p...@gmail.comwrote: Sebastien: The data file I attached to the previous version of this update note was too large. I am resending the note with that file removed. Tim -- Forwarded message -- From: Timothy Cale drtsc.p...@gmail.com Date: Fri, Nov 30, 2012 at 1:03 PM Subject: Re: [Paraview] (no subject) To: Sebastien Jourdain sebastien.jourd...@kitware.com Cc: paraview@paraview.org paraview@paraview.org Update: I am able to write a ply file using CreateWriter (see attached first_stab.py and nanovtp files). But the ply file is in binary. I looked around for more than an hour to find out how to write the file in ascii - to no avail. Any hints? Aside: When I put in 0 (for ascii) as a third arg. to CreateWriter, pvpython complained about having more than 2 arguments. I note that in the paraview users guide, CreateWriter has several arguments in some cases. help(CreateWriter) indicates that more than 2 arguments can be used: help(CreateWriter) Help on function CreateWriter in module paraview.simple: CreateWriter(filename, proxy=None, **extraArgs) Creates a writer that can write the data produced by the source proxy in the given file format (identified by the extension). If no source is provided, then the active source is used. This doesn't actually write the data, it simply creates the writer and returns it. Regards, Tim On Fri, Nov 30, 2012 at 10:15 AM, Timothy Cale drtsc.p...@gmail.comwrote: Sebastien: Good question: My goal is to have a script which smooths results between simulation steps (fortran codes). I use paraview to view results, and the smoothing filter in paraview seems to do what I want. I want to start with a Trace-generated python script, and edit it to write the vertices and element info to a file (.ply would be nice) that the next code can read. So, fortunately for me (in some sense), I decided to upgrade my ubuntu OS to 12.10. This has paraview 3.14.1-6build1 on its software list (aptitude). This version corrected a bug (with pvpython) in the version of paraview 3.14 that I was using. (I also spent a day trying to get/install other versions. That was not very successful.) Now if I import the trace generated py file, it pops up (and stays). Not a very good image, but it is a start! Being new to python and paraview, this is quite a step. Any suggestions as to how to write vertex/node info would be appreciated. Thanks, Tim On Thu, Nov 29, 2012 at 7:41 PM, Sebastien Jourdain sebastien.jourd...@kitware.com wrote: I don't know ? what your script is supposed to do ? Render an image and quit ? On Thu, Nov 29, 2012 at 1:19 PM, Timothy Cale drtsc.p...@gmail.comwrote: I am using paraview 3.14 (64 bit, ubuntu 12.04 vm on a MBP). I am trying to run pvpython to view .py files generated using Trace: 'which' pvpython' yields: /usr/bin/pvpython 'pvpython' yields: Error converting executable file /usr/bin/../lib/paraview/pvpython to real path: No such file or directory So, /usr/bin/python seems to be looking for /usr/lib/paraview/pvpython Which is indeed not there. I uninstalled (purged) and installed 3.14 again. Same thing. BTW: I did see the notes regarding 3.14.1-2 from ~6 months ago, but cannot tell which 3.14 binary installer is on the Paraview download page. Nevertheless, I downloaded the 3.14 tar-ball. When I run a .py script generated using trace, an image pops up for a second, then disappears. BTW: The same thing happens with 3.98, at least on a companion machine. What am I missing? Thanks, Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
Re: [Paraview] (no subject)
Sebastien: As a follow up: Usingwriter.FileType = 'Ascii' did work to complete the script generated by Trace. (first_stab.py) On the other hand, the script you sent did not work, as sent. By comparing the two scripts, and removing/adding back lines of code, the only line I needed to add to your (stand-alone, rather than Trace-generated) script is: DataRepresentation3 = Show() after smoothing. With that line, the slightly modified version of the script you sent is: from paraview.simple import * nanocone_pvd_1_vtp = XMLPolyDataReader( FileName=['/home/tscale/pv_sims/results/nanocone_pvd_1.vtp'] ) Smooth1 = Smooth() Smooth1.NumberofIterations = 200 DataRepresentation3 = Show() writer = CreateWriter(foo2.ply,Smooth1) writer.FileType='Ascii' writer.UpdatePipeline() del writer (Note that I changed the name of the imported data in your script, and added del writer at the end.) I have no clue as to what this line does, but if it is not there, the following message (among a lot of other output) appears: vtkSMWriterFactory (0xc89c10): No matching writer found for extension: ply Thanks again, Tim On Sat, Dec 1, 2012 at 8:42 AM, Sebastien Jourdain sebastien.jourd...@kitware.com wrote: Here is the script that you should run from paraview.simple import * data = XMLPolyDataReader( FileName=['/.../file.vtp'] ) smooth = Smooth(data) smooth.NumberofIterations = 200 writer = CreateWriter(foo.ply, smooth) writer.FileType = 'Ascii' writer.UpdatePipeline() On Fri, Nov 30, 2012 at 3:10 PM, Timothy Cale drtsc.p...@gmail.comwrote: Sebastien: The data file I attached to the previous version of this update note was too large. I am resending the note with that file removed. Tim -- Forwarded message -- From: Timothy Cale drtsc.p...@gmail.com Date: Fri, Nov 30, 2012 at 1:03 PM Subject: Re: [Paraview] (no subject) To: Sebastien Jourdain sebastien.jourd...@kitware.com Cc: paraview@paraview.org paraview@paraview.org Update: I am able to write a ply file using CreateWriter (see attached first_stab.py and nanovtp files). But the ply file is in binary. I looked around for more than an hour to find out how to write the file in ascii - to no avail. Any hints? Aside: When I put in 0 (for ascii) as a third arg. to CreateWriter, pvpython complained about having more than 2 arguments. I note that in the paraview users guide, CreateWriter has several arguments in some cases. help(CreateWriter) indicates that more than 2 arguments can be used: help(CreateWriter) Help on function CreateWriter in module paraview.simple: CreateWriter(filename, proxy=None, **extraArgs) Creates a writer that can write the data produced by the source proxy in the given file format (identified by the extension). If no source is provided, then the active source is used. This doesn't actually write the data, it simply creates the writer and returns it. Regards, Tim On Fri, Nov 30, 2012 at 10:15 AM, Timothy Cale drtsc.p...@gmail.comwrote: Sebastien: Good question: My goal is to have a script which smooths results between simulation steps (fortran codes). I use paraview to view results, and the smoothing filter in paraview seems to do what I want. I want to start with a Trace-generated python script, and edit it to write the vertices and element info to a file (.ply would be nice) that the next code can read. So, fortunately for me (in some sense), I decided to upgrade my ubuntu OS to 12.10. This has paraview 3.14.1-6build1 on its software list (aptitude). This version corrected a bug (with pvpython) in the version of paraview 3.14 that I was using. (I also spent a day trying to get/install other versions. That was not very successful.) Now if I import the trace generated py file, it pops up (and stays). Not a very good image, but it is a start! Being new to python and paraview, this is quite a step. Any suggestions as to how to write vertex/node info would be appreciated. Thanks, Tim On Thu, Nov 29, 2012 at 7:41 PM, Sebastien Jourdain sebastien.jourd...@kitware.com wrote: I don't know ? what your script is supposed to do ? Render an image and quit ? On Thu, Nov 29, 2012 at 1:19 PM, Timothy Cale drtsc.p...@gmail.comwrote: I am using paraview 3.14 (64 bit, ubuntu 12.04 vm on a MBP). I am trying to run pvpython to view .py files generated using Trace: 'which' pvpython' yields: /usr/bin/pvpython 'pvpython' yields: Error converting executable file /usr/bin/../lib/paraview/pvpython to real path: No such file or directory So, /usr/bin/python seems to be looking for /usr/lib/paraview/pvpython Which is indeed not there. I uninstalled (purged) and installed 3.14 again. Same thing. BTW: I did see the notes regarding 3.14.1-2 from ~6 months ago, but cannot tell which 3.14 binary installer is on the Paraview download page. Nevertheless, I downloaded the 3.14 tar-ball. When I run a .py script generated
Re: [Paraview] (no subject)
Sebastien: Good question: My goal is to have a script which smooths results between simulation steps (fortran codes). I use paraview to view results, and the smoothing filter in paraview seems to do what I want. I want to start with a Trace-generated python script, and edit it to write the vertices and element info to a file (.ply would be nice) that the next code can read. So, fortunately for me (in some sense), I decided to upgrade my ubuntu OS to 12.10. This has paraview 3.14.1-6build1 on its software list (aptitude). This version corrected a bug (with pvpython) in the version of paraview 3.14 that I was using. (I also spent a day trying to get/install other versions. That was not very successful.) Now if I import the trace generated py file, it pops up (and stays). Not a very good image, but it is a start! Being new to python and paraview, this is quite a step. Any suggestions as to how to write vertex/node info would be appreciated. Thanks, Tim On Thu, Nov 29, 2012 at 7:41 PM, Sebastien Jourdain sebastien.jourd...@kitware.com wrote: I don't know ? what your script is supposed to do ? Render an image and quit ? On Thu, Nov 29, 2012 at 1:19 PM, Timothy Cale drtsc.p...@gmail.comwrote: I am using paraview 3.14 (64 bit, ubuntu 12.04 vm on a MBP). I am trying to run pvpython to view .py files generated using Trace: 'which' pvpython' yields: /usr/bin/pvpython 'pvpython' yields: Error converting executable file /usr/bin/../lib/paraview/pvpython to real path: No such file or directory So, /usr/bin/python seems to be looking for /usr/lib/paraview/pvpython Which is indeed not there. I uninstalled (purged) and installed 3.14 again. Same thing. BTW: I did see the notes regarding 3.14.1-2 from ~6 months ago, but cannot tell which 3.14 binary installer is on the Paraview download page. Nevertheless, I downloaded the 3.14 tar-ball. When I run a .py script generated using trace, an image pops up for a second, then disappears. BTW: The same thing happens with 3.98, at least on a companion machine. What am I missing? Thanks, Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Fwd: (no subject)
Sebastien: The data file I attached to the previous version of this update note was too large. I am resending the note with that file removed. Tim -- Forwarded message -- From: Timothy Cale drtsc.p...@gmail.com Date: Fri, Nov 30, 2012 at 1:03 PM Subject: Re: [Paraview] (no subject) To: Sebastien Jourdain sebastien.jourd...@kitware.com Cc: paraview@paraview.org paraview@paraview.org Update: I am able to write a ply file using CreateWriter (see attached first_stab.py and nanovtp files). But the ply file is in binary. I looked around for more than an hour to find out how to write the file in ascii - to no avail. Any hints? Aside: When I put in 0 (for ascii) as a third arg. to CreateWriter, pvpython complained about having more than 2 arguments. I note that in the paraview users guide, CreateWriter has several arguments in some cases. help(CreateWriter) indicates that more than 2 arguments can be used: help(CreateWriter) Help on function CreateWriter in module paraview.simple: CreateWriter(filename, proxy=None, **extraArgs) Creates a writer that can write the data produced by the source proxy in the given file format (identified by the extension). If no source is provided, then the active source is used. This doesn't actually write the data, it simply creates the writer and returns it. Regards, Tim On Fri, Nov 30, 2012 at 10:15 AM, Timothy Cale drtsc.p...@gmail.com wrote: Sebastien: Good question: My goal is to have a script which smooths results between simulation steps (fortran codes). I use paraview to view results, and the smoothing filter in paraview seems to do what I want. I want to start with a Trace-generated python script, and edit it to write the vertices and element info to a file (.ply would be nice) that the next code can read. So, fortunately for me (in some sense), I decided to upgrade my ubuntu OS to 12.10. This has paraview 3.14.1-6build1 on its software list (aptitude). This version corrected a bug (with pvpython) in the version of paraview 3.14 that I was using. (I also spent a day trying to get/install other versions. That was not very successful.) Now if I import the trace generated py file, it pops up (and stays). Not a very good image, but it is a start! Being new to python and paraview, this is quite a step. Any suggestions as to how to write vertex/node info would be appreciated. Thanks, Tim On Thu, Nov 29, 2012 at 7:41 PM, Sebastien Jourdain sebastien.jourd...@kitware.com wrote: I don't know ? what your script is supposed to do ? Render an image and quit ? On Thu, Nov 29, 2012 at 1:19 PM, Timothy Cale drtsc.p...@gmail.comwrote: I am using paraview 3.14 (64 bit, ubuntu 12.04 vm on a MBP). I am trying to run pvpython to view .py files generated using Trace: 'which' pvpython' yields: /usr/bin/pvpython 'pvpython' yields: Error converting executable file /usr/bin/../lib/paraview/pvpython to real path: No such file or directory So, /usr/bin/python seems to be looking for /usr/lib/paraview/pvpython Which is indeed not there. I uninstalled (purged) and installed 3.14 again. Same thing. BTW: I did see the notes regarding 3.14.1-2 from ~6 months ago, but cannot tell which 3.14 binary installer is on the Paraview download page. Nevertheless, I downloaded the 3.14 tar-ball. When I run a .py script generated using trace, an image pops up for a second, then disappears. BTW: The same thing happens with 3.98, at least on a companion machine. What am I missing? Thanks, Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview first_stab.py Description: Binary data ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] (no subject)
I am using paraview 3.14 (64 bit, ubuntu 12.04 vm on a MBP). I am trying to run pvpython to view .py files generated using Trace: 'which' pvpython' yields: /usr/bin/pvpython 'pvpython' yields: Error converting executable file /usr/bin/../lib/paraview/pvpython to real path: No such file or directory So, /usr/bin/python seems to be looking for /usr/lib/paraview/pvpython Which is indeed not there. I uninstalled (purged) and installed 3.14 again. Same thing. BTW: I did see the notes regarding 3.14.1-2 from ~6 months ago, but cannot tell which 3.14 binary installer is on the Paraview download page. Nevertheless, I downloaded the 3.14 tar-ball. When I run a .py script generated using trace, an image pops up for a second, then disappears. BTW: The same thing happens with 3.98, at least on a companion machine. What am I missing? Thanks, Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Trace?
David: Thanks for the feedback. I am new to mailing lists: I cc'd paraview@paraview.org on this note - I hope that covers your request to keep the discussion on the mailing list. WRT Trace: Thank you for the links: I will need to spend time learning how to read the material . . . For now, I notice that the .py script (first_stab.py - which is attached) does not seem to direct the saving of a .ply file - which was one of the sequence of actions taken during the Trace. Is saving/writing a file part of what Trace is to record? (I used Save Data.) Thanks, Tim On Wed, Nov 28, 2012 at 6:44 AM, David E DeMarle dave.dema...@kitware.comwrote: Please keep the discussion on the mailing list so everyone can benefit. The upshot: Is there a way to use this .py file either in an executable, or between executables? Python is a particularly good glue language. You can have you scripts/programs call pvbatch yourscript.py and/or call arbitrary scripts/executables from within yourscript.py. For examples of how to call out from python see: http://stackoverflow.com/questions/89228/calling-an-external-command-in-python Once I get that going, I can generate a version of the .py file appropriate for each sim. I assume that can be refined to using filenames as arguments as I get off of my knuckles. For examples of command line argument access in python see: http://www.tutorialspoint.com/python/python_command_line_arguments.htm first_stab.py Description: Binary data ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Trace?
David: Thanks. I do indeed have a lot of learning potential. WRT Trace: You indicate that Trace should record a save action? I am not sure why Trace (the way I used it) did not record the Save Data action during my GUI session. What should I do to get Trace to record that action? Regards, Tim On Wed, Nov 28, 2012 at 9:04 AM, David E DeMarle dave.dema...@kitware.comwrote: Is saving/writing a file part of what Trace is to record? (I used Save Data.) Correct. Add a call to WriteImage(filename.png) to dump an png. Add this to your reading list: http://paraview.org/Wiki/ParaView/Python_Scripting And make liberal use of help() and tab completion in the python shell within the Paraview GUI as you learn. Thanks, Tim On Wed, Nov 28, 2012 at 6:44 AM, David E DeMarle dave.dema...@kitware.com wrote: Please keep the discussion on the mailing list so everyone can benefit. The upshot: Is there a way to use this .py file either in an executable, or between executables? Python is a particularly good glue language. You can have you scripts/programs call pvbatch yourscript.py and/or call arbitrary scripts/executables from within yourscript.py. For examples of how to call out from python see: http://stackoverflow.com/questions/89228/calling-an-external-command-in-python Once I get that going, I can generate a version of the .py file appropriate for each sim. I assume that can be refined to using filenames as arguments as I get off of my knuckles. For examples of command line argument access in python see: http://www.tutorialspoint.com/python/python_command_line_arguments.htm ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Trace?
I use save/load state to make viewing more efficient: viewing results during a simulation. Now I would like to make the results of a filter (say smoothing) avialable to downstream simulation steps. 'Trace' looks (looked) promising, but I don't get an option to save the trace (under Tools) after starting and stopping the trace. Does Trace work? If so, what does it take? I guess the first question might be: Will Trace let me run in 'batch'? Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] saving files
I am calling paraview from fortran code that I am developing. I am using system calls to load states; very nice. Specifically, I use 'load state' to create a view of an isosurface. I now save taht data (manually, as a ply file), and read the file in for further processing. Is there a way, hopefully w/o learning python (at this time), to save files within paraview - without my intervention? Thanks, Tim ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Can I stop the verbiage that occurs when I start paraview?
I am new to paraview and vtk. (The paraview page I was on, pointed me here . . .) When I start paraview (v.3.14.1, 64-bit), as installed using aptitude on ubuntu 12.04. I get dozens of messages that I don't understand, upon issuing 'paraview ', or any other approach I have taken. Examples are below. Paraview seems to work OK, though I am using it for simple visualizations right now. I do not remember having this problem (at least not to this extent) when using a previous version of paraview. (I think it was 3.4, which was the version supplied via aptitude for ubuntu 10.04.) Is there a way to stop the messages, even if it is just asking it to run in quiet mode? Thanks, Tim void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Threshold under id 138 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Glyph under id 134 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Calculator under id 143 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Annotate Time Filter under id 176 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Calculator under id 143 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Cell Centers under id 137 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Cell Data to Point Data under id 140 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Clip under id 145 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Contingency Statistics under id 170 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Contour under id 144 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Descriptive Statistics under id 171 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Extract Edges under id 133 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Extract Level under id 151 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Extract Selection under id 155 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Extract Subset under id 147 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action FOF/SOD Halo Finder under id 153 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Feature Edges under id 141 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Generate Surface Normals under id 135 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Glyph under id 134 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Group Datasets under id 150 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Histogram under id 156 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Integrate Variables under id 157 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Intersect Fragments under id 167 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action K Means under id 172 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Material Interface Filter under id 168 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Mesh Quality under id 139 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Multicorrelative Statistics under id 173 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Normal Glyphs under id 132 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Outline Corners under id 136 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Particle Pathlines under id 177 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action ParticleTracer under id 178 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Plot Data under id 158 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Plot Global Variables Over Time under id 159 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Plot On Intersection Curves under id 160 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Plot On Sorted Lines under id 161 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Plot Over Line under id 162 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Plot Selection Over Time under id 163 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Principal Component Analysis under id 174 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action Probe Location under id 164 void
