We can do all this, but how much effort do we really want to make for
supporting these inconvenient "convenience routines"?
BTW: We should really label these function with
Level: Recommended only for legacy applications being quickly ported to PETSc
I really only want people who already have a working non-PETSc code that
uses CSR directly already to use these routines so they can quickly try out
PETSc, I never want someone writing fresh code or doing a large refactorization
to EVER use these routines.
> On second thought, why don't we just document that
> MatMPIBAIJSetPreallocationCSR respects MAT_ROW_ORIENTED within each
> block and let the user choose which they want to use?
Also there is no way to get this flag into MatCreateMPIBAIJWithArrays()
Barry
On Sep 29, 2013, at 1:13 PM, Jed Brown <[email protected]> wrote:
> Jed Brown <[email protected]> writes:
>
>> Barry Smith <[email protected]> writes:
>>
>>> Fixed and accidentally pushed directly to maint at bitbucket
>>
>> Should warn that this function permanently changes MAT_ROW_ORIENTED and
>> thus will affect subsequent calls to MatSetValues. Or (better, in my
>> opinion) restore the original value of that option before returning.
>
> On second thought, why don't we just document that
> MatMPIBAIJSetPreallocationCSR respects MAT_ROW_ORIENTED within each
> block and let the user choose which they want to use?
