# Resample to Dataset terminology

**URL:** https://discourse.paraview.org/t/resample-to-dataset-terminology/1000
**Category:** ParaView Support
**Created:** [December 4, 2018, 8:18pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000 "2018-12-04T20:18:13Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![DennisConklin](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/d/b19c9b/32.png) [@DennisConklin](https://discourse.paraview.org/u/DennisConklin)
#### Post date: [December 4, 2018, 8:18pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/1 "2018-12-04T20:18:13Z")

</div>

Am I the only person who can never remember the difference between Input and Source when using this filter? I always have to look it up. Could we possibly relabel these as “Input Variables” and “Source Geometry” or would that make it too easy?

Irritatingly yours,

Dennis 😉

---

<div class="post-metadata">

### Author: ![Kenneth\_Moreland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kenneth_moreland/32/15033_2.png) [@Kenneth\_Moreland](https://discourse.paraview.org/u/Kenneth_Moreland)
#### Post date: [December 4, 2018, 8:46pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/2 "2018-12-04T20:46:20Z")

</div>

You are not the first to bring this up ([https://gitlab.kitware.com/paraview/paraview/issues/12257](https://gitlab.kitware.com/paraview/paraview/issues/12257)), but thanks for bringing it up to help raise the priority.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [December 4, 2018, 9:26pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/3 "2018-12-04T21:26:00Z")

</div>

Changed target to this spring release, marked as required. Oh, Dennis, you are sooo very correct.

---

<div class="post-metadata">

### Author: ![DennisConklin](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/d/b19c9b/32.png) [@DennisConklin](https://discourse.paraview.org/u/DennisConklin)
#### Post date: [December 5, 2018, 1:04pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/4 "2018-12-05T13:04:58Z")

</div>

In Kitware’s defense, I have just discovered the tips if you hover over the fields which clue us in!

---

<div class="post-metadata">

### Author: ![DennisConklin](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/d/b19c9b/32.png) [@DennisConklin](https://discourse.paraview.org/u/DennisConklin)
#### Post date: [December 5, 2018, 2:40pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/5 "2018-12-05T14:40:48Z")

</div>

How about a legitimate question about Resample to Dataset.

I am trying to take a cylindrical membrane surface and Resample it’s variables onto a copy of it that has been rotated.  
So, Input is the original cylinder, which is discretized every 2 degrees, and Source is a copy of the original cylinder that has been rotated by 0.5 degrees.

The "Compute Tolerance has to be increased to 0.02 in order to get a reasonable distribution on the rotated geometry. What is this tolerance, is it a physical distance, and how do I determine a reasonable value a priori? What bad things would happen if I used a non-optimized value (i.e., too large of a tolerance)?

The Computed Tolerance must be very small because I get a very bad distribution on the rotated geometry (almost single value)

Thanks for any help.  
Dennis

---

<div class="post-metadata">

### Author: ![Kenneth\_Moreland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kenneth_moreland/32/15033_2.png) [@Kenneth\_Moreland](https://discourse.paraview.org/u/Kenneth_Moreland)
#### Post date: [December 5, 2018, 5:15pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/6 "2018-12-05T17:15:08Z")

</div>

Trying to sample values from a surface is always problematic as an x, y, z coordinate will seldom be _exactly_ on a surface. In fact, in your case, none of your coordinates will be exactly on the surface. When you rotate your cylinder 0.5 degrees, the resulting points will deviate off the chords joining the 2 degree samples in the original mesh.

Choosing a tolerance is always problematic. Too small of a tolerance (particularly on surfaces) and points won’t be identified in the cells you want them to be. But too large of a tolerance and you might be sampling values in a mesh where you shouldn’t be. I wasn’t privy to the decisions in deciding what the computed tolerance should be, but I believe it picks small numbers to error towards only sampling points truly in cells.

You will have to play with the tolerance until it gives you the results you like. I also found that changing the `Cell Locator` to `Tree Cell Locator` seemed to improved performance.

---

<div class="post-metadata">

### Author: ![DennisConklin](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/d/b19c9b/32.png) [@DennisConklin](https://discourse.paraview.org/u/DennisConklin)
#### Post date: [December 5, 2018, 6:45pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/7 "2018-12-05T18:45:56Z")

</div>

Ken,

In my case, where I have a 1-to-1 correspondence of nodes/elements with slight displacement between the two structures, it doesn’t seem to change anything if I change Tolerance from 0.02 to 1000.0. I assume this is because it uses the closest point no matter what.

Since I am trying to write a general purpose routine which will be used on meshes of undetermined size and refinement, I think my only possible problem is having Tolerance too small, so by using 1000.0 I avoid this problem. I am always remapping onto an identical but slightly perturbed mesh, so that is my plan unless you can see a potential pitfall.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [January 3, 2019, 11:05pm UTC](https://discourse.paraview.org/t/resample-to-dataset-terminology/1000/8 "2019-01-03T23:05:27Z")

</div>

The name change has been completed in [https://gitlab.kitware.com/paraview/paraview/merge\_requests/2931](https://gitlab.kitware.com/paraview/paraview/merge_requests/2931)

_Input_ is now _Source Data Arrays_ and _Source_ has been changed to _Destination Mesh_.
