On Mon, 21 Jun 2010, Karen Lee wrote: > I'm using Elem::contains_point(). I'm also wondering, at what point > does libmesh start building the tree? Does it do so as it reads in > the mesh?
It does so the first time point_locator() is called. (either by you, or by the library itself if you're using periodic boundary conditions) > My program works with some test cases but not with the mesh I'm > interested in solving... I realized that some of the nodes have the > same coordinates. (It's a mesh that my collaborators obtained from > MRI...) I'm wondering if this might cause a problem. Almost certainly. IIRC, our code for reconstructing element neighbor topology (which needs to be done even to read in the mesh) currently assumes that you don't have overlapping nodes. --- Roy ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
