Sorry for the confusion, I am wanting all the active descendants. Andrea
On Mon, Aug 16, 2010 at 10:44 AM, John Peterson <peter...@cfdlab.ae.utexas.edu> wrote: > On Mon, Aug 16, 2010 at 10:04 AM, Roy Stogner <royst...@ices.utexas.edu> > wrote: >> >> On Mon, 16 Aug 2010, Andrea Hawkins-Daarud wrote: >> >>> Ok, so I would call active_family_tree and then essentially use the >>> size of the returned elem vector? >> >> active_family_tree() returns a vector of all an element's active >> descendants: children, grandchildren, etc. I don't think there's a >> good way to get just the active children except by looping from >> child(0) to child(n_children-1) and testing to see whether each is >> active or not. > > Oops, for some reason I thought that all the descendants was what she > wanted... > > We could add an Elem::n_active_children() function with the simple > algorithm described above. What do you think Roy? > > -- > John > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
