On Thu, Mar 10, 2011 at 9:27 AM, John Peterson <[email protected]> wrote: > On Thu, Mar 10, 2011 at 9:09 AM, Tim Kroeger > <[email protected]> wrote: > > Well, print_personal() already takes an ostream& so I don't think we'd > be stepping outside the current bounds of its responsibilities to > provide it a reasonable execution path for when os != std::cout. For > PETSc, I think PETSC_VIEWER_ASCII_COMMON, which uses "a sparse format > common among all matrix types" would be the way to go in > print_personal to avoid printing the zeros.
Actually, print_personal() already handles the sparsity format pretty nicely, doesn't it (at least in PETSc-2.3.3)? I added a print_personal() call in ex4 and the lines look like: row 0: (0, 3.55556e+08) (1, -4.44444e+07) (2, -0.0222223) (3, -4.44444e+07) (4, 8.88889e+07) (5, 0.111111) ... row 1: (0, -4.44444e+07) (1, 3.55556e+08) (2, -0.0666666) (3, -0.0222223) (4, 8.88889e+07) ... ... Is this not already sufficient for your purposes? I mean, once we start sending it to a file instead of stdout of course... -- John ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
