# Faster method for GetPoint

**URL:** https://discourse.vtk.org/t/faster-method-for-getpoint/3189
**Category:** Development
**Created:** [May 1, 2020, 6:36pm UTC](https://discourse.vtk.org/t/faster-method-for-getpoint/3189 "2020-05-01T18:36:07Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![lassoan](https://discourse.vtk.org/user_avatar/discourse.vtk.org/lassoan/32/50_2.png) [@lassoan](https://discourse.vtk.org/u/lassoan)
#### Post date: [May 9, 2020, 8:23pm UTC](https://discourse.vtk.org/t/faster-method-for-getpoint/3189/12 "2020-05-09T20:23:55Z")

</div>

> [@will.schroeder](#):
>
> If you can point me to / send me representative examples it will help us prioritize efforts.

Thanks a lot for looking into this! I’ve created a new topic with a link to test data and to discuss this further: [vtkWindowedSincPolyDataFilter performance improvement](https://discourse.vtk.org/t/vtkwindowedsincpolydatafilter-performance-improvement/3262)

> [@will.schroeder](#):
>
> A comment and question about vtkImageReslice: it is a beast, the swiss army knife of imaging filters with tons of options and permutations etc. Are there one or two workflows that are especially important in your application? We can than either focus on those workflows, or create specialty filters addressing those specific workflows.

Yes, this is a very complicated filter indeed. We utilize most of its features - that it can operate on a wide range of data types (integer and floating-point, one or more components), of practically any size, apply a (non-linear) transform, and can work faster when reslicing axes are aligned with image axes.

However, there is one critical use case: quick extraction of an image slice. We use this filter for displaying 2D slices of an image volume, so if performance of this could be made any faster that would visible improvement of slice browsing speed. Total display time includes sending the image data to a texture so that it can be rendered as an image plane. This sending to the GPU probably takes considerable time, too, and I’m not sure how much that part is optimized for this use case (very frequent update of texture, without changing its size or data type).

Reslicing on the GPU could be fast, but supporting of any data types, dynamic application of all kinds of non-linear transforms, supporting large images, etc. would be a lot of work to implement on GPU.

---

_[View the full topic](https://discourse.vtk.org/t/faster-method-for-getpoint/3189)._