MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010386ParaViewBugpublic2010-03-08 15:332011-01-13 17:00
ReporterUtkarsh Ayachit 
Assigned ToMarcus D. Hanwell 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.8Fixed in Version3.8 
Project
Topic Name
Type
Summary0010386: Marks: Log scale doesn't work for bottom/top axes
DescriptionLog scale doesn't seem to work for bottom or top axes, it works for left/right axes.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-03-08 15:33Utkarsh AyachitNew Issue
2010-03-08 15:33Utkarsh AyachitStatusbacklog => tabled
2010-03-08 15:33Utkarsh AyachitAssigned To => Marcus D. Hanwell
2010-03-10 17:13Marcus D. HanwellNote Added: 0019821
2010-03-12 11:45Marcus D. HanwellNote Added: 0019858
2010-03-12 11:45Marcus D. HanwellStatustabled => @80@
2010-03-12 11:45Marcus D. HanwellFixed in Version => 3.8
2010-03-12 11:45Marcus D. HanwellResolutionopen => fixed
2010-03-23 21:47Alan ScottNote Added: 0019994
2010-03-23 21:47Alan ScottStatus@80@ => closed
2011-01-13 17:00Source_changeset_attached => VTK master a2bd8391
2011-01-13 17:00Source_changeset_attached => VTK master 020ef709

Notes
(0019821)
Marcus D. Hanwell   
2010-03-10 17:13   
Working on this - the problem is that log10(0) is -infinity... So I will add treatment of NaN, inf and -inf to the chart rendering code. This may also require some extra logic when dealing with the range of the axes - first pass I will look at the existing code to see what solutions were found.
(0019858)
Marcus D. Hanwell   
2010-03-12 11:45   
VTK/Charts/vtkPlotLine.cxx 1.23 includes improved handling for inf/nan values. I will mark this issue as resolved, and keep fixes for making the top/right axes work on the other bug report that is open.
(0019994)
Alan Scott   
2010-03-23 21:47   
We now have logs top and bottom. Note that there is a known issue with log of 0, still being worked on.