On Tue, 1 Jun 2010, Vijay S. Mahadevan wrote: > From a user perspective, It is a little annoying that I can never > access the actual dof_number associated with the unknown at the node > due to the assert failures. Since all other build versions of the code > give me the correct dof-number (I've verified this for small meshes), > I think that the assert triggers a wrong failure for this use-case.
No, IF the number of components on a node is zero, then asking for the index of the first component on the node makes no sense. The assert is correct. But if that IF is wrong: > There are dofs associated with the nodes and there are dofs associated > with the elements based on the chosen basis. This would be an underlying bug. What elements are you using, with what bases? Can you put together a test case that replicates the problem? --- Roy ------------------------------------------------------------------------------ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
