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,768
    • Issues 1,768
    • 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
  • #18072

Closed
Open
Opened Mar 23, 2018 by Mathieu Westphal@mwestphalDeveloper

VTKm Clip Compute Scalars has no effect

VTKm Clip Compute Scalars properties does not seem to have any effect

How to reproduce :

  • Open ParaView
  • Load VTKm Filters plugin
  • Create a wavelet, Apply
  • Add a VTKm Clip filter
  • Set Value to 100
  • Compute Scalars is checked by default
  • Apply
  • As expected, RTData array is available in output
  • Uncheck compute scalars, Apply
  • RTData is still available but it should not be

This may be a bug in the VTKm Filter.

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#18072