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,964
    • Issues 1,964
    • 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
  • #20856
Closed
Open
Issue created Jul 27, 2021 by Andrew Bauer@acbauerDeveloper

Catalyst2/CxxImageDataExample has incorrect parallel output

When running the Catalyst2/CxxImageDataExample with mpirun -np 4 bin/CxxImageDataExampleV2 --output datasets/dataset-%04ts.vtpd and the fix at vtk/vtk!8221 (merged) either the extent or the origin for the datasets is wrong. On input to Catalyst/Conduit the extents are:

  • proc 0: [0, 18, 0, 60, 0, 44]
  • proc 1: [17, 36, 0, 60, 0, 44]
  • proc 2: [35, 53, 0, 60, 0, 44]
  • proc 3: [52, 70, 0, 60, 0, 44]

The origin is [0, 0, 0] on each process. Based on the output each process has the minimum extent of [0, 0, 0] and still has the origin at [0, 0, 0] so the datasets for each process are overlapping as seen in the attached file: dataset.tgz

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