Skip to content
GitLab
  • Menu
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,858
    • Issues 1,858
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 97
    • Merge requests 97
  • 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
  • ParaView
  • ParaViewParaView
  • Issues
  • #15441
Closed
Open
Created Apr 28, 2015 by Kitware Robot@kwrobotOwner

Below range color is (slightly) broken

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


The below range color feature is slightly broken. It is very, very probable that it is actually showing up a problem with Rescale to Data Range. Needs to get fixed. Basically, the minimum value on the color legend/ data range is very slightly too high. This use to just default to the lowest value, now it flips to the Below range color - color.

  • Linux, master, local server.
  • open disk_out_ref.exo. All vars on. Apply. Color by Temp.
  • Open the color map editor. Turn on Use Below Range Color. <> - You will see lots of black on the outside of the dataset. Note that this appears different (i.e., solid) and wrong on Windows.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking