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 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
  • #18262
Closed
Open
Issue created Jun 24, 2018 by Jean Favre@jfavreContributor

Vorticity shows artifacts at process boundaries

As discussed earlier

https://discourse.paraview.org/t/vorticity-artifacts-at-process-boundaries/219

Vorticity has artifacts at process boundaries. @acbauer suggested that the Xdmf reader was not providing proper ghost information. I'd rather think that it is the Vorticity filter itself messing up, as demonstrated with the enclosed Python script which uses a Wavelet (independent of Xdmf) and still showing inter-process artifacts which moves around the slice as I change the number of pvserver tasks.

VorticityIssue.py

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