Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
VTK
VTK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 593
    • Issues 593
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 153
    • Merge Requests 153
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #18160

Closed
Open
Created Mar 24, 2021 by Andrew Bauer@acbauerDeveloper

ExodusII reader having problems with 18 node prisms/wedge

There are two issues here. The first is that the 18 node prism/wedge is being read in as a 6 node cell. Can see by looking at one_prism18.e with ncdump that it is indeed an 18 node cell. For two_prism18.e the connectivity seems to be wrong. See the discussion at https://github.com/libMesh/libmesh/issues/2882#issuecomment-805862325.

Note that both files are completely open and can be added as test files if needed.

two_prism18.e

one_prism18.e

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None