On Tue, 27 Jan 2009, Tim Kroeger wrote:

> I invented two new methods in NumericVector that might help you: One is 
> NumericVector::is_ghosted(), that you can use to query whether a given vector 
> does contain ghost dofs, and the other is NumericVector::init(const 
> NumericVector&), which will initialize the vector using the same storage 
> scheme (i.e. parallel/serial/ghosted) as its argument.

That's excellent; it should be enough to fix system_projection.C.
That might take a little while, though; I'm busy this week, and I just
realized that to be worthwhile to you, I'll need to fix
project_vector() the *right* way, using a ghosted vector for
communication and not just using a temporary serial vector.

There's at least one more outstanding bug with your patch, though:
some regression has ex15 apparently converging to the correct solution
but reporting wildly incorrect ExactErrorEstimator values.  Hopefully
that'll be a simple bug to find, but since ex15 resolves a
steady-state equation after each refinement/projection, I don't think
it's the same problem.  ex14 looks to be affected too.

I'll take a crack at both of them this weekend.

> So there's no reason for me to be worried if I don't understand that code, is 
> there?  (-:

Hey, as long as having your solution accuracy depend on my
incomprehensible hack doesn't bother you!  I hardly ever wake up
sweating in terror about it anymore.
---
Roy

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to