On Mon, May 23, 2016 at 6:39 AM, Karl Rupp <[email protected]> wrote:
> Hi Marco, > > > I'm struggling with this statement: > >> >> "It is recommended that you call both of the above preallocation >> routines [MatSeqAIJSetPreallocation and MatMPIAIJSetPreallocation] for >> simplicity." >> >> (source: >> https://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Mat/MATAIJ.html >> ) >> >> I saw that, even on a single-processor communicator, >> MatMPIAIJSetPreallocation works fine (at least, it gives no errors, >> but I don't know about efficiency drops). >> What's the effect of the recommended double preallocation? >> > > It allows you to quickly switch between a serial run and a parallel run. > If something doesn't work as expected, it's much easier to debug (if > possible) on a single rank, hence MatSeqAIJSetPreallocation. However, > ultimately you are looking for parallel runs, for which you need > MatMPIAIJSetPreallocation. Changing your code back and forth is > non-productive, hence it's recommended to call both and you get full > flexibility :-) > PETSc uses a system for dispatch that ignores functions which do not apply to that concrete type. This allows you to call a variety of specialization functions without a) constantly checking the type b) failure where a downcast might fail Thanks, Matt > Best regards, > Karli > -- 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
