Hi,
I just found this page and wonder, if this will be a new approach for
python scripting:
http://www.paraview.org/ParaView3/index.php/Visualization_Script_Examples#Paraview_Python_Script_with_PVFWrap
In addition, there are comments about the VisIt way... do you plan
something like this!?
No. PVFWrap was a prototype interface that has been substantially improved to
become the current paraview.simple. Most people use the python trace to
establish their initial python scripts and then modify them, but if you know
the names of the filters and only want to specify changes from defau
That page is ancient.
I think PVFWrap was the predecessor to paraview.simple which since 3.6
is the standard way to do ParaView python scripting (see python
trace).
The comments about paraview state files being too verbose have been
addressed since then as well.
Or did you mean something else?
D
Hello,
thanks for the info!
Is my impression correct, that in version 3.8.1 the python trace state
process is not as 'complete' as using the old state file approach?
For my case setup, e.g. there is not always the correct camera position
and the correct slices...
Best Regards!
Fabian
On 01/2
Hi Fabian,
Regarding your issue of python trace state not replicating your paraview
state exactly, I believe both issues you quote (camera position and cut
filter's slice property) have been addressed in the latest version of
paraview. If not, can you list the steps required to repeat the problem
You are using 3.8.0, not 3.8.1. If you use 3.8.1 to generate the trace
script you will not receive these errors.
Your script can also be fixed by hand- editing test_trace.py and move the
lines at the very bottom modifying Slice1, Slice2 and Slice3. Moving the
lines up so they appear after the
Oh, sorry... at work I got 3.8.1, I mixed this up. I thought that I had
there similar behavior (not the error message)... I will check again.
Best Regards!
Fabian
On 01/24/2011 09:45 PM, pat marion wrote:
You are using 3.8.0, not 3.8.1. If you use 3.8.1 to generate the trace
script you will n
Hi Fabian,
Please remember to include the paraview mailing list when you reply.
What you report is a bug, but you can avoid it- when you open your openfoam
dataset you should check each block that you want to load *before you hit
apply for the first time*
The problem is the first time you load y
Hello Pat,
thanks for the explanation and help!
Best Regards!
Fabian
On 01/26/2011 04:42 PM, pat marion wrote:
Hi Fabian,
Please remember to include the paraview mailing list when you reply.
What you report is a bug, but you can avoid it- when you open your
openfoam dataset you should check
