View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0014895ParaView(No Category)public2014-07-29 17:492016-08-12 09:59
ReporterAlan Scott 
Assigned ToT.J. Corona 
PriorityhighSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Versiongit-master 
Target Version5.1Fixed in Version 
Summary0014895: 2d plots log is wrong
DescriptionOn a 2d plot, when a user has positive X axis data that is to be logged, and includes 0 or negative data, ParaView will arbitrarily change this minimum to 1. Please add more intelligence to this algorithm. What I would like is as follows:

If (X axis data is all positive)
  Leave algorithm as is.
else (i.e., we have 0 or negative X axis data)
  Possible-Min = max/(1e-4)
  If (Possible-Min < 1)
    Minimum = Possible-Min
  Else
    Minimum = 1

A trivial way to reproduce this is as follows:
* Master, local server, Linux.
* can.exo. All vars on. Apply.
* Move forward one time step.
* Plot over line. Left Axis Log Scale on. Apply.

A huge warning will appear, which makes 2d plots useless. Further, if you click on Use Custom Range, the minimum and maximum are not even preset! This creates huge headaches for users.

To show the magnitude of the problem, imagine a user needs to Y axis log scale 4 different 2d plots, with varrying min and max, with a few data points at 0. ParaView becomes very painful to use.
TagsNo tags attached.
ProjectSandia
Topic Name
Typeincorrect functionality
Attached Files

 Relationships
related to 0014835closedUtkarsh Ayachit Color legend log minimum color is wrong 
related to 0014896closedKitware Robot 2d plot log ranges - advanced 

  Notes
(0033137)
Alan Scott (manager)
2014-07-29 17:57

Adding a relationship between log scaling min and max colors, and Y axis for 2d plots. Algorithm is the same.
(0033184)
Utkarsh Ayachit (administrator)
2014-08-05 14:09

In reference to:

"Further, if you click on Use Custom Range, the minimum and maximum are not even preset! This creates huge headaches for users."

That's already fixed: BUG 0014899
(0035721)
Alan Scott (manager)
2016-02-11 22:06

I'm marking this for must be fixed for 5.1. However, probably needs to be tested to see if it still is a problem.
(0038610)
Kitware Robot (administrator)
2016-08-12 09:59

Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.

 Issue History
Date Modified Username Field Change
2014-07-29 17:49 Alan Scott New Issue
2014-07-29 17:49 Alan Scott Target Version => 4.2
2014-07-29 17:54 Alan Scott Relationship added related to 0014896
2014-07-29 17:56 Alan Scott Relationship added related to 0014837
2014-07-29 17:56 Alan Scott Relationship deleted related to 0014837
2014-07-29 17:57 Alan Scott Relationship added related to 0014835
2014-07-29 17:57 Alan Scott Note Added: 0033137
2014-07-31 13:08 Utkarsh Ayachit Status backlog => todo
2014-08-05 14:09 Utkarsh Ayachit Note Added: 0033184
2014-08-06 15:55 Utkarsh Ayachit Assigned To => Utkarsh Ayachit
2014-11-14 22:52 Utkarsh Ayachit Target Version 4.2 => 4.4
2015-07-08 16:30 Utkarsh Ayachit Status todo => backlog
2015-09-11 16:43 Utkarsh Ayachit Target Version 4.4 => 5.1
2016-02-11 22:06 Alan Scott Note Added: 0035721
2016-06-21 16:09 T.J. Corona Assigned To Utkarsh Ayachit => T.J. Corona
2016-08-12 09:59 Kitware Robot Note Added: 0038610
2016-08-12 09:59 Kitware Robot Status backlog => closed
2016-08-12 09:59 Kitware Robot Resolution open => moved


Copyright © 2000 - 2018 MantisBT Team