View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0014214ParaView(No Category)public2013-08-06 18:152015-01-11 08:21
ReporterAlan Scott 
Assigned ToUtkarsh Ayachit 
PriorityhighSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version4.0 
Target Version4.1Fixed in Version4.1 
Summary0014214: trace recorder ordering camera and WriteImage incorrectly
DescriptionThere is a bug in the trace recorder. I "believe" that it is that the WriteImage command and the RenderView.Camera* commands are in the wrong order. To replicate:

* Linux, local server, 4.0.1.
* Tools/ Start Trace.
* Open can.ex2, all variables on, apply.
* File/ Save Screenshot. OK. Choose name, save.
* Tools/ Stop Trace.

<<Here you can see the issue. It is that the WriteImage is before the RenderView.Camera* commands. >>

* Save the trace.
* Exit ParaView.
(Note, delete the screenshot created earlier.)

* pvbatch tracefile.
* Open the screenshot. It is incorrect.
TagsNo tags attached.
ProjectSandia
Topic Name0014214_fix_python_trace_issues
Typeincorrect functionality
Attached Files? file icon trace-3-bad.py [^] (2,395 bytes) 2013-08-06 18:15
? file icon trace-3-good.py [^] (2,397 bytes) 2013-08-06 18:16

 Relationships

  Notes
(0031394)
Alan Scott (manager)
2013-08-06 18:17

Attached python files showing procedure above, plus a fixed version.
(0031844)
Utkarsh Ayachit (administrator)
2013-11-07 10:20

Alas, this is entire broken now :(. We need to fix this before 4.1.
(0031845)
Utkarsh Ayachit (administrator)
2013-11-07 15:18

commit fda6f14b96f972f997de5620e80c60c60ad42e17
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Thu Nov 7 15:16:37 2013 -0500

    BUG 0014214: Fixes issues when tracing write-image.
    
    Addresses a few issues with Python tracing of write-image and other UI actions.
    The order of the traced events ended up being incorrect due to incorrect
    flushing on the queue. Fixed that.
    
    Change-Id: I8e90c8b7621530c04cecb43cc501c81db53248e4
(0031846)
Utkarsh Ayachit (administrator)
2013-11-08 09:26

---------------------------------------------
Topics merged into master:
        14214_fix_tracing_issues
        update-projected-tetra-ctests
(0032033)
Utkarsh Ayachit (administrator)
2013-12-19 17:05

commit ba74b11c4a4fce2e1131df718cad4fcfce30201f
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Tue Dec 17 17:02:38 2013 -0500

    BUG 0014214: Miscellaneous fixes for tracing.
    
    Cleaned up logic in tracing. We were ending up with out of order trace captures
    resulting in broken trace files that didn't work as expected using all ParaView
    executables. This was happening because a lot of new code added to smtrace
    directly appended to the trace_output stream without flushing the information
    currently gathered. Fixed that by streamlining the logic.
    
    Also fixed a leak with trace observer. The observer was in place even after
    tracing was stopped. Fixed that.
    
    Change-Id: I805ffd7570c0b79ace9b540504a55c8f5e842b23
(0032046)
Utkarsh Ayachit (administrator)
2013-12-22 11:12

Topics merged into master:
        0014214_fix_python_trace_issues
        14483_fix_find_data
        fix-warnings
        pvweb-doc-grammar-fix
        pvweb-ipython-integration
(VTK) vtk-master
(0032053)
Alan Scott (manager)
2013-12-24 16:24

This now seems to die, with the directions in the bug report. e-mailed Utkarsh for feedback. Showstopper for 4.1.0
(0032113)
Alan Scott (manager)
2014-01-02 14:06

tested master, linux, local server.

 Issue History
Date Modified Username Field Change
2013-08-06 18:15 Alan Scott New Issue
2013-08-06 18:15 Alan Scott Assigned To => Utkarsh Ayachit
2013-08-06 18:15 Alan Scott File Added: trace-3-bad.py
2013-08-06 18:16 Alan Scott File Added: trace-3-good.py
2013-08-06 18:17 Alan Scott Note Added: 0031394
2013-08-07 11:24 Utkarsh Ayachit Target Version => 4.1
2013-11-07 10:20 Utkarsh Ayachit Note Added: 0031844
2013-11-07 10:20 Utkarsh Ayachit Status backlog => active development
2013-11-07 15:18 Utkarsh Ayachit Topic Name => 14214_fix_tracing_issues
2013-11-07 15:18 Utkarsh Ayachit Note Added: 0031845
2013-11-07 15:18 Utkarsh Ayachit Status active development => gatekeeper review
2013-11-07 15:18 Utkarsh Ayachit Fixed in Version => git-next
2013-11-07 15:18 Utkarsh Ayachit Resolution open => fixed
2013-11-08 09:25 Utkarsh Ayachit Fixed in Version git-next => 4.1
2013-11-08 09:26 Utkarsh Ayachit Status gatekeeper review => customer review
2013-11-08 09:26 Utkarsh Ayachit Note Added: 0031846
2013-12-17 11:04 Utkarsh Ayachit Status customer review => backlog
2013-12-17 11:04 Utkarsh Ayachit Resolution fixed => reopened
2013-12-19 17:05 Utkarsh Ayachit Topic Name 14214_fix_tracing_issues => 0014214_fix_python_trace_issues
2013-12-19 17:05 Utkarsh Ayachit Note Added: 0032033
2013-12-20 08:35 Utkarsh Ayachit Status backlog => gatekeeper review
2013-12-20 08:35 Utkarsh Ayachit Fixed in Version 4.1 => git-next
2013-12-20 08:35 Utkarsh Ayachit Resolution reopened => fixed
2013-12-22 11:12 Utkarsh Ayachit Fixed in Version git-next => git-master
2013-12-22 11:12 Utkarsh Ayachit Status gatekeeper review => customer review
2013-12-22 11:12 Utkarsh Ayachit Note Added: 0032046
2013-12-24 16:24 Alan Scott Note Added: 0032053
2014-01-02 14:06 Alan Scott Note Added: 0032113
2014-01-02 14:06 Alan Scott Status customer review => closed
2014-01-11 08:39 Utkarsh Ayachit Fixed in Version git-master => 4.1
2015-01-11 08:21 Utkarsh Ayachit Source_changeset_attached => ParaView master 8c4432ac
2015-01-11 08:21 Utkarsh Ayachit Source_changeset_attached => ParaView master e48bf68c
2015-01-11 08:21 Utkarsh Ayachit Source_changeset_attached => ParaView master 8879c7e3
2015-01-11 08:21 Utkarsh Ayachit Source_changeset_attached => ParaView master fda6f14b


Copyright © 2000 - 2018 MantisBT Team