MantisBT - ParaView
View Issue Details
0008422ParaViewBugpublic2009-01-22 18:272011-01-13 17:00
Alan Scott 
Utkarsh Ayachit 
highfeaturealways
closedfixed 
 
3.6.23.6.2 
0008422: Need implicit exodus node index in selection view
Here is a request from a user. I think he makes more sense than I do, so I am copying what he said. There is a dataset associated with this request, ask me for it. (blade1_full.exo)

We need to be able to ascertain the exodus node number even in the presence of a node map. The attached file has two important node numbers associated with each node:
  1. The exodus node index, which is implicitly numbered (1:N) on the model.
It is used for all connectivity information.
  2. The global node id.

The situation is slightly different in parallel and serial. I will explain with an example. The attached example has a beam sticking out of the end of the blade. The last node on that beam is the 303 node in the exodus file.
It's global ID is 4800705. The "selection inspector" properly reports its global node id (or pedigree id). Both the global node id and pedigree id are the same in version 3.4.0. However, it's point id has no connection to anything in the exodus model. The point id is zero.

The underlying exodus file lists this as the 303 node in the model. The 303rd entry in the node number map is 4800705. Thus, paraview knows the index and is associating the proper node id with the node, but it does not report the index of 303. This index is used in various other places, most importantly in the connectivity table. The connectivity for element block 480000 contains this index as is shown by grope.

GROPE> sele block 480000
GROPE> list connecti

 Block***** (#2): 6 elements (3..8) 2-node 7 attributes
      # elem Connectivity
       1 3 303 304
       2 4 304 66
       3 5 66 67
       4 6 67 65
       5 7 65 64
       6 8 64 39

The same information can be seen (in another format) in the exodus file using either exotxt or ncdump. I can provide those if needed.

In parallel we need the same data, but the meaning is slightly different. In parallel, the node number map of the spread files points to the original exodus data numbering. Thus, in parallel (I believe) paraview will now return the number 303 for the global id. This is as it should be. But, now on the local subdomain, we should still be able to find the local exodus index which would depend of course on the decomposition.

I would suggest these values be labeled as follows.
global id should return the same data it currently does.
local id should return the index, i.e. 303 for the serial case.

No tags attached.
has duplicate 0009341closed  Implicit Node/Element Indices from Exodus Files 
related to 0009649closed Utkarsh Ayachit Get Exodus implicit index arrays to work with the Selection Inspector 
Issue History
2009-01-22 18:27Alan ScottNew Issue
2009-02-17 16:42Utkarsh AyachitStatusbacklog => tabled
2009-02-17 16:42Utkarsh AyachitAssigned To => Utkarsh Ayachit
2009-05-13 13:46Utkarsh AyachitTarget Version => 3.6
2009-08-24 13:18Ken MorelandCategory => Bug
2009-08-24 13:18Ken MorelandSummaryNeed exodus node index in selection view => Need implicit exodus node index in selection view
2009-08-24 13:20Ken MorelandNote Added: 0017185
2009-08-24 16:18Alan ScottTarget Version3.6 => 3.6.2
2009-09-01 15:11Alan ScottNote Added: 0017287
2009-09-28 19:53Nathan FabianNote Added: 0017812
2009-10-01 14:10Utkarsh AyachitNote Added: 0017875
2009-10-01 14:10Utkarsh AyachitStatustabled => @80@
2009-10-01 14:10Utkarsh AyachitFixed in Version => 3.6.2
2009-10-01 14:10Utkarsh AyachitResolutionopen => fixed
2009-10-02 15:11Alan ScottRelationship addedhas duplicate 0009341
2009-10-02 15:17Alan ScottRelationship addedrelated to 0009649
2009-10-02 15:19Alan ScottNote Added: 0017914
2009-10-02 15:19Alan ScottStatus@80@ => closed
2011-01-13 17:00Source_changeset_attached => VTK master a2bd8391
2011-01-13 17:00Source_changeset_attached => VTK master 020ef709

Notes
(0017185)
Ken Moreland   
2009-08-24 13:20   
I think this bug boils down to writing out special arrays for the implicit node and element indices (similar to the global indices or object ids). The data will not be visible in the selection inspector but will be visible in the spreadsheet view.
(0017287)
Alan Scott   
2009-09-01 15:11   
Please talk to me before implementing. Alan
(0017812)
Nathan Fabian   
2009-09-28 19:53   
I've added this and it works as expected for all the exodus files I've looked at (especially the ones above. There may be a number of caveats to how it works with older files. It should work well for serial files. The only really troubling ones are split exodus files which are not detectable from within ExodusIIReader (but are from withing PExodusIIReader). With a work around to detect split files, the caveats for older versions could probably be specialized.
(0017875)
Utkarsh Ayachit   
2009-10-01 14:10   
Committing Nathan's fixes for BUG 0008422 to 3.6 branch
* Added implicit index arrays as requested in 8422. It is off by default
as there are currently a number of caveats to what numbers will show up
there.
* XML changes to load implicit exodus arrays.
* Added the implicit variables to the exodus variable box, off by default.

/cvsroot/ParaView3/ParaView3/Qt/Components/pqExodusIIPanel.cxx,v <-- Qt/Components/pqExodusIIPanel.cxx
new revision: 1.19.6.3; previous revision: 1.19.6.2
/cvsroot/ParaView3/ParaView3/Servers/ServerManager/Resources/readers.xml,v <-- Servers/ServerManager/Resources/readers.xml
new revision: 1.152.2.7; previous revision: 1.152.2.6
/cvsroot/ParaView3/ParaView3/VTK/Hybrid/vtkExodusIIReader.cxx,v <-- VTK/Hybrid/vtkExodusIIReader.cxx
new revision: 1.76.2.3; previous revision: 1.76.2.2
/cvsroot/ParaView3/ParaView3/VTK/Hybrid/vtkExodusIIReader.h,v <-- VTK/Hybrid/vtkExodusIIReader.h
new revision: 1.27.2.2; previous revision: 1.27.2.1
/cvsroot/ParaView3/ParaView3/VTK/Hybrid/vtkExodusIIReaderPrivate.h,v <-- VTK/Hybrid/vtkExodusIIReaderPrivate.h
new revision: 1.6.2.1; previous revision: 1.6
/cvsroot/ParaView3/ParaView3/VTK/Hybrid/vtkExodusModel.cxx,v <-- VTK/Hybrid/vtkExodusModel.cxx
new revision: 1.8.10.1; previous revision: 1.8
/cvsroot/ParaView3/ParaView3/VTK/Hybrid/vtkExodusReader.cxx,v <-- VTK/Hybrid/vtkExodusReader.cxx
new revision: 1.56.10.1; previous revision: 1.56
/cvsroot/ParaView3/ParaView3/VTK/Hybrid/vtkPExodusIIReader.cxx,v <-- VTK/Hybrid/vtkPExodusIIReader.cxx
new revision: 1.27.2.1; previous revision: 1.27
(0017914)
Alan Scott   
2009-10-02 15:19   
Tested with can.exo, client/numerous servers, Linux.