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,758
    • Issues 1,758
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 68
    • Merge Requests 68
  • 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
  • #14579

Closed
Open
Opened Feb 16, 2014 by Kitware Robot@kwrobotOwner

Applying Threshold to a TableToPoints yields wrong results

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


Hello,

steps to reproduce the bug:

  1. Import the attached CSV file
  2. Apply TableToPoints filter, choosing columns X->X, Y->Y, Z->Z
  3. Apply a Threshold filter
  4. The resulting is empty or sometimes wrong

For example: after step 2 we can check in a spreadsheet view that the field "VALUE" is 0 for about one third of the points, 1 for another third, 2 for another third. However, applying the threshold on field VALUE for the range 0-0 yields an empty dataset. Same happnes with ranges 0-1, 1-2, etc. Sometimes, messing around with the thresholds, the resulting dataset is equal to the original one.

Additional informations: sometimes I get a "Could not determine array range" error.

This happens with both 4.1.0 and 4.0.1.

Note: I think I selected the project "Paraview" for this bug report, but there is another "Probject" box where there is no "Paraview" anymore. Sorry, where am I wrong?

Note 2: there are other minor problems with the threshold (e.g. the range is not scaled automatically after choosing the field, but only after selecting a specific value - older versions of Paraview behaved correctly instead), but I guess these are to be filled separately?

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