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,659
    • Issues 1,659
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 59
    • Merge Requests 59
  • 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
  • #5769

Closed
Open
Created Sep 23, 2007 by Kitware Robot@kwrobotOwner

TIME and Time (and TimeData) strings should not be case sensitive

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


If a data file contains the string "TIME" or "time" (as well as TimeData, TIMEDATA, or other time-approved names), ParaView3 should be smart enough to treat them the same. I.e. it shouldn't be case sensitive... though perhaps pathological spellings could be treated differently, e.g. TiMEDaTa (then we assume the data producer really wanted to treat it differently).

for example if I read in a CSV file that has "Time" column, ParaView3 knows to put Time on the X-axis, but if it has "TIME" column, it tries to plot it.

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