[petsc-dev] MatComputeExplicitOperator

[Stefano Zampini]

What is the rationale behind MatComputeExplicitOperator returning SEQDENSE
in sequential and MPIAIJ in parallel?

Also, before commit
https://bitbucket.org/petsc/petsc/commits/b3d09e869df0e6ebcb615ca876706bfed4fcf1cd
 full
preallocation of the MPIAIJ matrix was happening. Now, if we have a very
dense operator that we want to sample just for testing purposes (inspecting
entries, etc..) we have to pay the price of reallocating over and over.

What is the proper fix? 1) Use MPIDENSE? 2) Restore full preallocation for
MPIAIJ? 3) Have MatComputeExplicitOperator to accept more arguments ?

I'm in favor of 1

-- 
Stefano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190419/c3259b05/attachment.html>