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,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 97
    • Merge requests 97
  • 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
  • #19880
Closed
Open
Issue created Apr 29, 2020 by David@bg2b

Glyph filter sometimes produces misplaced arrows

This issue is from the discussion in a thread on the ParaView forums.

It's arising under Linux, 64-bit, 5.8.0 build downloaded from paraview.org, and also occurs on a nightly build from 28th April.

Summary: After reading a VTU file with Int32 as the types for the connectivity and offset arrays, the Glyph filter when run on cell data sometimes produces arrows in incorrect places where there are no cells. It is not consistent; changing, e.g., the glyph scaling and re-applying will change the location of the arrows that are produced. If the VTU file uses Int64 for the types of connectivity and offset but is otherwise identical, then the issue does not arise.

Steps to reproduce:

  1. Open the attached cleaned32.vtu and apply
  2. Select current and surface with edges, reduce opacity to 0.2 so the glyphs can be seen
  3. Filters->Glyph, select orientation array current_dir, no scale array, scale factor 5, all points, apply
  4. If need be, switch back and forth between scale factor 4 + apply and scale factor 5 + apply a few times. At some point you’ll see the misplaced arrows.

Example picture of the problem (not always reproduced exactly):

misplaced

The issue does not occur if you use cleaned.vtu (which has Int64 as the offset and connectivity type).

cleaned32.vtu cleaned.vtu

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