Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 829
    • Issues 829
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 239
    • Merge requests 239
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #18256
Closed
Open
Issue created Jul 12, 2021 by Lionel Wilhelm@lionel.wilhelm

vtkFLUENTReader - Boundary cells not imported

Dear All,

I was wondering if somehow it is possible to retrieve the boundary faces with their information (like boundary zone id or boundary condition type) when data is read with the vtkFluentReader. It would be very useful for a lot of applications to be able to make the difference between the different type of boundaries (internal boundaries, interfaces, inlets, outlets, walls, walls with specific boundary conditions etc.) to compute standard post-processing values in an automated way (pressure drops, temperature differences, heat flows across boundaries).

Extracting the boundary faces with a surface extract filter after the import doesn't allow such post-processing operations.

After reading the IO/Geometry/vtkFLUENTReader.cxx source file, I noticed that those information are parsed and stored in the Faces data structure (GetFacesAscii and GetFacesBinary functions). It seems that this Faces data structure is never written to any VTK data structure.

IMO, the ideal way of dealing with this issue would be to store the Faces data structure in an additional vtkUnstructuredGrid which would then be added in the vtkMultiBlockDataSet (let's say the last block).

I don't know to which extent this would mess all existing workflows based on this reader but in case it does, users should just deactivate the last block of the vtkMultiBlockDataSet and the trick is done.

What's your opinion about this ?

best,

Lionel

Assignee
Assign to
Time tracking