Re: [deal.II] Difference between BlockDynamicSparsityPattern and TrilinosWrappers::BlockSparsityPattern

2019-09-04 Thread Bruno Blais
Dear Wolfgang, Thank you, everything is clear now and i managed to accomplish what I wanted. Thanks! Bruno On Tuesday, 3 September 2019 19:09:00 UTC-4, Wolfgang Bangerth wrote: > > > Bruno, > > > Is there a different between how DynamicSparsityPatterns and > > BlockDynamicSparsityPatterns

Re: [deal.II] Difference between BlockDynamicSparsityPattern and TrilinosWrappers::BlockSparsityPattern

2019-09-03 Thread Wolfgang Bangerth
Bruno, > Is there a different between how DynamicSparsityPatterns and > BlockDynamicSparsityPatterns behave? The latter is just an array of the former. Under the hood, every block is simply a DynamicSparsityPattern that can be initialized in the same way one always does. > When you look

Re: [deal.II] Difference between BlockDynamicSparsityPattern and TrilinosWrappers::BlockSparsityPattern

2019-09-01 Thread Bruno Blais
Dear Wolfgang, Thank you very much for your message. Is there a different between how DynamicSparsityPatterns and BlockDynamicSparsityPatterns behave? When you look at step-40, which is the first "MPI" step, the way the sparsity pattern is made is (

Re: [deal.II] Difference between BlockDynamicSparsityPattern and TrilinosWrappers::BlockSparsityPattern

2019-08-30 Thread Wolfgang Bangerth
Bruno, I don't quite recall if we ever used the BlockDynamicSparsityPattern in a parallel context. For sure, the way you're initializing it implies that every process allocates the memory for all DoFs as it's not given the information about locally_relevant_dofs. I'd have to look up whether

[deal.II] Difference between BlockDynamicSparsityPattern and TrilinosWrappers::BlockSparsityPattern

2019-08-30 Thread Bruno Blais
Hello, I am currently working on a parallel implementation of step-57, thus I am learning to live with BlockVectors, BlockMatrices and BlockSparsityPatterns in parallel. Originally, I thought that I could make my sparsity pattern the following way (i.e as in step-57, but distributing it