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,960
    • Issues 1,960
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 96
    • Merge requests 96
  • 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

Gitlab will be updated February 2nd, between 8am and 9am EST (UTC-5). Gitlab will be offline during that time.

  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #19640
Closed
Open
Issue created Jan 30, 2020 by Daniel Livingston@daniellivingston

Rendering multiple timesteps in SILO with only one defined mesh

ParaView cannot render a timeseries collection via SILO, where the mesh is only defined once and all other files 'reference' that mesh object.

Files to reproduce: time_invariant_mesh.7z

The 'base' file contains the static mesh.

The remaining timestep files have a multi-block mesh object in each of them. However, that object points to the one and only realized mesh in the base file.

Tested and verified in VisIt 3.0.

Might be related to #19298 ?

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