Skip to content

GitLab

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

Closed
Open
Opened Mar 01, 2014 by Kitware Robot@kwrobotOwner

Issue of Saving Sources of EnSight Reader

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


  1. Read EnSight *.case files which have names of blocks
  2. Save Data with VTK Multi-Block Dataset as *.vtm
  3. Read *.vtm and all names are lost.

Additionally, the '*.encas' extension is official and some tools like ANSYS FLUENT use it, but ParaView isn't supporting it.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#14611