So... running into more than a few issues with ParallelMesh... most of them are fairly simple fixes but this one I'm not quite sure that this is the right way to solve it.
The problem is that you can't call is_child_on_side on a RemoteElem. This was happening in Elem::active_family_tree_by_side() (even when the base of that tree was _not_ a RemoteElem itself). All I've done is put a check in to make sure it's not a RemoteElem.... but I am wondering if this could have some adverse effects. What do you think? Derek
0001-don-t-call-is_child_on_side-on-a-Remote-elem.patch
Description: Binary data
------------------------------------------------------------------------------ Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
