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,666
    • Issues 1,666
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 62
    • Merge Requests 62
  • 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
  • #20222

Closed
Open
Created Sep 22, 2020 by Armin Wehrfritz@awehrfritz

AMReX reader ignores time information

Many AMReX-based simulation codes write checkpoints/datasets at non-uniform time intervals. The datasets contain however the time information in the Header file. It would be nice if ParaView was to read and use that information.

Tested with ParaView 5.8.1.

Edited Sep 22, 2020 by Armin Wehrfritz
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
5.10 (Fall 2021)
Milestone
5.10 (Fall 2021)
Assign milestone
Time tracking
None
Due date
None