[Paraview] Error using Python Trace in PV3.10-RC1

Adriano Gagliardi agagliardi at ara.co.uk
Wed Feb 23 10:07:36 EST 2011


I found a problem using the Python Trace functionality with PV3.10-RC1. I've
loaded in a dataset and started a trace. I then proceeded to take a slice
through the dataset, which worked fine. Next, in the animation view, I added
a cue based on the x-value of the slice origin. Double-clicking on the
scalar bar gives the pop up window to set the start and end values. At this
point, I can't change any of the values and ParaView just hangs. This only
appears to happen with the variables that are essentially vector components
(Normals and Origin); I can modify the scalar options without it crashing.

I did manage to get around the problem by adding one of the vector
components as a track BEFORE starting the trace and then deleting it
immediately. I can then start the trace, add the track again (or any of the
options), modify its values without ParaView crashing.

Regards,

Adriano

===================================

Adriano Gagliardi MEng PhD
Business Sector Leader
Computational Aerodynamics
Aircraft Research Association Ltd.
Manton Lane
Bedford

Tel: 01234 32 4644
E-mail: agagliardi at ara.co.uk
Url: www.ara.co.uk 


**********************************************************************
This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************


More information about the ParaView mailing list