[aspect-devel] PETSc support

[Timo Heister]

> I take it back, I did find an Assertion being tripped, but in the Trilinos
> debug mode.  In the temperature statistics postprocessor, calls to
> local_range() are failing the assertion
>
> end-begin == vector->Map().NumMyElements()
>
> in trilinos_vector_base.h.  Seems like probably an easy fix somewhere?

Oops, yes. I will fix that later.

> Sure, especially for the AMG preconditioners.  I'm a little surprised that
> there is such a difference for the ILU preconditioners.

Agreed. That is strange.

>> Do you get any output if you do
>> mpirun -n 2 ./aspect -log_summary
>> or "-log_trace out" and look at the out.* files?
>>
>>
> Okay, due to the hanging, log_summary does not produce any output.
> log_trace, however, seems to have useful information.  I was wrong about it
> not getting past the MPI_Init stage.
>
> In general, there are several thousand petsc calls per processor, and then
> the processors appear to get out of sync and hang.
> [0] 1.06899 Event begin: MatMult [1] 1.06912 Event begin: VecCopy

Very strange. I'll switch to petsc optimized mode to see if I can
reproduce that.

-- 
Timo Heister
http://www.math.clemson.edu/~heister/