[vtkusers] Double precision in VTK

[Berk Geveci]

We are slowly moving towards preserving the native type of the input.
There are some filters that are internally templated for this purpose.
If you see ones that you think should be double precision, please
report them. Note that not all filters need to produce double
precision data. If an algorithm is inherently limited in precision, it
is best to use floating point for performance reasons.

-berk

On Thu, Apr 15, 2010 at 10:55 AM, egk865 at yahoo.com <egk865 at yahoo.com> wrote:
> Are there any plans to support double precision in VTK anytime soon?
> It seems that much of VTK is optimized primarily for
> single floating point precision with many filters hardcoded to output
> data in single precision even when the input to them is in double
> precision.
>
> One possible reason I can see why vtk may have been written
> primarily with single precision in mind is that most modern
> graphics cards are optimized for single precision and internally
> store the data in single precision. However, not all applications
> need to write to the graphics card and the ability for VTK to work
> well with double precision data would be very useful especially for
> science and research applications where accuracy is important.
>
> Thanks,
> Eli
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>