Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #19865
Closed
Open
Issue created Apr 23, 2020 by Philip Blakely@pmblakely

Silo format mesh rendering issue

Our custom CFD code is capable of outputting Silo format files, some of which do not render correctly in Paraview version 5.8.0 (or any previous version I've tried, e.g. 5.6.0 or 5.7.0).

I think the issue is with how Paraview detects which (rectilinear) mesh patches are adjacent to each other.

An example plot is: PV_bad_screenshot (Use Surface With Edges on variable Air_rho). Clearly the top of the mesh is missing.

The resolution of the full domain is 71x71x71 cells with spatial extent 10.0x10.0x10.0

I found that if I scale all coordinate values in this file by 1/0.71, then the grid renders correctly: PV_good_screenshot

The Silo files include a Multi-mesh Adj object called Domain_Decomposition, which I thought should help Paraview work out some issues. It may be because the domain decomposition includes patches of width 1 cell.

For what it's worth, VisIt 3.0.2 renders the file correctly: Visit_screenshot.png0000

(I only mention this because I know the Silo reading interface is virtually the same as VisIt's.)

I've attached a zip of the two .silo files, the original (Output_bad.silo) and the 1/0.71 scaled one (Output_good.silo).

Any suggestions on how to solve this would be helpful (including what information we might have failed to output correctly to the .silo files, or any further hints I can give Paraview.)

Thank you very much.

Output.zip

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking