View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0002911 | VTK | (No Category) | public | 2006-02-24 11:21 | 2016-08-12 09:54 | ||||
Reporter | maik | ||||||||
Assigned To | Will Schroeder | ||||||||
Priority | low | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0002911: vtkPoints precision | ||||||||
Description | I've been noticing point coordinates are sometimes off by 1/8 of a foot or so. I looked in vtkPoints.cxx and noticed that the default data type is still "float". I was under the impression that since 4.2, the vtk point representation was changed to double (since PolyData functions like GetBounds and GetPoint return double values) It was pretty easy to change this in the vtkPoints constructor. I just wanted to bring this up and suggest that either that double should be the default representation or that the class documentation for vtkPoints and vtkPolyData should make it clear that the points only store single precision floats. | ||||||||
Tags | No tags attached. | ||||||||
Project | |||||||||
Type | |||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0036834) 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. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-06-16 13:11 | Zack Galbreath | Category | => (No Category) |
2016-08-12 09:54 | Kitware Robot | Note Added: 0036834 | |
2016-08-12 09:54 | Kitware Robot | Status | expired => closed |
2016-08-12 09:54 | Kitware Robot | Resolution | open => moved |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |