From: Derek G. <fri...@gm...> - 2011-06-10 14:48:10
|
I'm still doing testing on System::update() with the large systems that are giving us problems. I haven't been able to isolate the problem yet.... but I'm working on it. I am thinking that the issue might actually be elsewhere but it's causing the failure in System::update().... I'm somewhat hopeful that after I track it down we might be able to revert System::update() to the previous algorithm. Sorry it's taking so long.... just hard to debug these big problems. Derek On Jun 10, 2011, at 8:44 AM, David Andrs wrote: > > Hi! > > So we bumped into another issue with the recent libMesh update. It seems that System::update() does not close() the solution vector any more, however this call is crucial if the solution vector is ghosted. > > Attached is the patch that fixes it. > > Thanks, > -- > David > > <0001-Ghosted-solution-has-to-be-closed-on-System-update.patch>------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev_______________________________________________ > Libmesh-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-devel |
From: Roy S. <roy...@ic...> - 2011-06-10 15:43:20
|
On Fri, 10 Jun 2011, Derek Gaston wrote: > I'm still doing testing on System::update() with the large systems > that are giving us problems. I haven't been able to isolate the > problem yet.... but I'm working on it. Thanks! Any chance I could get a look at the (tail of the) stack trace to help? I'm anxious to at least know whether the segfault hits us in localize() itself, _restore_array, a PETSc function, or elsewhere in the code. > I am thinking that the issue might actually be elsewhere but it's > causing the failure in System::update().... I'm somewhat hopeful > that after I track it down we might be able to revert > System::update() to the previous algorithm. > Sorry it's taking so long.... just hard to debug these big problems. Understandably so. And for what it's worth, I think I've massaged the code into more tolerable shape now; we've gone from "ugly workaround that will probably break on other localize() uses and that definitely breaks on PETSc+noMPI or Trilinos" to plain "ugly workaround". Still definitely worth investigating and probably worth reverting when we can, but now that it's no longer turning a bunch of regression tests red I'm no longer as anxious about the timeframe. --- Roy |