On Thu, 22 Jan 2009, Roy Stogner wrote: > On Thu, 22 Jan 2009, Tim Kroeger wrote: > >> I see. My idea is, since the vector is anyway cleared and re-initialized >> in operator=, why not use PETSc's VecDuplicate() function. > > Can that be sufficient? The manual page says VecDuplicate doesn't > copy the vector, just allocates storage for it.
Oops, you are right. I have obviously been misdirected by the function's name. > I think a > VecDuplicate followed by a VecCopy should do the trick, and I'll try > that out on the examples and on our few unit tests today if I find > time, but this is why I wanted other people looking at the problem; > I'm not familiar enough with PETSc's APIs Nor am I, as you see. That's just the problem. It would actually be nice if additional people would look at the code as well. On the other hand, having at least you and me looking at the PETSc part of it (and hopefully you and Ben on the "other" part) is at least better than only one person alone. > and I'm not a fan of trial-and-error coding and debugging. I agree than one shouldn't, but sometimes I tend to do so. (-: Best Regards, Tim -- Dr. Tim Kroeger [email protected] Phone +49-421-218-7710 [email protected] Fax +49-421-218-4236 Fraunhofer MEVIS, Institute for Medical Image Computing Universitaetsallee 29, 28359 Bremen, Germany ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
