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,768
    • Issues 1,768
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 66
    • Merge Requests 66
  • 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
  • #17637

Closed
Open
Opened Aug 02, 2017 by W. Alan Scott@wascottMaintainer

Exodus dataset with strange time data doesn't play

I have a dataset that has strange time data in it. This dataset does play correctly in EnSight. Here is from a user:

"Attached is an example Exodus output file. We have a Continuation Parameter being varied from 0 to 1 in steps of 0.1. At each continuation step, the ELECTRIC_POTENTIAL, ELECTRON_DENSITY, and HOLE_DENSITY fields are getting written out to Exodus, along with the Continuation Parameter as a global variable. Each time we write out, though, we're doing so at time 0, so it appears as if there are 11 "timesteps" in the output, though time = 0 for all of them. When I open the file up in ParaView, I would expect there to be a way to step through each of the "writes" such that I could see what the fields looked like for each step of the Continuation Parameter. Is that possible?"

I have the dataset. It is named pndiode.dd-result.loca.exo, and is in directory jmg*. Ask me for this dataset.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
5.5 (Spring 2018)
Milestone
5.5 (Spring 2018) (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#17637