Dear Roy, On Wed, 14 Jan 2009, Roy Stogner wrote:
> By "that" I just meant the stuff you've referred to as "the other > side"; I don't have time to figure out the right PETSc APIs for > part-contiguous, part-sparse vectors. Okay, so I will start doing the NumericVector and the PetscVector stuff now. I will keep you informed. Now, the first problem I encounter -- but actually it's not really a problem -- is that PETSc supplies the possibility to automatically communicate any changes of vector components to the other processors that may have those indices as ghost indices. While, in a long term view, using that functionality would help to get rid of the duplicated solution representation, I think that I should for now *not* use that functionality since the current construction of current_local_solution does not expect that. Let me know if you have a different option. 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
