MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014813ParaView(No Category)public2014-06-19 15:502015-01-11 08:16
ReporterAlan Scott 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versiongit-master 
Target Version4.2Fixed in Version4.2 
ProjectSandia
Topic Name14813_fix_mode_shapes_range
Typeincorrect functionality
Summary0014813: Mode shapes slider is off by 1
Description* Master, Linux, local server.
* Open file block-rv-eigen.g. All vars on. Advanced property tab. Select Has Mode Shapes. Apply.
* The problem is that the mode shape slider is off by 1. It goes from 0-14, where the actual mode shapes are in 1-15.
* Move the Mode Shape slider to the left. Apply. It will be mode shape 0, and there will be a bazillion warnings in the Output Message.
* Move the Mode Shape slider to the right. Notice that it only goes to 14. Manually type 15 in the mode shape, and click Apply. There is actually a mode shape 15 that is "hidden".

Since this is representing data incorrectly, lets fix this in 4.2 if possible. Otherwise, 4.3 for sure.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0009328closed Utkarsh Ayachit Mode shapes should go from 1 to N, not 0 to N-1 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-06-19 15:50Alan ScottNew Issue
2014-06-19 15:50Alan ScottNote Added: 0032906
2014-07-29 21:11Alan ScottNote Added: 0033139
2014-07-29 21:11Alan ScottTarget Version => 4.2
2014-07-30 11:18Utkarsh AyachitRelationship addedrelated to 0009328
2014-07-30 12:00Utkarsh AyachitNote Added: 0033140
2014-07-30 12:36Utkarsh AyachitTopic Name => 14813_fix_mode_shapes_range
2014-07-30 12:36Utkarsh AyachitNote Added: 0033141
2014-07-30 12:36Utkarsh AyachitStatusbacklog => gatekeeper review
2014-07-30 12:36Utkarsh AyachitFixed in Version => git-next
2014-07-30 12:36Utkarsh AyachitResolutionopen => fixed
2014-07-30 12:36Utkarsh AyachitAssigned To => Utkarsh Ayachit
2014-08-02 09:25Utkarsh AyachitNote Added: 0033175
2014-08-02 09:25Utkarsh AyachitStatusgatekeeper review => active development
2014-08-04 10:11Utkarsh AyachitStatusactive development => gatekeeper review
2014-08-04 10:12Utkarsh AyachitFixed in Versiongit-next => git-master
2014-08-04 10:12Utkarsh AyachitStatusgatekeeper review => customer review
2014-08-04 10:12Utkarsh AyachitNote Added: 0033179
2014-08-19 12:07Utkarsh AyachitNote Added: 0033256
2014-08-19 12:07Utkarsh AyachitStatuscustomer review => gatekeeper review
2014-08-20 08:45Utkarsh AyachitStatusgatekeeper review => customer review
2014-08-20 08:45Utkarsh AyachitNote Added: 0033273
2014-08-29 10:59Utkarsh AyachitFixed in Versiongit-master => 4.2
2014-11-05 22:08Alan ScottNote Added: 0033735
2014-11-05 22:08Alan ScottStatuscustomer review => closed
2015-01-09 13:40Utkarsh AyachitSource_changeset_attached => VTK master c2218cb6
2015-01-09 13:40Utkarsh AyachitSource_changeset_attached => VTK master 2327e0ac
2015-01-11 08:16Utkarsh AyachitSource_changeset_attached => ParaView master 1043199b
2015-01-11 08:16Utkarsh AyachitSource_changeset_attached => ParaView master 31ae6163

Notes
(0032906)
Alan Scott   
2014-06-19 15:50   
Sending the dataset to Utkarsh.
(0033139)
Alan Scott   
2014-07-29 21:11   
This is impacting one of my users. Thus, lets try for 4.2. If needed, OK to slide to 4.3.
(0033140)
Utkarsh Ayachit   
2014-07-30 12:00   
commit 2327e0aca8042680b4bdf6b52c2c777a1d1546d2
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Wed Jul 30 11:59:34 2014 -0400

    BUG 0014813: Fix range reported for mode shapes.
    
    Since mode shapes in Exodus are index starting with 1, we add a new API
    to vtkExodusIIReader to report this range explicitly, rather that users
    having to deduce the range from TimeStepRange.
    
    Change-Id: I761ee20590cf1c0cbdfa152b77534dc508a60676
(0033141)
Utkarsh Ayachit   
2014-07-30 12:36   
commit 31ae6163c49e00e133a04f8cb58b8fd25ebf140e
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Wed Jul 30 12:34:58 2014 -0400

    BUG 0014813: Use correct range for mode shapes index.
    
    Using new API on vtkExodusIIReader to get the mode shape range offset
    appropriately.
    
    Change-Id: I8748da0c04f2fbf108a899bee871c2f8624e2724
(0033175)
Utkarsh Ayachit   
2014-08-02 09:25   
awaiting VTK gerrit review: http://review.source.kitware.com/#/t/4467/ [^]
(0033179)
Utkarsh Ayachit   
2014-08-04 10:12   
SUMMARY
---------------------------------------------
Topics merged into master:
(VTK) 14279_glyph_filter
(VTK) fix_invalid_socket_check
(0033256)
Utkarsh Ayachit   
2014-08-19 12:07   
merged in next again. I believe this didn't go through last time due to the VTK topic not being in master. It is now. Should go through this time.
(0033273)
Utkarsh Ayachit   
2014-08-20 08:45   
SUMMARY
---------------------------------------------
Topics merged into master:
        14279_fix_rand_on_windows_attempt_2
        14813_fix_mode_shapes_range
        catalyst-updates


---------------------------------------------
Topics reverted from next:
  catalyst-script-plugin-client
(0033735)
Alan Scott   
2014-11-05 22:08   
Nice. Tested master, local server, Linux.