MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015060ParaView(No Category)public2014-10-21 22:112015-01-11 08:15
ReporterAlan Scott 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version4.2 
Target Version4.3Fixed in Version4.3 
ProjectSandia
Topic Name0015060_fix_temporalshift_issue
Typeincorrect functionality
Summary0015060: (Venus) TemporalShiftScale doesn't update 2d correctly
DescriptionNot sure where the fault is here, I can only give you the end bug.

* Linux, 4.2.0, local server.

The goal here is to be able to change time units in a 2d plot to something reasonable. User has time that is in 1e-13 seconds, wants to change to 1e-4 nanoseconds.

* Open can.exo. All variables on. Apply.
* Last time step.
* Temporal Shift Scale filter. Apply.
* Plot over line filter. Change Chart Title to "Time = ${TIME} Milliseconds"
* Now, click on Temporal Shift Scale filter. Change scale to 1000. Apply.

<<Bug>> - the time in the title of the 2d plot didn't change! You can make it change by moving forward/ back in time.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-10-21 22:11Alan ScottNew Issue
2014-10-21 22:11Alan ScottTarget Version => 4.3
2014-11-04 09:52Utkarsh AyachitTarget Version4.3 => bug_fix
2014-11-04 13:43Utkarsh AyachitTopic Name => 0015060_fix_temporalshift_issue
2014-11-04 13:43Utkarsh AyachitNote Added: 0033710
2014-11-04 13:43Utkarsh AyachitStatusbacklog => gatekeeper review
2014-11-04 13:43Utkarsh AyachitFixed in Version => git-next
2014-11-04 13:43Utkarsh AyachitResolutionopen => fixed
2014-11-04 13:43Utkarsh AyachitAssigned To => Utkarsh Ayachit
2014-11-05 08:10Utkarsh AyachitFixed in Versiongit-next => git-master
2014-11-05 08:11Utkarsh AyachitStatusgatekeeper review => customer review
2014-11-05 08:11Utkarsh AyachitNote Added: 0033720
2014-11-06 17:34Alan ScottNote Added: 0033761
2014-11-06 17:34Alan ScottStatuscustomer review => closed
2014-11-14 22:56Utkarsh AyachitTarget Versionbug_fix => 4.3
2015-01-02 10:45Utkarsh AyachitFixed in Versiongit-master => 4.3
2015-01-11 08:15Utkarsh AyachitSource_changeset_attached => ParaView master a4fb3298
2015-01-11 08:15Utkarsh AyachitSource_changeset_attached => ParaView master 4a3f3687

Notes
(0033710)
Utkarsh Ayachit   
2014-11-04 13:43   
commit 4a3f368706874d3efc25c7188e4c8543c58c6345
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Tue Nov 4 13:40:58 2014 -0500

    BUG 0015060. Fixed issue when using TemporalShiftScale.
    
    The problem was that when the current timesteps changed, we didn't snap
    the current time to the new timesteps. That meant that we continued to
    show the same old timestep even though the pipeline timesteps changed.
    We fix this behavior by ensuring that we snap to a valid timestep when
    the timesteps change and the animation is in "snap to timesteps" mode.
    
    Change-Id: Ib6d1c1ca22eedf84cc8e9aa36592ad403d10a172
(0033720)
Utkarsh Ayachit   
2014-11-05 08:11   
SUMMARY
---------------------------------------------
Topics merged into master:
        0015060_fix_temporalshift_issue
        15059_fix_time_comments
        15100_fix_color_map_editor_size
        python_syntax_highlighting_bugs
        test_max
(VTK) vtk_master_20141104
(0033761)
Alan Scott   
2014-11-06 17:34   
Not sure if I like this solution, but I can't think of a better one. It also fixes this specific bug. I will write up another if my customer doesn't like this.

Tested Linux, master, local server.