| View Issue Details [ Jump to Notes ] | [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006240 | ParaView | (No Category) | public | 2008-01-14 16:29 | 2016-08-12 09:57 |
|
| Reporter | Eric Monson | |
| Assigned To | Berk Geveci | |
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | moved | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0006240: Global IDs not read as vtkIdType from vtkXMLUnstructuredGridReader |
| Description | When reading a VTK XML Unstructured Grid file with Global IDs set, ParaView recognizes that there are Global Ids set (the Use Global Ids check box becomes available in both the Plot Point Over Time and the Selection Inspector), but they not valid -- e.g. they are listed as "int" rather than "idtype" in the Information tab.
When points are selected, the Selection Inspector shows the Index for the points, but if you check Use Global Ids the list goes blank. In the Selection Inspector if you then try to uncheck Use Global Ids, ParaView crashes. |
| Steps To Reproduce | ExodusII files seem to work fine. If you save either box.ex2 or can.ex2 as a vtu file, then reload it, PV will reproduce this behavior. |
| Additional Information | With my data I was able to use the Python Programmable Filter within ParaView to read those "int" GlobalIds into a vtkIdTypeArray and (after a shallow copy of the input) set the filter output GlobalIds to this new array. After this, all the Global ID stuff seems to work fine, so I think it really is an issue with the reader. It's not clear why unchecking the Use Global Ids box in the Selection Inspector crashes PV when the incorrect "int" IDs are present. |
| Tags | No tags attached. |
|
| Project | |
| Topic Name | |
| Type | |
|
| Attached Files | |
|