|
From: Roy S. <roy...@ic...> - 2006-06-22 22:08:05
|
On Thu, 22 Jun 2006, Derek Gaston wrote: > It does appear that it is finding the wrong element... here is an > element and a point for which the newton iterations fail (as they very > well probably should since the point is outside the element...) > > ################ > Node 0:0.131279 0 > Node 1:0.17075 0 > Node 2:0.167717 0.032511 > Node 3:0.131771 0.0454457 > Point: 0.184449 0.121701 > ##################### > > They are x y pairs. The nodes are the nodes of the "element" pointer > at around line 192 of mesh_function.C the point is the x y pairs of > "p" in the same place. > > It would appear that "p" is _not_ in "element".... Okay, then our next step is figuring out why the code thinks otherwise. The MeshFunction shouldn't be trying to use an element for which element->contains_point(p) hasn't returned true. If you run Elem::contains_point on that element with that p, does it return true or false? --- Roy |