On Mon, Feb 6, 2012 at 12:40 PM, Jed Brown <[email protected]> wrote:
On Mon, Feb 6, 2012 at 20:35, Matthew Knepley <[email protected]> wrote:
VecCreate()
VecSetType() VecSetGhosted()
Is there a compelling reason for memory to be allocated before VecSetUp()? Deferring it would make it easier to specify what memory to use or specify ghosting in any order.
My preference is that ghosting is orthogonal to type, to the extent that it would make sense for the storage format (non-contiguous AMR grids might not be).
I don't like this because it would mean calling VecSetUp() all over the place. Couldn't the ghosting flag be on the same level as the sizes? Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener