Jed, I disagree; It's quite natural to want custom bindings for these things if you want some new mesh type to have local-to-global and global-to-local operations over that mesh. Having it abstracted out to the matrix or vector is constraining.
They should totally be in there and should be implementation-level in DMShell. - Peter On Thu, Feb 21, 2013 at 12:42 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote: > It would be natural to have a matching interface, but why do you need it? > You're in charge of making the matrices and vectors so you can give them > local-to-global mappings. The only solver that calls > DMGetLocalToGlobalMapping is PCEXOTIC, which only works with DMDA anyway. > > > On Thu, Feb 21, 2013 at 12:35 PM, Richard Tran Mills <rtm at > eecs.utk.edu>wrote: > >> Hi Folks, >> >> I want to set a LocalToGlobal mapping in a DMShell object. Should we add >> a DMShell routine to do this, or just add a DMSetLocalToGlobalMapping() >> routine? >> >> Thanks, >> Richard >> >> -- >> Richard Tran Mills, Ph.D. >> Computational Earth Scientist | Joint Assistant Professor >> Hydrogeochemical Dynamics Team | EECS and Earth & Planetary Sciences >> Oak Ridge National Laboratory | University of Tennessee, Knoxville >> E-mail: rmills at ornl.gov V: 865-241-3198 http://climate.ornl.gov/~** >> rmills <http://climate.ornl.gov/~rmills> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130221/12043a8a/attachment.html>
