David: Thanks for the feedback.
I am new to mailing lists: I cc'd [email protected] 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 <[email protected]>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 >
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
