MantisBT - VTK
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003319VTK(No Category)public2006-06-02 18:362016-08-12 09:54
ReporterNick Gnedin 
Assigned ToBerk Geveci 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Project
Type
Summary0003319: Loss of precision in many VTK filters
DescriptionMany of VTK filters that work with vtkPolyData create vtkPoints for the output as:

newPts = vtkPoints::New();

This produces float vtkPoints. If the input vtkPoints are of type double, the filter converts double point coordinates to float, with the devastating loss of precision for high dynamic range data. I think you need to go over all chidren of vtkPolyDataAlgorithm and replace the line above with

newPts = vtkPoints::New(inPts->GetDataType());

Without this fix, many of VTK filters are unusable for visualizing Adaptive Mesh Refinement data, which may easily have dynamic range of more than the precision of float, 10^7.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-02-06 10:19Jeff BaumesAssigned To => Berk Geveci
2008-02-06 10:19Jeff BaumesSeveritymajor => minor
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2016-08-12 09:54Kitware RobotNote Added: 0036874
2016-08-12 09:54Kitware RobotStatusexpired => closed
2016-08-12 09:54Kitware RobotResolutionopen => moved

Notes
(0006424)
Ken Martin   
2007-02-15 12:04   
This has been the case in VTK since the beginning. These filters should be modified to support double.
(0036874)
Kitware Robot   
2016-08-12 09:54   
Resolving issue as `moved`.

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