On Wed, 14 Jan 2009, Tim Kroeger wrote: >>> I think that adding the required functionality to NumericVector and >>> PetscVector would not be too complicated (PETSc's VecCreateGhost() >>> seems to do the trick). I can try to do this part myself, that is to >>> add a constructor that aditionally takes a list of ghost indices that >>> we want to store (and implement everything on the PETSc side). The >>> other side is to make the System class use that new constructor (in >>> PETSc case at least) and, in particular, determine which indices are >>> actually required. And to do the correct thing when the grid is >>> refined/coarsened. I feel not able to implement that part because I'm >>> not familiar enough with the interna of libMesh. >> >> Yeah, I can do that easily enough. Ben's already done the hard work >> of properly creating the "send_list" of ghost DoFs; I don't think I'll >> have any problem figuring out when to plug that into a constructor or >> reinitialization function. > > What do you mean by "Yeah"? Would you like me to do something > (NumericVector, PetscVector), or do you mean you will do everything > yourselves?
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. I'll write "dummy" implementations for Laspack and Trilinos vectors too - not to get the same performance out of them yet, but just to make sure stuff still compiles after the change. > In any case, is there any idea about when this will be usable? Depends how fast you get the Petsc implementation working. ;-) But if you put in that part of the work, I'll do my best not to hold you up waiting for the rest. This won't be a high priority yet on my day job, but for a real chance at finishing something that's been on the libMesh TODO list for years, I wouldn't mind working a couple nights or a weekend. --- Roy ------------------------------------------------------------------------------ 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
