| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0002971 | ParaView | (No Category) | public | 2006-03-16 19:20 | 2009-12-09 15:06 | ||||
| Reporter | yvan.fournier | ||||||||
| Assigned To | Berk Geveci | ||||||||
| Priority | normal | Severity | major | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0002971: Paraview/VTK are unable to read nfaced type elements in EnSight Gold files | ||||||||
| Description | EnSight Gold Files containing "nfaced" (convex polyhedron) type elements (available since EnSight 7.4) are not handled by the current VTK EnSight Gold readers, crashing the readers. A patch (and test data) is proposed at the given URL, reaading nfaced elements as vtkConvexPointSets. (the modified versions are based on the ParaView CVS head as of March 3 2006, that is: vtkEnSightGoldBinaryReader.cxx/1.64/ vtkEnSightGoldReader.cxx/1.56/ vtkEnSightGoldReader.h/1.20/ vtkEnSightReader.cxx/1.61/ vtkEnSightReader.h/1.27/) | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files |  vtk_EnSight.tar.gz [^] (29,148 bytes) 1969-12-31 19:00 vtk_EnSight_minimal_changes.tar.gz [^] (29,288 bytes) 1969-12-31 19:00 Example.tar.gz [^] (17,502 bytes) 1969-12-31 19:00 | ||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0003940) yvan.fournier (reporter) 2006-03-31 17:52 |
Here are the modified files (based on the CVS head as of March 3 2006), hoping that they may good enough for inclusion in ParaView/VTK. As EnSight's nfaced elements are defined by n polygonal faces, vertices appear in an element's node list once per face to which they belong. This does not seem to be the case with VTK_CONVEX_POINT_SET, so I used a nodeMarker array, initialized to -1 for each node. Looping on elements, when a node is first used for a given element, its marker value is set to the current element index, so if we encounter it again for this element, seeing that its marker value is not lower than the current element index, we know that it has already been counted. This seems to work fine. For the Ensight Gold text reader, I had to add a "ElementIdsListed" member to the "vtkEnSightGoldReader" class (similar to the one used in "vtkEnSightGoldBinaryReader"), because the method used for polygons ("nsided") to skip optional element ids was not extensible to polyhedra. In the vtk_EnSight_minimal_changes.tar.gz version of the modified files, this member is only used for polyhedra. In the vtk_EnSight.tar.gz version, it is also used for polygons, for consistency (and simplification). Further cleanup would be possible, but I would rather check first that the modifications are OK for inclusion in ParaView. Everything seems to work fine, except for "cell centers" outside the VTK_CONVEX_POINT_SET (which I suspect is an unrelated bug). "shrink" shows cells having the correct shape. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2009-12-09 14:51 | Berk Geveci | Project | @3@ => ParaView |
| 2009-12-09 15:06 | Berk Geveci | Status | tabled => closed |
| 2009-12-09 15:06 | Berk Geveci | Resolution | open => fixed |
| 2011-06-16 13:09 | Zack Galbreath | Category | => (No Category) |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |