On Tue, Nov 30, 2010 at 10:41 AM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com" target="_blank">david.gobbi@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Tue, Nov 30, 2010 at 9:25 AM, David Doria <span dir="ltr"><<a href="mailto:daviddoria@gmail.com" target="_blank">daviddoria@gmail.com</a>></span> wrote:</div><div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<br>
</div>So it considers a point on the boundary to be "outside" no matter the<br>
tolerance? Doesn't that seem silly? Often you may know the coordinates<br>
of the grid points and want to get the cell id they are associated<br>
with. This method should work for all such points, but it seems to<br>
work only on points that aren't on the boundary faces of the<br>
structured grid?<br></blockquote><div><br></div></div><div>Hmm... I looked at the FindCell implementation in vtkImageData, and it ignores</div><div>the tolerance completely. This is not good. As you said, boundary points</div>
<div>should be considered to be inside the cell unless the tolerance is strictly set</div><div>to zero (and even then, it should be an even 50/50 chance that the boundary</div><div>points are considered to be inside).</div>
<div><br></div><div>In fact this is precisely the sort of boundary issue that tolerances are for:</div><div>to ensure that points on the boundary are not mistakenly marked as "outside"</div><div>due to roundoff error.</div>
</div></blockquote><div> </div><div>David, can you put this into the bug tracker? The entry doesn't have to say</div><div>much, it just has to say that vtkImageData::FindCell ignores the tolerance</div><div>and that, because of this, there is no way to ensure that FindCell will return</div>
<div>a cell when given a point that lies on the boundary of the data set.</div><div><br></div><div>There is a good chance that I can do a fix for this in the coming weeks.</div><div><br></div><div> David</div></div><br>