The mailing list has been very busy the last few weeks and the team here at the INL has fallen a little bit behind on libMesh revisions. It turns out that a couple of the commits over the last week have caused us some issues.
It appears that a number of our regression tests are failing with the removal
of the "clear()" call out of the petsc_nonlinear_solver interface (r4223). In
addition, we have other tests that are failing independently with the addition
of this new logic (2 lines in 2 places) in the system_project method (r4224).
Specifically the following logic:
// If this element doesn't have an old_dof_object with dofs for the
// current system, then it must be newly added, so the user
// is responsible for setting the new dofs.
if (!elem->old_dof_object ||
!elem->old_dof_object->has_dofs(system.number()))
continue;
I've had John and Derek in on the discussion and none of us have any concrete
reasoning right now to pin point the root of the problem. For now I just
wanted to toss this observation out there with the patch that we are currently
using to undo these changes which fixes all of our issues. Perhaps we should
revisit some of the discussion from last week to reevaluate some of the choices
made.
Thanks,
Cody
libmesh.patch
Description: Binary data
------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
