On Tue, 30 Jun 2015, Andrew Davis wrote:
> Thanks for the help and sorry for the slow reply; I've been using the
> deprecated code for now.
That's fine; the only problem with the deprecated code is a race
condition when using threads, and libMesh only uses threads when
instructed to on the comm
Hey,
Thanks for the help and sorry for the slow reply; I've been using the
deprecated code for now. I had to prepare for a conference presentation
and didn't want to worry about updating or anything.
I just did a git pull so I should have the most recent version of libmesh
(0.9.4 I think).
I tr
On Wed, 10 Jun 2015, Andrew Donaldson Davis wrote:
> const libMesh::PointLocaterBase& ptLocator(mesh.point_locator());
> libMesh::Elem* element = ptLocator(point);
>
> Is there a better way to do this?
sub_point_locator(). Call it first (ignoring the result if necessary)
from outside threaded c
On Wed, Jun 10, 2015 at 1:59 PM, Andrew Donaldson Davis
wrote:
> Hello,
>
> I'm trying to figure out which element a point is in. Right now I am doing
> something like:
>
> const libMesh::PointLocaterBase& ptLocator(mesh.point_locator());
> libMesh::Elem* element = ptLocator(point);
>
> but I ge
Hello,
I'm trying to figure out which element a point is in. Right now I am doing
something like:
const libMesh::PointLocaterBase& ptLocator(mesh.point_locator());
libMesh::Elem* element = ptLocator(point);
but I get this warning:
*** Warning, This code is deprecated, and likely to be removed
