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,778
    • Issues 1,778
    • 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
  • #4223

Closed
Open
Opened Dec 17, 2006 by Kitware Robot@kwrobotOwner

multiple execution of Image Reader when running PV in parallel

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


I am having trouble developping a custom reader (public inheritance of vtkImageAlgorithm). When running PV on a single node, my reader executes once only - as expected - and creates a vtkImageData. I can then use any number of Filters downstream

When running PV on multiple nodes, my reader executes every time I start a new filter. Can't figure out what triggers it.

Forget about my own source code. I went back to the basics and put a DebugOn() statement in vtkImageReader. It exhibits exactly the same behavior:

on a single node, execute once and only once as expected. on multiple nodes, executes multiple times. Here is an example running on 2 nodes,

First read of a 90^3 raw binary file (the extents are split in the Z direction):

Reading extent: 0, 89, 0, 89, 0, 45 Reading extent: 0, 89, 0, 89, 43, 89

then I extracted a I=29 ortho-slice and the reader executed again

Reading extent: 29, 29, 0, 89, 0, 89 Reading extent: 29, 29, 0, 89, 0, 89

then I extracted an J=45 orthoslice and the reader executed again Reading extent: 0, 89, 45, 45, 0, 89 Reading extent: 0, 89, 45, 45, 0, 89

then I executed an isosurface and the reader executed again

Reading extent: 0, 89, 0, 89, 0, 45 Reading extent: 0, 89, 0, 89, 43, 89

We have only found this multiple execution with ImageData. Other readers (for example for StructuredGrid) do not execute multiple times.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#4223