Re: [Libmesh-devel] Why do we use vector instead of a matrix in FE?

2012-10-27 Thread Lorenzo Botti
Operator[] works for eigen vectors, the following is taken from the online documentation "The operator[] is also overloaded for index-based access in vectors, but keep in mind that C++ doesn't allow operator[] to take more than one argument. We restrict operator[] to vectors, because an awkwardnes

Re: [Libmesh-devel] Why do we use vector instead of a matrix in FE?

2012-10-27 Thread Kirk, Benjamin (JSC-EG311)
Lei, could you explain why this particular part is important to you? As Roy pointed out, for implicit apps this never shows up as a bottleneck, and for JFNK work I think Derek agrees there are other hotspots? Why not address those if performance is an issue? I don't want to discourage the chan

Re: [Libmesh-devel] Patch for computing SparsityPattern in parallel

2012-10-27 Thread Derek Gaston
Keep in mind the ability to add extra stuff to the sparsity pattern (using AugmentSparsityPattern). That is something we rely on. Also what is the current state of libMesh svn? I just got this compile error: Compiling C++ (in optimized mode) src/base/dof_map_constraints.C... src/base/dof_ma

Re: [Libmesh-devel] Patch for computing SparsityPattern in parallel

2012-10-27 Thread Roy Stogner
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 correc

Re: [Libmesh-devel] Patch for computing SparsityPattern in parallel

2012-10-27 Thread Derek Gaston
On Sat, Oct 27, 2012 at 10:09 AM, Roy Stogner wrote: > 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 o

Re: [Libmesh-devel] Patch for computing SparsityPattern in parallel

2012-10-27 Thread Derek Gaston
On Sat, Oct 27, 2012 at 10:09 AM, Roy Stogner wrote: > 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. > Hmmm... I'm still g

Re: [Libmesh-devel] Patch for computing SparsityPattern in parallel

2012-10-27 Thread Roy Stogner
On Sat, 27 Oct 2012, Derek Gaston wrote: We actually don't compute off-processor extra sparsity entries currently.  We do all the work to get all the info on the local processor that the local processor needs to make decisions about it's sparsity pattern and then just add the local entries. R

Re: [Libmesh-devel] Patch for computing SparsityPattern in parallel

2012-10-27 Thread Roy Stogner
On Sat, 27 Oct 2012, Derek Gaston wrote: Hmmm... I'm still getting this: src/base/dof_map_constraints.C: In member function ‘void libMesh::DofMap::scatter_constraints(libMesh::MeshBase&)’: src/base/dof_map_constraints.C:2871: error: ‘mesh’ was not declared in this scope make: *** [src/base/d