View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0003319

VTK

(No Category)

public

2006-06-02 18:36

2016-08-12 09:54

Reporter

Nick Gnedin

Assigned To

Berk Geveci

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

moved

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0003319: Loss of precision in many VTK filters

Description

Many 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.

Tags

No tags attached.

Project

Type

Attached Files

Relationships

Notes
(0006424) Ken Martin (developer) 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 (administrator) 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.

Issue History
Date Modified	Username	Field	Change
2008-02-06 10:19	Jeff Baumes	Assigned To	=> Berk Geveci
2008-02-06 10:19	Jeff Baumes	Severity	major => minor
2011-06-16 13:11	Zack Galbreath	Category	=> (No Category)
2016-08-12 09:54	Kitware Robot	Note Added: 0036874
2016-08-12 09:54	Kitware Robot	Status	expired => closed
2016-08-12 09:54	Kitware Robot	Resolution	open => moved