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
  • #14605

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

Reading a table with strings in it, then table to points, can't do calculations

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


This is also present in 3.98.0. Both 64-bit versions.

If you use the CSV reader to load the attached file (paste a "tab" character into the field), you get a table with a string row and then some integer rows. If you use Table to Points with the first numerical column as X and Y and use 2D points, you get a line of points with values associated. If you then use the Calculator to pass through the final field (count of proteins), you get all sorts of strange values.

After trying a bunch of things involving making sure that the integer values were read as doubles, adding a header to the file, and converting to 3D points and then pulling out coordZ using the calculator (none of which worked), I finally tried just pulling the character-string field out of the file read by the table.

When I did this, the calculator filter worked fine on even the integer data.

So it looks like the presence of a character field in the CSV-read table causes Paraview to not be able to deal correctly with some of the other table entries.

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