View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0015331 | ParaView | (No Category) | public | 2015-02-19 07:03 | 2015-09-06 12:17 | ||||
Reporter | Vadim SANDLER | ||||||||
Assigned To | Tristan Coulange | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 4.3 | ||||||||
Target Version | Fixed in Version | 4.4 | |||||||
Summary | 0015331: Regression of the animation from python | ||||||||
Description | Script demo.py works well in the ParaView-4.1 but doesn't work as expected in the ParaView-4.2 and ParaView-4.3.1 1) Modify the script demo.py from the archive demo.tag.gz (https://drive.google.com/file/d/0B_XAVXb9X2V8MXRmbEJHSldwbGc/view?usp=sharing [^]) in order to set correct path to the demo_*.vtm files. 2) Execute script in the ParaView python shell In the the result the following errors are detected: 1) Presentation is not coloured by 'RESULT__DEPL____________________', 'Magnitude' array. It is coloured by this array after change component to 'DX' and to 'Magnitude' again on the 'Active Variable Controls' tool-bar. 2) Show animation view. The line for animation by WarpByVector1 'ScaleFactor' property with the Key Frames specified in the python script is not added to the animation view table. It works well in the ParaView-4.1. | ||||||||
Tags | No tags attached. | ||||||||
Project | ParaViS | ||||||||
Topic Name | 0015331_fix_animation_track_python | ||||||||
Type | incorrect functionality | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0034329) Tristan Coulange (developer) 2015-03-27 04:13 |
Hello, Regarding the first error, you have to add the following command at line 65: WarpByVectorDataRepresentation.RescaleTransferFunctionToDataRange(True) It corresponds to the button "Rescale To Data Range" in the GUI. In the previous versions of ParaView it was done automatically, but now you will have to do it explicitly. You can see it in the documentation "TheParaViewGuide-v4.3-CC-Edition.pdf", or by doing the same steps in the GUI with Python trace enabled: the generated trace has the command too. Regarding the second error, it was fixed and merged into master: https://gitlab.kitware.com/paraview/paraview/merge_requests/19#note_8369 [^] Tristan |
(0034732) Alan Scott (manager) 2015-07-09 21:29 |
Closing bug report. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2015-02-19 07:03 | Vadim SANDLER | New Issue | |
2015-02-19 07:03 | Vadim SANDLER | Assigned To | => Tristan Coulange |
2015-03-26 02:47 | Tristan Coulange | Topic Name | => 0015331_fix_animation_track_python |
2015-03-26 02:47 | Tristan Coulange | Reproducibility | have not tried => always |
2015-03-26 02:47 | Tristan Coulange | Status | backlog => active development |
2015-03-27 04:13 | Tristan Coulange | Note Added: 0034329 | |
2015-03-27 04:44 | Tristan Coulange | Status | active development => gatekeeper review |
2015-06-02 08:46 | Utkarsh Ayachit | Status | gatekeeper review => customer review |
2015-06-02 08:46 | Utkarsh Ayachit | Resolution | open => fixed |
2015-06-02 08:46 | Utkarsh Ayachit | Fixed in Version | => git-master |
2015-07-09 21:29 | Alan Scott | Note Added: 0034732 | |
2015-07-09 21:29 | Alan Scott | Status | customer review => closed |
2015-09-06 12:17 | Utkarsh Ayachit | Fixed in Version | git-master => 4.4 |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |