On Sat, 27 Oct 2012, Derek Gaston wrote:
Keep in mind the ability to add extra stuff to the sparsity pattern
(using AugmentSparsityPattern). That is something we rely on.
Hmm... how do you want to handle extra sparsity entries in the
distributed case?
1. User code is responsible for correctly adding all extra entries to
each processor's sparsity rows on that processor. This should still
work fine now.
2. User code can add extra remote sparsity entries to the new
nonlocal part of the sparsity pattern, and then they get passed on to
the right processors in the communications step. This would be work
after I move one line.
You know, supporting (2) wouldn't actually add anything to
computational cost and wouldn't interfere with support for (1). I'm
leaning toward (2) now. ;-)
src/base/dof_map_constraints.C:2875: error: ‘mesh’ was not declared in this
scope
make: *** [src/base/dof_map_constraints.x86_64-apple-darwin11.4.2.opt.o] Error 1
Should be fixed in r6227, thanks.
---
Roy
------------------------------------------------------------------------------
WINDOWS 8 is here.
Millions of people. Your app in 30 days.
Visit The Windows 8 Center at Sourceforge for all your go to resources.
http://windows8center.sourceforge.net/
join-generation-app-and-make-money-coding-fast/
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
