On Fri, 27 Aug 2010, Johannes A Huber wrote: > I was wondering, is it might be possible petsc_matric.C on line 72 (and > perhaps in other lines as well, like 139, 142, ...) > The matrix that is created in these lines is always quadratic > (n_global*n_global). I guess, the second argument to MatCreateSeqAIJ should be > m_global instead of n_global.
Let me run this by libmesh-devel (Ben Kirk is the one who wrote that code, and he surely understands it better than I do), but it looks to me like you're right. And since libMesh (and, I'd be willing to bet, all its primary developers) only creates square sparse matrices, we'd never have noticed a bug that breaks rectangular sparse matrix creation. > Furthermore I have a perhaps quite dumb question: Why can I only print from > process 0 after initializing libmesh: > > i.e. Proc 1 does not print after I initialized libMesh, but only before. Basically there are a lot of conditions which get encountered at every processor but for which we only want one message, not n_processors() messages. Our default behavior is for libMesh::out and libMesh::err to proxy cout and cerr, then disable the former on all other processors. Try --keep-cout if you don't want to disable anything. Or try --separate-libmeshout if you want the libMesh::out disabled on other processors but cout retained. There's also --redirect-stdout to send the libMesh output to files instead of stdout. --- Roy ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
